From: Roberto Nibali <ratz@drugphish.ch>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: hidden interface (ARP) 2.4.20
Date: Tue, 10 Dec 2002 11:40:53 +0100 [thread overview]
Message-ID: <3DF5C4B5.3030205@drugphish.ch> (raw)
In-Reply-To: Pine.LNX.3.96.1021209200239.9066D-100000@gatekeeper.tmr.com
Hi,
Maybe I should first note that I am not against the hidden patch at all,
I just accepted that it won't go in. I use it on an almost daily basis.
> In spite of vast resistance from some developers, it is highly desirable
> on some systems to force a packet with a given source IP out an interface
> which has that IP assigned. With this capability it is possible to make a
Yes, source address selection based on different rules and routing
tables. What does it have to do with the hidden patch?
> single machine with multiple NICs behave like two machines with individual
> NICs. This also solves ARP issues, although it's a much more general
> thing.
Yes.
> Think development, think debug, think UML virtual machines, or a machine
> with multiple boundary routers which are addressed to separate NICs. The
Ok, I've quite a few boxes running that way.
> usual proxy_arp fix doesn't really address these cases. If I have multiple
> default routes, the router on which the packet arrived is likely to be on
> the route with the fewest hops, randomly using another route doesn't help.
??? Depends how you use those multiple default routes. If you do nexthop
routing you do sort of RR balancing on preferred routes. If you do
source address selection routing based on rules you have fixed default
routes which will not match because of the fewest hops but because of
the rule. I am a bit confused as to what you're trying to tell me.
> Source routing takes too much overhead for lots of connections, and as I
Either we have a different view of source routing or I have to ask you
why you think there is too much overhead with source routing.
> recall is limited to 256 rules. I'm not sure the hidden interface patch
> really does this, although I just looked quickly.
The hidden patch doesn't do source routing and the limit of available
source routes is 254 but not because of the rules (you can have 2**16
rule entries) but because of the amount of routing tables which is 256
[0..255] minus local table minus main table which equals to 254 tables.
> Patches like the hidden interface will continue as long as there are
> useful things people want to do with Linux and can't. It's one of many in
Yes, that's the nice thing about patches, isn't it :).
> the networking area. I don't expect them to be adopted in the main kernel,
> but as long as they're easier than making multiple configs, particularly
> at runtime, they will be around.
Yes, definitely. And I think noone has said anything against that.
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2002-12-10 10:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 20:53 hidden interface (ARP) 2.4.20 Bingner Sam J Contractor PACAF CSS/SCHE
2002-12-05 21:42 ` David S. Miller
2002-12-05 22:03 ` Phil Oester
2002-12-05 22:50 ` Roberto Nibali
2002-12-05 23:48 ` Phil Oester
2002-12-05 23:59 ` Roberto Nibali
2002-12-06 6:01 ` Willy Tarreau
2002-12-06 17:52 ` Stephan von Krawczynski
2002-12-07 23:30 ` Roberto Nibali
2002-12-08 16:03 ` Stephan von Krawczynski
2002-12-08 17:01 ` Willy Tarreau
2002-12-09 11:08 ` Stephan von Krawczynski
2002-12-10 9:42 ` Gilad Ben-Yossef
2002-12-10 10:40 ` Roberto Nibali
2002-12-10 13:09 ` hidden interface (ARP) 2.4.20 / network performance Stephan von Krawczynski
2002-12-10 18:11 ` Roberto Nibali
2002-12-10 23:29 ` Willy TARREAU
2002-12-10 1:22 ` hidden interface (ARP) 2.4.20 Bill Davidsen
2002-12-10 10:40 ` Roberto Nibali [this message]
2002-12-10 14:47 ` Bill Davidsen
2002-12-10 18:15 ` Roberto Nibali
2002-12-11 16:15 ` Bill Davidsen
2002-12-12 1:33 ` Bernd Eckenfels
2002-12-05 22:18 ` Martin Josefsson
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 23:57 Bingner Sam J Contractor PACAF CSS/SCHE
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=3DF5C4B5.3030205@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=davidsen@tmr.com \
--cc=linux-kernel@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