Max Baro

Hey Steven. Thanks for the responses so far. I found the root cause of my deployment issue. I see you use BusyBox in the initrd image as the embeded linux for startup. BusyBox has added the vconfig applet to configure VLAN interfaces, but it is not found in the current image I am running. Can I just drop in a newer version of BusyBox? I checked the source for DRBL from this site and did not see this application, is it included in Clonezilla instead?

Thank you for the reply. We have been testing with iPXE with no success so far. I believe our base issue is there is not enough support for VLAN tagging in RH8.

2 questions: When the system pxe boots in clonezilla-se mode, during initrd-pxe.img is it executing the /initrd or /sbin/initrd? I found the function 'config_drbl_live_network'. Is this what configures the network when booting in clonezilla-se? I see it does not grab the VLAN ID from DHCP and configures it. My DHCP is set as such: host lpsrv1 { hardware ethernet aa:bb:cc:11:22:33; fixed-address 10.0.0.1; option vlan-id "200"; option host-name "lpsrv1"; }

Update, I got the module 8021q into initrd-pxe by modifying mkpxeinitrd-net, but it does not appear to load. How do I run drblsrv-offline to build the PXE kernel and initrd with the 8021q mod loading?

Thanks for that. I'm still running into issues getting PXE to work. We have determined the kernel module 8021q is required for VLAN tagging. The module is not being built into the initrd-pxe.. file. I have gone through the scripts starting with 'drblserv-offline' and followed the process through to mkpxeinitrd-net. I added the module name 8021q to /usr/lib/mkpxeinitrd-net/initrd-skel/etc/modules and recompiled. The module is still not getting into initrd. Is there a filter somewhere that limits what...

Hi Steven. We use VLAN tagging in order to connect multiple networks to a single network interface. When the traffic is tagged, meaning the VLAN ID is transmitted in the packet it works like a control, in that the system will not receive packets that are not tagged. We found that the limitation was in the GRUB version in RH8, v2.02 does not support VLAN tagging. Version 2.12 does however and we are attempting to make that work, creating the bootx64.efi PXE file with the 2.12 version. If I can get...

We have tagged vlan configured across the servers in order to trunk multiple vlans over a single interface. The server BIOS is configured with the VLAN ID and the initial DHCP traffic is tagged, the initial boot64.efi file is downloaded, but subsequent connections are not tagged, so no other requests are tagged so the remaining files do not download. I looked through /sbin/drbl-gen-grub-efi-nb but do not see a way to enable vlan tagging. Using clonezilla-5.4.6-drbl1.noarch. Can we enable VLAN tagging...