Hopeless Windows VPN client as gateway in a Linux Network?

From: Børge Nygaard Austvold (baustvold_at_hotmail.com)
Date: 02/28/05


Date: Mon, 28 Feb 2005 19:37:29 +0100

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



Relevant Pages

  • Re: Multi NIC Windows 2003 routing problem
    ... 157025 - Default Gateway Configuration for Multihomed Computers ... Microsoft Windows XP - Multihoming Considerations ... > I have a Windows 2003 Enterprise Server which talks to machines in one> private network, hosted on one network card, and another private network as> well as the internet which should be routed over the other network card. ...
    (microsoft.public.win2000.networking)
  • Re: [opensuse] Would like explanation from networking guru
    ... And 192.168.11.1 is the gateway between Linux network and Windows ... How do you get that 192.168.11.1 is gateway to the Windows network? ...
    (SuSE)
  • Re: Norton Internet Security and XP Pro *before* logon
    ... The Internet Gateway is an XP Pro SP2 machine ... >> Windows is up to date on all the networked PC's. ... The network is connected via a switch to a second Ethernet card ... >> other connections *even though the gateway PC is sitting at the logon ...
    (alt.comp.anti-virus)
  • Re: [opensuse] Would like explanation from networking guru
    ... network, but not the internet on the wireless from linux.. ... Cannot get to the internet from linux on the windows network in any case ... Without any default gateway you can still connect to any PC in the SAME ...
    (SuSE)
  • Re: How can I configure my Windows 2003 DC machine to act as a router?
    ... Get rid of one of the the default gateways on the Windows Server 2003 ... On subnet A either configure machines with a default gateway of ... There are two network interfaces on Windows 2003 Server. ...
    (microsoft.public.windows.server.networking)