PPTP-WAN does not connect at boot time
-
I run the latest 2.1-BETA1 for some weeks now and have noticed that when I boot up pfsense my WAN does not come up by itself.
This is a PPTP-connection to some old and so far reliable Alcatel SpeedTouch Home ADSL Modem (Austria).
It works OK after I enter "Interfaces" and click "Connect".
For settings: WAN is configured without Dial-On-Demand and I set "Idle Timeout" to "0" (although the value is not displayed anymore when I enter "Interfaces-WAN" now to check for it).
It would be nice to have the connection start by itself obviously.
Please advise, thanks, Stefan
-
Could you post your system log after a fresh boot? That's the main thing I wanted to see, and you're not gonna fit that one in a tweet. ;) (OP and I talked a bit on twitter)
-
last 50 lines of "PPP":
Mar 28 13:59:48 ppp: [wan_link0] MAGICNUM 59aca90c
Mar 28 13:59:48 ppp: [wan_link0] LCP: state change Req-Sent –> Ack-Sent
Mar 28 13:59:50 ppp: [wan_link0] LCP: SendConfigReq #3
Mar 28 13:59:50 ppp: [wan_link0] ACFCOMP
Mar 28 13:59:50 ppp: [wan_link0] PROTOCOMP
Mar 28 13:59:50 ppp: [wan_link0] ACCMAP 0x000a0000
Mar 28 13:59:50 ppp: [wan_link0] MRU 1500
Mar 28 13:59:50 ppp: [wan_link0] MAGICNUM 742f537b
Mar 28 13:59:50 ppp: [wan_link0] LCP: rec'd Configure Ack #3 (Ack-Sent)
Mar 28 13:59:50 ppp: [wan_link0] ACFCOMP
Mar 28 13:59:50 ppp: [wan_link0] PROTOCOMP
Mar 28 13:59:50 ppp: [wan_link0] ACCMAP 0x000a0000
Mar 28 13:59:50 ppp: [wan_link0] MRU 1500
Mar 28 13:59:50 ppp: [wan_link0] MAGICNUM 742f537b
Mar 28 13:59:50 ppp: [wan_link0] LCP: state change Ack-Sent –> Opened
Mar 28 13:59:50 ppp: [wan_link0] PPTP call terminated
Mar 28 13:59:50 ppp: [wan_link0] Link: DOWN event
Mar 28 13:59:50 ppp: [wan_link0] LCP: Down event
Mar 28 13:59:50 ppp: [wan_link0] LCP: state change Ack-Sent –> Starting
Mar 28 13:59:50 ppp: [wan_link0] Link: reconnection attempt 3 in 2 seconds
Mar 28 13:59:50 ppp: [wan_link0] LCP: auth: peer wants CHAP, I want nothing
Mar 28 13:59:50 ppp: [wan_link0] LCP: LayerUp
Mar 28 13:59:50 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 13:59:52 ppp: [wan_link0] Link: reconnection attempt 3
Mar 28 13:59:52 ppp: [wan_link0] PPTP call successful
Mar 28 13:59:52 ppp: [wan_link0] Link: UP event
Mar 28 13:59:52 ppp: [wan_link0] LCP: Up event
Mar 28 13:59:52 ppp: [wan_link0] LCP: Oops, UP at Opened
Mar 28 13:59:54 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 13:59:58 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:02 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:06 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:10 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:15 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:19 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:20 ppp: [wan_link0] rec'd proto LCP while dead
Mar 28 14:00:23 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:27 ppp: [wan_link0] rec'd proto CHAP while dead
Mar 28 14:00:30 ppp: [wan_link0] LCP: authorization timer expired
Mar 28 14:00:30 ppp: [wan_link0] LCP: authorization failed
Mar 28 14:00:30 ppp: [wan_link0] LCP: parameter negotiation failed
Mar 28 14:00:30 ppp: [wan_link0] LCP: state change Opened –> Stopping
Mar 28 14:00:30 ppp: ASSERT "new == PHASE_ESTABLISH" failed: file "lcp.c", line 413
Mar 28 14:00:30 ppp: fatal error, exiting
Mar 28 14:00:30 ppp: [wan] IFACE: Close event
Mar 28 14:00:30 ppp: [wan] IPCP: Close event
Mar 28 14:00:30 ppp: [wan] IPV6CP: Close event
Mar 28 14:00:30 ppp: [wan] Bundle: Shutdown
Mar 28 14:00:30 ppp: [wan_link0] Link: Shutdown
Mar 28 14:00:30 ppp: process 8873 terminatedwant more/anything else? get logs via ssh?
Thanks, Stefan
-
When I applied the latest update today … after reboot the connection was UP.
Great.Let's see what happens next time ;-)