[LARTC] Big Recv-Q
I found a lot of connections with big Recv-Q like this: Proto Recv-Q Send-Q Local Address Foreign Address State tcp 153829 0 x.x.x.x:53147 64.15.119.12:80 ESTABLISHED tcp 153079 0 x.x.x.x:52019 64.15.118.200:80 ESTABLISHED tcp 144306 0 x.x.x.x:55079 213.251.139.92:80 ESTABLISHED tcp 137365 0 x.x.x.x:46043 213.251.141.84:80 ESTABLISHED tcp 133520 0 x.x.x.x:50579 209.17.65.38:80 ESTABLISHED tcp 120746 0 x.x.x.x:47240 74.125.10.23:80 ESTABLISHED tcp 104210 0 x.x.x.x:55118 208.64.44.102:80 ESTABLISHED tcp 102200 0 x.x.x.x:47276 64.246.38.79:80 ESTABLISHED tcp 100323 0 x.x.x.x:50529 89.202.157.134:80 ESTABLISHED What really means? It's a waste of traffic? Why the sockets are not receiving that data? All connections are to squid. I'm using 2.6.18 Kernel and squid 2.6.STABLE13. No delay pools, no traffic control rules. TOP said that: Tasks: 103 total, 3 running, 100 sleeping, 0 stopped, 0 zombie Cpu(s): 1.7%us, 2.0%sy, 0.0%ni, 84.3%id, 10.3%wa, 0.0%hi, 1.7%si, 0.0%st Mem: 1036160k total, 992744k used, 43416k free, 39236k buffers Swap: 2650684k total, 135824k used, 2514860k free, 126252k cached Thank you for any information. Paolo MalfattiLas mejores tiendas, los precios mas bajos, entregas en todo el mundo, YupiMSN Compras: Haz clic aquí... ___ 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?)
It works because linux (and XP too) maintain a cache of all routes learned. Try: ip route show cache.You can clean this cache: ip route flush cache. From: Andrew McGill <[EMAIL PROTECTED]>To: lartc@mailman.ds9a.nlSubject: [LARTC] netmask 255.255.255.255 vs ip route add via ... (bug?)Date: Tue, 14 Nov 2006 15:48:41 +0200 (SAST)>Greetings routing folks,>>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:>>Here's the interface, set up with a netmask of /32:>> # ip addr> ...> 2: eth0: mtu 1500 qdisc pfifo_fast >qlen 1000> link/ether 00:08:74:48:1f:0c brd ff:ff:ff:ff:ff:ff> inet 192.168.1.6/32 brd 192.168.1.255 scope global eth0> inet6 fe80::208:74ff:fe48:1f0c/64 scope link>valid_lft forever preferred_lft forever> ...>>And here's me trying to add the route:>> # ip route add default via 192.168.1.17> RTNETLINK answers: Network is unreachable>>Hmm ... erk ... workaround ... add a host route first, then add it >as a default route ...>> # sudo ip route add 192.168.1.17 dev eth0> # sudo ip route add default via 192.168.1.17>>And this is what we get ... (yep, it works)>> # ip route ls> 192.168.1.17 dev eth0 scope link> default via 192.168.1.17 dev eth0>>But wait! We can delete the host route! And it works just fine (you >*can* try this at home folks).>> # sudo ip route del 192.168.1.17> # ip route ls> default via 192.168.1.17 dev eth0>>So why did we need that host route?>>It should be possible to add the gateway directly, or it should be >impossible to delete it once something "depends" on it. The current >behaviour seems a little unbalanced (and, for my strange purposes, >inconvenient :)>> Tested on Ubuntu 6.06 Dapper (Kernel: 2.6.15, iproute2 20041019)> Looks the same on Fedora Core 3, (Kernel 2.6.11.8, iproute2 >2.6.9)>>&:-)>>>-->Disclaimer: this disclaimer and your base are us>___>LARTC mailing list>LARTC@mailman.ds9a.nl>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartcMSN Amor Busca tu ½ naranja ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] Two outbound internet links, using one network interface
From: Dashamir Hoxha <[EMAIL PROTECTED]>To: Pio Mendez <[EMAIL PROTECTED]>Subject: Re: [LARTC] Two outbound internet links, using one network interfaceDate: Thu, 12 Oct 2006 14:37:19 +0200>Pio Mendez wrote:>>PREROUTING chain is not traversed by local traffic, but OUTPUT >>chain does.>>I think that OUTPUT is traversed after routing decision is taken, so >it is still the same problem. I'm using OUTPUT chain in production environment to balance squid box traffic between 2 ISP, so I'm sure that you can reroute output packets using mangle OUTPUT chain. After traversing mangle and nat OUTPUT chains there is another routing process. Please check this diagram: http://www.imagestream.com/~josh/PacketFlow.png Las mejores tiendas, los precios mas bajos, entregas en todo el mundo, YupiMSN Compras: Haz clic aquí... ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] Two outbound internet links, using one network interface
PREROUTING chain is not traversed by local traffic, but OUTPUT chain does. What about this script? - IPT=/sbin/iptables PORT_LIST="22 53" for PORT in $PORT_LIST do $IPT -t mangle -A PREROUTING -p tcp --dport $PORT -s -j MARK --set-mark 4 $IPT -t mangle -A OUTPUT -p tcp --dport $PORT -s -j MARK --set-mark 4 done iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE ip route add 192.168.10.0/24 dev eth0 table 4 ip route add default via 192.168.10.1 table 4 ip rule add fwmark 4 table 4 Paolo Malfatti CiDiS Camiri _ Charla con tus amigos en línea mediante MSN Messenger: http://messenger.latam.msn.com/ ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
[LARTC] Only root qdisc's stats shows overlimits
Hi, I have a bridge with debian sarge and i'm shaping traffic with HTB. I dont understand why only root qdisc's stats shows overlimits. No other class or qdisc shows overlimits. Thanks, Paolo Las mejores tiendas, los precios mas bajos, entregas en todo el mundo, YupimMSN Compras: Haz clic aquí ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc