Re: Strange 224.0.0.251 address being accessed on bootup
On Tuesday 28 August 2007 03:53, Douglas A. Tutty wrote:
> On Mon, Aug 27, 2007 at 04:28:48PM +0200, Nigel Henry wrote:
> > On Monday 27 August 2007 03:52, Douglas A. Tutty wrote:
> > > Since this is all happening in /etc/rcS.d, I'd suggest booting with
> > > init=/bin/sh and running the /etc/rcS.d scripts manually one at a time
> > > to try to track it down. If you can get a shell while these errors are
> > > happening, perhaps you can see what processes are running.
> >
> > I havn't tried that before. Is that going to be similar to the
> > interactive boot up that you can do on Fedora?
>
> I've never used Fedora. There's nothing interactive about it. When you
> init=/bin/sh, you get sh running instead of init. The only drive
> mounted is the / and its ro. So you cd to /etc/rcS.d, do an ls and
> write down all the file names so you can tick them off as you run them.
>
> #less README
>
> read it..
>
> Then, one at a time, type e.g.:
> #./S01glibc.sh start
> #./S02hostname.sh start
>
> You're sort-of single-stepping the init process to track down a problem.
> Once you have, try to fix it and then shutdown. Since init normally
> does this, I wouldn't want to try to bring the system all the way up in
> this manner.
>
> Doug.
Thanks for that Doug. I tried it out on my Etch install.
I've still got this avahi-daemon problem on the Etch install. it's a bit
puzzling. I booted Etch up, opened synaptic to verify the zeroconf package
was no longer installed, and that is so. Then opened sysv-rc-conf in a
terminal, and see that I'd already disabled the avahi-daemon in all
runlevels. tail -f /var/log/messages though is still showing IP 192.168.0.7
pointing to IP 224.0.0.251.
I then do an ifdown eth0, and an ifup eth0, and the messages are still there.
next I do an /etc/init.d.avahi-daemon stop, and it confirms a stop.
Do an ifdown eth0, and an ifup eth0 again, and no more messages apart from the
one line that confirms that eth0 is up.
It would appear that even though the daemon is disabled on all runlevels,
something somewhere is starting it before I login.
Interestingly I opened synaptic to see if I could remove the avahi-daemon, and
got a few dependencies that would also be removed, as below.
kde
kdenetwork
kdnssd
libnss-mdns
Now I don't want KDE to be removed, as that's my desktop.
Out of interest I shutdown Etch, bootup Lenny, and here, synaptic only want s
to remove libnss-mdns as a dependency.
It looks like KDE has something to do with this problem.
How do I find out what is responsible for launching the avahi-daemon
shellscript?
This is the last bit of dmesg on Etch, where for some reason I can't disable
the avahi daemon, apart from running /etc/init.d/avahi-daemon stop , when I'm
booted up.
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (8127 buckets, 65016 max) - 224 bytes per conntrack
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
lp0: using parport0 (interrupt-driven).
ppdev: user-space parallel port driver
eth0: no IPv6 routers present
DROPPED IN= OUT=eth0 SRC=192.168.0.7 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.7 DST=224.0.0.251 LEN=141 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=121
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=141 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=121
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=141 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=121
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=129 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=109
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=175 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=155
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=175 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=155
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=175 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=155
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=236 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=216
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=113 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=93
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=236 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=216
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=129 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=109
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=236 TOS=0x00
PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=216
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0
TTL=1 ID=0 DF OPT (94040000) PROTO=2
NET: Registered protocol family 4
NET: Registered protocol family 3
NET: Registered protocol family 5
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
DROPPED IN= OUT=eth0 SRC=192.168.0.7 DST=224.0.0.251 LEN=72 TOS=0x00 PREC=0x00
TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=52
d
Any comments, suggestions, and including "go and get a life", welcome.
This is no big deal, but would be nice to resolve this problem.
Nigel.
Reply to: