Netdev List
 help / color / mirror / Atom feed
From: Remco van Mook <remco@slashme.org>
To: netdev@oss.sgi.com
Cc: jamal <hadi@cyberus.ca>, ahu@ds9a.nl
Subject: Re: bridge between ppp and ethernet - 1 IP address and assign it to another host
Date: Wed, 9 Mar 2005 21:01:12 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0503092041400.17842@localhost> (raw)


I've been toying with the suggestion to do something with routing table 0 to
accomplish this, and I can report it works, standard 2.6.10 kernel. Here's how
I did it:

Assuming a linux system, connected to a local network 172.16.0.0/24, own
address 172.16.0.13, 'ppp' ip address to be assigned to a system that has
ip address 172.16.0.4

On the box that establishes the PPP connection:
1) establish ppp connection, get IP address, say 192.168.0.2
2) ip route del local 192.168.0.2
3) ip route add 192.168.0.2 via 172.16.0.4

On the other box, 172.16.0.4:

1) ip addr add 192.168.0.2 dev eth0
2) ip route add 0/0 via 172.16.0.13

I didn't bother assigning the IP address for the other box dynamically; that
might still pose a challenge - outside the scope of netdev IMHO.

Optionally you might want to SNAT outbound traffic on the PPP interface to
enforce the correct IP address. Of course the solution doesn't actually
'bridge' the traffic, you get another visible hop, but the effect is almost
the same.

Kind regards,

Remco van Mook

             reply	other threads:[~2005-03-09 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 20:01 Remco van Mook [this message]
2005-03-10  0:30 ` bridge between ppp and ethernet - 1 IP address and assign it to another host jamal
  -- strict thread matches above, loose matches on Subject: below --
2005-03-06  5:01 Mark Smith
2005-03-07 12:39 ` jamal
2005-03-07 13:56   ` Mark Smith
2005-03-07 21:32     ` bert hubert
2005-03-07 23:33       ` jamal
2005-03-08  1:27         ` Mark Smith
2005-03-08 14:10           ` jamal
2005-03-05 22:04 bert hubert
2005-03-16  2:37 ` Horms

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=Pine.LNX.4.58.0503092041400.17842@localhost \
    --to=remco@slashme.org \
    --cc=ahu@ds9a.nl \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    --cc=remco@virtu.nl \
    /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