From: "Shawn Keen" <dkeen@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 23:40:21 -0500 [thread overview]
Message-ID: <000c01c799cf$cfeacca0$6401a8c0@laptop> (raw)
In-Reply-To: <001601c799ce$a0dba390$6601a8c0@GRANDMA>
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
>
>
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 [this message]
` 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='000c01c799cf$cfeacca0$6401a8c0@laptop' \
--to=dkeen@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).