PPPoE issues since 2.4
-
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.
-
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.
-
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 ? -
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.
-
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"?
-
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.
-
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
![[01]_Dashboard_1.png](/public/_imported_attachments_/1/%5B01%5D_Dashboard_1.png)
![[02]_Physical_Connection_1.png](/public/_imported_attachments_/1/%5B02%5D_Physical_Connection_1.png)
-
Additionally, from a telnet session to the Vigor 130, type the command: show status
The first line of the output will show the uptime
-
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.
-
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)
-
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.
-
Just posting an update.
I had some time last weekend and decided to rebuild my router and do a fresh install with 2.4.
Only change i made from my old setup was to enable IPv6 on the BT connection right from the start during the PPPoE setup.
So far my connection has been up for 6 days.
My guess would be something got messed up when i upgraded to 2.4 from 2.3. As in it was trying to use the IPv6 even though it was disabled.
Thanks for all your help and suggestions.
-
Just had a same issue with "IPV6CP: rec'd Configure Ack" messages appearing even though IPV6CP is disabled on the WAN interface.
It didnt appear again on the PPPoE reconnect.
-
And you are seeing PPPoE disconnect?
-
This probably happened on/after daily PPPoE reconnect. Everything worked normally except the DDNS client that didn't update properly (different issue: https://forum.netgate.com/topic/142719/ddns-client-skipped-ip-update/5). But I dont know why I have IPv6 messages on an interface where IPv6 is disabled.
After reconnecting PPPoE WAN again, the messages didnt start appearing again. -
If the ISP supports v6 is may have sent that ACK in repsonce to a config request. If your interface is not configured for v6 it would just have ignored it.
Unless you are actually seeing a connections problem there I would ignore that. I looks like a harmless response.Steve
