How to quiet Emonpi kernel messages caused by Multicast Network Traffic in /var/log/messages?

Hardware emonPi
1

How to quiet Emonpi kernel messages in /var/log/messages?

My /var/log/messages is very noisy and fills up fast with the following:

ct 3 23:34:54 emonpi kernel: [427377.543021] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:94:18:00:00:2e:06:9b:da SRC=66.249.88.19 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=37912 PROTO=TCP SPT=64783 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:34:55 emonpi kernel: [427377.749805] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:04:86:00:00:2e:06:7d:75 SRC=66.102.6.158 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=1158 PROTO=TCP SPT=38293 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:34:56 emonpi kernel: [427379.543005] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:98:68:00:00:2e:06:97:8a SRC=66.249.88.19 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=39016 PROTO=TCP SPT=64783 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:34:57 emonpi kernel: [427379.749820] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:0b:fb:00:00:2e:06:76:00 SRC=66.102.6.158 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=3067 PROTO=TCP SPT=38293 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:35:00 emonpi kernel: [427383.542717] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:a0:63:00:00:2e:06:8f:8f SRC=66.249.88.19 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=41059 PROTO=TCP SPT=64783 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:35:01 emonpi kernel: [427383.749799] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:14:28:00:00:2e:06:6d:d3 SRC=66.102.6.158 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=5160 PROTO=TCP SPT=38293 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:35:06 emonpi kernel: [427389.408053] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:55:5c:00:00:2e:06:da:99 SRC=66.249.88.16 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=21852 PROTO=TCP SPT=39808 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:35:09 emonpi kernel: [427391.749813] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:25:d6:00:00:2e:06:5c:25 SRC=66.102.6.158 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=9686 PROTO=TCP SPT=38293 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:35:37 emonpi kernel: [427420.407754] [UFW BLOCK] IN=eth0 OUT= MAC=b8:27:eb:ee:f5:f9:f4:f5:e8:87:79:e2:08:00:45:00:00:3c:98:ad:00:00:2e:06:97:48 SRC=66.249.88.16 DST=192.168.1.21 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=39085 PROTO=TCP SPT=39808 DPT=1723 WINDOW=42780 RES=0x00 SYN URGP=0
Oct 3 23:36:34 emonpi kernel: [427476.697876] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:f4:f5:e8:87:79:e2:08:00:45:c0:00:1c:e2:88:00:00:01:02:34:ed SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=57992 PROTO=2
Oct 3 23:36:37 emonpi kernel: [427479.822169] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:26:4d:6d:19:7f:08:00:46:c0:00:20:00:00:40:00:01:02:40:d7 SRC=192.168.1.157 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
Oct 3 23:38:39 emonpi kernel: [427601.706552] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:f4:f5:e8:87:79:e2:08:00:45:c0:00:1c:e2:89:00:00:01:02:34:ec SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=57993 PROTO=2
Oct 3 23:38:40 emonpi kernel: [427603.180172] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:26:4d:6d:19:7f:08:00:46:c0:00:20:00:00:40:00:01:02:40:d7 SRC=192.168.1.157 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2

I read on other parts of the forums that you can put:
[[RFM2Pi]]
[[[runtimesettings]]]
quiet = true

However I did this and rebooted the EmonPi and it’s still being noisy. Any ideas on how to resolve?

I am using EmonPi with 4 EmonTH sensors.

Edit: Appears to be logging these due to multi-cast traffic on my LAN. I don’t think this is avoidable as I run phone and TV over Ethernet and have a number of PoE and other multimedia network devices that are constantly scanning the network for other powered on multimedia devices to stream from/to.

The question is, how do I get EmonPi to be quiet about logging this traffic?
Would an IP Tables rule be needed?

2

I think you would be better asking this on the RaspberryPi forum. This is a Linux issue and not specific to emonPi.

However, on the emonPi /var/log is mounted in ram as a tmpfs partition and log rotate is aggressive therefore log files will never get to big or use all your disk so no need to worry.

3

Appears to be a UFW logging issue. This may help:

Glyn, isn’t UFW included as part of the emonPi software package?

4

yes it is. Configured as follows:

5

Looks like setting UFW to allow traffic from the IP addresses and/or ports flagged in the UFW log, would help.
More UFW info here: An Introduction to Uncomplicated Firewall (UFW) - Linux.com