F5F Stay Refreshed Power Users Networks Plex isn't reaching pfSense correctly.

Plex isn't reaching pfSense correctly.

Plex isn't reaching pfSense correctly.

E
emmylee33
Senior Member
710
03-11-2016, 04:09 AM
#1
Hi! I see the issue with your pfSense setup. You're trying to allow Plex from your main LAN to your IoT LAN while blocking all private networks, but you're encountering a "connection refused" error. It might help to double-check the VLAN configurations and ensure the correct subnets are assigned. Also verify that Plex is properly set up for those VLANs. Let me know if you need further guidance!
E
emmylee33
03-11-2016, 04:09 AM #1

Hi! I see the issue with your pfSense setup. You're trying to allow Plex from your main LAN to your IoT LAN while blocking all private networks, but you're encountering a "connection refused" error. It might help to double-check the VLAN configurations and ensure the correct subnets are assigned. Also verify that Plex is properly set up for those VLANs. Let me know if you need further guidance!

M
mennogerben
Member
199
03-11-2016, 05:44 AM
#2
It's generally not advised to route traffic across subnets, as it can heavily stress the router by managing both Plex streaming and your regular internet connection. This setup also adds complexity since Plex sends its broadcast out to the local network, making forwarding difficult. If you still want to proceed, consider missing elements like NAT and proper outbound rules that allow LAN-to-NAT communication with IoT devices. These are often overlooked because automatic rules appear in place from LAN to WAN, but manual or hybrid rules become necessary when NAT is done within the same local network.
M
mennogerben
03-11-2016, 05:44 AM #2

It's generally not advised to route traffic across subnets, as it can heavily stress the router by managing both Plex streaming and your regular internet connection. This setup also adds complexity since Plex sends its broadcast out to the local network, making forwarding difficult. If you still want to proceed, consider missing elements like NAT and proper outbound rules that allow LAN-to-NAT communication with IoT devices. These are often overlooked because automatic rules appear in place from LAN to WAN, but manual or hybrid rules become necessary when NAT is done within the same local network.

T
thebjmax1
Senior Member
395
03-11-2016, 06:54 AM
#3
I needed to perform a similar action but for enabling external connections to my Emby server. Just set up a rule—choose IoT LAN network instead of WAN, and assign Plex to TCP 32400.
T
thebjmax1
03-11-2016, 06:54 AM #3

I needed to perform a similar action but for enabling external connections to my Emby server. Just set up a rule—choose IoT LAN network instead of WAN, and assign Plex to TCP 32400.

E
elijahjoseph
Junior Member
16
03-11-2016, 07:14 AM
#4
It was a subnetting problem. I don’t mind the extra load on the firewall. With gigabit support, I’m using IPS and traffic filtering, and the CPU usage stays under 5%. Besides, layer 3 switching is already in place, so it’s not my main worry. Thanks for the advice!
E
elijahjoseph
03-11-2016, 07:14 AM #4

It was a subnetting problem. I don’t mind the extra load on the firewall. With gigabit support, I’m using IPS and traffic filtering, and the CPU usage stays under 5%. Besides, layer 3 switching is already in place, so it’s not my main worry. Thanks for the advice!

B
Bowling_Beast
Member
200
03-13-2016, 07:18 AM
#5
Certainly, providing precise information helps ensure clarity for anyone encountering the same problem later.
B
Bowling_Beast
03-13-2016, 07:18 AM #5

Certainly, providing precise information helps ensure clarity for anyone encountering the same problem later.

H
Hagnarock
Senior Member
434
03-15-2016, 06:37 AM
#6
The regional LAN subnet configuration used an incorrect CIDR range. The issue has now been resolved.
H
Hagnarock
03-15-2016, 06:37 AM #6

The regional LAN subnet configuration used an incorrect CIDR range. The issue has now been resolved.

T
teocool
Junior Member
14
03-15-2016, 12:48 PM
#7
I already tried that, it's a simple error on pfSense since its sanity checks aren't very reliable. I'm definitely hitting my head against a brick wall while setting up a Wireguard server—maybe it will work this time. Appreciate the update to the thread!
T
teocool
03-15-2016, 12:48 PM #7

I already tried that, it's a simple error on pfSense since its sanity checks aren't very reliable. I'm definitely hitting my head against a brick wall while setting up a Wireguard server—maybe it will work this time. Appreciate the update to the thread!