TIP: Click on subject to list as thread! ANSI
echo: mystic
to: g00r00
from: Andrew Leary
date: 2014-11-09 22:21:08
subject: New Binaries

Hello g00r00!

Friday November 07 2014 09:35, g00r00 wrote to Kris Jones:

 gr> I suspect the ADR is hitting the 255 character limit.  If he turns on
 gr> the option in BINKD for you to so that it only uses the relvant
 gr> addresses, it should work.

Gert's system has A LOT of addresses, so you are probably onto something
there. I have one Mystic downlink here, who I had problems with until I
modified my BinkD.cfg to only present my primary address in each network. 
When I was helping debug with him, I also seem to remember that his system
was only able to deal with the first 15 addresses presented when checking
the passwords.

 gr> I'll see if I can expand it beyond the 255 limit.

The Binkp/1.0 protocol specification allows up to 32767 bytes for the data
part of a Binkp command frame, so in theory you could expect up to 32766
bytes in the M_ADR address listing.

Regards,

Andrew

---
* Origin: Bits & Bytes BBS * V.Everything! * 860/535-4284 (1:320/119)
SEEN-BY: 3/0 633/267 280 640/384 712/0 620 848 770/1
@PATH: 320/119 261/38 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

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™.