View Single Post
  #3   (View Single Post)  
Old 24th May 2021
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,132
Default

I have to admit I am now confused too. I thought that "!!relayd" acted similar to a "quick" rule in the pf firewall.
And it indeed does....Relayd is now logging to its own log.

But all other logging has stopped.. For example no more ssh logins in /var/log/authlog.

So I moved it back to the end under the commented 'doas' line and am trying with specifying something other than that *.* wildcard.


!relayd
daemon.info
still logs to its own log file, as well as "/var/log/daemon".

So now the question is how to stop logging to the "/var/log/daemon".?
But right now I have no time to pursue this any further.

Feel free to test and with this shell script
Code:
#!/bin/sh

INTERVAL=10
PRIORITY="-p daemon.info"

echo Starting $0 ...... | logger $PRIORITY -t $0

while true ; do
    sleep $INTERVAL
    echo Testing sleeping $INTERVAL seconds ... at $(date)
done 2>&1 | logger $PRIORITY -t $0
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote