> First of all, thanks to all who responded to my initial post. > This includes Mark, Scott, Matt, Charles, David, Sean, Michael, > and Richard. I've tried pretty much everything that's been > suggested: setting various dhclient parameters, setting HOSTNAME > and HOSTS0, etc. Unfortunately, I'm still having the same problem. > I figured it was time to post a more thorough support request. > > Problem description: After being transitioned off of home.com to > attbi.com, I wasn't able to ping any addresses from my old LRP box. > I upgraded to Dachstein 1.0.2, but that didn't seem to make much > difference. > > If I hook my win2k box directly into the cable modem, things work > fine. It gets assigned address 12.237.7.206, subnet 255.255.240.0, > and default gateway 12.237.0.1. > > The fact that the router gets such a different configuration makes > me suspect its some sort of DHCP problem. But by all appearences, > DHCP works fine. It acquires its addresses from 12.237.0.1, which > happens to be the default gateway for the win2k box AND appears to > be the ONLY address that I can successfully ping from the router.
So using Dachstein, and the alternate (/28) DHCP settings, you CAN ping 12.237.0.1 but nothing else? This is very odd, and would likely indicate a problem on your ISP's end of things... > I've included the following information: > . network diagram > . dmesg output > . ip addr show > . ip route show > . ip neighbor show > . ip -s link show > . /etc/network.conf > . /etc/lrp.conf > . /etc/dhclient.conf Your config looks OK, but the martian messages are odd...or did you ping the network IP (.128) from your firewall? Things to try: Since you're getting much different DHCP data using linux instead of windows, you might try to see if you can change some dhcp settings and get something more similar to your working windows config. First try removing any dhcp client leases (in /var/state/dhcp)...shut down dhclient & restart (svi dhclient stop/start). If that doesn't work, try tricking the DHCP server by giving your external interface the same MAC address as the card in your windows box (just make sure you don't have both interfaces on the same ethernet segment...things would get massively confused). You can do this with the ip command (ip link set eth0 address 00:80:c8:ca:ab:11)...repace the MAC address with the right one, of course, and make sure you've cleared any dhclient leases as well... It would also be interesting to see the output dhclinet generates on startup, which was not captured by your dmesg output, and the contents of your dhcp lease file. Also, in addition to the networking information you provided (ip addr & ip route), the results of the following ping tests (using IP addresses, not hostnames) firewall to default gateway firewall to internet IP Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
