Re: [pfSense] Client doesn't work if there are multiple network interfaces

2017-03-13 Thread Steve Yates
I am not sure I understand the configuration, however, if you forward a port 
via NAT, pfSense should default to adding a matching firewall rule for it.  If 
you are trying to access the WAN IP from inside the LAN, you will need to 
enable NAT reflection.

You will also need firewall rules allowing traffic between interfaces.

--

Steve Yates
ITS, Inc.

-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Manh Nguyen Tien
Sent: Saturday, March 11, 2017 4:19 AM
To: list@lists.pfsense.org
Subject: [pfSense] Client doesn't work if there are multiple network interfaces

Hello everyone.
I've been stuck for a couple of days setting up a network using virtual
machines.
Could anyone give me some suggestions?

I couldn't access my application if the box has multiple network interfaces.
It has one interface (virtualbox internal network) to connect to pfSense
box.
Another interface is for bridged adapter so my computer can talk to it via
LAN.
My application port can't be reached through pfSense although I forward it
correctly.

I check with another box having only one net interface to pfSense and it
runs without problems.
My client can connect to the service using pfSense's IP and forwarded port.
The real production network has the same schema, only app server stays
behind pfsense for public clients and it also need LAN network to
communicate with other LAN only servers.
So I have some questions:

Q1: Do I need to force all the machines to communicate via pfSense router
only?
Q2: If multiple network interfaces do cause problems, what can I do to
investigate more?

Or maybe someone could share experiences about deploying on Linode.com with
resemble architecture (public app servers with pfSense, Linode's private
LAN for databases), I would very appreciate that.

Thank you in advance.
Manh.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


[pfSense] Client doesn't work if there are multiple network interfaces

2017-03-11 Thread Manh Nguyen Tien
Hello everyone.
I've been stuck for a couple of days setting up a network using virtual
machines.
Could anyone give me some suggestions?

I couldn't access my application if the box has multiple network interfaces.
It has one interface (virtualbox internal network) to connect to pfSense
box.
Another interface is for bridged adapter so my computer can talk to it via
LAN.
My application port can't be reached through pfSense although I forward it
correctly.

I check with another box having only one net interface to pfSense and it
runs without problems.
My client can connect to the service using pfSense's IP and forwarded port.
The real production network has the same schema, only app server stays
behind pfsense for public clients and it also need LAN network to
communicate with other LAN only servers.
So I have some questions:

Q1: Do I need to force all the machines to communicate via pfSense router
only?
Q2: If multiple network interfaces do cause problems, what can I do to
investigate more?

Or maybe someone could share experiences about deploying on Linode.com with
resemble architecture (public app servers with pfSense, Linode's private
LAN for databases), I would very appreciate that.

Thank you in advance.
Manh.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold