Content
@
0 reply
0 recast
0 reaction
Greg
@greg
dappnode networking question: - I can ssh into the local IP when connected to my home wifi - I can access my.dappnode when connected to external wifi with wireguard enabled - I cannot ssh into the local IP when connected to external wifi with wireguard enabled why? do i need to forward port 22? is that safe?
7 replies
19 recasts
605 reactions
Sileo
@sileo.eth
To answer the initial question (not discussing Tailscale atm), yes you'd have to forward port 22. I recommend using public key authentication and disabling pw auth. Installing fail2ban is also recommended. Additionally, there's a possibility to whitelist specific IPs if you wish.
0 reply
0 recast
0 reaction
Eddy Lazzarin π
@eddy
I never quite trust port forwarding. Tailscale solves this beautifully β install via ssh locally and then you can tunnel in through Tailscale anywhere. Creates a virtual LAN for all your devices regardless of physical network.
2 replies
0 recast
3 reactions
pugson
@pugson
jfc greg install tailscale and stop asking questions
1 reply
0 recast
2 reactions
Leeward Bound
@leewardbound
i don't use dappnode but it sounds like you need to ssh to the wg ip (or dappnode.local, not the local ip? the local ip should only work w/in your home wifi, wg (probably) has its own subnet and distinct ip address - try to ping dappnode.local (or dig cli) from external wifi to see what ip the dns name is resolving to
1 reply
0 recast
0 reaction
Marc Zeller
@lemiscate
I use tailscale with my machines makes things easier while keeping a bit of safety. But even with ssh enabled fail2ban and keys policy will be strong enough imho
0 reply
0 recast
1 reaction
Yusuff
@hysolac
$FCKN cool
0 reply
0 recast
0 reaction
Dulng
@duongvu999
May all your dreams come true today. Have a fantastic day!
0 reply
0 recast
0 reaction
