Netgate SG-1000 microFirewall

Author Topic: PPPoE issues since 2.4  (Read 367 times)

0 Members and 1 Guest are viewing this topic.

Offline Stealth1081

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
PPPoE issues since 2.4
« on: February 03, 2018, 09:37:34 am »
Hello all.

So to start due to my limited understanding of pfsense internal workings i have thus far been unable to determine if its pfsense losing the PPPoE connection or if i am losing the dsl sync on the modem.

From the log file i am getting several drops and it seems to be trying to use IPv6 even though it is disabled so not really sure what is going on.

Any enlightenment or help appreciated.



Log of the PPP below. - previous drop.

Feb 3 12:17:39   ppp      [wan] 217.42.170.107 -> 172.16.14.1
Feb 3 12:17:39   ppp      [wan] IPCP: LayerUp
Feb 3 12:17:39   ppp      [wan] IPCP: state change Ack-Sent --> Opened
Feb 3 12:17:39   ppp      [wan] IPADDR 217.42.170.107
Feb 3 12:17:39   ppp      [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Feb 3 12:17:39   ppp      [wan] IPADDR 217.42.170.107
Feb 3 12:17:39   ppp      [wan] IPCP: SendConfigReq #3
Feb 3 12:17:39   ppp      [wan] 217.42.170.107 is OK
Feb 3 12:17:39   ppp      [wan] IPADDR 217.42.170.107
Feb 3 12:17:39   ppp      [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
Feb 3 12:17:39   ppp      [wan] IFACE: Rename interface ng0 to pppoe0
Feb 3 12:17:39   ppp      [wan] IFACE: Up event
Feb 3 12:17:39   ppp      [wan] 428d:5cff:fea5:688c -> 0221:05ff:fe76:bc34
Feb 3 12:17:39   ppp      [wan] IPV6CP: LayerUp
Feb 3 12:17:39   ppp      [wan] IPV6CP: state change Ack-Sent --> Opened
Feb 3 12:17:39   ppp      [wan] IPV6CP: rec'd Configure Ack #1 (Ack-Sent)
Feb 3 12:17:39   ppp      [wan] IPADDR 0.0.0.0
Feb 3 12:17:39   ppp      [wan] IPCP: SendConfigReq #2
Feb 3 12:17:39   ppp      [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Feb 3 12:17:39   ppp      [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
Feb 3 12:17:39   ppp      [wan] IPCP: state change Req-Sent --> Ack-Sent
Feb 3 12:17:39   ppp      [wan] IPADDR 172.16.14.1
Feb 3 12:17:39   ppp      [wan] IPCP: SendConfigAck #162
Feb 3 12:17:39   ppp      [wan] 172.16.14.1 is OK
Feb 3 12:17:39   ppp      [wan] IPADDR 172.16.14.1
Feb 3 12:17:39   ppp      [wan] IPCP: rec'd Configure Request #162 (Req-Sent)
Feb 3 12:17:39   ppp      [wan] IPV6CP: state change Req-Sent --> Ack-Sent
Feb 3 12:17:39   ppp      [wan] IPV6CP: SendConfigAck #43
Feb 3 12:17:39   ppp      [wan] IPV6CP: rec'd Configure Request #43 (Req-Sent)
Feb 3 12:17:39   ppp      [wan] IPV6CP: SendConfigReq #1
Feb 3 12:17:39   ppp      [wan] IPV6CP: state change Starting --> Req-Sent
Feb 3 12:17:39   ppp      [wan] IPV6CP: Up event
Feb 3 12:17:39   ppp      [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Feb 3 12:17:39   ppp      [wan] IPADDR 0.0.0.0
Feb 3 12:17:39   ppp      [wan] IPCP: SendConfigReq #1
Feb 3 12:17:39   ppp      [wan] IPCP: state change Starting --> Req-Sent
Feb 3 12:17:39   ppp      [wan] IPCP: Up event
Feb 3 12:17:39   ppp      [wan] IPV6CP: LayerStart
Feb 3 12:17:39   ppp      [wan] IPV6CP: state change Initial --> Starting
Feb 3 12:17:39   ppp      [wan] IPV6CP: Open event
Feb 3 12:17:39   ppp      [wan] IPCP: LayerStart
Feb 3 12:17:39   ppp      [wan] IPCP: state change Initial --> Starting
Feb 3 12:17:39   ppp      [wan] IPCP: Open event
Feb 3 12:17:39   ppp      [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Feb 3 12:17:39   ppp      [wan_link0] Link: Join bundle "wan"
Feb 3 12:17:39   ppp      [wan_link0] Link: Matched action 'bundle "wan" ""'
Feb 3 12:17:39   ppp      [wan_link0] LCP: authorization successful
Feb 3 12:17:39   ppp      [wan_link0] MESG: CHAP authentication success
Feb 3 12:17:39   ppp      [wan_link0] CHAP: rec'd SUCCESS #1 len: 31
Feb 3 12:17:39   ppp      [wan_link0] CHAP: sending RESPONSE #1 len: 45
Feb 3 12:17:39   ppp      [wan_link0] CHAP: Using authname "bthomehub@btinternet.com"
Feb 3 12:17:39   ppp      [wan_link0] Name: "acc-aln1.do"
Feb 3 12:17:39   ppp      [wan_link0] CHAP: rec'd CHALLENGE #1 len: 55
Feb 3 12:17:39   ppp      [wan_link0] LCP: LayerUp
Feb 3 12:17:39   ppp      [wan_link0] LCP: auth: peer wants CHAP, I want nothing
Feb 3 12:17:39   ppp      [wan_link0] LCP: state change Ack-Sent --> Opened
Feb 3 12:17:39   ppp      [wan_link0] MAGICNUM 0x610f60cd
Feb 3 12:17:39   ppp      [wan_link0] MRU 1492
Feb 3 12:17:39   ppp      [wan_link0] LCP: rec'd Configure Ack #2 (Ack-Sent)
Feb 3 12:17:39   ppp      [wan_link0] MAGICNUM 0x610f60cd
Feb 3 12:17:39   ppp      [wan_link0] MRU 1492
Feb 3 12:17:39   ppp      [wan_link0] LCP: SendConfigReq #2
Feb 3 12:17:39   ppp      [wan_link0] PROTOCOMP
Feb 3 12:17:39   ppp      [wan_link0] LCP: rec'd Configure Reject #1 (Ack-Sent)
Feb 3 12:17:39   ppp      [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Feb 3 12:17:39   ppp      [wan_link0] MAGICNUM 0x40193235
Feb 3 12:17:39   ppp      [wan_link0] AUTHPROTO CHAP MD5
Feb 3 12:17:39   ppp      [wan_link0] MRU 1492
Feb 3 12:17:39   ppp      [wan_link0] LCP: SendConfigAck #237
Feb 3 12:17:39   ppp      [wan_link0] MAGICNUM 0x40193235
Feb 3 12:17:39   ppp      [wan_link0] AUTHPROTO CHAP MD5
Feb 3 12:17:39   ppp      [wan_link0] MRU 1492
Feb 3 12:17:39   ppp      [wan_link0] LCP: rec'd Configure Request #237 (Req-Sent)
Feb 3 12:17:39   ppp      [wan_link0] MAGICNUM 0x610f60cd
Feb 3 12:17:39   ppp      [wan_link0] MRU 1492
Feb 3 12:17:39   ppp      [wan_link0] PROTOCOMP
Feb 3 12:17:39   ppp      [wan_link0] LCP: SendConfigReq #1
Feb 3 12:17:39   ppp      [wan_link0] LCP: state change Starting --> Req-Sent
Feb 3 12:17:39   ppp      [wan_link0] LCP: Up event
Feb 3 12:17:39   ppp      [wan_link0] Link: UP event
Feb 3 12:17:39   ppp      [wan_link0] PPPoE: connection successful
Feb 3 12:17:39   ppp      PPPoE: rec'd ACNAME "acc-aln1.do"
Feb 3 12:17:37   ppp      [wan_link0] PPPoE: Connecting to ''
Feb 3 12:17:37   ppp      [wan_link0] Link: reconnection attempt 3
Feb 3 12:17:36   ppp      [wan_link0] Link: reconnection attempt 3 in 1 seconds
Feb 3 12:17:36   ppp      [wan_link0] LCP: Down event
Feb 3 12:17:36   ppp      [wan_link0] Link: DOWN event
Feb 3 12:17:36   ppp      [wan_link0] PPPoE connection timeout after 9 seconds
Feb 3 12:17:27   ppp      [wan_link0] PPPoE: Connecting to ''
Feb 3 12:17:27   ppp      [wan_link0] Link: reconnection attempt 2
Feb 3 12:17:26   ppp      [wan_link0] Link: reconnection attempt 2 in 1 seconds
Feb 3 12:17:26   ppp      [wan_link0] LCP: Down event
Feb 3 12:17:26   ppp      [wan_link0] Link: DOWN event
Feb 3 12:17:26   ppp      [wan_link0] PPPoE connection timeout after 9 seconds
Feb 3 12:17:17   ppp      [wan_link0] PPPoE: Connecting to ''
Feb 3 12:17:17   ppp      [wan_link0] Link: reconnection attempt 1
Feb 3 12:17:13   ppp      [wan_link0] Link: reconnection attempt 1 in 4 seconds
Feb 3 12:17:13   ppp      [wan_link0] LCP: Down event
Feb 3 12:17:13   ppp      [wan_link0] Link: DOWN event
Feb 3 12:17:13   ppp      [wan_link0] PPPoE connection timeout after 9 seconds
Feb 3 12:17:04   ppp      [wan_link0] PPPoE: Connecting to ''
Feb 3 12:17:04   ppp      [wan_link0] LCP: LayerStart
Feb 3 12:17:04   ppp      [wan_link0] LCP: state change Initial --> Starting
Feb 3 12:17:04   ppp      [wan_link0] LCP: Open event
Feb 3 12:17:04   ppp      [wan_link0] Link: OPEN event
Feb 3 12:17:04   ppp      [wan] Bundle: Interface ng0 created
Feb 3 12:17:04   ppp      web: web is not running
Feb 3 12:17:03   ppp      process 71391 terminated
Feb 3 12:17:03   ppp      [wan_link0] Link: Shutdown
Feb 3 12:17:03   ppp      [wan] Bundle: Shutdown
Feb 3 12:17:03   ppp      [wan] IPV6CP: rec'd Configure Request #45 (Closing)
Feb 3 12:17:03   ppp      [wan] IPCP: SendTerminateReq #14
Feb 3 12:17:03   ppp      waiting for process 71391 to die...
Feb 3 12:17:03   ppp      [wan] IPV6CP: SendTerminateReq #10
Feb 3 12:17:02   ppp      waiting for process 71391 to die...
Feb 3 12:17:02   ppp      [wan] IPCP: rec'd Configure Request #57 (Closing)
Feb 3 12:17:01   ppp      [wan] IFACE: Rename interface pppoe0 to pppoe0
Feb 3 12:17:01   ppp      [wan] IFACE: Down event
Feb 3 12:17:01   ppp      [wan] IPV6CP: LayerDown
Feb 3 12:17:01   ppp      [wan] IPV6CP: SendTerminateReq #9
Feb 3 12:17:01   ppp      [wan] IPV6CP: state change Opened --> Closing
Feb 3 12:17:01   ppp      [wan] IPV6CP: Close event
Feb 3 12:17:01   ppp      [wan] IPCP: SendTerminateReq #13
Feb 3 12:17:01   ppp      [wan] IPCP: state change Ack-Sent --> Closing
Feb 3 12:17:01   ppp      [wan] IPCP: Close event
Feb 3 12:17:01   ppp      [wan] IFACE: Close event
Feb 3 12:17:01   ppp      caught fatal signal TERM
Feb 3 12:17:01   ppp      waiting for process 71391 to die...
Feb 3 12:17:01   ppp      process 49145 started, version 5.8 (nobody@pfSense_v2_4_1_amd64-pfSense_v2_4_1-job-01 16:32 21-Oct-2017)
Feb 3 12:17:01   ppp      Multi-link PPP daemon for FreeBSD
Feb 3 12:17:01   ppp      [wan] IFACE: Rename interface ng0 to pppoe0
Feb 3 12:17:01   ppp      [wan] IFACE: Up event
Feb 3 12:17:00   ppp      [wan] 428d:5cff:fea5:688c -> 0221:05ff:fe76:bc34
Feb 3 12:17:00   ppp      [wan] IPV6CP: LayerUp
Feb 3 12:17:00   ppp      [wan] IPV6CP: state change Ack-Sent --> Opened
Feb 3 12:17:00   ppp      [wan] IPV6CP: rec'd Configure Ack #8 (Ack-Sent)
Feb 3 12:17:00   ppp      [wan] IPV6CP: state change Opened --> Ack-Sent
Feb 3 12:17:00   ppp      [wan] IPV6CP: SendConfigAck #45
Feb 3 12:17:00   ppp      [wan] IPV6CP: SendConfigReq #8
Feb 3 12:17:00   ppp      [wan] IFACE: Rename interface pppoe0 to pppoe0
Feb 3 12:17:00   ppp      [wan] IFACE: Down event


Offline Gertjan

  • Hero Member
  • *****
  • Posts: 2433
  • Karma: +191/-9
    • View Profile
Re: PPPoE issues since 2.4
« Reply #1 on: February 03, 2018, 01:13:25 pm »
Hi,
This line at the top is the most recent line, right ?
Code: [Select]
Feb 3 12:17:39   ppp      [wan] 217.42.170.107 -> 172.16.14.1If so, you showed a perfect example of a successful pppoe connection establishment - IPv6 included.
The link is up - all seems fine to me.

If something made drop the connection, it happens later on.

Offline Stealth1081

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: PPPoE issues since 2.4
« Reply #2 on: February 03, 2018, 01:23:28 pm »
Thanks for the reply.

I thought that showed a complete drop to a reconnect below is the current connection up until it starts getting IP info.

Feb 3 12:20:46 is when i lost the connection again. Posted 2 line from previous log for comparison.

I still don't know why there is any IPv6 because it is disable.

Feb 3 12:20:57   ppp      [wan] IPCP: rec'd Configure Request #142 (Req-Sent)
Feb 3 12:20:57   ppp      [wan] IPV6CP: state change Req-Sent --> Ack-Sent
Feb 3 12:20:57   ppp      [wan] IPV6CP: SendConfigAck #246
Feb 3 12:20:57   ppp      [wan] IPV6CP: rec'd Configure Request #246 (Req-Sent)
Feb 3 12:20:57   ppp      [wan] IPV6CP: SendConfigReq #3
Feb 3 12:20:57   ppp      [wan] IPV6CP: state change Starting --> Req-Sent
Feb 3 12:20:57   ppp      [wan] IPV6CP: Up event
Feb 3 12:20:57   ppp      [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Feb 3 12:20:57   ppp      [wan] IPADDR 0.0.0.0
Feb 3 12:20:57   ppp      [wan] IPCP: SendConfigReq #5
Feb 3 12:20:57   ppp      [wan] IPCP: state change Starting --> Req-Sent
Feb 3 12:20:57   ppp      [wan] IPCP: Up event
Feb 3 12:20:57   ppp      [wan] IPV6CP: LayerStart
Feb 3 12:20:57   ppp      [wan] IPV6CP: state change Initial --> Starting
Feb 3 12:20:57   ppp      [wan] IPV6CP: Open event
Feb 3 12:20:57   ppp      [wan] IPCP: LayerStart
Feb 3 12:20:57   ppp      [wan] IPCP: state change Initial --> Starting
Feb 3 12:20:57   ppp      [wan] IPCP: Open event
Feb 3 12:20:57   ppp      [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Feb 3 12:20:57   ppp      [wan_link0] Link: Join bundle "wan"
Feb 3 12:20:57   ppp      [wan_link0] Link: Matched action 'bundle "wan" ""'
Feb 3 12:20:57   ppp      [wan_link0] LCP: authorization successful
Feb 3 12:20:57   ppp      [wan_link0] MESG: CHAP authentication success
Feb 3 12:20:57   ppp      [wan_link0] CHAP: rec'd SUCCESS #1 len: 31
Feb 3 12:20:57   ppp      [wan_link0] CHAP: sending RESPONSE #1 len: 45
Feb 3 12:20:57   ppp      [wan_link0] CHAP: Using authname "bthomehub@btinternet.com"
Feb 3 12:20:57   ppp      [wan_link0] Name: "acc-aln1.do"
Feb 3 12:20:57   ppp      [wan_link0] CHAP: rec'd CHALLENGE #1 len: 53
Feb 3 12:20:57   ppp      [wan_link0] LCP: LayerUp
Feb 3 12:20:57   ppp      [wan_link0] LCP: auth: peer wants CHAP, I want nothing
Feb 3 12:20:57   ppp      [wan_link0] LCP: state change Ack-Sent --> Opened
Feb 3 12:20:57   ppp      [wan_link0] MAGICNUM 0xe9801181
Feb 3 12:20:57   ppp      [wan_link0] MRU 1492
Feb 3 12:20:57   ppp      [wan_link0] LCP: rec'd Configure Ack #4 (Ack-Sent)
Feb 3 12:20:57   ppp      [wan_link0] MAGICNUM 0xe9801181
Feb 3 12:20:57   ppp      [wan_link0] MRU 1492
Feb 3 12:20:57   ppp      [wan_link0] LCP: SendConfigReq #4
Feb 3 12:20:57   ppp      [wan_link0] PROTOCOMP
Feb 3 12:20:57   ppp      [wan_link0] LCP: rec'd Configure Reject #3 (Ack-Sent)
Feb 3 12:20:57   ppp      [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Feb 3 12:20:57   ppp      [wan_link0] MAGICNUM 0x0562dfdd
Feb 3 12:20:57   ppp      [wan_link0] AUTHPROTO CHAP MD5
Feb 3 12:20:57   ppp      [wan_link0] MRU 1492
Feb 3 12:20:57   ppp      [wan_link0] LCP: SendConfigAck #223
Feb 3 12:20:57   ppp      [wan_link0] MAGICNUM 0x0562dfdd
Feb 3 12:20:57   ppp      [wan_link0] AUTHPROTO CHAP MD5
Feb 3 12:20:57   ppp      [wan_link0] MRU 1492
Feb 3 12:20:57   ppp      [wan_link0] LCP: rec'd Configure Request #223 (Req-Sent)
Feb 3 12:20:57   ppp      [wan_link0] MAGICNUM 0xe9801181
Feb 3 12:20:57   ppp      [wan_link0] MRU 1492
Feb 3 12:20:57   ppp      [wan_link0] PROTOCOMP
Feb 3 12:20:57   ppp      [wan_link0] LCP: SendConfigReq #3
Feb 3 12:20:57   ppp      [wan_link0] LCP: state change Starting --> Req-Sent
Feb 3 12:20:57   ppp      [wan_link0] LCP: Up event
Feb 3 12:20:57   ppp      [wan_link0] Link: UP event
Feb 3 12:20:57   ppp      [wan_link0] PPPoE: connection successful
Feb 3 12:20:57   ppp      PPPoE: rec'd ACNAME "acc-aln1.do"
Feb 3 12:20:51   ppp      [wan_link0] PPPoE: Connecting to ''
Feb 3 12:20:51   ppp      [wan_link0] Link: reconnection attempt 1
Feb 3 12:20:47   ppp      [wan_link0] Link: reconnection attempt 1 in 4 seconds
Feb 3 12:20:47   ppp      [wan_link0] LCP: LayerDown
Feb 3 12:20:47   ppp      [wan] IPV6CP: state change Closing --> Initial
Feb 3 12:20:47   ppp      [wan] Bundle: No NCPs left. Closing links...
Feb 3 12:20:47   ppp      [wan] IPV6CP: LayerFinish
Feb 3 12:20:47   ppp      [wan] IPV6CP: Down event
Feb 3 12:20:47   ppp      [wan] IPCP: state change Closing --> Initial
Feb 3 12:20:47   ppp      [wan] IPCP: LayerFinish
Feb 3 12:20:47   ppp      [wan] IPCP: Down event
Feb 3 12:20:47   ppp      [wan] IFACE: Rename interface pppoe0 to pppoe0
Feb 3 12:20:47   ppp      [wan] IFACE: Down event
Feb 3 12:20:46   ppp      [wan] IPV6CP: LayerDown
Feb 3 12:20:46   ppp      [wan] IPV6CP: SendTerminateReq #2
Feb 3 12:20:46   ppp      [wan] IPV6CP: state change Opened --> Closing
Feb 3 12:20:46   ppp      [wan] IPV6CP: Close event
Feb 3 12:20:46   ppp      [wan] IPCP: LayerDown
Feb 3 12:20:46   ppp      [wan] IPCP: SendTerminateReq #4
Feb 3 12:20:46   ppp      [wan] IPCP: state change Opened --> Closing
Feb 3 12:20:46   ppp      [wan] IPCP: Close event
Feb 3 12:20:46   ppp      [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Feb 3 12:20:46   ppp      [wan_link0] Link: Leave bundle "wan"
Feb 3 12:20:46   ppp      [wan_link0] LCP: state change Opened --> Starting
Feb 3 12:20:46   ppp      [wan_link0] LCP: Down event
Feb 3 12:20:46   ppp      [wan_link0] Link: DOWN event
Feb 3 12:20:46   ppp      [wan_link0] PPPoE: connection closed
Feb 3 12:17:39   ppp      [wan] 217.42.170.107 -> 172.16.14.1
Feb 3 12:17:39   ppp      [wan] IPCP: LayerUp


Offline Gertjan

  • Hero Member
  • *****
  • Posts: 2433
  • Karma: +191/-9
    • View Profile
Re: PPPoE issues since 2.4
« Reply #3 on: February 03, 2018, 01:31:32 pm »
At the bottom, inversed  :

Code: [Select]
Feb 3 12:17:39   ppp      [wan] IPCP: LayerUp
Feb 3 12:17:39   ppp      [wan] 217.42.170.107 -> 172.16.14.1
Connection ok for 3 minutes.
And then :
Code: [Select]
Feb 3 12:20:46   ppp      [wan_link0] PPPoE: connection closed
I don't know why the connection was closed. I mean, if this is a programmed "clean" shutdown, or the result of a 'modem' that runs out of sync, bad line, etc.

I used a pppoe connection for many years - and my ISP send a "connection shut down command" every 7 days sharp - pfSense rebuild the connection straight away, and I was good for another week.

edit : possible to look closely at your "modem" to see if it has any "carrier" or "sync" led ? Has it a GUI - I could access my modem back then, I assigned it an IP like 10.0.0.1 on iy's LAN and put an IP like 10.0.0.138 on the WAN NIC of pfSense, some NAT rules (if I remember well) and I could checkout the GUI of my modem which had some indication about dB, line noise, sync speed, errors, etc.
« Last Edit: February 03, 2018, 01:34:57 pm by Gertjan »

Offline Stealth1081

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: PPPoE issues since 2.4
« Reply #4 on: February 03, 2018, 01:43:36 pm »
Thanks for the reply.

I have recently replaced the modem with a vigor 130 as i thought my old openreach modem was on its last legs but they both do the same thing.

Line stats from Vigor

> vdsl status

  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 32324000 bps   US Actual Rate       :  6633000 bps
   DS Attainable Rate      : 38224168 bps   US Attainable Rate   :  6888420 bps
   DS Path Mode            :  Interleave    US Path Mode         :        Fast
   DS Interleave Depth     :      471       US Interleave Depth  :        1
   NE Current Attenuation  :       22 dB    Cur SNR Margin       :        5  dB
   DS actual PSD           :     5. 6 dB    US actual PSD        :     5. 7  dB
   NE CRC Count            :      461       FE CRC Count         :      185
   NE ES Count             :      145       FE  ES Count         :      178
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : b5004946       ITU Version[1]       : 544e0000
   VDSL Firmware Version   : 05-07-06-0D-01-07   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       30 dB    Far SNR Margin       :        6  dB
   CO ITU Version[0]       : b5004946       CO ITU Version[1]    : 544eb206
   DSLAM CHIPSET VENDOR    : < IFTN >

I mention the IPv6 because i have not had a problem up until it started appearing in the logs. It wasn't uncommon to have my connection up for over 30 days.

In Interfaces/WAN

IPv6 Configuration Type - None

I don't use it on my LAN either

I may just have to connect the BT home hub and run dual NAT for awhile then fight BT as they have been there usual helpful selves.

Offline Stealth1081

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: PPPoE issues since 2.4
« Reply #5 on: February 03, 2018, 01:46:32 pm »
Edit

I have yet to figure out how to view how long the modem has been synced so i could see if they drop at the same time.

Offline hda

  • Sr. Member
  • ****
  • Posts: 599
  • Karma: +32/-4
    • View Profile
Re: PPPoE issues since 2.4
« Reply #6 on: February 03, 2018, 05:58:09 pm »
Strange. Is private 172.16.14.1 the gateway of your ISP ? Where is that number located.
Do you have the DrayTek Vigor130 doing the PPPoE and the again PPPoE from pfSense to Vigor ?

But can't you put the Vigor130 in bridge mode and pass-through,
then have PPPoE public 217.xy.abc.107 to pfSense-WAN with a *public* gateway ?
« Last Edit: February 03, 2018, 06:01:31 pm by hda »

Offline Stealth1081

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: PPPoE issues since 2.4
« Reply #7 on: February 03, 2018, 09:42:56 pm »
 Thanks for the reply.

No idea why that address is appearing as you say it's a private address range. May have something to do with openvpn but don't know enough about it.

As for the vigor it is set to bridge mode. Pfsense does the pppoe stuff.

Either there is a line issue or starting to think something got messed up in the upgrade to 2.4.

Just found a box to drop all ipv6 in the advanced section will see if it helps but the ppp log still shows it getting an ipv6 address.

Offline Sysyphus

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-1
    • View Profile
Re: PPPoE issues since 2.4
« Reply #8 on: February 04, 2018, 03:17:51 am »
The Vigor130 has a Web GUI front-end this should show the uptime of the modem.

Do you need IPv6, have you tried just using IPv4 until everything is "settled"?

Offline Stealth1081

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: PPPoE issues since 2.4
« Reply #9 on: February 04, 2018, 07:06:03 am »
Thanks for the reply

Which section is that under in the vigor. I must of missed it as don't see it.

As for IPv6 I don't currently need it which is why it is already set to none on the lan and wan. Yet the wan still gets an IPv6 address.

Offline Sysyphus

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-1
    • View Profile
Re: PPPoE issues since 2.4
« Reply #10 on: February 04, 2018, 02:08:55 pm »
You need to setup an outband NAT in pfSense to access the modem - Click here

Once you logon to the Vigor 130 modem, you will be at the dashboard, you will see the uptime in hours-minutes-seconds,another point is to make sure that you have the most up-to-date firmware.

From the dashboard you can navigate on the left to Online Status -> Physical Connection


Offline Sysyphus

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-1
    • View Profile
Re: PPPoE issues since 2.4
« Reply #11 on: February 04, 2018, 02:39:31 pm »
Additionally, from a telnet session to the Vigor 130, type the command:   show status

The first line of the output will show the uptime

Offline Grimson

  • Sr. Member
  • ****
  • Posts: 310
  • Karma: +46/-3
    • View Profile
Re: PPPoE issues since 2.4
« Reply #12 on: February 04, 2018, 03:56:22 pm »
Uptime is how long the Vigor is running, it is not affected by the DSL sync.

You can send syslog messages, with DSL information, to a device on your network, then you can filter them and see when DSL goes through a resync.

Offline muppet

  • Newbie
  • *
  • Posts: 23
  • Karma: +1/-0
  • I'm a Muppet
    • View Profile
    • Tim H
Re: PPPoE issues since 2.4
« Reply #13 on: February 06, 2018, 06:25:15 pm »
I would run a tcpdump (Diagnostics->Packet Capture) on the WAN interface of the pfSense while this fault is happening.

Posting that to a pastebin where we can look at it would be helpful (you'll have to scrub any passwords etc, be careful here before just blindly pasting)

Offline Stealth1081

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: PPPoE issues since 2.4
« Reply #14 on: February 11, 2018, 05:29:07 pm »
Thanks for the reply's.

Been very busy the last week and most of next week.

Will have to put up with it for awile untill I can try out your suggestions and get the log files.

Will post again when have them.