Problem with PPPOE connection on raspberry pi 1

ShashankaNataraj · November 4, 2019, 5:56pm

So I basically downloaded the image corresponding to the raspberry pi 1 from the openwrt website. The raspberry pi and the modem are on the same LAN, but connected to a single Cisco Switch through ethernet cables.

I also have working ssh and the web interface when I hit http://192.168.1.1 through any devices connected to my LAN.

The problem is when I try to do the PPPOE connection with my modem by going to network->interfaces-> PPPOE and fill in the details given by my ISP for the username and password, I get the following error on the pi through tail -f /tmp/system.log

Thu Jun 27 16:19:40 2019 daemon.warn pppd[7113]: Timeout waiting for PADO packets
Thu Jun 27 16:19:40 2019 daemon.err pppd[7113]: Unable to complete PPPoE Discovery
Thu Jun 27 16:19:40 2019 daemon.info pppd[7113]: Exit.
Thu Jun 27 16:19:40 2019 daemon.notice netifd: Interface 'Airtel' is now down
Thu Jun 27 16:19:40 2019 daemon.notice netifd: Interface 'Airtel' is setting up now
Thu Jun 27 16:19:40 2019 daemon.err insmod: module is already loaded - slhc
Thu Jun 27 16:19:40 2019 daemon.err insmod: module is already loaded - ppp_generic
Thu Jun 27 16:19:40 2019 daemon.err insmod: module is already loaded - pppox
Thu Jun 27 16:19:40 2019 daemon.err insmod: module is already loaded - pppoe
Thu Jun 27 16:19:40 2019 daemon.info pppd[7177]: Plugin rp-pppoe.so loaded.
Thu Jun 27 16:19:40 2019 daemon.info pppd[7177]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Thu Jun 27 16:19:40 2019 daemon.notice pppd[7177]: pppd 2.4.7 started by root, uid 0

I found another thread by googling which said to set LCP echo failure threshold and LCP echo interval to 5 when the PADO packet error occurred. I've done that to no avail.

I am unable to figure out what this error is even after extensive googling! Please help!

eduperez · November 4, 2019, 6:51pm

That message means the RPi is trying to contact the server, but is receiving no response at all. LCP is used to detect broken connections.

Does PPPoE work over a switch? And sharing the port with the LAN interface? I would try to make a test connecting the RPi directly to the modem.

Are you sure you do not need to configure VLANs? Some ISP require it.

trendy · November 4, 2019, 8:14pm

From older experiments it can work like this. I had a Cisco switch and a Cisco router on a stick. 2 VLANs for WAN and LAN tagged on the router and untagged WAN VLAN to the modem.

@ShashankaNataraj is the VLAN configuration on the switch proper?

ShashankaNataraj · November 5, 2019, 1:48am

Thanks for your replies!

@eduperez I have another raspberry pi (3B+) with me, with a raspbian image on it. I tried to configure PPPOE on it with the command line and was able to get it to dial into the ISP with the same credentials I'm providing open wrt. I'm able to access the internet on it as well.

@trendy I didn't config any vlans on the above mentioned raspberry pi 3, thus I am relatively sure it should work through open wrt as well.

The basic problem I'm trying to solve is:

I have a Cisco switch
I have a modem provided by my ISP
I have a pc
One raspberry pi (B+) with open wrt running on it
Another raspberry pi (3B+) running raspbian

2,3,4,5 are all connected to 1 through Ethernet cables. 3,5 are able to connect to the internet by dialing in their own PPPOE connections. Surprisingly, my ISP lets me pull in multiple IP's and lets the same connection to be dialled multiple times!

I'm trying to get either 4 or 5 to dial a PPPOE connection and have the rest of the devices access the internet through it.

All the tutorials I've seen on Google talk about sharing internet on wifi through an Ethernet cable. That's unfortunately not what I'm looking for!

eduperez · November 5, 2019, 7:43am

Could you share the exact command you used on the other RPi, please?

ShashankaNataraj · November 5, 2019, 9:15am

@eduperez

sudo pppoeconf -eth0

