3 ms·
> This kindof reinforces how having an 'IoT Gateway' would be a good idea: The gateway can provide DHCP, and rough time, and (S)NTP, and DNS Aka a router. Am I
by josteink 8y ago
> This kindof reinforces how having an 'IoT Gateway' would be a good idea: The gateway can provide DHCP, and rough time, and (S)NTP, and DNS
Aka a router. Am I missing something?
- mschuster91 8y agoYes, as routers generally only speak Ethernet and WiFi while IoT devices speak Zigbee, BT/LE, Powerline, 433 MHz custom protocols, a bunch of low power WAN protocols and for the more professional/industry settings CANbus, Profibus and more.
- josteink 8y agoAFAIK Powerline is Ethernet, so that’s covered. Zigbee, BT/LE, 433Mhz and friends don’t do IP, so they won’t need DHCP and DNS. So again... What am I missing?
- deleted 8y ago[deleted]
- gumby 8y agoI doubt most routers provide DHCP. Maybe consumer ones.
- detaro 8y agoWhat's the point of this nitpick? Networks that configure everything statically are fairly rare, and do so intentionally. If they don't, they have a DHCP server somewhere already, and if they aren't consumer-level networks they sure as hell don't want some random "IoT gateway" box providing DHCP. So it's clear what "router" means in this context.
- gumby 8y agoI have a separate dhcp server so if the router has issues machines can still attach to the network and talk to local services.
- p1necone 8y agoIn my experience the majority (all the ones I've owned at least) of consumer grade routers have DHCP.
- psds2 8y agoMost layer 3 switches provide DHCP, and since almost all consumer routers also provide DHCP, probably most routers do provide DHCP.