Ismael Milach da Silveira wrote:
> ok, there it is...
>
> shorewall version - 3.0.1-1
>
> the hosts involved in the connection:
> from: 192.168.200.1
> to: 201.3.160.245
>
> I've made some changes but with the same result I've previously reported.
>
> dump is attached.
>
>From the dump:
Mangle Table
...
Chain tcfor (1 references)
pkts bytes target prot opt in out source destination
0 0 MARK all -- * * 192.168.200.1 0.0.0.0/0
MARK set 0x1 <===================
3 247 MARK all -- * * 192.168.200.10 0.0.0.0/0
MARK set 0x2
Chain tcout (1 references)
pkts bytes target prot opt in out source destination
Chain tcpost (1 references)
pkts bytes target prot opt in out source destination
0 0 CLASSIFY all -- * eth0 0.0.0.0/0 0.0.0.0/0
MARK match 0x1 CLASSIFY set 1:11
3 247 CLASSIFY all -- * eth0 0.0.0.0/0 0.0.0.0/0
MARK match 0x2 CLASSIFY set 1:12
No traffic with source IP address 192.168.200.1 was forwarded by the
firewall during the time covered by this dump as evidenced by the
zeros in the 'pkts' column for the rule for that source address.
So no traffic was sent to the 1:11 TC class (Regrettably, you are
running an old version of Shorewall that does not display traffic
shaping information in the dump).
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ [EMAIL PROTECTED]
PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
