Hopeless Windows VPN client as gateway in a Linux Network?

Hi,

I've got couple of linux machines setup in a local network via a DSL router
as the gateway to internet and it works fine. The problem is that the only
way to connect to my office network is via a Windows Shiva VPN client. So I
installed windows on a box and tried to use it as a second gateway in the
linux network.

The problem is that the VPN client adds a server assigned routing to my
windows routing table with destination 0.0.0.0 and gateway 0.0.0.0 to the
VPN interface with metric 1. I've tried to edit the routing table, but the
VPN client detects any changes in the routing table and flushes a brand new
one that overwrites any changes that I made.

So my billion dollar question is. Is it any way to use this windows box as a
second gateway in my network to connect to my office? I've prefer to have It
always connected any use the windows box as a gateway. Can I use VMware and
NAT? create a bridge or do I have to roll out a mile long cable to connect
to my office from Linux?

Anybody? Please help, I prefere to do development on linux, but since the
VPN software only runs on windows I'm forced to work in this environment
unless a bright brain out there can help me....

This is the routing table on my windows box before and after I connect the
VPN client.

================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 02 a5 c2 b2 34 ...... Intel(R) PRO/100 VM Network Connection -
Packet Scheduler Miniport
0x3 ...00 c0 45 00 00 02 ...... VPN Client Virtual Adapter #2 - Packet
Scheduler Miniport
0x4 ...00 c0 45 00 00 01 ...... VPN Client Virtual Adapter - Packet
Scheduler Miniport
0x40006 ...00 08 02 f6 40 f1 ...... Compaq WLAN MultiPort W200 - Packet
Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.103 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.103 192.168.1.103 30
192.168.1.103 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.1.255 255.255.255.255 192.168.1.103 192.168.1.103 30
224.0.0.0 240.0.0.0 192.168.1.103 192.168.1.103 30
255.255.255.255 255.255.255.255 192.168.1.103 2 1
255.255.255.255 255.255.255.255 192.168.1.103 3 1
255.255.255.255 255.255.255.255 192.168.1.103 4 1
255.255.255.255 255.255.255.255 192.168.1.103 192.168.1.103 1
Default Gateway: 192.168.1.1
================================================== =========================
Persistent Routes:
None


================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 02 a5 c2 b2 34 ...... Intel(R) PRO/100 VM Network Connection -
Packet Scheduler Miniport
0x3 ...00 c0 45 00 00 02 ...... VPN Client Virtual Adapter #2 - Packet
Scheduler Miniport
0x4 ...00 c0 45 00 00 01 ...... VPN Client Virtual Adapter - Packet
Scheduler Miniport
0x40006 ...00 08 02 f6 40 f1 ...... Compaq WLAN MultiPort W200 - Packet
Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.19.144.53 172.19.144.53 1
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.103 31
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.19.144.0 255.255.255.0 172.19.144.53 172.19.144.53 1
172.19.144.53 255.255.255.255 127.0.0.1 127.0.0.1 30
172.19.255.255 255.255.255.255 172.19.144.53 172.19.144.53 30
192.168.1.0 255.255.255.0 172.19.144.53 172.19.144.53 1
192.168.1.103 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.1.255 255.255.255.255 192.168.1.103 192.168.1.103 30
224.0.0.0 240.0.0.0 172.19.144.53 172.19.144.53 1
224.0.0.0 240.0.0.0 192.168.1.103 192.168.1.103 31
255.255.255.255 255.255.255.255 172.19.144.53 172.19.144.53 1
255.255.255.255 255.255.255.255 192.168.1.103 2 1
255.255.255.255 255.255.255.255 192.168.1.103 4 1
255.255.255.255 255.255.255.255 192.168.1.103 192.168.1.103 1
Default Gateway: 172.19.144.53
================================================== =========================
Persistent Routes:
None

Thanks,

Børge Nygaard Austold




Børge Nygaard Austvold

Børge Nygaard Austvold wrote:
> Hi,
>
> I've got couple of linux machines setup in a local network via a DSL router
> as the gateway to internet and it works fine. The problem is that the only
> way to connect to my office network is via a Windows Shiva VPN client. So I
> installed windows on a box and tried to use it as a second gateway in the
> linux network.
>
> The problem is that the VPN client adds a server assigned routing to my
> windows routing table with destination 0.0.0.0 and gateway 0.0.0.0 to the
> VPN interface with metric 1. I've tried to edit the routing table, but the
> VPN client detects any changes in the routing table and flushes a brand new
> one that overwrites any changes that I made.
>
> So my billion dollar question is. Is it any way to use this windows box as a
> second gateway in my network to connect to my office? I've prefer to have It
> always connected any use the windows box as a gateway. Can I use VMware and
> NAT? create a bridge or do I have to roll out a mile long cable to connect
> to my office from Linux?
>
> Anybody? Please help, I prefere to do development on linux, but since the
> VPN software only runs on windows I'm forced to work in this environment
> unless a bright brain out there can help me....
>

You're not likely to like it, but ...

Many corporate VPN clients go to great trouble to
deny all other networking for the duration of the
VPN connection. This is done to prevent uncontrolled
sneak paths between the corporate intranet and the
Internet. It seems that you have such a thing.

--

Tauno Voipio
tauno voipio (at) iki fi