Netgate Device ID (NDI)

GTAXL

Hello I have a few questions about NDI and how it works. I've noticed my NDI has changed after I changed my WAN port assignment on a 1541 from ix0 to igb0. I had to do this after discovering the ix NIC's don't support negotiation at 100Mbps, only 1Gbps/10Gbps and wouldn't get a link to my modem.

How is NDI generated? I've heard it's a special hash against the MAC addresses on the system.
Where is NDI stored? Or is it generated at each console display load and web ui load?
Is it tied to port assignments? it appears so, change what port uses wan and I noticed a new NDI..
What is NDI used for? Does it verify a system is eligible for pfSense Plus? If this changes from what is on the sticker on the unit, is that a real problem? I've added in a 4-port SFP+ card and my NDI didn't appear to change when I did that. So I'm curious what MAC addresses the hash is against and if it's based on what NICs are assigned to what.

rcoleman-netgate

@gtaxl said in Netgate Device ID (NDI):

How is NDI generated? I've heard it's a special hash against the MAC addresses on the system.

It is. The NDI should not change by changing assignments... but if you added a USB NIC or a PCIe NIC that will cause it to change.

GTAXL

@rcoleman-netgate Right, it does appear it changed from when I added the PCIe NIC. This is something to be expected for this unit, as it has an expansion slot. My other questions remain un-answered.

What is NDI used for?
The unit already has pfSense Plus on it, when I go to do an update, will it still work? Is the NDI changing any problem?

rcoleman-netgate

@gtaxl said in Netgate Device ID (NDI):

What is NDI used for?
The unit already has pfSense Plus on it, when I go to do an update, will it still work? Is the NDI changing any problem?

The NDI is used to track support tickets, TAC contracts, etc.

On Netgate branded hardware the serial number is used as a fall-back to verify software eligibility... when you open a ticket in the future for software images please use your serial number.

If you have a TAC support subscription you will want to get the subscription attached the new NDI as soon as possible - you will want to open a ticket at the URL in my signature to proceed. But if you aren't using TAC Professional or TAC Enterprise right now I would not worry about it -- just make sure you add your serial number to any future tickets.

GTAXL

@rcoleman-netgate Thanks!

artenpie

@rcoleman-netgate I'd ask that the devs consider removing USB-based ethernet ports from the things that determine the NDI.

In my case, I have a Pi Zero set up as an "ethernet gadget" to run PiHole without using up an ethernet port, and I noticed the NDI changed when I attached it and rebooted. Since the Pi isn't necessarily permanent, I expect the NDI will change again when I remove it.

I guess I can run the CE version (where the NDI doesn't matter), but I'd rather not have to.

Thanks!

rcoleman-netgate

@artenpie said in Netgate Device ID (NDI):

I'd ask that the devs consider removing USB-based ethernet ports from the things that determine the NDI.

Feature requests should be added to https://redmine.pfsense.org/

mfld

@rcoleman-netgate said in Netgate Device ID (NDI):

@artenpie said in Netgate Device ID (NDI):

I'd ask that the devs consider removing USB-based ethernet ports from the things that determine the NDI.

Feature requests should be added to https://redmine.netgate.com/

Public facing side is https://redmine.pfsense.org/ , not https://redmine.netgate.com

rcoleman-netgate

@mfld You're right. I must have been pretty exhausted two weeks ago - I never make that error!

mfld

@rcoleman-netgate

I'd be exhausted, too. PHP 7.x -> PHP 8.x for an ancient PHP app is not a small job. And then FreeBSD 12.x -> FreeBSD 14 in the same swoop, with in-place upgrades where the install base is made up of eclectic hardware.

It's a miracle most of my 2.7.0-dev and 23.01 Rel upgrades worked. For those that did not.... Enjoy Q2 2023 #nosleep