When I try to connect to a particular "Mystic/1.12A34 binkp/1.0" system, all I get is this:
+ 24 Jun 20:57:40 [30502] call to ***
24 Jun 20:57:40 [30502] trying ***...
24 Jun 20:57:40 [30502] connected
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
Is this a known problem maybe? Or what could it be?
When I try to connect to a particular "Mystic/1.12A34 binkp/1.0"
system, all I get is this:
+ 24 Jun 20:57:40 [30502] call to ***
24 Jun 20:57:40 [30502] trying ***...
24 Jun 20:57:40 [30502] connected
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
+ 24 Jun 20:57:41 [30502] done (to ***, failed, S/R: 0/0 (0/0 bytes))
24 Jun 20:57:41 [30502] session closed, quitting...
Is this a known problem maybe? Or what could it be?
When he polls mine it seems to work...
When I try to connect to a particular "Mystic/1.12A34 binkp/1.0"
system, all I get is this:
+ 24 Jun 20:57:40 [30502] call to ***
24 Jun 20:57:40 [30502] trying ***...
24 Jun 20:57:40 [30502] connected
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
Is this a known problem maybe? Or what could it be?
There aren't any known issues with Mystic's BINKP at the moment.
Are you able to get a log from that system from the Mystic side to see
if it reports an error on its side?
What software are you using? I know there is some issue with someone
I know who has a BBBS system where his system keeps polling Mystic
over and over (but Mystic connecting to him works fine).
Hi All,
When I try to connect to a particular "Mystic/1.12A34 binkp/1.0" system, all I get is this:
+ 24 Jun 20:57:40 [30502] call to ***
24 Jun 20:57:40 [30502] trying ***...
24 Jun 20:57:40 [30502] connected
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
+ 24 Jun 20:57:41 [30502] done (to ***, failed, S/R: 0/0 (0/0 bytes))
24 Jun 20:57:41 [30502] session closed, quitting...
Is this a known problem maybe? Or what could it be?
When he polls mine it seems to work...
When I try to connect to a particular "Mystic/1.12A34 binkp/1.0" system, all I get is this:
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
+ 24 Jun 20:57:41 [30502] done (to ***, failed, S/R: 0/0 (0/0 bytes))
24 Jun 20:57:41 [30502] session closed, quitting...
Check with the admin that your IP address has not ended up in badip.txt
in the data dir of Mystic. If it has he should remove it and restart his MIS.
i have binkd... in my case, the destination has "require secure
session" enabled which is blocking general netmails from any system to connect to their's...
i have binkd... in my case, the destination has "require secure
session" enabled which is blocking general netmails from any system
to connect to their's...
Almost sounds like they have CRAM-MD5 enabled in the binkp server,
rather than on a per-link basis.
Almost sounds like they have CRAM-MD5 enabled in the binkp
server, rather than on a per-link basis.
yeah, i forget what the setting is but it is set and no one can
connect to them unless they already have a session set up... i
understand the setting but it kinda puts the cart before the horse as
when things change while an operator is sleeping (eg: a net host goes away), there's no way for others to drop them a netmail and let them
know since they're blocking everyone by default...
When I try to connect to a particular "Mystic/1.12A34 binkp/1.0"
system, all I get is this:
+ 24 Jun 20:57:40 [30502] call to ***
24 Jun 20:57:40 [30502] trying ***...
24 Jun 20:57:40 [30502] connected
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
+ 24 Jun 20:57:41 [30502] done (to ***, failed, S/R: 0/0 (0/0 bytes))
24 Jun 20:57:41 [30502] session closed, quitting...
Is this a known problem maybe? Or what could it be?
When he polls mine it seems to work...
Check with the admin that your IP address has not ended up in badip.txt in the data dir of Mystic. If it has he should remove it and restart his MIS.
If you are on a static IP let him know what it is and get him to add
it to goodip.txt in the mystic data dir.. he may need to create the
txt file from scratch.
When I try to connect to a particular "Mystic/1.12A34 binkp/1.0"
system, all I get is this:
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
+ 24 Jun 20:57:41 [30502] done (to ***, failed, S/R: 0/0 (0/0 bytes))
24 Jun 20:57:41 [30502] session closed, quitting...
Is there any chance your IP is listed in their badip list? I've had that happen here when someone couldn't connect with me.
Do you still get a tcp/ip connection when that's the case? See the "connected" above, and the 1 second delay before the "connection
reset"...
IPDo you still get a tcp/ip connection when that's the case? See the
"connected" above, and the 1 second delay before the "connection
reset"...
Yes, it would still connect that is the only way it can get the incoming
to check it against the database of bad IP addresses. So when a blockedIP
tries to connect, they'll connect successfully then get a "BLOCKED"printed
to the client before disconnecting shortly after.
which mystic system? i've seen netmail from you jambed up because the destination has the "require secure session" setting enabled... i've contacted that NC about said netmail but haven't heard anything backyet...
Hi All,
When I try to connect to a particular "Mystic/1.12A34 binkp/1.0" system, all I >get is this:
+ 24 Jun 20:57:40 [30502] call to ***
24 Jun 20:57:40 [30502] trying ***...
24 Jun 20:57:40 [30502] connected
+ 24 Jun 20:57:40 [30502] outgoing session with ***
? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
+ 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
+ 24 Jun 20:57:41 [30502] done (to ***, failed, S/R: 0/0 (0/0 bytes))
24 Jun 20:57:41 [30502] session closed, quitting...
Is this a known problem maybe? Or what could it be?
When he polls mine it seems to work...
Bye, Wilfred.
--- FMail-lnx64 2.1.0.12-B20170618
* Origin: FMail development HQ (2:280/464)
That doesn't show in the binkd log file. Maybe it's possible to change that so a more meaning full message appears in the binkd log file of the system that's trying to connect?
Anyway, he had the Netherlands blocked in his badcountry.txt. Once that was removed the connection worked... :-/ ;)
That looks like something is causing you to not connect. Your welcome
to contact me and get a connection too LinuxNode which is latest
mystic serving Fido. We can get it figure out.
Message me if you want to test.
That doesn't show in the binkd log file. Maybe it's possible to
change that so a more meaning full message appears in the binkd log
file of the system that's trying to connect?
Maybe, but I think that would be up to binkd to do so.
which mystic system? i've seen netmail from you jambed up because the
destination has the "require secure session" setting enabled... i've
contacted that NC about said netmail but haven't heard anything back
yet...
That was a different system I had issues with connecting directly. ;)
Thanks for getting involved to fix this!
Thanks for getting involved to fix this!
still waiting on word back... hopefully the operator will wake up soon...
sad that there aren't any netmail zonegates for his other networks so
that one could send netmail through them to his system... zonegates
were a GoodThing<tm>... granted, they were used for fidonet zones in
the beginning but the concept works and worked great for othernets,
too... sure, some of them may not want contact from "fidonet" but
we're only talking about netmail here, not echos... route or deliver direct to the zonegate and let them handle delivery on the other side based on their network ops... it is crazy to have to join an othernet
just to be able to let someone know of a problem on their system...
that's playing othernet roulette just trying to find one that they may
be active on...
That doesn't show in the binkd log file. Maybe it's possible to
change that so a more meaning full message appears in the binkd
log file of the system that's trying to connect?
Maybe, but I think that would be up to binkd to do so.
Maybe, but I think that would be up to binkd to do so.
Binkd only knows the binkp protocol. The "blocked" message is outside
that protocol, so just garbage to it, which is ignored. (I suspect)
I think what he was trying to say, was that he was not notified by
Mystic of being blocked in his connection logs, and you originally said it's supposed to do so.
Are you saying on the Mystic side? He's not using Mystic.
Why would binkd say anything about being blocked? Its not the one
doing the blocking.
Thanks for getting involved to fix this!
still waiting on word back... hopefully the operator will wake up
soon...
Are we talking about 1:123/0 here?
sad that there aren't any netmail zonegates for his other networks so
that one could send netmail through them to his system... zonegates
were a GoodThing<tm>... granted, they were used for fidonet zones in
the beginning but the concept works and worked great for othernets,
too... sure, some of them may not want contact from "fidonet" but
we're only talking about netmail here, not echos... route or deliver
direct to the zonegate and let them handle delivery on the other side
based on their network ops... it is crazy to have to join an othernet
just to be able to let someone know of a problem on their system...
that's playing othernet roulette just trying to find one that they
may be active on...
I don't see how that would have helped here. I couldn't deliver crash
mail to this node (as a node of either net), because he disabled
unsecure sessions. So I tried a routed netmail in fidonet, guessing he would have a secure connection setup with his Host.
If your IP is blocked the connection is dropped when you try to
connect. The way that binkd logs that is not up to me; I'm not sure
there is anything I could do other than to not block it when its
blocked.
I think what he was trying to say, was that he was not notified by
Mystic of being blocked in his connection logs, and you originally
said it's supposed to do so.
Are you saying on the Mystic side? He's not using Mystic.
Why would binkd say anything about being blocked? Its not the one
doing the blocking.
here's an idea... add some intelligence so that mystic might see if there' mailer calling... if there is, then send a custom netmail reply telling th they are blocked... if it isn't a mailer, then just block... this should b easy to do and blocks could even be set to be limited by port instead of j the originating address... let's see what port they are connection to and block or not... MMS! make mystic smarter! :) O:) :)
developer,Binkd only knows the binkp protocol. The "blocked" message is outside
that protocol, so just garbage to it, which is ignored. (I suspect)
Yep I am well aware of that. But I thought you asked about changing it so a meaningful message appears in the BINKD log. I am not a binkd
so I can't change the way it logs anything! :)
If your IP is blocked the connection is dropped when you try to connect.
The way that binkd logs that is not up to me; I'm not sure there is anything I could do other than to not block it when its blocked.
still waiting on word back... hopefully the operator will wake up
soon...
Are we talking about 1:123/0 here?
no... /10... i just polled and got the same "rerror: unsecured session not allowed" response... the clock is ticking ;)
sad that there aren't any netmail zonegates for his other networks so
that one could send netmail through them to his system... zonegates were
a GoodThing<tm>... granted, they were used for fidonet zones in the beginning but the concept works and worked great for othernets, too... sure, some of them may not want contact from "fidonet" but we're only talking about netmail here, not echos... route or deliver direct to the zonegate and let them handle delivery on the other side based on their network ops... it is crazy to have to join an othernet just to be able
to let someone know of a problem on their system... that's playing othernet roulette just trying to find one that they may be active on...
still waiting on word back... hopefully the operator will wake up
soon...
Are we talking about 1:123/0 here?
no... /10... i just polled and got the same "rerror: unsecured
session not allowed" response... the clock is ticking ;)
I meant Ed was involved in fixing this.
But I have established email contact with /10, so I could ask him to contact Ed to resolve this?
sad that there aren't any netmail zonegates for his other networks so
that one could send netmail through them to his system... zonegates
were a GoodThing<tm>... granted, they were used for fidonet zones in
the beginning but the concept works and worked great for othernets,
too... sure, some of them may not want contact from "fidonet" but
we're only talking about netmail here, not echos... route or deliver
direct to the zonegate and let them handle delivery on the other side
based on their network ops... it is crazy to have to join an othernet
just to be able to let someone know of a problem on their system...
that's playing othernet roulette just trying to find one that they
may be active on...
Where do I find the software to run this? Sounds like an interesting
thing to do for netmail between Zone 21 and others.
If Mystic is sending the text, shouldn't binkd log it? I mean, unless
Or is this something only visable on the Mystic side?
here's an idea... add some intelligence so that mystic might see if there's a mailer calling... if there is, then send a custom netmail
theI meant Ed was involved in fixing this.
yeah but i'm not sure what "this" is... are you talking about resolving
"rerror: Unsecured session not allowed" problem? if so, /10 can do that themselves without ed needing to tell him about it... since you have email contact with /10, you can let them know ;) then once /10 turns that option off, direct and routed netmail can be delivered there and his NC can contact him if/when necessary...
it is especially bad if it stays turned on and his NC cannot contact him... i would expect that the node would be removed from the nodelist after some time of the NC being unable to contact them and this not
being resolved... tick tock tick tock tick tock...
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495933:06:17 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,910 |