Re: Re: Status changes for nodes hosted on clrghouz
By: Warpslide to deon on Sat Aug 29 2026 06:39 pm
Howdy,
If it's the same IP as your other BBS, I'll make a change this side so its not that strict on you.
For NRTG it'll be 99.244.153.113, it's technically dynamic but that hasn't changed on me in years *knock wood*.
OK, I see both your BBSes come from different IPs, looks like 3/110 uses mostly IP6 too...
The reason 3/210 was being blocked, looks like it was polling every minute: ::ffff:99.244.153.113:1272 [29/Aug/2026:21:15:20.137] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1275 [29/Aug/2026:21:16:20.068] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1276 [29/Aug/2026:21:17:20.018] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1277 [29/Aug/2026:21:18:20.022] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1278 [29/Aug/2026:21:19:20.053] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1279 [29/Aug/2026:21:20:20.123] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1280 [29/Aug/2026:21:21:20.038] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1281 [29/Aug/2026:21:22:20.057] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1282 [29/Aug/2026:21:23:20.033] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
::ffff:99.244.153.113:1283 [29/Aug/2026:21:24:20.048] fe-clrg-binkp fe-clrg-binkp/<NOSRV> -1/-1/0 0 PR 1/1/0/0/0 0/0
Since you are using binkd for that, you probably want to look at the binkd fail options. There is one that counts how many times it retries, and the other being the time between failed retries.
From memory:
try 2
hold 15m
...δεσ∩
--- SBBSecho 3.37-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)