From: Oleg <lego12239@yandex.ru>
To: linux-admin@vger.kernel.org
Subject: Re: Policy routing problem
Date: Wed, 24 Oct 2012 17:40:17 +0400 [thread overview]
Message-ID: <20121024134017.GA23202@localhost> (raw)
In-Reply-To: <36513.129.217.4.64.1351005255.squirrel@postamt.cs.uni-dortmund.de>
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.
next prev parent reply other threads:[~2012-10-24 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 15:14 Policy routing problem Christoph Pleger
2012-10-24 13:40 ` Oleg [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-25 12:57 Christoph Pleger
2012-10-25 9:25 Christoph Pleger
2012-10-25 10:38 ` Giles Coochey
2012-10-25 9:23 Christoph Pleger
2012-10-23 11:05 Christoph Pleger
2012-10-23 11:27 ` Oleg
2012-10-23 13:23 ` Christoph Pleger
2012-10-23 14:47 ` Oleg
2012-10-23 12:16 ` Jimmy Thrasibule
2012-10-23 14:14 ` Christoph Pleger
2012-10-24 14:27 ` Giles Coochey
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=20121024134017.GA23202@localhost \
--to=lego12239@yandex.ru \
--cc=linux-admin@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).