linux still dying;potential errors

linux still dying;potential errors

[Littlefield, Tyler]

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,

Re: linux still dying;potential errors

[Richard Villa]

That looks like a classic DHCP renewal process.  I don't know why that 
client doesn't maintain the IP address.

----- Original Message ----- 
From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 18, 2007 10:20 PM
Subject: linux still dying;potential errors


> 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,
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: linux still dying;potential errors

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yeah, that looked normal for the most part, though it did look like
the client wasn't immediately picking up the new lease. What I mean
is, it looked like the dhcp server gave out the new lease, but the
client didn't acknowledge getting it, and was still broadcasting a
renewal request.

Greg


On Fri, May 18, 2007 at 10:28:10PM -0500, Richard Villa wrote:
> That looks like a classic DHCP renewal process.  I don't know why that 
> client doesn't maintain the IP address.
> 

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGTnsm7s9z/XlyUyARAqHbAJ9dDQcgd3eV6w5XiMzLInA9tZMPTwCZAXFe
s5GBZHWIt2YN363ifJs2LF8=
=7Mxd
-----END PGP SIGNATURE-----

Re: linux still dying;potential errors

[Cody]

try a mask of 255.255.255.0
----- Original Message ----- 
From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 18, 2007 8:20 PM
Subject: linux still dying;potential errors


> 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,
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: linux still dying;potential errors

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hmmm, not sure how the netmask suggestion fits into all of this. If
his netmask was the problem, he likely wouldn't have had a connection
at all.

Greg



On Fri, May 18, 2007 at 09:25:10PM -0700, Cody wrote:
> try a mask of 255.255.255.0

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGTn2B7s9z/XlyUyARAjU4AJ9emHWWRIckuZMl3CIossa831YkXQCgrsUA
nMfJGo7xoJ6mi8lHXhtFog0=
=lz8O
-----END PGP SIGNATURE-----

Re: linux still dying;potential errors

[Littlefield, Tyler]

that's what its at now.
----- Original Message ----- 
From: "Cody" <churst35@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 18, 2007 10:25 PM
Subject: Re: linux still dying;potential errors


> try a mask of 255.255.255.0
> ----- Original Message ----- 
> From: "Littlefield, Tyler" <compgeek13@gmail.com>
> To: "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
> Sent: Friday, May 18, 2007 8:20 PM
> Subject: linux still dying;potential errors
>
>
> > 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,
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: linux still dying;potential errors

[Cody]

just a guess is all. either way it probably wouldn't have mattered since 
it's still a class c address. There is a certain disagreement somewhere 
between the nic card and the router..unless the ip suddenly changes for 
wherever reason I'd say set the nic card on the linux box to have a static 
address. but either way I've never had a problem with it though it is a pain 
to keep up with when you do have a dynamic ip. try disabling it on the 
router and enabling static ip's on the machines.
----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 18, 2007 9:30 PM
Subject: Re: linux still dying;potential errors


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hmmm, not sure how the netmask suggestion fits into all of this. If
> his netmask was the problem, he likely wouldn't have had a connection
> at all.
>
> Greg
>
>
>
> On Fri, May 18, 2007 at 09:25:10PM -0700, Cody wrote:
>> try a mask of 255.255.255.0
>
> - -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGTn2B7s9z/XlyUyARAjU4AJ9emHWWRIckuZMl3CIossa831YkXQCgrsUA
> nMfJGo7xoJ6mi8lHXhtFog0=
> =lz8O
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: linux still dying;potential errors

[Littlefield, Tyler]

that was my thoughts as well...

----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 18, 2007 10:30 PM
Subject: Re: linux still dying;potential errors


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hmmm, not sure how the netmask suggestion fits into all of this. If
> his netmask was the problem, he likely wouldn't have had a connection
> at all.
> 
> Greg
> 
> 
> 
> On Fri, May 18, 2007 at 09:25:10PM -0700, Cody wrote:
> > try a mask of 255.255.255.0
> 
> - -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
> 
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> 
> iD8DBQFGTn2B7s9z/XlyUyARAjU4AJ9emHWWRIckuZMl3CIossa831YkXQCgrsUA
> nMfJGo7xoJ6mi8lHXhtFog0=
> =lz8O
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: linux still dying;potential errors

[Shawn Keen]

it didn't show that  to be so in that log. it showed
255.255.255.255

----- Original Message ----- 
From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 18, 2007 11:31 PM
Subject: Re: linux still dying;potential errors


> that's what its at now.
> ----- Original Message ----- 
> From: "Cody" <churst35@verizon.net>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Friday, May 18, 2007 10:25 PM
> Subject: Re: linux still dying;potential errors
>
>
>> try a mask of 255.255.255.0
>> ----- Original Message ----- 
>> From: "Littlefield, Tyler" <compgeek13@gmail.com>
>> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
>> Sent: Friday, May 18, 2007 8:20 PM
>> Subject: linux still dying;potential errors
>>
>>
>> > 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,
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@braille.uwo.ca
>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.467 / Virus Database: 269.7.3/809 - Release Date: 5/17/2007 
> 5:18 PM
>
> 

