44
Port Forwarding Alternative?
(lemm.ee)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Nov 2023
44 points (100.0% liked)
Selfhosted
39948 readers
298 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 1 year ago
MODERATORS
What you could do, is set your phone with a temporary static IP (like, manually set on the device if the router doesn't have static leases). Then port forward to your phone as you would for the server. Then, set the phone back to DHCP, and set the server as the same static IP you used.
Assuming the router isn't smart enough to try to follow your phone's IP, you'll effectively have forwarded for the server.
It may also do it based on DHCP provided names, rather than WiFi names. In that case, you should make sure the server uses DHCP and advertises a valid name. If it's already got a static IP, that would explain why it doesn't show up on the UI.