Re: Strange 224.0.0.251 address being accessed on bootup
- From: Avi Rozen <avi.rozen@xxxxxxxxxxxx>
- Date: Mon, 27 Aug 2007 11:53:54 +0300
Looks like zeroconf traffic (avahi/mdns), maybe try:
/etc/init.d/avahi-daemon stop
and see what happens.
HTH,
Avi.
Nigel Henry wrote:
I've had this problem for a while. When booting Debian Lenny, and perhaps Etch
as well. When booting up I've had the following output trying to access
224.0.0.251.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
lp0: using parport0 (interrupt-driven).
ppdev: user-space parallel port driver
eth0: no IPv6 routers present
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0
TTL=1 ID=0 DF OPT (94040000) PROTO=2
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=257 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=237
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=257 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=237
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=257 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=237
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=239 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=219
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=136 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=136 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=136 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=116
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=225 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=205
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=195 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=175
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=225 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=205
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=200 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=180
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=91 TOS=0x00 PREC=0x00
TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=71
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.251 LEN=225 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=205
DROPPED IN= OUT=eth0 SRC=192.168.0.8 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0
TTL=1 ID=0 DF OPT (94040000) PROTO=2
According to RFC 3171 this block of addresses (224.0.0.x) is reserved for
special purposes.
192.168.0.8 is the static address of my Lenny install, and 224.0.0.251 is the
mystery address.
There are 2 daemons that are running and looking for a response at bootup.
Ntpd is directed towards my other machine that is getting it's time from the
Internet. That is across the LAN, not the Internet. That's not the problem.
The only thing accessing the Internet at boot up is freshclam, and that once
the ethernet connection is up.
Any help, suggestions would be really welcome.
Nigel.
--
"If you are an expert in the intricacies of C++, please consider this
knowledge a kind of martial art - something a real master never uses."
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: Strange 224.0.0.251 address being accessed on bootup
- From: Nigel Henry
- Re: Strange 224.0.0.251 address being accessed on bootup
- References:
- Strange 224.0.0.251 address being accessed on bootup
- From: Nigel Henry
- Strange 224.0.0.251 address being accessed on bootup
- Prev by Date: which videcard for dual-monitor setup?
- Next by Date: Re: xterm won't start
- Previous by thread: Re: Strange 224.0.0.251 address being accessed on bootup
- Next by thread: Re: Strange 224.0.0.251 address being accessed on bootup
- Index(es):
Relevant Pages
|
