| 1 |
On Monday 23 Feb 2015 08:39:42 Walter Dnes wrote: |
| 2 |
|
| 3 |
> Looks like it's time to play around with the "ip" command and try to |
| 4 |
> duplicate my current setup. Does anyone have a multi-route setup |
| 5 |
> similar to mine configured with iproute2? The net.example file says |
| 6 |
> |
| 7 |
> # If you need more than one address, you can use something like this |
| 8 |
> # NOTE: ifconfig creates an aliased device for each extra IPv4 address |
| 9 |
> # (eth0:1, eth0:2, etc) |
| 10 |
> # iproute2 does not do this as there is no need to |
| 11 |
> # WARNING: You cannot mix multiple addresses on a line with other |
| 12 |
> parameters! #config_eth0="192.168.0.2/24 192.168.0.3/24 192.168.0.4/24" |
| 13 |
> # However, that only works with CIDR addresses, so you can't use |
| 14 |
> # netmask. |
| 15 |
> |
| 16 |
> What exactly do they mean by... |
| 17 |
> "iproute2 does not do this as there is no need to" |
| 18 |
|
| 19 |
There is no need to create virtual interfaces like eth0:1 to be able to have |
| 20 |
secondary IP addresses. The ip command adds them to the same eth0 interface. |
| 21 |
|
| 22 |
When I use VPN I can see that my interface has a secondary LAN address created |
| 23 |
by VPN, but it does not have an additional virtual NIC. |
| 24 |
|
| 25 |
The only thing is that if my primary IP address goes down temporarily, the |
| 26 |
secondary address becomes primary and stays there. I need to look at the VPN |
| 27 |
configuration to see how to define the VPN LAN as a secondary subnet, but this |
| 28 |
is not related to your question. |
| 29 |
|
| 30 |
PS. Did you look at setting your desired subnet rather than a local-link |
| 31 |
auto-configured address at your HDHomerun device? |
| 32 |
|
| 33 |
-- |
| 34 |
Regards, |
| 35 |
Mick |
Archives