mirror of
https://github.com/spr-networks/super.git
synced 2026-04-24 20:35:55 +03:00
[GH-ISSUE #422] clearfog missing dhcpcd #214
Labels
No labels
blocked
bug
documentation
enhancement
fixed
fixed ✅
hardening
implemented
installer
multicast
p1
p2
pending
podman
pull-request
security
testing
v1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/super#214
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lts-rad on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/spr-networks/super/issues/422
[ 23.168213] rc.local[441]: /home/spr/setup.sh: line 8: dhcpcd: command not found
@lts-rad commented on GitHub (Jun 3, 2025):
[ 23.168213] rc.local[441]: /home/spr/setup.sh: line 8: dhcpcd: command not found
@Dave247 commented on GitHub (Jun 3, 2025):
I discovered this when flashing the image on the C9130 Pro from the SD card. The version used was 1.0.13
@lts-rad commented on GitHub (Jun 3, 2025):
[ 509.812761] rc.local[1022]: rm: cannot remove '/containers': Is a directory
@Dave247 commented on GitHub (Jun 4, 2025):
I've gone through the past releases to track down where the issue of lan@eth1 not appearing started happening so to get a last known good working configuration which I hope is of use to tracking down the cause.
Also worth noting, 0.3.13 contains both above mentioned errors, while 0.3.9 only contains the second.
0.3.13 is the most recent version where it appeared to stop working.
0.3.13 boot log
0.3.12, 0.3.11 & 0.3.10 are all broken and do not boot properly.
0.1.11 boot log
0.3.9 is the most recent version where it was still working.
0.3.9 boot log
@Dave247 commented on GitHub (Jul 11, 2025):
Have tried again using the recent 1.0.14 Seems to have gotten worse though as no connection to eth1 is recognized at all.
There is a change to rc.local though
Here's the mentioned systemctl status output.
And here's the full console boot log
1.0.14 boot log
@lts-rad commented on GitHub (Jul 11, 2025):
i will look, we are having a problem with GHA where the builds are timing out, so it sounds related to that
@Dave247 commented on GitHub (Jul 23, 2025):
The 1.0.17 release is a big improvement, lots of activity that I haven't otherwise observed before with Docker pulling multiple things.
Still no bridged LAN though appearing when checking the list of devices and interfaces. But what is there is doing stuff.
Because the boot log is a lot longer this time around I've included it as a separate file.
putty.log
@lts-rad commented on GitHub (Jul 23, 2025):
are you able to log in over 192.168.1.243?
@Dave247 commented on GitHub (Jul 24, 2025):
Yeah I was able to log in just fine, but that's as far as I have gotten, I'm yet to try doing anything and see what breaks as I just haven't had the time/focus.
@Dave247 commented on GitHub (Aug 21, 2025):
Apologies it's taken so long. As expected LAN/downlink connections aren't recognized at all in any port. WiFi does appear to work however. Not being able to separate the two AP points with different names does concern me though, as I don't trust for it to connect to the 5Ghz when over the 2.4 which it appeared to prefer for some reason but that's a separate thing.
@lts-rad commented on GitHub (Aug 21, 2025):
need to get back to this for the dtb changes that may have broken lan. It is possible to separate the 2 names, have you been able to toggle the interface ?
under wifi -> radio settings you can set the name there
@Dave247 commented on GitHub (Aug 21, 2025):
Ah I missed the option. Yes I can change and the SSID field is there but my list appears to be in alphabetical order which puts the SSID field at the mid-bottom.
On the topic of the UI I would like to see that the channel selection menus/checkboxes only show applicable options for the currently selected interface as there's no reason to have it selectable otherwise a it just adds confusion. Unlike in the previous builds I tried though changing these options do appear to work as previously there was error messages, though I now wonder if perhaps those were in part because I had mistakenly had the wrong AP point selected.