accel-ppp.org

Sure. I'll try. I'll try the 1.10.2 version first and upgrade the kernel version. I did not upgrade yet. I'll upgrade soon. Until now things look stable but I'll look close to random crashs and let you know. Following the logs the crash could be happened after try to disconnect ppp2196 or another in...

accel-ppp-1.10.1

Thanks, I'll try. Just for note, the last accel-ppp.log before kernel panic: [2016-04-15 13:20:10]: info: : send [RADIUS(1) Access-Request id=1 <User-Name "useraaaaaaaaaa"> <NAS-Identifier "accel-ppp"> <NAS-IP-Address hh.hh.hh.hh> <NAS-Port-Type Virtual> <Service-Type Framed-User...

This server is using the current debian default.
Upgrade to like this one for example?
Linux 4.4 for 64-bit PCs:
https://packages.debian.org/jessie-back ... mage-amd64

It just happened a kernel panic.
I had to restart the server

/var/log/kern.log file contents:
http://

I've been checking some clients and I've found that Acct-Terminate-Cause Lost-Carrier are the pppoe clients that doesn't support send the LCP termination request (differents devices). So are duplicated very old connections due the fact that clients already start new one. I'll enable single-session=r...

i suggest to analyze logs first to find exact reason I analyzed some logs but I can't find yet the reason: Follow atached the /var/log/accel-ppp/accel-ppp.log in the link: http://www.sametext.com/view/raw/0721ca7d The problem start after the [2016-04-14 14:40:36] [2016-04-14 14:40:36]: info: ppp139...

Today I saw in the server hundreds of connections that have terminated (20% of total) and reconnected. All those peers ended the connection with the message: <Acct-Terminate-Cause User-Request>] I believe it may have been that the pppoe client peer sent LCP echo messages and accel-ppp did not answer...

If I type the reload comand into the cli: telnet localhost 2000 reload It's doesn't reload ip pool. for example: [ip-pool] gw-ip-address=172.16.0.1 attr=Framed-Pool #192.168.0.2-192.168.0.254 I commented the #192.168.0.2-192.168.0.254 line and pppoe client still get ip from current 192.168.0.2-192.1...