I'm probably doing something stupid. Or, Movistar has done something stupid (again) with their (weird, custom) router firmware. I'm hoping someone can tell me which, and what
I have Movistar (Spain)'s fibre based Internet service "Fusión", with a VG-8050 Internet router.
Behind that I have a MikroTik RouterBOARD 951Ui 2HnD.
The MikroTik only has Ether2 connected. I am not using the MikroTik's Ether1 "upstream" port.
The MikroTik's sole job in life is to function as a VPN server.
The LAN IP addressing is 192.168.255.0/26, with the VG-8050 Internet router as 192.168.255.7, a Windows Server 2012R2 at 192.168.255.8 and a variety of other boxes and appliances either statically or DHCP configured within that 192.168.255.0/26 range (DHCP server on the Windows Server).
The MikroTik's Ether2 (which appears as ether2-master-local) has two /IP ADDR configured, as 192.168.255.3/26 and as 192.168.255.125/26.
The MikroTik's default route is 192.168.255.7. No pref-src set.
I've configured both a PPTP VPN and an SSTP VPN. An Internet client (a Windows 10 notebook computer) can connect to both successfully, and can navigate through the MikroTik VPN tunnels to the 192.168.255.0/26 LAN segment.
However, any attempt to navigate through the MikroTik VPN tunnel to the Internet results in all packets being lost.
/TOOL SNIFFER captures show packets arriving through the SSTP or PPTP interface on the MikroTik from the IP address which the MikroTik has assigned to the VPN client (/IP POOL VPNpool1 ranges=192.168.255.80-192.168.255.89) and being sent out the bridge-local interface (presumably down the default route to the VG-8050 at 192.168.255.7) ... and then nothing more is ever heard of those packets.
I'm fairly sure that it's some quirk of the VG-8050 rather than something I've done wrong on the MikroTik, but...
Does anyone see anything that I've done wrong in the MikroTik configuration above?
Or have any other suggestion for fixing why the VPN tunnels seem to work but navigating the Internet through those tunnels does not work?
Oh, bugger. I've probably just proved the theory that it's a problem on the VG-8050: I statically assigned an IP address from that 192.168.255.80-89 range to a notebook computer and cabled it by Ethernet to the internal LAN, and it behaves exactly the same as clients when connected through the VPNs...
Well, still, if anyone's got any sage advice?