OpenVPN @ VM - connected, but unable to view internal networ

YoGi

Hi,
So i managed to roll out with a brand new Debian based OpenVPN server. There are however some issues regarding access to my home network - atm i am unable to either ping or view any website within my network.

My home network goes by 192.168.0.1/32 with router being 192.168.0.1 and vpn server 192.168.0.193. Is there something im missing?

client

proto udp
dev tun
ca ca.crt
dh dh2048.pem
cert yogi.crt
key yogi.key
remote xx.xxx.xxx.xxx 23432
cipher AES-256-CBC
verb 2
mute 20
keepalive 10 120
comp-lzo
persist-key
persist-tun
float
resolv-retry infinite
nobind

Server

port 23432
proto udp
dev tun0
ca keys/openvpn-test/ca.crt
cert keys/openvpn-test/server.crt
key keys/openvpn-test/server.key
dh keys/openvpn-test/dh2048.pem
server 10.8.3.0 255.255.255.0
crl-verify keys/openvpn-test/crl.pem
cipher AES-256-CBC
user root
group root
status servers/serwer-testowy/logs/openvpn-status.log
log-append servers/serwer-testowy/logs/openvpn.log
verb 2
mute 20
max-clients 2
keepalive 10 120
client-config-dir /etc/openvpn/servers/serwer-testowy/ccd
tls-server
comp-lzo
persist-key
persist-tun
ccd-exclusive
mode server
push "route 10.8.3.0 255.255.255.0"
push "dhcp-option DNS 192.168.0.1"

routing

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
10.8.3.0        10.8.3.2        255.255.255.0   UG    0      0        0 tun0
10.8.3.2        *               255.255.255.255 UH    0      0        0 tun0
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0

YoGi

since i cant edit 1st post anymore ill just mention that i have deleted whole iptables rules but still it didnt help 🙁

YoGi

tnx debbie for a response but the network I am connecting FROM goes by 192.168.120.1 which should not create any sort of problems
i did see a note tho:

Wed Jun 4 08:23:51 2014 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Wed Jun 4 08:23:51 2014 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

In advance i also enabled ip forwarding.
Now i can ping only vpn ip by 10.8.3.2 and it doesnt let me past this point, which gets me thinking if perhaps i am missing a proper routing since vpn server does exist in both 10.8.3.0/24 and 192.168.0./24 and i can also ping either machines connected via vpn and home router itself
any thoughs ?
I have a crappy D-Link router that doesnt allow me to play with routing tables properly (for some reason it only let me route WAN interface but as far as I know its firmware related issue). Had to force it with a little help of some 3rd party firefox extensions :>. Still no effect 🙁

YoGi

ok i solved it 🙂
as i though my problem indeed was within my routing table @ vpn server.

root@yogi-vpn:/home/yogi# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
10.8.3.0        10.8.3.2        255.255.255.0   UG    0      0        0 tun0
10.8.3.2        *               255.255.255.255 UH    0      0        0 tun0
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0

after adding that last line it all worked just fine 😉