From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [SOLVED] What happened to my 2nd eth0?
Date: Fri, 27 Feb 2015 06:28:55 +0000 [thread overview]
Message-ID: <201502270629.12085.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20150226185744.GA5936@waltdnes.org>
[-- Attachment #1: Type: Text/Plain, Size: 1321 bytes --]
On Thursday 26 Feb 2015 18:57:44 Walter Dnes wrote:
> Let's forget about additional routes with different metrics, and try
> to get the simplest case working, and move forward from there. If I have
> /etc/conf.d/net as...
>
> modules=( "!iproute2" ) <== Delete this for iproute2 usage ==
> config_eth0="
> 192.168.123.251/29 broadcast 192.168.123.255
> 169.254.1.1/16 broadcast 169.254.255.255"
> routes_eth0="
> default via 192.168.123.254
169.254.0.0/16 via 169.254.1.1" <==Add this route for 169.254.0.0/16==
or if your router can route packets for the 169.254.0.0/16 subnet (I doubt it)
then change it to:
169.254.0.0/16 via 192.168.123.254
> I'm still trying to wrap my brain around how the ADSL router decides
> whether to look for 169.254.0.0/16 on the ethernet cable to the TV tuner
> rather than on the phone line going to my ISP, and then the world.
If the router has link-local configured it should be able to communicate with
other devices in the same 169.254.0.0/16 subnet. However, I doubt that it
will be NAT-ing packets to this subnet, because it is meant for ad-hoc device-
to-device connections when there is no DHCP server in the local network.
Have a look at the router's route and arp tables to see what it does on this
matter.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-27 6:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 4:52 [gentoo-user] What happened to my 2nd eth0? Walter Dnes
2015-02-22 9:01 ` Mick
2015-02-23 8:39 ` [gentoo-user] Re: [SOLVED] " Walter Dnes
2015-02-24 6:43 ` Mick
2015-02-24 22:07 ` Walter Dnes
2015-02-24 22:08 ` Tom H
2015-02-26 6:26 ` Walter Dnes
2015-02-26 14:46 ` Tom H
2015-02-26 18:57 ` Walter Dnes
2015-02-26 22:59 ` Tom H
2015-02-27 4:27 ` Walter Dnes
2015-03-01 3:22 ` [gentoo-user] Why my wierd ifconfig setup won't work in iproute2... ever Walter Dnes
2015-03-01 9:12 ` Mick
2015-03-01 9:49 ` Walter Dnes
2015-03-01 11:30 ` Walter Dnes
2015-03-01 16:36 ` Daniel Frey
2015-03-02 9:30 ` Walter Dnes
2015-03-02 0:33 ` Stroller
2015-03-02 6:13 ` Mick
2015-03-02 6:52 ` [gentoo-user] DHCP is a "hidden feature" / "easter egg" Walter Dnes
2015-02-27 6:28 ` Mick [this message]
2015-02-28 6:55 ` [gentoo-user] Re: [SOLVED] What happened to my 2nd eth0? Walter Dnes
2015-02-22 13:31 ` [gentoo-user] " Tom H
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=201502270629.12085.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.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