Hello Vincent!
I continue to try and send my echo updates, but there is no connection
to your system. This has been going on now for over 2 weeks.
Here's a line from today's binkd log:
=== Cut ===
? 06 Mar 10:15:39 [5323] connection to 2:25/21@fidonet failed:
Connection timed out
=== Cut ===
--
Sincerely,
Marc Lewis
Hello Marc!
06 Mar 26 11:17, you wrote to me:
Please try and use 2:250/1 as the address and advise of experience.
May be I need to change the port address.
Hello Vincent!
06 Mar 26 18:36, you wrote to me:
Hello Marc!
06 Mar 26 11:17, you wrote to me:
Please try and use 2:250/1 as the address and advise of
experience.
May be I need to change the port address.
What do I utilise as the system IP address?
Marc Lewis
Hello Vincent!
06 Mar 26 18:36, you wrote to me:In the meanwhile I have now changed the port used from 24555 to the default of 24554 - JIC (Just in Case) which should be in the DAILY nodelists as of Saturday.
The url is the same if you do not use a nodelist.
Hello Vincent!
08 Mar 26 15:22, you wrote to me:
Hello Vincent!
06 Mar 26 18:36, you wrote to me:
In the meanwhile I have now changed the port used from 24555 to
the default of 24554 - JIC (Just in Case) which should be in the
DAILY nodelists as of Saturday.
The url is the same if you do not use a nodelist.
Very well, I have re-sent all my updates to the 2:250/1 address... One
of the batches of updates were inadvertently sent to port 24555 which
I corrected and resent them to the appropriate port (24554).
Hello Vincent!
08 Mar 26 15:22, you wrote to me:
Hello Vincent!
06 Mar 26 18:36, you wrote to me:
In the meanwhile I have now changed the port used from 24555 to
the default of 24554 - JIC (Just in Case) which should be in the
DAILY nodelists as of Saturday.
The url is the same if you do not use a nodelist.
Very well, I have re-sent all my updates to the 2:250/1 address...
One of the batches of updates were inadvertently sent to port 24555
which I corrected and resent them to the appropriate port (24554).
Did you send it using your Fido address as I do not see any such files
received and acted upon.
Well, it seems that 2:250/1 may be either off-line or is simply not answering:
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
? 12 Mar 11:48:13 [223] connection to 2:250/1@fidonet failed: Connection timed
out. -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
Well, it seems that 2:250/1 may be either off-line or is simply
not
answering:
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
? 12 Mar 11:48:13 [223] connection to 2:250/1@fidonet failed:
Connection timed out. -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
I can reach it with no problem. So there seems to be some (firewall) blocking going on somewhere between your systems.
So lets start with some of the basics to resolve this.
How does applewoodbbs.linkpc.net resolve to an IPv4 address on your system? This is what I get:
# host applewoodbbs.linkpc.net
applewoodbbs.linkpc.net has address 82.30.228.158
Unfortunately Vince's system can not be pinged, but 82.30.228.1 in the same sub-net can be. So you can try to ping that system to test if
there is some kind of geo blocking going on.
And can you open http://applewoodbbs.linkpc.net/ in your webbrowser
(from your fidosystem)? You should get the home webpage from Vince's system...
[snip]I can reach it with no problem. So there seems to be some
(firewall) blocking going on somewhere between your systems.
So lets start with some of the basics to resolve this.
How does applewoodbbs.linkpc.net resolve to an IPv4 address on
your system? This is what I get:
# host applewoodbbs.linkpc.net
applewoodbbs.linkpc.net has address 82.30.228.158
Here is what my ping returns:
PING applewoodbbs.linkpc.net: 56 data bytes
64 bytes from 172.235.136.206: icmp_seq=0. time=30. ms
And can you open http://applewoodbbs.linkpc.net/ in your
webbrowser (from your fidosystem)? You should get the home
webpage from Vince's system...
That's going to take a bit of doing as under OS/2 my Firefox for OS/2
is very dated. I do have a Windows machine on the same network; I can
try it from there.
# host applewoodbbs.linkpc.net
applewoodbbs.linkpc.net has address 82.30.228.158
Here is what my ping returns:
PING applewoodbbs.linkpc.net: 56 data bytes
64 bytes from 172.235.136.206: icmp_seq=0. time=30. ms
And can you open http://applewoodbbs.linkpc.net/ in your webbrowser
(from your fidosystem)? You should get the home webpage from Vince's
system...
That's going to take a bit of doing as under OS/2 my Firefox for OS/2 is very
dated. I do have a Windows machine on the same network; I can try it from there.
On 2026-03-12 13:03:24, you wrote to me:
# host applewoodbbs.linkpc.net
applewoodbbs.linkpc.net has address 82.30.228.158
Here is what my ping returns:
PING applewoodbbs.linkpc.net: 56 data bytes
64 bytes from 172.235.136.206: icmp_seq=0. time=30. ms
That is the wrong IPv4 address! And probably the cause of your
connection problems. So the dns resolving on your fido machine seems broken somehow.
And can you open http://applewoodbbs.linkpc.net/ in your
webbrowser (from your fidosystem)? You should get the home
webpage from Vince's system...
That's going to take a bit of doing as under OS/2 my Firefox for
OS/2 is very dated. I do have a Windows machine on the same
network; I can try it from there.
Please do! And also show us the nslookup (or ping) from that machine
to applewoodbbs.linkpc.net.
Hello Wilfred!
12 Mar 26 19:25, you wrote to me:
On 2026-03-12 13:03:24, you wrote to me:
# host applewoodbbs.linkpc.net
applewoodbbs.linkpc.net has address 82.30.228.158
Here is what my ping returns:
PING applewoodbbs.linkpc.net: 56 data bytes
64 bytes from 172.235.136.206: icmp_seq=0. time=30. ms
That is the wrong IPv4 address! And probably the cause of your
connection problems. So the dns resolving on your fido machine
seems broken somehow.
And can you open http://applewoodbbs.linkpc.net/ in your
webbrowser (from your fidosystem)? You should get the home
webpage from Vince's system...
That's going to take a bit of doing as under OS/2 my Firefox for
OS/2 is very dated. I do have a Windows machine on the same
network; I can try it from there.
Please do! And also show us the nslookup (or ping) from that
machine to applewoodbbs.linkpc.net.
I was able to use Firefox on my Windows machine to reach it
successfully.
I have altered my binkd NODES.CFG to directly connect 2:250/1 to 82.30.228.158... Let's see how that goes.
# host applewoodbbs.linkpc.net
applewoodbbs.linkpc.net has address 82.30.228.158
Here is what my ping returns:
PING applewoodbbs.linkpc.net: 56 data bytes
64 bytes from 172.235.136.206: icmp_seq=0. time=30. ms
I was able to use Firefox on my Windows machine to reach it
successfully.
I have altered my binkd NODES.CFG to directly connect 2:250/1 to 82.30.228.158... Let's see how that goes.
# host applewoodbbs.linkpc.net
applewoodbbs.linkpc.net has address 82.30.228.158
Here is what my ping returns:
PING applewoodbbs.linkpc.net: 56 data bytes
64 bytes from 172.235.136.206: icmp_seq=0. time=30. ms
I have altered my binkd NODES.CFG to directly connect 2:250/1 to
82.30.228.158... Let's see how that goes.
Can you use the nodelist with Binkd ?
Hello Marc![snip]
12 Mar 26 18:17, you wrote to Wilfred van Velzen:
Hello Wilfred!
12 Mar 26 19:25, you wrote to me:
I was able to use Firefox on my Windows machine to reach it
successfully.
I have altered my binkd NODES.CFG to directly connect 2:250/1 to
82.30.228.158... Let's see how that goes.
Can you use the nodelist with Binkd ?
@REPLY: 2:250/1@fidonet 69b34f75I have located the issue with the odd-ball IP address. I have altered the actual routing in that machine's (OS/2) IP system where it routes
@MSGID: 1:396/45 69b38b72
@CHRS: CP437 2
@TZUTC: -0600
Hello Vincent!
12 Mar 26 23:42, you wrote to me:
Hello Marc!
12 Mar 26 18:17, you wrote to Wilfred van Velzen:
[snip]Hello Wilfred!
12 Mar 26 19:25, you wrote to me:
I was able to use Firefox on my Windows machine to reach it
successfully.
I have altered my binkd NODES.CFG to directly connect 2:250/1 to
82.30.228.158... Let's see how that goes.
Can you use the nodelist with Binkd ?
No, it strictly utilses the NODES.CFG file:
node 2:250/1@fidonet 82.30.228.158
I have located the issue with the odd-ball IP address. I have altered
the actual routing in that machine's (OS/2) IP system where it routes applewoodbbs.linkpc.net directly to 82.30.228.158.
Hi Marc,
On 2026-03-13 11:18:32, you wrote to you:
I have located the issue with the odd-ball IP address. I have
altered the actual routing in that machine's (OS/2) IP system
where it routes applewoodbbs.linkpc.net directly to
82.30.228.158.
And does that keep working if Vince for some reason changes the IP
address that applewoodbbs.linkpc.net resolves to?
As the problem has been resolved to be not related to my systems I
will (when get around to it) return the post address back - However as there is only one system being utilised for both addresses there does
not appear to be a rush if at all.
I.e., Leaving it as is - it was set up to use a Pi3B+ as the Elist
system that run mbse, Elist software that was only routed to 250/1 for
all traffic other than delivery of submission files.
The idea was to pass on the system to another node, hopefully a lot younger
than me (79 in June) so that if I become ill or worse the service will continue but no one came forwards - typical users et al.
| Sysop: | Dave Parker |
|---|---|
| Location: | Redhill, Surrey |
| Users: | 6 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 355:12:36 |
| Calls: | 51 |
| Files: | 1 |
| D/L today: |
1 files (2K bytes) |
| Messages: | 20,680 |