i cannot for love nor money get port 2302 and 27015 open please help
-
here - that took all of 20 seconds..
So that validates traffic got to pfsense, so it can forward it... Now do the packet capture on the lan side - do you see pfsense sending it??
So is this tcp or udp you need - 2302, that is common game port...Is the game server running?
-
??
like i said im new to all this and have spent hours googling how to fix this -
So that is a test from 192.168.1.1 (pfsense) you need to validate it is coming from OUTSIDE!!!!
Do that packet capture when you go to canyouseeme and run their test..
-
-
OK good, packets are hitting your WAN. Now like John said, trace the same thing but on LAN and see if the packets are being forwarded to your server.
-
This post is deleted! -
-
It looks like it's getting through. Now, I did a quick check and it seems that nobody knows for sure which protocol and ports Dayz uses. You have tcp2302 and 27025, but I've read of others talking about udp2302-2305 and other higher port ranges.
Is there a definitive spec on what this game really needs for network access? Your NAT might be perfect but it doesn't work because you've got the wrong ports defined.
-
i pretty much went off what i was told to open to run the server, but i can try the ports you suggested too
-
Don't listen to me; I have no idea. All I am saying is that your NATs look good and seem to work for how they are defined. Someone on Reddit was saying that your server won't show up in the community browser unless you also forward the Steam Query port 27016, but they didn't say if that was tcp or udp.
In other words, you need to do some detective work to confirm what Dayz actually needs. The developer's page is total crap and their wiki is empty. So helpful of them.
Good luck.
-
ok dude ill have a look and see what i can find, thank you both for all your help <3
-
That would certainly explain why you had it configured properly but it still wasn't working.
-
I would also validate that the 192.168 box isn't sending back RST! ;)
Have it show more detail in your packet capture, or download them and open them with wireshark.
But yeah getting some games to work can be painful since they don't document their shit work anything... I mean really how hard is to say these ports are need unsolicated inbound tcp and or udp, etc..
And these ports are needed outbound from the client..
They just say these ports are needed.. BS the game doesn't need 80 and 53 inbound, etc. etc..
A trick you can sometimes do is just fire up UPnP and run your game - and see what it opens... Then you can shut down UPnP and just open the port it had opened with UPnP..
-
ill give that a go too dude, just had a little look and most people are saying ports 2302 - 2306 udp/tcp
-
ok so i had a brainwave and decided to do a packet captuer filtering for the ip and port when i was connecting to a dayz server i play on to see if it was udp or tcp
-
While you can sometimes derive the info you need through what's essentially reverse-engineering, it would be better to get a real specification as to what this game needs.
This page talks about 2302 and 2305 but doesn't say if tcp or udp.
https://community.bistudio.com/wiki/DayZ:Server_Configuration
-
Well that server you connecting to is running on 2402
What does that have to do with inbound to you?
-
This :
@matt211 said in i cannot for love nor money get port 2302 and 27015 open please help:
Port Checker - http://prntscr.com/nm56um
implies that the TCP test runs from pfSense to some device on your LAN, your game server.
pfSense can't connect to it ..., the 192.138.1.118 device refuses connections from your pfSense, probably 192.168.1.1.In that case, its normal that your NAT rule won't work neither : the server doesn't reply.
Make your game server answering to requests.Example : I test my Synology NAS on my LAN :
Port 80 on my Syno is open for connections, so the result was Ok.
-
ok so i set my network back to original setup, using the virginmedia super hub 3 only and forwaded ports 2302, 2305 and 27015 and now my server shows up to community so it is deffinaly a probem with the pfsense port forward
-
@matt211 said in i cannot for love nor money get port 2302 and 27015 open please help:
2302, 2305 and 27015 and now my server shows up to community so it is deffinaly a probem with the pfsense port forward
Dude have already been over this... the link to troubleshooting port forwards... Does your super hub have UPnP enabled?
Do a sniff of this traffic lets see only these ports only inbound 2302 and 27015 and 2305... Is that UDP or TCP or both?
You showed a sniff that 2302 being forwarded, etc. etc..
Here is what I can tell you - in the 10+ years have been here.. Every port forward thread, and there have been plenty has always come down down to PEBKAC!!
