I have my next task, setting up a OpenVPN link to my job from my x86 RouterOS box. Currently, the box has a DHCP lease to my Comcast cable modem (public), and a DHCP-Server on my lan side (local) I also have a simple PPTP server biridged to my local side (wan)
Public (ether2): Comcast DHCP-Client lease
Local (ether1): 172.16.11.1
I can create a opvpn interface to my job, and work with it from the Winbox terminal and it seems ok I have been unsuccessful in routeing it to my local side.
When my openvpn interface connects to my job, I receive a dynamic address of 172.16.254.10 with a network of 172.16.254.1
I have figured it out. Yes by IP…
My X86 RouterOS box is currently configured pretty simple for home experimental/training use. As I stated earlier, simple in/out and an additional PPTP interface bridged to a DHCP server for me to access remotely. I use a local ip range of 172.16.11.0/24. My router has been functioning great but I needed to access my companies network via an OpenVPN server. After banging around trying this and trying that, the solution to my OpenVPN problem turned out to be pretty simple.
Masquerade the OpenVPN port with a src-nat firewall entry -
/ip firewall nat
add action=masquerade chain=srcnat comment=“” disabled=no out-interface=ovpn-nwa src-address=172.16.11.0/24
This might sound like a stupid question, but WHY does it require a username?
I do not have any username/password settings on my openvpn server.
Use certificates only.
Hi ;
the case is strange .
he need to connect to VPN server at work .
so the MT not involve in the case here .
he just need to do VPN connection setting on his pc to connect to that VPN server at work .
the only thing he should check is the MT not blocking the pptp connections .
with best regards .