Date: Tue, 26 Apr 2011 16:53:35 +0200 From: Maciej Milewski <milu@dat.pl> To: Ryan Coleman <ryan.coleman@cwis.biz> Cc: freebsd-questions@freebsd.org Subject: Re: OpenVPN routing Message-ID: <201104261653.35417.milu@dat.pl> In-Reply-To: <6ABDD9A5-E75D-4998-8D49-C89B280F32D4@cwis.biz> References: <6073BC9F-553D-41E2-AE42-341B61850EA7@cwis.biz> <BANLkTikvQRGiFS%2BvRu4_tk3aOsFt7zubwA@mail.gmail.com> <6ABDD9A5-E75D-4998-8D49-C89B280F32D4@cwis.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 26 of April 2011 15:45:22, Ryan Coleman wrote: > I have a bridge set up, pingable... but can't ping the em1 (192.168.46.2) from the remote machine. ... > push "route 192.168.47.0 255.255.255.0" Have you tried adding the route to 192.168.46.0/24 subnet into the vpn client? You want to ping the host/interface on different subnet. If you don't set the routing to this subnet how your client should know that he needs to put that packet through tap interface not defaultroute which I suspect is different? Can you show the output of netstat -rn of the vpn client? You may try to look into tcpdump on the vpn router to find what is going with your packets.And for such scenario like vpnclient->vpnserver->network you may even not need nat just simple routing will be enough as long as you set it up on right. My setup is based on tun interfaces and works like a charm. I don't use nat and I only added routing info to the specific routers in the internal networks. Maciej Milewski
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201104261653.35417.milu>