On Mon, Nov 15, 2004 at 01:32:14PM +0100, Hendrik Wiese wrote:
> Hello there,
>
> I hope I do right posting this here. So please don't be angry if I'm
> wrong. I'm kind of newbie.
There is a netfilter-devel@xxxxxxxxxxxxxxxxxxx lists for
iptables/netfilter related questions. But I think netdev is quite ok in
this case, since at this time it is unclear (and I think very unlikely)
to be a netfilter/iptables issue.
> as soon as we want to use iptables to establish one of the modules as a
> router to the outer world (tp network connected via front panel eth
> device) this doesn't work...
_please_ give us more detailed descriptions than "doesn't work".
> correctly as it works for to eth devices. Is there any ability else a
> network device driver must have to work with iptables?
no, as iptables is based on netfilter IPv4 hooks which are embedded into
the IPv4 stack. Between your driver and iptables is the ipv4 stack and
the generic networking core. There is no driver/iptables interface at
all.
--
- Harald Welte <laforge@xxxxxxxxxxxxx> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
signature.asc
Description: Digital signature
|