Pfsense with 3 NICS

bryan.paradis

@bryan.paradis:

@Jamerson:

Dear All,
i have on my ESXI Pfsense 2.1 with 3 NICS
1 WAN
1 LAN
1 LAN 2
the issue is all is working beside the LAN2 when the users are connectiong to the LAN 2 and using it as gateway they can't browse to the internet
i've checked the firewall rules they are file,
P.S. users on the Lan are fine !
can you please point me to the right direction ?

Go to Interfaces -> Assign -> Bridges tab -> Create bridge of LAN1 and LAN2 unless you want them as seperate lans for some reason

hi Bryan,
yes I want both of them to be separated,
is this possible ?

What kind of separation? What is the goal?

stephenw10

What subnets are you using for LAN and LAN2?
Do you see anything in the firewall logs when LAN2 users try to connect?

Please give as many details as possible.

Steve

johnpoz

What firewall rules do you think are fine? Did you turn off automatic nat?

Jamerson

Dear Bryan,
the Goal is both not to reach each otherse, from each side there is a File server which is gonna be restricted. also LAN2 NIC will have different restriction than LAN1

Stephen
LAN 1 is 192.168.4.0/24
LAN2 is 192.168.6.0/24

John:
Automatic NAT is on
the firewall rules are exactly the same on both NICS, Allow all
but LAN1 works and LAN2 no,

the only different is LAN2 not attached to a Physique NIC and LAN1 it does so as it showen on the attached

LAN2.jpg_thumb

stephenw10

I assume you add some VMs to vSwitch2 to tests LAN2?

You realise the firewall rule on LAN2 must have the source address as the LAN2 subnet or 'any'. It differs from the LAN default rule in that way.
Since you don't mention it I assume you're not seeing anything in the firewall logs.

Steve

bryan.paradis

@Jamerson:

Dear Bryan,
the Goal is both not to reach each otherse, from each side there is a File server which is gonna be restricted. also LAN2 NIC will have different restriction than LAN1

Stephen
LAN 1 is 192.168.4.0/24
LAN2 is 192.168.6.0/24

John:
Automatic NAT is on
the firewall rules are exactly the same on both NICS, Allow all
but LAN1 works and LAN2 no,

the only different is LAN2 not attached to a Physique NIC and LAN1 it does so as it showen on the attached

Go to Esxi - firewall vm properties -> Add a third network card and place it on LAN2
Go to pFsense -> Interfaces -> Make sure the third interface is assigned and labeled
Go to pFsense -> Services -> DHCP Server -> Press the third interface tab -> Setup up DHCP
Go to pFsense -> Firewall -> Outbound -> Press "Add a new rule based on this one" For the "Auto created rule for LAN to WAN" and change the source to reflect your second LAN subnet

Jamerson

@bryan.paradis:

@Jamerson:

Dear Bryan,
the Goal is both not to reach each otherse, from each side there is a File server which is gonna be restricted. also LAN2 NIC will have different restriction than LAN1

Stephen
LAN 1 is 192.168.4.0/24
LAN2 is 192.168.6.0/24

John:
Automatic NAT is on
the firewall rules are exactly the same on both NICS, Allow all
but LAN1 works and LAN2 no,

the only different is LAN2 not attached to a Physique NIC and LAN1 it does so as it showen on the attached

Go to Esxi - firewall vm properties -> Add a third network card and place it on LAN2
Go to pFsense -> Interfaces -> Make sure the third interface is assigned and labeled
Go to pFsense -> Services -> DHCP Server -> Press the third interface tab -> Setup up DHCP
Go to pFsense -> Firewall -> Outbound -> Press "Add a new rule based on this one" For the "Auto created rule for LAN to WAN" and change the source to reflect your second LAN subnet

Bryan,
Go to pFsense -> Firewall -> Outbound -> Press "Add a new rule based on this one" For the "Auto created rule for LAN to WAN" and change the source to reflect your second LAN subnet
Do you mean create the same rule as LAN1 ? or Edit the Rule ?
on the firewall in dont have OUTBOUND option.
do i need some plug in ?

stephenw10

It's in Firewall: NAT: Outbound:
However by default the outbound NAT mode is set to 'Automatic outbound NAT rule generation'. That will work fine for your dual LAN setup. There should be need to add manual outbound rules as long as it's still set to automatic.

Please post your LAN2 firewall rules, a screenshot if possible.

Steve

Jamerson

@stephenw10:

It's in Firewall: NAT: Outbound:
However by default the outbound NAT mode is set to 'Automatic outbound NAT rule generation'. That will work fine for your dual LAN setup. There should be need to add manual outbound rules as long as it's still set to automatic.

Please post your LAN2 firewall rules, a screenshot if possible.

Steve

hi Stephen
there is only one rule to allow the whole traffic,
attached is the screenshot
how can i do this exactly ?

Go to pFsense -> Firewall -> Outbound -> Press "Add a new rule based on this one" For the "Auto created rule for LAN to WAN" and change the source to reflect your second LAN subnet

on the Outband there is no Manual rules yet. just Automatically.
i've configured a user with 192.168.6.0/24 on the same NIC but can't ping 192.168.6.1 the router
firewall screenshot is of the client behind the LAN2 when try to browse.
Much appreciate it !

LAN2.jpg_thumb

Firewall.jpg_thumb

bryan.paradis

@stephenw10:

