I have connected to my router via l2tp. To that router is connect several switches with adresses in range 192.168.88.1-254.
I set dhcp pool with that l2tp profile to range which switches are configured. But I cant see switches, i cant ping, but tp link easy smart configuration utility cant see them. I have got an 88 address, but I cant see it.
Do you have any idea?
Did you enable proxy-arp on your LAN interface (or bridge) ?
no? Must I?
And where to configure? ON my router where are switches connected?
I often use l2tp and all works just fine
You have to activate on on the router where you establish your L2TP connection under bridge(or LAN_INTERFACE) ==> ARP and then choose proxy-arp in the drop-list
But i have connected to l2tp and have access to the internet. So l2tp is working, just i cant cant access to 88 where are switches
can anyone give me idea what to try?
Someone already has, if your L2TP setup is using the same address space as your LAN then you need to enable proxy ARP. Sadly, enabling proxy ARP isn’t ideal from a security standpoint. I’d recommend looking at moving your L2TP setup to it’s own network. When that is done, normal routing will move packets between the VPN connections and the LAN. That said, if your switch configuration tool requires broadcast that would not work.
Why you need proxy ARP if you want to keep your L2TP setup on the same network as your LAN:
An interface exists on your router for 192.168.88.0/24, that is likely your LAN bridge. All traffic for that network stays contained within that network. Your L2TP client obtains an IP in 192.168.88.0/24 but it is setup as a /32 both for the client side route and the server side interface. This means when routing traffic from the Internet to your VPN user it works without proxy ARP. In the situation of a host on the LAN bridge (192.168.88.0/24) trying to send to a specific /32 within 192.168.88.0/24 (your L2TP client) it never reaches the routing table. The client, say one of your switches, doesn’t send the return packet to default gateway, MikroTik router. Instead, it sends an ARP request for the specific IP used by the L2TP client. Because a broadcast isn’t forwarded past layer 3 boundaries (interfaces) the LAN bridge does not forward the ARP request to through the L2TP server interface onto the L2TP client interface. Therefore the ARP fails and the client, switch, cannot find the MAC address of the L2TP client. What proxy ARP does is tell the router to reply to ARP requests for any IP address in it’s routing table. This means the MikroTik router would now respond to the ARP request from the switch to the L2TP client with it’s MAC address. When the packet arrives it is routed to the most specific entry in the routing table, the /32 entry for the L2TP client.