Hey,
Unfortunately, Both me and my friend cannot forward our ports due to ISP restrictions(NAT it forced).
Is there a bypass to make internet play available without forwarding ports(5000/213)?
Many thanks.
You can setup a ssh tunnel and forward the port trough it.
https://www.retrokits.de - blog, retro projects, hdd clicker, diy soundcards etc
https://www.retroianer.de - german retro computer board
matze79 wrote on 2021-11-12, 23:19:You can setup a ssh tunnel and forward the port trough it.
Any guides or walktroughs btw that you can link up?
Thanks in advance!
https://www.retrokits.de - blog, retro projects, hdd clicker, diy soundcards etc
https://www.retroianer.de - german retro computer board
I'm missing something.
For SSH tunneling wouldn't you still have to portforward to an SSH server? Yes it would SSH encrypt your traffic, but you aren't saving anything in terms of complexity.
Second, how can an ISP block portforwarding? That is something that is done on the local side of the network. ISPs don't have control over that. What are they blocking everything to you but port 80 and 443 traffic? What do you mean it's because ISP is forcing NAT? That's how routers work (How else do you think every device on your private local network can share the same public IP?), and the very reason for portforwarding in the first place (You got to tell the incoming traffic, that you are serving, where on your internal network it has to go).
Darklord42 wrote on 2022-02-13, 03:50:Second, how can an ISP block portforwarding? That is something that is done on the local side of the network. ISPs don't have control over that. What are they blocking everything to you but port 80 and 443 traffic? What do you mean it's because ISP is forcing NAT? That's how routers work (How else do you think every device on your private local network can share the same public IP?), and the very reason for portforwarding in the first place (You got to tell the incoming traffic, that you are serving, where on your internal network it has to go).
Not necessarily.
ISPs can block any traffic they want. For example blocking traffic bound for port 25 on customer's connections is extremely common, to prevent compromised machines acting as mail relays.
Many ISPs now don't provide public IPs to their customers due to lack of available IPV4 addresses. Instead they hand out private IPs and perform NAT at their end. This started with mobile devices (phones etc.) and they got away with it, so now it gets done to fixed lines as well. It's horrible for games that rely on P2P, even if they bother to implement methods like STUN.
I see, so you are on a private network, within a private network...that is lousy.
( I keep thinking I shouldn't have given up my original cable internet provider where I had 3 static IPV4 addresses grandfathered, but they pissed me off so bad, 1/3 the paid for speed and frequent drops...... though I wonder now if they were just pissing me off on purpose because they wanted the IPs back 🤣 )
Unicorn herding operations are proceeding, but all the totes of hens teeth and barrels of rocking horse poop give them plenty of hiding spots.
So back to the topic,
In which case the SSH tunnel won't work, because the ISP still has to forward the public SSH traffic to your private network through their NAT, only then can you forward the SSH traffic to your SSH server through your NAT.
Am I getting that right?
