From: Sergey Popovich <popovich_sergei@mail.ru>
To: netdev@vger.kernel.org
Subject: Re: Incorrect ARP behavior when multiple/none IPv4 address assigned to interface
Date: Wed, 24 Oct 2012 13:37:36 +0300 [thread overview]
Message-ID: <5087C4F0.4070607@mail.ru> (raw)
In-Reply-To: <alpine.LFD.2.00.1210241106080.1616@ja.ssi.bg>
Julian Anastasov пишет:
> dummy module is usually used as blackhole for
> traffic or to hide addresses from other interfaces with
> some sysctl interface flags.
>
> For example, can it work in this way?:
>
> eth0: addr 10.0.1.1/24
> ip route 10.0.1.2/32 dev eth0 src 10.0.1.1
>
> eth1: addr 10.0.1.1/24
> ip route 10.0.1.3/32 dev eth1 src 10.0.1.1
>
> eth2: addr 10.0.2.1/24
> ip route 10.0.2.2/32 dev eth2 src 10.0.2.1
>
> By this way we have subnet on every device and
> we can prefer local IP from such subnet in inet_select_addr.
> May be arp_ignore=1/2 and arp_announce=1/2 can help here
> to put the needed restrictions, i.e. we should not expose
> addresses from other devices. It should not cause problem
> for proxy_arp because we have more specific /32 routes.
>
Yes, just apply proposed configuration to lab schema.
Everything works as expected with no extra arp_ignore/arp_announce
configuration. Even if I add second primary address 192.168.1.1/24 to
eth2, and introduce pc4 in same broadcast domain as pc3 (eth2).
Well, configuration with 3000 subinterfaces looks worse, but it works
with no extra patches/configuration.
Thank you for your help.
--
SP5474-RIPE
Sergey Popovich
prev parent reply other threads:[~2012-10-24 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 11:28 Incorrect ARP behavior when multiple/none IPv4 address assigned to interface Sergey Popovich
2012-10-24 0:15 ` Julian Anastasov
2012-10-24 7:18 ` Sergey Popovich
2012-10-24 9:06 ` Julian Anastasov
2012-10-24 10:37 ` Sergey Popovich [this message]
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=5087C4F0.4070607@mail.ru \
--to=popovich_sergei@mail.ru \
--cc=netdev@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 NNTP newsgroup(s).