Date: Sat, 25 Feb 2006 09:49:20 GMT From: Vlad GALU <vladgalu@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/93825: pf reply-to doesn't work Message-ID: <200602250949.k1P9nKoS015998@www.freebsd.org> Resent-Message-ID: <200602250950.k1P9o4nG075734@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 93825
>Category: kern
>Synopsis: pf reply-to doesn't work
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Feb 25 09:50:04 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Vlad GALU
>Release: 6.1-PRERELEASE
>Organization:
>Environment:
FreeBSD snakepit.afraid.org 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Mon Feb 6 12:14:23 EET 2006 root@snakepit.afraid.org:/usr/src/sys/i386/compile/SNAKEPIT i386
>Description:
This is a multihomed machine. I expect replies to requests that came on one interface to leave the machine on the same interface. This doesn't happen.
>How-To-Repeat:
Assuming you have packets coming in through $local_if, and the following ruleset:
pass in quick on $local_if reply-to ($local_if $local_gw) \
inet proto tcp from any to ($local_if) \
port = 80 flags S/SA keep state
This rule does create state, but the packets leave the machine through the interface the default route is connected to, which is not $local_if.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602250949.k1P9nKoS015998>