[LARTC] ingress still not working :-(

[LARTC] ingress still not working :-(

[Clemens]

<PRE>Hi there,

I am still having troubles getting ingress policy shaping to work. I run
2.2.16-3 kernel with all QoS options enabled (and in the kernel, not as
modules), installed iproute.2.2.4-2 from RPM (running Red Hat here).

Shaping in the 'other direction' is working by the way.

I try the following (as found in multiple documents):
tc qdisc add dev eth0 handle ffff: ingress

The error I get is:
RTNETLINK answers: No such file or directory

Any help is greatly appreciated,

Clemens Sibon



</PRE>

[LARTC] ingress still not working :-(

[bert]

<PRE>On Fri, Oct 27, 2000 at 11:37:02PM +0200, Clemens Sibon wrote:

&gt;<i> I try the following (as found in multiple documents):
</I>&gt;<i> tc qdisc add dev eth0 handle ffff: ingress
</I>&gt;<i> 
</I>&gt;<i> The error I get is:
</I>&gt;<i> RTNETLINK answers: No such file or directory
</I>
This is a known issue. I try to find the people who wrote the ingress
policer. I'll also put a note in the HOWTO.

Regards,

bert hubert

-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>

[LARTC] ingress still not working :-(

[Clemens]

<PRE>
On Sat, 28 Oct 2000, bert hubert wrote:

&gt;<i> On Fri, Oct 27, 2000 at 11:37:02PM +0200, Clemens Sibon wrote:
</I>&gt;<i> 
</I>&gt;<i> &gt; The error I get is:
</I>&gt;<i> &gt; RTNETLINK answers: No such file or directory
</I>&gt;<i> 
</I>&gt;<i> This is a known issue. I try to find the people who wrote the ingress
</I>&gt;<i> policer. I'll also put a note in the HOWTO.
</I>
When I read the help in the kernel-menu, I saw something under Kernel/User
netlink socket (CONFIG_NETLINK) about a device that should be made having
major mode 36. Could this be the thing missing that generates the above
error?

I have no idea how to find out if I have the device or how to make it,
since the name isn't mentioned anywhere.

I have been looking for a /dev/ingress but that doesn't exist..

Do I have to upgrade to a 2.4.X kernel to get ingress policer to work
without the errors? If that's the case, I am willing to give it a try
(and probably I should convert my ipchains to iptables?)

Clemens Sibon



</PRE>

[LARTC] ingress still not working :-(

[bert]

<PRE>On Sat, Oct 28, 2000 at 03:25:51PM +0200, Clemens Sibon wrote:

&gt;<i> When I read the help in the kernel-menu, I saw something under Kernel/User
</I>&gt;<i> netlink socket (CONFIG_NETLINK) about a device that should be made having
</I>&gt;<i> major mode 36. Could this be the thing missing that generates the above
</I>&gt;<i> error?
</I>
No, that's not it.

&gt;<i> I have been looking for a /dev/ingress but that doesn't exist..
</I>
And it shouldn't - these filters have no corresponding entries in /dev.

&gt;<i> Do I have to upgrade to a 2.4.X kernel to get ingress policer to work
</I>&gt;<i> without the errors? If that's the case, I am willing to give it a try
</I>&gt;<i> (and probably I should convert my ipchains to iptables?)
</I>
It doesn't work in 2.4 either. I'll post some mail about this problem here
shortly.

Regards,

bert hubert

-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>