Hi Andrew,

In my quest to override nodelist settings with those in mbsetup, I discovered that anytime a setting was put in Inet hostname (7.x.3), any other logging reporting (mbout n ... and log files), show the BBS name as the Inet
Hostname. Can figure out why it should change the BBS name?

lib/nodelist.c around line 764.

/*
* Get system name
*/
if ((q=strchr(p,',')))
*q++ = '\0';
if (ndrecord && strlen(nd.Nl_hostname)) {
Syslog('+', "getnlent: %s system name override with %s", ascfnode(addr,0xff), nd.Nl_hostname);
nodebuf.name = nd.Nl_hostname;
} else
nodebuf.name = p;

...deon

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)

Hello Deon!

18 Sep 18 06:00, you wrote to me:

In my quest to override nodelist settings with those in mbsetup, I discovered that anytime a setting was put in Inet hostname (7.x.3),
any other logging reporting (mbout n ... and log files), show the BBS
name as the Inet Hostname. Can figure out why it should change the BBS name?

The original method for listing an internet hostname in the FidoNet NodeList was in the system name field. The INA: flag for the internet address came much later. MBSE was originally designed to look for the hostname in the system name field; then later adapted to other methods of listing the hostname, such as the INA: flag or attached to a protocol flag, or even an IP address in the phone number field.

Andrew

--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)