From: Andrew Ross <aross@westnet.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Promisc routing
Date: Sat, 28 Aug 2004 00:11:02 +0000 [thread overview]
Message-ID: <1093651862.8457.10.camel@localhost> (raw)
In-Reply-To: <001001c48c6c$a65918b0$030aa8c0@t>
On Sat, 2004-08-28 at 05:32, Roy wrote:
> I want to set interface to promisc mode and do all routing with iptables.
You don't need to set an interface in promisc mode to do routing. You
need the clients to have you configured as a router (easily acheived via
dhcp).
Routing isn't actually done with netfilter, although the routed packets
are available for filtering.
> Is it somehow possible?
Is it possible to use netfilter to make a routing decision? I suppose it
_might_ be (using the MARK target and iproute2), but it would be overly
convulted, esp compared to doing it "the normal way".
> I see now kernel do not pass everything to ipables.
I think you'll find that netfilter _does_ see all packets it's supposed
to see - it's just a matter of what chains they pass through.
Routed packets will pass through the FORWARD chains. Of course, this
won't happen unless you have configured your machine as a router, and
you have clients actually using it as a router (see above).
> Basicaly I want to ignore ethernet addess and use only ip for routing.
Um, that's what routing is (at least, in my understanding). You're
talking about a Layer 3 router, which makes routing decisions based on
IP addreses/subnets.
Cheers
Andrew
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-08-28 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 19:32 [LARTC] Promisc routing Roy
2004-08-27 20:01 ` Raúl Alexis Betancort Santana
2004-08-28 0:11 ` Andrew Ross [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=1093651862.8457.10.camel@localhost \
--to=aross@westnet.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.