When I did this, I routed the ingress traffic to an "ifb0" device, and then you can regulate the traffic normally like outbound traffic. This mechanism worked well, although you still cannot get good control how fast people send data to you so it is not very accurate. The best way to regulate the traffic is with a VPN server. -----Original Message----- From: lartc-owner@xxxxxxxxxxxxxxx [mailto:lartc-owner@xxxxxxxxxxxxxxx] On Behalf Of Andy Furniss Sent: Friday, July 31, 2015 11:18 AM To: Danushka Menikkumbura; lartc Subject: Re: Fwd: Ingress qdisc Danushka Menikkumbura wrote: > Hi, > > I am trying to enable ingress qdisc on my Linux box for some research > work that I am working on. I use the following command just to enable > ingress qdisc on eth1 but my machine freezes so that I cannot setup > any filters afterwards. > > sudo tc qdisc add dev eth1 handle 1: ingress > > Could someone let me know what might be the issue here please? Don't know - it works for me - though "handle 1:" is ignored ingress gets ffff: I guess you could try without handle and make sure your tc version matches your kernel. Though saying that I am using an old tc on a newer kernel! If you are using the latest for both maybe you should file a bug or mail the netdev list. -- To unsubscribe from this list: send the line "unsubscribe lartc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n����j�\�)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
