All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sadus ." <sadus@swiftbin.net>
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Internal PC/external Gateway
Date: Sat, 14 May 2005 19:20:33 +0300	[thread overview]
Message-ID: <1116087634.18707.2.camel@debianbox> (raw)
In-Reply-To: <20050514153608.GA24455@bender.817west.com>

The Multi routing doc is another scenario that includes sharing or load
balancing between 2 providers to the same machine, that's not what i
want.

I tried using iproute2 and iptables (SNAT), but i just don't know what
to set as default gw for PC2, since PC2 can't see Provider 2 unless the
gateway of PC2 is the Linux GW (since it got ipforward).

thanks

On Sat, 2005-05-14 at 11:36 -0400, Jason Opperisano wrote:
> On Sat, May 14, 2005 at 11:59:36AM +0300, Sadus . wrote:
> > Hello,
> > So here's my current setup at home.
> > I control Provider 2. (which is not more than a simple box taking
> > internet from provider 1 and that internet sharing enabled, restricted
> > to the box' internal network and my IP which is on the external
> > interface).
> > I also control the Linux GW.
> > 
> >                                                                  
> >                                           +------------+        
> >                                           |            |       |
> >                                       ----+ Provider 1 +-------
> >         __                            |   |            |     /
> >   PC1__/  \_         +------+-------+ |   +------------+    |
> >   _/        \__      |              | |                    /
> >  /             \     |              | |                    |
> > | Local network -----+Linux GW  eth0|-                     |Internet
> >  \_           __/    |              | |                    |
> >    \__     __/       |              | |                    \
> >   PC2 \___/          +------+-------+ |   +------------+    |
> >                                       |   |            |     \
> >                                       ----+ Provider 2 +-------
> >                                           |            |       |
> >                                           +------------+        
> 
> how about following the instructions in the document you copied that
> ASCII art from [1]?
> 
> to paraphrase the openbsd folks, "don't ask how to do something, explain
> to us what you've done and where you got stuck."
> 
> -j
> 
> [1]:  http://lartc.org/howto/lartc.rpdb.multiple-links.html
> 
> --
> "Stewie: For God's sake, shake me. Shake me like a British nanny."
>         --Family Guy
> 



  reply	other threads:[~2005-05-14 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14  8:59 Internal PC/external Gateway Sadus .
2005-05-14 15:36 ` Jason Opperisano
2005-05-14 16:20   ` Sadus . [this message]
2005-05-14 16:41     ` Jason Opperisano
2005-05-14 17:01       ` Sadus .
2005-05-14 17:26         ` Jason Opperisano
2005-05-14 18:30           ` Sadus .
2005-05-14 19:00             ` Jason Opperisano
2005-05-14 23:52               ` Sadus .
2005-05-16 21:48                 ` Jason Opperisano
2005-05-17 12:55                   ` Sadus .

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=1116087634.18707.2.camel@debianbox \
    --to=sadus@swiftbin.net \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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.