pppd[824] logfile spam

[heliosone]

hi !

Im running a openVPN server on my N66U (@LTEusbSTICK),and my logfile gets spammed every minute with this :

Nov 18 17:00:14 pppd[824]: Timeout waiting for PADO packets
Nov 18 17:01:29 pppd[824]: Timeout waiting for PADO packets
Nov 18 17:02:44 pppd[824]: Timeout waiting for PADO packets
Nov 18 17:03:59 pppd[824]: Timeout waiting for PADO packets
Nov 18 17:05:14 pppd[824]: Timeout waiting for PADO packets
Nov 18 17:06:29 pppd[824]: Timeout waiting for PADO packets
Nov 18 17:07:44 pppd[824]: Timeout waiting for PADO packets
Nov 18 17:08:59 pppd[824]: Timeout waiting for PADO packets

Im not sure if this openVPN related

any idea how to disable this ?

 

[tomsk]

Theres an old thread which sounds like the same thing.
http://www.snbforums.com/threads/what-causes-pado-timeouts-in-my-log.20200/

 

[tomsk]

And here's what i got fishing around on t'interweb

A PADO (PPPoE Active Discovery Offer) is a packet that should be sent back to your computer after it sent a PADI.
In the case of a UTD connected via Ethernet, this is the response that is supposed to come back from the modem, after your IPCOP sent a PADI (to discover PPPoE capable devices).
If no PADO is received after sending a PADI, the message "Timed out waiting for PADO packet" or such, is printed in your system log

not sure what that would have to do with openVPN... Im assuming your WAN connection is PPPoE?

 

[john9527]

Step 1: Replace the ethernet cable between the modem and router with a good quality cat5e or cat6 cable
Step 2: If Step 1 doesn't resolve the problem, call your ISP and report a problem.

 

[heliosone]

hi everyone!
Thank you all for your input

* I read that old thread too, but thats no help

* there is no modem/cable, the router is connected to a usb lte stick.
Not sure if thats done via pppoe. ifconfig shows me a ppp0?

I have NO problem with the wan/internet connection, I just dont want my logfile. to be filled with that crap.

I also researched this before posting and found a thread about openwrt and pado problems.
the fix included :

Enable_PPP_Echo_Detect = NO
Enable_Internet_Detect = NO

source : https://forum.openwrt.org/viewtopic.php?id=55158

but I dont find these options anywhere.

a workaround for me would be a way to prevent pppd writing into the logfile, as everythings works perfectly!

 

[john9527]

Sorry, I missed the USB modem part. The options you are looking for are on the main WAN page under 'Internet Detection'.

But, I don't think it will change your results, as the PADO errors are protocol errors, not part of the internet detection. Let us know your results.

 

[heliosone]

when I do ps i find :

/usr/sbin/pppd file /tmp/ppp/options.wan1

which contains :

noauth                                                                                                       
refuse-eap                                                                                                   
user ''                                                                                                     
password ''                                                                                                 
nomppe nomppc                                                                                               
plugin rp-pppoe.so nic-eth0                                                                                 
mru 1492 mtu 1492                                                                                           
persist                                                                                                     
holdoff 10                                                                                                   
maxfail 0                                                                                                   
usepeerdns                                                                                                   
ipcp-accept-remote ipcp-accept-local noipdefault                                                             
ktune                                                                                                       
default-asyncmap nopcomp noaccomp                                                                           
novj nobsdcomp nodeflate                                                                                     
lcp-echo-interval 6                                                                                         
lcp-echo-failure 10                                                                                         
lcp-echo-adaptive                                                                                           
unit 1                                                                                                       
linkname wan1

maybe there is an option to add to this file which stops the pado log entry?

 

[heliosone]

Sorry, I missed the USB modem part. The options you are looking for are on the main WAN page under 'Internet Detection'.

But, I don't think it will change your results, as the PADO errors are protocol errors, not part of the internet detection. Let us know your results.

I dont see "Internet Detection" anywhere

 

[john9527]

Hmmm......they must not show the option for USB connections (the question is if it is actually ignored, or was a simplification of the gui...would take a while to try and trace the code to find out).

