Network
One Ethernet port, and one USB port that can become a second one.
Ethernet
10/100 Mbit, Auto-MDIX, up to 100 m on CAT5. This is the normal path: the controller and the devices it talks to sit on the same installation network.
USB
There is exactly one USB 2.0 type A port, and it is the reason the controller does not need variants. WiFi, a second isolated network, another field bus, or a firmware stick — all of it arrives through that port, and the drivers ship with the firmware, so there is nothing to enable in the web interface first.
The constraints are physical and worth knowing before you buy adapters:
| Controller | EHCI · 480 Mbit/s |
| Root hub | maxchild = 1 — one adapter at a time |
| Budget | 500 mA |
| Hubs | Not supported |
So WiFi, a second LAN and a firmware stick are mutually exclusive. Which one the site needs is a decision, not a configuration.
The supported adapter families are listed on USB adapters.
Addressing: what the controller comes up as on first boot (DHCP or a fixed address), how to find it on the network, and what to do when the board network has no DHCP server. Needs confirmation from firmware.