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:46:18 +0000	[thread overview]
Message-ID: <marc-lartc-103866057809285@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103865308106021@msgid-missing>

Thanks for your help.

I will try this later this afternoon and let you know. I think I
understand a bit more about routing and networks now.

On Sat, 30 Nov 2002 14:37:09 +0200
Abraham van der Merwe <abz@frogfoot.net> wrote:

> Hi Roch?!
> 
> > > 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?
> 
> That is correct. See, ppp is a point-to-point protocol, so traffic can only
> go in two directions anyway, so you can tell ppp not to use any kind of
> layer 3 routing and just send packets to the other side automatically.
> 
> In Linux you do that by just specifying local_ip:remote_ip on the server
> side and : on the client side.
> 
> > > 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.
> 
> Ok, so this (otoh so don't blame me if it doesn't work *g*) in your inittab
> should do the job:
> 
> ------------< snip <------< snip <------< snip <------------
> # At office
> S0:23:respawn:/usr/sbin/pppd /dev/ttyS0 115200 modem noauth crtscts persist \
> 192.168.1.10:192.168.2.10 nodetach >>/var/log/leased.log
> 
> # At home
> S0:23:respawn:/usr/sbin/pppd /dev/ttyS0 115200 noauth lock debug crtscts
> defaultroute persist nodetach >>/var/log/leased.log
> ------------< snip <------< snip <------< snip <------------
> 
> -- 
> 
> Regards
>  Abraham
> 
> A morsel of genuine history is a thing so rare as to be always valuable.
> -- Thomas Jefferson
> 
> ___________________________________________________
>  Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks
>  P.O. Box 3472, Matieland, Stellenbosch, 7602
>  Cell: +27 82 565 4451 Http: http://www.frogfoot.net
>  Email: abz@frogfoot.net
> 
> 


-- 
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:46 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
2002-11-30 12:37 ` Abraham van der Merwe
2002-11-30 12:46 ` =?unknown-8bit?q?Roch=C3=A9?= Compaan [this message]
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-103866057809285@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