|
Hi Folks, I was hoping that someone might be able to help me with this or direct me to another internet group that would.... Summary: DHCP is not getting set-up correctly on the Linux side. On the Windows side all is okay. So the network card would appear okay. Detailed Description: Linux/Debian: It doesn't seem to matter which kernel is used (tried both 2.4.25 and 2.6.7). The ethernet driver in use is the fealnx. Hardware: PC with AMD K7 processor. Connectivity: I am trying to connect to a cable modem. The way it works by me is first you get a dhcp lease from the cable company and then one tunnels using pptp to obtain the connection to the ISP. The present problem is that the initial dhcp connection does not seem to be properly setup. When running dhclient the following occurs: --------------------------- andromeda:/etc# dhclient Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved. Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html Listening on LPF/dummy0/1a:60:19:07:1a:f0 Sending on LPF/dummy0/1a:60:19:07:1a:f0 Listening on LPF/lo/<null> Sending on LPF/lo/<null> Listening on LPF/eth0/00:e0:50:02:89:88 Sending on LPF/eth0/00:e0:50:02:89:88 Sending on Socket/fallback/fallback-net DHCPDISCOVER on dummy0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 4 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 10.206.192.1 SIOCADDRT: Network is unreachable bound to 172.25.221.21 -- renewal in 271209 seconds. andromeda:/etc# --------------------------------------------- Things that I have noticed here are: 1) the IP address that the card binds to 172.25.221.21 is the same address each time and is NOT the same as on the Windows side. 2) The message "SIOCADDRT: Network is unreachable" can not be good. Except for the IP address the differences between ifconfig for linux and ipconfig for Windows seem small: Linux: andromeda:/etc# ifconfig eth0 Link encap:Ethernet HWaddr 00:E0:50:02:89:88 inet addr:172.25.221.21 Bcast:255.255.255.255 Mask:255.255.224.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12118 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:786783 (768.3 KiB) TX bytes:1710 (1.6 KiB) Interrupt:18 Base address:0xe800 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:211 errors:0 dropped:0 overruns:0 frame:0 TX packets:211 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:66050 (64.5 KiB) TX bytes:66050 (64.5 KiB) andromeda:/etc# -------------------------------- Windows: C:\Documents and Settings\Joshua>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : andromeda Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139/810X Family PCI Fast Ethernet NIC Physical Address. . . . . . . . . : 00-E0-50-02-89-88 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 172.25.207.86 Subnet Mask . . . . . . . . . . . : 255.255.224.0 Default Gateway . . . . . . . . . : 172.25.224.1 DHCP Server . . . . . . . . . . . : 213.57.35.2 DNS Servers . . . . . . . . . . . : 192.168.101.102 192.168.101.101 Lease Obtained. . . . . . . . . . : Monday, November 08, 2004 11:26:45 A M Lease Expires . . . . . . . . . . : Sunday, November 14, 2004 1:49:53 AM C:\Documents and Settings\Joshua> ------------------------------------------------------ At this point I probably should mention that Debian during installation told me I should use the fealnx driver, while windows used the Realtek RTL... driver. Normally I would have thought that therefore my card would correspond to the 8139too driver, but that driver I would never work with the card while the fealnx driver binded right to it. Well, back to the main point.... Finally the difference in the route tables are:... Linux: andromeda:/etc# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.25.192.0 * 255.255.224.0 U 0 0 0 eth0 andromeda:/etc# ---------------------------------- While Windows is something huge... C:\Documents and Settings\Joshua>route print =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x2 ...00 e0 50 02 89 88 ...... Asound 10/100M Based Fast Ethernet Card - Pack Scheduler Miniport =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.25.224.1 172.25.207.86 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 172.25.192.0 255.255.224.0 172.25.207.86 172.25.207.86 20 172.25.207.86 255.255.255.255 127.0.0.1 127.0.0.1 20 172.25.255.255 255.255.255.255 172.25.207.86 172.25.207.86 20 224.0.0.0 240.0.0.0 172.25.207.86 172.25.207.86 20 255.255.255.255 255.255.255.255 172.25.207.86 172.25.207.86 1 Default Gateway: 172.25.224.1 =========================================================================== Persistent Routes: None Of which none of the routes match the one put in by linux. One final note, I can ping the eth0 card directly, so it does indeed seem to be working on some level. Also it definently appears to begin to get the dhcp info. For instance the addresses is resolv.conf match those stated as the DNS servers by Windows. So here I am wondering if perhaps I need t change something in the dhclient.conf file, although nothing I have done so far seems to have moved this problem along. If anyone has any idea of what I can try next I would be gratefull. Regards, Joshua |
- Re: Problems with DHCP Setup Joshua J. Brickel
- Re: Problems with DHCP Setup Ben Hutchings
- Re: Problems with DHCP Setup Andrea Vettorello
- Re: Problems with DHCP Setup Joshua J. Brickel
