Btw: Can we still expect updates for this list in the future?
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367 ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-U
npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Real name is the name from the nodelist. ;)
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-U
npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Real name is the name from the nodelist. ;)
[08:58:54 brorabbit ~]$ grep ,5858, ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-
U npubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Real name is the name from the nodelist. ;)
Yeah, tell that to Santa Clause, he may believe it. ;-)
Hmmm...
+ 19:24 [1672] call to 2:5001/100@fidonet
19:24 [1672] trying f100.n5001.z2.binkp.net
[2a00:1911:1:1db:6940:47ee:732a:d826]...
19:24 [1672] connected
+ 19:24 [1672] outgoing session with f100.n5001.z2.binkp.net:24554
[2a00:1911:1:1db:6940:47ee:732a:d826]
- 19:24 [1672] SYS Postmortem
? 19:24 [1672] recv: {W32 API error 10054} An existing
connection was forcibly closed by the remote host
+ 19:24 [1672] done (to 2:5001/100@fidonet, failed, S/R: 0/0 (0/0
bytes)) 19:24 [1672] session closed, quitting...
AH, I see. You refuse connections with unlisted systems. There is a
flag for that, the LO flag. You do not carry that flag in the
nodelist. So....
Whatever, it will be fixed in a couple of hours.
@PATH: 280/5555 5020/1042 4441 5001/100
Looks like 2:5020/1042 deserves a punishment..
For what?
And you are even not allowed no post here :)
Says who?
FROM: 2:280/5555
REASON: Sender not active for this area
AREANAME: IPV6
And you are even not allowed no post here :)
Says who?
But you accepted a connection from 2:280/464.5555...
Anyway, my fiberglas connection supports IPv6 as you can see. *1)
We have a very weird guy in R50 who is sending multi-GB pkts and
zip bombs from the TOR network and public proxies to my node.
That is annoying and if for that reason you refuse connections from unlisted systems you should fly the LO flag. You do not...
Good! Let's make this world better.
I am listed in today's daily.
For processing echomail from node that is not in nodelist.
Unlisted, but not unknown.
You may not actually be "Michiel van der Vlist", but rather one
of his virtual identities. According to the nodelist, the real
Michiel van der Vlist left Fidonet in June
Those alleged virtual identities would not have the matching
passwpords to have the connection accepted and the echomail processed. That is why passwords were invented.
Anyway, we are getting off-topic.
To get back on topic:
*1) My fiberglass connection supports IPv6 but to my annoyance there
still is a problem with incoming IPv6 connetctions. The modem/router
that they supply (Nokia XS-2426G-B) has no functioning method to
create an IPv6 pinhole in the firewall. :-(
LO flag means I'll have to refuse all connections from unlisted
nodes, but this is not what I want.
No LO does not mean you MUST refuse all connections from unlisted
systems. It just means you refuse unlisted connections. Some of them,
not all of them.
The problem is that I only update the nodelist weekly. Please
wait.
That is not MY problem.
Even setting Attack Protection to Disabled + Security level = Off
Yes, when I disable the IPv6 firewall, incoming IPv6 connection are possible. But of course I am not going to do that. Then ALL
unsollicited IPv6 packets are allowed. No way Jose!
and configuring port forwarding?
Port forwarding is for IPv4, Yes that works.
No LO does not mean you MUST refuse all connections from unlisted
systems. It just means you refuse unlisted connections. Some of
them, not all of them.
From current nodelist:
LO Node accepts calls Only from Listed
There is nothing about "some of them", the description is pretty
strict - "Only from Listed". Could you please cite any Fidonet
document along with your interpretation?
Even setting Attack Protection to Disabled + Security level =
Off
Yes, when I disable the IPv6 firewall, incoming IPv6 connection
are possible. But of course I am not going to do that. Then ALL
unsollicited IPv6 packets are allowed. No way Jose!
Looks like someone decided to skip proper firewall implementation :(
In theory I could fix it by getting my own fiberglass modem/router but
for XSPON they are expensive and there is little choice. Plus that it
is not easy to get it running. I just think that the burden of
providing a decent modem/router is on them.
97 2:5020/715 Alex Barinov T-6in4 he.net
^^^^^^^^^^^^^^^
Thanks for the offer but I do not have an SFP comatible router at hand
and this is not a good time to start such a major project.I am still
in the process of tuning my Fidonet system after six month of absence
and that takes a lot of time. Not to mention other time concuming
projects in and around the house.
| Sysop: | Bagwaa |
|---|---|
| Location: | Nottingham, UK |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 224:16:24 |
| Calls: | 14 |
| Files: | 1 |
| D/L today: |
2 files (6,861K bytes) |
| Messages: | 78,825 |