frr VS ctl

FRR https://frrouting.org/ is another open source tool for a more Cisco style CLI syntax. You’d install that on top of most Linux distros.

Use a decent PC or three, use https://frrouting.org/ and see fast bgp convergence 8-)

Open source, check out freerouter (https://wiki.geant.org/display/RARE/Home) and FRR (https://frrouting.org/)

u/GamerLymx The setup goal was, originally, to set this up as a desktop testing router using FRRouting so I could experiment with some technologies I work with, namely OpenFabric without having to buy a $6k switch (Extreme Networks) as well as OSPF and EIGRP. However, I ran into some issues with setting up FRRouting and could not find sufficient information out there to overcome those. So I decided to just turn it into a plain router using NFTables, etc., when I ran into the issues with Netplan.

Has anyone ever setup FRRouting to connect to a consumer VPN such as NordVPN? I have been Googling but have come up empty so I am assuming it is not something that can be done. Just the same, I thought I would ask in case I am asking the question wrong in my searches.

Linux machine with 96G RAM, can do full internet table IPv4/IPv6 (dual stack) with FRR (https://frrouting.org)

Right, so it turns out that FRR (the routing plugin for opnsense) doesn't support multiple address familys in ospfv3. It is down as a feature request here and is closed as issue #303.

C Container Template Library (CTL)

I guess something like that may exist but it can be done with the preprocessor alone. See https://github.com/tylov/STC or https://github.com/glouw/ctl

I assume you refer to that two of the letters match with STL or STD, right? Even if they are not related to C at all. I assume STB, CTL, are not acceptable for you either?

The standard C library lacks any kind of containers (vectors, hash tables etc.) so the first thing would be to find one you like. For example, the C Template Library is a nice one: https://github.com/glouw/ctl

While I agree the common pattern is to use void*/dynamic dispatch, this is not necessary. E.g., https://github.com/glouw/ctl/ or https://github.com/c-blake/bst show a couple ways to have generic code statically specialized in regular old C.

The template instantiation is rewritten and is now similar to how glouw CTL library does it. STC no longer contains long macros for generating the templated code.

define type macros before #including the implementation. (intrusive) This is how https://github.com/glouw/ctl does it. The good: type-safety. no casting, clear error messages. Somewhat clumsy to have to individual #includes for each container type instantiation of the same container.