Project

General

Profile

Actions
Copy link

Bug #5718

closed

Port forward NAT doesn't work when using a gateway outside interface subnet

Added by Jorge M. Oliveira almost 10 years ago. Updated almost 10 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/30/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Hello,

Following feature #972 implementation, automatic outbound NAT works even when using a gateway outside interface subnet. Previously this required the creation of manual outbound NAT rules.

But... Port forward still doesn't work when using a gateway outside interface subnet.

Those are the settings that cause it to be not working:
https://imgur.com/a/BRWsP

If I change the subnet from 32 to 24 it works (but will "defeat" what implementing the feature meant).

Regards,
Jorge M. Oliveira

Actions
Copy link
 #1

Updated by Jorge M. Oliveira almost 10 years ago

Forgot to mention the version I tested with is: 2.3-ALPHA (amd64) built on Wed Dec 30 04:22:05 CST 2015

Actions
Copy link
 #2

Updated by Jorge M. Oliveira almost 10 years ago

I've found the cause.

VMware Workstation network drivers don't like this kind of configuration and it only "works" when I sniff packets with Wireshark to see what is happening.

If I connect the virtualized pfSense WAN directly my physical network (bridge connection) this feature works.

Please flag this as 'Not a Bug' since the cause was my very specific setup.

Thank you.

Actions
Copy link
 #3

Updated by Jim Pingle almost 10 years ago

  • Status changed from New to Not a Bug
Actions
Copy link

Also available in: Atom PDF