When sysklogd binds to localhost, it will try to use that socket to
reach any remove syslog servers which fails because of obvious reasons.
Therefore we will have to let sysklogd bind to 0.0.0.0 and we create a
separate firewall so that we won't accept any packets from the network
but localhost which is accepted in the LOOPBACK chain.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
iptables -A GUIINPUT -i "${GREEN_DEV}" -p tcp --dport 444 -j ACCEPT
fi
+ # Drop any messages to syslog
+ iptables -N SYSLOG
+ iptables -A SYSLOG -p udp --dport 514 -j DROP
+ iptables -A SYSLOG -p tcp --dport 514 -j DROP
+ iptables -A INPUT -j SYSLOG
+
# WIRELESS chains
iptables -N WIRELESSINPUT
iptables -A INPUT -m conntrack --ctstate NEW -j WIRELESSINPUT
case "${1}" in
start)
boot_mesg "Starting system log daemon..."
- loadproc syslogd -m 0 -r -k -b 127.0.0.1
+ loadproc syslogd -m 0 -r -k
boot_mesg "Saving Bootlog..."
if [ -e /var/log/bootlog ]; then