Greetings,
Surprisingly enough it was high on my list to move the dhcp REQUEST/ACK
log messages from my /var/log/messages...
From reading this thread I would agree with both sides, syslog in
dnsmasq is not fully documented and syslog configuration is the place to
implement the fix.
Does
On Fri, Mar 18, 2011 at 6:10 PM, Frederick C. Damen f...@damen.org wrote:
Greetings,
Surprisingly enough it was high on my list to move the dhcp REQUEST/ACK log
messages from my /var/log/messages...
From reading this thread I would agree with both sides, syslog in dnsmasq is
not fully
Frederick C. Damen (f...@damen.org) wrote on 18 March 2011 18:10:
From reading this thread I would agree with both sides, syslog in
dnsmasq is not fully documented
It is. It clearly says logs will go to either syslog or to a file.
and syslog configuration is the place to implement the fix.
On 03/18/2011 08:51 PM, Carlos Carvalho wrote:
Frederick C. Damen (f...@damen.org) wrote on 18 March 2011 18:10:
From reading this thread I would agree with both sides, syslog in
dnsmasq is not fully documented
It is. It clearly says logs will go to either syslog or to a file.
It maybe
Hallo, Carlos,
Du meintest am 18.03.11:
[...]
I also noticed that the log messages in the /var/log/messages for
the DHCP REQUEST/ACK the string after the hostname and before the
[pid], (I assume this is the ident parameter to openlog), is
'dnsmasq-dhcp'. Am I to assume that --log-queries
Dear all,
I have a setup where there are two (or more) separate subnets behind a DHCP
relay.
DHCP relay
|| |-|
10.1.0.1/16|eth1|10.0.0.0/16|Dnsmasq sever|
--|eth2|---| |
2011/3/19 Takács Balázs tak...@freemail.hu:
Dear all,
I have a setup where there are two (or more) separate subnets behind a DHCP
relay.
DHCP relay
|| |-|
10.1.0.1/16|eth1 |10.0.0.0/16|Dnsmasq sever|
