On Thu, Nov 3, 2011 at 5:42 AM, Craig Drown <[email protected]> wrote: > Hi Chris, > > udp 58.28.20.150:5060 <- 192.168.11.15:5060 MULTIPLE:MULTIPLE > udp 192.168.11.15:5060 -> 10.1.1.2:53918 -> 58.28.20.150:5060 > MULTIPLE:MULTIPLE > > Hans' response that they had a problem when the dynamic IP was changed seemed > plausible > I just disconnected the modem and reconnected to get a new IP and that killed > the phone > There's another layer of NAT as the modem does NAT- here in NZ it's PPoA so > pfSense can't connect if the modem is in bridge mode. > Consequently, pfSense wouldn't even see it's WAN IP change....
Then the problem is on the modem with its state keeping since it's the one doing NAT to the public IP. The reason resetting states on pfSense works around it is because it then rewrites the source port to a new port and it looks to the modem to be a new connection, which it then properly NATs to its new IP. > Is there a way to force a state reset periodically, or is that part of the > mythical > http://redmine.pfsense.org/issues/855 > Has no relation at all to that. _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
