Re: multicast weirdness

[Chris Kuethe <ckuethe@ualberta.ca>]

On Wed, 2 Jul 2003, Andy Wettstein wrote:

> Hello
>
> I am using zebra 0.93a (the packaged version) and the RIP built in
> to it on openBSD 3.3.  The problem is the RIP updates are not
> properly multicasting.  But when I do a "tcpdump host 224.0.0.9" all
> traffic is received and all the RIP updates work correctly.  When I
> kill tcpdump everything stops working again.  I have a route to
> 224.0.0.9 through 127.0.0.1, but that doesn't seem to help.
>
> I was using zebra on OpenBSD 3.2 and that worked no problems without any
> additionaly configuration.  Is there something that needs to changed on
> 3.3 for multicast, now?

obGrumble: where's your full GENERIC dmesg?

anywaym i've got the same(-ish) problem. i thought it might have been my
interfacesi, so i updated to -stable, and applied the em driver patch in
hopes that that might fix the busted multicast. as it happens, setting
"multicast_host=em1" in /etc/rc.conf didn't work either (though the route
table does have the correct entry.

a lame workaround is to create /etc/bridgename.bridge0 and put
	add fxp0 up
in it (if fxp0 was your multicast interface).

i'm still poking at the hardware to see if maybe the built-in scsi
controllers are breaking things.

CK

-- 
Chris Kuethe, GCIA CISSP: Secure Systems Specialist - U of A CNS
      office: 157 General Services Bldg.    +1.780.492.8135
              chris.kuethe@[pyxis.cns.]ualberta.ca

     GDB has a 'break' feature; why doesn't it have 'fix' too?