micronet daemon + Ethernet EEE/TSO tweaks for Pi 5 hub - #3
Merged
Conversation
Replace configure-ethernet and configure-dhcp with one JSON-configured daemon that probes foreign DHCP, pings gateway.ip, and applies client, gateway, or static .252 modes with dnsmasq only when needed. Co-authored-by: Cursor <cursoragent@cursor.com>
- Drop port=0 from dnsmasq.conf so the DNS listener stays on; we hand out option:dns-server = gateway.ip and ARCHITECTURE describes DHCP+DNS. - Poll the interface every ~3s in client mode and update the status snapshot when dhclient finally acquires a lease, so micronet check liveness sees a non-empty cidr instead of looping restarts. Co-authored-by: Cursor <cursoragent@cursor.com>
Fail closed on probe errors and validate DHCPOFFER xid/chaddr/opcode. Own dnsmasq and dhclient via pidfiles, start dhclient -nw, and periodically re-probe in gateway mode so a later foreign DHCP server makes us yield. Live liveness, real CIDR, teardown CLI, and legacy configure-* check fallback. Co-authored-by: Cursor <cursoragent@cursor.com>
BigFred OS now seeds micronet.json with 192.168.0.1/24 instead of 10.0.10.0/24. Co-authored-by: Cursor <cursoragent@cursor.com>
Best-effort ethtool after ip link set up complements dtparam=eee=off on Pi 5 hubs where the BCM54213PE PHY flaps under AutogrEEEn / IEEE 802.3az LPI. Failures (missing ethtool, ENOTSUP) are logged and do not fail apply. Co-authored-by: Cursor <cursoragent@cursor.com>
Resolve conflicts with merged micronet daemon on main: retain 192.168.0.0/24 seed addresses and post-bring-up ethtool EEE/TSO/GSO off for Pi 5 PHY stability. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
gateway/static/client) with unified bring-up, DHCP probe hardening, and dnsmasq integration.ip link set up, best-effort ethtool disables EEE and TSO/GSO on the wired interface — a belt-and-suspenders complement todtparam=eee=offon the hub image.Why (symptoms)
On the BigFred hub (Raspberry Pi 5), Ethernet was dropping periodically — the link went down and came back, sometimes several times per hour. This looked like a network or DHCP problem but was not:
BCM54213PEbehind the RP1 macb driver) is known to flap when AutogrEEEn / IEEE 802.3az LPI (“energy-efficient Ethernet sleep”) negotiates with many switches.performance; isolcpus is unrelated.micronet brings the interface up on boot; turning EEE off in software right after link-up avoids relying only on device-tree timing if the PHY re-negotiates after a flap.
Test plan
make fmt test clippyin micronetethtool --show-eee eth0→ EEE disabled/inactive after micronet applymicronet statusstablegatewayon empty LAN; no repeated Link Down/Up indmesgMade with Cursor