I need help with QWK networking, I have one network that my pail is going out, but it's not posting on his system which is a hub, so in turn, my messages are not getting to his downlinks. I know my system is processing the message, as I wrote a test message, and it gets bundled as a rep file, then goes out. I renamed the actual network amd address to protect the privacy of the other system, and my info.
Bundling
--------
2/21 05:09:54p NotNamedNet BBS Advertising
New: 1 of 138
2/21 05:09:54p Packing Sub-board...
2/21 05:09:54p Packed: 1 of 1
Calling Out And Delivering
--------------------------
2/21 05:09:55p QWK Network call-out: NETWORK
2/21 05:09:55p Executing external: *qnet-ftp NETWORK bbsaddress.com 0000 2/21 05:09:55p QNET-FTP: NETWORK bbsaddress.com 0000
2/21 05:09:55p QNET-FTP: Connecting to bbsaddress.com:21 ...
2/21 05:09:56p QNET-FTP: Connected to bbsaddress.com
2/21 05:09:56p QNET-FTP: Logging in as 'QWKNAME' (PW: '0000')
2/21 05:10:01p QNET-FTP: Logged in successfully
2/21 05:10:01p QNET-FTP: Sending REP packet: c:\SBBS\data\NETWORK.rep
2/21 05:10:02p QNET-FTP: REP packet sent successfully
My BBS QWK Setup on His system (HUB)
----------------------
QWK Settings for NETWORK #187:
[A] Ctrl-A Color Codes : Leave in
[T] Archive Type : ZIP
[E] Include E-mail Messages : Un-read Only
[I] Include File Attachments : Yes
[D] Delete E-mail Automatically : Yes
[F] Include New Files List : No
[N] Include Index Files : No
[C] Include Control Files : No
[V] Include VOTING.DAT File : Yes
[H] Include HEADERS.DAT File : Yes
[Y] Include Messages from You : No
[Z] Include Time Zone (TZ) : Yes
[V] Include Message Path (VIA) : Yes
[M] Include Message/Reply IDs : Yes
[X] Extended (QWKE) Packet Format: No
Which or [Q]uit:
I can't see any problem, on my system or his, but my systems messages are not being delivered by his system. I'm getting everything he is sending out, and I am sending ok, what are we missing?
We are both at a loss.
I even
today, deleted everything on my system pertaining to his networking, and started from scratch, then reset the pointers and imported everything he had. It's got to be something simple. Using Windows 7 Pro. This isn't my first rodeo, but I've exhausted everything I know to fix this, not I'm trying to get suggestions to see if I can give one of us a clue to what is going on. Thanks in advance.
I need help with QWK networking, I have one network that my pail is going out, but it's not posting on his system which is a hub, so in turn, my messages are not getting to his downlinks. I know my system is processing the message, as I wrote a test message, and it gets bundled as a rep file,
I can't see any problem, on my system or his, but my systems messages
are not being delivered by his system. I'm getting everything he is
sending out, and I am sending ok, what are we missing?
Does your QWKnet account on the hub BBS have the permission to post messages?
We are both at a loss.
The hub's logs will tell him why your messages weren't posted.
I even
today, deleted everything on my system pertaining to his networking,
and started from scratch, then reset the pointers and imported
everything he had. It's got to be something simple. Using Windows 7
Pro. This isn't my first rodeo, but I've exhausted everything I know
to fix this, not I'm trying to get suggestions to see if I can give
one of us a clue to what is going on. Thanks in advance.
If you manually upload a .REP packet using a terminal (e.g. Telnet) client, you should see what the post failure reason (error) is. Or the hub can check his logs.
you are setting all the qwk conference numbers up for your uplink correctly? that could be the ONLY thing I could think it would be, would be nice to have the other systems log snippet of the transfer.. he's probably getting your messages and getting log messages lije:
qwk conf: 4242 invalid.. or however it states it...
Well, I discovered one issue with not receiving some Dove-Net posts/replies ... somehow one of your IP addresses (vert to be specific) ended up in ip.can, so none of those messages were be imported ... I discovered it by logging onto vert and resetting the pointers and watching the import ... 137 messages in all were imported once I deleted your IP from ip.can :-/
Hopefully the corrupt message ID's I have been experiencing are resolved
Sorry, DM, I didn't realize vert was blocked (TOO MANY FAILED LOGIN ATTEMPTS)
Re: QWK
By: Mortifis to Digital Man on Thu Aug 08 2019 09:34 am
Well, I discovered one issue with not receiving some Dove-Net posts/replies ... somehow one of your IP addresses (vert to be specific) ended up in ip.can, so none of those messages were be imported ... I discovered it by logging onto vert and resetting the pointers and watching the import ... 137 messages in all were imported once I deleted your IP from ip.can :-/
Hopefully the corrupt message ID's I have been experiencing are resolved
Sorry, DM, I didn't realize vert was blocked (TOO MANY FAILED LOGIN ATTEMPTS)
That's interesting. Other than the daily sbbslist verification, I can't think of any reason why my system would be trying to connect to yours over TCP. Do have a log of these failed login attempts?
digital man
Re: QWK
By: Mortifis to Digital Man on Thu Aug 08 2019 09:34 am
Well, I discovered one issue with not receiving some Dove-Net posts/replies ... somehow one of your IP addresses (vert to be specific) ended up in ip.can, so none of those messages were be imported ... I discovered it by logging onto vert and resetting the pointers and watching the import ... 137 messages in all were imported once I deleted your IP from ip.can :-/
Hopefully the corrupt message ID's I have been experiencing are resolved
Sorry, DM, I didn't realize vert was blocked (TOO MANY FAILED LOGIN ATTEMPTS)
That's interesting. Other than the daily sbbslist verification, I can't think of any reason why my system would be trying to connect to yours over TCP. Do have a log of these failed login attempts?
Other than that entry in ip.can (I deleted the entry before I noted the date/time) I do not see your IP address in any data/logs/ file ... odd indeed
Other than that entry in ip.can (I deleted the entry before I noted the date/time) I do not see your IP address in any data/logs/ file ... odd indeed
Not in data/hack.log?
Anything address auto-added to ip.can should be reflected in hack.log. I'm pretty sure.
digital man
Other than that entry in ip.can (I deleted the entry before I noted the date/time) I do not see your IP address in any data/logs/ file ... odd indeed
Not in data/hack.log?
Anything address auto-added to ip.can should be reflected in hack.log. I'm pretty sure.
digital man
I'm sure you are pretty sure; since you are SBBS :-) ... so I found this single entry:
SUSPECTED NNTP LOGIN HACK ATTEMPT for user 'guest' on Mon Jul 15 2019 04:31 am Using port 60864 at <no name> [71.95.196.34]
Details: 3.7042561
Odd, since I do not believe I even have NNTP(s) enabled or the ports forwarded .. I will investigate further ... that seems about the time I created a GUEST account ... no worries ... you can hack my system any time you feel inclined, (please do), since you'd only improve it :-P
Re: Re: QWK
By: Mortifis to Digital Man on Thu Aug 08 2019 08:14 pm
Other than that entry in ip.can (I deleted the entry before I noted the date/time) I do not see your IP address in any data/logs/ file ... odd indeed
Not in data/hack.log?
Anything address auto-added to ip.can should be reflected in hack.log. I'm pretty sure.
digital man
I'm sure you are pretty sure; since you are SBBS :-) ... so I found this single entry:
SUSPECTED NNTP LOGIN HACK ATTEMPT for user 'guest' on Mon Jul 15 2019 04:31 am Using port 60864 at <no name> [71.95.196.34]
Details: 3.7042561
Odd, since I do not believe I even have NNTP(s) enabled or the ports forwarded .. I will investigate further ... that seems about the time I created a GUEST account ... no worries ... you can hack my system any time you feel inclined, (please do), since you'd only improve it :-P
That is pretty weird. Of course, *I* didn't try to login to your system via NNTP. We do have the nightly sbbslist verifications, but that's just a TCP connection (no login attempt). So I have no idea about that just yet.
What do you have your LoginAttemptHackThreshold set to in your sbbs.ini file?
Do you have a Guest account on your system?
That is pretty weird. Of course, *I* didn't try to login to your system via NNTP. We do have the nightly sbbslist verifications, but that's just a TCP connection (no login attempt). So I have no idea about that just yet.
What do you have your LoginAttemptHackThreshold set to in your sbbs.ini file?
Do you have a Guest account on your system?
So... I guessing you either don't have a Guest account or you have a Guest account with a (non-blank) password.
And there was a bug, but that's now
fixed. So it shouldn't happen again even if you don't change anything (but do update to the latest and greatest dev build).
digital man
That is pretty weird. Of course, *I* didn't try to login to your system via NNTP. We do have the nightly sbbslist verifications, but that's just a TCP connection (no login attempt). So I have no idea about that just yet.
What do you have your LoginAttemptHackThreshold set to in your sbbs.ini file?
... LoginAttempthackThreshold = 3
... AttemptDelay = 5000
... Throttle = 1000
... Filter = 3
... Ban 6000
... Duration - 1D
Do you have a Guest account on your system?
Yes, After 25 years or so, I do have a Guest account now, as of last month ... huh, was my lame u-dev method the culprit? :-P
So... I guessing you either don't have a Guest account or you have a Guest account with a (non-blank) password.
... NO IT IS BLANK!
And there was a bug, but that's now
fixed. So it shouldn't happen again even if you don't change anything (but do update to the latest and greatest dev build).
.. as always, I need to keep up with a full dev-update and not a half-assed one like I usually do :-P ... thank you DM ... keep me on my toes :-)
Wow, that's pretty harsh: 3 failed password attempts and you permantly ban a user's IP addrss!
Your TempBanThreshold is 6000? That seems.... oddly high.
If you directly copy/pasted from the sbbs.ini file, I might get a more accurate view of your configuration settings.
Wow, that's pretty harsh: 3 failed password attempts and you permantly ban a user's IP addrss!
Your TempBanThreshold is 6000? That seems.... oddly high.
LOL I suppose it is :-P I set that to 3 after watching the same ip addresses the stock 10 attempts since if it was a real user they'd see the prompt "Did you forget your password?"
If you directly copy/pasted from the sbbs.ini file, I might get a more accurate view of your configuration settings.
; Failed login-attempt tracking, throttling, logging, and filtering:
LoginAttemptDelay = 5000
LoginAttemptThrottle = 1000
LoginAttemptHackThreshold = 3 (I changed it to 10)
LoginAttemptFilterThreshold = 3 (I changed it to 10)
LoginAttemptTempBanThreshold = 6000 (I changed it to 20)
LoginAttemptTempBanDuration = 1D (Might change it to 1Y :)
OutgoingV4=0.0.0.0
OutgoingV6=::
OutboundInterface = 0.0.0.0
OutboundV6Interface = ::
And, yes, I am not sure how LoginAttemptTempBanThreshold ended up being 6000 instead of the typical 20 :-?
I'll do a full, proper, update this weekend, Thank you DM
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495935:21:54 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,933 |