"
I am seeing the same behavior as well. I am on version 1.6.7.7 for what it's worth.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
16.7 Legacy Series / Re: Deleting traffic shaper ports & queues does not take effect until reboot
October 28, 2016, 10:39:53 PM #2
16.7 Legacy Series / Re: Problem assigning NAT rule for Plex Media Server
October 28, 2016, 10:35:35 PM
I initially had trouble with the port forwarding setup after switching from an older version of pfSense. OPNsense's implementation is actually very close to the current pfSense 2.x series. Here's what I did (I have Time Warner Cable with a single dynamic IP):
Under Firewall -> Nat -> Port Forward
No RTR: unchecked
Interface: WAN
TCP/IP Version: IPv4
Protocol: TCP
Source: Any
Source Port: Any/Any
Destination: WAN Address
Destination port range: 32400/32400
Redirect target IP: My Plex server internal IP
Redirect target port: 32400
Description: Plex Media Server
NAT Reflection: None
Filter Rule Association: create associated filter rule.
I am connected and things are working fine for me. Now to tackle traffic shaping for remote Plex streams. :)
Under Firewall -> Nat -> Port Forward
No RTR: unchecked
Interface: WAN
TCP/IP Version: IPv4
Protocol: TCP
Source: Any
Source Port: Any/Any
Destination: WAN Address
Destination port range: 32400/32400
Redirect target IP: My Plex server internal IP
Redirect target port: 32400
Description: Plex Media Server
NAT Reflection: None
Filter Rule Association: create associated filter rule.
I am connected and things are working fine for me. Now to tackle traffic shaping for remote Plex streams. :)
Pages1
