Think I found my issue. Will post back my result. Thanks

here is the long thread on the same matter, no fix for it, its since 2.0 and when mpd was upgraded to 5 which has made pfsense 2.0 very unreliable for me regarding pppoe only, rest all work fine, older mopd used to be brillant and no matter a power failure, cable unplug or any other situation, pppoe used to reconnect in a single attempt without issues. http://forum.pfsense.org/index.php/topic,35475.0.html

Hello, I'm coming back after a long time… To have the latest version, I've updated the Pfsense's software to the 2.0rc3 version (The online update didn't work on my Alix 2d3 system, I had to write it on another CF card and swap them). I'm in the same situation, and you're right about the gateways, when run separately, all different ADSL/pppoe lines have the same gateway (and I don't think I could change anything about this, it's my FAI' s choice, isn't it ?). I can understand having same gateways for different WAN could be difficult for detecting which line is working... but is it still possible to work with multiple WAN with PfSense with this setup ? Thanks for your help,         Fred.

Hi, It seems we try to do the same kind of design. I'm doing my lab on GNS3 VirtualBox Edition. The first part of my test was : 3 sites  meshed with GRE over IPSec (Transport) and OSPF as routing protocol. Everything is ok. Now, I'm trying to configure 2 pfsense per site but still 1 router per site. CARP is running (LAN+WAN)and I have  temporaly disabled the IPSEC. The GRE is up and linked to the remote WAN_CARP.The second pfsense node become master if I shutdown the 1st pfsense node. The problem is when I restart the 1st pfsense node. Both PFsense stay master !! Modification : In fact I've found out that this problem is related to disabling and re-enabling CARP on the Master. Stephane [image: BasicDesign.jpg] [image: BasicDesign.jpg_thumb]

No luck with your suggestion…have reset BIOS back to it's original setting for pfSense 1.2.3 where the reboot worked. I agree that this is a FreeBSD issue and not a pfSense problem. Let me know if you come across anything else.

Hm. the line in question refers to the "Prefer older IPsec SAs" option. Setting it, saving, then unsetting it allowed me to proceed.

@Jonb: I am changing my WAN up to a new subnet. I have multiple IPSec tunnels and I am wondering if I can add the new subnet as a secondary on the WAN interface wail I update remote ends and DNS. Is this possible. I think you should have a secondary WAN interface to do that, but I am not sure… Regards, Michele

any ideas? or have you found any obvious, fatal errors in the posted info disposing you not to write any answer anymore?

Using /etc/rc.conf_mount_rw and ro is the right method.

That was most likely due to the old system being pretty far out of date. Had you reinstalled the packages before upgrading it may have been OK. That whole test_pfspkg deal was fixed months and months ago.

Yes, if you can reproduce it every time it would be good to know

Same problem here … unable to connect PPTP

Great!  I've just done that, we'll see how it works.  Thanks very much!

@xtreme698866: @johnpoz: Well you sure that alternate monitor IP you have set it valid and online?  I can tell you I can ping your actual gateway IP, but that monitor IP is not answering ping..  So yeah your offline seems valid to me C:\Windows\System32>ping 119.93.67.253 Pinging 119.93.67.253 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 119.93.67.253:    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Windows\System32>ping 122.3.149.254 Pinging 122.3.149.254 with 32 bytes of data: Reply from 122.3.149.254: bytes=32 time=224ms TTL=238 Reply from 122.3.149.254: bytes=32 time=224ms TTL=238 Reply from 122.3.149.254: bytes=32 time=224ms TTL=238 Reply from 122.3.149.254: bytes=32 time=224ms TTL=238 Ping statistics for 122.3.149.254:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:    Minimum = 224ms, Maximum = 224ms, Average = 224ms if you say you have nothing in the alternate monitoring IP, did you try putting in your actual gateway IP and see if that changes it, and then try unchecking to use alternate monitor IP. noted sir try it later fix thanks for pointing it out

sweet that fixed it up, so now I see the advanced items.  And my 1 in the Frequency Probe was set.. So I removed this 1 and left it blank for default and now I see the button. So I am guessing that the ifs were not triggering on the 1 which was default in the Frequency Probe setting to show the settings, but since items was set even if was the default I was not seeing the button? But its working now, I see buttons for both of my gateways again.  And I will play with the frequency probe setting and make sure it then shows the settings, etc. etc. But looks good - thank you!

Doing a compare on the auth.inc from here and the RC3 version… it seems to include group support, but there's a lot of stuff not in that version that's in the RC3 release. So is replacing the auth.inc still a valid option?