PPTP into a router that uses EoIP to another location

RouterOS General
1

Weird problem here.

I am using EoIP to connect two locations together and that connection is working fine. I can ping poing A from point B and point b from point a.

I have people that pptp into point A and they can reach everything at point A but it can not reach anything at point B. It wont even ping the LAN ip of the router at point B. Also the point B router can not ping the ip address assigned to the pptp connection but the router at point A can.

Summary: EoIP works fine, pptp works fine but once clients connect into the router with pptp they cannot move across the EoIP connection.


Any ideas?

Thanks.

2

I’m not sure if this might be your problem, but it might apply.

Windows PPTP clients to a MikroTik/RoS box use class based netmasks and routes.

Thus, if you PPTP into RoS from a Windows machine, you’ll get a mask/route based on the class of IP assigned to the Windows PC.

So, if the Windows PC is on a 10.x.x.x network, it will get a /8 mask and route.
On a 192.168.x.x it will get a /16, IIRC.

[Most other linux PPTP devices use DHCP to pass a mask and route to the PPTP client, but this isn’t possible with RoS.

Again, I’m not sure if that’s part of the problem or not. But it’s an odd behavior that could impact routing in ways you don’t expect.

-Greg

3

Thanks for the response,

I do not believe that is the problem because the addresses assigned to location B are in the middle of the sub-net at 160 but i can ping things on either side of that IP at location A. so i can ping .254 as well as .5.

I am at a loss of ideas.

4

this problem! Help!

office 1: ping 192.168.0.200-accept, ping 192.168.0.201-192.168.0.249-accept
office 2: ping 192.168.0.254-accept, ping 192.168.0.1-192.168.0.199-accept
office 3: ping 192.168.0.254-accept, ping 192.168.0.1-192.168.0.199-accept
office 3: ping 192.168.0.200-DROP, ping 192.168.0.201-192.168.0.249-DROP

help!

5

solution

add action=masquerade chain=srcnat comment=“eoip via pptp”
disabled=no out-interface=bridge-lan src-address=172.16.23.0/24