OpenVPN Support Forum

Hallo.
Have a little issue with localnet game servers and openvpn.

When openvpn is connect any localnet clients (CS, Call of Duty, WC3 and all others) do not see localnet game servers. For example, server 192.168.0.7, client 192.168.0.2.
Its strange because server 192.168.0.7 is reachable (ping is ok, see share folders).
Changing default route 0.0.0.0 to local gateway didnt get any results.

Thanks.

hi there,

please give us details of your setup,config files..


Michael.

I think problem with broadcast after VPN connection.
topic7319.html

Anyway, server-config:
------------
dev tun0
port 5190
proto udp
server 20.8.1.0 255.255.255.0

ca /opt/etc/openvpn/keys/ca.crt
cert /opt/etc/openvpn/keys/server.crt
key /opt/etc/openvpn/keys/server.key
dh /opt/etc/openvpn/keys/dh1024.pem

client-to-client
keepalive 10 120
max-clients 22
verb 3

status /opt/var/log/openvpn/openvpn_status.log
log-append /opt/var/log/openvpn/openvpn_log.log
------------

client-config:
------------
client
dev tun
proto udp
remote mydomain 5190
nobind
redirect-gateway

ca ca.crt
cert key01.crt
key key01.key

verb 3
mute 20
------------

hi there,


>I think problem with broadcast after VPN connection.

if you want your clients to connect to a server inside your local lan
over the vpn tunnel and your games use broadcasts then you must
use bridging not routing (tap instead of tun).

Michael.

No.
Question was: "Why after initiate VPN connection my localnet users cant see localnet game-servers?"

1. In CounterStrike I see LAN servers
2. Connect OpenVPN
3. Servers is gone
4. Disconnect OpenVPN
5. I see servers.

Wireshark give me some packets when CS trying to find LAN servers:
source 192.168.0.2
dest 255.255.255.255
src port: 63616 (i think is dynamic)
dst port: 27015
protocol: UDP

Why OpenVPN lock LAN-broadcast on client after connection?

if i understand correct you say:

you have lets say 5 pcs on a lan
they play a game,
everything working ok

one of the pcs starts openvpn with the config posted
then games stop working..?

Michael.

Why OpenVPN lock LAN-broadcast on client after connection?

because your client config is using This tends to redirect all traffic via the VPN; try disabling this comment or add to your client configuration.

ArthurX wrote:Hallo.
Have a little issue with localnet game servers and openvpn.

When openvpn is connect any localnet clients (CS, Call of Duty, WC3 and all others) do not see localnet game servers. For example, server 192.168.0.7, client 192.168.0.2.
Its strange because server 192.168.0.7 is reachable (ping is ok, see share folders).
Changing default route 0.0.0.0 to local gateway didnt get any results.

Thanks.

2nd time.
After connect OpenVPN LAN server 192.168.0.7 is reachable (ping is ok, see share folders), and other LAN PCs reachable.

route add 192.168.0.0 mask 255.255.255.0 192.168.0.1
or
route add 0.0.0.0 mask 0.0.0.0 192.168.0.1
didnt get any any results.
Removing "redirect-gateway" from config also didnt get any any results.

Michael, game didnt stop, on clients pcs where openvpn is connected just disappear LAN servers list. If we try to connect to game server by console command like "connect 192.168.0.7:27015" its works, but most users are lamers and they just see servers in list and connect to any they want.
As I spoke, its problem with broadcast, but why?

Sorry guys.
Now I testing without RUNPAD SHELL, and gameservers in LAN-list find correct.
Problem with RUNPAD SHELL.

Sorry another time.
Its not RUNPAD SHELL.


Red color its now, blue its I want to be.


Why LAN-clients listen broadcast over tun, but not over ethernet interface?

update.
Ok, I find something.
route print:
255.255.255.255 255.255.255.255 20.8.1.10 20.8.1.10 1
255.255.255.255 255.255.255.255 192.168.0.7 192.168.0.7 1

If metrics equal Windows will choose first line 20.8.1.10.
How to replace 20.8.1.10 and 192.168.0.7, or change metric bigger for 20.8.1.10?

I solve this problem.
Changing address 20.*.*.* to 196.*.*.* will automatic replace 192.168.0.7 and 196.8.1.10 in routing table.

255.255.255.255 255.255.255.255 192.168.0.7 192.168.0.7 1
255.255.255.255 255.255.255.255 196.8.1.10 196.8.1.10 1

Because octet 196 is larger then 192.
And everything work properly.

Woo Hoo!
Thanks.

great to hear that it is working; on a side-note, you can specify the metric used for VPN routes using