All,
Looking at the changelog, I see what may have occurred (since I upgraded from 1.13 to 1.16):
Version 1.13 (20.Nov.2014): - Ignore subnets for which the gateway is inside their own subnet - Reconstruct RIP messages to be forwarded and send them about every 30 sec - Forwarded RIP messages do not use authentication Version 1.14 (21.Sep.2016): - Password in included in the daemon. Only need to set it should it ever change (OK from Brian Kantor - Tnx.) - Added man page courtesy of Ana C. Custura and the DebianHams * Version 1.15 (21.Sep.2016):** ** - Removed multicast access mode. Only raw sockets are used. Parameter '-r' is ignored
------------------------------------------------------------------------------------- * Version 1.16 (3.Feb.2017): - Added support for BGP announced 44net endpoints Version 1.16.1 (4.Feb.2017): - Added route cleanup on exit via CTRL-C in console mode. - No functional changes Version 1.16.2 (5.Feb.2017): - Reconnect RIP forwarding interface after interface down (Tnx. Gus, I0OJJ). - No functional changes * Version 1.16.3 (19.**Feb**.2017): <think month is off** ** - Correction for host routes on big endian machines.** ** - No functional changes** * If I revert to 1.13/1.14, I loose functionality. If I continue with 1.16, I cannot:
- send to other gateways with proper password (lost in versions <=1.13) *- OPTION to FIREWALL receipt of IPENCAP on WAN-facing side on Linux machine using iptables/netfilter (broken in 1.15)* *- correctly process routes on RISC-based CPUs (fixed in 1.16.3)* - enjoy the bug fix if tunl0 goes down while system is up (fixed in 1.16.2) - clear routes stored in the table when the process ends (added in 1.16.1) *- contact BGPed subnets (fixed in 1.16.0)* - POSSIBLY SEE ENCODED MAC ON LAN-facing SIDE OF TUNL0 (reported by Rob)
(I highlighted 3 major 'physical' and 'logical' bugs with 1.16.3.)
- Lynwood KB3VWG