Quantcast
Channel: SRX Services Gateway topics
Viewing all articles
Browse latest Browse all 3959

Enable multicast traffic into the same security zone

$
0
0

Hi,

 

I would like to send a multicast stream from a source connected on one interface to an other interface on an Juniper SRX240 (12.1X46).

 

Mutlicast source is connected on ge-0/0/3 interface.

Clients are connected on ge-0/0/1 interface.

 

Here we have the interfaces :

 

 

interfaces {
    ge-0/0/1 {
        unit 0 {
description stb; family inet { address 172.16.1.254/24; } } } ge-0/0/3 { unit 0 { description local-stream; family inet { address 172.16.3.254/24; } } }

 

 

IGMP and PIM configuration :

 

 

> show configuration protocols
igmp {
    interface all {
        version 2;
    }
}
pim {
    interface all {
        mode dense;
        version 2;
    }
}

To simplify the setup, I put the 2 interfaces in the same secury zone named "trust" :

 

 

    zones {
        security-zone trust {
            host-inbound-traffic {
                system-services {
                    all;
                }
                protocols {
                    all;
                }
            }
            interfaces {
                ge-0/0/1.0;
                ge-0/0/3.0;
            }

Since all interfaces are in the same zone, I don't need security rules to allow the multicast traffic between source and receiver.

 

Multicast routing from Multicast source looks good. But When I call stream from a PC I have nothing.

 

> show multicast route group 232.1.20.2 detail
Instance: master Family: INET

Group: 232.1.20.2
    Source: 172.16.3.1/32
    Upstream interface: ge-0/0/3.0
    Session description: Source specific multicast
    Statistics: 0 kBps, 0 pps, 0 packets
    Next-hop ID: 0
    Upstream protocol: PIM

The show multi route command should display a downstream interface list, containing a least the receiver interface ge/0/0/1.0

Here we can see the IGMP request done by the client :

igmp_client.PNG

 

Is it possible that my problem come from the TTL value send by the client, which is equal to 1 on the wireshark screenshot.
 
Any idea ?
 
Best Regards,
 
Bernado
 

 


Viewing all articles
Browse latest Browse all 3959

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>