Paul Mansfield wrote:
On 14/12/09 14:13, Duncan Hall wrote:
Today I had an issue where the pfsense firewall (1.2.3RC3) could not
access the remote syslog on another server because of a network fault
(dead switch).
The end result of this was the firewall stopped responding after
behaving intermittently. I imagine the firewall buffered the messages
until the memory was full.
If there an automated way of telling the firewall to not use remote
syslog if it is not available? I would prefer to lose the logs rather
than have an unstable firewall.
this seems an unlikely cause to me as syslog uses udp, so if the network
path goes away the packets will simply be lost.
could it have been a different problem - loss of DNS lookups for the
remote syslog server?
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
thanks for the quick response, remote syslog was via IP not name but the
remote syslog server was also the secondary DNS server.
Regards,
Duncan
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
