| 1 |
On Thursday 26 Feb 2015 18:57:44 Walter Dnes wrote: |
| 2 |
> Let's forget about additional routes with different metrics, and try |
| 3 |
> to get the simplest case working, and move forward from there. If I have |
| 4 |
> /etc/conf.d/net as... |
| 5 |
> |
| 6 |
> modules=( "!iproute2" ) <== Delete this for iproute2 usage == |
| 7 |
> config_eth0=" |
| 8 |
> 192.168.123.251/29 broadcast 192.168.123.255 |
| 9 |
> 169.254.1.1/16 broadcast 169.254.255.255" |
| 10 |
> routes_eth0=" |
| 11 |
> default via 192.168.123.254 |
| 12 |
169.254.0.0/16 via 169.254.1.1" <==Add this route for 169.254.0.0/16== |
| 13 |
|
| 14 |
or if your router can route packets for the 169.254.0.0/16 subnet (I doubt it) |
| 15 |
then change it to: |
| 16 |
|
| 17 |
169.254.0.0/16 via 192.168.123.254 |
| 18 |
|
| 19 |
|
| 20 |
> I'm still trying to wrap my brain around how the ADSL router decides |
| 21 |
> whether to look for 169.254.0.0/16 on the ethernet cable to the TV tuner |
| 22 |
> rather than on the phone line going to my ISP, and then the world. |
| 23 |
|
| 24 |
If the router has link-local configured it should be able to communicate with |
| 25 |
other devices in the same 169.254.0.0/16 subnet. However, I doubt that it |
| 26 |
will be NAT-ing packets to this subnet, because it is meant for ad-hoc device- |
| 27 |
to-device connections when there is no DHCP server in the local network. |
| 28 |
|
| 29 |
Have a look at the router's route and arp tables to see what it does on this |
| 30 |
matter. |
| 31 |
|
| 32 |
-- |
| 33 |
Regards, |
| 34 |
Mick |
Archives