From owner-freebsd-ipfw@FreeBSD.ORG Tue Aug 13 09:40:02 2013 Return-Path: Delivered-To: freebsd-ipfw@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 06FD1257 for ; Tue, 13 Aug 2013 09:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E8FAC2873 for ; Tue, 13 Aug 2013 09:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7D9e1aH074625 for ; Tue, 13 Aug 2013 09:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7D9e18F074624; Tue, 13 Aug 2013 09:40:01 GMT (envelope-from gnats) Date: Tue, 13 Aug 2013 09:40:01 GMT Message-Id: <201308130940.r7D9e18F074624@freefall.freebsd.org> To: freebsd-ipfw@FreeBSD.org Cc: From: n j Subject: Re: kern/122963: [ipfw] tcpdump does not show packets redirected by 'ipfw fwd' on proper interface X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: n j List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2013 09:40:02 -0000 The following reply was made to PR kern/122963; it has been noted by GNATS. From: n j To: bug-followup@freebsd.org, zuborg@advancedhosters.com Cc: Subject: Re: kern/122963: [ipfw] tcpdump does not show packets redirected by 'ipfw fwd' on proper interface Date: Tue, 13 Aug 2013 11:37:16 +0200 --14dae94ee3b1c4da3004e3d0fd49 Content-Type: text/plain; charset=ISO-8859-1 Hi, I just ran into this bug on 9.0. Likely present on 9.1 as well. Assume: em0 192.168.1.2 em1 10.1.1.2 # forward to port 80 port 8080 traffic going out via em1 ipfw add 100 fwd 192.168.1.2:80 tcp from me 8080 to 10.1.80.80 out xmit em1 # make sure the traffic goes via em1 route add 10.1.80.80 10.1.1.1 # expect to see outgoing packets tcpdump -i em1 host 10.1.80.80 # but no packets seen nc -p 8080 10.1.80.80 31337 Regards, -- Nino --14dae94ee3b1c4da3004e3d0fd49 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I just ran into = this bug on 9.0. Likely present on 9.1 as well.

Assume:
em0 192.168.1.2
em1 10.1.1.2

# forw= ard to port 80 port 8080 traffic going out via em1
ipfw add 100 fwd 192.168.1.2:80= tcp from me 8080 to 10.1.80.80 out xmit em1

# make sure = the traffic goes via em1
route add 10.1.80.80 10.1.1.1

# expect to see outgoing packets
tcpdump -i em1 host 10.1.80.= 80

# but no packets seen
nc -p 8080 10.1.80.80 31= 337


Regards,
--
Nino
--14dae94ee3b1c4da3004e3d0fd49--