From owner-freebsd-net@FreeBSD.ORG Sat Aug 4 16:43:37 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECA66106564A for ; Sat, 4 Aug 2012 16:43:37 +0000 (UTC) (envelope-from bthcom@higonnet.net) Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [IPv6:2a01:e0c:1:1599::11]) by mx1.freebsd.org (Postfix) with ESMTP id 0341E8FC0A for ; Sat, 4 Aug 2012 16:43:35 +0000 (UTC) Received: from freebsd.higonnet.net (unknown [82.238.41.134]) by smtp2-g21.free.fr (Postfix) with ESMTP id DAE964B00BB for ; Sat, 4 Aug 2012 18:43:29 +0200 (CEST) Received: from [192.168.4.17] (unknown [192.168.4.17]) by freebsd.higonnet.net (Postfix) with ESMTP id 6E3AF284B8 for ; Sat, 4 Aug 2012 18:44:38 +0200 (CEST) Message-ID: <501D5147.9070905@higonnet.net> Date: Sat, 04 Aug 2012 18:43:51 +0200 From: Bernard Higonnet User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <501696C6.4040208@higonnet.net> <5017806A.8050608@norma.perm.ru> In-Reply-To: <5017806A.8050608@norma.perm.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Uanble to use mpd5 as a gateway VPN, FreeBSD - solved X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Aug 2012 16:43:38 -0000 On 31/07/2012 08:51, Eugene M. Zheganin wrote: > Hi. > > On 30.07.2012 20:14, Bernard Higonnet wrote: >> Hello, >> >> Hope this is the right place to mail... >> >> I have two networks A and B. >> >> One machine on A runs an MPD5 server. >> >> On network B I have machine X which has an MPD5 client used to >> establish a connection the VPN server on machine Z in network A. Seems >> to work fine (ping, ssh, etc.). This machine is also set up as a >> gateway. When I look at the routing table, it looks OK, all references >> to A being sent to Z. >> >> On network B I also have machine Y. On this machine I have added a >> route which specifies that network A is to accessed via machine X. >> >> It would appear (sic) that requests from Y to a machine on A are >> received by that machine. However, nothing ever comes back. >> >> All these machines are running FreeBSD, 8 on Z, and 9.0 on X and Y. >> >> I'm hoping I have forgotten some very obvious thing which a kind soul >> will point out to me so I don't have to tcpdump everything all over >> the place... >> > So.... Z is an mpd, X is a client, Y is a machine behind a client. X > sees Z, Y doesn't see Z because Z isn't answering, however, Z sees > incoming packets. > My guess - Z doesn't know where is the B network, as when X is > exchanging packets with Z, it does it by using it's p2p-address. > > Try to see the output of 'route -n get ' on Z. > If I'm right - add a route, via bundle matching or via up-script, or > manually, or use nat on X. > > Eugene. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" Yes, I had to route add B X Thanks Bernard Higonnet