*WHY SYSLOG *
Central log on Windows for all routers. Proves ISP edge R1 is alive before NAT/OSPF.
STEP 1: WINDOWS - CHECK AND OPEN PORT
Run PowerShell as Administrator
netstat -an | findstr 514
netsh advfirewall firewall add rule name="Syslog 514 UDP" dir=in action=allow protocol=UDP localport=514
Expected result:
PS C:\Windows\system32> netsh advfirewall firewall add rule name="Syslog 514 UDP" dir=in action=allow protocol=UDP localport=514
Ok.
New-NetFirewallRule -DisplayName "Syslog514" -Direction Inbound -Protocol UDP -LocalPort 514 -Action Allow
netstat -an | findstr 514
Should now show:
TCP 0.0.0.0:514 0.0.0.0:0 LISTENING
UDP 0.0.0.0:514 :
STEP 2: SYSLOG WATCHER APP
Open Syslog Watcher > Settings > Check "Allow Remote Access" / "Enable Remote Access"
Restart Syslog Watcher
STEP 3: VYOS R1 - FIX AND SEND
On R1 - VyOS-R1
ping 192.168.56.1
Must ping before continuing. If not, fix Host-Only adapter gateway.
IMPORTANT: Copy this exact line, the quotes matter to keep .
sudo bash -c "echo '. @192.168.56.1:514' > /etc/rsyslog.d/99-lab.conf"
cat /etc/rsyslog.d/99-lab.conf
Must show: . @192.168.56.1:514 NOT . @192.168.56.1:514
sudo systemctl restart rsyslog
sleep 3
logger FINAL TEST FROM R1
logger TRY AGAIN FROM R1
IF STILL NOTHING SHOWS - DEBUG BLOCK
sudo tcpdump -c 5 -i eth0 port 514
In another session run: logger PACKET TEST R1
If tcpdump shows packet -> problem is Windows Firewall/Watcher
If tcpdump shows nothing -> problem is R1 config fileHOW I FIXED SYSLOG MONITORING ON VYOS-R1 ---
Last night I finally got syslog monitoring working on R1. The main issue was I was using the wrong config for this version of VyOS.
I was on VyOS 2026.03:
vyos@VyOS-R1:~$ show version | match VyOS
Version: VyOS 2026.03
I kept trying the old syntax (set system syslog host 192.168.56.1) and VyOS kept returning "invalid syslog command". For 2026.03 the correct syntax is:
configure
delete system syslog host
set system syslog global facility all level notice
set system syslog global facility protocols level warning
set system syslog host 192.168.56.1 facility all level notice
commit
save
exit
Verification:
Send a test: logger test
vyos@VyOS-R1:~$ logger testProve it leaves R1 with tcpdump (this is not the listener, this is the proof of sending):
vyos@VyOS-R1:~$ sudo tcpdump -c 5 -i any udp
16:23:28.129448 eth1 Out IP 192.168.56.101.52994 > 192.168.56.1.syslog: SYSLOG user.notice, length: 42
16:23:28.435432 eth1 Out IP 192.168.56.101.52994 > 192.168.56.1.syslog: SYSLOG user.notice, length: 48Prove it arrives on Windows: The Windows listener now shows UDP/AnyIPv4(0.0.0.0)/514 with bytes received (1000+ and growing to 9212 bytes). That counter is the real syslog server receiving.
Result: End-to-end syslog from VyOS-R1 (192.168.56.101) to Windows (192.168.56.1:514) is now monitoring. We can now log Dave's bathroom trips, interface flaps, and SSH events.
Characters in this lab: Dave, the VirtualBox gremlins, the Boomers, and the Mother of My Ex keep showing up as the cause of flaps, failed logins, and mysterious config changes.
Watch out for upcoming blog: Lab Lore - Meet Dave, The Gremlins & The Mother Of Ex
That post will be our official character guide - so when we say "Dave kicked the cable again" you know exactly who we're blaming.
Top comments (0)