Forum Discussion
Backend server IP not visible in TCP dump
- Dec 14, 2022
Hi F5_LB_ENG,
> Answer to: tcpdump -p
Check the KB article Omar2 send you. The -p option does not work for HTTP2.
> Answer to 1.)
No. I dont recommend to used the HTTP MRF Router in Gateway mode. Way too many trouble and limitations.
> Answer to 2.)
I noticed the same. The functionality of the HTTP MRF Router in Gateway mode is somehow pure annoying and causes headaches. But miliage may vary...
> Answer to 3.)
Lots of fixes and also new issues. Some symtoms are only valid for if you use HTTP MRF Router and some are valid if you dont use HTTP MRF Router. I found the problems without using HTTP MRF Router more acceptable so far. Right now I dont have any known issues on my agenda using latest v16.
> Answer to 4.)
Plenty of them. Check the f5 support page and take some time for a reading.
> Answer to 5.)
Use it only for HTTP/2 full-proxy mode (HTTP MRF Router must be enabled in this specific case). Try to avoid the use of iRules or Local Traffic Policies and unnecessary features. Try to run this setup in a clean 1:1 VS->Pool mapping by using VS settings only. Thats probably the best usecase for it right now.
Cheers, Kai
Hello,
This happened when for example you have an i-rule to select between different pools "different dest IP combination" and the solution is to set the host addresses or other details specific to the peers as the KB below:
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com