It's in Firewall: NAT: Outbound:
However by default the outbound NAT mode is set to 'Automatic outbound NAT rule generation'. That will work fine for your dual LAN setup. There should be need to add manual outbound rules as long as it's still set to automatic.

Please post your LAN2 firewall rules, a screenshot if possible.

Steve

Yeah that makes sense. It should make it automatically

johnpoz

Why would you have a block rfc1918 rule on your LAN interface? You do understand your lan2 would be private, and pfsense own IPs on that lan would be rfc1918 as well

LAN 1 is 192.168.4.0/24
LAN2 is 192.168.6.0/24

And how is anything suppose to get to lan2 when there is nothing in your vswitch for lan 2 - what interface in pfsense is connected to lan2?

stephenw10

Yep that's your problem.
Go to Interfaces: LAN1: and uncheck 'block private networks' and 'block bogon networks'.
Bogons may not be necessary but there's no need to block them on LAN.

Steve

bryan.paradis

@johnpoz:

Why would you have a block rfc1918 rule on your LAN interface? You do understand your lan2 would be private, and pfsense own IPs on that lan would be rfc1918 as well

LAN 1 is 192.168.4.0/24
LAN2 is 192.168.6.0/24

And how is anything suppose to get to lan2 when there is nothing in your vswitch for lan 2 - what interface in pfsense is connected to lan2?

@stephenw10:

Yep that's your problem.
Go to Interfaces: LAN1: and uncheck 'block private networks' and 'block bogon networks'.
Bogons may not be necessary but there's no need to block them on LAN.

Steve

What is the default on those when configuring a new interface ?

johnpoz

OFF, it only defaults to be on WAN interface.

bryan.paradis

@johnpoz:

OFF, it only defaults to be on WAN interface.

This is what I had thought so I assume he must have changed options or maybe reversed his iunterfaces at some point and had to reassign?

Jamerson

Why would you have a block rfc1918 rule on your LAN interface? You do understand your lan2 would be private, and pfsense own IPs on that lan would be rfc1918 as well

LAN 1 is 192.168.4.0/24
LAN2 is 192.168.6.0/24

And how is anything suppose to get to lan2 when there is nothing in your vswitch for lan 2 - what interface in pfsense is connected to lan2?

hi Bryan,
i am using all my 3 NICS to use Teaming so all traffic will go thought the WAN.

 Yep that's your problem.
Go to Interfaces: LAN1: and uncheck 'block private networks' and 'block bogon networks'.
Bogons may not be necessary but there's no need to block them on LAN.

Steve

those rules were added automatically when i created the rules.
you mean i need to uncheck all private Network between the LANS ?

is it possible to have all traffic go out and in thought the WAN wihtout assign a physique NIC on the Vswitch ?

creating a Vlan with one Physique NIC could fix the issue ?

stephenw10

Uncheck the two boxes on the interface setup page.
It doesn't matter that all the traffic is going to the WAN. The source is the LAN subnet which is a private network. If you look at your firewall rules for that interface you'll see that the 'block private networks' rules is at the top of the list so it matches the incoming packets first and the 'allow all rules' are never reached. The 'block private networks' check box is only there for WAN interfaces where you would not expect traffic arriving with an RFC1918 source address unless it's been spoofed.

Steve

johnpoz

"those rules were added automatically when i created the rules."

No I highly doubt that, nnless you created a WAN interface, by putting a gateway on it?

"i am using all my 3 NICS to use Teaming so all traffic will go thought the WAN."

What – no you are not.. I suggest you look up the term "teaming" as it has to do with network interfaces - you are not doing that ;)

"is it possible to have all traffic go out and in thought the WAN wihtout assign a physique NIC on the Vswitch ?"

Sure - if your Other vm's have an interface in that vswitch - see example below on my dmz vswitch. There is an interface connected to my pfsense VM, and then the other vms that need to use this interface on pfsense are tied to that same vswitch. It does not need to be tied to the physical network. But it can access the physical network through pfsense that has its other lan and wlan in my case tied to physical networks. See attachment 2

nophysical.png_thumb

Jamerson

@johnpoz:

"those rules were added automatically when i created the rules."

No I highly doubt that, nnless you created a WAN interface, by putting a gateway on it?
"i am using all my 3 NICS to use Teaming so all traffic will go thought the WAN."

What -- no you are not.. I suggest you look up the term "teaming" as it has to do with network interfaces - you are not doing that ;)
this where i want to go to, use all my NIC for teaming

"is it possible to have all traffic go out and in thought the WAN wihtout assign a physique NIC on the Vswitch ?"

Sure - if your Other vm's have an interface in that vswitch - see example below on my dmz vswitch. There is an interface connected to my pfsense VM, and then the other vms that need to use this interface on pfsense are tied to that same vswitch. It does not need to be tied to the physical network. But it can access the physical network through pfsense that has its other lan and wlan in my case tied to physical networks. See attachment 2

the machine on your DMZ can reach the internet even there is no Physique interface?
this exactly what i am looking for.

johnpoz

Yes why would they not.. They are connected to a switch that is in connected to pfsense interface (be it all virtual), which has physical connection to the real network.

That is not TEAMING.. where did you come up that you think you want to do teaming?

Teaming in reference to network, call it link aggregation, port trunking, nic teaming, bonding has nothing to do with this.

But notice in your drawing - there is NOTHING connected to your switch, no vm's no interface in pfsense that your calling lan2, but where is that connected to a vswitch?