Background
We are using one RB 3011 UiAS-RM (L5 license) connected to two GPON CPE devices that are configured in bridged mode, each to an individual port (eth1 and eth10) on the Mikrotik. Each port has individual PPPoE client interfaces associated (pppoe-out1 on eth1, pppoe-out2 on eth10). To simplify the troubleshooting, the device is factory reset and has no config other than the LAN IP.
Problem
One of the PPPoE client interfaces does not connect. After plugging the respective bridged CPE directly to a Windows machine instead of the Mikrotik, the Windows machine can establish a PPPoE session. Here is the Wireshark capture from the Windows machine
pppoeWindows.rar (1.29 KB)
. As seen in the captures the provider’s PPPoE server is Juniper and the exact problem we are experiencing, Mikrotik PPPoE client against a Juniper PPPoE server, has been reported previously in the following threads.
http://forum.mikrotik.com/t/ppoe-client-can-not-connect/41054/1
http://forum.mikrotik.com/t/mikrotik-pppoe-client-connecting-to-juniper-pppoe-server/68115/1
http://forum.mikrotik.com/t/pppoe-client-on-adsl-line-not-work-after-upgrade-to-6-34-6-potential-bug-or-t-mob-cz-adsl-incompatibility/99850/1
http://forum.mikrotik.com/t/pppoe-problems/47375/1
http://forum.mikrotik.com/t/problem-with-pppoe-connection/63598/1
http://forum.mikrotik.com/t/pppoe-client-bugs/107046/1
http://forum.mikrotik.com/t/pppoe-cient-random-no-pado-response/120812/1
http://forum.mikrotik.com/t/pppoe-client-cant-connect-anymore/128862/1
It looks like the Mikrotik sends consecutive PADIs then giving up (LCP down) if it does not get a PADO within a short period of time. From what I understand in the packet capture from Windows, I am assuming that the provider’s Juniper is delaying the PADO response.
Additional Context
Here is a list of what did not help.
- Disabling DHCP client on the port associated with the PPPoE client interface.
- Removing the port associated with the PPPoE client interface from any bridges.
- Setting the PPPoE service name as “internet” as well as just “”
- Upgrading from 6.42 to 6.46 (release notes does not mention anything about the PPPoE client anyway)
- Having a single PPPoE Client interface configuration at a time.
- Setting the port and/or PPPoE client interface MTU/MRU to 1492, 1480, 1460.
Request
We would appreciate if Mikrotik could at least identify the underlying cause for this incompatibility. Please let us know if you would need any further information.