From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] booting term kernel over the net
Date: Wed, 11 Dec 2002 16:16:50 -0800 [thread overview]
Message-ID: <8d3c9c51edaabf726e415e3dd5ca04a1@collyer.net> (raw)
I believe Skip's problem is that he's got 001 IP addresses from his
DSL provider, and that's needed for his DSL router or bridge that is
also doing NAT. NAT implementations generally don't understand IL,
but most of them allow incoming calls to specific ports to be
forwarded to specified internal machines.
next reply other threads:[~2002-12-12 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 0:16 Geoff Collyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 18:04 Russ Cox
2002-12-11 18:03 Fco.J.Ballesteros
2002-12-11 17:26 Fco.J.Ballesteros
2002-12-11 17:12 a
2002-12-11 17:51 ` Axel Belinfante
2002-12-11 15:14 Skip Tavakkolian
2002-12-11 13:59 Russ Cox
2002-12-11 11:17 Fco.J.Ballesteros
2002-12-11 8:37 Fco.J.Ballesteros
2002-12-11 8:11 Skip Tavakkolian
2002-12-11 1:23 Skip Tavakkolian
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=8d3c9c51edaabf726e415e3dd5ca04a1@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).