New Host for net 105: Host,105,Awesome_Net,Portland_Or,Rick_Smith,-Unpublished-,300,CM,IBN:hub.awesomenet.us:24556
Timeout on trying to connect. Which is the same for the regular node of
Rick Smith with a different host name (and IPv4 address).
New Host for net 105:
Host,105,Awesome_Net,Portland_Or,Rick_Smith,-Unpublished-,300,CM,IBN:hu
b.awesomenet.us:24556 Timeout on trying to connect. Which is the same
for the regular node of Rick Smith with a different host name (and IPv4
address).
Awesome!
New Host for net 105:
Host,105,Awesome_Net,Portland_Or,Rick_Smith,-Unpublished-,300,CM,I
BN:hu b.awesomenet.us:24556 Timeout on trying to connect. Which is
the same for the regular node of Rick Smith with a different host
name (and IPv4 address).
Awesome!
;-)
Or maybe not so much...
New Host for net 105:
Host,105,Awesome_Net,Portland_Or,Rick_Smith,-Unpublished-,300,CM,I
BN:hu b.awesomenet.us:24556 Timeout on trying to connect. Which is
the same for the regular node of Rick Smith with a different host
name (and IPv4 address).
Awesome!
;-)
Or maybe not so much...
Awesome, awenone or aweany, I am unable to connect to any of Rick Smith's listed nodes.
Another net with a ghost host. :(
New Host for net 105:
Host,105,Awesome_Net,Portland_Or,Rick_Smith,-Unpublished-,300,CM,I
BN:hu b.awesomenet.us:24556 Timeout on trying to connect. Which is
the same for the regular node of Rick Smith with a different host
name (and IPv4 address).
Awesome!
;-)
Or maybe not so much...
New Host for net 105:
Host,105,Awesome_Net,Portland_Or,Rick_Smith,-Unpublished-,300,CM,I
BN:hu b.awesomenet.us:24556 Timeout on trying to connect. Which is
the same for the regular node of Rick Smith with a different host
name (and IPv4 address).
Awesome!
;-)
Or maybe not so much...
Awesome, awenone or aweany, I am unable to connect to any of Rick
Smith's listed nodes. Another net with a ghost host. :(
Seems to work quite fine from here.
Hello Tommi,
On 2021-09-04 20:43:46, you wrote to Michiel van der Vlist:
New Host for net 105:
Host,105,Awesome_Net,Portland_Or,Rick_Smith,-Unpublished-,300,CM,I
BN:hu b.awesomenet.us:24556 Timeout on trying to connect. Which is
the same for the regular node of Rick Smith with a different host
name (and IPv4 address).
Awesome!
;-)
Or maybe not so much...
Awesome, awenone or aweany, I am unable to connect to any of Rick
Smith's listed nodes. Another net with a ghost host. :(
Seems to work quite fine from here.I just tried it again on is host and node system, but still get a timeout. Maybe he has a rather strict firewall on his system? But I still would call that a misconfiguration, if not every node in fidonet can deliver crash mail to his system...
Regards, NPC.
Seems to work quite fine from here.
Awesome, awenone or aweany, I am unable to connect to any of Rick
Smith's listed nodes. Another net with a ghost host. :(
I am able to connect to 1:105/0 with no issues using the information published in the nodelist.
Perhaps you didn't see the non-standard port?
Are you sure about the port? Just checked again with my phone:
# nmap -Pn -p 24554-24556 hub.awesomenet.us
Starting Nmap 6.47 ( http://nmap.org ) at 2021-09-05 12:56 CEST
Nmap scan report for hub.awesomenet.us (65.102.14.165)
Host is up.
rDNS record for 65.102.14.165: mail.sailorfej.net
PORT STATE SERVICE
24554/tcp filtered binkp
24555/tcp filtered unknown
24556/tcp filtered unknown
Nmap done: 1 IP address (1 host up) scanned in 3.28 seconds
He seems to be blocking the Netherlands. I tried it from 3 different ip's/locations.
# nmap -Pn -p 24554-24556 hub.awesomenet.us
Starting Nmap 6.47 ( http://nmap.org ) at 2021-09-05 12:56 CEST
Nmap scan report for hub.awesomenet.us (65.102.14.165)
Host is up.
rDNS record for 65.102.14.165: mail.sailorfej.net
PORT STATE SERVICE
24554/tcp filtered binkp
24555/tcp filtered unknown
24556/tcp filtered unknown
Nmap done: 1 IP address (1 host up) scanned in 3.28 seconds
From Spain:
nmap -Pn -p 24554-24556 hub.awesomenet.us
Starting Nmap 7.70 ( https://nmap.org ) at 2021-09-06 00:32 CEST
Nmap scan report for hub.awesomenet.us (65.102.14.165)
Host is up (0.17s latency).
PORT STATE SERVICE
24554/tcp closed binkp
24555/tcp closed unknown
24556/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 1.57 seconds
He seems to be blocking the Netherlands. I tried it from 3 different
ip's/locations.
There are country tables available for this. The commercial firewall appliance we use at work has a special configuration page for this.
(This used to be an extra option you would have to buy if you wanted
to use it, but it became free in the last version)
There are country tables available for this. The commercial firewall
appliance we use at work has a special configuration page for this.
(This used to be an extra option you would have to buy if you wanted
to use it, but it became free in the last version)
That is how it should be. So he seems to be blocking just the
Netherlands. Strange!
If you maintain it for a million customers and the updates are
automatic, the cost for each customer is neglectable...
That is how it should be. So he seems to be blocking just the
Netherlands. Strange!
Germany (where my Austrian node runs ;) is not blocked.
Germany (where my Austrian node runs ;) is not blocked.
Apparently we are very dangerous overhere. Nothing but hackers... :-/
Apparently we are very dangerous overhere. Nothing but hackers... :-/
I sent netmail to the sysop of 1:105/0.
I sent netmail to the sysop of 1:105/0.
Crash? :D :D
Apparently we are very dangerous overhere. Nothing but
hackers... :-/
Ok, we'll stay tuned...
Apparently we are very dangerous overhere. Nothing but
hackers... :-/
Ok, we'll stay tuned...
So our suspicions are confirmed. It probably was easiest for him to
block the complete Netherlands instead of just the offending ranges...
So our suspicions are confirmed. It probably was easiest for him to
block the complete Netherlands instead of just the offending
ranges...
Hello Angel,
Btw: How come the subject line is mangled on your reply?
Btw: How come the subject line is mangled on your reply?
Yes, I have seen it but I don't know why it is. I use Golded and when I
give a reply (q) the subject is changed and I don't know why it is.
It has done it again in this message :(.
--- GoldED+/LNX 1.1.5-b20180707 + HPT 1.9 + Binkd 1.1 en Debian
Yes, I have seen it but I don't know why it is. I use Golded
and when I give a reply (q) the subject is changed and I don't
know why it is.
It has done it again in this message :(.
I've never seen this before with a message composed by GoldED. Did you compile it yourself?
I've never seen this before with a message composed by GoldED. Did
you compile it yourself?
I see that also on my 64bit build of golded. I don't think that happens on a 32bit build.
It only seems to happen on messages that have a subject line that
starts with "Re:".
I see that also on my 64bit build of golded. I don't think that
happens on a 32bit build.
I'm using my own 64 bit build. But it is older from 2016ish... I've
never seen this problem.
It only seems to happen on messages that have a subject line that
starts with "Re:".
Interesting...
I see that also on my 64bit build of golded. I don't think that
happens on a 32bit build.
I'm using my own 64 bit build. But it is older from 2016ish... I've
never seen this problem.
Do you happen to have a zip of that source? I wouldn't mind trying that out.
It only seems to happen on messages that have a subject line that
starts with "Re:".
Interesting...
It seems to stumble if there is another ":" somewhere in the subject line.
--- GoldED+/LNX 1.1.5-b20180707 + HPT 1.9 + Binkd 1.1 en Debian
I've never seen this before with a message composed by GoldED. Did you compile it yourself?
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 513 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 08:18:02 |
| Calls: | 8,293 |
| Calls today: | 6 |
| Files: | 15,521 |
| Messages: | 929,113 |