I Can't seem to open any Ports?

Gertjan

Is there a router in front of pfSense ?

Datastream101

Thanks,

I have a Virgin Media But it's in modem mode connected to PF sense as my router.

Ran the packet sniffer on the wan and the lan. (Nothing come up on the wan)

This is the LAN. with port 18080 (It's showing my PC but has ports 16915,16921 etc. after it?)

14:37:27.712520 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.715877 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.716924 IP 192.168.0.3.16921 > 202.61.252.224.18080: tcp 0
14:37:27.717012 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.718459 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.719672 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.721852 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.723009 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.725658 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.726923 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.728085 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.729269 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.731757 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.732923 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.745192 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.746421 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.747911 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.749170 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0
14:37:27.756647 IP 202.61.252.224.18080 > 192.168.0.3.16921: tcp 0
14:37:27.762669 IP 192.168.0.3.16923 > 68.203.5.125.18080: tcp 0
14:37:27.788327 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 0
14:37:27.800330 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.800793 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.800796 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.800798 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.801019 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.801024 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.801025 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.801027 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.801029 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.801662 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.802161 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.802587 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802591 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802593 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802594 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802596 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802906 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802911 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802913 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.802915 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.803662 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.804372 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.804669 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.804673 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.804674 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.804676 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1088
14:37:27.804873 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.804875 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.804876 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.804878 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.805625 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.805972 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.806140 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.806142 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.806144 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.806145 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.806147 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.806148 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.806497 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.807123 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.807761 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.807762 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.807765 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.807767 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.807997 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.807999 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.808122 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.808124 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.808125 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.808748 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.809544 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.809545 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1088
14:37:27.809547 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.809548 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.809550 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.809551 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.809872 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.809874 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.809875 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.810497 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.811286 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811288 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811290 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811496 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811498 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811499 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811501 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811502 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.811746 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.812247 IP 192.168.0.3.16870 > 185.112.185.140.18080: tcp 0
14:37:27.813051 IP 185.112.185.140.18080 > 192.168.0.3.16870: tcp 1440
14:37:27.813246 IP 198.1.231.6.18080 > 192.168.0.3.16783: tcp 1460
14:37:27.813248 IP 198.1.231.6.18080 > 192.168.0.3.16783: tcp 1460
14:37:27.813249 IP 198.1.231.6.18080 > 192.168.0.3.16783: tcp 1460
14:37:27.813495 IP 198.1.231.6.18080 > 192.168.0.3.16783: tcp 1460
14:37:27.813497 IP 198.1.231.6.18080 > 192.168.0.3.16783: tcp 1460
14:37:27.813499 IP 198.1.231.6.18080 > 192.168.0.3.16783: tcp 1460
14:37:27.813500 IP 213.149.186.211.18080 > 192.168.0.3.16915: tcp 1452
14:37:27.814123 IP 192.168.0.3.16915 > 213.149.186.211.18080: tcp 0

When I run it using the WAN I don't get any results.

Trying the other ports for the miner, 31400 for example. Nothing on the WAN side of things, and nothing on the LAN either?

Sorry guys no idea.

NogBadTheBad

This post is deleted!

viragomann

@datastream101 said in I Can't seem to open any Ports?:

This is the LAN. with port 18080 (It's showing my PC but has ports 16915,16921 etc. after it?)

Do you try to access from inside your LAN? If so, you won't see any packets on WAN, of course, cause they don't pass it.
Also you will not succeed without enabling NAT reflection in the port forwarding rule.
Try the access from the internet.

16915,16921 etc. are the outgoing ports of your PC.

Datastream101

@viragomann

Thanks, makes sense on the WAN.

When you say "Try access from the interent" do you mean try and connect to PF sense?

I've tried the different "nat" options and saved and let it reload, done a test but still blocked?

Thanks.

P.s I don't get it, my CCTV works fine away from home and yet that port is coming up as blocked as well? wtf..?!?!

06-04-2021 19-03-10.jpg

viragomann

@datastream101
You still did not show your port forwarding rule. So I'm assuming you have a rule on WAN forwarding traffic from WAN address to 192.168.0.3.
So to investigate you have to do initiate access from the internet. You may use a port testing web portal for that.
Run a packet capture on WAN while you check the port to see if the packets arrive.

Datastream101

@viragomann

I'll give it a go...

Is this screen you mean?

viragomann

@datastream101
Yeah, that's it.

The destination has to be "WAN address" in the NAT rule, cause this is that one the client is sending its packets to.

Datastream101

@viragomann

Thanks for helping a n33b out.

OK, I changed to wan, but alas, still saying closed. I've run a packet capture and have attached the pics. Hope that helps.

Thanks again. :)

07-04-2021 09-28-24.jpg

viragomann

@datastream101
Cannot find any packet with destination port 18080 in these.

Moreover you should take the capture on the WAN interface first if you want to investigate access from the internet! Mentioned that multiple times already!

johnpoz

@viragomann said in I Can't seem to open any Ports?:

Moreover you should take the capture on the WAN interface first if you want to investigate access from the internet!

^ exactly!!!

First step in troubleshooting port forwards, is to validate that traffic is actually getting to your wan..

You don't even need port forward or wan rule setup to validate this.. Just sniff (diag menu, packet capture) on your wan.. No go to your fav port checker - can you see me . org for example..

Here I don't have this port open.. But I can validate it actually gets to my wan, so pfsense could forward it, if wanted too..

If your not seeing the traffic hit your wan - then there is nothing to forward. First step is actual validation that traffic gets to your wan..

Datastream101

@johnpoz @viragomann

Thanks for this, I know it used to work, for example when I set up a "killing floor 2" server It was easy, and my CCTV etc. also had this "pi node" working as well. Only thing that I changed or done was updated Pfsense and then loaded my config file back in.

Looks like packets are making it the WAN. So that's a good thing!

johnpoz

Well that is not the 18080 port your saying your trying to forward.. But yeah that validates that 31400 is getting to your wan.

Make sure you test via the port your wanting to forward.

Datastream101

@johnpoz Thanks, Yeah I was just trying 31400 as that's the Pi Node.

Tried the other port which is for the "Monero" app. 18080

07-04-2021 11-55-50.jpg

07-04-2021 11-53-52.jpg

Looks like it's hitting the WAN.

Thanks again for your help.

viragomann

@datastream101
Okay, now you see packets hitting your WAN IP (I guess) on port 18080, but there is no response.
You should also see response packets from your WAN address 18080 to the remote address.

Now do a capture on the internal interface to see if the packets are forwarded correctly and if your internal device is responding. Best to do two captures simultanously on WAN and LAN (or whatever interface is facing to the destination device). So if there are packets arriving on the WAN you should also see it on the internal interface.

Datastream101

@viragomann All sorted thanks so much. after doing what you said I could see packets hitting the WAN and the LAN....so it had to be PC related. (I've never done this before so that was good to learn how to send packets to the WAN and the LAN and monitor them)

I removed and re-installed "Docker" on the PC, fired up the Pi Node (which had ports 31400 - 31409 blocked) and it worked. docker for some reason just had them ports blocked.

Thanks for the tip on putting destination as WAN as you mentioned earlier, it would have never worked the way I had it configured.

"Monero" which had port 18080 is working great....

Once again thanks for taking your patience with a n00b.

Much appreciated.

johnpoz

Glad you got it sorted.. Once you know how it works, and the basics - it really only takes a couple of minutes to figure out where the problem is..

Wan check first, if there - then lan - if sending on, then its downstream of pfsense.

Good reference
https://docs.netgate.com/pfsense/en/latest/troubleshooting/nat.html

https://docs.netgate.com/pfsense/en/latest/troubleshooting/nat-port-forwards.html

Datastream101

@johnpoz Brilliant! Can I donate?, haven't got much as the "plandemic" destroyed my business, my life and my future.! but hey can always send something :)

I for the past what maybe 6 or 7 years wanted to install Pfsense and last year in lockdown I did, I should of had it years ago! Had an old laptop that finally became my router...

Love the menu's the lay out the charts the configs, I'm a nerd for stuff like this...lol, and yes the support is awesome!

Brilliant piece of software!

johnpoz

While they use to have a gold subscription you could get for $99 as a way of showing support. They really have never just had a donate sort of button.

Currently the best way to support is buy netgate hardware, or a support contract.

If you want to throw a few bucks towards the cause - you could donate to the freebsd foundation.. Which rolls downhill towards.. If freebsd is better, pfsense will end up better since pfsense runs on freebsd..

https://freebsdfoundation.org/

viragomann

@datastream101
Glad it's working now. Thanks for feedback.

I guess, you've learned your lesson. We all had to start once with that stuff.