Re: [LARTC] need bandwidth manager
> i want to install and configure bandwidth manager > using Rednat Linux server, i saw the codes to use from > website but the problem is how to apply the code, will > i be entering the code one after the other at shell > prompt or put it in a notepad or how can I use the > codes? You can do either, but I suggest you put them in a bash script, which means that you will be able to run them again more easily. Make sure you start your script with '#!/bin/bash' and make it executable (chmod +x scriptname). Andy Beverley ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] bypassing qdisc for some traffic
> Problem: I don't want to limit traffic from eth1 to > eth2. Is there a clean way to bypass the qdisc for > certain kind of traffic (all traffic from eth1)? You can create a 100mbit root class 1: rate 100mbit default 11, containing two subclasses: 1:10 rate 2mbit and 1:11 rate 98mbit ceil 100mbit. Use iptables to mark all traffic coming from eth0 to go to 1:10 ... Daniel ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
[LARTC] bypassing qdisc for some traffic
Hello everybody. I would like to enable QoS on the internal firewall NIC (eth2) to prevent bandwidth saturation from ftp downloads (for example). This is my firewall schema. ___ private network (100bit/s FD) / / /\ | / //\\ |/ || |eth2\\ | \\traffic flow from dmz +-+-+\\to private network | | || (from eth1 to eth2) | linux | || | router | | & +--eth1--DMZ (100bit/s FD) | Squid | | | +-+-+ | |eth0 (HDSL 2mbit/s) | ++ | ISP | | router | || ++ Problem: I don't want to limit traffic from eth1 to eth2. Is there a clean way to bypass the qdisc for certain kind of traffic (all traffic from eth1)? ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] netmask 255.255.255.255 vs ip route add via ... (bug?)
On Wednesday Nov 15, 2006 around 8:04am, Martin A. Brown wrote, ... : # ip route add onlink default via 192.168.1.17 dev $DEV : ? : : Because from the point of view of the kernel, 192.168.1.17 is : unreachable, it must know the interface. Absolutely! Thank you for the correction of my ommission. Is there a reason that 'onlink' is not the default behaviour when the device is specified? Would onlink add some information that is missing? e.g. ip route add 12.0.0.0/8 via 5.5.5.5 dev eth0 should mean that 5.5.5.5 is directly connected to eth0 (rightly or wrongly). &:-) -- Overflow in kitchen sink. Do you want to report this error? ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] netmask 255.255.255.255 vs ip route add via ... (bug?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexandru, : > # ip route add onlink default via 192.168.1.17 : > : shouldn't be : : # ip route add onlink default via 192.168.1.17 dev $DEV : ? : : Because from the point of view of the kernel, 192.168.1.17 is : unreachable, it must know the interface. Absolutely! Thank you for the correction of my ommission. - -Martin - -- Martin A. Brown http://linux-ip.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: pgf-0.72 (http://linux-ip.net/sw/pine-gpg-filter/) iD8DBQFFWx5ZHEoZD1iZ+YcRAizdAKCM9yVTH40l60mbxFx05ftapB9bPwCg4jKh AGbZhbm15DCRTrtwnBtAlpk= =yAvc -END PGP SIGNATURE- ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] Shaping incoming VoIP traffic fails
On Wednesday 15 November 2006 12:07, Daniel Musketa wrote: > Could I setup HTB better than below? Should I reduce eth1's queue length > (now 1000)? If yes, how? The txqueuelen can be changed by ip link set eth1 txqlen I tried values of 100 and 3 but can't hear an improvement. I can watch traffic coming in on ppp0 with `iftop` and it never exeeds 900kbit. Why could a 2000kbit headroom be not enough for clean receiving of 80kbit VoIP data? Daniel ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] netmask 255.255.255.255 vs ip route add via ... (bug?)
Martin A. Brown wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings Andrew McGill, : I want to use the netmask 255.255.255.255 to insulate (not quite : isolate) machines on a shared subnet from each other. This works : just fine on win XP, but Linux iproute will not acccept the : gateway address in one step -- neither on the command line nor : via DHCP: Try using the onlink nexthop flag for your route: # ip route add onlink default via 192.168.1.17 shouldn't be # ip route add onlink default via 192.168.1.17 dev $DEV ? Because from the point of view of the kernel, 192.168.1.17 is unreachable, it must know the interface. This marks the route for entry even though the local routing table may not have a route to the nexthop destination. In your case, this is a valid parameter, and should prevent the need for you to add the host route only to remove it. : So why did we need that host route? You need the host route to the destination as a simple sanity check. - From the perspective of the kernel, there's no route to 192.168.1.17 if the IP bound to your interface is a /32. When you add the route, the sanity check succeeds. Essentially, you are suppressing this sanity check by using the onlink parameter, which says "Yes, I know there's no route to IP 192.168.1.17 out this interface, but I know the IP is there on this link layer anyway, so set the route anyway and stop griping."* Good luck, - -Martin * RTNETLINK answers: Network is unreachable - -- Martin A. Brown http://linux-ip.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: pgf-0.72 (http://linux-ip.net/sw/pine-gpg-filter/) iD8DBQFFWnH+HEoZD1iZ+YcRAsu2AKDixJF7A0LMClN8snQVq1zk9DV4dQCeIW7R HMtOMud8Kt5yQLskMK7HwDY= =PVyl -END PGP SIGNATURE- ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
[LARTC] Shaping incoming VoIP traffic fails
Hello, I'm trying to get lossless VoIP traffic over my 3000k/500k ADSL line. Shaping outgoing traffic is no problem: I set total ceil for outgiong device (ppp0) to 450kbit and put VoIP into highest prio class. Even during full upload the voice is clean on the other end. Now I tried to get the same result for incoming data. I attached HTB to eth1 where the incoming voip traffic is forwarded to. But even when I set the ceiling for other traffic as low as 800kbit there are drop outs in incoming voice while "full" downloading. Could I setup HTB better than below? Should I reduce eth1's queue length (now 1000)? If yes, how? Thanks. Daniel 8< INT=eth1 # creating root and root class tc qdisc add dev $INT root handle 1: htb default 10 tc class add dev $INT parent 1: classid 1:1 htb rate 1000mbit prio 0 # class for not forwarded traffic (and sfq leaf) tc class add dev $INT parent 1:1 classid 1:10 htb \ rate 997mbit ceil 1000mbit prio 1 tc qdisc add dev $INT parent 1:10 handle 10: sfq perturb 10 # class for forwarded traffic tc class add dev $INT parent 1:1 classid 1:11 htb \ rate 2500kbit ceil 2500kbit prio 0 # class for highest prio VOIP (and sfq leaf) tc class add dev $INT parent 1:11 classid 1:110 htb \ rate 200kbit ceil 2500kbit prio 0 tc qdisc add dev $INT parent 1:110 handle 110: sfq perturb 10 # class for higher prio traffic (and sfq leaf) tc class add dev $INT parent 1:11 classid 1:111 \ htb rate 1200kbit ceil 1500kbit prio 1 tc qdisc add dev $INT parent 1:111 handle 111: sfq perturb 10 # class for low prio traffic (and sfq leaf) tc class add dev $INT parent 1:11 classid 1:112 htb \ rate 100kbit ceil 800kbit prio 2 tc qdisc add dev $INT parent 1:112 handle 112: sfq perturb 10 # filters for forwarded traffic tc filter add dev $INT parent 1: prio 0 protocol ip handle 110 fw flowid 1:110 tc filter add dev $INT parent 1: prio 1 protocol ip handle 111 fw flowid 1:111 tc filter add dev $INT parent 1: prio 2 protocol ip handle 112 fw flowid 1:112 # iptables ruels for marking forwarded traffic # put everything to lowest prio iptables -t mangle -A FORWARD -o $INT -j MARK --set-mark 112 # VOIP traffic -> 110 iptables -t mangle -A FORWARD -o $INT -p udp --sport sip \ -j MARK --set-mark 110 iptables -t mangle -A FORWARD -o $INT -p udp --dport sip \ -j MARK --set-mark 110 iptables -t mangle -A FORWARD -o $INT -p udp --dport 1:10500 \ -j MARK --set-mark 110 # higher prio iptables -t mangle -A FORWARD -o $INT -p tcp -m multiport \ --sports 22,80,443,143 -j MARK --set-mark 111 iptables -t mangle -A FORWARD -o $INT -p icmp -j MARK --set-mark 111 >8 ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
[LARTC] need bandwidth manager
dear sir, i want to install and configure bandwidth manager using Rednat Linux server, i saw the codes to use from website but the problem is how to apply the code, will i be entering the code one after the other at shell prompt or put it in a notepad or how can I use the codes? I am a network engineer and I am new to using Linux Sever. Thank you Regards, Seye Sponsored Link Online degrees - find the right program to advance your career. Www.nextag.com ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
