I’ve also been troubleshooting frequent PPPoE issues with an OpenBSD router at this point my troubleshooting has resulted in the following:
The residential ISP supplied ZyXEL C100Z currently supports forty five days plus of PPPoE uptime It appears the C100Z PTM (Packet Transfer Mode) traffic is 802.1q VLAN tagged 201 perhaps to support VOIP prioritization. Adding a managed switch & configuring transparent PPPoE bridging resulted in MTU issues necessitating baby jumbo’s on the non ISP router. Perhaps the ISP. Supplied router can accommodate 802.1q VLAN tags on the PPPoE device with a loopback that does not necessitate ethernet MTU. In addition I speculate that the routers wireless access point supports FCC certification on 802.11n & can accommodate frequency/channel change as required Regards Patrick > On Mar 16, 2017, at 7:46 PM, Nicholas Bachmann <[email protected]> wrote: > > Hi all, > > I’m having a problem where PPPoE disconnects every 6-7 minutes. I’m > originally saw this in 5.9; I then upgraded to 6.0 but still have the > same issue. > > If I run “ifconfig pppoe0 up” right after it disconnects, it comes > right back up again. I have a ddwrt box that can successfully keep > this same PPPoE connection up without these disconnects, so I don’t > think the problem is related to the ISP equipment. > > My hostname.pppoe0 looks like: > > inet 0.0.0.0 255.255.255.255 NONE \ > pppoedev em0 authproto pap peerproto chap \ > authname ‘username’ authkey ‘mypassword’ up > dest 0.0.0.1 > !/sbin/route add default -ifp pppoe0 0.0.0.1 > > In dmesg and /var/log/messages, I see only this: > Mar 17 04:02:42 greatwall /bsd: pppoe0: LCP keepalive timeout > > I ran tcpdump, and this is all the pppoe traffic I see: > 04:09:07.070988 Echo-Request, Magic-Number=1174906872 > 04:09:07.070995 Echo-Reply, Magic-Number=1072546934 > 04:09:09.231366 Configure-Request, Interface-ID=0225:baff:fe7a:03fd > 04:09:09.231378 Configure-Ack, Interface-ID=0225:baff:fe7a:03fd > 04:09:12.331417 Configure-Request, Interface-ID=0225:baff:fe7a:03fd > 04:09:12.331430 Configure-Ack, Interface-ID=0225:baff:fe7a:03fd > 04:09:15.631510 Configure-Request, Interface-ID=0225:baff:fe7a:03fd > 04:09:15.631522 Configure-Ack, Interface-ID=0225:baff:fe7a:03fd > 04:09:32.308186 Echo-Request, Magic-Number=1072546934 > 04:09:42.310549 Echo-Request, Magic-Number=1072546934 > 04:09:52.312791 Echo-Request, Magic-Number=1072546934 > 04:10:02.315637 Terminate-Request > 04:10:02.342731 Configure-Request, Magic-Number=849593138, > Max-Rx-Unit=1492, Auth-Prot CHAP/MD5[|lcp] > 04:10:02.390879 Configure-Request, Max-Rx-Unit=1492, Auth-Prot PAP, > Magic-Number=535689543, Vendor-Ext > 04:10:02.390889 Configure-Ack, Max-Rx-Unit=1492, Auth-Prot PAP, > Magic-Number=535689543[|lcp] > 04:10:02.390995 Configure-Reject, Auth-Prot CHAP/MD5, Vendor-Ext > 04:10:02.391001 Terminate-Request > 04:10:02.392061 Terminate-Ack > > This isn't much to go on so I’d be grateful for any suggestions about > where to troubleshoot this further. > > Thanks, > Nick
