1. Forum
  2. FSXNet
  3. FSX MYS

  • BinkP Server

    From Avon@21:1/101 to g00r00 on Fri Jan 31 21:12:34 2020
    A request. Would it be possible to create somewhere the sysop can set the max number of files that can be sent in an incoming/outgoing session?

    Perhaps in the server settings sections within Mystic

    [snip]

    + 2020.01.31 21:05:56 BINKP 1-New frame detected
    + 2020.01.31 21:05:56 BINKP 1-Begin receive command frame: GOT (Size=28)
    + 2020.01.31 21:05:56 BINKP 1-R: GOT 0ce68de0.pkt 1150 1579629164
    + 2020.01.31 21:05:56 BINKP 1-After Frame State R:Done T:GetEOF Have:True Need:False
    + 2020.01.31 21:05:56 BINKP 1-Before Frame State R:Done T:NextFile
    Have:False Need:True
    + 2020.01.31 21:05:56 BINKP 1-S: EOB
    + 2020.01.31 21:05:56 BINKP 1-Session ended (200 sent, 0 rcvd, 0 skip)

    [snip]

    I just watched a node pull down 200 packets then the session ended. I'm sure there are more there to be got. I'm assuming there's a limit coded somewhere
    to cause the session to end at the moment? I had a recollection it was lower
    in the past and you upped it. But on occasions like this when I think it's a node that has not polled for a while there can be a ton of stuff to collect when they want raw packets and 200 seems a low number to drop the call.

    Thanks for considering.

    --- Mystic BBS v1.12 A44 2020/01/29 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From g00r00@21:1/108 to Avon on Fri Jan 31 13:09:19 2020
    I just watched a node pull down 200 packets then the session ended. I'm sure there are more there to be got. I'm assuming there's a limit coded somewhere to cause the session to end at the moment? I had a

    Yes, it caps at 200 queued files per session. If so if they had 350 bundles waiting for them, they would get 200 the first poll and 150 the next.

    Is this a common thing you see where this number is reached? I think I had it set to 100 originally and I expanded it to 200 for you. I do want to keep some sort of limit in place and not just let it run wild and queue 15,000 files or something if they are there.

    --- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Avon@21:1/101 to g00r00 on Sat Feb 1 21:33:22 2020
    On 31 Jan 2020 at 01:09p, g00r00 pondered and said...

    Is this a common thing you see where this number is reached? I think I had it set to 100 originally and I expanded it to 200 for you. I do
    want to keep some sort of limit in place and not just let it run wild
    and queue 15,000 files or something if they are there.

    Not that common, but when a node asks for packets and does not poll for a few days it can get into the thousands quickly.. I think either allow for a
    manual setting in the BinkP server 0=unlimited or set a number 1-999 files
    per session... and allow fidopoll to read that setting also or perhaps lets just try with no limits.

    I tend towards allowing limits to be stated by the sysop. What if bandwidth
    is an issue or packets are being sent not directly by internet but over RF
    via AX.25 etc. then setting some limits would be a good idea :)

    I also think for the BinkP server the lower limits are not needed as incoming polls from nodes can occur concurrently so it does not matter if a node is
    tied up and pulling down 1200 packets if nodes 2-10 are free for other
    inbound polls.

    But for the current sequential fidopoll it does matter as the next node won't get it's packets until 1200 packets are sent to the node before it. So more reason to have settings for these things, and also for a fidopoll2 that
    mimics the multiple outbound polling of BinkD :)

    --- Mystic BBS v1.12 A44 2020/01/31 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)