![]() Internet Protocol Version 4, Src: 10.73.73.8 (10.73.73.8), Dst: 5.5.5.5 (5.5.5.5)ĪCK to my 200 OK with SD should arrive here and it never does!Įverything else I have done with PFSense Nat & Portforwarding has worked flawlessly and without a hitch until I ran into this problem. (Hair pulling) I'm not sure if this is a bug or by design but it's not effing port forwarding UDP 5060 all the time like I expect.ġ0.73.73.8 = my internal asterisk host where ALL port forwarded UDP 5060 should arrive after I get it at the public Interface and it's natted. I also reset state and or reboot every time I've tried something different just to be sure. (We send out the INVITE but do not get the ACK all the way back to the endpoint at host:5060)Īdjusting the rules & advanced settings over two weeks has not changed this behavior for me at all. ![]() This is happening consistently and on all tested inbound SIP invites. You can see that Packet 10 (see below) gets natted and shows up on the LAN interface But packet 11 never does. Pfsense is dropping or not natting these select packets (for reasons I have not been able to figure out) and also not logging anything about it.Īs Captured on PFSENSE itself. My problem is not with dynamic ports it with a simple port forward that is not working 'properly'. Have so far I am still seeing my issue where the SIP ack appears on the WAN interface but never makes it to the LAN interface as seen BOTH by doing packet capturesįrom the PFSense box itself and looking at the incoming UDP port 5060 packets on the internal asterisk box. however across trying all of these things that I I've read many posts that suggest a number of settings to try setting up static outbound rules & the like. I don't mind paying for support if it can get this resolved or re-written to work. Has so far kept us using IPCOP and a number of other routing natting platforms that I long to move away from since I've seen PFSense. I ever so badly want to use PFSense in our production environments but this is one stupid irritating problem that I have been unable to figure out I've been at this for a couple of weeks and now am at the point of pulling my hair out. They pass on the wan rule (don't get logged as a drop) but they are not being natted and appearing on the LAN interface. It's behaving like some kind of sick ALG and consistently dropping certain SIP ACK packets. Pfsense 2.0 is NOT port forwarding UDP port 5060 to my Internal host (Unconditionally) like I'd expect.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |