Are you guys ready for a story? This one is actually not so bad. A couple days ago I post on Facebook if anyone happened to have a spare PCI\/PCIe Network Interface Card (NIC), since it was going to be used for interest access I was ok with it being 100, but was aiming for 1000 (now that Shaw provide over 300mbps internet, clearly 100 doesn’t cut it).<\/p>\n
After a day of no luck, and a bunch of funny remarks (as almost none of my friends had any idea of what I was talking about), I decided to take another look through my old computer hardware to see what I could scrounge up…<\/p>\n
<\/span>PCI NIC Found!<\/span><\/h2>\n![\"\"](\"https:\/\/i.imgur.com\/FfQ6RQT.jpg\")
<\/a>well, well, not even dusty, a PCI NIC, exactly what I needed in my hypervisor to play with OPNsense. I originally was going to try layer 2 trunking via VLANs, however the main vSwitch already had VMkernel Nics bound to the physical adapter @ layer 3, and the same interface on my firewall (Palo Alto) wouldn’t allow me to create a layer 2 sub-interface is the main interface was already bound to layer 3. Since I wanted my OPNsense VM to get an actual public IP address, this required my device to get a connection from my VM, directly to my modem at layer 2… yeah another NIC. So here we are, and it didn’t take long for me to shut down my VMs and install the card, and boot my hypervisor back up (I hope to one day have multiple hypervisor to not have to shut down my VMs, but even then, if you don’t pay chances are you won’t get access to the APIs that migrate the memory states of the VMs for you, so it’s a hassle either way…. anyway back to the story.<\/p>\n<\/span>PCI NIC Found … NOT<\/span><\/h2>\nOh Borat, who brought you in?!?! So as you may have guessed I went to add a new vSwitch for my new VM to get it’s direct Public IP, and to my dismay there was no physical NIC to pick… what the….<\/p>\n
So to Google! and hopefully either VMware support<\/a>, or usually always better personal blogs! We all loves these right… ahem… anyway…<\/p>\nYou can probably guess where the official answer went, but I’ll enlighten you as I did follow along for … pain? OK I don’t know why I did, I was really hopeful it wasn’t going to be the answer I knew it was going to be….<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/jb11ROS.png\")
<\/a><\/p>\nHey! some of the command they provided helped, or did they? All this was, was some BS data chasing to tell you, IT’s Not supported, SOWWY!<\/p>\n
Clearly, there must be some answers by the community forums right??<\/p>\n
<\/span>Community’s great! VMwares…. :S<\/span><\/h2>\nSo what do we get… One<\/a>… unanswered and crying about a badly referenced link to source two.<\/a>.. also unanswered crying about the same stuff we already know…. it’s officially not supported. Well I’m running ESXi 5.5 Free and using GhettoVCB’s scripts, also unsupported, so not really an issue… the issue is teh lack of help right now.<\/p>\nBut bring me down, I don’t thikn so, the internet has many sites, and many people sharing their knowledge, how?!?! BLOGS! Ahem…<\/p>\n
<\/span>Blogs to the Rescue!<\/span><\/h2>\nYes believe it or not it is the power of the real untethered, unfiltered beauty that is blogging that we actually get some meat and potatoes. My first source<\/a> showed signs of light! One problem, it’s literally 9 years old and using ESXi 4. OK well it also wanted a fair amount of direct file placing and special manipulation. Most of this works fairly differently in ESXi 5.x, and vibs or precompiled binaries that work with esxcli are the more preferred method. I avoid saying supported here, cause I use these methods to install unsupported packages :D.<\/p>\nAlright, so now what, well the Holy Grail<\/a>! This King managed to not only blog about getting this working but shared the drivers\/vibs packages required to get it to work too! Epic! Let’s get this dang NIC working…<\/p>\n1) Grab the VIB files<\/a><\/p>\n2) Change your support level on ESXi5+:<\/p>\n
~ # esxcli software acceptance set \u2013level=CommunitySupported<\/strong>
\nHost acceptance level changed to \u2018CommunitySupported\u2019.<\/p>\n3) Install the driver with: \u201cesxcli software vib install -v \/DLink-528T-1.x86_64.vib\u201c<\/p>\n
4) Reboot<\/p>\n
Sounds simple enough lets give it a shot… and I hit some errors, classic…<\/p>\n
I won’t show the erros just yet as I have it one long snippet, but basically I had a bit of problems cause of the GhettoVCB scripts I had pushed on to my host, but the error results weren’t exactly clear… I attempted a couple things first, like copying the VIB to the path it kept complaining about and specifying the fully qualified path to the VIB.. nothing till I stumbled across this..<\/a>.<\/p>\nesxcli software vib install -v \/full\/path\/to\/.vib -f<\/pre>\nwhich finally gave me a driver install successful!<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/bWd5Pov.png\")
<\/a><\/p>\nAlright, and after reboot…..<\/p>\n
\n![\"\"](\"https:\/\/i.imgur.com\/tLLpwIP.png\")
<\/a><\/p>\nOMG! No way, there it is with the proper name and everything. Considering the blog post I followed was for a different NIC model I wasn’t sure if it would work, but there it is… so lets not get to ahead of ourselfs and see if it comes up and is able to transmit packets…<\/p>\n
I was having some issues initially so I decided to give my lil netbook a simple \/24 IP and give my OPNsense a simple \/24 IP just to validate the card wasn’t the issue, or the drivers I just installed.<\/p>\n
Plug them together, lights come up, that’s good… checking ESXI vSphere…<\/p>\n
<\/a>well, well, not even dusty, a PCI NIC, exactly what I needed in my hypervisor to play with OPNsense. I originally was going to try layer 2 trunking via VLANs, however the main vSwitch already had VMkernel Nics bound to the physical adapter @ layer 3, and the same interface on my firewall (Palo Alto) wouldn’t allow me to create a layer 2 sub-interface is the main interface was already bound to layer 3. Since I wanted my OPNsense VM to get an actual public IP address, this required my device to get a connection from my VM, directly to my modem at layer 2… yeah another NIC. So here we are, and it didn’t take long for me to shut down my VMs and install the card, and boot my hypervisor back up (I hope to one day have multiple hypervisor to not have to shut down my VMs, but even then, if you don’t pay chances are you won’t get access to the APIs that migrate the memory states of the VMs for you, so it’s a hassle either way…. anyway back to the story.<\/p>\n<\/span>PCI NIC Found … NOT<\/span><\/h2>\nOh Borat, who brought you in?!?! So as you may have guessed I went to add a new vSwitch for my new VM to get it’s direct Public IP, and to my dismay there was no physical NIC to pick… what the….<\/p>\n
So to Google! and hopefully either VMware support<\/a>, or usually always better personal blogs! We all loves these right… ahem… anyway…<\/p>\nYou can probably guess where the official answer went, but I’ll enlighten you as I did follow along for … pain? OK I don’t know why I did, I was really hopeful it wasn’t going to be the answer I knew it was going to be….<\/p>\n
<\/a><\/p>\nHey! some of the command they provided helped, or did they? All this was, was some BS data chasing to tell you, IT’s Not supported, SOWWY!<\/p>\n
Clearly, there must be some answers by the community forums right??<\/p>\n
<\/span>Community’s great! VMwares…. :S<\/span><\/h2>\nSo what do we get… One<\/a>… unanswered and crying about a badly referenced link to source two.<\/a>.. also unanswered crying about the same stuff we already know…. it’s officially not supported. Well I’m running ESXi 5.5 Free and using GhettoVCB’s scripts, also unsupported, so not really an issue… the issue is teh lack of help right now.<\/p>\nBut bring me down, I don’t thikn so, the internet has many sites, and many people sharing their knowledge, how?!?! BLOGS! Ahem…<\/p>\n
<\/span>Blogs to the Rescue!<\/span><\/h2>\nYes believe it or not it is the power of the real untethered, unfiltered beauty that is blogging that we actually get some meat and potatoes. My first source<\/a> showed signs of light! One problem, it’s literally 9 years old and using ESXi 4. OK well it also wanted a fair amount of direct file placing and special manipulation. Most of this works fairly differently in ESXi 5.x, and vibs or precompiled binaries that work with esxcli are the more preferred method. I avoid saying supported here, cause I use these methods to install unsupported packages :D.<\/p>\nAlright, so now what, well the Holy Grail<\/a>! This King managed to not only blog about getting this working but shared the drivers\/vibs packages required to get it to work too! Epic! Let’s get this dang NIC working…<\/p>\n1) Grab the VIB files<\/a><\/p>\n2) Change your support level on ESXi5+:<\/p>\n
~ # esxcli software acceptance set \u2013level=CommunitySupported<\/strong>
\nHost acceptance level changed to \u2018CommunitySupported\u2019.<\/p>\n3) Install the driver with: \u201cesxcli software vib install -v \/DLink-528T-1.x86_64.vib\u201c<\/p>\n
4) Reboot<\/p>\n
Sounds simple enough lets give it a shot… and I hit some errors, classic…<\/p>\n
I won’t show the erros just yet as I have it one long snippet, but basically I had a bit of problems cause of the GhettoVCB scripts I had pushed on to my host, but the error results weren’t exactly clear… I attempted a couple things first, like copying the VIB to the path it kept complaining about and specifying the fully qualified path to the VIB.. nothing till I stumbled across this..<\/a>.<\/p>\nesxcli software vib install -v \/full\/path\/to\/.vib -f<\/pre>\nwhich finally gave me a driver install successful!<\/p>\n
<\/a><\/p>\nAlright, and after reboot…..<\/p>\n
\n<\/a><\/p>\nOMG! No way, there it is with the proper name and everything. Considering the blog post I followed was for a different NIC model I wasn’t sure if it would work, but there it is… so lets not get to ahead of ourselfs and see if it comes up and is able to transmit packets…<\/p>\n
I was having some issues initially so I decided to give my lil netbook a simple \/24 IP and give my OPNsense a simple \/24 IP just to validate the card wasn’t the issue, or the drivers I just installed.<\/p>\n
Plug them together, lights come up, that’s good… checking ESXI vSphere…<\/p>\n
You can probably guess where the official answer went, but I’ll enlighten you as I did follow along for … pain? OK I don’t know why I did, I was really hopeful it wasn’t going to be the answer I knew it was going to be….<\/p>\n
Hey! some of the command they provided helped, or did they? All this was, was some BS data chasing to tell you, IT’s Not supported, SOWWY!<\/p>\n Clearly, there must be some answers by the community forums right??<\/p>\n So what do we get… One<\/a>… unanswered and crying about a badly referenced link to source two.<\/a>.. also unanswered crying about the same stuff we already know…. it’s officially not supported. Well I’m running ESXi 5.5 Free and using GhettoVCB’s scripts, also unsupported, so not really an issue… the issue is teh lack of help right now.<\/p>\n But bring me down, I don’t thikn so, the internet has many sites, and many people sharing their knowledge, how?!?! BLOGS! Ahem…<\/p>\n Yes believe it or not it is the power of the real untethered, unfiltered beauty that is blogging that we actually get some meat and potatoes. My first source<\/a> showed signs of light! One problem, it’s literally 9 years old and using ESXi 4. OK well it also wanted a fair amount of direct file placing and special manipulation. Most of this works fairly differently in ESXi 5.x, and vibs or precompiled binaries that work with esxcli are the more preferred method. I avoid saying supported here, cause I use these methods to install unsupported packages :D.<\/p>\n Alright, so now what, well the Holy Grail<\/a>! This King managed to not only blog about getting this working but shared the drivers\/vibs packages required to get it to work too! Epic! Let’s get this dang NIC working…<\/p>\n 1) Grab the VIB files<\/a><\/p>\n 2) Change your support level on ESXi5+:<\/p>\n ~ # esxcli software acceptance set \u2013level=CommunitySupported<\/strong> 3) Install the driver with: \u201cesxcli software vib install -v \/DLink-528T-1.x86_64.vib\u201c<\/p>\n 4) Reboot<\/p>\n Sounds simple enough lets give it a shot… and I hit some errors, classic…<\/p>\n I won’t show the erros just yet as I have it one long snippet, but basically I had a bit of problems cause of the GhettoVCB scripts I had pushed on to my host, but the error results weren’t exactly clear… I attempted a couple things first, like copying the VIB to the path it kept complaining about and specifying the fully qualified path to the VIB.. nothing till I stumbled across this..<\/a>.<\/p>\n which finally gave me a driver install successful!<\/p>\n Alright, and after reboot…..<\/p>\n OMG! No way, there it is with the proper name and everything. Considering the blog post I followed was for a different NIC model I wasn’t sure if it would work, but there it is… so lets not get to ahead of ourselfs and see if it comes up and is able to transmit packets…<\/p>\n I was having some issues initially so I decided to give my lil netbook a simple \/24 IP and give my OPNsense a simple \/24 IP just to validate the card wasn’t the issue, or the drivers I just installed.<\/p>\n Plug them together, lights come up, that’s good… checking ESXI vSphere…<\/p>\n<\/a><\/p>\n<\/span>Community’s great! VMwares…. :S<\/span><\/h2>\n
<\/span>Blogs to the Rescue!<\/span><\/h2>\n
\nHost acceptance level changed to \u2018CommunitySupported\u2019.<\/p>\nesxcli software vib install -v \/full\/path\/to\/.vib -f<\/pre>\n
<\/a><\/p>\n
\n<\/a><\/p>\n