From: jamal <hadi@cyberus.ca>
To: lartc@vger.kernel.org
Subject: Re: [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 with
Date: Thu, 11 Jul 2002 12:06:38 +0000 [thread overview]
Message-ID: <marc-lartc-102638963713023@msgid-missing> (raw)
I havent run any 2.2 code in years (and dont have a machine with such
code;->)
Can you turn on debugging in the ingress code?
Does the same syntax work in 2.4?
cheers,
jamal
On Thu, 11 Jul 2002, Andrei Boros wrote:
>
> 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 it were passive mode, why didn't the ingress capture the ftp session
> packets on port 21???
>
> I even set firewall to mark everything and the filter directs it to
> ingress. Nothing happened.
>
>
> > > 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.
> > > Recompiled, installed kernel and modules.
> > > Recompiled tc with diffserv=y.
> > >
> > > I tried a setup very similar to the example Edge2:
> > >
> > >ipchains -A input -p tcp -d 0/0 20 --mark 20
> > >ipchains -A input -p tcp -d 0/0 21 --mark 20
> > >
> > >tc qdisc add dev eth0 handle ffff: ingress
> > >
> > >tc filter add dev eth0 parent ffff: protocol ip prio 50 handle 20 fw
> > >police rate 256kbit burst 25k mtu 1.5k drop flowid :1
> > >
> > >I tried uploading with a ftp client and there was no traffic limit
> > >imposed on what my box received.
> > >
> > >tc -s qdisc ls shows all counters as 0 (zero).
> > >
> > >I looked around for this issue and managed to find exactly my problem
> > >described in a forum at
> > >http://www.geocrawler.com/archives/3/11111/2001/5/0/5806401/ but the
> > >message was unaswered there.
> > >
> > > If anyone has any suggestions, they are most welcome.
> > >
> > >--
> > >ing. Andrei Boros
> > >mailto:andrei@srr.ro / +40-1-303-1870
> > >Centrul pt. Tehnologia Informatiei
> > >Societatea Romana de Radiodifuziune
> > >_______________________________________________
> > >LARTC mailing list / LARTC@mailman.ds9a.nl
> > >http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> > >
> >
> > -----------------------------------
> > mailto:alexey_talikov@texlab.com.uz
> > BR
> > Alexey Talikov
> > FORTEK
> > -----------------------------------
> >
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
> --
> ing. Andrei Boros
> mailto:andrei@srr.ro / +40-1-303-1870
> Centrul pt. Tehnologia Informatiei
> Societatea Romana de Radiodifuziune
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> PC Mods, Computing goodies, cases & more
> http://thinkgeek.com/sf
> _______________________________________________
> Diffserv-general mailing list
> Diffserv-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/diffserv-general
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-07-11 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 12:06 jamal [this message]
2002-07-12 9:57 ` [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 jamal
2002-07-12 10:11 ` [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 with jamal
2002-07-12 10:49 ` Julian Anastasov
2002-07-12 11:37 ` jamal
2002-07-12 12:26 ` Julian Anastasov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-102638963713023@msgid-missing \
--to=hadi@cyberus.ca \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.