Host at home with a Hairpin NAT

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

Spent 5 hours trying to figure out why it's not working for me, and with your video fixed it in 5 minutes. Thank you!

Bang-Smash
Автор

Hah! I recently discovered this term when facing the same issue on an Eero wifi router. They only recently added support for hairpin NAT. Never thought it was a special feature since it works by default on most generic consumer routers (Asus, Linksys, etc).

Blocked 22 is a blessing. Running on 2222 avoids 99% of the sshd log spam.

SebastiaanDeckers
Автор

New routerOS 6.48 breaks my hairpin NAT. My mikrotik local IP web interface, now redirects to my webserver ddns. Cracking my head what cause the request redirect to port 80 on different box. I endup downgrade the routeros and restore my old config.

And also, NAT didnt work with Dst. Address List set to WAN IP, which i used to doi it to portfoward all my services.

AlifAmzariAzamee
Автор

I never had problems accessing my web server from my internal Network when I was on Charter Business Spectrum cable however today I switched over to Frontier gigabit fiber and now my websites take too long to respond. Sometimes I can see two of my eight websites but it's not always the same too it seems to rotate randomly. Sometimes I can't see any of my websites. I can only see them if I use a 4G cellular network outside the land. I have a Linksys wrt 3200acm router. Not sure how to fix this problem.

basspig
Автор

So we could also modify our host files on every machine we want to access the services if I understand correctly. Or run a DNS server that will resolve that address for us locally.

brakahiphop
Автор

Mmm... Do you know that the IP Cloud host doesn't change? And you published it here... 😂

geogmz
Автор

I don't understand a word you're saying. If I did I probably wouldn't need to watch this.

lazzer
join shbcf.ru