dhcp issue
Timothy Murphy
tim at birdsnest.maths.tcd.ie
Sat Sep 2 14:05:37 UTC 2006
Gbenga Shobowale wrote:
> On 9/2/06, Timothy Murphy <tim at birdsnest.maths.tcd.ie> wrote:
>> Gbenga Shobowale wrote:
>>
>> > I just upgrade to FC5 before then I had 2 NIC in one with static IP
>> > and other on DHCP, however after the upgrade my machine can't seem to
>> > up up an IP from the modem...I Check the card its configured properly
>> > and the one with a static IP works fine...I put the link on a windows
>> > machine and it work..hence I think FC is having a problem with
>> > DHCP..any ideas anyone?
>>
>> Maybe eth0 and eth1 have been swapped?
>> What does ifconfig say?
> eth0 Link encap:Ethernet HWaddr 00:01:53:00:E9:0C
> inet addr:172.16.1.2 Bcast:172.16.1.255 Mask:255.255.255.0
> inet6 addr: fe80::201:53ff:fe00:e90c/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:530 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:25415 (24.8 KiB)
> Interrupt:21 Base address:0xcc00
>
> eth1 Link encap:Ethernet HWaddr 00:11:5B:38:06:EA
> inet6 addr: fe80::211:5bff:fe38:6ea/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:67 errors:0 dropped:0 overruns:0 frame:0
> TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:6283 (6.1 KiB) TX bytes:5292 (5.1 KiB)
> Interrupt:17 Base address:0xc800
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:286 errors:0 dropped:0 overruns:0 frame:0
> TX packets:286 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:26190 (25.5 KiB) TX bytes:26190 (25.5 KiB)
>
> I swapped it no dice...
> Is there some thing in the kernel that could be causing this issue?
I wouldn't have thought so.
It seems to me more likely that there is something incorrect
in /etc/sysconfig/network-scripts/ifcfg-eth[01] .
Maybe you could show them, if you still have a problem.
Since eth1 has come up, I think the kernel must be finding the driver.
But the above does not show eth[01] are the right way round.
You could add IPV6INIT=no to ifcfg-eth1,
though I doubt if that is the problem.
What does /var/log/messages say about DHCP -
is eth1 looking for an address?
Ps I don't claim to be a network guru!
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
More information about the fedora-list
mailing list