From: Andreas Unterkircher <unki@netshadow.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] simple routing query
Date: Thu, 10 Nov 2005 18:42:06 +0000 [thread overview]
Message-ID: <4373947E.1080104@netshadow.at> (raw)
In-Reply-To: <20051110174536.GA10440@tranquility.scriptkitchen.com>
I had such a experience with SuSE on a server with two network
interface. While only one of them was
connected to the lan with a fixed IP, the other was configured by YaST
to get it's IP from a DHCP server.
Cause it can't reach it and timed out, the interface didn't get an IP
address, but suddenly a 169.254.x.x
route appeared. Probably you hit the same thing.
Payal Rathod wrote:
>On Thu, Nov 10, 2005 at 12:50:34PM -0500, Brett Charbeneau wrote:
>
>
>>http://www.cas.ilstu.edu/shac/Knowledge/Spam/iana.htm
>>
>> see the "Autoconfiguration" IP Addresses section.
>>
>>
>
>Yes, I read it, thnaks but I don't understand it.
>| Addresses in the range 169.254.0.0 to 169.254.255.255 are used
>|automatically by some PCs and Macs when they are configured to use IP,
>|do not have a static IP Address assigned, and are unable to obtain an
>|IP address using DHCP.
>|
>|This traffic is intended to be confined to the local network, so the
>|administrator of the local network should look for misconfigured hosts.
>
>What do they mean by this? Is it at address given by error due to
>misconfiguaration.
>
>Payal
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-11-10 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 17:45 [LARTC] simple routing query Payal Rathod
2005-11-10 17:50 ` Brett Charbeneau
2005-11-10 18:33 ` Payal Rathod
2005-11-10 18:36 ` Brett Charbeneau
2005-11-10 18:42 ` Andreas Unterkircher [this message]
2005-11-10 18:47 ` Payal Rathod
2005-11-10 19:13 ` Andreas Unterkircher
2005-11-11 10:21 ` Jandre Olivier
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=4373947E.1080104@netshadow.at \
--to=unki@netshadow.at \
--cc=lartc@vger.kernel.org \
/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