dhcp problem FC2

Jim Dishaw (dishawjp) no-reply-gw at fcp.homelinux.org
Sun Mar 20 16:18:31 UTC 2005 

My main computer is a dual boot FC2/FC3 machine. A while back I had some really serious issues with FC3, probably 
related to a combination of running SELinux (which I still 
 insist on running) and bad mixing of apt repositories. 
Anyway, I reinstalled and FC3 was fine. During the install 
I had hosed grub and lost my FC2 bootloader and just got 
around to fixing that last night. Now it dual boots 
perfectly. But I do now have a problem with FC2. I can't 
get DHCP information on eth0,  or ppp0, but only with FC2. 
They both work fine with FC3 and the same setup used to 
work fine in FC2. The only change I made to FC2 was to 
delete a single line in its /etc/fstab that was pointing 
to a nonexistant swap partition I used to have on the hard 
drive that FC3 is installed on. Grub is installed (now) on 
hdc which is the hard drive that FC3 is installed on, so I 
didn't even mess with that.

 When I first boot to FC2, my ifconfig looks like this: 

[code]
[dishawjp at eunix dishawjp]$ /sbin/ifconfig
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:246 errors:0 dropped:0 overruns:0 frame:0
          TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:16994 (16.5 Kb)  TX bytes:16994 (16.5 Kb)

[dishawjp at eunix dishawjp]$ 
[/code]
Which is exactly what I want. I want both interfaces (eth0 
and ppp0) to be user controlled. I have the command 
"/sbin/ifup eth0" aliased to "net" and when I give that 
command, I get this: 
[code]
[dishawjp at eunix dishawjp]$ net

Determining IP information for eth0... failed.
[dishawjp at eunix dishawjp]$ 
[/code]
But then checking my ifconfig, I get this: 
[code]
[dishawjp at eunix dishawjp]$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 02:00:06:E3:3E:9C
          inet6 addr: fe80::6ff:fee3:3e9c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5273 errors:1 dropped:0 overruns:0 frame:0
          TX packets:6 errors:4 dropped:0 overruns:0 carrier:4
          collisions:0 txqueuelen:1000
          RX bytes:316380 (308.9 Kb)  TX bytes:1508 (1.4 Kb)
          Interrupt:11 Base address:0xef00

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:248 errors:0 dropped:0 overruns:0 frame:0
          TX packets:248 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:17098 (16.6 Kb)  TX bytes:17098 (16.6 Kb)

[dishawjp at eunix dishawjp]$ 
[/code]
If I try to ping a remote host, I get:
[code]
[dishawjp at eunix network-scripts]$ ping http://www.yahoo.com
ping: unknown host http://www.yahoo.com
[dishawjp at eunix network-scripts]$ 
[/code]
Looking at my ifcfg-eth0 I find: 
[code]

[dishawjp at eunix network-scripts]$ more ifcfg-eth0
# Lite-On|LNE100TX
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=02:00:06:e3:3e:9c
ONBOOT=no
TYPE=Ethernet
USERCTL=yes
PEERDNS=yes
IPV6INIT=yes
[dishawjp at eunix network-scripts]$ 
[/code]
Which looks to be fine to me.

I have tried disabling iptables to see if it was a 
firewall issue.  My /etc/resolv.conf looks to be fine.  
I have checked all my settings in "system-config-network" 
and they are good.  The same as they are in my FC3 boot and 
they work fine there.  My /etc/modprobe.conf is loading the 
tulip driver for eth0 so that looks good.  I have googled 
this quite a bit but found nothing there that was quite 
the same. Pulling th erelevant lines from my /var/log/messages, I get the following:
for ppp0:
[code]

Mar 19 21:34:30 eunix ifup-ppp: pppd started for ppp0 on /dev/modem at 115200
Mar 19 21:34:30 eunix kernel: CSLIP: code copyright 1989 Regents of the University of California
Mar 19 21:34:30 eunix kernel: PPP generic driver version 2.4.2
Mar 19 21:34:30 eunix pppd[2470]: pppd 2.4.2 started by root, uid 0
Mar 19 21:34:31 eunix wvdial[2492]: WvDial: Internet dialer version 1.53
Mar 19 21:34:31 eunix wvdial[2492]: Initializing modem.
Mar 19 21:34:32 eunix wvdial[2492]: Sending: ATZ
Mar 19 21:34:32 eunix wvdial[2492]: ATZ
Mar 19 21:34:32 eunix wvdial[2492]: OK
Mar 19 21:34:32 eunix wvdial[2492]: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Mar 19 21:34:32 eunix wvdial[2492]: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Mar 19 21:34:32 eunix wvdial[2492]: OK
Mar 19 21:34:32 eunix wvdial[2492]: Sending: ATM1L2
Mar 19 21:34:32 eunix wvdial[2492]: ATM1L2
Mar 19 21:34:32 eunix wvdial[2492]: OK
Mar 19 21:34:32 eunix wvdial[2492]: Modem initialized.
Mar 19 21:34:32 eunix wvdial[2492]: Sending: ATDT5795300
Mar 19 21:34:32 eunix wvdial[2492]: Waiting for carrier.
Mar 19 21:34:32 eunix wvdial[2492]: ATDT5795300
Mar 19 21:35:01 eunix wvdial[2492]: CONNECT 48000/ARQ/V90/LAPM/V42BIS
Mar 19 21:35:01 eunix wvdial[2492]: Carrier detected.  Waiting for prompt.
Mar 19 21:35:03 eunix wvdial[2492]: NO CARRIER
Mar 19 21:35:13 eunix wvdial[2492]: Don't know what to do!  Starting pppd and hoping for the best.
Mar 19 21:35:13 eunix pppd[2470]: Serial connection established.
Mar 19 21:35:13 eunix pppd[2470]: Using interface ppp0
Mar 19 21:35:13 eunix pppd[2470]: Connect: ppp0 <--> /dev/modem
Mar 19 21:35:14 eunix pppd[2470]: Serial line is looped back.
Mar 19 21:35:14 eunix pppd[2470]: Connection terminated.
Mar 19 21:35:15 eunix pppd[2470]: Exit. 
[/code]
and for eth0:
[code]
Mar 19 21:37:04 eunix dhclient: sit0: unknown hardware address type 776
Mar 19 21:37:05 eunix dhclient: sit0: unknown hardware address type 776
Mar 19 21:37:07 eunix kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
Mar 19 21:37:08 eunix dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Mar 19 21:37:16 eunix dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Mar 19 21:37:32 eunix dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Mar 19 21:37:45 eunix dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Mar 19 21:37:57 eunix dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Mar 19 21:38:04 eunix dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Mar 19 21:38:09 eunix dhclient: No DHCPOFFERS received. 
[/code]

Any insight from the gurus here greatly appreciated.

Jim Dishaw


-- 
This is an email sent via the webforum on http://fcp.homelinux.org
http://fcp.homelinux.org/modules/newbb/viewtopic.php?post_id=51223&topic_id=12926&forum=10#forumpost51223

More information about the fedora-list mailing list