Install mkinitcpio-nfs-utils
# Add net hook to mkinitcpio.conf
sed -e '/HOOKS=/a HOOKS+=(net)' -i /etc/zfsbootmenu/mkinitcpio.conf
# In config.yaml change Kernel.CommandLine, e.g.
# CommandLine: "ro quiet loglevel=0 ip=:::::eth0:dhcp"
Install dropbear
# Create custom key
dropbearkey -t ed25519 -f "/etc/dropbear/dropbear_ed25519_host_key"
# Add pub keys to /etc/dropbear/root_key
Install mkinitcpio-dropbear
# Adjust /usr/lib/initcpio/install/dropbear
# https://github.com/grazzolini/mkinitcpio-dropbear/pull/10/files
# Also maybe adjust port in /usr/lib/initcpio/hooks/dropbear
# Add dropbear hook to mkinitcpio.conf
sed -e '/HOOKS=/a HOOKS+=(dropbear)' -i /etc/zfsbootmenu/mkinitcpio.conf
generate-zbm
When done ZBM does not activate nor configure eth0. Can Ctrl+R into ZBM rescue shell then manually:
ip link set eth0 up
ip a a 1.1.1.2/24 dev eth0
ip route add default via 1.1.1.1
And also manually:
dropbear -E -s -j -k
Connections are then open, cannot connect with:
ssh root@1.1.1.2
Need to instead:
ssh root@1.1.1.2 "/bin/bash -i"
# And apparently also
export TERM=linux
But ZBM then doesn't find kernels to boot
Findings:
```
Install mkinitcpio-nfs-utils
# Add net hook to mkinitcpio.conf
sed -e '/HOOKS=/a HOOKS+=(net)' -i /etc/zfsbootmenu/mkinitcpio.conf
# In config.yaml change Kernel.CommandLine, e.g.
# CommandLine: "ro quiet loglevel=0 ip=:::::eth0:dhcp"
Install dropbear
# Create custom key
dropbearkey -t ed25519 -f "/etc/dropbear/dropbear_ed25519_host_key"
# Add pub keys to /etc/dropbear/root_key
Install mkinitcpio-dropbear
# Adjust /usr/lib/initcpio/install/dropbear
# https://github.com/grazzolini/mkinitcpio-dropbear/pull/10/files
# Also maybe adjust port in /usr/lib/initcpio/hooks/dropbear
# Add dropbear hook to mkinitcpio.conf
sed -e '/HOOKS=/a HOOKS+=(dropbear)' -i /etc/zfsbootmenu/mkinitcpio.conf
generate-zbm
```
When done ZBM does not activate nor configure `eth0`. Can `Ctrl+R` into ZBM rescue shell then manually:
```
ip link set eth0 up
ip a a 1.1.1.2/24 dev eth0
ip route add default via 1.1.1.1
```
And also manually:
```
dropbear -E -s -j -k
```
Connections are then open, cannot connect with:
```
ssh root@1.1.1.2
```
Need to instead:
```
ssh root@1.1.1.2 "/bin/bash -i"
# And apparently also
export TERM=linux
```
But ZBM then doesn't find kernels to boot
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Findings:
When done ZBM does not activate nor configure
eth0. CanCtrl+Rinto ZBM rescue shell then manually:And also manually:
Connections are then open, cannot connect with:
Need to instead:
But ZBM then doesn't find kernels to boot
ServerAliveCountMaxandServerAliveInterval/usr/sbin/dropbear -E -s -j -k -K 1 -p <n>ssh -o ServerAliveInterval=3 -o ServerAliveCountMax=0 <addr> -p <port>dropbearkey -t dss -f "/etc/dropbear/dropbear_dss_host_key"zfsbootmenufromHOOKSTest if
command='zfsbootmenu',no-agent-forwardingworkszfsbootmenuhook must be last or not present at allSyslinux shouldn't have a
CommandLine, try UEFI first for IP address