I’ll follow my own advice and try the unofficial support forum (in addition to my post on the official support one)
I have 8 new Vexnet keys that don’t show Present on the Vexnet Mac utility.
Most older keys do, some dont; non-working ones don’t.
I tried using the win7 cmd: getmac
and it shows a macid of c8 3a 35 ce a3 d0 for one of the new keys
whereas the old keys have 00:B0:8C : xx : yy : zz (some variations)
Anyone else have similar results, or a workaround?
otherwise I’ll use macid and a script to reformat the data to be like the utility.
I don’t have any new keys so hard to help, however, c8 3a 35 ce a3 d0 is a legit MAC id and belongs to products from Tenda, it’s probably correct. Interestingly the MAC for the old keys did not show in the database I was searching.
Thanks, whats the database you checked?
I might be able to impress someone in my day job with data like that,
since we need to buy and install MACids on some products.
As of 9am, Sept 19, 2011, the wiki link doesn’t install correctly, but a link PM’ed to me does.
For teams with only a few VEXnet keys to get whitelisted, it may be more expedient to just use the built-in windows command “getmac” and cut and paste the values by hand.
For a large number of VEXnet keys, the VEXnet MACid utility is handy to build a nice clean text list.
Its interesting that the early key prefixes are not listed with a mfg registry.
Thanks for posting the links to IEEE and other lookup places.
Now I understand more of the background.
I can only assume that Tenda registered as a privately held OUI which you can still do, it just costs more money. The keys are Tenda W541U devices, if you look in the user manual they show a similar MAC address to the older VEXnet keys. I’m assuming the VEXnet mac utility checks all installed network interfaces and just checks for known OUI’s. It’s a simple application to write if anyone wants more functionality.