One occasion I had SSH throw a Connection Reset by Peer on my when was the SD-card of a Raspberry Pi started failing and the ext4 filesystem got mounted in read-only mode.
Then sshd was still listening on port 22, but since it could not write to disk any more, it threw a Connection Reset by Peer to the client.
It was on OpenSuSE Tumbleweed, but would failed just as well using Raspbian.
wait 5 minutes (there is no output on HDMI apart from some flickering and no output on TTY using 115200 bits/second despite trying [WayBack] en:c1_hardware_uart [ODROID Wiki])
The second part is getting the USB web cameras to work.
I’ve got two types, but the label on them doesn’t list their common name, only their P/N sometimes with M/N:
P/N 860-000049 M/N V-UBC40 (really old USB cameras)
P/N 860-000334 (new USB camera)
The MotionEyeOS web interface didn’t list any working cameras so I had to do some digging.
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
Wicked changed its defaults to use this DHCPv6 compatible RFC4361 client-id in favour of the older RFC2132 client-id. However, this has caused some issues with older DHCPv4 servers and existing setups where the client-id stored by the server is used to assign a (static) address. It is recommended to fix this server-side, but still, wicked provides several ways of addressing this issue
2018-02-02 - mt@suse.de
- version 0.6.44
- dhcp4: use rfc4361 client-id as new default for ethernet on sle15
(fate#323576). It can be also enabled/disabled in wicked-config(5).
- client: fixed broken wicked arp utility command (bsc#1078245)
- cleanup: add mising/explicit designated field initializers
- pkgconfig: fix to request libnl3 instead of libnl1
- dbus: add missing DBUS_ERROR_FAILED type to a dbus_set_error call
and enforce formatting input as string when an extension did not
returned any error message.
- Removed patch included in the source archive
[- 0001-wickedd-explicitly-unbind-slaves-on-deletion.patch]
The traditionally used RFC 2132 DHCPv4 client-id on Ethernet is constructed from the hardware type (01 for Ethernet) and followed by the hardware address (the MAC address), for example:
01:52:54:00:02:c2:67
The RFC 4361 client-id starts with 0xff (instead of the hardware type), followed by the DHCPv6 IAID (the interface-address association ID that describes the interface on the machine), followed by the DHCPv6 DUID (client-idwhich identifies the machine).
Using the above hardware type-based and hardware address-based DUID (LLT type used by default), the new RFC 4361 DHCPv4 client-id would be:
Using the last bytes of the MAC address as the IAID: ff:00:02:c2:67:00:01:xx:xx:xx:xx:52:54:00:02:c2:67
When the IAID is a simple incremented number: ff:00:00:00:01:00:01:xx:xx:xx:xx:52:54:00:02:c2:67
There are plenty of HDMI displays, but if you want a smaller size it become more complicated although some 7″ HDMI displays are available. However, if you
The Wiert Corner - irregular stream of stuff 