Vero V ignores DHCP option 121.
Looks like there was a feature request back in 2020 yet the issue is not resolved.
This is normal networking, Debian on a laptop works just fine. Wonder why Debian on the Vero does not.
“DHCP option 121 is a classless static route option that allows a DHCP server to send static routes to DHCP clients. The clients can then use these routes in their local routing tables.”
What’s your point?
I’ve been using it for years, no definition necessary.
The query was in regards to the Vero ignoring RFC 3442.
It isn’t implemented in ConnMan.
And there are good arguments to not implement it in future: https://thehackernews.com/2024/05/new-tunnelvision-attack-allows.html
That’s not a good argument against implementation. It’s no real argument at all. It states:
…by means of an attacker-configured DHCP server using the [classless static route option 121]…
An attcker configured anything on your network can be a problem. And an attacker configured DHCP server doesn’t need option 121 to wreak havoc.
I don’t know much about ConnMan. Is there some reason that it is desirable vs standard Linux networking (that all support RFC 3442, as does Windows, Mac, etc.)?
Yes. It is a lightweight connection manager and suited for embedded setups.
3 Likes