pfSense on Hyper-V Home Setup questions.



  • Hi there!

    I want to install pfSense on my home lab and I have some questions/. Here are the data :

    I have :

    1. an Asus DSL AC-68U router
    2. a Hyper-V host (Windows 2012 R2 with 8GB of RAM and two (2) NICs.
    3. a physical workstation PC
    4. One Laptop
    5. Smartphones
    6. One Tablet
    7. A Netgear Managable Switch (8 ports)

    and I want to be able to use pfSense only as a Firewall for my network.

    I have a Windows 2012 R2 VM installed on Hyper-V as a DC for my Active Directory and also, yesterday, I installed pfSense as a VM on Hyper-V (I followed the online manual of Netgear Support pages).

    I want my physical workstation but also the wireless clients, to be able to be protected behind the pfSense firewall VM and I have an "understanding" problem of how I'm gonna be able to accomplish that.

    Can you please help me understand the network diagram that I will have to design\deploy to make it work?

    As I am guessing I have to design this kind of network diagram :

    network.png

    But, the wireless clients? How are they gonna passthrough the pfSense first?

    As you guessed it, I am a little bit confused. :/


  • LAYER 8

    disable the wireless on the asus, buy an AP and put it in a vlan



  • @kiokoman There is no other way right?


  • LAYER 8 Global Moderator

    Use your wifi router as just AP and put it behind pfsense.. You can do that with pfsense as VM.. Does your VM host have more than 1 nic?

    If not then you would need a vlan switch between your isp modem and the rest of your network..



  • @johnpoz My Asus AC68U is a modem/router. So I use it as my ISP modem and then as a router. I dont know if I can use it as AP only (and not losing the routing operations of this device). I dont have a separate ISP modem. Also, my hyper-v host has 2 nics.


  • LAYER 8 Global Moderator

    Then you have the wrong model number posted, a RT-AC68U is not a gateway device. The ac68u is a very common "router" only device.. Good reason to make sure post exact modem number ;) heheheh

    You have a DSL-AC68U?

    if your device is a gateway, then no you can not.. You would need to get a different modem or AP.. So you can separate the functionality of your modem and your AP.

    Once you can sep the functions - then yeah its very easy to put everything behind pfsense - even your wifi... What I would suggest is get a real AP, vs modem and using your current device as just AP... Say a unifi AP that supports vlans - this will allow you to create multiple segments for wifi, as long as you have a vlan capable switch - which I assume you do since you call out vlans in your drawing - what is the exact model of this netgear?



  • @johnpoz oh man! sorry. :) Yes, I have a DSL-AC68U. My netgear switch is a GS108T. So I think I might keep Asus as a modem and the buy a Unifi AP (Im watching videos right now, for the AirCube ACB-AC) and separate my wifi and put it behind pfSense right?


  • LAYER 8

    yup, exactly as i said, it 's the best solution, this way you can place the access point in a better position


  • LAYER 8 Global Moderator

    @uxm said in pfSense on Hyper-V Home Setup questions.:

    AirCube ACB-AC

    No that is not what you would want... That is airmax... If you want something you just set on a table or something you prob want the https://store.ui.com/collections/wireless/products/unifi-flexhd

    Why can you not just get a normal AP that is mounted?
    This is more what you would setup in a home as your AP
    https://www.ui.com/unifi/unifi-ac/


  • LAYER 8

    @uxm said in pfSense on Hyper-V Home Setup questions.:

    AirCube ACB-AC

    did pay attention to this, yeah, listen to johnpoz


  • LAYER 8 Global Moderator

    Yeah not sure what video's he is watching... But that is not wifi AP you would use in a home setup..

    deployment.png



  • @johnpoz sorry I didnt know that Aircube is for costumers deoloyment. I think I will go for the Unifi AP-AC as you said.

    Can I ask one more question? Should the virtual switches on my pfSense be internal and external? How will I be able to manage it? From the host itself or a VM? I thing my physical workstation will not be able to access it, right?


  • LAYER 8 Global Moderator

    You would manage esxi host via the vmkern, which would be on your lan network..



  • @johnpoz I dont have VMware esxi installed


  • LAYER 8 Global Moderator

    Sorry hyper-V just admin it from the lan side



  • @johnpoz that was my question/statement. That I cant admin it from lan side by a physical pc if the pfsense vm connects to an internal (hyperv) virtual switch. :(


  • LAYER 8 Global Moderator

    You do understand pfsense can have multiple lan side interfaces right, and VM switches can be tied to physical network a well.. Maybe your issue is you don't actually get how VM Hosts work?

    Your drawing is tied to both physical and virtual networks - so not sure why your confused?



  • I know how Hyper-V works..The actual reason that I am confused, is that I can't ping pfsense from my physical PC nor I can admin it.

    Physical PC : 192.168.2.108
    Pfsense Internal side : 192.168.2.10

    both on the same LAN/VLAN.


  • LAYER 8 Global Moderator

    Well then you have something setup wrong. Or not connected how you think its connected, etc.



  • @johnpoz Yeah I guess so. I will try to find the reason. There is no reason to bother you with that kind of questions but I will come back if I cant make it work.

    Thank you ALL for your precious help! This community seems to be totally ALIVE!



  • For this, both your LAN and WAN switches should be External.

    Private - allows VM to VM comms
    Internal - allows VM to VM comms plus comms to Host
    External - As above, plus outside world

    On the LAN v-switch, you can select the sharing checkbox below (I don't on mine because i have a 4-port NIC where I assign the host a port of its own). Then you can manage the VM from the host OS.
    8699a045-7560-4df4-afcd-60406f44649a-image.png
    I just run a flat network with no VLANs. I don't really see the point in a home setup, just more complexity.

    Internet--Modem--Host--pfSense--Switches--Access Points--Clients

    Only reason I'd use a VLAN would be it I was trying to use a single NIC board as a pfSense hardware firewall (Router-on-a-stick). You could use your Asus as an AP by just plugging one of the LAN (not WAN) ports into your network as long as the LAN side is configured as the same network as the rest of your LAN, but you'd still need to buy a modem. HTH


  • LAYER 8 Global Moderator

    @provels said in pfSense on Hyper-V Home Setup questions.:

    I don't really see the point in a home setup, just more complexity.

    Do you have more things on this flat network than just your PC or a couple of devices - iot, stuff that is serving up to the internet, etc.. You would use vlans or other network segments as a means to secure your network..

    He doesn't need a modem - he needs an AP he can use his current device as just the modem and turn off its wifi.. Or use it as well as different non filtered wifi network that is on the "wan" side of pfsense.



  • @johnpoz No IoT, even though my refrigerator and dishwasher could talk to the world if I desired it. No Alexa or other because I would want an always-on mic in my house..., why? I have no desire to talk to any device unless it is a phone and there is a live body on the other end. Several network receivers, couple phones, Hyper-V host that is also my main workstation with pfSense and several other workstation OS, smart TV, and a lappy for RDP. I even run G wireless with MAC filtering and hidden SSIDs (the horror!) And it's just me, so.... no need for guest nets. And no FB or Twitter even, because that is just largely the toilet of the Internet. anyway. So there.

    Agreed, I know he doesn't need a modem, but he will have to buy something to do what he wants. Frankly I'd just ditch the gateway on EBay and buy discreet components. Kind of depends how many of his clients are in use simultaneously as well.


  • LAYER 8 Global Moderator

    @provels said in pfSense on Hyper-V Home Setup questions.:

    I even run G wireless with MAC filtering and hidden SSIDs

    Because that is pointless ;) And you like added pain for no reason?



  • @johnpoz Point? I have trusted devices in family, anyone else can pay for their own data.


  • LAYER 8 Global Moderator

    None - its pointless to do such a thing.. You just added complexity for ZERO reason other than your own grief.. But someone segmenting out their network for actually security reasons is pointless complexity?

    If you don't want someone on your wifi - then don't give them the PSK.. There is zero reason for mac filtering or not broadcasting the SSID.



  • @johnpoz Well, if you can find me, feel free to hack my wireless. At any rate, it still depends WHY he wants to do it. Just because you CAN doesn't mean you SHOULD. Sort of how I feel about running a DC on a home net...



  • So, for my pfsense, to be able to "talk" to the physical workstations on the network, there must be two external virtual switches on the hyperv hosts right?



  • @uxm said in pfSense on Hyper-V Home Setup questions.:

    So, for my pfsense, to be able to "talk" to the physical workstations on the network, there must be two external virtual switches on the hyperv hosts right?

    Yep, and one pf interface min hooked to each.



  • Sorry for returning back after so long. I had some personal issues and didnt have the time for pfsense. I will try to continue this project. So, I have a Hyper-V with 2 VMs. One is the pfsense VM and the other is my DC (for my Active Directory) with Windows 2012 R2 installed. The Hyper-V host has three NICs. I gave two nics for the pfsense (lan and wan) and one nic to my Windows 2012 R2 DC Server.

    I have a netgear manageable switch. How many VLANs I have to create? Two right? One is the "wan side VLAN" and the other is the "LAN side VLAN" right?

    Can you help me please?..

    fbe5657d-8fcd-4a19-be1a-0dcc443e2f7a-image.png



  • @uxm As you have drawn this, you need no extra VLANS. Two External v-switches (WAN, LAN) created in Hyper-V and assigned to 2 of your physical NICs. WAN, LAN interfaces on pfSense assigned to the corresponding v-switch. The WAN v-switch NIC wired to your router's LAN interface and the LAN v-switch NIC hooked to your switch. Run through the web setup on pfSense and BANG! Internet! Add an AP off your switch for your phones and laptop, use the Asus's wireless as a guest net.



  • Thank you very much! Im starting right away! Thanks @provels !


Log in to reply