Routing openvpn client to "main" network

[tomgregory87]

Apologies if this has been covered elsewhere...

I've got openvpn set up and connecting quite happily. It's assigning an IP on the 192.168.2.0 network, but I would like it to be able to access a NAS on the 192.168.1.0 network. I've got more or less no idea what I'm doing, but wonder if it can be done with a static route. Anyone got any suggestions?

I'm running the 3.0.0.4.270.24 Merlin build on an RT-N66U.

Thanks!

 

[RMerlin]

Apologies if this has been covered elsewhere...

I've got openvpn set up and connecting quite happily. It's assigning an IP on the 192.168.2.0 network, but I would like it to be able to access a NAS on the 192.168.1.0 network. I've got more or less no idea what I'm doing, but wonder if it can be done with a static route. Anyone got any suggestions?

I'm running the 3.0.0.4.270.24 Merlin build on an RT-N66U.

Thanks!

The Windows client will automatically establish static routes for you when you connect (that's the reason why you have to run the client with elevated privileges). Just make sure you have "Push LAN to clients" enabled on the OpeNVPN server.

 

[tomgregory87]

Thanks for that, didn't realise it was quite so easy!

 

[RMerlin]

Thanks for that, didn't realise it was quite so easy!

One of the numerous reasons why I prefer OpenVPN over PPTP.

 

[tomgregory87]

Is there any way (as far as you know) to allow DLNA over tun? I have to use tun as Android doesn't support tap interfaces. I'm not convinced there is as DLNA relies on broadcast which tun wouldn't forward (I think).

 

[RMerlin]

Is there any way (as far as you know) to allow DLNA over tun? I have to use tun as Android doesn't support tap interfaces. I'm not convinced there is as DLNA relies on broadcast which tun wouldn't forward (I think).

DLNA relies on broadcasts indeed, so it won't work over a TUN interface.

For remote media access, AiCloud is your best bet at the moment.