I have an IP that is known to me, which BFM produces alerts about on two DA servers.
Using the "IP Info" on one server results in a time out message:
Using "IP Info" for any other listed IP showing in BFM "Failed Login" or "Blocked IP" lists has always been fine... Just this one IP, so far.
The other DA server has no trouble showing "IP Info" for the same IP, or any other IPs queried.
I've scoured the logs and find traces of the time out but that is all. Debug mode 'b2000' level seems to just mirror of the info shown within DA:
Confused about this one..
- works in shell (same dig cmd)
- works for all other IP tried in DA
- doesn't work in DA for this IP
It's the fact it's so strange that bothers me. I could live without this "IP Info" working.
The proper/normal communication between the foreign IP and the DA server is fine -- the alerts are simply the byproduct of me changing the password on the DA machine and not updating the foreign IP (server) with the new password yet.
Using the "IP Info" on one server results in a time out message:
Using the same command (dig -x xx.xx.xx.xx +noshort) that DA uses, in the server's shell works fine.
Using "IP Info" for any other listed IP showing in BFM "Failed Login" or "Blocked IP" lists has always been fine... Just this one IP, so far.
The other DA server has no trouble showing "IP Info" for the same IP, or any other IPs queried.
I've scoured the logs and find traces of the time out but that is all. Debug mode 'b2000' level seems to just mirror of the info shown within DA:
Code:
Command::doCommand(/CMD_BRUTE_FORCE_MONITOR)
Dynamic(api=0, error=0):
text='Your connection has timed out'
result='Either your request was invalid or the program hasn't completed your request.<br>
Please notify the server admin'
Sockets::handshake - begin
Sockets::handshake - end- works in shell (same dig cmd)
- works for all other IP tried in DA
- doesn't work in DA for this IP
It's the fact it's so strange that bothers me. I could live without this "IP Info" working.
The proper/normal communication between the foreign IP and the DA server is fine -- the alerts are simply the byproduct of me changing the password on the DA machine and not updating the foreign IP (server) with the new password yet.