linux still dying;potential errors

[Ralph W. Reid]

I am not sure whether disabling dhcp would help.  If you do, then I
would expect that your computer would need to be assigned a static IP
address (perhaps by its own settings).  On Slackware systems, static
IP addresses can be assigned in /etc/rc.d/rc.inet1.conf .

You might be able to increase the lease time from your computer with
some dhcpcd command line options or on your router using whatever
settings that device has.  I believe an option is available for dhcpcd
to request an IP address or request that the lease for the previous IP
address be renewed without assigning a new IP--you will have to look
it up for your particular router and Linux distribution to be sure to
get the settings in the right place(s).  Posting more details about
your system here or looking up the man page for dhcpcd might help
more.

HTH, and have a great day.



On Sat, May 19, 2007 at 11:53:23AM -0600, Littlefield, Tyler wrote:
> hmm. it shouldn't be doing it that much.
> Would it help if I disabled dhcp on the router?
> Thanks,
> ----- Original Message ----- 
> From: "Ralph W. Reid" <rreid at sunset.net>
> To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca>
> Sent: Saturday, May 19, 2007 10:55 AM
> Subject: Re: linux still dying;potential errors
> 
> 
> > This sample from your log looks like your computer reestablishing a
> > new IP address with a router after a disconnect of some sort or after
> > the previously assigned IP address expired.  Given the number of
> > seconds assigned, the IP addresses appear to expire every 12 hours,
> > and then a new one needs to be assigned.  If this type of stuff shows
> > up in your log more frequently than about once every twelve hours,
> > then something is causing the connection to be dropped--what that
> > something might be is not clear from this sample of log info.
> >
> > HTH, and have a great day.
> >
> > On Fri, May 18, 2007 at 09:20:08PM -0600, Littlefield, Tyler wrote:
> > > Hello list,
> > > I'm still getting a dead network at random.
> > > Here is what came up in syslog about the time the connection died:
> > > May 18 15:11:43 tysdomain dhclient: DHCPREQUEST on eth0 to 192.168.1.1
> port 67
> > > May 18 15:11:43 tysdomain dhclient: DHCPNAK from 192.168.1.1
> > > May 18 15:11:43 tysdomain dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 7
> > > May 18 15:11:44 tysdomain dhclient: DHCPOFFER from 192.168.1.1 graphic
> 581 May 18 15:11:44 tysdomain dhclient: DHCPREQUEST on eth0 to
> 255.255.255.255 port
> > > 67
> > > May 18 15:11:44 tysdomain dhclient: DHCPACK from 192.168.1.1
> > > May 18 15:11:44 tysdomain dhclient: bound to 192.168.1.101 -- renewal in
> 43200 seconds.
> > > Does this tell anyone anything?
> > > Thanks,
> >
> > -- 
> > Ralph.  N6BNO.  Wisdom comes from central processing, not from I/O.
> > rreid at sunset.net  http://personalweb.sunset.net/~rreid
> > ...passing through The City of Internet at the speed of light...
> > _PI = 4 * ARCTAN (1)

-- 
Ralph.  N6BNO.  Wisdom comes from central processing, not from I/O.
rreid at sunset.net  http://personalweb.sunset.net/~rreid
...passing through The City of Internet at the speed of light...
_PI = 4 * ARCTAN (1)