so as far as I can tell, the issue is that when a local device tries to send something to the network's WAN IP, NAT rules just don't apply to it for some reason I don't fully understand. so you have to manually add a rule that says "any traffic from a LAN device to another LAN device should be masqueraded" and once you have that the normal NAT rules for forwarding traffic to specific devices work fine. I suddenly feel like I have a lot more to learn about this
WAIT I GET IT if you're in the local network and you send a request to your public IP the router will send the request on to the internet but it won't receive its own request so it never gets an answer. so you use a hairpin NAT rule to say "if a LAN device makes a request against our WAN IP, pretend it came from the WAN interface and handle it normally"
*Due to increased bot signup, manual approval is required. Please write some applicable request text on signup with why you want to join. Blank submissions will be denied.*
This Mastodon instance is for tech workers, academics, students, and others interested in tech who are LGBTQIA+ or Allies.
We have a code of conduct that we adhere to. We try to be proactive in handling moderation, and respond to reports.
We're not a free speech absolutist. We're not interested in Nazis, TERFS, or hate speech. No homophobia, transphobia, queerphobia, racism allowed.
This instance is meant to be a friendly, welcoming space to all who are willing to reciprocate in helping to create that environment.
If you’re ever unsure, ask first. Use CWs where required.
If you’re accused of causing harm, either take some responsibility or ask moderators for help.
Our moderators are here to listen and respond to reports.
This instance is funded in part by Patreon donations.