Portfowarding help

[Beep Boop]

Hey guys, just trying to forward some of my ports to play 7 Days To Die with my buddies and i'm having issues and some general confusion. These are the ports that the game says it needs.

 

https://i.imgur.com/xVNvZxU.png

 

4 sets of ports and I forwarded them all just to be safe and my buddies are still unable to connect. Here is a pic of my forwarded ports and a part of the confusion is the "server ip address" box.

 

https://i.imgur.com/qwjUMmO.png

 

It's auto filled with "192.168.1." which is obviously the address to access my router. I tried putting in the address I found when I goto whatsmyip.com and it came up with errors. Any help would be amazing guys.

[Beep Boop]

Update, I did "ipconfig" in the cmd and found my local address and inputted that. Will let you guys know if that worked.

 

That didn't end up working...

[elpiop]

Yes, you should forward the "IPv4 Address" from ipconfig. Then give your friends your public ip from whatismyip.com and have them connect to that 

[Beep Boop]

Yeah. I have done that, and i'm just super confused because he can see the server and everything, just can't connect.

 

 

Also i'm confused about my router cause there is no straight up "Port Forward" tab and I dunno if i'm inputting these ports in the right area. I put the ports in both "virtual servers" and "Port Triggering"

[Beep Boop]

Ya, i'm just so confused on what's the deal. I feel like I have forwarded the ports properly.

[Beep Boop]

I ended up testing these ports on canyouseeme.org and it says the connection timed out and didn't work. I don't know what i'm doing wrong really.

 

 

 

Like I said before, I can't find anything specifically called "Port Forwarding" but these looked like the closest two where you input ports to open

 

 

[elpiop]

Maybe try removing the duplicate entries on the Virtual Server setup, keep on the one with your computers private ip

[Beep Boop]

Ok

[LogicalDrm]

-> Moved to Netwoprking

 

PS. Bumping is only allowed once per 24h.

[beersykins]

I'd get rid of the 192.168.1.0 rules in your virtual server setup, you need the internal IP of the hosting computer for that such as 192.168.1.4.

 

You generally can't forward the same inbound port to two different destinations.

 

Port triggering doesn't really apply to a server environment, that will dynamically allocate permits for connections you initiate out from your LAN so that new sessions will be permitted inbound from that destination.  Not really what you want.

 

You'll also likely need to permit via a software layer firewall on the hosting PC whether it is iptables on Linux, Windows Firewall or similar.

[Beep Boop]

On 3/15/2020 at 4:00 AM, LogicalDrm said:

-> Moved to Netwoprking

 

PS. Bumping is only allowed once per 24h.

Thank you sir!

 

On 3/15/2020 at 4:12 AM, beersykins said:

I'd get rid of the 192.168.1.0 rules in your virtual server setup, you need the internal IP of the hosting computer for that such as 192.168.1.4.

 

You generally can't forward the same inbound port to two different destinations.

 

Port triggering doesn't really apply to a server environment, that will dynamically allocate permits for connections you initiate out from your LAN so that new sessions will be permitted inbound from that destination.  Not really what you want.

 

You'll also likely need to permit via a software layer firewall on the hosting PC whether it is iptables on Linux, Windows Firewall or similar.

Ok, so what should I be doing? Most of the stuff you said is going over my head. I apologize for being ignorant in this field. I did delete the rules in the virtual setup like you asked.

[beersykins]

Do something like:

Virtual server rules:

8080 8082 TCP 8080 8082 192.168.1.4 ppp0.1
26900 26902 UDP 26900 26902 192.168.1.4 ppp0.1

 

Verify your firewall rules on the server/desktop permit that traffic with the same port/protocols from source 'any'.

 

Verify with a port checker such as https://www.yougetsignal.com/tools/open-ports/ to 8080 with the server daemon running.