
                      XROUTER CHANGELOG
                      #################

                  Summary of Recent Changes
                  =========================


Version 504k (19th Oct 2025)
============

Fixed:  Bug introduced in v504j which caused segfault when unicasting
        an "internal" nodecall via INP3.

Fixed:  Bug introduced in v504j which caused blank Admin page on HTTP
        interface.

Change: When loading the XRNODES recovery file, the saved MAXHOPS value
        for a ROUTE now overrides the PORT maxhops ONLY if the route is
        locked.

Added:  AX25v2.2 TEST functionality.

************************************************************************

Version 504l (26th Nov 2025)
============

Fixed:  PING now returns "No Route" instead or "No socket layer" if
        an ethernet port was available but no suitable route had been
        defined in IPROUTE.SYS.

Fixed:  Restored the ability to specify COM in the Windows version as
        either "COM=5" or "COM=COM5". This was broken in March 2020,
        since when only the second form had been accepted.

Fixed:  Suppressed the "Use cap-net_raw" msg on Windows.

Fixed:  The Windows version can now use ALT-X to exit, as per the Linux
        versions, instead of CTRL-C.

Change: CHANNELS.DAT now uses plain text instead of binary format,
        allowing it to be used by 16, 32 and 64-bit versions without
        risk of corruption.

Change: Prevented reception of outgoing frames looped back from
        EXTERNAL ethernet drivers. These were not causing any problem,
        other than cluttering up the packet trace display.

Added:  Automatic default route, if no routes specified in IPROUTE.SYS.
        The policy of giving sysops the freedom to configure things how
        they wanted has caused far too much work for me, having to try
        and diagnose their configuration mistakes by telepathy. The
        automatic route can of course be overridden by a manual entry.

Added:  AXTEST command, which sends an AX25v2.2 TEST frame.

Added:  Lots more packet reporting stuff.

Added:  Protection against unspecified ETHADDR in EXTERNAL interface,
        in Windows version.

************************************************************************

Version 504m (29th Oct 2025)
============

Fixed:  In some situations, the timestamp associated with a CHAT
        channel could be wrong.

Added:  ARP and IP header tracing for Packet Network Monitoring Project.

************************************************************************

Version 504n (9th Nov 2025)
============

Fixed:  Potential memory leak upon graceful close of TCP stream on the
        host TCP/IP stack.

Fixed:  When node-hopping via the HTTP interface, the user callsign
        was being replaced by the nodecall.

Fixed:  Bug in FRMR tracing that could, in very rare instances, cause
        a segfault.

Change: Trace for CREQ and CREQX now report "myCct" instead of "cct".
        It is the same number, but this change clarifies its purpose.

Added:  L2 trace reports can now be read via the MQTT broker, using
        the topic xrouter/L2Trace/{nodecall}/{portnum}.

Added:  If the mailbox is in "full BBS" mode, it is now connectable
        via NetRomX service 3 (BBS). Service 2 (PMS) access the mailbox
        in "PMS" mode, i.e. private messages only. If the mailbox is
        NOT in "full BBS" mode, service 3 is not available.

Change: Added "serial" to "L2Trace" reports, so that the chronological
        sequence of reports can be preserved even if the transport or
        server processing changes the sequence.

Change: Other minor tweaks to packet tracing.

************************************************************************


