OpenVPN Client Routing

Hi All,

I am very new to Mikrotik and have a RB2001UiAS-2HnD with an interface that is successfully connected to my OpenVPN server (thanks to google search results J ). However one thing I can not understand is how to route certain traffic over that vpn.

If I wanted to say any traffic from my LAN to 8.8.8.8 needs to be route over the VPN interface (for example). How would I go about configuring that through the Webfib interaface?

Any help would be much appreciated!

Thanks in advance!

JA

To Add…

I have a route that says:

Destination: 8.8.8.8
Gateway: VPN Interface

Pinging 8.8.8.8 get timeouts

More to add…

The OpenVPN pushes out an address 10.222.222.X and the Mikrotik router received 10.222.222.8 however despite this I still can not ping 10.222.222.1 which is the OpenVPN Server. I know this is pingable.

Any ideas greatly appreciated.

Use gateway 10.222.222.1 for your route.

Also it’s likely that you’ll have to add masquerade rule for traffic going out via VPN interface. Either that, or you’d need to configure VPN server to know route to your client LAN.

Non-pingable server address, if you know for sure that it’s not blocked, is strange. Can you try the other way, ping client from server? To make sure that tunnel really works.

Hi Sob,

Thanks for the reply… I am finding it really odd. The VPN is up but every so often it drops and reconnects I am assuming that because there is no traffic passing.

The VPN is up. I get the address 10.222.222.8 there is a route automatically added for 10.222.222.0/24 via that VPN interface but I still cant ping 10.222.222.1.

I have viscosity on my Mac and when I connect there I can ping 10.222.222.1 just fine.

I am sure its something I have done, I am new to Mikrotik been a SonicWALL (not too sure if I am allowed say that dirty word on this forum) user for years but as the world of Mikrotik is unknown to me.

That being said:

  • The VPN is up
  • The route is automatically added for the 10.222.222.0/24 network

I don’t know, if ping works from other client, it should also work from router. Try to use Tools->Torch on VPN interface, maybe you’ll see something interesting…