I've been running my old crappy 99% stock BBS for years now, and the ammount of
times I get hangs from scripts hammering away on port 23 is absolutely insane. >I have setup (well at least the commands didn't complain, no idea if it >actually works) rate limiting on inbound port 23, but it doesn't stop.. As 2016
winds down, is it really feasable to run 90's era software on the internet >using port 23?
I'm the lone one with OS/2 and SIO of all thing. I know that there was some >dump last week of public anonymous ftp sites, and I'm certainly not the only >one running ancient stuff out there! ... But has anyone experenced any massive >downside to not having port 23 accessable?
I would consider switching permanently but I have not had much time to figure out how to get the DOS doors running under SBBS linux. So, while dial-up still gets GT, what few telnet users I had who liked the doors are sort of out of luck for now.
MIKE POWELL wrote to NEOZEED <=-
In my case, the GT BBS software did not have any issues with the hammering... it was the SIO/VMODEM software that would hang after being hammered non-stop for so long.
Odd thing... about a week after I switched to SBBS, the hammering has mostly stopped. I added some things to the CAN files that may have
helped but, mostly, I think it stopped on its own.
I would consider switching permanently but I have not had much time to figure out how to get the DOS doors running under SBBS linux. So,
while dial-up still gets GT, what few telnet users I had who liked the doors are sort of out of luck for now.
I have actually thought about trying to set something up, using the
SBBS door that telnets to other boards, so that folks can telnet from
the SBBS locally over to the GT board.
I ran into so many problems just over the past month with that, right about the time that the Clinton e-mails leaked (oddly), that I decided to at least temporarily shut down telnet for my OS/2 / SIO / GT Power board and have routed the telnet traffic to Synchronet, which I was using just for a web board.Oh good, there are like TWO of us now! I did a test upgrade to Warp 3 & 4 to see if that helped, and it sure did not. So back down to OS/2 2.0 WR06100 for me.
In my case, the GT BBS software did not have any issues with the hammering... it was the SIO/VMODEM software that would hang after being hammered non-stop for so long.
Others with this problem have had success using Mystic as a front end, using its matrix menu. Mystic takes the sting out of the probes, adding them to its block list. Legitimate users get passed on to SIO.
I haven't done this myself, but I know others who have with success.
That would work. Similar to the Mystic solution, though the Mystic matrix menu doesn't require a login before being transferred to the other BBS.
Neozeed wrote to Vk3jed <=-
I was thinking of something to front the OS/2 SBBS, but hadn't really
gone that much further after I setup rate limiting...
I haven't done this myself, but I know others who have with success.
That would work. Similar to the Mystic solution, though the Mystic matrix menu doesn't require a login before being transferred to the other BBS.
It may very well be worth looking at.
Others with this problem have had success using Mystic as a front end, using its matrix menu. Mystic takes the sting out of the probes, adding them to its[...snip...]
block list. Legitimate users get passed on to SIO.
That would work. Similar to the Mystic solution, though the Mystic matrix menu
doesn't require a login before being transferred to the other BBS.
Yes, SIO is the weakest link, for sure. It is annoying as frankly OS/2 is the >best way to run multiuser MS-DOS Doors, bar none that I've found. But machines
get faster and faster, I may break down and try some text mode Qemu passthru >along with some samba server or something in the middle. DOSBox can't lock, >but booting MS-DOS with a lan card to a shared drive ought to do the trick, >just have to setup scripts to pass it flags and stuff, I guess build custom >boot disks and script it all out in some insane fashion..... Or just suck it >up, and keep OS/2. It's too bad Ray Gwinn just up and disappeared..
all out in some insane fashion..... Or just suck it up, and keep
OS/2. It's too bad Ray Gwinn just up and disappeared..
MIKE POWELL wrote to HEMO <=-
doesn't require a login before being transferred to the other BBS.
Interesting. Do you mean the Mystic BBS software or is this some other Mystic? I guess it automatically sniffs out the probes? I wonder if
it could pass straight to the other BBS software without SIO/VMODEM.
He's on facebook... but I think he's said in the past he lost the source.
Re: Pulling The Plug On Port
By: Tiny to Neozeed on Sat Oct 01 2016 05:22 pm
He's on facebook... but I think he's said in the past he lost the source.
Oh bummer.. Its amazing the stuff that is lost, digitial wise, setting it free is the only way to keep it around..
Oh bummer.. Its amazing the stuff that is lost, digitial wise, setting it free is the only way to keep it around..
some things are best lost.
In the same light, I guess it's why UNIX clones are so popular, but nobody ever
coded an OS/2 clone. It was just too good at running Windows 3.0/3.1 standard >mode stuff, and MS-DOS apps.
He's on facebook... but I think he's said in the past he lost the source.Is there still a need for SIO/VMODEM aside from bbsing? Maybe the new
Shawn
Quoting Matthew Munson to TINY <=-
Is there still a need for SIO/VMODEM aside from bbsing? Maybe the new people developing OS/2 could make it all over again.
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 137 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 92:21:16 |
| Calls: | 15,362 |
| Files: | 20,057 |
| D/L today: |
7 files (1,002K bytes) |
| Messages: | 1,797,472 |