Eve-NG Profressional + LACP/bonds

[chsmith2023]

{whisper: sent an email to info@eve-ng.net on my FRI - trying here as well}

Are there any notes on adjusting a “3.3.2 BM Server Installation Ubuntu legacy ISO” to employ “IEEE 802.3ad/LACP/Bonds” towards physical Ethernet switching?

I had followed the notes at “UbuntuBonding @ https://help.ubuntu.com/community/UbuntuBonding” and thought we were all good until a colleague tried the Wireshark pop-up via an HTML Console GUI and nothing happened.

I understand – by text searching on “bond” and “lacp” within the Cookbook – this may not be presently supported. But, yeah, we would be honoured to guinea pig our install to progress/test install tweaks to get this going.

Regards, Christopher

[mariannerawlins]

Hello, have you solved your issue? I also want to adjust the installation to support LACP/Bonds, but I can't find any resources that may be helpful.

[rusty725]

it won't work, don't waste time on this.

[chsmith2023]

it won't work, don't waste time on this.

I was going to play around on this a bit today, even with just standard "Hello World" type containers. Basically to build a picture of what exactly is not happening.

Sorry, but since we're paying for a Professional ($$$, re-occuring spend) seat, I won't be able to go back to my executive with a boiler-plate "not supported" nor "it won't work," type answer.
So yeah if there's ANYTHING you can share/give, it would be most helfpul! My sniff that our issue is the bond, came from here ...

"EVE-NG Professional Cookbook Version 5.9 > 15 EVE Troubleshooting> 15.2 Correct EVE server network interfaces order"
(from "https://www.eve-ng.net/index.php/docume ... -cookbook/")

I've attached some interesting snippet / notes, re from nicorder-wizard and seeing / noticing our bond is not listed.

20240102a.pdf

[chsmith2023]

Hello, have you solved your issue? I also want to adjust the installation to support LACP/Bonds, but I can't find any resources that may be helpful.

Maria, I have been able to progress our issues successfully. Some highlights -

> I had rebuilt our EVE-NG bare metal November'ish 2023. There were no build notes from the previous engineer, and so I've been on this march to piecemail their work outside the regular EVE-NG backups and restores.
> First, there are two NICs inside /etc/network/interfaces -- natmac and nat0 -- that, during our build, kept throwing errors on boot. We had commented them out and ran through a manual NAT config-bind against pnet9 using ISC DHCP.
> This was our first error: not coming back to this band-aid. Today, I reversed that work and now our EVE-NG is using the natmac and nat0 as expected. What changed? I'd be guessing ...
> Second, at some point there must have been an IPTABLES save to /etc/iptables as it kept loading phantom masquerades. For this, I just moved out the IPv4 rules files some place else so it would not get parsed on boot. This allowed EVE-NG + Docker runtimes to set up the right rules as they needed without anything stale.
> Finally, the Third - which, I believe, THE most important - there's a System Settings configuration inside our 5.0.1-120-PRO (Login via web, then navigate to "Systems --> Systems Settings"). One of the features (am assuming this is new ... ThankGod) is to change around the DOCKER subnets used. (1) I spun up a laptop with PRO and noticed a fresh build / install used 172.17.0.0/16 for DOCKERS and (2) running a watch -d iptables -t nat -L -v -n --line-numbers on attempting to start anything Docker'esque, and I could see highlighted differences on 172.17.x.x nets. Armed with these two points of confidence, I (A) set the System Settings IP to something else to what was there (172.18.0.0__ to I think 172.20.0.0__ since it's temporary), (B) rebooted, (C) went back into System Settings and set it to 172.17.0.0__, then (D) last reboot.

We login as HTML5 Console, so my testing is limited to this realm. Once back in after the reboots, I could (1) Guacamole --> RDP to an "eve-gui-server:latest" docker that had DHCP on it's eth0 and (2) Guacamole --> RDP to the dynamic Wireshark docker that gets kicked off from "Capture --> eth0"

FWIW, there was nothing special about our bond0 config (see PDF attached to previous post). It's just a bridge anyways to pnet0.

Kind regards