On Wednesday 02 May 2007 14:55, you wrote:
> Hi,
>
> Thanks for the response, the issue is that windows doesn't support TUN
> devices, so your configuration for them MUST be different, can you post it
> here? (the server.conf and client.conf - remove any secret things :) )
The OpenVPN installation package for Windows installs a device called "TAP" -
and it works fine doing tunnelling. I use OpenVPN that way, and I have
clients both on Linux and Windows and we all use the exact same config file:
client
dev tun
proto udp
remote <vpn server IP> <vpn server port>
resolv-retry infinite
nobind
user nobody
group nobody
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
tls-auth ta.key 1
ns-cert-type server
cipher <my cypher>
comp-lzo
verb 4
mute 20
up /etc/openvpn/vpn_up.sh
down /etc/openvpn/vpn_down.sh
(Some details where removed to protect the innocent, the "user"/"group"
directives will issue a warning on Windows clients that they are not
supported (but it works anyways, so I see no reason not to use it globally),
and the "up"/"down" directives are the one that I added personally, those are
very simple script that change my resolv.conf to the intranet's domain search
list and nameservers after connection, and reverts back to ISP's when I shut
down the connection).
-- Shimi
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
