That didn't work either. I wonder if its my kernel
version. I'm running:
Kernel: 2.4.20-6
patch: ebtables-brnf-3_vs_2.4.21.diff (applied 3/16)
Latest POM (12/03: applied 3/22)
IPTables: 1.2.9
EBTables: 2.0.6
>From the docs, the br-nf code is required for iptables
to see the bridge traffic. I'm wondering if the order
in which I applied the patches matters. I'll go take a
look at that, but if you folks have any hints I'd much
appreciate it!
Merci beaucoup,
S C
--- Cedric Blancher <blancher@xxxxxxxxxxxxxxxxxx>
wrote:
> Le mar 23/03/2004 à 22:16, Sandy C a écrit :
> > iptables -A INPUT -m physdev --physdev-in eth1 -p
> tcp
> > --destination-port 2049 -j LOG
> [...]
> > iptables -A INPUT -m physdev --physdev-in eth2 -p
> tcp
> > --source-port 2049 -j LOG
> [...]
> > I must be missing something though because I get
> > nothing in my logs.
> [...]
> > what could I be doing wrong?
>
> Bridged traffic goes through FORWARD chain, for it's
> not destined to
> your box.
>
>
> --
> http://www.netexit.com/~sid/
> PGP KeyID: 157E98EE FingerPrint:
> FA62226DA9E72FA8AECAA240008B480E157E98EE
> >> Hi! I'm your friendly neighbourhood signature
> virus.
> >> Copy me to your signature file and help me
> spread!
>
__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
