Selfhosted

40677 readers

602 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

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

submitted 1 week ago* (last edited 1 week 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

[–] anamethatisnt@lemmy.world 26 points 1 week ago (2 children)

First off, check that it is also true when using a device outside the LAN. Easiest would be to check with your phone with wifi off. You probably won't get to the login.
If you do then it's time to check firewall settings.

[–] Sunny@slrpnk.net 11 points 1 week ago

Yeah ur right, i was on my LAN and thats why it worked. I only assumed because I was accessing it via my WAN IP it was 'automatically' public.

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

Wait what?

[–] anamethatisnt@lemmy.world 15 points 1 week 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 1 week ago* (last edited 6 days 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.