I’m working on a good work-flow for connecting to routers remotely using BTH. I think allowing neighbor discovery would be easiest so I don’t have to check the IP for each connection each time. Can neighbor discovery work over a BTH connection?
I have tested some discovery settings on the router in question, but without success. When connected to BTH, my neighbor list does not show the router I’m connecting to over BTH.
Thank you.
Neighbor discovery works on Layer 2. BTH is Layer 3. So no, it won’t work.
Thank you. I knew LLDP was L2, but somehow I thought MNDP was L3. I appreciate the response.
Nope. Some people go to great lengths to use discovery/romon over wireguard. It's doable with some sort of added L2 tunneling like eoip or l2tp, but so not worth it.
I think the l2 management things are mostly a way to avoid having to use a serial console. But once a proper ip setup is reached, there is no point to it. When you use wireguard, it's mostly inevitable that you already have a solid l3 configuration...
I was looking to solve a problem that doesn’t exist. I wanted to be able to quickly see an existing available RouterBOARD connected through BTH connections on my laptop. I thought that each BTH connection would have a different IP range.
It turns out, the BTH configuration does not choose a random address range for BTH, it uses 192.168.216.0/24 every time, with the router taking 192.168.216.1. So, when you connect to a different BTH router, the address is always 192.168.216.1.
I could see this being an issue with multiple BTH connections when trying to support customers, and ending up connected to the wrong router. I have to think about a good procedure for connecting and supporting these devices.
It's always the same. In most case, you can still use interface routing or adjust metrics locally if you made two connections. And, while I've never tried, and not 100% it work... but you might be able to use a firewall NAT netmap on the router to re-number BTH range if this was a recurring thing.
Overall, BTH is does not offer more "pro" features, which is annoying and limiting. I'd like the "proxy" to be an option on normal WG, verse this all-in-one things in /ip/cloud.
And on original topic, an EoIP client for desktops would be nice, then you can wire up EoIP over WG to get local discovery. See EoIP client for Windows from 2007 so I'm not hopeful. And while "MNDP" is L3, it uses UDP broadcast packets which are not carried by WG.
Actually, the matching BTH IP situation just showed up for me as a possible issue. I was connecting to the remote office BTH for testing, and logged into that router. When I disconnected the BTH/wireguard link, Winbox automatically re-logged into the local office BTH router (since the IP addresses match, and the tests have matching credentials).
I suppose the current solution would be to save multiple connections that use the local IP of the router instead of the BTH IP of the router.