For me, it was openwrt bouncing the external interface during a DHCP renewal, even when the IP didn’t change. They still haven’t fixed that. I patch the stupid file every upgrade.
But yeah, at least I could fix it!
Comment on handy
undefined@lemmy.hogru.ch 15 hours ago
I feel like — like myself — no one on Lemmy would actually like this. For me, my router is a mini PC running Alpine Linux and it’s likely the modem (which I own) is having problems with the physical cable connection but if I were using an all-in-one shit box from the ISP there would be no way of knowing.
All this to say, if restarting the router “fixes” things there’s likely a deeper, more unsettling problem happening that’s not being diagnosed.
For me, it was openwrt bouncing the external interface during a DHCP renewal, even when the IP didn’t change. They still haven’t fixed that. I patch the stupid file every upgrade.
But yeah, at least I could fix it!
But yeah, at least I could fix it!
Isn’t openwrt open-source? If you fixed it on your machine, couldn’t you submit a PR to their codebase?
I've actually got the exact same issue - how did you end up fixing it?
This is the file:
/etc/hotplug.d/iface/20-firewall
In there, there’s a line that says
[ “$ACTION” = ifupdate -a -z “$IFUPDATE_ADDRESSES” -a -z “$IFUPDATE_DATA” ] && exit 0
change it to
[ “$ACTION” = ifupdate -a -z “$IFUPDATE_ADDRESSES” ] && exit 0
I pieced it together from this post, if it’s still around: github.com/openwrt/openwrt/issues/10338
Vogons@fedinsfw.app 6 hours ago
Came here to say just this. ISP box goes into a Debian board with 10 gigE uplink to my actual switching. I asked if I could replace the XGPON-ONT by SFP+s but Alas the sales agent was rather confused and basically said “why?!”…