On Wed, Sep 8, 2010 at 4:26 PM, Michael C. Robinson <[email protected]> wrote: > On Wed, 2010-09-08 at 15:46 -0700, Larry Brigman wrote: >> On Wed, Sep 8, 2010 at 2:30 PM, Michael C. Robinson >> <[email protected]> wrote: >> > I'm having trouble getting spamcannibal working, so I decided to upgrade >> > from 4.6 Final to 5.5 Final. A strange issue has popped up. When I go >> > to restart the network interfaces I get a SIOCADDRT network is >> > unreachable error. What having to do with an upgrade would cause this? >> > Oddly enough, networking seems to be working just fine despite the >> > error. >> >> We see this when the default gateway device is not reachable from the default >> interface. >> >> There is also the possibility that SELINUX which is on by default in >> 5.5 could be causing problems. >> Possible but not likely. A bunch of other stuff would be spamming the >> log files if that was the case. > > There is a log of can't reach 224.0.0.120 in my logs. Hmm, I think > avahi is causing a problem and generating the error.
avahi is part of the zeroconf set that started shipping with RHEL5 (and others). It normally doesn't cause problems, just consumes some CPU time and memory resources, mostly very small. We had some problems with this type of thing when we were setting the gateway in the /etc/sysconfig/network file instead of the interface we wanted to use for the default route. > > Sep 8 15:03:02 xerxes kernel: udp_glob_OUTPUT:IN= OUT=eth2 > SRC=216.151.30.108 DST=224.0.0.251 LEN=267 TOS=0x00 PREC=0x00 TTL=255 > ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=247 > Sep 8 15:03:02 xerxes kernel: udp_glob_OUTPUT:IN= OUT=eth2 > SRC=216.151.30.108 DST=224.0.0.251 LEN=141 TOS=0x00 PREC=0x00 TTL=255 > ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=121 > Sep 8 15:03:02 xerxes kernel: udp_glob_OUTPUT:IN= OUT=eth2 > SRC=216.151.30.108 DST=224.0.0.251 LEN=267 TOS=0x00 PREC=0x00 TTL=255 > ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=247 > Sep 8 15:03:03 xerxes kernel: udp_glob_OUTPUT:IN= OUT=eth2 > SRC=216.151.30.108 DST=224.0.0.251 LEN=267 TOS=0x00 PREC=0x00 TTL=255 > ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=247 > Sep 8 15:03:03 xerxes kernel: udp_glob_OUTPUT:IN= OUT=eth2 > SRC=216.151.30.108 DST=224.0.0.251 LEN=249 TOS=0x00 PREC=0x00 TTL=255 > ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=229 > Sep 8 15:03:03 xerxes kernel: udp_glob_OUTPUT:IN= OUT=eth2 > SRC=216.151.30.108 DST=224.0.0.251 LEN=236 TOS=0x00 PREC=0x00 TTL=255 > ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=216 > > Okay folks, how do I stop this? I have NOZEROCONF=yes > in /etc/sysconfig/network. Also you can turn avahi-daemon off by chkconfig avahi-daemon off service avahi-daemon stop > > An upgrade from 4.6 to 5.2 and the 5.5 should not have been a big deal. > I am not running X, which probably would break. If I have to back up > my custom scripts and apply to them to a fresh install of 5.2, fine. > Seems like this issue should be directly solvable though. Maybe. Depends. Major to Major upgrades like this work when you boot to the target distro and do upgrade as the command line option. 5.2 to 5.5 would not have the problems. 4.6 to 5.2 would have been the place that probably broke it. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
