TIP: Click on subject to list as thread! ANSI
echo: binkd
to: MICHIEL VAN DER VLIST
from: PAVEL GULCHOUCK
date: 2016-05-16 18:21:00
subject: Feature request

Hi Michiel!

13 May 16, Michiel van der Vlist ==> Andrew Kolchoogin:

 MV>>> So I hope it will be included in v1.1a-95.

 AK>> You have to spend some time kicking the ass of 463/68. :)

 MvdV> Then I will do that. ;-)

Got it. ;-)

The easiest way to include a patch is create pull request on github.

In this particular case I doubt that this patch is really useful. On most cases
binkd is not multihomed, or it does not matter which local IP address was used,
so it's redundant information in the log, obstructing to read it for most of
sysops.

If you need this info, you can get it by either run two separate binkd servers
(with "include" common part in config) or get this information in the
on_handshake() perl hook and put it to log.

IMHO it's make sense to log local IP if multiple "listen" keywords specified in
config. But you faced some problem in such configuration. I'll try to catch it,
but not sure.

              Lucky carrier,
                           Pavel
                           aka  gul@gul.kiev.ua
--- GoldED+/LNX 1.1.5
* Origin: II:CDLXIII/LXVIII (2:463/68)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.