Route Tables Vpn

Hello Linux friends,

Im quite new to linux, as I was bored and frustrated with M$ XP decided to install KDE on my server.
With help from our best friend google and these forums I almost managed to get my server completely working under Linux Suse 10.3

As expected I came across a few bumps in the road to linux, but patient as I am I managed to go sort most of them out which leaves me to one issue I need some help with.

I installed a VPN server on my server (pptpd) which is can connect to.

When I connect to my Linux server from my M$ work laptop I am registered on the network and I can ping the device.

My network looks like this.
I forwarded port 1723 to my server so I can connect from the internet to my server (VPN port) I can login from the WAN address and also enabled IP forwarding on my linux server.

Server IP: 192.168.2.189
work laptop IP: 192.168.2.101
VPN IP laptop: 10.10.10.10

I tried forwarding the VPN route to my gateway, but seem to be stuck.

Also I disabled the Suse firewall (as I am behind a firewall of my router)

To me it seems like there is a problem with my route table

I cant use NX remote control and SSH.. so that why I thought my routes were bad.

Enclosed you will see my route table:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.10.10 * 255.255.255.255 UH 0 0 0 ppp0
192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

Any ideas ?

Anyone ?

Anyone ?[/b]

Didn't answer originally because there are chunks missing from your information about the vpn server and how it issues IP addresses.

At face value, it looks like the server has a 192.168.x.x address on a physical adaptor, is issuing a 10.x.x.x address to a vpn connected client which also has a physical adaptor on a 192.168.x.x range - but no mention that the server has taken a 10.x.x.x address for itself.

Trying to talk to a 192.x.x.x address through a 10.x.x.x address just won't work - you need some common ground.

I may be reading your config wrong, but from the info you supplied, that's the best I can make from it.

Didn't answer originally because there are chunks missing from your information about the vpn server and how it issues IP addresses.

At face value, it looks like the server has a 192.168.x.x address on a physical adaptor, is issuing a 10.x.x.x address to a vpn connected client which also has a physical adaptor on a 192.168.x.x range - but no mention that the server has taken a 10.x.x.x address for itself.

Trying to talk to a 192.x.x.x address through a 10.x.x.x address just won't work - you need some common ground.

I may be reading your config wrong, but from the info you supplied, that's the best I can make from it.
[/b]

yes, the servers nic is 192.168.2.189, it is giving 10.10.10.10 address to the VPN client.
There is only one active NIC in the server.

My intention is, that I connect externally to the 10.10.10.10 address that is given to the client.

I had this setup before, and I could connect to the 10.10.10.10 address (but htis was in M$, so I assumed the method was right)

What do you suggest ?

yes, the servers nic is 192.168.2.189, it is giving 10.10.10.10 address to the VPN client.
There is only one active NIC in the server.

I had this setup before, and I could connect to the 10.10.10.10 address (but htis was in M$, so I assumed the method was right)[/b]

The M$ server would have had a 10.x.x.x address in order for it to work.

Depending whether you want access only to the server or to all or part of the remote LAN dictates both which IP address range VPN issues and also what IP address it ASSIGNS TO ITSELF.

I imagine your old windows server was doing something like ...

REAL INTERFACE: 192.168.2.189
VPN INTERFACE: 10.10.10.2
VPN CLIENT POOL 10.10.10.10 -> 20

.. to get access to the server only.

To get access to the whole (or part of the) LAN, you'd need to do something like ...

REAL INTERFACE: 192.168.2.189
VPN INTERFACE: 192.168.2.190
VPN CLIENT POOL 192.168.2.191 -> 200