Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1015287: dropbear-initramfs: Configure dropbear to use VLAN
647 views
Skip to first unread message
Graham Cobb
Jul 18, 2022, 6:10:03 PM7/18/22
to
Package: dropbear-initramfs
Version: 2022.82-3
Severity: wishlist
I have recently started using dropbear-initramfs to try to help with situations
where boot problems need to be resolved remotely.
I have it working on one system but when I try to use it on a second system it doesn't work.
This second system is a server which is connected directly to a VLAN trunk, so the IP config
needs to specify a VLAN to use.
I tried using the kernel command line "ip=" to specify the interface name with a VLAN id
in the same format as used in /etc/network/interfaces:
ip=192.168.0.205::::name.a.b.c:eth0.100::192.168.0.1:
However, this did not work.
It would be great if I could use dropbear-initramfs on the host systems
which are directly connected to the VLAN trunk.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dropbear-initramfs depends on:
ii busybox 1:1.35.0-1
ii dropbear-bin 2022.82-3
ii initramfs-tools 0.140
ii udev 250.4-1
Versions of packages dropbear-initramfs recommends:
ii cryptsetup-initramfs 2:2.4.3-1
dropbear-initramfs suggests no packages.
-- debconf-show failed
Version: 2022.82-3
Severity: wishlist
I have recently started using dropbear-initramfs to try to help with situations
where boot problems need to be resolved remotely.
I have it working on one system but when I try to use it on a second system it doesn't work.
This second system is a server which is connected directly to a VLAN trunk, so the IP config
needs to specify a VLAN to use.
I tried using the kernel command line "ip=" to specify the interface name with a VLAN id
in the same format as used in /etc/network/interfaces:
ip=192.168.0.205::::name.a.b.c:eth0.100::192.168.0.1:
However, this did not work.
It would be great if I could use dropbear-initramfs on the host systems
which are directly connected to the VLAN trunk.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dropbear-initramfs depends on:
ii busybox 1:1.35.0-1
ii dropbear-bin 2022.82-3
ii initramfs-tools 0.140
ii udev 250.4-1
Versions of packages dropbear-initramfs recommends:
ii cryptsetup-initramfs 2:2.4.3-1
dropbear-initramfs suggests no packages.
-- debconf-show failed
Guilhem Moulin
Jul 20, 2022, 7:40:04 AM7/20/22
to
Control: reassign -1 initramfs-tools-core
On Mon, 18 Jul 2022 at 22:17:09 +0100, Graham Cobb wrote:
> I have it working on one system but when I try to use it on a second system it doesn't work.
> This second system is a server which is connected directly to a VLAN trunk, so the IP config
> needs to specify a VLAN to use.
>
> I tried using the kernel command line "ip=" to specify the interface name with a VLAN id
> in the same format as used in /etc/network/interfaces:
>
> ip=192.168.0.205::::name.a.b.c:eth0.100::192.168.0.1:
>
> However, this did not work.
>
> It would be great if I could use dropbear-initramfs on the host systems
> which are directly connected to the VLAN trunk.
The network configuration routine isn't implemented in src:dropbear but in
initramfs-tools-core's /usr/share/initramfs-tools/scripts/functions:configure_networking().
All dropbear-initramfs does is to call that function in its hook script.
AFAICT initramfs-tools=0.140ubuntu14 adds vlan (and IPv6) support but I
don't know if these patches are viable for Debian.
--
Guilhem.
On Mon, 18 Jul 2022 at 22:17:09 +0100, Graham Cobb wrote:
> I have it working on one system but when I try to use it on a second system it doesn't work.
> This second system is a server which is connected directly to a VLAN trunk, so the IP config
> needs to specify a VLAN to use.
>
> I tried using the kernel command line "ip=" to specify the interface name with a VLAN id
> in the same format as used in /etc/network/interfaces:
>
> ip=192.168.0.205::::name.a.b.c:eth0.100::192.168.0.1:
>
> However, this did not work.
>
> It would be great if I could use dropbear-initramfs on the host systems
> which are directly connected to the VLAN trunk.
initramfs-tools-core's /usr/share/initramfs-tools/scripts/functions:configure_networking().
All dropbear-initramfs does is to call that function in its hook script.
AFAICT initramfs-tools=0.140ubuntu14 adds vlan (and IPv6) support but I
don't know if these patches are viable for Debian.
--
Guilhem.
Thomas Kuhlmann
Jan 24, 2024, 1:10:05 PM1/24/24
to
A solution would be really great, because ...
... crypted root and vlan (in combination) are not uncommon.
... all other (large) distributions (Ubuntu, RedHat, SuSe) already
supports this.
With many thanks in advance,
Thomas
... crypted root and vlan (in combination) are not uncommon.
... all other (large) distributions (Ubuntu, RedHat, SuSe) already
supports this.
With many thanks in advance,
Thomas
0 new messages