the cipe interface's are setup to use 192.168.6.1 and 192.168.6.2 on either end, there are 2 routes, one for the tunnel itself and one for the packets going down the tunnel (as I said class C addresses work fine) I am going to try using a GRE tunnel (per advice from the cipe mailing list) and see how that works.
Mar 30, 2020 · @CNLiberal said in Solution for Multicast Over Tunnel: haven't found decent OpenVPN software for the Mac yet. On this point, the client linked on this page from the OpenVPN Access server docs, in my experience, works fine with an OpenVPN server on pfSense. Just import the standard config. I have not tried this with a tap connection. Apr 08, 2016 · GRE tunnel endpoints: devices we’ll send the multicast traffic between as we lob it over the top of the service provider WAN. In our testing we’re going to use a Cisco 1921 ISR and a Nexus 7613 switch. A couple of test PCs with VLC installed. An mp4 video file; An empty washing up liquid bottle and some eggcartons Multicast IPsec VPN without PIM. This is an example of allowing transparent multicast communication between two networks located behind FortiGates connected via IPsec VPN. Multicast is configured to send traffic across the IPsec tunnel without the use of protocol-independent multicast (PIM) or other multicast routing protocols. Oct 03, 2010 · This use of virtual tunnel interfaces permits consistent PIM state handling for the registration process. During the registration process, the tunnel interface appears like any other interface in the Outgoing Interface List for the multicast data source (S,G) state with all the rules valid for the state management.
In order to route multicast traffic, you need a userspace daemon like smcrouted (recommended) or mrouted. Since you'll also be needing some kind of interface representing the destination network in the routing table, you could create tunnel interfaces for your SSH connection using the ssh -w 0:0.
If a router or switch does not receive a response from the system, the system’s multicast group information is removed from the router or switch’s forwarding table. Note : VPN tunneling supports streaming media at up to 2 mbps on a single tunnel (megabits per second). In order to route multicast traffic, you need a userspace daemon like smcrouted (recommended) or mrouted. Since you'll also be needing some kind of interface representing the destination network in the routing table, you could create tunnel interfaces for your SSH connection using the ssh -w 0:0.
You cannot multicast on the public Internet, but you can multicast across the public Internet to another site by using a tunnel that supports multicast. Multicast routing is very different from unicast routing, and all the routers in the path of the multicast packets need to have multicast routing configured.
The method includes, in response to determining that the multicast source is not multi-homed, forwarding traffic for the multicast source on an inclusive provider tunnel without initiating setup of a selective provider tunnel to the egress network device, and in response to determining that the multicast source is multi-homed, initiating setup the cipe interface's are setup to use 192.168.6.1 and 192.168.6.2 on either end, there are 2 routes, one for the tunnel itself and one for the packets going down the tunnel (as I said class C addresses work fine) I am going to try using a GRE tunnel (per advice from the cipe mailing list) and see how that works.