i cannot for love nor money get port 2302 and 27015 open please help
-
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!!
-
@johnpoz the vorgin hub does not use upnp while in modem mode, from what i can find out anyway, there is no option to change anything in modem mode other than to switch back to router mode
i have been through everything on this page https://docs.netgate.com/pfsense/en/latest/nat/port-forward-troubleshooting.html
and it is still not working
im using udp/tcp as thats what was suggested and that option also worked when i was running with the superhub only
ill post pics of sniffed ports 2302, 2305, 27015 and i also tried from my phone to sniff the port and still said error
-
And you can see an answer was sent... So open up that packet capture in say wireshark.. Maybe your game sent back a RST... What was the sniff on your lan side - did you send it on to your game box? local IP? If so then the port forward is working!!!
We have already gone over how to troubleshoot this - it takes 2 minutes to do..
Here is the thing that test can only test TCP... If its UDP you can not test... So what is it udp or tcp? if you created the firewall rules... Then sniff when you run you run your game on both your wan and lan - do you see inbound traffic on those ports? Do they get forwarded?
As went over already - turn on UPnP on pfsense - what does it show your game is asking to be opened... Does it work then, etc.
-
@matt211 : you read my 'diskstation' ping test above ?
Il expose it for a couple of hours on the Internet :
URL brit.test-domaine.fr port 80 TCP
So enter http://brit.test-domaine.fr in a browser and you'll see the default nginx (?) home page of my Syno (diskstation) - it hosts a web server, it's running on my Syno NAS, a device present on my LAN.
For this to happen, I need to create a NAT TCP port 80 rule.
.....
(2 minutes)Done :
Now, test for yourself : http://brit.test-domaine.fr
(edit : I have a upstream Router, not a modem, so I had also put in a NAT rule in that device, that took me 30 sec max).
edit : to check your ports (TCP only I guess) use world's most famous test site : https://www.grc.com/x/ne.dll?rh1dkyd2
The result for me was :
-
i canot see anything comming from the outside to my server machine, but then again i have never used wireshark before so am unsure if i have done it right
-
@johnpoz i have sent you a PM
-
@Gertjan i already have the rules created
going to change to UDP only as that is what all the servers i have joined use
-
Well that 2305 shows 16 active states...
-
@johnpoz is that good or bad? XD like I said my dude I'm still new to this, so sorry if I seem a bit thick with it
-
That means there connections using that... And your other rules got hits as well..
-
@matt211 said in i cannot for love nor money get port 2302 and 27015 open please help:
i already have the rules created
Nice, but on what interface ? Why hiding it ?
As @johnpoz : packets are coming in, using these rules. So : what's doing 192.168.1.5 with them ?
Are you sure that the server on 192.168.1.5 accepts connections on ports 2302, 2305 and 27015, coming in from the world wide network (Internet) ?
It's rather easy to packet-snif on LAN for traffic to these ports, and what comes back etc.
Do you have some device on your LAN that host a server like my diskstation (a web interface - TCP - port 80 or port 443) : use that to NAT a rule on it's port, and prove this way that your are doing things well.
