multicast connection problems

[Chattha, Ishwinder S.]

Hi everyone, 

I have run into a little problem that I can’t seem to find a solution for so I am turning to the experts for help.  :D

 

I have a program that listens on the network for multicast I can get it run on the box that is multicasting however not on a separate box (called box t for now).   The program returns this message when run on box t (I put the XX because of DOT security requirements):

**** Ready To Join a Multicast Group: 224.1.1.XX /10193

IP_ADD_MEMBERSHIP setsockopt: No such device

Can't connect to XXX multicast host:224.1.1.XX  port:10193 - status:-5005

 

Now on the box t I have setup a tcpdump tcp port 10193 then ssh –p 10193 XXX.XX.XX.XX (ip address of the box that is multicasting).  Tcpdump shows that a send and reply events even though the connection was refused.  Also on box t if I do a tcpdump udp port 10193 I am able to see the multicast broadcasting the info. 

 

Any suggestion on what else I can try or why box t is not connecting to the multicast?

 

Once again sorry for the X and what not I am limited because of security policies. 

Thanks

Ish

[Steve Nordquist]

> **** Ready To Join a Multicast Group: 224.1.1.XX /10193
> IP_ADD_MEMBERSHIP setsockopt: No such device
> Can't connect to XXX multicast host:224.1.1.XX  port:10193 - status:-5005

Multicast datagram types not included in box t kernel or other ip
stack; ipfw rejection or selection to whatever can ignore streams and
IP addresses efficiently?
PIM assert or other multicast heartbeat on intermediary routers if any?
Box t has to file need-to-know? ;`o

[John McPherson]

Sometimes adding a route for multicast traffic ( "route add 224.0.0.0 netmask 240.0.0.0 dev eth0" in Linux) will allow you to use multicast.

-- 
You received this message because you are subscribed to the Google Groups "kulua-l" group.
To post to this group, send email to kul...@googlegroups.com.
To unsubscribe from this group, send email to kulua-l+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/kulua-l?hl=en.

[Billy Crook]

That is a commonly overlooked requirement if your machine is
multihomed, and the default route is on another interface than the one
on which you want to do multicast.

[Chattha, Ishwinder S.]

Ok great, thanks guys I will try that out today.
Thanks again
Ish

-----Original Message-----
From: kul...@googlegroups.com [mailto:kul...@googlegroups.com] On Behalf Of Billy Crook
Sent: Thursday, May 12, 2011 1:31 PM
To: kul...@googlegroups.com
Subject: Re: [KULUA] multicast connection problems

That is a commonly overlooked requirement if your machine is
multihomed, and the default route is on another interface than the one
on which you want to do multicast.

On Thu, May 12, 2011 at 08:54, John McPherson <xeni...@gmail.com> wrote:
> Sometimes adding a route for multicast traffic ( "route add
> 224.0.0.0 netmask 240.0.0.0 dev eth0" in Linux) will allow you to use
> multicast.
>
>
>
> On May 11, 2011, at 1:50 PM, Chattha, Ishwinder S. wrote:
>
> Hi everyone,
> I have run into a little problem that I can't seem to find a solution for so
> I am turning to the experts for help.  :D
>
> I have a program that listens on the network for multicast I can get it run
> on the box that is multicasting however not on a separate box (called box t
> for now).   The program returns this message when run on box t (I put the XX
> because of DOT security requirements):
> **** Ready To Join a Multicast Group: 224.1.1.XX /10193
> IP_ADD_MEMBERSHIP setsockopt: No such device
> Can't connect to XXX multicast host:224.1.1.XX  port:10193 - status:-5005
>

> Now on the box t I have setup a tcpdump tcp port 10193 then ssh -p 10193