search for: ss001007

Hello. I have got strange problem with tc utility (iproute2-ss001007) on linux 2.4.18. No matter what rules i am going to test, the resul of ''tc class ls/show'' is always the same : ATSLite ()# tc -s class ls dev eth1 do_page_fault() #2: sending SIGSEGV to tc for illegal read access from 00000000 (epc == 00000000, ra == 00408750) Segmentation fault...

...ded a rule for it. Then the network was unreachable. I tried the same things on kernel 2.2.14 (suse 6.4) and kernel 2.2.16 (on a modified redhat). I tried also on a machine with two network cards. I also played with /proc/sys/net/ipv4/ip_forward. The ip command version was ss991023 (suse 6.4) and ss001007 on redhat. What am I doing wrong? Thank you, Gustavo. -- "E pur si muove" -- Galileo Galilei

I applied esfq patch to kernel then I have applied iproute2-2.2.4-now-ss001007-esfq.diff to patch iproute2 (tc utility, iproute2-ss010824) source: http://www.ssi.bg/~alex/esfq/ But whenever I try to add esfq qdisc with parameter it says it donot know the qdisc i.e esfq. tc qdisc add dev eth0 parent 1:13 handle 13: esfq perturb 34 quantum 1514 depth 25 divisor 23...

...rb 10 My default class quantum (99) is correct I guess : quantum is > 1500 (my MTU). If I change the rate of my default class to something >= 79 Kbit then it work without any warning !?!? I am just looking for an explanation as I''m lost here... FYI : # tc -V tc utility, iproute2-ss001007 # uname -r 2.4.26 # ip link sh eth0 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc htb qlen 1000 link/ether 00:40:63:c9:b3:32 brd ff:ff:ff:ff:ff:ff Thanks, Yacine.

...Alexey, Sorry to bother you with this small question about nexthop syntax failing, but I haven''t found anyone else who can answer it - including Matthew Marsh or those on the lartc mailing list. The problem, with 2.2.19 and 2.2.20 kernels and versions of iproute2 up to iproute2-2.2.4-now-ss001007 (the most recent that compiles for me), is that this command does not work: # ip ro add default nexthop via 66.xx.yy.209 dev eth1 nexthop via 65.yy.xx.97 dev eth2 RTNETLINK answers: Invalid argument This is despite the fact that adding these individually works fine: # ip ro add default via 66.xx...

...ianized source from: http://packages.debian.org/testing/net/iproute ...but the vanilla source should work fine. For some reason I can''t find a working download right now. 4. The esfq 0.2 patch from: http://www.ssi.bg/~alex/esfq/ Extract the tar.gz and use iproute2-2.2.4-now-ss001007-esfq.diff to patch your iproute2 source. Beware that this may not compile if your distro uses its own headers in /usr/include, and iproute2 needs to reference the patched pkt_sched.h. I don''t know what the best way around this is. Please note that I don''t really know...

...p flags:!SYN,RST,ACK/ACK MARK set 0x14 MARK tcp -- anywhere anywhere tcp flags:SYN,RST,ACK/ACK length 0:64 TOS match !Normal-Service MARK set 0x14 MARK all -- anywhere anywhere MARK match 0x0 MARK set 0x63 # tc -V tc utility, iproute2-ss001007 # uname -r 2.4.26 # iptables --version iptables v1.2.9 Thank you, Yacine.

Hello Lartc''s users, This is my first contact. I''m trying to implement a new queue discipline based on bfifo schedule. I search on internet but there are some problem(s) that I don''t Know how to solve them and that''s why I''m here asking for your help. Well, These were my steps for the implementation: - Put the new qdisc routine