From owner-freebsd-current@FreeBSD.ORG Mon Dec 29 13:24:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F61B1065670 for ; Mon, 29 Dec 2008 13:24:46 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id EED2C8FC1F for ; Mon, 29 Dec 2008 13:24:45 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LHI6r-0000PG-5r for freebsd-current@freebsd.org; Mon, 29 Dec 2008 13:24:41 +0000 Received: from 195.208.174.178 ([195.208.174.178]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Dec 2008 13:24:41 +0000 Received: from vadim_nuclight by 195.208.174.178 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Dec 2008 13:24:41 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Vadim Goncharov Date: Mon, 29 Dec 2008 13:24:32 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 36 Message-ID: References: <1229476796.49670.7.camel@shumai.marcuscom.com> <1229637745.60337.62.camel@shumai.marcuscom.com> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 195.208.174.178 X-Comment-To: Li, Qing User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: NAT (ipfw/natd) broken in latest -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2008 13:24:46 -0000 Hi Li, Qing! On Thu, 18 Dec 2008 17:41:02 -0800; Li, Qing wrote about 'RE: NAT (ipfw/natd) broken in latest -CURRENT': > I have checked in a fix for this issue (r186308), which turned out to > be a problem in the ppp module. The ppp module updates the p2p host > route that was installed during the tunnel configuration, however, the > ppp code always set the RTF_GATEWAY flag. The patch has been verified to > be working by Joe. Will it break again all the NAT-PMP using programs which need to determine IP-address of default gateway? Currently it works with mpd, which sets default gateway to correct IP, not an interface or self route. >>>> My netstat on the server side looks like: >>>> >>>> Internet: >>>> Destination Gateway Flags Refs Use > Netif >>>> Expire >>>> default 172.18.254.1 UGS 0 46685 > em0 >>>> 10.1.1.76 link#5 UGH 0 1735 > tun0 >>>> 127.0.0.1 link#3 UH 0 1171 > lo0 >>>> 172.18.254.0/24 link#1 U 0 0 > em0 >>>> 172.18.254.237/32 link#1 U 0 8 > em0 -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]