[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] Problems with windows version and route command


  • Subject: [Openvpn-users] Problems with windows version and route command
  • From: "Clemson, Chris" <Chris.Clemson@xxxxxxxxxxxxxxxx>
  • Date: Fri, 8 Aug 2003 09:58:21 +0100

Hello!
I downloaded Openvpn yesterday, and managed to get it set up as a server on
our linux machine (i think - it's listening for requests anyway!).
I am now having problems with the windows version.

I installed the .exe version which seemed to install ok.
I created a new connection (so now i actually have 2 new virtual adapters -
i didn't realise the installer had set one up) and renamed it to saglanvpn.
doing openvpn --show-adapters shows the two adapters properly.

however, when i run the following command, route complains that it can't add
the route.

G:\Communications\OpenVPN>bin\openvpn --dev tap --dev-node saglanvpn
--config tls-home.conf
Fri Aug 08 08:50:52 2003 0: OpenVPN 1.5-beta4 Win32-MinGW [SSL] [LZO]
[MTU-DYNAM
IC] built on Aug  5 2003
Fri Aug 08 08:50:52 2003 1: LZO compression initialized
Fri Aug 08 08:50:52 2003 2: Data Channel MTU parms [ link_mtu=1606
extra_frame=4
2 extra_buffer=19 extra_tun=64 ]
Fri Aug 08 08:50:52 2003 3: Control Channel MTU parms [ link_mtu=1606
extra_frame=38 extra_buffer=0 extra_tun=0 ]
Fri Aug 08 08:50:52 2003 4: TAP-WIN32 device [saglanvpn] opened:
\\.\{99122DD6-84F9-47DC-92CF-1A9D269BC64C}.tap
Fri Aug 08 08:50:52 2003 5: home.up.bat saglanvpn 1500 1606   init

G:\Communications\OpenVPN>pause
Press any key to continue . . .

G:\Communications\OpenVPN>route add 10.42.20.0 mask 255.255.252.0
192.168.3.2
The route addition failed: Either the interface index is wrong or the
gateway do
es not lie on the same network as the interface. Check the IP Address Table
for
the machine.

Fri Aug 08 08:50:55 2003 6: script failed: system() returned error code 176
Fri Aug 08 08:50:55 2003 7: Exiting

G:\Communications\OpenVPN>

Now, according to the docs, the example home.up file has an environment
variable $5 (which would be %5 on windows). to make sure this was working i
change the $5 to the ip address of 192.168.3.2 and then 192.168.3.3 (they
should be the endpoints of the VPN).
This still didn't work as you can see.

i added a pause to the config file to see what happened.
When this is added, the adapter does come up, as the little red X in the
systray in windows disappears. however, when i do an ipconfig (while the
script is paused) to show what ip address it has, the address is 0.0.0.0
even though i've specified the address and mask in the adapter general tab
in windows.

the tls-home.conf which i edited from the example file is as follows:

#
# Sample OpenVPN configuration file for
# home using SSL/TLS mode and RSA certificates/keys.
#
# '#' or ';' may be used to delimit comments.

# Use a dynamic tun device.
# For Linux 2.2 or non-Linux OSes,
# you may want to use an explicit
# unit number such as "tun1".
# OpenVPN also supports virtual
# ethernet "tap" devices.
#dev tap

# Our OpenVPN peer is the office gateway.
remote (internet accessible ip address at office)

# 10.1.0.2 is our local VPN endpoint (home).
# 10.1.0.1 is our remote VPN endpoint (office).
#ifconfig 10.1.0.2 10.1.0.1
#ifconfig 192.168.3.3 192.168.3.2

# Our up script will establish routes
# once the VPN is alive.
up home.up.bat

# In SSL/TLS key exchange, Office will
# assume server role and Home
# will assume client role.
tls-client

# Certificate Authority file
ca my-ca.crt

# Our certificate/public key
cert home.crt

# Our private key
key home.key

# OpenVPN uses UDP port 5000 by default.
# Each OpenVPN tunnel must use
# a different port number.
# lport or rport can be used
# to denote different ports
# for local and remote.
; port 5000

# Downgrade UID and GID to
# "nobody" after initialization
# for extra security.
; user nobody
; group nobody

# If you built OpenVPN with
# LZO compression, uncomment
# out the following line.
comp-lzo

# Send a UDP ping to remote once
# every 15 seconds to keep
# stateful firewall connection
# alive.  Uncomment this
# out if you are using a stateful
# firewall.
; ping 15

# Uncomment this section for a more reliable detection when a system
# loses its connection.  For example, dial-ups or laptops that
# travel to other locations.
; ping 15
; ping-restart 45
; ping-timer-rem
; persist-tun
; persist-key

# Verbosity level.
# 0 -- quiet except for fatal errors.
# 1 -- mostly quiet, but display non-fatal network errors.
# 3 -- medium output, good for normal operation.
# 9 -- verbose, good for troubleshooting
verb 3

-----------

Any ideas on what i'm doing wrong?

thank you, and sorry for the long email. i hope i've included everything
pertinent.

chris

-- 
The content of this e-mail is confidential, may contain privileged material
and is intended solely for the recipient(s) named above. If you receive this
in error, please notify Software AG immediately and delete this e-mail.

Software AG (UK) Limited
Registered in England & Wales 1310740
Registered Office: Hudson House, Hudson Way,
Pride Park, Derby DE24 8HS

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users