Re: Problem with new --physdev-out style

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Volker Sauer a écrit :

with recent kernels, I have this problem:

kernel: physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.

What does "non-bridged" in this context mean??

It means packets leaving the IP stack, I guess you could say "routed" as opposed to "bridged". A packet can traverse iptables chains either when it is routed or when it is bridged. At the time a routed packet traverses the iptables chains, the "bridging decision" (i.e. chosing the output port when the output interface is a bridge) has not been made yet, so the output port is unknown and --physdev-out is irrelevant.
-
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux