Unable to Port Forward using a Ubiquiti Dream Router

[#1]

I'm not familiar with either wireshark or the tcpdump command, so forgive me if I've used this wrong. I ran tcpdump 192.168.1.100 and port 25565 on my PC whilst running the server and using a website to check if the port is open and it returned 0 packets captured, 1 packet received by filter and 0 packets dropped by kernel. Could that filtered packet be important?

Ok, I'm receiving packets when using the port checking website - and not receiving any when the firewall rule is off and doing the same. I feel like I'm on the right path and that I'm about to learn just how stupid I am!

[#2]

I ran tcpdump 192.168.1.100 and port 25565

Was that specifically to .100 and 25565 as destination ip and ports ?

https://www.howtouselinux.com/post/tcpdump-filters

[#3]

@bradleyp just looking at this https://www.reddit.com/r/Ubiquiti/comments/g25dp8/easiestworking_way_to_view_udm_firewall_logs/ . Seems the firewall logs MAY not be in the main system log ?

[#4]

Knowing nothing about Ubiqiti kit just a observation, probably pointless......

Looks like you used 192.168.1.6 - 192.168.1.253 as the DHCP range but given a server the fixed IP 192.168.1.100

I may be misunderstanding the thread but to me that looks like there could be a IP conflict.

[#5]

Ok I may have jumped the gun with the tcpdump command, wasn't able to see anything else that looked good after that. I had a look through the logs and it is a little difficult to read through. I created a rule to override the other rules and just allow every connection, and after doing that I've noticed a few connections show up with that test rule attempting to connect to 25565, however the open port check still fails?

[#6]

@Champnet 

My guess is that the DHCP server should recognise that as a fixed IP and not assign another device that same IP, I might be wrong but currently no two devices share the same IP

[#7]

Fixed IP addresses should be outside the allocated DHCP range though that doesn’t seem to be causing your problem…

[#8]

@Champnet Ah okay, thank you I'll bear that in mind in future

[#9]

Okay, suddenly the online port checker has said it can see the port. I deleted the test rule allowing all traffic and its still saying it can see the port - so for now I guess its working? I wish I could tell you what I did but aside from creating that test rule I haven't changed anything

[#10]

Did you find out what you did to make this work?

I am having the same issue on my UDM SE. It was working not port forwarding is simply not working.

Port checking websites are showing the port as closed and I am tearing my hair out.

Also with Plusnet with a static IP.

[#11]

Unfortunately no I can’t say there was any specific thing I did. All I can suggest is to repeat the steps I took above. If you're okay taking the risk of allowing all traffic and checking if the port shows up when you run the port checker.