Draytek Vigor 130 + PFSense constantly reconnecting via PPoE

[#1]

I switched to Plusnet earlier this week.

I'm using a Draytek Vigor 130 connected directly to the pfSense box (Protectli clone) on the WAN port.

The Draytek is configured in bridge mode with Service VLAN tag set to 101 and MTU 1500.

I've configured a static address on the WAN port of the pfSense box for UI access of the Draytek modem  on 192.168.2.1 address

I've then configured the PPoE connection on the WAN port using the username & pass from my account details.

I can bring up the PPoE connection and I am able to access the internet but the system logs are full of LCP down messages and reconnection notices

Sample below:

Mar 29 00:50:49	ppp	44599	[opt3_link0] LCP: Down event
Mar 29 00:50:49	ppp	44599	[opt3_link0] Link: reconnection attempt 696 in 2 seconds
Mar 29 00:50:51	ppp	44599	[opt3_link0] Link: reconnection attempt 696
Mar 29 00:50:51	ppp	44599	[opt3_link0] PPPoE: Set PPP-Max-Payload to '1500'
Mar 29 00:50:51	ppp	44599	[opt3_link0] PPPoE: Connecting to ''
Mar 29 00:51:00	ppp	44599	[opt3_link0] PPPoE connection timeout after 9 seconds
Mar 29 00:51:00	ppp	44599	[opt3_link0] Link: DOWN event
Mar 29 00:51:00	ppp	44599	[opt3_link0] LCP: Down event
Mar 29 00:51:00	ppp	44599	[opt3_link0] Link: reconnection attempt 697 in 4 seconds
Mar 29 00:51:04	ppp	44599	[opt3_link0] Link: reconnection attempt 697
Mar 29 00:51:04	ppp	44599	[opt3_link0] PPPoE: Set PPP-Max-Payload to '1500'
Mar 29 00:51:04	ppp	44599	[opt3_link0] PPPoE: Connecting to ''
Mar 29 00:51:13	ppp	44599	[opt3_link0] PPPoE connection timeout after 9 seconds
Mar 29 00:51:13	ppp	44599	[opt3_link0] Link: DOWN event
Mar 29 00:51:13	ppp	44599	[opt3_link0] LCP: Down event
Mar 29 00:51:13	ppp	44599	[opt3_link0] Link: reconnection attempt 698 in 1 seconds
Mar 29 00:51:14	ppp	44599	[opt3_link0] Link: reconnection attempt 698
Mar 29 00:51:14	ppp	44599	[opt3_link0] PPPoE: Set PPP-Max-Payload to '1500'
Mar 29 00:51:14	ppp	44599	[opt3_link0] PPPoE: Connecting to ''
Mar 29 00:51:23	ppp	44599	[opt3_link0] PPPoE connection timeout after 9 seconds
Mar 29 00:51:23	ppp	44599	[opt3_link0] Link: DOWN event
Mar 29 00:51:23	ppp	44599	[opt3_link0] LCP: Down event
Mar 29 00:51:23	ppp	44599	[opt3_link0] Link: reconnection attempt 699 in 1 seconds
Mar 29 00:51:24	ppp	44599	[opt3_link0] Link: reconnection attempt 699
Mar 29 00:51:24	ppp	44599	[opt3_link0] PPPoE: Set PPP-Max-Payload to '1500'
Mar 29 00:51:24	ppp	44599	[opt3_link0] PPPoE: Connecting to ''
Mar 29 00:51:33	ppp	44599	[opt3_link0] PPPoE connection timeout after 9 seconds
Mar 29 00:51:33	ppp	44599	[opt3_link0] Link: DOWN event
Mar 29 00:51:33	ppp	44599	[opt3_link0] LCP: Down event
Mar 29 00:51:33	ppp	44599	[opt3_link0] Link: reconnection attempt 700 in 1 seconds
Mar 29 00:51:34	ppp	44599	[opt3_link0] Link: reconnection attempt 700
Mar 29 00:51:34	ppp	44599	[opt3_link0] PPPoE: Set PPP-Max-Payload to '1500'
Mar 29 00:51:34	ppp	44599	[opt3_link0] PPPoE: Connecting to ''

So far I've tried v130_3851_579F17, v130_3841_579F17 and 3.8.5.1 firmware on the Draytek, played around with SNR values and disabled vectoring none of this seems to have helped reduce the number of disconnections. 

I've also played a fair bit with MTU sizes to no benefit. I've also disabled gateway monitoring in pfsense but again does not appear to have had any tangible impact.

DSL does seem to sync successfully:

  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 40557000 bps   US Actual Rate       : 13575000 bps
   DS Attainable Rate      : 40103880 bps   US Attainable Rate   : 13660662 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast 
   DS Interleave Depth     :        1       US Interleave Depth  :        1 
   NE Current Attenuation  :       15 dB    Cur SNR Margin       :        9  dB
   DS actual PSD           :     6. 5 dB    US actual PSD        :    13. 3  dB
   NE CRC Count            :        0       FE CRC Count         :     6123
   NE ES Count             :        0       FE  ES Count         :     4835
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : fe004452       ITU Version[1]       : 41590000
   VDSL Firmware Version   : 05-07-09-0F-01-07   [with Vectoring support] 
   Power Management Mode   : DSL_G997_PMS_L0 
   Test Mode               : DISABLE 
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       23 dB    Far SNR Margin       :        6  dB
   CO ITU Version[0]       : b5004946       CO ITU Version[1]    : 544ed086
   DSLAM CHIPSET VENDOR    : < IFTN >

Any help advice would be appreciated.

[#2]

Moderator's note:
Post released from the automatic Spam Filter.

[#3]

When I was with Plusnet FTTC, I used a Vigor 130 with pfSense for years.

Is your static WAN port setup like this ? - Netgate : Accessing a CPE/Modem from Inside the Firewall 

I have seen the problem you're describing when the pfSense WAN ethernet sees a mismatch of PPPoE MTU and the static IP WAN port MTU, using the same physical interface port, when attempting to use PPPoE jumbo frames.  For example, the WAN static IP port might have an MTU=1500, but the PPPoE MTU=1508, causing the ethernet port to repeatedly reboot.  Oddly even when there is an MTU mismatch, rebooting pfSense does allow the WAN connection to start up and work, but will break again as soon as there is an an attempt to restart the PPPoE after a line disconnection !

Leaving pfSense's WAN MTU and MSS blank works for me -

[#4]

Cheers for the response PlanetX

Yeah that was the guide I followed to get the WebUI Accesible initially.

Here are my current settings- to the best of my knowledge match the guide. 

ModemManagement Interface

ModemManagement Interface

The WAN Interface looks like this

WAN InterfaceInterfaces

As you can see the PPoE is up but the logs are just being spammed with LCP Down events

I've experiemented with the baby jumbo frames before I reflashed the Vigor 130 with the alternative ECI firmware which limits to 1500 MTU and that didn't really seem to help.

Anything you can spot?

[#5]

What error messages do you see if you click on the red bell icon on the pfSense screen top right ?

Was this same setup working OK with your previous ISP ?

The only thing I can see so far that caught my eye is your modem stats -

        "NE Current Attenuation : 15 dB    Cur SNR Margin : 9  dB"

I have never seen a Vigor 130 with an SNR Margin of 9dB !,  I'm wondering if you have a VDSL line fault ?

My Vigor 130 typically sits around 4dB margin, at worst 6dB, and will hang on to sync until the margin is less than zero (negative).

Try running the Plusnet broadband fault detection 'bot', to see whether your line has an identifiable problem -

[#6]

@oakteryx Im no pfsense expert but those entries in the log don't (to me) seem connected with the primary WAN pppoe interface. The opt3_link0 and the 'connection to ""'  would seem to indicate that you may have another (hidden?) interface defined somewhere which is trying to make a pppoe connection ?

[#7]

Thanks again for your input PlanetX.

I was previously with Now Broadband and was unable to get the pfSense box + vigor working with their MER Authentication so this is a completely new setup in fairness.

Since I sent that first post appears the VDSL line has re-synced and looks a bit better now. Perhaps some noise on the line??? 

---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 59952000 bps US Actual Rate : 13235000 bps
DS Attainable Rate : 60958688 bps US Attainable Rate : 13251227 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 15 dB Cur SNR Margin : 3 dB
DS actual PSD : 6. 6 dB US actual PSD : 13. 8 dB
NE CRC Count : 0 FE CRC Count : 6125
NE ES Count : 0 FE ES Count : 4837
Xdsl Reset Times : 0 Xdsl Link Times : 2
ITU Version[0] : fe004452 ITU Version[1] : 41590000
VDSL Firmware Version : 05-07-09-0F-01-07 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 23 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544ed086
DSLAM CHIPSET VENDOR : < IFTN >

@Anonymous  With this new sync/connection settles still think there could be a fault? Still worth getting on with the bot?

@MisterW Keen eye there- I was confused by this initially but I've just run a TCP dump on each of the interfaces and the WAN Interface is the only one with PPoE traffic. Think it's fairly safe to say there isn't a second rogue PPoE connection going out?

[#8]

@oakteryx that log is definitely showing as from the opt3 interface. What have you got the opt3 interface configured as ?

This might help https://kb.protectli.com/kb/pfsense-optional-port-configuration/

but I've just run a TCP dump on each of the interfaces and the WAN Interface is the only one with PPoE traffic

Tcpdump possibly wont show any pppoe traffic, I suspect whatever it is, its not getting past the PADI broadcast

[#9]

---

@oakteryx wrote:

@Anonymous  With this new sync/connection settles still think there could be a fault? Still worth getting on with the bot?

That looks MUCH better, I'd be happy with that !

My thought about the 'bot', is that as you are new here, your line + phone socket cabling has never been tested (as it is now).

If you simply run the line checker, it costs nothing, it is easy to do, and it might highlight an as yet unidentified issue.

If it comes back with 'nothing found' then you have peace of mind that your new connection was seen to be OK today,  but equally if a 'fault' is detected then you can get it investigated sooner rather than later.

.

[#10]

It is odd- other than this log entry I can't see any reference to OPT3 on any of interfaces.  As far as I can see I don't have an OPT3 interface. Possibly some 'ghost' config?? 

I will remove all of my interfaces and re-add them this evening while nobody is online.

[#11]

Cheers @Anonymous  as a precaution I will kick off a bot test- as you say nothing to loose.

[#12]

What was the answer to my question about your pfSense error messages ?

---

@Anonymous wrote:

What error messages do you see if you click on the red bell icon on the pfSense screen top right ?

---

---

@oakteryx wrote:

---

[#13]

@Anonymous 

Sorry seem they to have disappeared since I rebooted it and no way to check historical notifications. I did read them and didn't think they had any relevance- maybe something to do about offer for Netgate support or changing the default password?

[#14]

---

@oakteryx wrote:

It is odd- other than this log entry I can't see any reference to OPT3 on any of interfaces.  As far as I can see I don't have an OPT3 interface.

---

Try selecting "Status" in the top menu bar, and selecting "Interfaces" from the drop down list.

If you then scroll down that screen, looking at the black title bar for each interface, is there any clue to what OPT3 is ?

[#15]

@Anonymous  nothing I can see?

When I go to add a new interface- it wants to call the next one I add OPT3- again to me suggesting I don't currently have an  OPT3