Selfhosted

60281 readers

597 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

(SOLVED) Is it normal that browsing to my own WAN-IP shows my Omada controller interface? (slrpnk.net)

submitted 2 years ago* (last edited 2 years ago) by Sunny@slrpnk.net to c/selfhosted@lemmy.world

18 comments fedilink hide all child comments

Hi there, been working on my selfhosted setup a bit lately and just noticed that if I browse to my own WAN-IP it will show to the public the interfance of my oc200 omada hardware controller. While it does have a login form with username password, id be much more confident if this wasnt public at all. I've looked online and in my settings but struggle to find anything related to this. Is it common that this is on be default?

Any pointers greatly appriciated.

Edit: Solved - I panicked without thinking I was on my own lan when checking this..

you are viewing a single comment's thread
view the rest of the comments

[–] Agility0971@lemmy.world 0 points 2 years ago (2 children)

Wait what?

[–] anamethatisnt@lemmy.world 15 points 2 years ago

Hairpin NAT/NAT Reflection can make the experience of visiting the WAN IP from the LAN a different one then if you do it from somewhere else. Or what is your what?

[–] Fuck_u_spez_@sh.itjust.works 1 points 2 years ago* (last edited 2 years ago)

NAT loopback, if supported and enabled, may appear to bypass firewall rules.

Basically, traffic to your public (WAN) IP that comes from inside the network is not subject to the same level of security as outside traffic would be. The last part of the parent comment didn't quite make sense, though.