From: alex avriette <alex@macachu.yi.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing roaming computers with wireless ethernet cards
Date: Fri, 06 Apr 2001 16:51:20 +0000 [thread overview]
Message-ID: <marc-lartc-98657590819193@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98657267508407@msgid-missing>
> question: how should routing be handled for
> computers with wireless ethernet connections?
well thats easy, mostly. have your wireless hub attached to a new nic, and
have that interface be assigning dhcp to all your roaming clients. then
route the traffic over that interface the exact same way you would route
any other interface. apple's airports provide dhcp and NAT all on their
own -- im not sure if any of the other ones do that.
have fun,
alex
(wireless on a powerbook g4)
_______________________________________________
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-06 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 15:59 [LARTC] routing roaming computers with wireless ethernet cards terrylr
2001-04-06 16:51 ` alex avriette [this message]
2001-04-06 17:56 ` Terry L. Ridder
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-98657590819193@msgid-missing \
--to=alex@macachu.yi.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox