Hy there!
This is not really a bug! This caused by the reduced physdev match capabiliti
of iptables in 2.6.20 (and newer) kernels.
http://www.shorewall.net/3.0/NewBridge.html
I don't know the reason behind this change, but in our point of view, it
may be good if ubuntu can shomehow patch this fe
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Is this symptom still reproducible in 8.10 alpha/beta?
** Changed in: shorewall (Ubuntu)
Status: New => Incomplete
--
shorewall doesn't start: "Couldn't load target `fw2loc'"
https://bugs.launchpad.net/bugs/95592
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- shorewall doesn't start
+ shorewall doesn't start: "Couldn't load target `fw2loc'"
--
shorewall doesn't start: "Couldn't load target `fw2loc'"
https://bugs.launchpad.net/bugs/95592
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
running the above command gives me:
[EMAIL PROTECTED]:~# /sbin/iptables -A OUTPUT -o br0 -m physdev --physdev-out
eth0 -m policy --pol none --dir out -j fw2loc
iptables v1.3.6: Couldn't load target `fw2loc':/lib/iptables/libipt_fw2loc.so:
cannot open shared object file: No such file or directory
