On 23/10/2018 06.56, Andrei Borzenkov wrote:
22.10.2018 22:52, Carlos E. R. пишет:
On 22/10/2018 14.49, Rodney Baker wrote:
Just as a test, I tried to ping 224.0.0.1 on my local lan and got only one response - my L3 network switch which has igmp snooping enabled by default. No other devices responded.
I tried on three machines, and on all of them the ping had 100% failure. The firewall log of this machine did not reflect any hits. I guess they don't even get out.
Legolas:~ # ping 224.0.0.1 PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data. ^C --- 224.0.0.1 ping statistics --- 24 packets transmitted, 0 received, 100% packet loss, time 23544ms
Legolas:~ #
On this machine I see more log entries, incoming from two sources and to two destinations:
<0.4> 2018-10-22 21:33:13 Legolas kernel - - - [44907.911153] FINAL_REJECT: IN=wlan1 OUT= MAC=01:00:5e:00:00:01:f8:8e:85:64:78:f2:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
That's the one in the OP. After I turned on the printer, I also get these:
<0.4> 2018-10-22 21:34:58 Legolas kernel - - - [45012.967174] FINAL_REJECT: IN=wlan1 OUT= MAC=01:00:5e:00:00:fb:00:1e:0b:08:4c:cb:08:00 SRC=192.168.1.3 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=227 PROTO=2
Destination MAC and IP are for mDNS (Avahi), but mDNS is using UDP and here PROTO=2 == IGMP. It does not match. It would be interesting to see full packet trace.
Ok, I'll do that this night. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)