Set 1 disk-file-count=5 disk-file-name=disk2/log disk-lines-per-file=4096Īdd comment=defconf interface=bridge list=LANĪdd comment=defconf interface=ether1 list=WANĪdd allowed-address=10.255.255.2/32,192.168.90.0/24 comment=\ I think they are correct yet it doesn't work.Ĭonfig files (redacted to hide all public and secret stuff)Ĭode: Select all # jan/31/2022 20:38:55 by RouterOS 7.1.1Īdd admin-mac= auto-mac=no comment=defconf name=bridgeĪdd listen-port=19685 mtu=1450 name=wireguardĪdd name=dhcp ranges=192.168.2.100-192.168.2.254Īdd address-pool=dhcp interface=bridge name=defconf The only thing which "should" be there are the allowed addresses in the peer settings and some routing rules, as far as I understood. searched loads of relevant posts and solutions here. So the tunnel works but I can not get behind the router onto the LAN.Īnd that's where I am lost. When I am in France and want to access NAS on 192.168.2.15 -> timeout.īut ping / Winbox from 10.255.255.1 or. When I'm home and want to ping 192.168.88.1 -> timeout. The problem starts once I want to access device behind the router or use the normal LAN IP addresses. Wireguard between Hex and SXT works when using WG IP adresses. Serving 2 APs (cAP AC and cAP Lite, both also 7.2rc3) Some remote WG devices like laptop and phone, they can connect without any problem to local LAN (not on diagram). Hex 7.1.1, sitting behind ISP modem with dynamic IP (though in the past I have NEVER seen it change, I consider it dynamic to be safe), port forwarding for Wireguard from ISP to Hex. To be able to connect two sites through wireguard, both LAN environments need to be accessible from 'the other side'. Home Hex to SXT - Cisco network diagram.jpeg
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |