From owner-freebsd-current@FreeBSD.ORG Mon Dec 29 19:59:40 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 105B4106566B; Mon, 29 Dec 2008 19:59:40 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id BE9918FC0C; Mon, 29 Dec 2008 19:59:39 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id mBTJxc7V023405; Mon, 29 Dec 2008 11:59:39 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 29 Dec 2008 11:55:01 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NAT (ipfw/natd) broken in latest -CURRENT Thread-Index: AclpuS8DTvuZXrheSiGVGwXCu5byZwANicF5 References: <1229476796.49670.7.camel@shumai.marcuscom.com><1229637745.60337.62.camel@shumai.marcuscom.com> From: "Li, Qing" To: , Cc: qingli@freebsd.org Subject: RE: NAT (ipfw/natd) broken in latest -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 19:59:40 -0000 Hi Vadim, =20 I don't quite understand your question. =20 The ppp route insertion code always set the RTF_GATEWAY flag regardless whether the gateway information is present. I fixed the code such that the RTF_GATEWAY is set only if gateway is given. =20 This ppp bug appears to be uncovered by the arp-v2 changes, however, I was informed another thread on net@ also raised a ppp issue of similar erroneous behavior in 7.x. =20 So if I remember correctly, the problem you've reported is a different issue. I had to fix the kernel code. =20 -- Qing ________________________________ From: owner-freebsd-current@freebsd.org on behalf of Vadim Goncharov Sent: Mon 12/29/2008 5:24 AM To: freebsd-current@freebsd.org Subject: Re: NAT (ipfw/natd) broken in latest -CURRENT 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] _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"