Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!not-for-mail
From: ggm@bunyip.cc.uq.oz.au (George Michaelson)
Newsgroups: comp.os.386bsd.questions
Subject: Re: NetBSD-current and multicast
Date: 19 Apr 1994 13:14:47 +1000
Organization: Prentice Centre, University of Queensland
Lines: 44
Message-ID: <2ovib7$sum@bunyip.cc.uq.oz.au>
References: <2oog2e$ipf@aggedor.rmit.EDU.AU> <2ot44p$gd1@fw.novatel.ca>
NNTP-Posting-Host: bunyip.cc.uq.oz.au
X-Newsreader: NN version 6.5.0 #2 (NOV)
hpeyerl@sidney.novatel.ca (Herb Peyerl) writes:
>Glen Pill (rxtgep@geppc.xx.rmit.edu.au) wrote:
>: Does anyone know what the option to set in the config file for multicast
>: is? I just recently installed the NetBSD-current GENERICAHA kernel along
>: with the current binaries and would like to get multicast running.
>Multicast has been a non-optional part of NetBSD for a few months now. It
>should just work for you. Please tell someone if it doesn't.
Hang on. You still need to say options MULTICAST MROUTING in the config
file surely....
Also, getting a multicast kernel to enable promiscuous mode can be a
pain, the simplest way is to run mrouted which frobs the kernel the
right way, but since the code in NetBSD 0.9 is oldish multicast, your
local feed to the MBONE may be less than happy to make you routing
active (the older code has some bad scaling behaviour fixed in multicast
3.1 and onwards, but the code in NetBSD has a different kernel
mbuf/malloc usage to the standard code so engineering a new port is
slightly non-trivial)
That said, I've been using it on a PC and a Sparc just fine.
Oh yes. one last thing. NetBSD current has adopted new setsockopt()
flag values which make running the binary-only code (vat, sd) very
hard. Either this needs a new widgit in the compat code, or else you
need to do what I did, and un-convert /usr/include/in.h before making
your kernel and the 6 crucial binaries which reference setsockopt() with
the conflicting flags.
Needless to say the same applies to BSDI and all other *nix flavours,
I understand why these things happen to NetBSD, but for myself, I find
loss of this kind of binary-level compatibility intensely irritating.
Really, the Multicast-use of in.h IP_OPTIONS values pre-dates the
changes and NetBSD should not have overridden them. Live goes on.
-George
--
George Michaelson
Internet: G.Michaelson@cc.uq.oz.au Phone: +61 7 377 4079
Postal: George Michaelson, Prentice Computer Centre
Queensland University, St Lucia, QLD Australia 4067.