From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Advance Routing Guidance
Date: Thu, 15 Aug 2002 19:35:16 +0000 [thread overview]
Message-ID: <marc-lartc-102944020117120@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102939645206458@msgid-missing>
On Thu, 15 Aug 2002, Laurens van Alphen wrote:
> Why don't you want to use NAT? NAT is not dirty. NAT is stable, fast,
> secure and saves you from renumbering your network when you switch
> providers.
On the other hand, NAT breaks useful stuff such as IPSec.
Doei, Arthur.
--
/\ / | arthurvl@sci.kun.nl | Work like you don't need the money
/__\ / | A friend is someone with whom | Love like you have never been hurt
/ \/__ | you can dare to be yourself | Dance like there's nobody watching
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-08-15 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 7:45 [LARTC] Advance Routing Guidance Arindam Haldar
2002-08-15 8:42 ` William L. Thomson Jr.
2002-08-15 15:34 ` Laurens van Alphen
2002-08-15 19:35 ` Arthur van Leeuwen [this message]
2002-08-15 21:06 ` Julian Anastasov
2002-08-16 14:52 ` Arindam Haldar
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-102944020117120@msgid-missing \
--to=arthurvl@sci.kun.nl \
--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.