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…

26 points

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.

permalink
report
reply
11 points

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.

permalink
report
parent
reply
0 points

Wait what?

permalink
report
parent
reply
15 points

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?

permalink
report
parent
reply
1 point
*

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.

permalink
report
parent
reply
16 points

I know you solved it but for anyone that finds this later this feature/behavior is typically called “NAT Hairpin” in case you are looking for a setting to enable or disable, hope this helps!

permalink
report
reply
5 points

In pfSense land it’s called nat reflection. I believe it’s off by default on pfSense, but it makes accessing your own stuff “externally” while inside the network a pain so I’d imagine most devices have it enabled by default.

permalink
report
parent
reply
1 point

Thanks!

permalink
report
parent
reply
1 point
Deleted by creator
permalink
report
parent
reply
1 point

Yeah, I’ve never fixed this issue with my fritz.box, only thing that helps is calling up my DynDNS URL. Is there a better way?

permalink
report
parent
reply
5 points

Can you access your wan ip when you are somewhere else than on your own lan?

If not, then this is probably just that your router does firewalling and nat is such order that you can access admin interface from local network via wan address.

If yes, then router has some serious misconfiguration.

permalink
report
reply
3 points

Yeah exactly what happened, i was on my lan thinking WAN IP meant it was public - it was not :P

permalink
report
parent
reply
4 points

Are you browsing from outside your local network?

permalink
report
reply
3 points

No I wasnt… just realised this, thats a great relief really. Was afraid it had been publicly available all this time.

Learn something new every day :)

permalink
report
parent
reply
4 points

It’s worth checking from an external network anyway, but I’d be surprised if it was public facing.

permalink
report
parent
reply
3 points

Do you see that only when you’re on the LAN or also when you’re coming in from WAN?

permalink
report
reply
3 points

Ah yeah you’re right, i can only access this interface if I am on my LAN. Tried with hotspot now and it doesn’t “load” - so thats good.

permalink
report
parent
reply
2 points

My opnSense box does the same thing. I’d rather get to it via internal IP like pfSense worked. (I assume I can make that happen somehow, but I haven’t researched it yet.)

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

Community stats

  • 4.9K

    Monthly active users

  • 3.7K

    Posts

  • 80K

    Comments