OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: overopn on June 04, 2018, 05:37:44 am
-
Hi, I have RTSP server in my LAN. I can connect to it fine with TCP but not with UDP. I understand there is a source port rewrite which I must disable, however that is not working.
(https://filedn.com/l3TGy7Y83c247u0RDYa9fkp/temp/pfsense/opnsensenat2.jpg)
(https://filedn.com/l3TGy7Y83c247u0RDYa9fkp/temp/pfsense/opnsensenat3.jpg)
When I do a packet capture on WAN, I can see the TCP part going back but the UDP packets are going to a different (and wrong?) port.
(https://filedn.com/l3TGy7Y83c247u0RDYa9fkp/temp/pfsense/opnsensenat4.jpg)
-
Try splitting the rules, so have two rules, one for UDP and one for TCP... should work as is, but it's a question of ruling things out... or in, as the case may be.
-
I tried pfsense and face the same issue, and I worked with an experienced pfsense guy and determine it is a bug with pfsense, and it does not happen with old pfsense 2.3
Seems opnsense have this bug too since they share same code base?
https://forum.netgate.com/topic/131765/nat-problem-with-rtcp-server
-
The are both FreeBSD based, but the fork to Opnsense happened before pf 2.4 so it suggests an issue upstream.
Have a look at /tmp/rules.debug.. does that show the correct rule?