[accel-ppp] PPPoE Server not running in vyos 1.3.0-RC5

maimun.najib · July 15, 2021, 4:35am

Hi,

I have a problem on vyos 1.3.0-rc5 where pppoe server can’t work and accel-ppp status is not running in systemctl. the following is attached my pppoe server config

vyos@DR-VYOS-SYS-5018D-FN8T# run show configuration commands | grep pppoe | strip-private
set service pppoe-server authentication mode 'radius'
set service pppoe-server authentication radius server xxxxx.tld key xxxxxx
set service pppoe-server client-ip-pool subnet 'xxx.xxx.0.0/10'
set service pppoe-server gateway-address 'xxx.xxx.1.1'
set service pppoe-server interface eth4


root@DR-VYOS-SYS-5018D-FN8T:/home/vyos# service accel-ppp status
● accel-ppp.service - Accel-PPP
   Loaded: loaded (/lib/systemd/system/accel-ppp.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2021-07-15 11:28:46 WIB; 4min 55s ago
  Process: 3608 ExecStart=/usr/sbin/accel-pppd -d -p /var/run/accel-pppd.pid -c /etc/accel-ppp.conf (code=exited, status=1/FAILURE)

Jul 15 11:28:46 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Service RestartSec=100ms expired, scheduling restart.
Jul 15 11:28:46 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Scheduled restart job, restart counter is at 5.
Jul 15 11:28:46 DR-VYOS-SYS-5018D-FN8T systemd[1]: Stopped Accel-PPP.
Jul 15 11:28:46 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Start request repeated too quickly.
Jul 15 11:28:46 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Failed with result 'exit-code'.
Jul 15 11:28:46 DR-VYOS-SYS-5018D-FN8T systemd[1]: Failed to start Accel-PPP.

root@DR-VYOS-SYS-5018D-FN8T:/home/vyos# journalctl -xe | grep accel-pp
-- Subject: A start job for unit accel-ppp.service has begun execution
-- A start job for unit accel-ppp.service has begun execution.
Jul 15 11:26:34 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Control process exited, code=exited, status=1/FAILURE
-- An ExecStart= process belonging to unit accel-ppp.service has exited.
Jul 15 11:26:34 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Failed with result 'exit-code'.
-- The unit accel-ppp.service has entered the 'failed' state with result 'exit-code'.
-- Subject: A start job for unit accel-ppp.service has failed
-- A start job for unit accel-ppp.service has finished with a failure.
Jul 15 11:26:34 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Service RestartSec=100ms expired, scheduling restart.
Jul 15 11:26:34 DR-VYOS-SYS-5018D-FN8T systemd[1]: accel-ppp.service: Scheduled restart job, restart counter is at 1.
-- Automatic restarting of the unit accel-ppp.service has been scheduled, as the result for
-- Subject: A stop job for unit accel-ppp.service has finished
-- A stop job for unit accel-ppp.service has finished.

Thanks.

Dmitry · July 15, 2021, 5:55am

Hello @maimun.najib , VyOS uses a different service name for each daemon. Try to catch the following info:

sudo ps ax | grep accel
sudo systemctl status accel-ppp@pppoe.service

Your config successfully tested on VyOS 1.3.0-rc5 in our LAB.

vyos@vyos# run show pppoe-server statistics 
uptime: 0.00:02:09
cpu: 0%
mem(rss/virt): 5444/100532 kB
core:
  mempool_allocated: 134018
  mempool_available: 131810
  thread_count: 1
  thread_active: 1
  context_count: 8
  context_sleeping: 0
  context_pending: 0
  md_handler_count: 4
  md_handler_pending: 0
  timer_count: 0
  timer_pending: 0
sessions:
  starting: 0
  active: 0
  finishing: 0
pppoe:
  starting: 0
  active: 0
  delayed PADO: 0
  recv PADI: 0
  drop PADI: 0
  sent PADO: 0
  recv PADR(dup): 0(0)
  sent PADS: 0
  filtered: 0
radius(1, 192.168.0.10):
  state: active
  fail count: 0
  request count: 0
  queue length: 0
  auth sent: 0
  auth lost(total/5m/1m): 0/0/0
  auth avg query time(5m/1m): 0/0 ms
  acct sent: 0
  acct lost(total/5m/1m): 0/0/0
  acct avg query time(5m/1m): 0/0 ms
  interim sent: 0
  interim lost(total/5m/1m): 0/0/0
  interim avg query time(5m/1m): 0/0 ms

maimun.najib · July 15, 2021, 9:09am

Hi @Dmitry ,

After I checked there was the following log on my vyos so the user couldn’t connect to the pppoe server,

Jul 15 16:07:01 DR-VYOS-SM accel-pppoe: eth7.2201.110: recv [PPPoE PADI 64:d1:54:d1:42:c1 => ff:ff:ff:ff:ff:ff sid=0000 <Host-Uniq 23050401> <Service-Name > <PPP-Max-Payload 1314>]
Jul 15 16:07:01 DR-VYOS-SM accel-pppoe: eth7.2201.110: send [PPPoE PADO ac:1f:6b:7a:1d:a5 => 64:d1:54:d1:42:c1 sid=0000 <AC-Name GMEDIA> <Service-Name > <AC-Cookie c7a676cc89ae05fe6dd76de18d1467ebeff015f9b82517ae> <Host-Uniq 23050401> <PPP-Max-Payload 1314>]
Jul 15 16:07:04 DR-VYOS-SM accel-pppoe: eth7.2201.110: recv [PPPoE PADI 64:d1:54:d1:42:c1 => ff:ff:ff:ff:ff:ff sid=0000 <Host-Uniq 24050401> <Service-Name > <PPP-Max-Payload 1315>]
Jul 15 16:07:04 DR-VYOS-SM accel-pppoe: eth7.2201.110: send [PPPoE PADO ac:1f:6b:7a:1d:a5 => 64:d1:54:d1:42:c1 sid=0000 <AC-Name GMEDIA> <Service-Name > <AC-Cookie c7a676cc89ae05fe6dd76de18d1467eb35cc23c4dedfcd83> <Host-Uniq 24050401> <PPP-Max-Payload 1315>]
Jul 15 16:07:07 DR-VYOS-SM accel-pppoe: eth7.2201.110: recv [PPPoE PADI 64:d1:54:d1:42:c1 => ff:ff:ff:ff:ff:ff sid=0000 <Host-Uniq 25050401> <Service-Name > <PPP-Max-Payload 1316>]
Jul 15 16:07:07 DR-VYOS-SM accel-pppoe: eth7.2201.110: send [PPPoE PADO ac:1f:6b:7a:1d:a5 => 64:d1:54:d1:42:c1 sid=0000 <AC-Name GMEDIA> <Service-Name > <AC-Cookie c7a676cc89ae05fe6dd76de18d1467eb859a9904dc033e2d> <Host-Uniq 25050401> <PPP-Max-Payload 1316>]
Jul 15 16:07:10 DR-VYOS-SM accel-pppoe: eth7.2201.110: recv [PPPoE PADI 64:d1:54:d1:42:c1 => ff:ff:ff:ff:ff:ff sid=0000 <Host-Uniq 26050401> <Service-Name > <PPP-Max-Payload 1317>]
Jul 15 16:07:10 DR-VYOS-SM accel-pppoe: eth7.2201.110: send [PPPoE PADO ac:1f:6b:7a:1d:a5 => 64:d1:54:d1:42:c1 sid=0000 <AC-Name GMEDIA> <Service-Name > <AC-Cookie c7a676cc89ae05fe6dd76de18d1467eb035e9157c732c5c6> <Host-Uniq 26050401> <PPP-Max-Payload 1317>]
Jul 15 16:07:13 DR-VYOS-SM accel-pppoe: eth7.2201.110: recv [PPPoE PADI 64:d1:54:d1:42:c1 => ff:ff:ff:ff:ff:ff sid=0000 <Host-Uniq 27050401> <Service-Name > <PPP-Max-Payload 1318>]
Jul 15 16:07:13 DR-VYOS-SM accel-pppoe: eth7.2201.110: send [PPPoE PADO ac:1f:6b:7a:1d:a5 => 64:d1:54:d1:42:c1 sid=0000 <AC-Name GMEDIA> <Service-Name > <AC-Cookie c7a676cc89ae05fe6dd76de18d1467ebb184f4d603c7a535> <Host-Uniq 27050401> <PPP-Max-Payload 1318>]

Dmitry · July 15, 2021, 9:57am

That means VyOS answers PADO, but the client does not want to establish the connection. Try to catch logs on the client side.