Is there an option in mystic to show more of the binkp output to the
log so we can better trouble shoot this? I suspect he is never
reaching the binkd on my end but cannot really tell from this output level.
On linux I can do "telnet capitolcityonline.net 24554" and that is how I see >the Connection closed message. I get the same on port 23 although I don't know >if you have a BBS on port 23.
I have asked him to try connecting to the bbs to see what happens.
You should be getting an answer on port 23. What is your IPA, so that
I can check the bad ip lists and make sure it is not there.
While you are at it, could you also try port 7636, which is a
different machine running magicka, or port 27, also a different
machine?
I have checked my router and all filtering is turned off, which has me
a little worried about why you cannot get through.
I have asked him to try connecting to the bbs to see what happens.
You should be getting an answer on port 23. What is your IPA, so that
I can check the bad ip lists and make sure it is not there.
Good evening,
I have a new FTN node that is trying to connect with my system using mystic. When he attempts to poll here, he is getting the following log output on his end. On my end, I do not see any suggestion that there was ever a binkd connection to be lost.
Is there an option in mystic to show more of the binkp output to the log so we can better trouble shoot this? I suspect he is never reaching the binkd on my end but cannot really tell from this output level.
Yes, those two work fine. On port 7636 I got your MagickaBBS login and I was >able to connect on port 27 also.
Something seems to be blocking me (and probably your link) on your port 23 and >24554 although I don't know what.
Something seems to be blocking me (and probably your link) on your port 23 an >> 24554 although I don't know what.
I wonder what. I have sent my *.can files to DM via email to see if he
maybe sees something I do not. I do have several blocks in the
ip-silent.can file, but neither of you would appear to be covered by any of them.
From what I can tell, the machine has no active firewall running. ubuntu
did install one, but running it with the 'status' option shows that it is
not running.
That's really curious. I think if it was Synchronet blocking access it would log the activity an IP affected.
I am not sure it would if it was on the ip-silent.can file. It might.
I have binkd installed on this system. I did think about firing it up on a different port to see what happens.
Hello Dumas,
I have asked him to try connecting to the bbs to see what happens. You should be getting an answer on port 23. What is your IPA, so tha I can check the bad ip lists and make sure it is not there.
When I try to connect with nodespy on port 23 an info window pops up
that says "Connection terminated".
While you are at it, could you also try port 7636, which is a different machine running magicka, or port 27, also a different machine?
Yes, those two work fine. On port 7636 I got your MagickaBBS login and I was able to connect on port 27 also.
I have checked my router and all filtering is turned off, which has m a little worried about why you cannot get through.
Something seems to be blocking me (and probably your link) on your port
23 and 24554 although I don't know what.
Ttyl :-),
Al
g00r00 recently added some logging options to later pre-alpha builds of 1.12 A46 such that you can set 'verbose' logging output for mis and mis poll
Yes, those two work fine. On port 7636 I got your MagickaBBS login and I >able to connect on port 27 also.
So could my link, so that rules out the router, isp, and modem.
Something seems to be blocking me (and probably your link) on your port 2 >24554 although I don't know what.
I wonder what. I have sent my *.can files to DM via email to see if he maybe sees something I do not. I do have several blocks in the ip-silent.can file, but neither of you would appear to be covered by any of them.
From what I can tell, the machine has no active firewall running. ubuntu did install one, but running it with the 'status' option shows that it is not running.
* SLMR 2.1a * Bless our young they will inherit our national dept.
--- SBBSecho 3.10-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)
Yep, I am the link that is being blocked. Sounds like there is more
than one of us in the same boat.
When I try to telnet in from my home system to either port 23 or to
port 24554, it is an immediate disconnect. At work with a different
IP, no issue.
@MSGID: <5E8530C7.6855.fsx_bbs@capitolcityonline.net>
@REPLY: <5E8512F4.6849.fsx_bbs@capitolcityonline.net>
I am not sure it would if it was on the ip-silent.can file. It might.
I have binkd installed on this system. I did think about firing it up on a different port to see what happens.
If you do put binkd online let me know the port and I'll give it a try.
If you do put binkd online let me know the port and I'll give it a
try.
24553. Thanks!!!!
24553. Thanks!!!!
24553. Thanks!!!!
Yep, a mailer poll on port 24554 fails and a poll on 24553 succeeds.
You might have to talk to DM about that.. :)
nmap -p- 67.131.57.133
nmap -p- 67.131.57.133
DM has suggested switching the ports on your BinkIT and Binkd mailers tosee
what changes.
If you can do that I'll poll and see what happens.
Let me know what ports to test.
Actually, I have temporarily removed the filter files. You might try
port 23 again and see what happens. On the basis of your nmap output
it sure looks like it is open to you now!
If that does not work, try port 2022. I am using a non-standard SSH
port so maybe it won't be blocked if the block is outside my network.
I would prefer not to try switching the binkit ports as it might fool
my connections. I will try it if all else fails, though, but I think
2022 might be a similar test as it is not standard.
If that does not work, try port 2022. I am using a non-standard SSH port so maybe it won't be blocked if the block is outside my network.
It looks good now. I can connect with my mailer on 24554 and all the other ports as well with telnet.
Looks like clear skies and gentle breezes now.
Looks like clear skies and gentle breezes now.
Yes, thank you so much for your assistance!
I wonder, though, what was in my ip-silent.can file that had you
blocked. I went over and over it and none of the IP ranges started
with 104, and none of the ones that were close should have included
yours. DM also looked at it and did not think there was anything
wrong.
I personally think I probably had one of the wildcards set wrong! :O
There must be an answer there somewhere but just what I'm still not
sure.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,044 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 00:11:05 |
| Calls: | 500,299 |
| Calls today: | 17 |
| Files: | 95,203 |
| D/L today: |
2,557 files (611M bytes) |
| Messages: | 465,277 |
| Posted today: | 12 |