Date: Fri, 31 May 1996 23:55:11 +0100 (BST) From: Nik Clayton <nik@blueberry.co.uk> To: FreeBSD-gnats-submit@freebsd.org Subject: conf/1285: route_multicast and route_loopback lines in /etc/sysconfig are bogus Message-ID: <199605312255.XAA11739@guava.blueberry.co.uk> Resent-Message-ID: <199605312300.QAA19497@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1285
>Category: conf
>Synopsis: route_multicast and route_loopback lines in /etc/sysconfig are bogus
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Fri May 31 16:00:02 PDT 1996
>Last-Modified:
>Originator: Nik Clayton
>Organization:
Blueberry Design
>Release: FreeBSD 2.1.0-RELEASE i386
>Environment:
From 'sysctl -a' (I hope this is sufficient)
kern.ostype = FreeBSD
kern.osrelease = 2.1-STABLE
kern.osrevision = 199306
Basically, -stable supped about a month ago.
>Description:
As shipped, /etc/sysconfig has two bogus entries for
route_multicast
and
route_loopback
The 'route_multicast' line appears to cause the system to hang
at boot time if there's no name server around. And apparently
the 'route_loopback' line is "completely bogus" and "should
not be present at all" (according to Garrett).
This problem has been known about for a while. Search the hackers
mailing list for the message from Garrett with ID
<9512131521.AA09355@halloran-eldar.lcs.mit.edu>
and re: loopback and multicast messed up on /etc/sysconfig ?
This message is dated Dec 13th, 1995 (!).
I'm sending this -pr in because I've just been bitten by this
problem, and it's only because I remembered discussion of it
in the mailing lists that I knew what to search for. Someone
knew to the OS doesn't have this advantage.
I realise my version of -stable is somewhat out of date, and that
this may well have been fixed in a later SNAP. Unfortunately,
I don't have the resources to track -stable as well as I want
at the moment, so I'm submitting this in the hope that someone
will take the time to verify that this problem has now been
fixed. Or commit a usable change to the source tree(s).
>How-To-Repeat:
Boot any system that doesn't have access to a name server that
can turn 224.0.0.0 into something useful. I think. The system
will appear to hang when adding the default gateway. A ctrl-c
clears it, but also seems kill /etc/netstart, which means things
like routed won't get started.
>Fix:
Quoting from <9512131521.AA09355@halloran-eldar.lcs.mit.edu> in
the -hackers mailing list: (long lines broken)
>> The problem is in:
>> # route_multicast="224.0.0.0 -netmask 0xf0000000 \
>> -interface ${hostname}"
>> # route_loopback="${hostname} localhost"
>>
>> If I uncomment this line in sysconfig, the system will not boot.
>
> This line is broken. It /never/ correct to refer to hosts by this
> early in the configuration process, and more importantly, host names
> DO NOT NAME INTERFACES.
>
> The correct way to set this up is as follows:
>
> route_multicast="224.0.0.0 -netmask 0xf0000000 \
> -interface IP.OF.DESIRED.IFACE"
>
> Furthermore, the `route_loopback' bit is completely bogus, and should
> not be present at all.
>
> -GAWollman
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605312255.XAA11739>