Joshua J. Brickel wrote:
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.
<snip>
The present problem is that the initial dhcp connection does not seem
to be properly setup.
Is there anything that actually does not work, or are you just
surprised to get a slightly different configuration?
<snip>
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.
Not a problem.
2) The message "SIOCADDRT: Network is unreachable" can not be good.
Well, it doesn't *look* good, but it might not really indicate a problem.
<snip>
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#
Hmm, no gateway. I'm not sure why that is; if a DHCP server gives a
gateway address then it should normally become the default gateway.
However you can configure dhclient to selectively ignore what the
server tells it.
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
This is the default route which is missing under Linux.
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
This is the loopback route which is not needed under Linux.
172.25.192.0 255.255.224.0 172.25.207.86
172.25.207.86 20
This is the local network route which is present under Linux (though
with a different local address).
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
I think these special routes are not needed under Linux because its
network stack works differently.
Default Gateway: 172.25.224.1
===========================================================================
Persistent Routes:
None
Of which none of the routes match the one put in by linux.
The only important difference from the routes active under Linux is
the existence of the default gateway.
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.
You shouldn't need anything in there.
If anyone has any idea of what I can try next I would be gratefull.
If you do have anything in dhclient.conf other than comments, try
commenting it out and reinitialising the interface (ifdown eth0 && rm
/var/lib/dhcp/dhclient.leases && ifup eth0).
Ben.
II------------------------------------------------------------------------
II AquaNet promises to take care and help its' customers stay
safe II This Mail was Scanned By AquaNet's Anti-Virus Server And
was Found OK! II
http://www.aquanet.co.il
II------------------------------------------------------------------------