Rampler
February 26, 2017, 7:36am
1
I get to many of these messages..
Sun Feb 26 08:17:47 2017 daemon.notice odhcpd[1011]: Learned about 2003:d2:53f0:xxxx:1549:ad23:5dbf:5487 on br-LAN
Is there a possibilty to adjust the log-level of odhcpd ?
I am searching for a parameter in the dhcp config..
best reagrds
Klaus
Rampler
February 26, 2017, 9:09am
2
I have solved it, by modifying the script /etc/init.d/odhcpd:
procd_set_param command /usr/sbin/odhcpd -l 4
A better way would be via UCI, but i see no possibility ..
Thank you for your solution.
hnyman
February 28, 2017, 8:20am
4
There is an uci way in the most recent version of odhcpd (2017-02-21) in LEDE master. Originally implemented in odhcpd with https://git.lede-project.org/?p=project/odhcpd.git;a=commitdiff;h=a898ee5458950203d4b2f8fec28c85313c855b91;hp=51c756cfc15c63322df9fdb70d5c701cfb6b9a9f
In practice we need to edit the odhcpd section in /etc/config/dhcp and add a new "loglevel" option that takes 0-7 as the value. 6 is the current verbose default, while 4 is the old default that only displays warnings and errors.
/etc/config/dhcp
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
1 Like
I've changed the loglevel parameter to 4, and I'm still getting the following every 10 seconds in the syslog:
daemon.info odhcpd[1360]: Using a RA lifetime of 0 seconds on br-lan
I've tried with loglevel 8 ... and 1 , same thing ... Ideas?
Per
October 27, 2017, 9:44am
6
This seems to make it stop:
uci set dhcp.odhcpd.loglevel=4
uci commit dhcp.odhcpd.loglevel
/etc/init.d/odhcpd restart
DG12
December 24, 2017, 12:26am
7
How is your What is your /etc/rsyslog.conf
With this I currently get these messages only to 06_info and 07_debug:
*.emerg /var/log/00_em.log
*.alert /var/log/01_alert.log
*.crit /var/log/02_crit.log
*.err /var/log/03_err.log
*.warn /var/log/04_warn.log
*.notice /var/log/05_notice.log
*.info /var/log/06_info.log
*.debug /var/log/07_debug.log