Re: Policy routing problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 23, 2012 at 05:14:15PM +0200, Christoph Pleger wrote:
> > Are you have real tagged vlan interfaces or by vlan you mean an interface
> > aliases (where multiple IP exists on one interface)?
> 
> I have real VLAN interfaces, but one of these interfaces has two IPs
> (there are two Vservers in that subnet).

  For real vlans all should be fine without a special configuration. For
example, i have a dhcp server with many tagged vlans:

~# ip a
....
4: vlan23@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 18:03:73:73:03:14 brd ff:ff:ff:ff:ff:ff
    inet 10.16.23.2/24 scope global vlan23
5: vlan24@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 18:03:73:73:03:14 brd ff:ff:ff:ff:ff:ff
    inet 10.16.24.2/24 scope global vlan24
6: vlan25@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 18:03:73:73:03:14 brd ff:ff:ff:ff:ff:ff
    inet 10.16.25.2/24 scope global vlan25
....
~# ip -d link
....
4: vlan23@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 18:03:73:73:03:14 brd ff:ff:ff:ff:ff:ff
    vlan id 102 <REORDER_HDR> 
4: vlan24@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 18:03:73:73:03:14 brd ff:ff:ff:ff:ff:ff
    vlan id 103 <REORDER_HDR> 
4: vlan25@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT 
    link/ether 18:03:73:73:03:14 brd ff:ff:ff:ff:ff:ff
    vlan id 104 <REORDER_HDR> 
....
~# ip rou
....
10.16.23.0/24 dev vlan23  proto kernel  scope link  src 10.16.23.2
10.16.24.0/24 dev vlan24  proto kernel  scope link  src 10.16.24.2
10.16.25.0/24 dev vlan25  proto kernel  scope link  src 10.16.25.2
....

Thus, all routing related to these interfaces should work fine. If
you have a multiple IP on a single interface, all routing must be
fine in this case too, because you have device routes like above ones(for 
vlan23, vlan24, vlan25). If you create separate routing tables you must
duplicate to it the same device routes as you have in main for these
interfaces or/and play with src option.
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Newbie]     [Audio]     [Hams]     [Kernel Newbies]     [Util Linux NG]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Device Drivers]     [Samba]     [Video 4 Linux]     [Git]     [Fedora Users]

  Powered by Linux