From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Firewall/NAT and importing outside interface
Date: Sun, 10 May 2020 19:04:29 +0100 [thread overview]
Message-ID: <CAOw7k5gJOwE3OficCLC4vswbJNzHPdGpV3K5wxkuVgjA=JjdQw@mail.gmail.com> (raw)
In-Reply-To: <CAOomyf8emhBqqeq7Nst=tudFLRtNEQE_nUBiUztTw-7BEXsdBw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]
>
> If one is running a mail server and has it inside their firewall and if
> using one IP then t has to use NAT. Couldn't one presumeably use the setup
> above and run a mail server on Plan 9 and bypass having to use NAT? And
> also do the same thing for a web server?
Yes, I do that. The example you quoted creates two independent IP stacks,
starting with the default '#I0' IP stack on ether0, then adding a new IP
stack '#I1' connected to ether1 (#l1).
There is a separate TCP/IP, UDP/IP, ICMP etc for each stack. I also import
/net from a Linux server via Inferno (on Linux) so I can send mail from a
non-RBLd address.
You can create several types of virtual interface ("medium") on the IP
stack, connected to a user-mode process. See pkg and netdev in ip(3)
I still have a router with NAT though for non-Plan 9 machines. I never
got round to writing a NAT for Plan 9 (which could work in user mode).
On Fri, May 8, 2020 at 7:55 PM Robert Sherwood <robert.sherwood@gmail.com>
wrote:
> I love the idea of importing the external interface to get outside the
> network. When I first read about this in Plan9, that's when the system
> really "clicked" for me.
>
> On Fri, May 8, 2020 at 1:08 PM hiro <23hiro@gmail.com> wrote:
>
>> you can also have multiple ipstacks, working ipv6 and what have you.
>> cinap fixed a bunch of stuff in this regard.
>>
>> it's much more like linux network namespaces now, no limits to your
>> creativity...
>>
>> ------------------------------------------
>> 9fans: 9fans
>> Permalink:
>> https://9fans.topicbox.com/groups/9fans/Te43262c53bc71855-M9383be68c88caf7d73dc38d6
>> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>>
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Te43262c53bc71855-M5a51a5f17a7747f354e5309b>
>
[-- Attachment #2: Type: text/html, Size: 3694 bytes --]
prev parent reply other threads:[~2020-05-10 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1088262094.244310.1588956346600.ref@mail.yahoo.com>
2020-05-08 16:45 ` G B
2020-05-08 17:07 ` [9fans] " hiro
2020-05-08 18:53 ` Robert Sherwood
2020-05-10 18:04 ` Charles Forsyth [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='CAOw7k5gJOwE3OficCLC4vswbJNzHPdGpV3K5wxkuVgjA=JjdQw@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).