On Thu, Oct 9, 2008 at 12:15 AM, Dave Feustel <dfeustel(a)mindspring.com&gt;wrote: > On Wed, Oct 08, 2008 at 10:20:17PM +0100, Laura Speck wrote: > > Hey all, > > > > I am having a problem with a brand new install of Fedora 9. This > > machine has two nic's, eth0 and eth1. They are both . We currently > > have eth0 plugged into a router, had eth1 plugged in earlier to try it > > as well but we have this problem on both nics. > > > > Basically, on install we specified that both nics were to be dhcp, and > > to come up on boot. But neither of them get an ip on boot. I know that > > it's not a problem with the cable, as we plugged it into a different > > machine and it works fine. I don't think it's a problem with the nics > > as I can't see both of them being toast on a new machine. > > > > ifconfig eth0 up does nothing. I've gotten someone local to the server > > to try dhclient eth0 and then tail /var/log/messages. We see > > DHCPREQUEST, a bunch of DHCPDISCOVER lines and then end with a "No > > DHCPOFFERS received" message. ifconfig never shows either interface as > > having an "inet ..." line, but they get an "inet6 ..." line. I know > > it's not a problem with the dhcp server because it's our isp's, and > > our other machines can grab an ip fine. > > > > I've shut off Networkmanager (service NetworkManager stop) and started > > the network (service network start). > > > > service network start outputs: > > Bringing up loopback interface [OK] > > Bringing up interface eth0: > > Determining IP information for eth0... failed. [FAILED] > > Bringing up interface eth0: > > Determining IP information for eth1... failed. No link available. > > Check cable. [FAILED] > > > > Our /etc/sysconfig/network-scripts/ifcfg-eth0 looks like... > > > > DEVICE=eth0 > > BOOTPROTO=dhcp > > ONBOOT=yes > > > > Any tips would be greatly appreciated. Thanks in advance! > > > > Laura > > I have F9 running on a computer with just one nic. Everything worked > until about a week ago, when the nic suddenly no longer automatically > got a dhcp address. My work around is to run dhclient etho &. DHCP > connects then. I still haven't figured out why this happened or what > the correct fix is. > You're missing the HWADDR= stanzas in your configs. This tells the kernel which NIC is actually eth0 and eth1 by identifying the MAC address.

Dave Feustel wrote: > On Wed, Oct 08, 2008 at 10:20:17PM +0100, Laura Speck wrote: > I have F9 running on a computer with just one nic. Everything worked > until about a week ago, when the nic suddenly no longer automatically > got a dhcp address. My work around is to run dhclient etho &. DHCP > connects then. I still haven't figured out why this happened or what > the correct fix is. > I had a thread going about the recent "enhancement" to NetworkManager. After applying that both my hardwire and wireless NICs stopped working. Did you by any chance "upgrade" your packages recently, say about the time everything stopped working? Mine worked after the upgrade until the next reboot, then went away forever. I tried to force a downgrade, but rpm was designed to work in one direction only, there's no way to tell rpm or yum to roll back and rollback all the dependencies at the same time. I gave up, I removed NM totally and completely, and now do the whole setup with a script run at boot time.

Hey all, I am having a problem with a brand new install of Fedora 9. This machine has two nic's, eth0 and eth1. They are both . We currently have eth0 plugged into a router, had eth1 plugged in earlier to try it as well but we have this problem on both nics. Basically, on install we specified that both nics were to be dhcp, and to come up on boot. But neither of them get an ip on boot. I know that it's not a problem with the cable, as we plugged it into a different machine and it works fine. I don't think it's a problem with the nics as I can't see both of them being toast on a new machine. ifconfig eth0 up does nothing. I've gotten someone local to the server to try dhclient eth0 and then tail /var/log/messages. We see DHCPREQUEST, a bunch of DHCPDISCOVER lines and then end with a "No DHCPOFFERS received" message. ifconfig never shows either interface as having an "inet ..." line, but they get an "inet6 ..." line. I know it's not a problem with the dhcp server because it's our isp's, and our other machines can grab an ip fine. I've shut off Networkmanager (service NetworkManager stop) and started the network (service network start). service network start outputs: Bringing up loopback interface [OK] Bringing up interface eth0: Determining IP information for eth0... failed. [FAILED] Bringing up interface eth0: Determining IP information for eth1... failed. No link available. Check cable. [FAILED] Our /etc/sysconfig/network-scripts/ifcfg-eth0 looks like... DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes Any tips would be greatly appreciated. Thanks in advance! Laura -- fedora-list mailing list fedora-list(a)redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

