Shorewall users - Nov 2003 - logs

I have never seen a log like this
Nov 16 02:19:31 00a0c9a52422 kernel: Shorewall:logdrop:DROP:IN=eth0
OUTMAC=01:00:5e:00:00:01:00:30:80:76:ec:54:08:00 SRC=10.104.0.1 DST=224.0.0.1
LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=2723 PROTO=2
Nov 16 02:20:31 00a0c9a52422 kernel: Shorewall:logdrop:DROP:IN=eth0
OUTMAC=01:00:5e:00:00:01:00:30:80:76:ec:54:08:00 SRC=10.104.0.1 DST=224.0.0.1
LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=3100 PROTO=2
    I also have never installed shorewall on this type of network (cable
modem with click-network), nor this ISP.
I assume this is a router broadcasting to a class D network and the no rfc
1918 in shorewall is Dropping the packets

Mike

On Sun, 2003-11-16 at 12:05, Mike Lander wrote:
> I have never seen a log like this
> Nov 16 02:19:31 00a0c9a52422 kernel: Shorewall:logdrop:DROP:IN=eth0 OUT>
MAC=01:00:5e:00:00:01:00:30:80:76:ec:54:08:00 SRC=10.104.0.1 DST=224.0.0.1
> LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=2723 PROTO=2
> Nov 16 02:20:31 00a0c9a52422 kernel: Shorewall:logdrop:DROP:IN=eth0 OUT>
MAC=01:00:5e:00:00:01:00:30:80:76:ec:54:08:00 SRC=10.104.0.1 DST=224.0.0.1
> LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=3100 PROTO=2
>     I also have never installed shorewall on this type of network (cable
> modem with click-network), nor this ISP.
> I assume this is a router broadcasting to a class D network and the no rfc
> 1918 in shorewall is Dropping the packets
Mike -- I told you yesterday to bookmark FAQ 17 because it gave you all
of the information you need to decode log messages; it still does today.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net