Topics created by explosivo98

@george1421 I’ve actually managed to deploy this image to a range of different hardware without doing the sysprep, although I guess the fact that this thread exists might indicate that’s not the best idea… I would very much be interested in the guide you mentioned, I think next time I’m in the office I’ll have to seriously look into doing it through vmware/vbox.

@explosivo98 Strange that kernel should boot because the only thing added was some apple hardware IDs and an apple disk patch. Nothing for non-apples should be impacted.

Okay, so after some testing this morning I’m happy to report that I was able to get this working. I was going off the guide on the wiki which had it configured almost exactly like I pasted in the OP, but after some googling I saw people recommending NOT including the bond-primary lines for each of the bonded interfaces. I commented out those lines to test and sure enough it worked. Below is my current network interfaces config:

auto lo iface lo inet loopback auto eno1 iface eno1 inet dhcp auto bond0 iface bond0 inet static bond-slaves none bond-mode 2 bond-miimon 100 address 192.168.214.10 netmask 255.255.255.0 network 192.168.214.0 broadcast 192.168.214.255 gateway 192.168.214.1 hwaddress ether 90:e2:ba:f5:58:ba auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 # bond-primary enp2s0f0 enp2s0f1 auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 # bond-primary enp2s0f0 enp2s0f1

I think what also helped was a clean reinstall of Debian; when I posted this thread I was attempting to change existing settings from a pretty setup using only one of the network ports. I did a full reinstall and configured the interface bonding FIRST, then once I was confident that was working I ran the Fog installer and used bond0 as the interface. Installation completed without a hitch and I was online. I appreciate the assistance, I definitely learned a lot along the way, but the solution to this problem of mine with multiple network ports ended up being much easier than anticipated once I knew what to do. Now it’s time to image!

After a few days of testing on a local network just using the onboard ethernet port going to a router this is already a heck of a lot easier than the previous imaging solution that I banged my head against for a month. Bare metal is definitely the way to be and I greatly appreciate the insight. I would have torn what remains of my hair out trying to figure out making that work with Virtualbox.

Going from here, trying to get the final set up the way I described in my original post, it sounds like I need to look into the DHCP configuration to move the imaging to the two additional ethernet ports and off eno1, is that correct? Right now I have eno1, enp2s0f0, and enp2s0f1. eno1 will be supplying internet and I presume the other two will be on different gateways reaching out to the switch where the target PC’s will be connected to. Would this be something I can achieve using the built in tools?