Question: USWest DSL
Mike Cantrell
mikec@autodispatch.com
Mon, 7 Aug 2000 13:13:03 -0700
----- Original Message -----
From: "Julian M Catchen" <julian@catchen.org>
To: <plug-discuss@lists.PLUG.phoenix.az.us>
Sent: Sunday, August 06, 2000 10:17 PM
Subject: Question: USWest DSL
> Hello Everyone-
>
> I recently got the ADSL service from USWest. I am running it through a
Cisco
> 675 router/modem and have it up and running in SuSE linux with Dhclient.
>
> Although its working, I am not quite sure why it is. I was hoping someone
on
> the list could shed some light on the subject of how this works.
>
> <snip>
>
> As you can see, it lists my IP as a dummy address (10.0.0.2). When I do a
> traceroute to any other machine I get output like this:
>
> traceroute to 128.118.25.3 (128.118.25.3), 30 hops max, 40 byte
packets
> 1 10.0.0.1 (10.0.0.1) 1 ms 1 ms 1 ms
> 2 * * *
> 3 * * *
> ...
>
> It never finds the machine (even though I can get to it with ping or
through
> the web). So, what is my IP address? How am I connected to the network?
It has to do w/ how the router handles NAT and imcp packets. I'm sure
there's a way to play w/ your NAT rules to get traceroute to work correctly.
>
> Finally, it appears that dhclient is trying to renew its lease every 80
> seconds. Although in the dhclient config file I have it set to renew
every 24
> hours (84600 seconds.) I know this because my /var/log/messages file is
filled
> with this:
>
> Aug 6 22:13:46 topeka dhclient: DHCPREQUEST on eth0 to 10.0.0.1 port
67
> Aug 6 22:13:46 topeka dhclient: DHCPACK from 10.0.0.1
> Aug 6 22:13:46 topeka dhclient: bound to 10.0.0.2 -- renewal in 80
seconds.
>
> Does anyone know why this is happening.
>
> Thanks in advance...
>
> julian
>
Hmm... is there any reason you want to run your clients DHCP? It's fine if
you have a large network w/ lots of clients and DNS but if it's just your
home machine, I'd just set you network info statically. You'll end up w/
less head aches in the long run IMHO.
Regards,
Mike Cantrell