FreePBX & state table any progress?
-
Have you tried using DynDNS to monitor your WAN ?
-
Can you elaborate please? Thanks!
-
I haven't tested it personally, but I had jimp's recent comment in mind about the improved dyndns on 2.1:
This is already done on 2.1 during a dyndns update. If it detects the IP has changed, it will send a notification that it changed. If you have smtp notifications enabled, that means it will send you an e-mail when it happens.
http://forum.pfsense.org/index.php/topic,51413.msg275400.html#msg275400I assumed that this also meant that if pfsense's dyndns detects the IP has changed, it'll also flush any states associated with the old gateway.
-
DynDNS wouldn't be the one flushing states.
rc.newwanip will flush states when an IP changes
rc.newwanip will update dyndns when an IP changesBoth are separate independent actions taken by rc.newwanip.
-
I guess that works fine if WAN is PPPoE, but what if the external IP changes without a link-down/up event ? (as apparently is the case for the people posting here).
-
rc.newwanip runs in any case where the IP can change: pppoe, dhcp, manual, etc.
There isn't a case where the IP can change that the script doesn't already run that I'm aware of.
-
But my IP address is the same as it has been for well over a year now. So, I'm not sure I am having any IP address changing. However, I did see here or somewhere that come cable ISPs (like, mine, Comcast) are doing some "failover" node testing in the overnight hours. If I understood it correctly, the IP address change is momentary. It also might explain why my Putty session from my house to my office tends to get reset (dropped) sometime between 1am and 4am most nights. I did run some tcpdumps on the LAN and WAN interfaces on my home pfsense this morning when it was timing out and the again after I rebooted pfsense and it started working. I will look at those tonight and post what I see here. I should also be able to look at the asterisk log and see when it starts failing again and see if the timing coincides with the putty drop. I will look at these scripts too. Clearly, I'm not the only one having this problem. But, like I said, it has to involve siproxd and/or static ports = no, because on my office (which has same comcast service) pfsense, I NEVER have this problem (san siproxd and static ports = yes).
-
Can I call 'pfctl -b' from the shell? I'm running 2.1 snapshot and when I try to run it I get an "illegal option – b" error. ??
-
Can I call 'pfctl -b' from the shell? I'm running 2.1 snapshot and when I try to run it I get an "illegal option – b" error. ??
The new syntax (note: pfsense-specific) has become
pfctl -i em0 -Fs -G gwipCheck http://redmine.pfsense.org/issues/1629
-
Thanks, it isn't quite clear to me the difference between
pfctl -i em4 -Fs
and
pfctl -i em0 -Fs -G gwip
can you just elaborate a tiny bit more?