Re: linux still dying;potential errors

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, it seems like we've got some confusion when it comes to netmasks with
standard dhcp query addresses. The log snipit he posted said nothing
at all about the netmask, and no, 255.255.255.255 isn't the netmask
he's using, (never mind the fact it isn't a netmask to begin with, at
least not for a class c address).

Greg



On Fri, May 18, 2007 at 11:40:21PM -0500, Shawn Keen wrote:
> it didn't show that  to be so in that log. it showed
> 255.255.255.255
> 

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGTpPf7s9z/XlyUyARAofQAJ9S0+0PicK2mAdz8d3NxCF3dosXAgCgmHLG
uVbk9JYzDp6AppQODe3s/XM=
=9Z2D
-----END PGP SIGNATURE-----

Re: linux still dying;potential errors

[Richard Villa]

The IP address in question 255.255.255.255 is the broadcast address.

----- Original Message ----- 
From: "Shawn Keen" <dkeen@sbcglobal.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, May 18, 2007 11:40 PM
Subject: Re: linux still dying;potential errors


> it didn't show that  to be so in that log. it showed
> 255.255.255.255
>
> ----- Original Message ----- 
> From: "Littlefield, Tyler" <compgeek13@gmail.com>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Friday, May 18, 2007 11:31 PM
> Subject: Re: linux still dying;potential errors
>
>
>> that's what its at now.
>> ----- Original Message ----- 
>> From: "Cody" <churst35@verizon.net>
>> To: "Speakup is a screen review system for Linux."
>> <speakup@braille.uwo.ca>
>> Sent: Friday, May 18, 2007 10:25 PM
>> Subject: Re: linux still dying;potential errors
>>
>>
>>> try a mask of 255.255.255.0
>>> ----- Original Message ----- 
>>> From: "Littlefield, Tyler" <compgeek13@gmail.com>
>>> To: "Speakup is a screen review system for Linux."
>> <speakup@braille.uwo.ca>
>>> Sent: Friday, May 18, 2007 8:20 PM
>>> Subject: linux still dying;potential errors
>>>
>>>
>>> > 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,
>>> > _______________________________________________
>>> > Speakup mailing list
>>> > Speakup@braille.uwo.ca
>>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>>
>> -- 
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.467 / Virus Database: 269.7.3/809 - Release Date: 5/17/2007
>> 5:18 PM
>>
>>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: linux still dying;potential errors

[Ralph W. Reid]

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@sunset.net  http://personalweb.sunset.net/~rreid
...passing through The City of Internet at the speed of light...
_PI = 4 * ARCTAN (1)

Re: linux still dying;potential errors

[Littlefield, Tyler]

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@sunset.net>
To: "Speakup is a screen review system for Linux." <speakup@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@sunset.net  http://personalweb.sunset.net/~rreid
> ...passing through The City of Internet at the speed of light...
> _PI = 4 * ARCTAN (1)
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: linux still dying;potential errors

[Cody]

do like I said and set static ip's on your linux box and it will never 
change / what router are you using I use a linksys and am currently setting 
up a few ciscos.

----- Original Message ----- 
From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, May 19, 2007 10:53 AM
Subject: Re: linux still dying;potential errors


> 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@sunset.net>
> To: "Speakup is a screen review system for Linux." 
> <speakup@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@sunset.net  http://personalweb.sunset.net/~rreid
>> ...passing through The City of Internet at the speed of light...
>> _PI = 4 * ARCTAN (1)
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: linux still dying;potential errors

[Littlefield, Tyler]

that's the problem. isn't it.
----- Original Message ----- 
From: "Cody" <churst35@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, May 19, 2007 5:55 PM
Subject: Re: linux still dying;potential errors


> do like I said and set static ip's on your linux box and it will never
> change / what router are you using I use a linksys and am currently
setting
> up a few ciscos.
>
> ----- Original Message ----- 
> From: "Littlefield, Tyler" <compgeek13@gmail.com>
> To: "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
> Sent: Saturday, May 19, 2007 10:53 AM
> Subject: Re: linux still dying;potential errors
>
>
> > 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@sunset.net>
> > To: "Speakup is a screen review system for Linux."
> > <speakup@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@sunset.net  http://personalweb.sunset.net/~rreid
> >> ...passing through The City of Internet at the speed of light...
> >> _PI = 4 * ARCTAN (1)
> >>
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@braille.uwo.ca
> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: 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@sunset.net>
> To: "Speakup is a screen review system for Linux." <speakup@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@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@sunset.net  http://personalweb.sunset.net/~rreid
...passing through The City of Internet at the speed of light...
_PI = 4 * ARCTAN (1)