Crumb
c/mikrotik · by WeAreAllOne@lemmy.dbzer0.com · 1y

Back to home connectivity issue

Hey all, so I am trying to figure out, why I can't connect remotely to my router using Back to Home in some cases. I can connect from my mobile, but I can't connect using my laptop via Ethernet cable not via some wifi connections. I've found a wifi connection that works but not on others. What might be the issue here ?

8 points · 4 comments · view on lemmy.world

4 Comments

sylver_dragon@lemmy.world · 2 pts · 1y (1 reply)

I'd guess it's one of two possible issues:

  1. Ports blocked by the network provider. Some networks will block outbound connections on all ports and then explicitly allow some of the common ports (e.g. 80, 443). Some will also allow slightly less common ports for corporate VPN connections (e.g. 500 and 4500 for L2TP). Based on the documentation for Back to Home, it looks like it uses WireGuard underneath. For MikroTik, that uses a default port of 13231 (source). If that port is blocked, outbound by a network provider, the tunnel would fail.
  2. Its always DNS. Based on the documentation Back to Home relies on a Dymanic DNS (DDNS) service. Some networks may specifically block DNS queries for well known DDNS services as a security measure. DDNS services were really popular with malware creators for a while and so DDNS services became a casualty of security configurations.
WeAreAllOne@lemmy.dbzer0.com · 1 pts · 1y

Hmm can't be neither. My mobile works in networks where my laptop via Ethernet does not. But so far my laptop via WiFi only works on a specific network and not on others. I need some more tests and I also might try what the other user below said that I might try adding different shares for laptop and mobile phone.

sylver_dragon@lemmy.world · 2 pts · 1y
[ removed ]
walden@sub.wetshaving.social · 1 pts · 1y (1 reply)

A while ago I decided that BTH only works well for 1 device (using wireguard at least) at a time.

I messed around and made different profiles (not sure of the actual name) for each device and that solved my problems.

Worth a shot.

WeAreAllOne@lemmy.dbzer0.com · 2 pts · 1y

Yeah I might try this too. But in any case I don't use the same share simultaneously. Will look into it.