From c1c29fb03a24244c1a725213aadaa38764f24f6a Mon Sep 17 00:00:00 2001 From: Christian Hesse Date: Thu, 7 Jun 2018 12:26:17 +0200 Subject: give hint about viewing the logs --- README.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 55e9db4..992ac6f 100644 --- a/README.md +++ b/README.md @@ -31,9 +31,23 @@ Usage ----- Just run `udp514-journal` or start a systemd unit with -`systemctl start udp514-journal`. +`systemctl start udp514-journal`. Make sure UDP port 514 is not blocked +in your firewall. -Make sure UDP port 514 is not blocked in your firewall. +Use `journalctl` to view the logs: + + $ journalctl -u udp514-journal + Jun 07 08:15:22 server 10.0.0.1[548]: dhcp,info mikrotik1: intern assigned 10.0.0.50 to 00:11:22:33:44:55 + Jun 07 09:16:59 server 10.0.0.1[548]: interface,info mikrotik1: en7 link down + Jun 07 09:17:17 server 10.0.0.1[548]: interface,info mikrotik1: en7 link up (speed 100M, full duplex) + Jun 07 10:07:16 server 10.1.1.1[548]: wireless,info mikrotik2: 00:11:22:33:44:66@wl2-guest: connected, signal strength -36 + Jun 07 10:07:21 server 10.1.1.1[548]: dhcp,info mikrotik2: guest assigned 192.168.1.50 to 00:11:22:33:44:66 + +Filtering is available with matching `SYSLOG_IDENTIFIER` the ip address: + + $ journalctl -u udp514-journal SYSLOG_IDENTIFIER=10.1.1.1 + Jun 07 10:07:16 server 10.1.1.1[548]: wireless,info mikrotik2: 00:11:22:33:44:66@wl2-guest: connected, signal strength -36 + Jun 07 10:07:21 server 10.1.1.1[548]: dhcp,info mikrotik2: guest assigned 192.168.1.50 to 00:11:22:33:44:66 ### Upstream -- cgit v1.2.3-54-g00ecf