Re: VPN when host is not gateway
- From: Tiago Cruz <tiagocruz@xxxxxxxx>
- Date: Tue, 24 Jan 2006 11:44:21 -0200
On Mon, 2006-01-23 at 20:49 +0000, Nate Nielsen wrote:
> I'd use tcpdump on the various interfaces (tap devices, ethernet) on the
> machines in question to see exactly at which host is not forwarding the
> packets properly and where they're going.
Thank you Nielsen!
I'm not expert in art of tcpdump, bu I see that:
- OpenVPN in my gateway (192.168.0.1):
1-) client vpn -> [ping] -> 192.168.0.19 [ok]
2-) 192.168.0.19 -> [reply] -> cliente vpn [ok]
- OpenVPN in my backup gateway (192.168.0.253)
1-) client vpn -> [ping] -> 192.168.0.19 [fail]
2-) no reply from 192.168.0.19
I think that this setup will works:
1-) client vpn -> [ping] -> 192.168.0.1 -> [ping] -> 192.168.0.19
2-) 192.168.0.19 -> [reply] -> 192.168.0.1 -> [reply] -> client vpn
So, my questions is this: How I make this route?
Many thanks!
--
Tiago Cruz
http://linuxrapido.org
Linux User #282636
"The box said: Requires MS Windows or better, so I installed Linux"
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: VPN when host is not gateway
- From: Nate Nielsen
- Re: VPN when host is not gateway
- References:
- VPN when host is not gateway
- From: Tiago Cruz
- Re: VPN when host is not gateway
- From: Nate Nielsen
- VPN when host is not gateway
- Prev by Date: Marvell/SysKonnect YukonII source code available
- Next by Date: Re: Marvell/SysKonnect YukonII source code available
- Previous by thread: Re: VPN when host is not gateway
- Next by thread: Re: VPN when host is not gateway
- Index(es):