From: phil@optimumdata.com phil@optimumdata.com
To: lartc@vger.kernel.org
Subject: [Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming
Date: Sat, 03 Mar 2001 05:46:52 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417091@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940417088@msgid-missing>
<PRE>On Fri, 2 Mar 2001, Mike Fedyk wrote:
><i> There has to be a better way.
</I>
It's the one I use; it works and works well.
Asking someone who deals with "network appliance" routers (ie Cisco) might
lead to some ideas. But the Cisco folks I asked recommended the solution
I told you about. You might have better luck asking someone else.
><i> I'm forwarding this to LKML. Maybe they have a better idea...
</I>
<A HREF="mailto:netdev@oss.sgi.com">netdev@oss.sgi.com</A> (or something like that) is actually a better place
><i> I know the kernel keeps a route cache, is there something like a reverse MASQ
</I>><i> feature somewhere. Storing which incoming route + port number and keeping a
</I>><i> dynamic list...
</I>
--
-----------------------------------------------------------------------
Phil Brutsche <A HREF="mailto:phil@optimumdata.com">phil@optimumdata.com</A>
</PRE>
next prev parent reply other threads:[~2001-03-03 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 3:38 [Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming routes] Mike
2001-03-03 4:15 ` [Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming Jeremy
2001-03-03 5:46 ` phil [this message]
2001-03-03 6:02 ` [Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming routes] David
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-98373940417091@msgid-missing \
--to=phil@optimumdata.com \
--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.