Its a wizard type interface that shows up in the command line...

moeller0 · November 5, 2019, 9:39am

PPPoE headers live inside an ethernet packets payload and hence have no issues when used over ethernet switches.

I probably would try to use VLANs to create a dedicated undisturbed path from the pi to the modem though.

moeller0 · November 5, 2019, 9:39am

So could you try to install OpenWrt on the 3B+ just to rule out issues with the older B+?

eduperez · November 5, 2019, 9:57am

I would like to make sure that the exact same configuration that works on one machine does not work on the other.

ShashankaNataraj · November 5, 2019, 10:24am

@eduperez @moeller0

Very much appreciate the time you guys are taking to help me out.

I hadn't thought of that before, but that does make sense: I will install the corresponding openwrt image on the raspberry pi 3B+ as well , try the PPPOE config on it and report back.

The switch I have is an unmanaged Cisco switch which doesn't have any software built in so any vlan configurations aren't possible on the switch itself as far as I'm aware.

trendy · November 5, 2019, 10:30am

ps -ef | grep ppp
will show the command that raspbian uses to establish the PPPoE.

ShashankaNataraj · November 5, 2019, 3:15pm

OK, first finding: the PPPOE connection doesnt get dialled on the raspberry pi 3B+ as well. I downloaded the corresponding raspberry pi 3B+ image and tried this.

Second Finding:

On the working PPPOE raspberry pi:

ps -ef | grep ppp

returns a "command not found" for ppp. There is no process running by that name!

trendy · November 5, 2019, 3:32pm

What does ps -ef return?

ShashankaNataraj · November 5, 2019, 3:47pm

This is the output of ps-ef

