Port Forward does not work..

As long as there is no service listening on this port at TCP, the access won't succeed naturally.
Your backend is listening at UDP 9987 and UDP probably cannot be probed with the port checker.

root1ng

@viragomann said in Port Forward does not work..:

As long as there is no service listening on this port at TCP, the access won't succeed naturally.
Your backend is listening at UDP 9987 and UDP probably cannot be probed with the port checker.

I changed from UDP to TCP and I still can't access it with the port checker, I still get a timeout.

viragomann

@root1ng
On the backend? And does it work from inside with TCP?

root1ng

@viragomann said in Port Forward does not work..:

@root1ng
On the backend? And does it work from inside with TCP?

Not working ..

viragomann

@root1ng
So I don“t expect it to work from outside.

johnpoz

@viragomann said in Port Forward does not work..:

The port checker might only be able to do TCP checks.

Yeah can you see me can only do TCP.. you would have to use something that can send udp..

Here is one..

https://www.ipvoid.com/udp-port-scan/

But if when testing and tcp gets there via packet capture - its a good sign that udp is open as well. But yeah its never bad idea to actually validate

My bad for not noticing 9987 was setup for udp..

root1ng

@johnpoz said in Port Forward does not work..:

@viragomann said in Port Forward does not work..:

The port checker might only be able to do TCP checks.

Yeah can you see me can only do TCP.. you would have to use something that can send udp..

Here is one..

https://www.ipvoid.com/udp-port-scan/

But if when testing and tcp gets there via packet capture - its a good sign that udp is open as well. But yeah its never bad idea to actually validate

My bad for not noticing 9987 was setup for udp..

In the packet capture log, only 30033 appears with the public ip, 9987 appears open on the last tool provided by you but does not appear in the log, I don't understand why it doesn't work

root1ng

@johnpoz

It seems that it finally appears, but I still can't connect to the teamspeak server using the public ip

viragomann

@root1ng
Sniffing the traffic is the way to investigate this and to nail down the issue.
Run a capture on the WAN. If you can see the expected packets there, run a capture on the LAN side.

However, it's required to know, which packets this service requires to work before.

johnpoz

@root1ng where did you sniff that - on the lan side interface of pfsense I have to assume because its already been forwarded to the 172.16 address. So pfsense did its thing.

Why your 172.16 doesn't answer could be lot of things, its not actually listening on that port, it has a firewall running not allowing it. Your sending to the wrong IP completely.

That device is not using pfsense as its gateway. But if your seeing traffic sent on from pfsense to the IP you want, and the port then its not pfsense issue.. Look to your device, or something else downstream in your network that could prevent that device from seeing the traffic.

Users all the time forget about host firewalls.. The only job pfsense has in this is sending it on to where you say to send it on too, if that device doesn't answer that is not a pfsense problem..

root1ng

@viragomann said in Port Forward does not work..:

Sniffing the traffic is the way to investigate this and to nail down the issue.
Run a capture on the WAN. If you can see the expected packets there, run a capture on the LAN side.

However, it's required to know, which packets this service requires to work before.

I came back with the log for WAN and LAN, I see that it responds to both, is it ok?

WAN:

LAN:

johnpoz

@root1ng where do you see 172.16.1.6 respond with traffic to its 9987 port?

I don't see a response to 192.241.153.165 port 53781 in what you posted.

root1ng

@johnpoz said in Port Forward does not work..:

@root1ng where do you see 172.16.1.6 respond with traffic to its 9987 port?

I don't see a response to 192.241.153.165 port 53781 in what you posted.

Yes, you are right, I checked once more and there is nothing from me to that ip, only from him to me.. I don't know what else to do, do you think you could help me by sharing or teamviewer?

johnpoz

@root1ng if you see traffic sent to that IP.. Check on that device that actually listening. Netstat -an will show you ports being listened on.

for example

Some udp ports my windows box is listening on.. Do you see that 9987 listed?

do a packet capture on the device, wireshark is free and 2 seconds to install, etc..

root1ng

@johnpoz said in Port Forward does not work..:

@root1ng if you see traffic sent to that IP.. Check on that device that actually listening. Netstat -an will show you ports being listened on.

for example

Some udp ports my windows box is listening on.. Do you see that 9987 listed?

do a packet capture on the device, wireshark is free and 2 seconds to install, etc..

The server is on linux (ubuntu), not on windows, I still ran the same command, I attach a picture below.