Private LAN setup with Server NICs
-
new to pfSense - so appreciate the help and please advise if my terminology needs improvement.
I am running a Dell PowerEdge 630 with Windows Server 2019. 4 NICs in back.
NIC#1 - Private LAN connection (per my design).
NIC#2 WAN connection.
NIC#3/#4 not used currently.pfSense running in a HyperV VM. Working fine and connecting via Private LAN to HyperV Windows Server 2019 File Server VM. Also, base install of server accesses internet fine from NIC#2.
Problem: Unmanaged Netgear switch connected to NIC#1 and downstream computer unable to connect to internet. On this machine I have tried assigning default gateway and not assigning. tried multiple IP addresses. It has the appearance to me that there is no internet signal being pushed from pfSense/Server from NIC#1 to switch - although both lights are on for each port on the switch. i have not tried direct connecting computer to server without the switch to test if switch is bad.
Private LAN IP addresses:
176.20.10.1 - pfSense
176.20.10.2 - File Server Virtual Machine.
176.20.10.3 - designated for downstream computer from unmanaged Netgear switch.Upstream of Poweredge server:
ATT fiber router in pass through mode
TP Link ER7206 router. Assigning 192.168.0.x/24.
TP Link unmanaged switch. (swapping to a new managed Cisco switch today for creation of VLANs)
Server NIC port #2.I am sure I am missing something simple. My thoughts and questions:
- Is it possible to create a LAN using these NICs in server is server limited to just internal switching? Does assignment of a virtual switch for Private LAN prevent outbound communications on the NIC?
- If yes, is there a BIOS setting I am missing?
- is there a pfSense setting I am missing? Should pfSense LAN settings be DHCP or are there DNS settings I need to edit?
- is there a firewall setting to allow this communication through?
Thanks for the help. If more data needed let me know.
-
Check out Hyper-V Virtual Switch Manager. If pfsense is a VM on HV, create a virtual switch with the external network set to the nic1 interface. You may need to check the box to allow management operating system to share this network adapter if you're not using another port to connect the Hyper-V host to the switch.
-
@ipeetables
Thank you for that reply. I tried that setting - which is only able to be done under external switch and not internal or private. That still did not work - I thought for sure it would.However, it made me think about External, Internal, and Private switches in HV. It looks like from the definitions from Microsoft that Internal and Private Switches only communicate between the host and other VMs on the same host. From Microsoft:
Virtual switch types are:***External virtual switch - Connects to a wired, physical network by binding to a physical network adapter.
Internal virtual switch - Connects to a network that can be used only by the virtual machines running on the host that has the virtual switch, and between the host and the virtual machines.
Private virtual switch - Connects to a network that can be used only by the virtual machines running on the host that has the virtual switch, but doesn't provide networking between the host and the virtual machines.***
My goal is to use the downstream machine as an Ubuntu Server for Veeam backups. i am hoping to do this with a software installation of pfSense if at all possible.
I am eager for additional thoughts here from all.
thanks again.
-
a way to make this setup work is to make the pfsense VM be the router/firewall for both the switch and the hyper-v Host itself (Server 2019 box).
assign two of your NICs to pfsense. one will be the WAN(tp-link 192.168.0.x address), the other will be LAN and connect to the switch. then you have two options: connect a third NIC to the switch for the HyperV Host to use the local lan & internet. Or, allow "operating system to share this network adapter" for the pfsense Lan connection.
-
@ipeetables
Following up here. Your suggestion worked and worked well.Thanks very much.
-
@tonydutt you're welcome!
