From owner-freebsd-net@FreeBSD.ORG Sat May 10 14:55:25 2008 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 67CC3106566C for ; Sat, 10 May 2008 14:55:25 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id DAE548FC25 for ; Sat, 10 May 2008 14:55:24 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO [192.168.3.2]) by cmail.optima.ua (CommuniGate Pro SMTP 5.1.14) with ESMTPA id 123739658; Sat, 10 May 2008 17:55:24 +0300 Message-ID: <4825B75B.9050604@FreeBSD.org> Date: Sat, 10 May 2008 17:55:23 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Oleksandr Samoylyk References: <48207C8B.4020509@samoylyk.sumy.ua> <48209BC4.5080602@elischer.org> <1210148584.00067004.1210135802@10.7.7.3> <1210155784.00067045.1210144801@10.7.7.3> <1210195392.00067265.1210183802@10.7.7.3> <1210195402.00067283.1210184402@10.7.7.3> <1210202586.00067324.1210189802@10.7.7.3> <1210202588.00067326.1210189802@10.7.7.3> <1210202593.00067329.1210190402@10.7.7.3> <1210209785.00067436.1210197002@10.7.7.3> <4825B177.7020503@FreeBSD.org> <4825B397.4060005@samoylyk.sumy.ua> In-Reply-To: <4825B397.4060005@samoylyk.sumy.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Julian Elischer Subject: Re: Problems with netgraph 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, 10 May 2008 14:55:25 -0000 Oleksandr Samoylyk wrote: > Alexander Motin wrote: >> Oleksandr Samoylyk wrote: >>> Julian Elischer wrote: >>>> this may be the issue: >>>> http://www.nabble.com/GRE-Mux-td16201899.html >>> >>> I think so. Should we hope for some progress in this direction in >>> future? >> >> This is not an issue any more for mpd. >> Originally multiplexing based on peers addresses by socket binding and >> connecting was used. There was only problem with multiplexing multiple >> calls inside the same tunnel (having the same peer addresses). >> Recent time (ng_pptpgre.c rev. 1.41 of Mar 24 2008) I have improved >> ng_pptpgre node to do multiplexing alike to the ng_l2tp node does and >> the latest mpd-5.1 is able to use this feature when it is present at a >> build time. >> > > * $FreeBSD: src/sys/netgraph/ng_pptpgre.c,v 1.40.2.1 2008/03/30 > 08:01:26 mav Exp $ As I can see you have build mpd before system build. Probably mpd was built on a system without this feature present yet: # uname -a FreeBSD xxx.xxxxxxxxx.xxx 7.0-STABLE FreeBSD 7.0-STABLE #0: Sat May 3 12:40:02 EEST 2008 xxxxx at xxx.xxxxxxxxx.xxx:/usr/obj/usr/src/sys/XXXX amd64 # mpd5 -v Version 5.1 (root at xxx.xxxxxxxxx.xxx 09:53 1-May-2008) Try to rebuild mpd to be sure it uses this feature. Also you can check this by observing the name of any ng_pptpgre hook used. If it is "upper", then ng_pptpgre multiplexing is not used and if it is "session_hhhh" then OK. -- Alexander Motin