Network interface controller

And if you wanna send in your questions for Jim and Alan or your feedback, you can email show@two.fiveadmins.com. Matthew writes, "I'm using OPNsense on an old PC with an Intel Core i3 6100 and eight gigs of RAM to segment my home network into VLANs with a UniFi USG 3P as the internet gateway.

I'm thinking of adding a second NIC to the OPNsense box as a WAN interface, which I can connect directly to the internet, so it can handle all routing duties by itself.

Are there any advantages to doing everything in OPNsense and getting rid of the USG? I'm also worried that Ubiquiti might end support for the network app that I run on my Proxmox server to manage my USG."

With this one, I don't think there's many disadvantages.

And if you want to send any questions for Jim and Alan or your feedback, you can email show at 2.5admins.com. Matthew writes, I'm using OpenSense on an old PC with an Intel Core i3-6100 and 8GB of RAM to segment my home network into VLANs, with the UniFi USG3P as the internet gateway.

I'm thinking of adding a second NIC to the OpenSense box as a WAN interface, which I can connect directly to the internet, so it can handle all routing duties by itself.

Are there any advantages to doing everything in OpenSense and getting rid of the USG? I'm also worried that Ubiquiti might end support for the network app that I run on my Proxmox server to manage my USG.

With this one, I don't think there's many disadvantages.

Uh, and they wanted to do it in a rapid [laughs] way, as quickly as possible.

Uh, so they brought together some of the key NIC vendors, uh, to kind of collaborate together to come up with a m- minimal viable product to meet their primarily training workload needs.

So that's kind of the history.

Uh, it's been, you know, the announcement's been great.

That, that's all true.

The other point to make is that the, the, there, there's been a lot of work done on, uh, allowing the job to continue operation if things happen in the fabric that are, uh, inefficient.

So in particular, if a link goes down, if a node goes down, if a, uh, um, a, a, a link flaps, for example, uh, we, we've put a lot of effort into MRC to make sure that, uh, at a, at a node level, the NIC that's sending out these, these, these packets can detect these sorts of events, can s- can start to exclude those paths, and then can... has a, has a way of getting, getting this, this information back when the path comes up so that it can begin to include it.

The big thing that, that sort of we have been getting from our primary customers is that they no longer have to think about the reliability of the job at a minute-to-minute level, which was a big problem for them before, right? So, I mean, it's, it's a self-healing fabric, is, is the point.

Uh, and they wanted to do it in a rapid [laughs] way, as quickly as possible.

Uh, so they brought together some of the key NIC vendors, uh, to kind of collaborate together to come up with a m- minimal viable product to meet their primarily training workload needs.

So that's kind of the history.

Uh, it's been, you know, the announcement's been great.

That, that's all true.

The other point to make is that the, the, there, there's been a lot of work done on, uh, allowing the job to continue operation if things happen in the fabric that are, uh, inefficient.

So in particular, if a link goes down, if a node goes down, if a, uh, um, a, a, a link flaps, for example, uh, we, we've put a lot of effort into MRC to make sure that, uh, at a, at a node level, the NIC that's sending out these, these, these packets can detect these sorts of events, can s- can start to exclude those paths, and then can... has a, has a way of getting, getting this, this information back when the path comes up so that it can begin to include it.

Mm-hmm.