I think the .255 address is what the problem is. Somewhere, something is blocking that IP, I'm guessing. I thought those were for broadcasts also. The netmask is 255.255.252.0.
I deleted the lease file, but it still fetched the same IP. The DHCP client belongs to AT&T, the box is my gateway to the outside world. Not too long ago my gateway released my last IP and got this new one. It's worked fine -- I haven't noticed too many timeouts on pages. But now I'm trying to get to a network I know is up and others can get to, so I suspect it's my IP. I'll try the power off cable modem, reboot the gateway method and see what happens... Thanks, Rob > On 20020227.1500, Ben Barrett said ... > > Rob, if you can find the leases file, you should be able to destroy it > and hopefully get a new lease. Alternatively, you might try renewing > the dhcp lease using a variant of your previous network topology: > will different ARP resolution reflect back to the dhcp server? > Anyway, I might be off-base but I thought .255 addresses were > supposed to be reserved for some kind of LAN broadcast use? > I also thought you can request a specific IP from most dhcp > servers, and they will let you claim it, so long as it is > in-range and unused... > > On Wed, 2002-02-27 at 14:34, Rob Hudson wrote: > > Anyone know about dhclient on FreeBSD? > > > > at-home gave me an address ending in .255, and I think it is > > interfering with the willamette.net network (I can't get to it now). > > Is there a way to tell dhclient to get a new IP, and not accept the > > same one? > > > > I can kill dhclient, but when I start it again, it gets the same IP > > back. > > > > Thanks, > > Rob > > -- > -- > Ben Barrett > Software & Systems Engineer > counterclaim > Phone: 541.484.9235 > Fax: 541.484.9193 > > -- Rob <rob_at_euglug_dot_net> my @euglugCode = qw(v+++ e--- eug+ bsd+++ gnu+ S+++);