On Fri, 2008-10-10 at 15:41 -0400, Bill Davidsen wrote: > I tried "Ad-hic" as well, so I could set the channel Ad-hoc mode is for connecting peer-to-peer without an access point, not the sort of thing that you want to do, usually.

I tried "Ad-hic" as well, so I could set the channel

Dave Feustel wrote: >> I gave up, I removed NM totally and completely, and now do the whole >> setup with a script run at boot time. > > All I have do to get connectivity is run dhclient as root. >

Interesting. I run iwconfig to set the essid, channel, and key. Then dhclient. Previously NM had all the info except the channel, and figured that out in "Managed" mode. After it stopped working I tried "Ad-hic" as well, so I could set the channel. Made no difference.

On Wed, Oct 08, 2008 at 10:20:17PM +0100, Laura Speck wrote:

I have F9 running on a computer with just one nic. Everything worked until about a week ago, when the nic suddenly no longer automatically got a dhcp address. My work around is to run dhclient etho &. DHCP connects then. I still haven't figured out why this happened or what the correct fix is.

Hey all, I am having a problem with a brand new install of Fedora 9. This machine has two nic's, eth0 and eth1. They are both . We currently have eth0 plugged into a router, had eth1 plugged in earlier to try it as well but we have this problem on both nics. Basically, on install we specified that both nics were to be dhcp, and to come up on boot. But neither of them get an ip on boot. I know that it's not a problem with the cable, as we plugged it into a different machine and it works fine. I don't think it's a problem with the nics as I can't see both of them being toast on a new machine. ifconfig eth0 up does nothing. I've gotten someone local to the server to try dhclient eth0 and then tail /var/log/messages. We see DHCPREQUEST, a bunch of DHCPDISCOVER lines and then end with a "No DHCPOFFERS received" message. ifconfig never shows either interface as having an "inet ..." line, but they get an "inet6 ..." line. I know it's not a problem with the dhcp server because it's our isp's, and our other machines can grab an ip fine. I've shut off Networkmanager (service NetworkManager stop) and started the network (service network start). service network start outputs: Bringing up loopback interface [OK] Bringing up interface eth0: Determining IP information for eth0... failed. [FAILED] Bringing up interface eth0: Determining IP information for eth1... failed. No link available. Check cable. [FAILED] Our /etc/sysconfig/network-scripts/ifcfg-eth0 looks like... DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes Any tips would be greatly appreciated. Thanks in advance! Laura

Hey all, I am having a problem with a brand new install of Fedora 9. This machine has two nic's, eth0 and eth1. They are both . We currently have eth0 plugged into a router, had eth1 plugged in earlier to try it as well but we have this problem on both nics. Basically, on install we specified that both nics were to be dhcp, and to come up on boot. But neither of them get an ip on boot. I know that it's not a problem with the cable, as we plugged it into a different machine and it works fine. I don't think it's a problem with the nics as I can't see both of them being toast on a new machine. ifconfig eth0 up does nothing. I've gotten someone local to the server to try dhclient eth0 and then tail /var/log/messages. We see DHCPREQUEST, a bunch of DHCPDISCOVER lines and then end with a "No DHCPOFFERS received" message. ifconfig never shows either interface as having an "inet ..." line, but they get an "inet6 ..." line. I know it's not a problem with the dhcp server because it's our isp's, and our other machines can grab an ip fine. I've shut off Networkmanager (service NetworkManager stop) and started the network (service network start). service network start outputs: Bringing up loopback interface [OK] Bringing up interface eth0: Determining IP information for eth0... failed. [FAILED] Bringing up interface eth0: Determining IP information for eth1... failed. No link available. Check cable. [FAILED] Our /etc/sysconfig/network-scripts/ifcfg-eth0 looks like... DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes Any tips would be greatly appreciated. Thanks in advance! Laura

