OpenWRT/LEDE and Watchguard Firebox Core x750e

[fever_wits]

Hello,
I'm a happy owner of a device Watchguard Firebox Core X750e and i will use it as a router and switch.
If I have confused the subject, please excuse me.
I need help for several problems:

1. I have to use a bond. I did not find the ifenslave package, it does not have it as a source to compile it. I made a manual configuration in the following way:
   root@Firebox:~# cat /etc/rc.local
   ............................
   .# Add BOND0
   .# Info: https://www.kernel.org/doc/Documentation/networking/bonding.txt
   /usr/sbin/ip link set bond0 down
   /usr/bin/echo +bond0 > /sys/class/net/bonding_masters
   /usr/bin/echo 4 > /sys/class/net/bond0/bonding/mode
   /usr/bin/echo 100 > /sys/class/net/bond0/bonding/miimon
   /usr/bin/echo 200 > /sys/class/net/bond0/bonding/downdelay
   /usr/bin/echo 200 > /sys/class/net/bond0/bonding/updelay
   /usr/bin/echo 1 > /sys/class/net/bond0/bonding/xmit_hash_policy
   /usr/bin/echo 1 > /sys/class/net/bond0/bonding/ad_select
   /usr/bin/echo 1 > /sys/class/net/bond0/bonding/lacp_rate
   /usr/bin/echo +eth2 > /sys/class/net/bond0/bonding/slaves
   /usr/bin/echo +eth3 > /sys/class/net/bond0/bonding/slaves
   /usr/sbin/ip link set bond0 up
   /usr/sbin/ip link set eth2 up
   /usr/sbin/ip link set eth3 up
   brctl addif br-lan bond0
   ...................................
   But the server on the other side returns the following error:
   bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
   Has anyone had a similar problem?

2. Firebox x750e has LEDs Arm / Disarm and Expansion, does anyone have any idea how can I use them?
   I found:
   https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Controlling_hardware_with_WGXepc
   And:
   https://github.com/fmertz/fbled
   https://github.com/fmertz/fbled/downloads#download_100802

When trying to run I get the following error:
root@Firebox:~# ./WGXepc
-bash: ./WGXepc: No such file or directory
root@Firebox:~# ./fbled
-bash: ./fbled: No such file or directory
root@Firebox:~# ./fbled-dbg
-bash: ./fbled-dbg: No such file or directory
I think there is no module, but I do not know who.

3. Firebox x750e has an LCD display, I was able to run LCDProc, but to send custum messages I need to expect: https://core.tcl.tk/expect/index
   Does anyone have a compiled package or help how to compile it.

4. I need to make my own mirror because there are packages that are not available, did anyone do it?

[jeff]

@fever_wits

I need to make my own mirror because there are packages that are not available, did anyone do it?

Lots there to digest and understand, but at least for that one, you can just add your packages on your own (local) branch of the existing repositories, or add a git repo for your own packages to feeds.conf

[fever_wits]

Thanks.
And ideas on other issues?

[jeff]

Looks like you've got several hardware- and/or application-specific utilities you need that aren't formal packages.

I don't know that you "need" expect in that it is the only way to send messages to the hardware. expect is pretty ancient (I recall using it in the early '90s) and something like Python may provide easier programming and greater utility for both your time in getting the package as well as not "dedicating" bytes on your device to a single purpose. expect will probably pull in Tcl runtime libraries, and may pull in GNU libc if it doesn't compile against musl

The build system isn't very well documented, but the couple resources I've found valuable include

Creating packages

Packaging guidelines

Moved to https://openwrt.org/docs/guide-developer/package-policies

and

Debugging package Makefile

I usually replace the $(eval $(call BuildPackage,...)) with $(error $(call BuildPackage,...)) - this will dump the entire dynamically generated ruleset to stderr. For all practical purposes, there is no distinction between the make package/.../compile and make package/.../install targets. The compile: goal depends on $(STAGING_DIR_ROOT)/stamp/.$(1)_installed which (through another stampfile) depends on $(STAMP_BUILT) and executes the package/.../install target. See include/package-ipkg.mk for…

[fever_wits]

Thank you very much for your help and assistance.
I use "Expect" to manage switches. For me personally, the language is very convenient for creating simple and complex scripts.
I will try to compile "Expect" and share my experience.

The solution to the problem of managing the Arm / Disarm and Expansion LEDs remains.
I think there is no module available. I tried to compile a whole system, but it bugs.
I will continue with attempts to compile everything or at least compile the kernel.

[fever_wits]

Hello,
I searched for my led problem and got into it:

tenchman/TTLinux

Can anybody help me to make a module for the kernel stream or add it to the kernel configuration?
This is beyond my capabilities, please help.