only use ROUTED OpenVPN.
As I said, I have several OpenVPN installations with Shorewall (obviuos).
And there a mix of remote endpoints and remote networks in the same Linux
box. "client-to-client" does the job.
Only one special consideration is when you have site-to-site tunnel, you
need also include " iroute" option to the remote network.
--
Gilson Soares
Gerência de Redes e Segurança
Kobold Gestora de Fundos Ltda
PS: I forgot to send to the list.
On 3/27/08, Tom Eastep <[EMAIL PROTECTED]> wrote:
>
> Gilson Soares wrote:
> > I don´t know the inner working of OpenVPN, but I suppose using
> > "client-to-client" option make the OpenVPN daemon do the routing, not
> > even leave the packets go thru O.S. routes.
> > I have several similar setups and never need to use routeback option.
> > Just "client-to-client" solved this problem.
>
> I'm just saying that we've had reports that 'client-to-client' is
> ineffective in routed setups. I haven't tried it. But I do use
> 'client-to-client' with my bridged configuration and it works fine.
>
> Can you confirm that 'client-to-client' works in a ROUTED OpenVPN
> configuration?
>
> -Tom (who wonders if he inadvertently dropped in on #openvpn)
> --
> Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
> Shoreline, \ http://shorewall.net
> Washington USA \ [EMAIL PROTECTED]
> PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
>
>
>
--
Gilson Soares
Gerência de Redes e Segurança
Kobold Gestora de Fundos Ltda
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
