Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: =?unknown-8bit?q?Roch=C3=A9?= Compaan <roche@upfrontsystems.co.za>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linking two networks
Date: Sat, 30 Nov 2002 12:13:32 +0000	[thread overview]
Message-ID: <marc-lartc-103865859608331@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103865308106021@msgid-missing>

On Sat, 30 Nov 2002 13:53:57 +0200
Abraham van der Merwe <abz@frogfoot.net> wrote:

Thanks for the advice :-)

> You don't need to add a route to get to 192.168.1.0/24 since you your
> default gw will route packets to that network anyway. You are also use
> 192.168.1.10 as a gateway to get onto the 1/24 network which won't
> work (you can't use a machine on the network which you want to reach
> as a gateway). You want to be using 192.168.2.10 as a gateway to get
> onto the 1/24 network.

Mmm, thought I had something upside down.

> 
> Also, you can use unnumbered ppp. Just do this:
> 
> On your home gateway's eth0 assign 192.168.2.10 and on your office's
> side, assign 192.168.1.10 to eth1. Then use unnumbered ppp on both
> sides and make sure that ip forwarding is enabled on the office gw.

I don't quite follow how to set up unnumbered ppp. Should I just omit
the local_ip:remote_ip in my ppp options file at home?

> 
> On your office side, you'll have
> 
> pppd ... 192.168.1.10:192.168.2.10
> 
> and on your home side, you'll have
> 
> pppd ... defaultroute :
> 
> Of course, you probably have /etc/ppp/* with the pon/poff scripts in
> which case you need to add above to your /etc/ppp/peers/* scripts

At the moment I have no scripts in place - I'm doing it manually to see
what works and what I should eventually put in the scripts. I only have
/etc/ppp/options on both sides.

-- 
Roché Compaan
Upfront Systems                 http://www.upfrontsystems.co.za
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-11-30 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30 10:41 [LARTC] Linking two networks =?unknown-8bit?q?Roch=C3=A9?= Compaan
2002-11-30 11:53 ` Abraham van der Merwe
2002-11-30 12:13 ` =?unknown-8bit?q?Roch=C3=A9?= Compaan [this message]
2002-11-30 12:37 ` Abraham van der Merwe
2002-11-30 12:46 ` =?unknown-8bit?q?Roch=C3=A9?= Compaan
2002-12-01  7:06 ` =?unknown-8bit?q?Roch=C3=A9?= Compaan
2002-12-01  7:11 ` =?unknown-8bit?q?Roch=C3=A9?= Compaan

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-103865859608331@msgid-missing \
    --to=roche@upfrontsystems.co.za \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox