Forum Discussion
VinceBlack
Altocumulus
AltocumulusHelp with Local Traffic Policy with streaming app. and basic understanding.
This is a homelab to have a better understanding of F5 BIG-IP and appercaite any help. For testing purpose I have setup a PLEX server for streaming service and will be setting up a Horizon View UAGs...
Hey, Paulius, thank you again for the tcpdump switches. That helped me find the reset message. I started looking into how to debug this more, which has been a great learning experience. I noticed in the log that when trying from the mobile device, the HTTP_Request for the Host has :443, but accessing from a web GUI or macOS app, it did not. Both policy and iRule had equal to abc.domain.com. I updated the iRule and policy to include or and now it works. See below for iRule. I like the policy features, but it was great to work with iRules too.
if { [HTTP::host] equals "abc.domain.com" or [HTTP::host] equals "abc.domain.com:443" }
Paulius
MVP
MVPVinceBlack Can you provide the configuration of the virtual server when it isn't working for everything excep the web interface? My guess is that the mobile device version of the app isn't sending something that your traffic policy is missing. You might consider running the following tcpdump to see if you can catch anything when you connect from one of the mobile devices. If you had this in an iRule instead you could log the event when it is hit and then you could have a catchall action and log that as well to see if you notice any differences in them.
tcpdump -nni 0.0:nnp host <mobile_device_client_IP>
VinceBlackAltocumulus
AltocumulusHey Paulius,
After running the tcpdump switches, I see that the F5 sent a reset with the message "No server selected." I'll look into creating an iRule as well. Also, I'm going to research this error.
- VinceBlack
According to F5 docs. "Couldn't open a connection to a pool member. This is typically the result of an iRule, Policy, or configuration that prevents the BIG-IP from choosing a pool member." I'll keep poking around and see why this happening.
- Paulius
VinceBlack If you can provide the configuration we can most likely come up with a solution rather quick. If you need to redact names please do so.
- VinceBlack
Hey, Paulius, thank you again for the tcpdump switches. That helped me find the reset message. I started looking into how to debug this more, which has been a great learning experience. I noticed in the log that when trying from the mobile device, the HTTP_Request for the Host has :443, but accessing from a web GUI or macOS app, it did not. Both policy and iRule had equal to abc.domain.com. I updated the iRule and policy to include or and now it works. See below for iRule. I like the policy features, but it was great to work with iRules too.
if { [HTTP::host] equals "abc.domain.com" or [HTTP::host] equals "abc.domain.com:443" }