Quote:
Originally Posted by Lazydog You have a default policy for INPUT and OUTPUT but none for FORWARD.
You have your forwards dropping to a sub chain and then returning.
What is IPTABLES doing with them once they are returned?
Instead of RETURN try replacing with ACCEPT? |
Hi Lazydog, thanks for trying to help me out!
First of all: I've added a default policy for FORWARD like this:
PHP Code:
iptables -P FORWARD ACCEPT
I tried changing the sub-chains of FORWARD (accounting-in and accounting-out) with ACCEPT instead of RETURN, but cannot see any difference. Like this:
PHP Code:
iptables -A accounting-out -s 192.168.0.101 -m mac --mac-source 00:19:B9:52:46:4A -j ACCEPT
iptables -A accounting-in -d 192.168.0.101 -j ACCEPT
At the moment the behaviour looks a bit like this: all html-traffic looks to be accounted for when doing 'iptables -L -vxn'. When firing up Youtube and start to viewing a movie, that isn't accounted for. BUT when I look at the Squid cache (parsed by LightSquid), all traffic which has been generated by the clients, looks OK. So basically, the amount of bytes isn't correct when doing 'iptables -L -vxn', which I parse to feed the database.
Do you have other thoughts?
Thx