From: "A. Peter Mee" <lartc@itsmee.worldonline.co.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] Ingress - No such file or directory
Date: Tue, 09 Jul 2002 07:53:38 +0000 [thread overview]
Message-ID: <marc-lartc-102620120930863@msgid-missing> (raw)
Hi all,
(My apologies if this appears to be a repost - my mail yesterday does not
appear to have got to the list.)
I am attempting to implement the SYN flood protection scheme as presented in
LARTC. Unfortunately, when I attempt `tc qdisc add dev eth0 handle ffff:
ingress` I get the error:
RTNETLINK answers: No such file or directory
I have seen this referenced several times on this mailing list, but I appear
to have a seperate set of circumstances. I am using a kernal 2.4.18 with
Ingress as a module (sch_ingress.o exists in the location
/lib/modules/2.4.18/kernel/net/sched), and am able to load it with insmod
and remove it with rmmod.
Regardless of the state of the sch_ingress.o module, I get the same error.
Perhaps someone can point me in the correct direction?
TIA
Best regards,
A. Peter Mee
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-07-09 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 7:53 A. Peter Mee [this message]
2002-07-09 9:42 ` [LARTC] Ingress - No such file or directory bert hubert
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-102620120930863@msgid-missing \
--to=lartc@itsmee.worldonline.co.uk \
--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.