Port forward plex
-
I am lost, here is the screen from canuseeme
.png)
.png_thumb) -
where are your wan rules?
-
here are the rules
.png)
.png_thumb)
.png)
.png_thumb)
.png)
.png_thumb) -
2 more screens
.png)
.png_thumb)
.png)
.png_thumb) -
What? Dude show me your wan rules… Like this!
-
I hope this is it
.png)
.png_thumb) -
Why in the world do you have an ANY ANY rule on your wan??? Remove that!!!
-
sorry, don't understand. Do I remove any from the rule and what do i replace with. Can you please show me an example
-
Dude Delete the ANY ANY rule you have on the top - Why would you have that??
-
deleted it, but still no access outside of network for custom, Sophia has no problem. Can,t figure this one.
-
Does the ATT 5268AC router modem have anything to do with this. I am using dmz to the pfsense router, and the pfsense to a switch.
-
Lets see your port forward tab..
If can you see me org shows that it can not talk to your plex then no it will not work… So you need to go through the troubleshooting guide I linked too and figure out why.
First step is to make sure the traffic even gets to pfsense, simple package capture on wan interface while you run your can you see me org test.
If that is there, then packet capture on the lan interface - does pfsense send the traffic on? If so then the problem lays with the plex box. Maybe its not actually listening on 32400, maybe there is a firewall, maybe it doesn't point back to pfsense as its gateway? etc..
It really should take only a couple of minutes to determine where the problem is.
So I added a port forward for 45500 to my plex box on 34200... I then go to can you see me.. Run the test, while I repeat this test I sniff on both the wan interface and the lan interface.
As you can see in my case even on the wan sniff I can see replies.. But lets assume it didn't show any responses but I did see the traffic to my wan IP on port 45500, I would then sniff on the interface the server I am forwarding to on (lan in my case) and see if pfsense send on the data to 192.168.9.10 - which it does in my case. But lets say I didn't see any response from 192.168.9.10.. If that is the case then it SCREAMS something wrong on that box.
Be it wrong IP for plex, firewall on the plex box. Plex not listening on that port, etc. If you do not see pfsense sending to 192.168.9.10 in my case. Maybe there is no machine on that IP? And pfsense can not arp for it - can you ping that IP from pfsense? etc..
Pretty much every possible scenario is gone over in the troubleshooting doc.. If you have questions on how to do something specific in that doc then please ask. But the attached walks you through very simple method of traffic down where the problem is. First thing to always validate is the traffic actually gets to pfsense.
Hope that helps.. If you want - if this is confusing.. Later today we could do a teamviewer and I could take a look remotely.
-
@johnpoz
I'm just curious, in you firewall rules, WAN.You have one rule at the bottom. You call it "Clean Block" Do you like to share the settings you have inside that rule?Thanks in advance!
-
Its just there so I only log SYN… I don't care to see the UDP noise and any sort of out of state block. So I turn off logging of the default block, and then only log SYN packets..
Just set the SYN tcp flag is all in the advanced option.. This removes all the nonsense UDP noise and out of state nonsense that really don't care to see... But I am curious to what is the common ports being hit.. 3389, 22, 23, 1433, you know the typical ones. But for example when that worm on the Mikrotik botnet was becoming popular saw a lot of port 8291 which was interesting..
Still see that 8291 now and thing - just looked saw a hit back on 15th ;)
-
Its just there so I only log SYN… I don't care to see the UDP noise and any sort of out of state block. So I turn off logging of the default block, and then only log SYN packets..
Just set the SYN tcp flag is all in the advanced option.. This removes all the nonsense UDP noise and out of state nonsense that really don't care to see... But I am curious to what is the common ports being hit.. 3389, 22, 23, 1433, you know the typical ones. But for example when that worm on the Mikrotik botnet was becoming popular saw a lot of port 8291 which was interesting..
Still see that 8291 now and thing - just looked saw a hit back on 15th ;)
Thank you very much. I didn't think about this. Great idea to show if some shit is going on and more easy to read, instead of using "Log firewall default blocks"(to much noise) Yeah, i can see some of the ports you mentioned now in my log :o :)
Little bit off topic, sorry :)
-
I want to thank you very much, after all the headaches it was something stupid on my end. I decided to log into my freenas which runs my customplugin server, and there it was the plex plugin was off. Could not turn it on, so I rebooted and the plex plugin strted again and now everything is working. Thank you for all your help in this matter. I now a little more on port forwards,and firewall rules thanks to you.
-
And don't forget you removed the any any rule that basically opened up your web gui to the world - so anyone on the planet might of guessed your pfsense username and password or sshed to it, etc. etc..
Why did you create the any any rule on your wan?
