4 ms·
No IPv4 support? https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_ne...
by topbanana 8y ago
No IPv4 support?
https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_ne...
- eecc 8y agoWell? Why would you want it, it's legacy. IPv4 is over, let it rest.
- topbanana 8y agoBecause most home networks are IPv4 via NAT
- jschwartzi 8y agoNot to mention most business networks, the vast majority of industrial control networks. So basically damn near anywhere you would want to deploy a networked embedded system. Many systems have IPv6 support but you will still need to talk to IPv4 devices, and you need an IPv4 stack to do that.
- eecc 8y agoAh ok, so we'll never get over IPv4 if we still take potshots at anything that doesn't support it. Oh by the way, I'm sure we all agree that using IPv4 for IoT, especially new deployments, is a particularly bad idea.
- eecc 8y agoMost home networks are also a single collision domain where an IPv6 network can establish itself autonomously, without the kludges of a v4. People, just let it rest.
- howard941 8y agoShow stopper :( . I can't justify an OS more complex than a simple message queue-based scheduler if the target isn't internetted. And I get arguments about the scheduler ("You should use a commutator/superloop"). Don't wish to be a downer though, seems like a great academic project. EDIT Elaborated beyond two words and the slimey
- ungzd 8y agoProbably it's still possible to use ipv4 with this OS, but not with "gnrc" framework. - IPv4 is mentioned in docs: http://doc.riot-os.org/group__net__ipv4.html http://doc.riot-os.org/group__net__ipv4.html - lwip config has ipv4 enabled: https://github.com/RIOT-OS/RIOT/blob/3091cd85bd6df0bce1fcf603553d047b290e1ff2/pkg/lwip/Makefile https://github.com/RIOT-OS/RIOT/blob/3091cd85bd6df0bce1fcf60...