|
|
tdb@xxxxxxx wrote: Ok, I'm a beginner at this stuff, but let me try to take a stab. If I understand it, you want multicast traffic to go over the tunnel. Have you tried using a tap device instead of a tun? A tap device will carry any traffic that will go over ethernet, tcp, udp, ipx, netbeui, etc... I think that will carry any traffic that hits the interface. Yes, that's what we've been using with vtund. It has multiple problems though; we have to use ebtables to strictly control what goes over the tunnel (to reduce wasted bandwidth), and the systems that are talking to each other don't know there's a router hop (or more) in between them. Since these are VoIP phones, it's important that they be aware of the network topology as much as possible. Since I posted my original question I have successfully got a solution set up using normal tun devices. I don't the multicast routing in place, but I have tested a working solution using mrouted and the appropriate tunnels. It will require predefining a tun device, routes and other settings for _each_ remote user, and each remote user will have to connect to a specific OpenVPN daemon on the server, but I can arrange for that. In fact, using OpenVPN's --tls-remote-name parameter, I can even ensure that noone accidentally connects to the _wrong_ OpenVPN daemon. ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |