[2.1.5-RELEASE] Bouncy PPPoE WAN (BT Home Broadband/Bridged TP-LINK TD-8817)
-
Hi Everyone,
Thanks in advance for your help, I have done quite a bit of searching on this but have not found any solutions (yep I know full well someone will do "one simple Google" and find the solution ;))
Right, I'm trying to setup pfSense at the edge of my network. I'm (sadly) on BT Home Unlimited Broadband (over an Exchange Only (EO) Line I think) hosting a few low bandwidth services for personal non-commercial purposes.
As the title suggests: The ADSL Line goes into a TP-Link TD-8817 configured as per BT instructions for VPI/VCI & in Bridged VC_MUX mode.
<iframe src="https://onedrive.live.com/embed?cid=F7B2CB21CF176DB8&resid=F7B2CB21CF176DB8%212001&authkey=ACmby0tBwiPLZaU" width="320" height="270" frameborder="0" scrolling="no"></iframe>
the TP-Link TD-8817 is then connected to the WAN Port of the pfSense, which is configured to use PPPoE with username and password of bthomehub@btbroadband.com
<iframe src="https://onedrive.live.com/embed?cid=F7B2CB21CF176DB8&resid=F7B2CB21CF176DB8%211987&authkey=AEVmNgUvDWbDosA" width="320" height="249" frameborder="0" scrolling="no"></iframe>
This connects fine and provides the internet and the hosted services are available externally
<iframe src="https://onedrive.live.com/embed?cid=F7B2CB21CF176DB8&resid=F7B2CB21CF176DB8%211990&authkey=ACJ4HQqDL-x-NxM" width="285" height="320" frameborder="0" scrolling="no"></iframe>
<iframe src="https://onedrive.live.com/embed?cid=F7B2CB21CF176DB8&resid=F7B2CB21CF176DB8%211989&authkey=AFeITXxEEnLDTUY" width="320" height="232" frameborder="0" scrolling="no"></iframe>Then the problems start, after an arbitrary amount of minutes the WAN Drops and takes 5+ minutes to reconnect (resulting in a new IP causing its own problems).
the lines written to the PPP.log are (4702 lines attached from less than 24 hours)
Dec 10 16:04:26 dudley ppp: [wan_link0] LCP: no reply to 1 echo request(s) Dec 10 16:04:36 dudley ppp: [wan_link0] LCP: no reply to 2 echo request(s) Dec 10 16:04:46 dudley ppp: [wan_link0] LCP: no reply to 3 echo request(s) Dec 10 16:04:56 dudley ppp: [wan_link0] LCP: no reply to 4 echo request(s) Dec 10 16:05:06 dudley ppp: [wan_link0] LCP: no reply to 5 echo request(s) Dec 10 16:05:06 dudley ppp: [wan_link0] LCP: peer not responding to echo requests Dec 10 16:05:06 dudley ppp: [wan_link0] LCP: state change Opened --> Stopping Dec 10 16:05:06 dudley ppp: [wan_link0] Link: Leave bundle "wan" Dec 10 16:05:06 dudley ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps Dec 10 16:05:06 dudley ppp: [wan] IPCP: Close event Dec 10 16:05:06 dudley ppp: [wan] IPCP: state change Opened --> Closing Dec 10 16:05:06 dudley ppp: [wan] IPCP: SendTerminateReq #84 Dec 10 16:05:06 dudley ppp: [wan] IPCP: LayerDown Dec 10 16:05:10 dudley ppp: [wan] IPV6CP: Close event Dec 10 16:05:10 dudley ppp: [wan] IPV6CP: state change Opened --> Closing Dec 10 16:05:10 dudley ppp: [wan] IPV6CP: SendTerminateReq #42 Dec 10 16:05:10 dudley ppp: [wan] IPV6CP: LayerDown Dec 10 16:05:10 dudley ppp: [wan] IFACE: Down event Dec 10 16:05:10 dudley ppp: [wan] IFACE: Rename interface pppoe0 to pppoe0 Dec 10 16:05:10 dudley ppp: [wan] IPCP: Down event Dec 10 16:05:10 dudley ppp: [wan] IPCP: LayerFinish Dec 10 16:05:10 dudley ppp: [wan] IPCP: state change Closing --> Initial Dec 10 16:05:10 dudley ppp: [wan] IPV6CP: Down event Dec 10 16:05:10 dudley ppp: [wan] IPV6CP: LayerFinish Dec 10 16:05:10 dudley ppp: [wan] Bundle: No NCPs left. Closing links... Dec 10 16:05:10 dudley ppp: [wan] IPV6CP: state change Closing --> Initial Dec 10 16:05:10 dudley ppp: [wan_link0] LCP: SendTerminateReq #83 Dec 10 16:05:10 dudley ppp: [wan_link0] LCP: LayerDown Dec 10 16:05:16 dudley ppp: [wan_link0] LCP: SendTerminateReq #84 Dec 10 16:05:18 dudley ppp: [wan_link0] LCP: state change Stopping --> Stopped Dec 10 16:05:18 dudley ppp: [wan_link0] LCP: LayerFinish Dec 10 16:05:18 dudley ppp: [wan_link0] PPPoE: connection closed Dec 10 16:05:18 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:05:18 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:05:18 dudley ppp: [wan_link0] LCP: state change Stopped --> Starting Dec 10 16:05:18 dudley ppp: [wan_link0] LCP: LayerStart Dec 10 16:05:18 dudley ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds Dec 10 16:05:21 dudley ppp: [wan_link0] Link: reconnection attempt 1 Dec 10 16:05:21 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:05:30 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:05:30 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:05:30 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:05:30 dudley ppp: [wan_link0] Link: reconnection attempt 2 in 3 seconds Dec 10 16:05:33 dudley ppp: [wan_link0] Link: reconnection attempt 2 Dec 10 16:05:33 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:05:42 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:05:42 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:05:42 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:05:42 dudley ppp: [wan_link0] Link: reconnection attempt 3 in 1 seconds Dec 10 16:05:43 dudley ppp: [wan_link0] Link: reconnection attempt 3 Dec 10 16:05:43 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:05:52 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:05:52 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:05:52 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:05:52 dudley ppp: [wan_link0] Link: reconnection attempt 4 in 2 seconds Dec 10 16:05:54 dudley ppp: [wan_link0] Link: reconnection attempt 4 Dec 10 16:05:54 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:06:03 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:06:03 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:06:03 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:06:03 dudley ppp: [wan_link0] Link: reconnection attempt 5 in 4 seconds Dec 10 16:06:07 dudley ppp: [wan_link0] Link: reconnection attempt 5 Dec 10 16:06:07 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:06:16 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:06:16 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:06:16 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:06:16 dudley ppp: [wan_link0] Link: reconnection attempt 6 in 4 seconds Dec 10 16:06:20 dudley ppp: [wan_link0] Link: reconnection attempt 6 Dec 10 16:06:20 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:06:29 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:06:29 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:06:29 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:06:29 dudley ppp: [wan_link0] Link: reconnection attempt 7 in 2 seconds Dec 10 16:06:31 dudley ppp: [wan_link0] Link: reconnection attempt 7 Dec 10 16:06:31 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:06:40 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:06:40 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:06:40 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:06:40 dudley ppp: [wan_link0] Link: reconnection attempt 8 in 3 seconds Dec 10 16:06:43 dudley ppp: [wan_link0] Link: reconnection attempt 8 Dec 10 16:06:43 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:06:52 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:06:52 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:06:52 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:06:52 dudley ppp: [wan_link0] Link: reconnection attempt 9 in 3 seconds Dec 10 16:06:55 dudley ppp: [wan_link0] Link: reconnection attempt 9 Dec 10 16:06:55 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:07:04 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:07:04 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:07:04 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:07:04 dudley ppp: [wan_link0] Link: reconnection attempt 10 in 3 seconds Dec 10 16:07:07 dudley ppp: [wan_link0] Link: reconnection attempt 10 Dec 10 16:07:07 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:07:16 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:07:16 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:07:16 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:07:16 dudley ppp: [wan_link0] Link: reconnection attempt 11 in 3 seconds Dec 10 16:07:19 dudley ppp: [wan_link0] Link: reconnection attempt 11 Dec 10 16:07:19 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:07:28 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:07:28 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:07:28 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:07:28 dudley ppp: [wan_link0] Link: reconnection attempt 12 in 4 seconds Dec 10 16:07:32 dudley ppp: [wan_link0] Link: reconnection attempt 12 Dec 10 16:07:32 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:07:41 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:07:41 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:07:41 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:07:41 dudley ppp: [wan_link0] Link: reconnection attempt 13 in 4 seconds Dec 10 16:07:45 dudley ppp: [wan_link0] Link: reconnection attempt 13 Dec 10 16:07:45 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:07:54 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:07:54 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:07:54 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:07:54 dudley ppp: [wan_link0] Link: reconnection attempt 14 in 2 seconds Dec 10 16:07:56 dudley ppp: [wan_link0] Link: reconnection attempt 14 Dec 10 16:07:56 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:08:05 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:08:05 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:08:05 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:08:05 dudley ppp: [wan_link0] Link: reconnection attempt 15 in 4 seconds Dec 10 16:08:09 dudley ppp: [wan_link0] Link: reconnection attempt 15 Dec 10 16:08:09 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:08:18 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:08:18 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:08:18 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:08:18 dudley ppp: [wan_link0] Link: reconnection attempt 16 in 1 seconds Dec 10 16:08:19 dudley ppp: [wan_link0] Link: reconnection attempt 16 Dec 10 16:08:19 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:08:28 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:08:28 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:08:28 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:08:28 dudley ppp: [wan_link0] Link: reconnection attempt 17 in 2 seconds Dec 10 16:08:30 dudley ppp: [wan_link0] Link: reconnection attempt 17 Dec 10 16:08:30 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:08:39 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:08:39 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:08:39 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:08:39 dudley ppp: [wan_link0] Link: reconnection attempt 18 in 3 seconds Dec 10 16:08:42 dudley ppp: [wan_link0] Link: reconnection attempt 18 Dec 10 16:08:42 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:08:51 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:08:51 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:08:51 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:08:51 dudley ppp: [wan_link0] Link: reconnection attempt 19 in 1 seconds Dec 10 16:08:52 dudley ppp: [wan_link0] Link: reconnection attempt 19 Dec 10 16:08:52 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:09:01 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:09:01 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:09:01 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:09:01 dudley ppp: [wan_link0] Link: reconnection attempt 20 in 2 seconds Dec 10 16:09:03 dudley ppp: [wan_link0] Link: reconnection attempt 20 Dec 10 16:09:03 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:09:12 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:09:12 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:09:12 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:09:12 dudley ppp: [wan_link0] Link: reconnection attempt 21 in 4 seconds Dec 10 16:09:16 dudley ppp: [wan_link0] Link: reconnection attempt 21 Dec 10 16:09:16 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:09:25 dudley ppp: [wan_link0] PPPoE connection timeout after 9 seconds Dec 10 16:09:25 dudley ppp: [wan_link0] Link: DOWN event Dec 10 16:09:25 dudley ppp: [wan_link0] LCP: Down event Dec 10 16:09:25 dudley ppp: [wan_link0] Link: reconnection attempt 22 in 4 seconds Dec 10 16:09:29 dudley ppp: [wan_link0] Link: reconnection attempt 22 Dec 10 16:09:29 dudley ppp: [wan_link0] PPPoE: Connecting to '' Dec 10 16:09:29 dudley ppp: PPPoE: rec'd ACNAME "bras-red14.sl-B226E1811E036E" Dec 10 16:09:29 dudley ppp: [wan_link0] PPPoE: connection successful Dec 10 16:09:29 dudley ppp: [wan_link0] Link: UP event Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: Up event Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: state change Starting --> Req-Sent Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: SendConfigReq #85 Dec 10 16:09:29 dudley ppp: [wan_link0] PROTOCOMP Dec 10 16:09:29 dudley ppp: [wan_link0] MRU 1492 Dec 10 16:09:29 dudley ppp: [wan_link0] MAGICNUM a4fed966 Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: rec'd Configure Request #76 (Req-Sent) Dec 10 16:09:29 dudley ppp: [wan_link0] MRU 1492 Dec 10 16:09:29 dudley ppp: [wan_link0] AUTHPROTO CHAP MD5 Dec 10 16:09:29 dudley ppp: [wan_link0] MAGICNUM 6597ad88 Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: SendConfigAck #76 Dec 10 16:09:29 dudley ppp: [wan_link0] MRU 1492 Dec 10 16:09:29 dudley ppp: [wan_link0] AUTHPROTO CHAP MD5 Dec 10 16:09:29 dudley ppp: [wan_link0] MAGICNUM 6597ad88 Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: rec'd Configure Reject #85 (Ack-Sent) Dec 10 16:09:29 dudley ppp: [wan_link0] PROTOCOMP Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: SendConfigReq #86 Dec 10 16:09:29 dudley ppp: [wan_link0] MRU 1492 Dec 10 16:09:29 dudley ppp: [wan_link0] MAGICNUM a4fed966 Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: rec'd Configure Ack #86 (Ack-Sent) Dec 10 16:09:29 dudley ppp: [wan_link0] MRU 1492 Dec 10 16:09:29 dudley ppp: [wan_link0] MAGICNUM a4fed966 Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: state change Ack-Sent --> Opened Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: auth: peer wants CHAP, I want nothing Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: LayerUp Dec 10 16:09:29 dudley ppp: [wan_link0] CHAP: rec'd CHALLENGE #1 len: 34 Dec 10 16:09:29 dudley ppp: [wan_link0] Name: "bras-red14.sl" Dec 10 16:09:29 dudley ppp: [wan_link0] CHAP: Using authname "bthomehub@btbroadband.com" Dec 10 16:09:29 dudley ppp: [wan_link0] CHAP: sending RESPONSE #1 len: 46 Dec 10 16:09:29 dudley ppp: [wan_link0] CHAP: rec'd SUCCESS #1 len: 43 Dec 10 16:09:29 dudley ppp: [wan_link0] MESG: CHAP authentication success, unit 12139 Dec 10 16:09:29 dudley ppp: [wan_link0] LCP: authorization successful Dec 10 16:09:29 dudley ppp: [wan_link0] Link: Matched action 'bundle "wan" ""' Dec 10 16:09:29 dudley ppp: [wan_link0] Link: Join bundle "wan" Dec 10 16:09:29 dudley ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps Dec 10 16:09:29 dudley ppp: [wan] IPCP: Open event Dec 10 16:09:29 dudley ppp: [wan] IPCP: state change Initial --> Starting Dec 10 16:09:29 dudley ppp: [wan] IPCP: LayerStart Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: Open event Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: state change Initial --> Starting Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: LayerStart Dec 10 16:09:29 dudley ppp: [wan] IPCP: Up event Dec 10 16:09:29 dudley ppp: [wan] IPCP: state change Starting --> Req-Sent Dec 10 16:09:29 dudley ppp: [wan] IPCP: SendConfigReq #85 Dec 10 16:09:29 dudley ppp: [wan] IPADDR 0.0.0.0 Dec 10 16:09:29 dudley ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: Up event Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: state change Starting --> Req-Sent Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: SendConfigReq #43 Dec 10 16:09:29 dudley ppp: [wan] IPCP: rec'd Configure Request #172 (Req-Sent) Dec 10 16:09:29 dudley ppp: [wan] IPADDR 217.32.147.109 Dec 10 16:09:29 dudley ppp: [wan] 217.32.147.109 is OK Dec 10 16:09:29 dudley ppp: [wan] IPCP: SendConfigAck #172 Dec 10 16:09:29 dudley ppp: [wan] IPADDR 217.32.147.109 Dec 10 16:09:29 dudley ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent Dec 10 16:09:29 dudley ppp: [wan] IPCP: rec'd Configure Reject #85 (Ack-Sent) Dec 10 16:09:29 dudley ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Dec 10 16:09:29 dudley ppp: [wan] IPCP: SendConfigReq #86 Dec 10 16:09:29 dudley ppp: [wan] IPADDR 0.0.0.0 Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: rec'd Configure Request #186 (Req-Sent) Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: SendConfigAck #186 Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: state change Req-Sent --> Ack-Sent Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: rec'd Configure Ack #43 (Ack-Sent) Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: state change Ack-Sent --> Opened Dec 10 16:09:29 dudley ppp: [wan] IPV6CP: LayerUp Dec 10 16:09:29 dudley ppp: [wan] f481:5407:fd5d:784d -> 0230:88ff:fe04:0dd0 Dec 10 16:09:30 dudley ppp: [wan] IFACE: Up event Dec 10 16:09:30 dudley ppp: [wan] IFACE: Rename interface ng0 to pppoe0 Dec 10 16:09:30 dudley ppp: [wan] IPCP: rec'd Configure Nak #86 (Ack-Sent) Dec 10 16:09:30 dudley ppp: [wan] IPADDR 86.166.154.245 Dec 10 16:09:30 dudley ppp: [wan] 86.166.154.245 is OK Dec 10 16:09:30 dudley ppp: [wan] IPCP: SendConfigReq #87 Dec 10 16:09:30 dudley ppp: [wan] IPADDR 86.166.154.245 Dec 10 16:09:30 dudley ppp: [wan] IPCP: rec'd Configure Ack #87 (Ack-Sent) Dec 10 16:09:30 dudley ppp: [wan] IPADDR 86.166.154.245 Dec 10 16:09:30 dudley ppp: [wan] IPCP: state change Ack-Sent --> Opened Dec 10 16:09:30 dudley ppp: [wan] IPCP: LayerUp Dec 10 16:09:30 dudley ppp: [wan] 86.166.154.245 -> 217.32.147.109
the number of re-connection attempts varies each time, the lowest I have seen in logs I have scanned over was 5. This appears to happen regardless of if I am using the WWW: Browsing, streaming music, etc. or not even on the network.
The reason I am pointing the finger at pfSense is if, like now, I connect the modem to my Windows 8.1 PC and setup a PPPoE Connection with the same username/password pair as pfSense, it connects and stays connected, including leaving unattended (not using internet), and the connections stays up consistently with no drops or IP changes. If Win 8.1 can manage it then surely pfSense can!!!
Has anyone already fixed this and/or does anyone have any ideas to try? Thanks again for any advice, happy to provide any extra info as needed.
Note: Snort is installed on pfSense with the balanced IPS Policy applied to WAN.
Note: pfSense box is a HP 704941-421 ProLiant Micro Server with a HP 503746-B21 NC112T PCI Express Gigabit Server Adapter. WAN is on-board, LAN is NC112T
ppp.log.txt -
What do you see in the system log?
I recently had to modify the monitor IP on my home BT connection. After they made some network changes the gateway machine no longer reliably responds to pings.
Steve
-
What do you see in the system log?
I recently had to modify the monitor IP on my home BT connection. After they made some network changes the gateway machine no longer reliably responds to pings.
Steve
Google Public DNS ( 8.8.8.8 ) set as monitor IP. Fingers crossed it will not stay up…
Thanks Steve I will give it 48 hours to see them update here :-)
-
What do you see in the system log?
I recently had to modify the monitor IP on my home BT connection. After they made some network changes the gateway machine no longer reliably responds to pings.
Steve
Steve,
I have tried two settings in System > Routing > WAN_PPPOE (default)
- Setting Monitor IP to 8.8.8.8
- Checking Disable Gateway Monitoring
Sadly, both still result in the PPPoE Connection repeatedly bouncing, with the same log entries as before in the ppp.log file
Dec 11 18:34:52 dudley ppp: [wan_link0] LCP: no reply to 1 echo request(s) Dec 11 18:35:02 dudley ppp: [wan_link0] LCP: no reply to 2 echo request(s) Dec 11 18:35:12 dudley ppp: [wan_link0] LCP: no reply to 3 echo request(s) Dec 11 18:35:22 dudley ppp: [wan_link0] LCP: no reply to 4 echo request(s) Dec 11 18:35:32 dudley ppp: [wan_link0] LCP: no reply to 5 echo request(s) Dec 11 18:35:32 dudley ppp: [wan_link0] LCP: peer not responding to echo requests
Despite setting it to not monitor the gateway, I notice the Status > Gateways, stil shows a monitor IP (the gateway) and is still checking.
Name Gateway Monitor RTT Loss Status Description WAN_PPPOE 217.32.147.109 217.32.147.109 0.0ms 0.0% Online Last check: Thu, 11 Dec 2014 18:43:55 +0000 Interface WAN_PPPOE Gateway
Anyone know what I'm doing wrong here?
Thanks
Joe -
Hmm. Are you seeing 'apinger' entries in the system log?
Can you swap back to something other than pfSense as a test? It could be some faulty upstream hardware.
Steve
-
Hmm. Are you seeing 'apinger' entries in the system log?
Can you swap back to something other than pfSense as a test? It could be some faulty upstream hardware.
Steve
I was just starting to think that setting back to 8.8.8.8 and rebooting had fixed it… then
Dec 11 21:12:04 ppp: [wan_link0] LCP: no reply to 1 echo request(s) Dec 11 21:12:14 ppp: [wan_link0] LCP: no reply to 2 echo request(s) Dec 11 21:12:24 ppp: [wan_link0] LCP: no reply to 3 echo request(s) Dec 11 21:12:34 ppp: [wan_link0] LCP: no reply to 4 echo request(s) Dec 11 21:12:44 ppp: [wan_link0] LCP: no reply to 5 echo request(s) Dec 11 21:12:44 ppp: [wan_link0] LCP: peer not responding to echo requests Dec 11 21:12:44 ppp: [wan_link0] LCP: state change Opened --> Stopping Dec 11 21:12:44 ppp: [wan_link0] Link: Leave bundle "wan" Dec 11 21:12:44 ppp: [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps Dec 11 21:12:44 ppp: [wan] IPCP: Close event Dec 11 21:12:44 ppp: [wan] IPCP: state change Opened --> Closing Dec 11 21:12:44 ppp: [wan] IPCP: SendTerminateReq #4 Dec 11 21:12:44 ppp: [wan] IPCP: LayerDown Dec 11 21:12:45 ppp: [wan] IFACE: Delete route 0.0.0.0/0 217.32.147.109 failed: No such process Dec 11 21:12:45 ppp: [wan] IPV6CP: Close event Dec 11 21:12:45 ppp: [wan] IPV6CP: state change Opened --> Closing Dec 11 21:12:45 ppp: [wan] IPV6CP: SendTerminateReq #2 Dec 11 21:12:45 ppp: [wan] IPV6CP: LayerDown Dec 11 21:12:45 ppp: [wan] IFACE: Down event Dec 11 21:12:45 ppp: [wan] IFACE: Rename interface pppoe0 to pppoe0 Dec 11 21:12:45 ppp: [wan] IPCP: Down event Dec 11 21:12:45 ppp: [wan] IPCP: LayerFinish Dec 11 21:12:45 ppp: [wan] IPCP: state change Closing --> Initial Dec 11 21:12:45 ppp: [wan] IPV6CP: Down event Dec 11 21:12:45 ppp: [wan] IPV6CP: LayerFinish Dec 11 21:12:45 ppp: [wan] Bundle: No NCPs left. Closing links... Dec 11 21:12:45 ppp: [wan] IPV6CP: state change Closing --> Initial Dec 11 21:12:45 ppp: [wan_link0] LCP: SendTerminateReq #3 Dec 11 21:12:45 ppp: [wan_link0] LCP: LayerDown Dec 11 21:12:47 ppp: [wan_link0] LCP: SendTerminateReq #4
The System > Gateway log mentions apinger
Dec 11 18:57:46 apinger: Starting Alarm Pinger, apinger(24935) Dec 11 21:11:46 apinger: ALARM: WAN_PPPOE(8.8.8.8) *** down *** Dec 11 21:16:24 apinger: SIGHUP received, reloading configuration. Dec 11 21:16:24 apinger: alarm canceled (config reload): WAN_PPPOE(8.8.8.8) *** down ***
That is by far the longest it has stayed up as far as I can tell…
I will try setting up the modem up direct to my PC tonight and leave it all night, and all day while I'm at work tomorrow and see if it stays up with the same IP.
-
Hmm, well apinger is still monitoring 8.8.8.8. but it goes straight to 'down' rather than delay or packet loss alarms. Do you still see ping times and packet loss stats in Status: Gateways: ?
Steve
-
Try an EU based ip address?
I have a Swiss ip address in the Monitor IP field for ppoe and have not had a problem with net connections dropping on TalkTalk in the UK, although for me, I was on 2.1.4 when this started happening a short while back. I moved to 2.2 beta but still saw the same problem, but only after putting an ip address in the Monitor IP field did my net connections stay up and come back up when the connection was eventually reset and new ip address assigned. Doing the same might work for you on 2.1.4.
This only became a problem a month or so ago so I suspect some changes have occurred with UK net infrastructure recently.
-
Dec 11 21:12:04 ppp: [wan_link0] LCP: no reply to 1 echo request(s) Dec 11 21:12:14 ppp: [wan_link0] LCP: no reply to 2 echo request(s) Dec 11 21:12:24 ppp: [wan_link0] LCP: no reply to 3 echo request(s) Dec 11 21:12:34 ppp: [wan_link0] LCP: no reply to 4 echo request(s) Dec 11 21:12:44 ppp: [wan_link0] LCP: no reply to 5 echo request(s) Dec 11 21:12:44 ppp: [wan_link0] LCP: peer not responding to echo requests Dec 11 21:12:44 ppp: [wan_link0] LCP: state change Opened --> Stopping
I will just point out that Link Control Protocol (LCP) are control packets embedded in PPP to control and monitor the link just from your device (pfSense in this case) to the ISP's connection point - just a single point-to-point hop.
http://en.wikipedia.org/wiki/Link_Control_ProtocolThese are like "ping" at a lower and more local level. It is saying that the ISP end has stopped responding.
Since putting Windows or some other device in place of pfSense works, then I guess there (must?) be some interoperability thing between the implementation of PPP+LCP FreeBSD/pfSense and in Windows. It would require some detailed capture of exactly what is going across the wire in PPP packets to analyse that.Having given no practical pointer to a solution, I shall press "Post" and go to sleep :(
-
:) Good point.
I don't think we've had a definitive answer as to whether it stays up using the Windows PPPoE client yet.
What we have had is a number of posts on the forum complaining about bad BT connections in recent days. Coincidence? ;)Steve
-
:) Good point.
I don't think we've had a definitive answer as to whether it stays up using the Windows PPPoE client yet.
What we have had is a number of posts on the forum complaining about bad BT connections in recent days. Coincidence? ;)Steve
Sorry for the delay in responding, I've been trying different things, currently back to HomeHub with a stable connection, as I have tried rebuilding the PPPoE connection, fresh install of pfSense, swapping the NICs round all still result in bouncy connections.
All tests I have done have been stable when connected directly to Windows PC, but I have not had chance to leave this for a whole day yet. I will be away for a few weeks and need reliable access back into the network, so will start trying to resolve this again in the new year.
Any further ideas welcome.
-
You dont say which BT router you are using.
I know the BT Business 2wire router has bugs in the software which forced me to abandon it when you run it in bridge mode,, namely if it lost power your settings would be lost plus BT can also remotely override your settings, so if you switched off the wifi on the router, you would see this being switched back on usually within a day but could be as quickly as a few hours.
http://www.nairod.co.uk/mountain-lion-download-problems-and-bt-business-2-wire-routers/
-
You dont say which BT router you are using.
I know the BT Business 2wire router has bugs in the software which forced me to abandon it when you run it in bridge mode,, namely if it lost power your settings would be lost plus BT can also remotely override your settings, so if you switched off the wifi on the router, you would see this being switched back on usually within a day but could be as quickly as a few hours.
http://www.nairod.co.uk/mountain-lion-download-problems-and-bt-business-2-wire-routers/
Sorry thought I'd mentioned earlier or in OP. It's a HomeHub4 it has no concept of bridge mode or I'd just use that
-
As Phil pointed out earlier you are seeing a failure of the PPPoE connection at a low level. I would be suspicious of the tp-link device which has to bridge the pppoe to pppoa. I think you will have to prove that device by connecting through it with something else. Either directly through Windos pppoe client or the homehib can do pppoe if want to try that.
Steve
-
As Phil pointed out earlier you are seeing a failure of the PPPoE connection at a low level. I would be suspicious of the tp-link device which has to bridge the pppoe to pppoa. I think you will have to prove that device by connecting through it with something else. Either directly through Windos pppoe client or the homehib can do pppoe if want to try that.
Steve
Hi everyone, sorry for the long delay in getting back to you, been very busy, so I've moved to Plusnet to get a Static IP and half my bill, still experiencing same problems. I have upgraded to 2.2-RELEASE (amd64).
Earlier I connected directly using the TP-Link and plugged the Ethernet into my Asus RT-AC68U. Within 30 minutes the same problem occurred and did not reconnect after 10 minutes, now back in bridge mode and plugged back into pfSense.
The log from the TP-Link says
2/25/2015 12:19:20> Last errorlog repeat 6 Times 2/25/2015 12:19:20> Call Failed 2/25/2015 12:19:20> netMakeChannDial: err=-3000 rn_p=8043336c 2/25/2015 12:19:26> Last errorlog repeat 15 Times 2/25/2015 12:19:27> netMakeChannDial: err=-3000 rn_p=8043336c 2/25/2015 12:19:27> Last errorlog repeat 1 Times 2/25/2015 12:19:28> netMakeChannDial: err=-3000 rn_p=8043336c 2/25/2015 12:19:38> Last errorlog repeat 16 Times 2/25/2015 12:19:39> netMakeChannDial: err=-3000 rn_p=8043336c 2/25/2015 12:19:39> Last errorlog repeat 2 Times 2/25/2015 12:19:41> netMakeChannDial: err=-3000 rn_p=8043336c 2/25/2015 12:19:43> Last errorlog repeat 3 Times 2/25/2015 12:19:44> netMakeChannDial: err=-3000 rn_p=8043336c 2/25/2015 12:19:51> Last errorlog repeat 20 Times 2/25/2015 12:19:51> Call Failed 2/25/2015 12:19:52> netMakeChannDial: err=-3000 rn_p=8043336c
Must have been luck when worked on Windows, or Windows is better at reconnecting quickly.
Any recommendations? I can think of two:
RMA TP-Link for replacement
RMA TP-Link for Return and get a different Modem (any suggestions on which?) -
Hmm, interesting. At least you've proved it's not a pfSense specific issue.
I'm on Plusnet and seeing very few issues. However if you are you should get on to their support forum and ask because they have real people with real technical knowledge there who will help. One of their support guys went to amazing lengths to pin down a fault I found.Are you on fibre? I used a V120 with their adsl2 service for years.
Steve
-
Hmm, interesting. At least you've proved it's not a pfSense specific issue.
I'm on Plusnet and seeing very few issues. However if you are you should get on to their support forum and ask because they have real people with real technical knowledge there who will help. One of their support guys went to amazing lengths to pin down a fault I found.Are you on fibre? I used a V120 with their adsl2 service for years.
Steve
Thanks Steve, moving discussion over to Plusnet Support Forum http://community.plus.net/forum/index.php/topic,137223.0.html