You can try to set it manually and see if it helps. Via telnet/ssh

nvram set wan_ppp_echo=0
nvram set wan0_ppp_echo=0
nvram commit

then reboot

 

[heliosone]

Hmmm......they must not show the option for USB connections (the question is if it is actually ignored, or was a simplification of the gui...would take a while to try and trace the code to find out).

You can try to set it manually and see if it helps. Via telnet/ssh

nvram set wan_ppp_echo=0
nvram set wan0_ppp_echo=0
nvram commit

then reboot

before setting the variables,I read out the old values (both were 1)
after setting them to zero,and reboot,its the same

as I only have a problem with the spam in my logfile,and not a problem with my internet connection,I would like to find a way to exclude a certain process/... from writing to the logfile.
>>>>i.e. to restart the syslogd service after router start with a different parameter or is there a config file for syslogd,which can be modified ?
well ... syslogd tells me :

(this version of syslogd ignores /etc/syslog.conf)

great

 

[heliosone]

a cheap solution in the meantime while waiting for a real solution :

decreasing the syslogd log sensitivity from 8 to 3

/sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 256 -l 3

not sure how much important stuff is also not shown,but with all the pado spam in the logfile,the logfile would be useless anyways...

if anyone has a REAL solution please tell and dont let me die stupid

 

[heliosone]

well who needs a REAL solution if there are workarounds... love workarounds.. and the commandline

here is another solution(aka workaround ) to general annoying repeating pointless logfile entries :

syslog-ng (opkg install syslog-ng)

a way more advanced version of syslog with toooonns of options (YEAHH )

so what I did to get rid of a certain endless repeating line of crap in my syslog :

* killing of syslogd (used the services_start script)
* starting of syslog-ng ( syslog-ng -f /opt/etc/syslog-ng.conf )
* adding these lines to the config file :

filter f_padotimeout { match("waiting for PADO packets"); };
log { source(src); filter(f_padotimeout); flags(final); };

and changed the destination of the main log file to the original syslogd file :

destination messages { file("/tmp/syslog.log"); };

tested it already for half an hour,and really only those annoying Padolines are gone,the rest just looks like as before.

with syslog-ng you can even define destinations for certain system message (different logfiles for different stuff).

also ,the syslog window within the gui is unchanged,as it only reads out /tmp/syslog.log

 

[tomsk]

well who needs a REAL solution if there are workarounds... love workarounds.. and the commandline

here is another solution(aka workaround ) to general annoying repeating pointless logfile entries :

syslog-ng (opkg install syslog-ng)

a way more advanced version of syslog with toooonns of options (YEAHH )

so what I did to get rid of a certain endless repeating line of crap in my syslog :

* killing of syslogd (used the services_start script)
* starting of syslog-ng ( syslog-ng -f /opt/etc/syslog-ng.conf )
* adding these lines to the config file :

filter f_padotimeout { match("waiting for PADO packets"); };
log { source(src); filter(f_padotimeout); flags(final); };

and changed the destination of the main log file to the original syslogd file :

destination messages { file("/tmp/syslog.log"); };

tested it already for half an hour,and really only those annoying Padolines are gone,the rest just looks like as before.

with syslog-ng you can even define destinations for certain system message (different logfiles for different stuff).

also ,the syslog window within the gui is unchanged,as it only reads out /tmp/syslog.log

Have you considered about how you will control the size of the log? ... as i understand it, the syslog.log file won't be rotated now because you have killed syslogd which was previously doing that job.

 

[heliosone]

Have you considered about how you will control the size of the log? ... as i understand it, the syslog.log file won't be rotated now because you have killed syslogd which was previously doing that job.

hmm good point,but in my case no problem,as the router shuts down (timer controled power outlet) every night and wakes up in the morning.
I just add a few lines to the services-stop script,so that the logfile is renamed with the current date,and moved to an archive location.Two birds with one stone.. archived and size controlled

# on second thought,its better to rename the file during start,after I killed syslogd,and before starting syslog-ng. If the router isnt shutdown/started everyday,then a cron job can do the same.