I have two WAN connections. Each has public IP.
WAN1 is used for http/https traffic. PMS detects WAN1 IP on Remote Access tab.
I want to use WAN2 for PMS connections.
Port forwarding is configured on WAN2. But I am unable to select WAN2 IP in PMS settings.
Is it possible to use WAN2 public IP?
Server Version#: 1.18.1.1973
Player Version#: iOS app
where does your 0’s route point to on your device with the 2 wan interfaces?
I am not sure what is “0’s route”, but WAN2 interface has lower metric than WAN1. On top of it policy based routing was put in place which directs all http/https traffic to WAN1.
Why?
0’s route is your default gateway.
what kind of device are you using to do this policy based routing?
Cisco ASA firewall.
I still think it has nothing to do with PMS configuration. Am I wrong?
Most likely not related to PMS.
in your ASA type this command
“sh route | in 0.0.0.0”
it should return some values and you should see something similar to this output
Gateway of last resort is 172.16.x.x to network 0.0.0.0
S* 0.0.0.0 0.0.0.0 [1/0] via 172.16.x.x, intf-name
Gateway of last resort is 176.57.x.x to network 0.0.0.0
S* 0.0.0.0 0.0.0.0 [1/0] via 176.57.x.x, outside2
outide2 is WAN2 interface
I assume PMS communicating with plex.tv core network via ports 80/443 thus it can see only WAN1 interface.
These are logs from PMS, not yours just some general logs.
I believe on startup PMS makes a HTTP request to the below URL in order to determine what public IP to use. Since you policy base route HTTP out WAN1 that is the IP PMS will try to use for remote access.
can you modify your PBR (Policy Based Routing) to send HTTP requests from PMS out WAN2 instead of using WAN1 like you do today?
Well I could definitely do as you suggest. I thought it would be easier just to correct some PMS config file and put WAN2 IP there instead of creating another PBR rule just for the PMS.
PMS can only select what local interface to use so if you had 2 interfaces on PMS you can say use NIC2 instead of NIC1 for example.
You can just modify your existing PBR ACL and put a deny for your PMS at the top, assuming you have NAT setup on outside2 as needed.
or you can create a new lower route-map sequence specific to this which should accomplish the same thing.
I don’t believe there is any configuration you can modify in Plex to have it use a specific external IP as that is determined by your local network configuration.
