![]() ![]() Also, I humbly plea to you not to design fixed firmware devices which are attached to the public internet unless you know exactly what you are getting into security wise ALL STM32 devices fall into this category IMO. Examples: MAC: 1ed5b182cd7e hostname: shinyiot-b182cd7e MAC: 1ed5f7198460 hostname: shinyiot-f7198460 MAC: 1ed544a1af98 hostname: shinyiot-44a1af98 I use murmur3_32 ( ) to generate a reasonably ( ) collision free 32-bit hash from the 96-bit device UID. Super useful if you need to support OTA firmware updates via a web/rest interface. Add the unique 32bit number as a hex value to your default hostname. And it makes firewall/filter configurations much easier. ![]() For instance they could configure a DHCP server to assign special IP address ranges for your product only. You'll make ITs work much easier that way if they plan to deploy a bunch of your devices. ![]() I use the other 16bits to mark off a unique product id and set LAA. The chances of collisions are really more theoretical. It's highly unlikely you'll run > 2^16 devices on the same subnet and/or fully routed out. A unique 32bit per device MAC address is generally plenty in my experience. A few rules I apply to my Ethernet projects, which are never exposed or routed to the public internet: 1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |