☑ Connect to selected server only: connection was to a different server

[grahamperrin]

Long ago, I preferred irc.inet.tele.dk alone for EFNet.

Earlier today, I found myself connected to a different network – efnet.port80.se – with an offensive MOTD.

Is this a bug in HexChat? Or can server infrastructure somehow override the user's preference?

Environment

% pkg iinfo hexchat
hexchat-2.16.1_3
% uname -aKU
FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #41 main-n263189-c2c9ac88c2bb-dirty: Sat May 27 16:55:26 BST 2023     grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 1400089 1400089
% 

[MetaNova]

This is not a bug. irc.inet.tele.dk is an alias for efnet.deic.dk. Connecting to efnet.deic.dk results in

efnet.deic.eu Message of the Day -
Welcome to the danish EFnet server
(Formely irc.inet.tele.dk, now efnet.deic.dk)

[grahamperrin]

From the window in the background:

* Disconnected (Remote host closed socket)
 Cycling to next server in EFnet...
* Disconnected ()

Is that something other than HexChat initiating the cycle?

[grahamperrin]

Following discussion in IRC, here's the session info for #2785 (comment) above:

efnet.deic.dk, efnet.deic.eu.txt

Highlights:

• Processing connection to efnet.deic.eu
• Disconnected (Remote host closed socket)
• Cycling to next server in EFnet...
• Disconnected ()
• Looking up irc.inet.tele.dk
• Connecting to efnet.deic.dk (130.226.213.194:6697)
• Processing connection to efnet.deic.eu
• Your host is efnet.deic.eu[130.226.213.194/6697], running version ircd-ratbox-3.0.10

– so, no problem there, although the wording of one line might be improved (if generated by HexChat). Change from:

Cycling to next server in EFnet...

to:

Cycling to next server for irc.inet.tele.dk...

---

If not presented by any address that's associated with irc.inet.tele.dk: I wonder how I got the offensive message for which efnet.port80.se is known.

In IRC, there's the suggestion to de-list efnet.port80.se and other servers. It's reasonable to assume that this will avoid the problem, however I'd like to know what's happening when the problem does occur so for now:

• I'll leave my preferences unchanged
• hoping to eventually, maybe randomly, encounter the problem, and then I'll take proper notes of the session.

[grahamperrin]

Afterthought, maybe this line is misleading:

Cycling to next server in EFnet...

– in that it did not cycle. If I'm not mistaken, it retried the same server.