From: fabian <fabian@catamarca.rffdc.edu.ar>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] TC on bridge
Date: Fri, 27 Apr 2001 05:35:01 +0000 [thread overview]
Message-ID: <marc-lartc-98840798310666@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98815371204972@msgid-missing>
>> Why don't you upgrade to 2.4 kernel as opposed to 2.2.18?
>> > 2.2.18 with wrr-010302 (wrr-linux-2.2.18.patch) /
CWM> Of course I don't know why, but WRR is less tested on 2.4 kernels (i.e.:
CWM> I have done no real testing except trying it - I have not received any
CWM> problem or success repports)
Christian: i get this error message when trying to compile the kernel
2.2.18 modules with wrr and bridge patch:
sch_wrr.c: In function 'mac_classify':
sch_wrr.c:600: structure has no member named 'pkt_bridged'
make[2]: *** [shc_werr.o] Error 1
make[2]: *** Leaving directory '/usr/src/linux-2.2.18/net/sched'
make[1]: *** [_modsubdir_sched] Error 2
make[1]: *** Leaving directory '/usr/src/linux-2.2.18/net'
make: *** [mod_net] Error 2
--
Best regards,
fabian mailto:fabian@catamarca.rffdc.edu.ar
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-04-27 5:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 6:57 [LARTC] TC on bridge fabian
2001-04-25 5:44 ` Christian Worm Mortensen
2001-04-26 6:20 ` Stef Coene
2001-04-27 5:27 ` Re[2]: " fabian
2001-04-27 5:35 ` fabian [this message]
2001-04-27 6:25 ` Re[4]: " fabian
2001-04-27 13:58 ` Re[2]: " Fabian Alejandro Gervan
2001-04-27 19:14 ` Ramin Alidousti
2001-04-27 19:19 ` Christian Worm Mortensen
-- strict thread matches above, loose matches on Subject: below --
2001-04-27 21:54 Re[2]: " Christian Worm Mortensen
2001-04-27 21:59 ` Ramin Alidousti
2001-04-28 6:56 ` Christian Worm Mortensen
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-98840798310666@msgid-missing \
--to=fabian@catamarca.rffdc.edu.ar \
--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.