routing nightmare

C. Olmsted cliffo at u.washington.edu
Fri Jul 14 00:46:19 PDT 2000


Hey all,

After much too much time spent trying every combination possible to get
pppd to authenticate over an ethernet connection, I have succeeded in
establishing a PPP over SSH VPN (virtual private network) between two
computers I am working with.

Now, I am trying to figure out what I'll need to do with the routing
tables and also to determine if I need to use IP masquerading.

Lets have some ascii art shall we (I'm new to this art form, so bare with
me)

The Client		 The "Server"		NFS/NIS Server
______________		 _____________		 _______________
| 192.168.1.4 |_ssh/ppp_| 192.168.1.3 |		 | 192.168.1.1 |
|	      |         | 192.168.1.2 |__no-ppp__|             |
|_____________|         |_____________|          |_____________|
        |		      |                       |
        |    _________________|________               |
	|____| rest of the internet   |_______________|
	     | via non encrypted link |
	     --------------------------


Ok, that will do.  Now, the client is running ssh which is tunnelling ppp
over netdevice ppp0.  The link between the two servers is actually
physically separate from the UW network system...thus no encryption
needed.  I would like to be able to communicate to the NFS/NIS server via
the secure link only (Note that all of these boxes have their own specific
UW IP address in addition to the ones shown).  In other words, all network
traffic headed for either server from the client should travel via the
ssh/ppp link and not via anything unencrypted...still with me?

The questions:
Does the first server (in the middle) need to have IP masquerading for the
client to see the nfs server?

What do I need to add to the routing tables such that a request to connect
to the nfs server is routed over the 192.168.1.0 network?

Thanks for the help...this is fun, but a pain.

Cliff



More information about the Linux mailing list