[SOLVED] OpenVPN brdige, LAN not pingable

@leksey · 2011-11-22 05:21:20

Hi, try to describe situation:
I have local network 192.168.0.0/24
My OpenVPN server 192.168.0.25 (arch)
Default gateway 192.168.0.1, this server has windows NAT and port forwarding tcp and upd 1194 to my OpenVPN.
My openvpn configuration (iptables disabled):

port 1194

proto tcp

dev tap0

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

ifconfig-pool-persist ipp.txt 
server-bridge 192.168.0.1 255.255.255.0 192.168.0.200 192.168.0.240
keepalive 10 120
client-to-client
 
push "route-gateway 192.168.0.1"
push "dhcp-option DOMAIN local.local"
push "dhcp-option DNS 192.168.0.21"

persist-key
persist-tun

max-clients 20
comp-lzo

user nobody
group nobody
status openvpn-status.log
log openvpn.log
verb 6

ifconfig after OpenVPN starts:

br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 metric 1
inet 192.168.0.25 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::da5d:4cff:fe80:def3 prefixlen 64 scopeid 0x20<link>
ether d8:5d:4c:80:de:f3 txqueuelen 0 (Ethernet)
RX packets 59459 bytes 4554908 (4.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14968 bytes 1717243 (1.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 metric 1
ether d8:5d:4c:80:de:f3 txqueuelen 1000 (Ethernet)
RX packets 61481 bytes 6113842 (5.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15331 bytes 1736437 (1.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 base 0xe000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 77 bytes 8624 (8.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 77 bytes 8624 (8.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

my client configuration (winxp):

remote vpn.mydomain.ru 1194
client
dev tap
proto tcp
resolv-retry infinite # this is necessary for DynDNS
nobind
persist-key
persist-tun
ca c:\\keys\\ca.crt
cert c:\\keys\\testxp.crt
key c:\\keys\\testxp.key
comp-lzo
mute 20
redirect-gateway
verb 4

when client connects it get 192.168.0.200 but it can't ping appliences in LAN (192.168.0.0/24)

Last edited by @leksey (2011-11-24 08:28:07)

senorsmile · 2011-11-23 20:49:39

I will let others chime in who know more. I believe you would want to assign a different subnet to your openvpn clients, e.g. 192.168.10.0/24. Then, all clients at 192.168.10.0/24 will be routed via 192.168.0.1 if they're trying to access that subnet. This is how I have done it on other distro's and have never had any problem.

@leksey · 2011-11-24 08:27:43

Thank you for you answer senorsmile!

I am sorry, but a couple of days ago i solved this issue. I found my mistake in bridge conf files. After checking with wiki it was fixed and now it works perfect!

henningphan · 2011-12-10 12:48:49

what was the solution?

@leksey · 2011-12-11 13:21:32

henningphan wrote:

what was the solution?

I followed by article on wiki.archlinux.org, but mistaked when modified bridge settings.
I edited openvpn_tap (/etc/networks.d/openvpn_tap) and instead
INTERFACE='tap0'
I wrote
INTERFACE='tun0'
when i checked it, vpn connection was worked.

Arch Linux

#1 2011-11-22 05:21:20

[SOLVED] OpenVPN brdige, LAN not pingable

#2 2011-11-23 20:49:39

Re: [SOLVED] OpenVPN brdige, LAN not pingable

#3 2011-11-24 08:27:43

Re: [SOLVED] OpenVPN brdige, LAN not pingable

#4 2011-12-10 12:48:49

Re: [SOLVED] OpenVPN brdige, LAN not pingable

#5 2011-12-11 13:21:32

Re: [SOLVED] OpenVPN brdige, LAN not pingable

Board footer