From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: 169.254 subnet
Date: Tue, 15 May 2012 18:48:02 -0400 [thread overview]
Message-ID: <20120515224802.GJ14763@denix.org> (raw)
In-Reply-To: <CAJfOToUiw6yqaY8ski5XHXja1c_PNeNTO-MDJjVZhZb308WahA@mail.gmail.com>
On Tue, May 15, 2012 at 03:34:56PM -0700, John Tobias wrote:
> Hello All,
>
> My board has a eth0 and wireless interfaces. I manually executed the
> following commands to configured my network interfaces:
>
> 1. ifconfig eth0 192.168.3.139 netmask 255.255.255.0 up
> 2. ifconfig wlan0:1 inet 169.254.6.199 netmask 255.255.0.0 broadcast
> 169.254.255.255 up
>
>
> My Routing table:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.3.0 * 255.255.255.0 U 0 0 0 eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0 ra0
>
>
> My other machine is in 192.168.3.x subnet and I am able to ping the
> 192.168.3.139. But, the problem is I can ping the 169.254.6.199 too.
>
> Is there any special on 169.254 because by using the said subnet it seems
> the two interfaces has a cross over routing?.
http://en.wikipedia.org/wiki/Link-local_address
--
Denys
prev parent reply other threads:[~2012-05-15 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 22:34 169.254 subnet John Tobias
2012-05-15 22:48 ` Denys Dmytriyenko [this message]
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=20120515224802.GJ14763@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.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