search for: run_tc

Hello guys, I past the last days trying to configure my shorewall 4.06 firewall to allow openvpn bridging connection. My scenario is the following: roadwarrior (openvpn client) -------------> Internet ------------> (X.Y.W.Z - eth0) Firewall/Gateway (10.x.x.254 - eth1) --------> Local Lan -------> OpenVPN Server (10.x.x.249 - br0) where 10.x.x.0-254 is my private lan X.Y.Z.W is

...rate 20755bps is measured). Setting the explicit bandwith (ceil=64kbps everywhere) does not work. Playing with burst and cburst did not any change. I''ve tried CBQ but it seems to do the same... :( Please help. Thank you, Bálint #################################### # add root HTB disc run_tc qdisc add dev eth1 root handle 1: htb default 11 r2q 1 # be optimistic about input rates :) run_tc class add dev eth1 parent 1: classid 1:1 htb rate 10mbit # setup classes for the local nodes run_tc class add dev eth1 parent 1:1 classid 1:10 htb rate 5kbps ceil 10mbit prio 2 run_tc class add dev...

...your faq, u have this noted: While I am currently using the HTB version of The Wonder Shaper (I just copied wshaper.htb to /etc/shorewall/tcstart and modified it as shown in the Wondershaper README), I treid this with wondershaper, using Bearing Leaf 1.0 stable i even changed the tc command to run_tc, and tried it in both angles, and i receive the following.. processing /etc/shorewall/tcstart :notfound :notfound :notfound :notfound :notfound :notfound :notfound :notfound :notfound /etc/shorewall/tcstart: 103: Syntax error: word unxpected i just made the changes for the Up/download kbits, renn...

...0.0.0.0/0 all 20 192.168.0.161/32 0.0.0.0/0 tcp 7000:7010 21 0.0.0.0/0 192.168.0.161/32 tcp 7010:7010 Now, shouldnt this mark all packets to / from .161 to our little daemon on ports 7000:7010 with handle 20 and 21? and here is my tcstart run_tc qdisc add dev eth0 root handle 1: htb default 30 run_tc class add dev eth0 parent 1:1 classid 1:10 htb rate 14kbit ceil 38kbit burst 15k prio 1 run_tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 20 fw classid 1:10 run_tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 21 fw cl...

...Control... HFSC: Illegal "umax" HFSC: Illegal "sc" ERROR: Command "tc class add dev eth1 parent 1:1 classid 1:110 hfsc sc umax b dmax 150ms rate 1575kbit ul rate 3150kbit" Failed After some investigation of /var/lib/shorewall/firewall I found the above line to be: run_tc class add dev eth1 parent 1:1 classid 1:110 hfsc sc umax ${eth1_mtu}b dmax 150ms rate 1550kbit ul rate 3100kbit But eth1_mtu was not defined anywhere! Hence it was getting the parmeter "umax b" where it should apparently say "umax 1500b". In the file generated by older version...

...ld be useful to have an option to generate a script of the commands Shorewall is about to issue, instead of issuing the commands directly. This script could then be used for revision, modification, and could also be used on another system. I thought about modifying run_iptables, run_ip, run_arp and run_tc to obtain this feature, but I think an option to /sbin/shorewall would be a cleaner and useful solution. Do anybody think this would be useful too? Thank you Luigi

http://www.shorewall.net/traffic_shaping.htm Page says run_tc qdisc add dev eth0 parent 1:10 pfifo limit 5run_tc qdisc add dev eth0 parent 1:20 pfifo limit 10 Im willing to _bet_ there is a line feed missing in there ;)