Hello,
On Fri, 12 Jul 2002, Andrei Boros wrote:
> I also tried filtering using the u32 match ip dport ... same result.
> I even tried u32 match ip (anything ip), same result.
This is another issue, may be for howto:12.1.2. Bert promised
to clarify them in the Howto:
http://mai
Julian Anastasov wrote:
>
> You probably have to apply more fixes to be sure something
> will not break. I just uploaded some fixes for the 2.2 code as
> it appears nobody have the time to deal with it:
>
> http://www.linuxvirtualserver.org/~julian/#qos-2.2
I'll try them asap.
>
>
Hello,
On Wed, 10 Jul 2002, Andrei Boros wrote:
> I tried to control the ingress traffic with the ingress qdisc with no
> success whatsoever.
> I got 2.2.21 kernel and installed the ds8 patch to have the ingress
> qdisc too.
You probably have to apply more fixes to be sure so
Alexey Talikov wrote:
>
> May be you use ftp in passive mode, where port 20 not used
>
No, I set the client not to use passive mode, and confirmed it with
tcpdump. If it were a protocol/port specific thing I'd dig more in that
direction.
And the statistic counters are on zero at all times.
If
May be you use ftp in passive mode, where port 20 not used
10.07.2002 11:57:48, Andrei Boros <[EMAIL PROTECTED]> wrote:
>
> Since some other constraints require me to still run 2.2 kernel.
>(drivers for some hardware not working under 2.4)
>
> I tried to control the ingress traffic with the ing
Since some other constraints require me to still run 2.2 kernel.
(drivers for some hardware not working under 2.4)
I tried to control the ingress traffic with the ingress qdisc with no
success whatsoever.
I got 2.2.21 kernel and installed the ds8 patch to have the ingress
qdisc too.
Recompi
