Multicast forwarding not working

  • Thread starter Thread starter Neil
  • Start date Start date
N

Neil

Hello.

Apologies to members of alt.satellite.internet who may not follow a
lot of the first paragraph, but may know the answer!

I am trying to forward UDP multicast traffic on a Windows 2000 server.
I have enabled RRAS, enabled IGMP proxy mode on the external
interface, and router mode on the internal interface. I am trying to
recieve packets on 239.0.4.17 port 9000 - the multicast statistics
show the data coming in, and show it apparently forwarding - however
it isn't! I am using a piece of client software called Kencast Fazzt
Client which joins multicast group 239.0.4.17 on port 9000 - but it
shows no traffic coming through.

I have checked the stats again after starting the client - I can see
my client IP in the group table, as well as the external interface -
but nothing seems to work. Does anyone know how I can get this
working, or can someone provide a software solution (preferably
downloadable). I tried writing a simple UDP program in VB but
couldn't work out how to get the external interface forwarding.

Any help would be appreciated!
 
Neil said:
Hello.

Apologies to members of alt.satellite.internet who may not follow a
lot of the first paragraph, but may know the answer!

I am trying to forward UDP multicast traffic on a Windows 2000 server.
I have enabled RRAS, enabled IGMP proxy mode on the external
interface, and router mode on the internal interface. I am trying to
recieve packets on 239.0.4.17 port 9000 - the multicast statistics
show the data coming in, and show it apparently forwarding - however
it isn't! I am using a piece of client software called Kencast Fazzt
Client which joins multicast group 239.0.4.17 on port 9000 - but it
shows no traffic coming through.

I have checked the stats again after starting the client - I can see
my client IP in the group table, as well as the external interface -
but nothing seems to work. Does anyone know how I can get this
working, or can someone provide a software solution (preferably
downloadable). I tried writing a simple UDP program in VB but
couldn't work out how to get the external interface forwarding.

Any help would be appreciated!
Click to expand...

Hi Neil,

I wrote a udp multicast test program for windows.

I'd love to know more about how satellites and your computer work together
etc.

Can you tell me some more about it ?

The program is at:

http://www.mycgiserver.com/~skybuck

Bye.
 
Hi,

Thanks for replying, I tried your software and it proved to me that
multicast is working fine through the server so I am a bit stuck now! I
found a utility on the internet called "fazztrouter" which joins the
multicast group and forwards the packets on, but unfortunately it doesn't
work - I just get Winsock 10038 errors - not sure why, and the authors email
address just bounces.

For your information though, this is how the satellite connection works..

1. Dial up connection is established
2. Proxy software supplied by Europe Online (Satellite Internet provider) is
started, and I log in to that - it sends out a request over the modem, and
somewhere in the background joins the required multicast groups which are
always streaming on the satellite.
3. Any data I request, i.e. web pages, are requested via the modem, and then
sent over the satellite to a card in my PC, which then in turn sends it
through the OSI layers to the proxy software, and out to my PC

The network config is as follows:

Satellite DVB-S card with IP 192.168.238.238 (Tuned to correct Frequency,
and all multicast PID's set)
Network Card with IP 192.168.0.2

The software called Fazzt is supposed to listen to a 2Mbit multicast stream
on the satellite, which you can request software downloads from - this is
the only thing I am having a problem with unfortunately!

Neil
 
Winsock 10038 is a nasty error.

Copy pasted from another thread:

10038 == WSAENOTSOCK : The descriptor is not a socket.

As to *why* it's happening - difficult to know, likely you are trying to
close the socket twice, or are using an invalid/corrupted value.


My advice try using a different port... maybe multiple applications are try
to use the same port number ?
 
Back
Top