-
Notifications
You must be signed in to change notification settings - Fork 89
Open
Description
I installed to an SDcard that had been set up with the full Raspian for some work on an internal network. It was configured to use an internal proxy, ntp server, etc. I let the automatic install do it's thing and ran into the following glitches. They are all fixable with minor edits, so it's not clear whether they are really bugs to fix. (The hardware is a Pi 4B.)
- The proxy settings were not removed although the network was reconfigured by the installer. This caused various issues, in particular ISC-agent failed. Fixed with some find/grep/edit of some .ini files.
- The disabling of IPv6 was incomplete. You need to also set ipv6.method to "disabled" in the NetworkManager connections files. It was left "auto" which resulted in an attempt to start, a failure, and failure messages in the log files every minute. It was an easy edit fix.
- The NTP address for timedate wasn't changed and didn't work. Raspberry uses rpi-config to set this, and the install removed that program. Again, find/grep/edit found the file that needed to be fixed.
- The installer asked whether to monitor the wired ethernet or wifi. I chose wired. I was a little surprised that the resulting iptable completely disabled use of the wireless. This might be intentional. For cabling and access reasons I decided to enable it for a little while by editing iptables. When the Pi gets buried back on a shelf I'll disable it. All the rest of the wifi configuration (access point, password, etc.) survived the install. The installer could ask whether to enable or disable the unused interface or be clear that the unused interface will be disabled.
It's now working properly, so these might not be considered bugs.
I am wondering whether there will be lifespan and reliability issues given all the read/write traffic to the SDcard. I don't know whether it does load leveling, etc., to deal with all the log traffic.
Metadata
Metadata
Assignees
Labels
No labels