14
port opening with ipv6 host exposure (lemmy.ml)
submitted 3 weeks ago* (last edited 3 weeks ago) by GravitySpoiled@lemmy.ml to c/selfhosted@lemmy.world
13 comments fedilink hide all child comments

I moved, and now my new router has no ipv4. I can expose the host with ipv6. After opening a port and exposing the host, the host is fully exposed and all ports are open. It'ss weird. Vodafone calls ut host exposure, I can select a specific port and all ports are open.

How do you guys corcumvent that issue? Is this the infamous cgnat problem or is this why many people use a cloudflare tunnel? I just want to reach my nextcloud and immich with a normal domain.

Edit: I called my provider and now I've got an ipv4 address with port forwarding

you are viewing a single comment's thread
view the rest of the comments
[-] ShortN0te@lemmy.ml 2 points 3 weeks ago

Because in the local/private network are many hosts, like your phone, pc and your server. Exposing means that the device that is exposed gets basically everything forwarded what usually the router would handle. Exposing does expose a host to the WAN.

Forwarding a Port only forwards the specified ports. You can use multiple hosts for that. For example you can port forward port 80 to your Phone to port 321 or whatever and port 443 to your server at port 20.

[-] GravitySpoiled@lemmy.ml 2 points 3 weeks ago

My router has a setting to expose the host X with port X. The port does nothing. That's the weird part.

[-] ShortN0te@lemmy.ml 1 points 3 weeks ago

So for port forwarding you need the port on the router the host and the port the traffic should get forwarded to on the selected host.

So you are saying, when exposing a host then the host is reachable over internet but when using port forwarding it is not?

How you check this? What commands/procedure?

this post was submitted on 29 Nov 2024
14 points (93.8% liked)

Selfhosted

40717 readers
368 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:

  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!

founded 2 years ago
MODERATORS
ruud@lemmy.world
CannaVet@lemmy.world
Loki@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz