From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple network cards on same subnet problem
Date: Tue, 03 May 2005 05:09:13 +0000 [thread overview]
Message-ID: <42770779.5050703@riverviewtech.net> (raw)
In-Reply-To: <427696B4.6030201@vulnscan.org>
> Did I miss a setting? A kernel compile option? Or is there a problem
> with arp_filter in 2.4.*? I hope I'm missing something obvious here ;).
The reason (as I know it) that this is happening is the way that Linux (for sure) and most unicies in general (as far as I know) will receive the traffic that comes in to the NICs on what ever physical NIC that it may be connected to. The problem is the reply. Unix will by default choose the first route that it has available to a subnet as it's route out to the world. If you updated your routing table and put eth2, eth1, and then eth0 all the traffic would go out eth2. In short the solution that Joe gave you is probably one that will work. I would possibly end up looking at setting up specific routing tables for each NIC which would have different routes, namely source IPs and interfaces, to the network. But the solution that Joe came up with will work just as well. I'm not familiar enough to know which one is better though.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-05-03 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 21:08 [LARTC] Multiple network cards on same subnet problem (arp_filter=1) Bram Matthys (Syzop)
2005-05-02 21:18 ` [LARTC] Multiple network cards on same subnet problem Joe Nuts
2005-05-02 21:42 ` Bram Matthys (Syzop)
2005-05-03 5:09 ` Taylor, Grant [this message]
2005-05-19 15:17 ` [LARTC] Multiple network cards on same subnet problem (arp_filter=1) Simon Haynes
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=42770779.5050703@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@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