> That's probably poor configuration - many access points come with a > predefined name (e.g. calling themselves "linksys") and their owners > never bother to change them.

To be honest it's probably a really bad configuration, but the essid is not the preset. The idea is that regular staff have one channel and one key, and executive staff have the other channel and key, but both APs share a name. At least with Windows that hasn't been an issue, although I see no reason why they didn't use two names.

> There is a use for having access points with the same ID, so that users > roaming through a large complex could just connect to "college" with the > nearest access point answering to that name. Though you'd also have the > same key on all the access points.

The nearby college has a load of same, just as you describe. I have no idea if the APs hand off like cell towers, I suspect not, but if the reconnect logic is robust and includes a search (and maybe use strongest match) I guess it might work as students wander the campus.

Mark Haney wrote: > Laura Speck wrote: >> 2008/10/9 Michael Magua <mmglug(a)gmail.com&gt;: >>> On Thu, Oct 9, 2008 at 12:15 AM, Dave Feustel <dfeustel(a)mindspring.com&gt; >>> wrote: >>>> On Wed, Oct 08, 2008 at 10:20:17PM +0100, Laura Speck wrote: >>>>> Hey all, >>>>> >>>>> I am having a problem with a brand new install of Fedora 9. This >>>>> machine has two nic's, eth0 and eth1. They are both . We currently >>>>> have eth0 plugged into a router, had eth1 plugged in earlier to >>>>> try it >>>>> as well but we have this problem on both nics. >>>>> >>>>> Basically, on install we specified that both nics were to be dhcp, >>>>> and >>>>> to come up on boot. But neither of them get an ip on boot. I know >>>>> that >>>>> it's not a problem with the cable, as we plugged it into a different >>>>> machine and it works fine. I don't think it's a problem with the nics >>>>> as I can't see both of them being toast on a new machine. >>>>> >>>>> ifconfig eth0 up does nothing. I've gotten someone local to the >>>>> server >>>>> to try dhclient eth0 and then tail /var/log/messages. We see >>>>> DHCPREQUEST, a bunch of DHCPDISCOVER lines and then end with a "No >>>>> DHCPOFFERS received" message. ifconfig never shows either >>>>> interface as >>>>> having an "inet ..." line, but they get an "inet6 ..." line. I know >>>>> it's not a problem with the dhcp server because it's our isp's, and >>>>> our other machines can grab an ip fine. >>>>> >>>>> I've shut off Networkmanager (service NetworkManager stop) and >>>>> started >>>>> the network (service network start). >>>>> >>>>> service network start outputs: >>>>> Bringing up loopback interface [OK] >>>>> Bringing up interface eth0: >>>>> Determining IP information for eth0... failed. [FAILED] >>>>> Bringing up interface eth0: >>>>> Determining IP information for eth1... failed. No link available. >>>>> Check cable. [FAILED] >>>>> >>>>> Our /etc/sysconfig/network-scripts/ifcfg-eth0 looks like... >>>>> >>>>> DEVICE=eth0 >>>>> BOOTPROTO=dhcp >>>>> ONBOOT=yes >>>>> >>>>> Any tips would be greatly appreciated. Thanks in advance! >>>>> >>>>> Laura >>>> I have F9 running on a computer with just one nic. Everything worked >>>> until about a week ago, when the nic suddenly no longer automatically >>>> got a dhcp address. My work around is to run dhclient etho &. DHCP >>>> connects then. I still haven't figured out why this happened or what >>>> the correct fix is. >>> >>> You're missing the HWADDR= stanzas in your configs. This tells the >>> kernel >>> which NIC is actually eth0 and eth1 by identifying the MAC address. >> >> Thanks, but nothing seems to change when I add the HWADDR to both >> eth's configs, so the problem is still existing. >> >> -- >> Laura >> > > Just for fun, have you checked to see if you have any available IP > addresses on your router? > > We had this problem a while back and it turned out our leases were > permanent and once the pool was used up, no one could get a lease. > > > No, they plugged in another computer to the router and according to them it worked fine. My guess is the drivers for both net cards are not correct. Who is the manufacturer of the cards?