Greetings All!


So we are switching fido networks from 340 to 105 here in oregon and I went through echocfg, scfg and areas.bbs and changed all the 340 info to 105 including binkp addy and passwords. I sent all mail out first so there is nothing in outbound left for 340. I keep getting this error, it runs every minute or so..

BINKP connection accepted from: 96.61.143.149 port 49558
Nov 10 20:40:54 sbbs synchronet[656]: srvc 0060 BINKP BinkIT/2.39 invoked with options:
Nov 10 20:40:54 sbbs synchronet[656]: srvc 0060 BINKP JSBinkP/1.123 inbound connection from 96.61.143.149:49558
Nov 10 20:40:54 sbbs synchronet[656]: srvc 0060 BINKP Peer version: Taurus/5.101/16.02.2009, 19:33 (Winter)/Win32 binkp/1.1
Nov 10 20:40:54 sbbs synchronet[656]: srvc 0060 BINKP Remote addresses: 1:340/0@fidonet 1:340/400@fidonet 10:10/1@league10 10:10/0@league10 10:3/1@league10 201:1000/3@dbnet 618:300/12@micronet 316:77/1@whispnet 24:140/0@sportnet 24:140/1@sportnet 24:140/2@sportnet 719:510/0@cscn 719:510/1@cscn
Nov 10 20:40:54 sbbs synchronet[656]: srvc 0060 BINKP BinkP got fatal error 'Invalid addrs: 1:105/11@fidonet 24:110/9@sportnet' from remote: 1:340/0@fidonet,1:340/400@fidonet,10:10/1@league10,10:10/0@league10,10:3/1@leag ue10,201:1000/3@dbnet,618:300/12@micr onet,316:77/1@whispnet,24:140/0@sportnet,24:140/1@spo
Nov 10 20:40:54 sbbs synchronet[656]: srvc 0060 BINKP Send failure
Nov 10 20:40:54 sbbs synchronet[656]: srvc 0060 BINKP Error in recv() of first byte of packet header

at first I thought it was inbound but it appears my system is trying to send stuff, but there is no stuff. Am I just reading this wrong? I now have no fido addy configured at all and it continues. 340 usually doesnt poll me so not sure what is happening. Is there some sort of binkp flush I can do or a binkp specific log? cant seem to find one specific to binkp


----
Regards,


Rick Smith (Nitro)

... Wildcat! is to BBSing what an Etch-a-sketch is to ART!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (1:340/202.1)