Old Synopsis: Port mapping does not work
New Synopsis: FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not work
Responsible-Changed-From-To: gnats-admin->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun May 18 22:45:21 UTC 2008
Responsible-Changed-Why:
Rescue this PR from th
H.fazaeli wrote:
It does work. However, if I understand your setup correctly, the freebsd
box
has been setup to act as a bridge, not as a router (routing is enabled with
sysctl net.inet.ip.forwarding=1). Bridging works when the forwarding is
between the same subnets.
For freebsd box to route b
On Sun, May 18, 2008 at 3:33 AM, Johan Ström <[EMAIL PROTECTED]> wrote:
> On May 18, 2008, at 9:19 AM, Matthew Seaman wrote:
>
>> Johan Ström wrote:
>>
>>> drop all traffic)? A check with pfctl -vsr reveals that the actual rule
>>> inserted is "pass on lo0 inet from 123.123.123.123 to 123.123.123.1
Old Synopsis: page fault after ppp restart and pf resync
New Synopsis: [panic] [altq] page fault after ppp restart and pf resync
Responsible-Changed-From-To: freebsd-net->freebsd-pf
Responsible-Changed-By: vwe
Responsible-Changed-When: Sun May 18 16:57:03 UTC 2008
Responsible-Changed-Why:
altq i
On May 18, 2008, at 9:19 AM, Matthew Seaman wrote:
Johan Ström wrote:
drop all traffic)? A check with pfctl -vsr reveals that the actual
rule inserted is "pass on lo0 inet from 123.123.123.123 to
123.123.123.123 flags S/SA keep state". Where did that "keep state"
come from?
'flags S/SA
Johan Ström wrote:
drop all traffic)? A check with pfctl -vsr reveals that the actual rule
inserted is "pass on lo0 inet from 123.123.123.123 to 123.123.123.123
flags S/SA keep state". Where did that "keep state" come from?
'flags S/SA keep state' is the default now for tcp filter rules -- th
