From: "Richard Villa" <richard_villa@sbcglobal.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: linux still dying;potential errors
Date: Fri, 18 May 2007 22:28:10 -0500 [thread overview]
Message-ID: <984F09F1AC6F4B90B7AA13BBC7F0A18A@pringles> (raw)
In-Reply-To: <002001c799c4$9abe21e0$6601a8c0@GRANDMA>
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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Richard Villa [this message]
` Gregory Nowak
` Cody
` Gregory Nowak
` Cody
` Littlefield, Tyler
` Littlefield, Tyler
` Shawn Keen
` Gregory Nowak
` Richard Villa
` Ralph W. Reid
` Littlefield, Tyler
` Cody
` Littlefield, Tyler
` 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=984F09F1AC6F4B90B7AA13BBC7F0A18A@pringles \
--to=richard_villa@sbcglobal.net \
--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).