From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: linux still dying;potential errors
Date: Sat, 19 May 2007 18:17:10 -0600 [thread overview]
Message-ID: <002901c79a78$25a594b0$6501a8c0@GRANDMA> (raw)
In-Reply-To: <004101c79a71$aba90030$6901a8c0@winxp>
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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Richard Villa
` Gregory Nowak
` Cody
` Gregory Nowak
` Cody
` Littlefield, Tyler
` Littlefield, Tyler
` Shawn Keen
` Gregory Nowak
` Richard Villa
` Ralph W. Reid
` Littlefield, Tyler
` Cody
` Littlefield, Tyler [this message]
` Ralph W. Reid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002901c79a78$25a594b0$6501a8c0@GRANDMA' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).