103
submitted 1 year ago* (last edited 1 year ago) by kokesh@lemmy.world to c/selfhosted@lemmy.world

I'm connected via a 4G modem. Got this setup about 3 years ago. In the beginning it was enough to look for the public IP (what's my IP). The modem showed some sort of private ip in the ui. I'm running stuff at home (Homeassistant, Gitea,) and bought a domain and pointed it to my home IP via Cloudflare. After some time I've noticed my modem shows the public IP also internally. For about 2 years now it ran flawlessly, the IP changed from time to time, but not really more than once in several weeks. For about a week all stopped working and the modem shows IP 100.xxxx and outside 85.something I guess I'm behind NAT now. Normal port forwarding on the modem is useless now. Is it possible to open the ports via UPNP? I've tried via miniupnp from my Ubuntu server, but it just throws an error.

upnpc -a ifconfig enp1s0| grep "inet addr" | cut -d : -f 2 | cut -d " " -f 1 22 22 TCP

Can I use this to somehow open the ports via UPNP on my modem and bypass the blocking? I can't even OpenVPN to my modem anymore.

EDIT: i also run AdguardHome, that I use as Private DNS on my Android phone

UPDATE: everything except Adguard Home used as Private DND on my Android works! I've used this: https://github.com/mochman/Bypass_CGNAT/wiki/Oracle-Cloud-(Automatic-Installer-Script) - free Oracle VPS + automated well described script. Even HTTPS works fine!

you are viewing a single comment's thread
view the rest of the comments
[-] clericc@feddit.de 24 points 1 year ago

i've been on CGNAT and just pointed my domain to my ipv6 address with no issues - every isp should hand out huge v6 subnets dedicated to you.

Since my v6 prefix is not stable, i use ddclient from my homeserver to update my domains AAAA record

[-] lemmyvore@feddit.nl 16 points 1 year ago

Unfortunately IPv6 adoption is not universal. There will be parts of the internet that won't be able to reach you at a 6-only address.

[-] kionite231@lemmy.ca 2 points 1 year ago

Yup, my gemini capsule is suffering from it. :(

[-] baldissara@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

I tried that and couldn't make it work. My server was unable to receive any http requests. Then I tried doing some tweaking in my ISP router configuration but with no success. So far cloudflare tunnel was the only solution I found

[-] clericc@feddit.de 1 points 1 year ago

port forwarding in your router properly set up?

[-] baldissara@lemmy.world 1 points 1 year ago

Yeah I set it up to forward 80:80 and 443:443 but it didn't seem to have any effect. Does port forward work on ipv6 the same way it does on ipv4?

[-] clericc@feddit.de 1 points 1 year ago

in m limited sample size of one avm fritz.box, yes. What ivp6 address did you use to try and connect? a device typically has multiple - i.e. dont use fd00::, fe80::

[-] baldissara@lemmy.world 1 points 1 year ago

I'd need to check it out, it's been a while. But I tried pretty much all addresses that are printed out with "ip address" command on linux

[-] EncryptKeeper@lemmy.world 1 points 1 year ago
[-] Still@programming.dev 1 points 1 year ago

wdym except Verizon? I have a whole section of /56 for me in ipv6, tho the Verizon website is ipv4 only

[-] EncryptKeeper@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

Verizon IPv6 rollout technically started but has been very limited in the last few years. I live outside one of the biggest cities in the U.S. and it hasn’t even made it here yet. In the last five years they’ve only made it to 50% of their userbase being capable.

[-] Still@programming.dev 1 points 1 year ago

ah, classic isp dumbassery

this post was submitted on 11 Nov 2023
103 points (92.6% liked)

Selfhosted

40383 readers
557 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