main 192.168.88.1 acts as DHCP server, LTE (backup) connection holder and main gatewat for network
192.168.88.101 - configured as switch with turned off firewall. Connected to 88.1 throu ruckus wifi bridge/ Dhcp server for static clients
192.168.88.100 - acts as a internet gate.with one L2tp ipsec connection as a client for special sites. Connects by wire to 192.168.88.101
issue - often i cant ping 192.168.88.100 and 192.168.88.101 from my windows machine. But from Mikrotik 192.168.88.1 - everything fine.
even when i connect throu VPN (to 192.168.88.100) - all 2 mikrotik pinging.
When i ping 192.168.88.100 from windows computer connected by wifi to 192.168.88.1 - no answer from host
but when i trace to www.google.com - 1 step is 192.168.88.1 and second - 192.168.88.100.
Internet working fine.
But it’s not convinient setup routers from outside VPN connection
Physical connection (ruckus wireless, ethernet cable) is one thing.
192.168.88.0/24 probably is defined as just one (1) subnet This means that everything must be bridged together. (L2 connection)
Having an ethernet cable between 101 and 100 does not define a bridged connection, if the wireless and the ethernet are not on the same bridge in 192.168.88.101
And yes the IP routing (L3) goes from 192.168.88.1 directly to 192.168.88.101.(there is no routing hop in the 192.168.88.101), its one subnet.
Your PC may not be able to find the MAC address through ARP of the 192.168.88.101 (same subnet , direct connection) if it is not all one L2 net.
The ruckus bridge might also be a “pseudo bridge in MKT definition” replacing MAC addresses by its own MAC address.
Adding proxy-arp (poor mans routing) may be a workaround, but it is somewhat fixing a faulty network design.
Check ARP tables.
Thank you for the answer.
on the 192.168.88.1 - all pings works to any computers or routers.
but connected to mikrotik by wifi computers - not.
arp -a doesn’t show 192.168.88.100 on computer
on 192.168.88.100 and 192.168.88.101 - shown mac and ip on arp table correctly
try: on 192.168.88.1 WLAN set ARP to “proxy-arp” (If WLAN is connected to a bridge, then “proxy-arp” is to be set on the bridge.
try: on 192.168.88.1 WLAN set ARP to “local-proxy-arp” (If WLAN is connected to a bridge, then “local-proxy-arp” is to be set on the bridge.