MSGID: 2:280/464.47 65493b7a
REPLY: 2:280/5555 6547e4e2
PID: JamNNTPd/Linux 1
CHRS: LATIN-1 2
TZUTC: 0100
TID: CrashMail II/Linux 1.7
Michiel wrote (2023-11-05):

 MvdV> Hello Binkd Team,

 MvdV> I would like to see the following.

 MvdV> On an incoming call binkd reports:

 MvdV> - 10 May 14:46:36 [756] incoming from 2001:16d8:ff00:306::2 (3499)

 MvdV> What I would like to see is this:

 MvdV> - 10 May 14:46:36 [756] incoming from 2001:16d8:ff00:306::2 (3499) to
 MvdV> 2001:7b8:2ff:3a9::2

 MvdV> Where 2001:7b8:2ff:3a9::2 is one of my own IP addresses, the address
that
 MvdV> caller used to contact my binkd server.


 MvdV> Reason:

 MvdV> My binkd server is "multi homed". It can be reached via two different
 MvdV> ways. Via my SixXs tunnel and via my he.net tunnel. In order to judge
how
 MvdV> effective this "multi homing" is, I would like to see via which channel
 MvdV> an incoming call comes in.

A Perl hook might work. Something like:

sub on_handshake
{
    Log(3,"incoming to $our_ip $our_port");
}


or modify the "incoming" log message in the on_log() hook

---
 * Origin: No REPLY kludge - no reply (2:280/464.47)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 123/131 124/5016 129/305
SEEN-BY: 153/757 7715 154/10 203/0 218/700 221/0 226/30 227/114 229/110
SEEN-BY: 229/112 113 200 206 275 307 317 426 428 470 550 664 700 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 291/111 292/854
SEEN-BY: 292/8125 301/1 305/3 310/31 317/3 320/219 322/757 341/66
SEEN-BY: 341/234 342/200 396/45 423/120 460/58 633/267 280 281 384
SEEN-BY: 633/410 412 418 420 509 2744 712/848 770/1 5020/400
PATH: 280/464 633/280 229/426