Date: Mon, 29 Dec 2008 13:24:32 +0000 (UTC) From: Vadim Goncharov <vadim_nuclight@mail.ru> To: freebsd-current@freebsd.org Subject: Re: NAT (ipfw/natd) broken in latest -CURRENT Message-ID: <slrnglhjsg.1ln5.vadim_nuclight@server.filona.x88.info> References: <1229476796.49670.7.camel@shumai.marcuscom.com> <B583FBF374231F4A89607B4D08578A4302A26B5F@bcs-mail03.internal.cacheflow.com> <1229637745.60337.62.camel@shumai.marcuscom.com> <B583FBF374231F4A89607B4D08578A4302A26E8C@bcs-mail03.internal.cacheflow.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrnglhjsg.1ln5.vadim_nuclight>