If the readiness of the client would be sent to the server as unicast (TCP) … * sigh *

Ok i try it
The man page of udp-receiver I know and therefore knows that the L2 registration over the broadcast and had it also verified with my tracker. Because of the, in my network structure necessary multicastforwarding as source IP is displayed not the client IP but the forwarder.

I’m wondering how the FOG makes multicast distribution beyond broadcast boundaries. You have in your wikis rudimentary hints to multicast routing (PIM with dense-spars-mode). The real mc works with me yes …

Regardless of my problems - THANKS to the team for your gigantic work!

Server

• FOG Version: 1.3.4-rc-2 (SVN 6063)
• OS: Debian 8 (Jessie)

Description:

The fog works with L2 mc deploy without problems.
If it is to deploy to another broadcast domain, the multicast does not start.

The forwarding is via PIM in dense mode and the function has been verified with IC_Tester_Mcast_v02 (MC forwarding no problems!)

The “FOG Multicast error search” (udp-sender … / udp-receiver) does not register the client. With the addition --mcast-rdv-address <IP-FOG>, the FOG reports “problem getting data from Client: Success”

In the log is also not the ip of the client but the gateway.

Forwarding is controlled by a checkpoint SG.

Any idea?