UID PID PPID C STIME TTY TIME CMD
root 1 0 0 20:46 ? 00:00:04 /sbin/init splash
root 2 0 0 20:46 ? 00:00:00 [kthreadd]
root 3 2 0 20:46 ? 00:00:00 [rcu_gp]
root 4 2 0 20:46 ? 00:00:00 [rcu_par_gp]
root 8 2 0 20:46 ? 00:00:00 [mm_percpu_wq]
root 9 2 0 20:46 ? 00:00:00 [ksoftirqd/0]
root 10 2 0 20:46 ? 00:00:00 [rcu_sched]
root 11 2 0 20:46 ? 00:00:00 [rcu_bh]
root 12 2 0 20:46 ? 00:00:00 [migration/0]
root 13 2 0 20:46 ? 00:00:00 [cpuhp/0]
root 14 2 0 20:46 ? 00:00:00 [cpuhp/1]
root 15 2 0 20:46 ? 00:00:00 [migration/1]
root 16 2 0 20:46 ? 00:00:00 [ksoftirqd/1]
root 19 2 0 20:46 ? 00:00:00 [cpuhp/2]
root 20 2 0 20:46 ? 00:00:00 [migration/2]
root 21 2 0 20:46 ? 00:00:00 [ksoftirqd/2]
root 23 2 0 20:46 ? 00:00:00 [kworker/2:0H-kblockd]
root 24 2 0 20:46 ? 00:00:00 [cpuhp/3]
root 25 2 0 20:46 ? 00:00:00 [migration/3]
root 26 2 0 20:46 ? 00:00:00 [ksoftirqd/3]
root 29 2 0 20:46 ? 00:00:00 [kdevtmpfs]
root 30 2 0 20:46 ? 00:00:00 [netns]
root 31 2 0 20:46 ? 00:00:00 [kworker/0:1-events]
root 34 2 0 20:46 ? 00:00:00 [khungtaskd]
root 35 2 0 20:46 ? 00:00:00 [oom_reaper]
root 36 2 0 20:46 ? 00:00:00 [writeback]
root 37 2 0 20:46 ? 00:00:00 [kcompactd0]
root 38 2 0 20:46 ? 00:00:00 [crypto]
root 39 2 0 20:46 ? 00:00:00 [kblockd]
root 40 2 0 20:46 ? 00:00:00 [watchdogd]
root 41 2 0 20:46 ? 00:00:00 [rpciod]
root 42 2 0 20:46 ? 00:00:00 [kworker/u9:0-hci0]
root 43 2 0 20:46 ? 00:00:00 [xprtiod]
root 46 2 0 20:46 ? 00:00:00 [kswapd0]
root 47 2 0 20:46 ? 00:00:00 [nfsiod]
root 58 2 0 20:46 ? 00:00:00 [kthrotld]
root 59 2 0 20:46 ? 00:00:00 [kworker/3:1-events]
root 60 2 0 20:46 ? 00:00:00 [iscsi_eh]
root 61 2 0 20:46 ? 00:00:00 [dwc_otg]
root 62 2 0 20:46 ? 00:00:00 [DWC Notificatio]
root 63 2 0 20:46 ? 00:00:00 [kworker/2:2-events]
root 64 2 0 20:46 ? 00:00:00 [vchiq-slot/0]
root 65 2 0 20:46 ? 00:00:00 [vchiq-recy/0]
root 66 2 0 20:46 ? 00:00:00 [vchiq-sync/0]
root 67 2 0 20:46 ? 00:00:00 [vchiq-keep/0]
root 68 2 0 20:46 ? 00:00:00 [SMIO]
root 69 2 0 20:46 ? 00:00:00 [irq/86-mmc1]
root 71 2 0 20:46 ? 00:00:00 [mmc_complete]
root 73 2 0 20:46 ? 00:00:00 [kworker/0:1H-mmc_complete]
root 74 2 0 20:46 ? 00:00:00 [kworker/1:1H-kblockd]
root 75 2 0 20:46 ? 00:00:00 [kworker/1:2H]
root 76 2 0 20:46 ? 00:00:00 [jbd2/mmcblk0p2-]
root 77 2 0 20:46 ? 00:00:00 [ext4-rsv-conver]
root 78 2 0 20:46 ? 00:00:00 [kworker/3:1H-kblockd]
root 79 2 0 20:46 ? 00:00:00 [ipv6_addrconf]
root 85 2 0 20:46 ? 00:00:00 [kworker/0:2H]
root 95 2 0 20:46 ? 00:00:00 [kworker/3:2H]
root 97 2 0 20:46 ? 00:00:00 [kworker/2:2H-kblockd]
root 108 1 0 20:46 ? 00:00:01 /lib/systemd/systemd-journald
root 131 2 0 20:46 ? 00:00:00 [kworker/3:2-memcg_kmem_cache]
root 169 1 0 20:46 ? 00:00:00 /lib/systemd/systemd-udevd
root 203 2 0 20:46 ? 00:00:00 [SMIO]
root 227 2 0 20:46 ? 00:00:00 [mmal-vchiq]
root 229 2 0 20:46 ? 00:00:00 [mmal-vchiq]
root 230 2 0 20:46 ? 00:00:00 [mmal-vchiq]
root 264 2 0 20:46 ? 00:00:00 [cfg80211]
root 271 2 0 20:46 ? 00:00:00 [brcmf_wq/mmc1:0]
root 272 2 0 20:46 ? 00:00:00 [brcmf_wdog/mmc1]
systemd+ 302 1 0 20:46 ? 00:00:00 /lib/systemd/systemd-timesyncd
root 328 1 0 20:46 ? 00:00:00 /usr/lib/udisks2/udisksd
root 332 1 0 20:46 ? 00:00:00 /usr/sbin/cron -f
root 342 1 0 20:46 ? 00:00:00 /usr/sbin/alsactl -E HOME=/run/a
nobody 343 1 0 20:46 ? 00:00:00 /usr/sbin/thd --triggers /etc/tr
root 345 2 0 20:46 ? 00:00:00 [kworker/u8:3-events_unbound]
root 348 1 0 20:46 ? 00:00:00 /usr/sbin/rngd -r /dev/hwrng
root 353 1 0 20:46 ? 00:00:00 /lib/systemd/systemd-logind
message+ 368 1 0 20:46 ? 00:00:00 /usr/bin/dbus-daemon --system --
root 378 1 0 20:46 ? 00:00:00 /sbin/wpa_supplicant -u -s -O /r
avahi 382 1 0 20:46 ? 00:00:00 avahi-daemon: running [raspberry
root 388 1 0 20:46 ? 00:00:00 /usr/sbin/rsyslogd -n -iNONE
root 431 1 0 20:46 ? 00:00:00 /sbin/dhcpcd -q -b
avahi 465 382 0 20:46 ? 00:00:00 avahi-daemon: chroot helper
root 540 2 0 20:46 ? 00:00:00 [kworker/u8:4-events_unbound]
root 559 1 0 20:46 ? 00:00:00 /usr/lib/policykit-1/polkitd --n
root 563 1 0 20:46 ? 00:00:00 /usr/sbin/pppd call dsl-provider
root 607 1 0 20:46 ? 00:00:00 wpa_supplicant -B -c/etc/wpa_sup
root 744 1 0 20:46 ? 00:00:00 /usr/bin/vncserver-x11-serviced
root 751 744 0 20:46 ? 00:00:00 /usr/bin/vncserver-x11-core -ser
root 759 1 0 20:46 ? 00:00:00 /usr/sbin/lightdm
root 762 1 0 20:46 ? 00:00:00 /usr/sbin/sshd -D
dnsmasq 768 1 0 20:46 ? 00:00:09 /usr/sbin/dnsmasq -x /run/dnsmas
root 801 759 0 20:46 tty7 00:00:06 /usr/lib/xorg/Xorg :0 -seat seat
root 803 1 0 20:46 tty1 00:00:00 /bin/login -f
www-data 836 1 0 20:46 ? 00:00:00 /usr/sbin/lighttpd -D -f /etc/li
root 839 2 0 20:46 ? 00:00:00 [kworker/1:2-events_power_effici
root 843 1 0 20:46 ? 00:00:00 /usr/bin/vncagent service 16
www-data 851 836 0 20:46 ? 00:00:00 /usr/bin/php-cgi
www-data 853 851 0 20:46 ? 00:00:00 /usr/bin/php-cgi
www-data 854 851 0 20:46 ? 00:00:00 /usr/bin/php-cgi
www-data 855 851 0 20:46 ? 00:00:00 /usr/bin/php-cgi
www-data 856 851 0 20:46 ? 00:00:00 /usr/bin/php-cgi
root 860 1 0 20:46 ? 00:00:00 /usr/bin/hciattach /dev/serial1
root 861 2 0 20:46 ? 00:00:00 [kworker/u9:2-hci0]
root 863 1 0 20:46 ? 00:00:00 /usr/lib/bluetooth/bluetoothd
root 865 1 0 20:46 ? 00:00:00 /usr/bin/bluealsa
root 878 2 0 20:46 ? 00:00:00 [krfcommd]
root 928 759 0 20:46 ? 00:00:00 lightdm --session-child 14 17
pi 936 1 0 20:46 ? 00:00:00 /lib/systemd/systemd --user
pi 939 936 0 20:46 ? 00:00:00 (sd-pam)
pi 985 928 0 20:46 ? 00:00:00 /usr/bin/lxsession -s LXDE-pi -e
pi 999 936 0 20:46 ? 00:00:00 /usr/bin/dbus-daemon --session -
pi 1009 803 0 20:46 tty1 00:00:00 -bash
pi 1041 985 0 20:46 ? 00:00:00 /usr/bin/ssh-agent x-session-man
pi 1051 936 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfsd
pi 1056 936 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfsd-fuse /run/us
pi 1071 985 0 20:46 ? 00:00:00 openbox --config-file /home/pi/.
pi 1072 985 0 20:46 ? 00:00:00 lxpolkit
pi 1075 985 0 20:46 ? 00:00:03 lxpanel --profile LXDE-pi
pi 1077 985 0 20:46 ? 00:00:02 pcmanfm --desktop --profile LXDE
pi 1084 1 0 20:46 ? 00:00:00 /usr/bin/ssh-agent -s
pi 1103 1 0 20:46 ? 00:00:01 /usr/bin/vncserverui service 17
pi 1147 1103 0 20:46 ? 00:00:00 /usr/bin/vncserverui -statusicon
pi 1156 936 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfs-udisks2-volum
pi 1164 1 0 20:46 ? 00:00:00 /usr/lib/menu-cache/menu-cached
pi 1169 936 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volum
pi 1173 936 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfs-goa-volume-mo
pi 1177 936 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfs-mtp-volume-mo
pi 1181 936 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfs-afc-volume-mo
pi 1187 1051 0 20:46 ? 00:00:00 /usr/lib/gvfs/gvfsd-trash --spaw
pi 1449 1075 0 20:48 ? 00:00:05 lxterminal
pi 1460 1449 0 20:48 pts/0 00:00:00 bash
root 1551 2 0 21:01 ? 00:00:00 [kworker/0:0]
root 1569 2 0 21:06 ? 00:00:00 [kworker/1:1-events_power_effici
root 1620 2 0 21:09 ? 00:00:00 [kworker/2:1-events]
root 1641 2 0 21:11 ? 00:00:00 [kworker/1:0-events_power_effici
root 1642 2 0 21:14 ? 00:00:00 [kworker/2:0-events]
root 1690 762 1 21:15 ? 00:00:00 sshd: unknown [priv]
sshd 1691 1690 0 21:15 ? 00:00:00 sshd: unknown [net]
root 1701 762 4 21:15 ? 00:00:00 sshd: pi [priv]
root 1703 2 0 21:15 ? 00:00:00 [kworker/3:0H]
pi 1715 1701 1 21:16 ? 00:00:00 sshd: pi@pts/1
pi 1718 1715 14 21:16 pts/1 00:00:00 -bash
pi 1733 1718 0 21:16 pts/1 00:00:00 ps -ef

moeller0 · November 5, 2019, 3:31pm

What does logread | grep -e pppd reveal (under OpenWrt on both the B+ and the 3B+)?

ShashankaNataraj · November 5, 2019, 4:00pm

On the 3B+, logread is a command not found.

Instead I tried to execute journalctl -b | grep ppp

Nov 04 22:33:05 raspberrypi systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...

Nov 04 22:33:05 raspberrypi systemd[1]: pppd-dns.service: Succeeded.

Nov 04 22:33:05 raspberrypi systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.

Nov 04 22:33:06 raspberrypi pppd[557]: Plugin rp-pppoe.so loaded.

Nov 04 22:33:06 raspberrypi ifup[319]: Plugin rp-pppoe.so loaded.

Nov 04 22:33:06 raspberrypi pppd[563]: pppd 2.4.7 started by root, uid 0

Nov 04 22:33:11 raspberrypi pppd[563]: PPP session is 2792

Nov 04 22:33:11 raspberrypi pppd[563]: Connected to 3c:94:d5:c8:b0:f7 via interface eth0

Nov 04 22:33:11 raspberrypi pppd[563]: Using interface ppp0

Nov 04 22:33:11 raspberrypi pppd[563]: Connect: ppp0 <--> eth0

Nov 04 22:33:11 raspberrypi pppd[563]: PAP authentication succeeded

Nov 04 22:33:11 raspberrypi pppd[563]: peer from calling number 3C:94:D5:C8:B0:F8 authorized

Nov 04 22:33:11 raspberrypi pppd[563]: local IP address 122.171.67.32

Nov 04 22:33:11 raspberrypi pppd[563]: remote IP address 122.172.64.12

Nov 04 22:33:11 raspberrypi pppd[563]: primary DNS address 125.22.47.101

Nov 04 22:33:11 raspberrypi pppd[563]: secondary DNS address 125.22.47.105

trendy · November 5, 2019, 4:01pm

The process is here, but I think the options are in some config file. Check in /etc/ if you can find it.

Is this raspbian or OpenWrt?

ShashankaNataraj · November 5, 2019, 4:14pm

Thats the output from raspbian on the 3B+. Im reflashing the rpi1's SD card with openwrt now since I own only 2 SD cards

ShashankaNataraj · November 5, 2019, 4:37pm

Here is the log for logread | grep -e pppd on the raspberry pi B+ running openwrt:

Thu Jun 27 12:28:50 2019 daemon.info pppd[1153]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:28:50 2019 daemon.info pppd[1153]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:28:50 2019 daemon.notice pppd[1153]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:29:03 2019 daemon.info pppd[1190]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:29:03 2019 daemon.info pppd[1190]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:29:03 2019 daemon.notice pppd[1190]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:29:18 2019 daemon.warn pppd[1190]: Timeout waiting for PADO packets

Thu Jun 27 12:29:18 2019 daemon.err pppd[1190]: Unable to complete PPPoE Discovery

Thu Jun 27 12:29:18 2019 daemon.info pppd[1190]: Exit.

Thu Jun 27 12:29:18 2019 daemon.info pppd[1219]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:29:18 2019 daemon.info pppd[1219]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:29:18 2019 daemon.notice pppd[1219]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:29:33 2019 daemon.warn pppd[1219]: Timeout waiting for PADO packets

Thu Jun 27 12:29:33 2019 daemon.err pppd[1219]: Unable to complete PPPoE Discovery

Thu Jun 27 12:29:33 2019 daemon.info pppd[1219]: Exit.

Thu Jun 27 12:29:33 2019 daemon.info pppd[1278]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:29:33 2019 daemon.info pppd[1278]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:29:33 2019 daemon.notice pppd[1278]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:29:48 2019 daemon.warn pppd[1278]: Timeout waiting for PADO packets

Thu Jun 27 12:29:48 2019 daemon.err pppd[1278]: Unable to complete PPPoE Discovery

Thu Jun 27 12:29:48 2019 daemon.info pppd[1278]: Exit.

Thu Jun 27 12:29:49 2019 daemon.info pppd[1337]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:29:49 2019 daemon.info pppd[1337]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:29:49 2019 daemon.notice pppd[1337]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:30:04 2019 daemon.warn pppd[1337]: Timeout waiting for PADO packets

Thu Jun 27 12:30:04 2019 daemon.err pppd[1337]: Unable to complete PPPoE Discovery

Thu Jun 27 12:30:04 2019 daemon.info pppd[1337]: Exit.

Thu Jun 27 12:30:04 2019 daemon.info pppd[1398]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:30:04 2019 daemon.info pppd[1398]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:30:04 2019 daemon.notice pppd[1398]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:30:19 2019 daemon.warn pppd[1398]: Timeout waiting for PADO packets

Thu Jun 27 12:30:19 2019 daemon.err pppd[1398]: Unable to complete PPPoE Discovery

Thu Jun 27 12:30:19 2019 daemon.info pppd[1398]: Exit.

Thu Jun 27 12:30:19 2019 daemon.info pppd[1465]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:30:19 2019 daemon.info pppd[1465]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:30:19 2019 daemon.notice pppd[1465]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:30:34 2019 daemon.warn pppd[1465]: Timeout waiting for PADO packets

Thu Jun 27 12:30:34 2019 daemon.err pppd[1465]: Unable to complete PPPoE Discovery

Thu Jun 27 12:30:34 2019 daemon.info pppd[1465]: Exit.

Thu Jun 27 12:30:35 2019 daemon.info pppd[1524]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:30:35 2019 daemon.info pppd[1524]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:30:35 2019 daemon.notice pppd[1524]: pppd 2.4.7 started by root, uid 0

Thu Jun 27 12:30:50 2019 daemon.warn pppd[1524]: Timeout waiting for PADO packets

Thu Jun 27 12:30:50 2019 daemon.err pppd[1524]: Unable to complete PPPoE Discovery

Thu Jun 27 12:30:50 2019 daemon.info pppd[1524]: Exit.

Thu Jun 27 12:30:50 2019 daemon.info pppd[1593]: Plugin rp-pppoe.so loaded.

Thu Jun 27 12:30:50 2019 daemon.info pppd[1593]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Thu Jun 27 12:30:50 2019 daemon.notice pppd[1593]: pppd 2.4.7 started by root, uid 0