Vince,
Didn't get these:
Area RAR - RAR: Main dist for releases/public betas ----------------------------------------------------------------------
--- RB64V701.ZIP 726 Kb. RAR 7.01 for FreeBSD x64. RL64V701.ZIP
713 Kb. RAR v7.01 for Linux x64. ROSAM701.ZIP 639 Kb. RAR 7.01 for
macOS (arm). ROSX701.ZIP 712 Kb. RAR 7.01 for macOS (64
bit). URSRC709.ZIP 252 Kb. UNRAR v7.0.9 sources. WR701X64.ZIP
3662 Kb. WinRAR x64 v7.01 Multifunctional
Any reason they haven't come down the pike? I polled your system this morning, no help there.
What gives?? Last version I have here is V700 which I hatched on
April 10. Janis
Didn't get these:
Area RAR - RAR: Main dist for releases/public betas
----------------------------------------------------------------------
--- RB64V701.ZIP 726 Kb. RAR 7.01 for FreeBSD x64. RL64V701.ZIP
713 Kb. RAR v7.01 for Linux x64. ROSAM701.ZIP 639 Kb. RAR 7.01 for
macOS (arm). ROSX701.ZIP 712 Kb. RAR 7.01 for macOS (64
bit). URSRC709.ZIP 252 Kb. UNRAR v7.0.9 sources. WR701X64.ZIP
3662 Kb. WinRAR x64 v7.01 Multifunctional
Any reason they haven't come down the pike? I polled your system this
morning, no help there.
What gives?? Last version I have here is V700 which I hatched on
April 10. Janis
See netmail just sent. but here is the response :
Your system is marked as on Pause when I could not poll yours.
That has not changed as per poll I just tried :
29-Jul-2024 16:00:40 mbcico[2235405] Calling 1:261/38@fidonet (<<PRISM BBS, phone (null))
+ 29-Jul-2024 16:00:40 mbcico[2235405] Open TCP connection to "filegate.net:24554"
+ 29-Jul-2024 16:00:40 mbcico[2235405] Trying IPv4 138.197.57.219 port 24554
There might well be other file / echo areas also on pause as it is a blanket option.
+ 29-Jul-2024 16:00:40 mbcico[2235405] Open TCP connection to
"filegate.net:24554"
+ 29-Jul-2024 16:00:40 mbcico[2235405] Trying IPv4 138.197.57.219 port 24554
You are polling the wrong port, node 1:261/100 lists the correct port, IBN:24555, not the standard binkd port. I can see that I should have my NC update my listing to make it clearer that for node #38 & #100, port 24555
should be used. People who poll me know to poll me on 24555.
You are polling the wrong port, node 1:261/100 lists the correct port, IBN:24555, not the standard binkd port. I can see that I should have
my NC update my listing to make it clearer that for node #38 & #100,
port 24555 should be used. People who poll me know to poll me on
24555.
You are polling the wrong port, node 1:261/100 lists the correct port, IBN:24555, not the standard binkd port. I can see that I should have
my NC update my listing to make it clearer that for node #38 & #100,
port 24555 should be used. People who poll me know to poll me on
24555.
You are polling the wrong port, node 1:261/100 lists the correct
port,
IBN:24555, not the standard binkd port. I can see that I should
have my NC update my listing to make it clearer that for node #38
& #100, port 24555 should be used. People who poll me know to
poll me on 24555.
# callipf -f 1:261/100
Parsing nodelist file /home/fido/nodelist/Z2DAILY.211
Nodelist for Monday, July 29, 2024 -- Day number 211 parsed, 940
IP-nodes processed (0.014 sec) Calling '1:261/100'. Call time:
'0000-2400' UTC. Now is: 2041 UTC. filegate.net, 24555 Calling
1:261/100 (138.197.57.219:24555) error (Connection refused)
29 Jul 24 16:18, you wrote to Vincent Coen:
You are polling the wrong port, node 1:261/100 lists the correct port,
IBN:24555, not the standard binkd port. I can see that I should have
my NC update my listing to make it clearer that for node #38 & #100,
port 24555 should be used. People who poll me know to poll me on
24555.
1. The nodelist is showing that 1:261/38 accepts BinkP on the standard port (24554).
2. I get "Connection refused" from both ports (24554 & 24555)
This situation has been ongoing for months. If your system indeed only accepts connections on 24555, the nodelist entry needs to be corrected ASAP.
In any case, it seems you need to check your firewall, as several people (myself, Vince, and Wilfred to name a few examples) cannot connect to your system.
1. The nodelist is showing that 1:261/38 accepts BinkP on the
standard port (24554).
That's correct. There is a standalone BinkD server/client on 24554,
the standard BinkD port. If you have not been instructed by me to
pick up traffic at filegate.net:24554, there will be no traffic there
for "you". I only use that port for some people.
2. I get "Connection refused" from both ports (24554 & 24555)
This situation has been ongoing for months. If your system indeed
only accepts connections on 24555, the nodelist entry needs to be
corrected ASAP.
I'll try to get to it ASAP.
In any case, it seems you need to check your firewall, as several
people (myself, Vince, and Wilfred to name a few examples) cannot
connect to your system.
There is a problem, yes. I will get to it as soon as I can.
Meanwhile, as I believe I've mentioned, those that pick up here do
connect to those ports.
Sorry for inconveniences I may have caused.
1. The nodelist is showing that 1:261/38 accepts BinkP on the
standard port (24554).
That's correct. There is a standalone BinkD server/client on 24554,
the standard BinkD port. If you have not been instructed by me to
pick up traffic at filegate.net:24554, there will be no traffic there
for "you". I only use that port for some people.
If that port is listed in the nodelist, ALL FidoNet nodes should be able to connect to it to deliver mail.
2. I get "Connection refused" from both ports (24554 & 24555)
This situation has been ongoing for months. If your system indeed
only accepts connections on 24555, the nodelist entry needs to be
corrected ASAP.
I'll try to get to it ASAP.
If those ports are not available to ALL FidoNet nodes, they should not be listed in the FidoNet nodelist.In any case, it seems you need to check your firewall, as several
people (myself, Vince, and Wilfred to name a few examples) cannot
connect to your system.
I would appreciate it if you would respond to the multiple emails I've sent you regarding this.
You are being a bit silly, IMO, Andrew. As I've said, anyone can
connect there. This month has been especially nasty _weatherwise_,
though, and for example my Internet connection was DEAD for almost a
week. No one can help that.. That was caused by my ISP being down,
Point Broadband (right now we are connecting fine however. As 'they'
say, S___ happens :) )
Hi Janis,
On 2024-08-05 16:55:42, you wrote to Andrew Leary:
You are being a bit silly, IMO, Andrew. As I've said, anyone can
connect there. This month has been especially nasty _weatherwise_,
though, and for example my Internet connection was DEAD for almost a
week. No one can help that.. That was caused by my ISP being down,
Point Broadband (right now we are connecting fine however. As 'they'
say, S___ happens :) )
Nope, still nothing:
# callipf -f 1:261/38,1:261/100
Parsing nodelist file /home/fido/nodelist/Z2DAILY.218
Nodelist for Monday, August 5, 2024 -- Day number 218 parsed, 941 IP-nodes processed (0.013 sec)
Calling '1:261/100'. Call time: '0000-2400' UTC.
Now is: 2116 UTC.
filegate.net, 24555
Calling '1:261/38'. Call time: '0000-2400' UTC.
Now is: 2116 UTC.
filegate.net, 24554
Calling 1:261/100 (138.197.57.219:24555)
Calling 1:261/38 (138.197.57.219:24554)
error (Connection refused)
error (Connection refused)
1. The nodelist is showing that 1:261/38 accepts BinkP on the
standard port (24554).
That's correct. There is a standalone BinkD server/client on
24554, the standard BinkD port. If you have not been instructed by
me to pick up traffic at filegate.net:24554, there will be no
traffic there for "you". I only use that port for some people.
If that port is listed in the nodelist, ALL FidoNet nodes should be
able to connect to it to deliver mail.
Of course they can, a number of folks have. I was simply mentioning
the obvious... If I did not tell a node to pick up their traffic at my 24554 binkp port, then there will be no traffic there. It DOESN'T
mean no one can CONNECT there :) :) Most people connect with my bbbs port, 24555.
2. I get "Connection refused" from both ports (24554 & 24555)
This situation has been ongoing for months. If your system indeed
only accepts connections on 24555, the nodelist entry needs to be
corrected ASAP.
I'll try to get to it ASAP.
If those ports are not available to ALL FidoNet nodes, they shouldIn any case, it seems you need to check your firewall, as several
people (myself, Vince, and Wilfred to name a few examples) cannot
connect to your system.
not be listed in the FidoNet nodelist.
You are being a bit silly, IMO, Andrew. As I've said, anyone can
connect there. This month has been especially nasty _weatherwise_,
though, and for example my Internet connection was DEAD for almost a
week. No one can help that.. That was caused by my ISP being down,
Point Broadband (right now we are connecting fine however. As 'they'
say, S___ happens :) )
I would appreciate it if you would respond to the multiple emails
I've sent you regarding this.
You are probably sending email to my OLD email address which was janis@filegate.net. I _closed_ that account quite a _long time ago_,
and have posted my new one here in fidonet! My new email address is jmklou@gmail.com. Dallas Hinton knows this email address, several
others do. Sorry you did not seem to know about it.
So... please change my email address to jmklou@gmail.com.
Calling 1:261/100 (138.197.57.219:24555)
Calling 1:261/38 (138.197.57.219:24554)
error (Connection refused)
error (Connection refused)
Thank you for testing this, Wilfred. I will try to find these connection attempts in my log, perhaps I will see what the problem is.
It is strange that some people have no problem, however.
Try again, Janis... Do you really want me to post the emails that I sent to your gmail.com address, which have received ZERO responses?
So... please change my email address to jmklou@gmail.com.
I haven't used the filegate.net address in quite a while.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 991 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 127:09:42 |
| Calls: | 12,960 |
| Calls today: | 2 |
| Files: | 186,574 |
| Messages: | 3,265,882 |