From: Kilian Krause <kk@verfaction.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] restricting nat on a net
Date: Wed, 27 Mar 2002 08:55:54 +0000 [thread overview]
Message-ID: <marc-lartc-101721940215347@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101718795922542@msgid-missing>
Hi Luiz,
for 802.11b there's a nice package at: http://nocat.net.. it restricts all traffic until authorization..
--
Best regards,
Kilian
----------------------------------------------------------------
/dev/random reads at Wednesday, March 27, 2002 09:55:
Don't stop posting, a good laugh breaks up my day nicely
----------------------------------------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-03-27 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 0:09 [LARTC] restricting nat on a net Luiz Felipe Ceglia
2002-03-27 8:55 ` Kilian Krause [this message]
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-101721940215347@msgid-missing \
--to=kk@verfaction.de \
--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.