Board:   [fsxNet] fsxNet Network Discussion
Subject: Re: Hub 3 rate limiting
From:    deon(21:2/116)
Date:    Thu Mar 26, 2026 10:28

  Re: Re: Hub 3 rate limiting
  By: Warpslide to deon on Wed Mar 25 2026 01:56 pm

Howdy,

 >  de> * Maximum 2 concurrent connections,
 >  de> * Maximum 5 connections in a 60 min period.
 >
 > These seem like sane limits.

Thanks, I was going for that :)

 > I have Mystic configured to send messages as I save them (they'll get
 > tossed/sent within ~60 seconds of being saved).  About the only way I could
 > see myself making more than 5 connections in a 60 minute period is if I
 > wrote and sent that many messages, which is unlikely.

I'm not 100% happy with implementing these - as it does drive a behaviour that I didnt want to drive - ie: an interactive chat via echomail/netmail that does sometimes happy. Thus, if you sent more than 5 message in an hour, the 6th wouldnt make it until the first connection "expired".

I'll probably relax it if I can, ie: dont count a connection if you send something to the hub.

 > How is the rate limit implemented?  Would the connection attempt be dropped
 > or rejected at the network level (fail2ban style) or would binkp still
 > answer and reply with a rate limit error message?

Haproxy is doing it for me - so its not getting to clrghouz at all.

If you exceed the limit on the BINKP port, you should get an M_BSY message and the connection will drop. If you exceed it on the EMSI port, you'll get a "I'm busy message" on connect and then it will be dropped.


....δεσ∩
--- SBBSecho 3.29-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
.