Single Nic install guide?



  • Any one know where a good tutorial is on a single nic setup? Just setting up a test network with our old switch at home and the pc i'm using only has a single nic connection  :(



  • Here's my 1st try - no luck so far..

    Switch port 2 set to vlan 2
    Switch port 3 set to vlan 3
    Switch port 4 set to trunk

    Pfsense
    em0 interface set to uassigned
    vlan 2 set as lan parent interface em0
    vlan 3 set as wan parent interface em0

    Do I have to define em0 as a trunk? If so how?


  • LAYER 8 Netgate

    No.  A VLAN trunk port is essentially synonymous to a VLAN tagged port.  When you assign an interface to a pfSense VLAN interface, traffic for that interface will be tagged.

    Not sure what kind of switch you're using but you might need to specify the VLANs on the trunk port.

    Switch port 2 would go to your LAN.
    Switch port 3 would go to your DSL/Cable modem/WAN (preferably in bridge mode)
    Switch port 4 would go to pfSense


  • LAYER 8 Global Moderator

    So quick question does this PC not have any slots at all to add a nic?  You can pick up a cheap nic for under $10 at any computer store, online, etc.  Even a somewhat decent nic, even dual port for 40$

    http://www.amazon.com/Intel-PWLA8492MT-PCI-X-Server-Adapter/dp/B00006HX1V

    While sure you can do it with vlans, if your not clear on the setup why not just pick up another nic.  Get that working - then if you want to play with hairpin vlan configurations



  • @johnpoz:

    So quick question does this PC not have any slots at all to add a nic?  You can pick up a cheap nic for under $10 at any computer store, online, etc.  Even a somewhat decent nic, even dual port for 40$

    http://www.amazon.com/Intel-PWLA8492MT-PCI-X-Server-Adapter/dp/B00006HX1V

    While sure you can do it with vlans, if your not clear on the setup why not just pick up another nic.  Get that working - then if you want to play with hairpin vlan configurations

    Not really trying to drop anything in it its just and old pc im using just to mock up what my new network layouts going to be before I implement it. - Still learning so I dont wanna on the fly with my offices network.


  • LAYER 8 Global Moderator

    So your new network is going to use hairpinned vlans?  I one nic?  That seems unlikely, I sure wouldn't suggest it ;)

    Get a nic, the amount of time you have spent looking for how to do a hairpinned vlan setup prob more than the $10, Forgo the morning coffee from starbucks to fund it ;)

    You haven't even told us what switch your trying to use..



  • @johnpoz:

    So your new network is going to use hairpinned vlans?  I one nic?  That seems unlikely, I sure wouldn't suggest it ;)

    Get a nic, the amount of time you have spent looking for how to do a hairpinned vlan setup prob more than the $10, Forgo the morning coffee from starbucks to fund it ;)

    You haven't even told us what switch your trying to use..

    No definitely not!! I have a true server dell pe1750 with 2 nic's at the office running pfsense.

    Just trying to mock some stuff up to pre-plan everything I thought I saw somewhere this single nic was possible so I figured I give it a go.

    Test Setup at home

    Old crap dell pc running pfsense single nic
    powerconnect 3448 switch

    Anywayz since its such a hassle ill spend the 10 bucks to add a second lan..

    http://www.amazon.com/TP-LINK-TG-3269-1000Mbps-Gigabit-Network/dp/B0034CSUZ8/ref=sr_1_1?s=electronics&ie=UTF8&qid=1417641774&sr=1-1&keywords=Lan+card


  • LAYER 8 Global Moderator

    Well looking at the manual for 3448, looks like page 299 goes over the vlan.. Via the gui you can do everything you need.

    So the port on the switch that goes to em0 on pfsense would need to be Tagged for your vlans.  Trunk port vs access port - but looks like from the gui you can just pick your vlan, and then set ports to be untagged or tagged in that vlan.

    So the ports that go to you lan would be untagged in your lan vlan, say vlan 20 for the number.  Port that goes to your wan, ie modem would be untagged say in vlan 30.  Now the port that connects pfsense would be trunked, or tagged with both vlan 20 and 30.

    Then in pfsense you set your wan to vlan 30 and your lan to vlan 20.

    Hope that helps - but in the long run, it is easier to just use a physical nic ;)


  • Netgate Administrator

    Mocking stuff up and testing in a safe environment when you're not doing it against the clock is how you learn about this stuff. I wouldn't run a 'router on a stick' config unless I was forced to either but I'd certainly like to think I could do it if pressed. If you're not familiar with VLANs this is your opportunity.  :D

    Steve


  • LAYER 8 Global Moderator

    Agreed, which is why I suggest after he gets the 2nd nic he can play with the vlan stuff.  You get pfsense up and running, then you know that works and can actually play with it.  Then you can play with putting vlans on your lan side, or running the hairpin setup, etc.



  • @pollardhimself:

    Any one know where a good tutorial is on a single nic setup? Just setting up a test network with our old switch at home and the pc i'm using only has a single nic connection  :(

    I don't have a tutorial , but it can be done. When you first setup pf you are presented with the option to create VLANs. Lets say you make VLAN 99 the WAN and VLAN 11 is LAN off of interface EM0. On your switch you need to remember ingress is what you assign to the PVID and egress is what you either tag or untag depending on what the port is connected to. So, the port used for WAN would be PVID 99, Untagged. The port used for LAN would be PVID 11, untagged. The port used for the trunk connected to pfSense would be PVID 11 -  then tag it VLAN 99 AND tag it for VLAN 11.



  • @pollardhimself:

    Any one know where a good tutorial is on a single nic setup? Just setting up a test network with our old switch at home and the pc i'm using only has a single nic connection  :(

    Read the following thread. The OP in that case was myself  ;). Anyway, you will find the answer embedded among the replies in middle to last portion of the entire thread.

    https://forum.pfsense.org/index.php?topic=28379.0



  • I've been running pfsense with a single NIC, using VLAN's, for several years.. Works great…. Just have to have a switch that supports VLAN's as well...


  • LAYER 8 Global Moderator

    "Works great."

    What would depend on what your looking to accomplish and what kind of performance you want out of it.. If you want to save couple of bucks on a nic and get lower performance then sure works great ;)  Hairpinning any sort of connection would never be my first choice to be sure.


Log in to reply