Re: [44net] ipencap routing question -> What about the future ?

Rob, * FYI - Wireguard has a Windows client; but I get your point about being OS/NOS agnostic * I honestly understand there to exist 2 common paradigms: 1.) those who route IPs to others/clients/hosts; and 2.) those who only tunnel the AMPR IPs to a single device. Your statement primarilly covers the latter use case. * I know of no embedded "Windows routers" (well there are small x86_64 machines) * IP Protocol No. 4 (IPENCAP) is possible on Windows (specifics unclear)...but there was never much support to ensure ampr-ripd/rip44d/something was tested/working, at least when I was attempting in 2012 * I found out even if I got a Windows machine working, if I wanted to do DNS (which I noted to late Brian that I would for the MDC Section), I leaned the Windows dns.exe executable will crash attempting to load our Public Forward and Reverse Zones - so I still need a *nix server/router - KB3VWG --- I think we should avoid running into traps like "let us choose that new wireguard as thestandard protocol to be used by everything" as we would again exclude everything outside of Linux and OpenWRTand end up in the same situation as we now are with IPIP mesh: always requiring the user to install a Linux box.