Just noticed this one:
Calling 2:240/5413 (2a01:a700:4629:211:f1d0:2:240:5413:24554)
error (Connection timed out)
IPv4 is ok for this node...
Just noticed this one:Netmail send to sysop.
Calling 2:240/5413 (2a01:a700:4629:211:f1d0:2:240:5413:24554)
error (Connection timed out)
IPv4 is ok for this node...
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
Hi Michiel.
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?
I have checked all the remaining nodes in the list for
connectivity and as a result more nodes have been flagged 6DWN or
even DOWN...
What happened to 2:221/10 ?
; Alexander Kruglikov T-6in4 Tunnel-Brkr-Net1 f
2:5057/19 = 2a03:1ac0:5571:3a38:f1d0:2:5057:19 (Native, ER-Telecom)AKA 2:5057/0
Missing:
2:5057/19 = 2a03:1ac0:5571:3a38:f1d0:2:5057:19 (Native, ER-Telecom) 2:5075/0 and 2:5075/35 = 2a03:80c0:1:f:f1d0:2:5075:35 (Native, RUWEB) 2:5075/37 = 2a03:c980:db:19:: (Native, IHC)
2:5075/128 = 2a03:e2c0:12a2:0:f1d0:2:5075:128 (T-6in4, IP4Market AKA TUNNELBROKER-0)
06.06.2023 21:19, Michiel van der Vlist »¿Ñ:
93 2:5020/5858
; Alexander Kruglikov T-6in4 Tunnel-Brkr-Net1 f
Also IP4Market, as "TUNNELBROKER-0" in your list
Hello All,
Paul Hayton now has native IPv6
Hi Michiel.
I have checked all the remaining nodes in the list for connectivityWhat happened to 2:221/10 ?
and as a result more nodes have been flagged 6DWN or even DOWN...
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?why do you ask ?
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?
why do you ask ?Why do you answer with a question?
Good ${greeting_time}, Benny!
02 Aug 2023 17:28:34, you wrote to Tommi Koivula:
I have checked all the remaining nodes in the list for connectivity
and as a result more nodes have been flagged 6DWN or even DOWN...
What happened to 2:221/10 ?
why do you ask ?Why do you answer with a question?
03 Aug 2023 11:51, Alexey Vissarionov wrote to Benny Pedersen:
Good ${greeting_time}, Benny!
02 Aug 2023 17:28:34, you wrote to Tommi Koivula:
I have checked all the remaining nodes in the list for
connectivity and as a result more nodes have been flagged
6DWN or even DOWN...
What happened to 2:221/10 ?
why do you ask ?Why do you answer with a question?
he, if Tommi can't check logs on his own network, its brokken
I have no logs of the "List of IPv6 nodes". ;-D
08 Feb 2024 09:39, Tommi Koivula wrote to Benny Pedersen:
TK> I have no logs of the "List of IPv6 nodes". ;-D
grep xxxx:: binkd.log
why is it needed to use external lists ?
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. ;-)
Could you please change:
30 2:5001/100 Dmitry Protasoff Native OVH
to
30 2:5001/100 Dmitry Protasoff Native Layer7 Networks
It's a very cheap VPS provider from Germany.
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...
BinkpAbstractConnector Protocol version 1.1 28-09-24 17:23:08
[00007394] BinkpAsyncConnector Frame received: [ M_ADR
2:280/5555@fidonet ] 28-09-24 17:23:08 [00007394]
BinkpAbstractConnector Invalid address 28-09-24 17:23:08 [00007394] NodelistScanner Using nodelist file nodelist 28-09-24 17:23:08 [00007394] BinkpAbstractConnector Local error: No valid address
specified
@PATH: 280/5555 5020/1042 4441 5001/100
Looks like 2:5020/1042 deserves a punishment..
And you are even not allowed no post here :)
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?
And you are even not allowed no post here :)
Says who?
You disappear for a long time, then you suddenly start posting to
echoes that you are not connected to. And from an unlisted node.
Shame on you.
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....
I accept connections from unlisted systems, but not from all.
If you are related somehow to 2:5001 - I'll accept connection from
your unlisted node (based on your ip address). But not from some
random Dutch Vodafone ipv6 address with non existing node address. Too suspicious.
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.
Whatever, it will be fixed in a couple of hours.
Good! Let's make this world better.
@PATH: 280/5555 5020/1042 4441 5001/100
Looks like 2:5020/1042 deserves a punishment..
For what?
For processing echomail from node that is not in nodelist.
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
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.
I am listed in today's daily.
The problem is that I only update the nodelist weekly. Please wait.
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. :-(
Even setting Attack Protection to Disabled + Security level = Off
and configuring port forwarding?
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
^^^^^^^^^^^^^^^
Non-authoritative answer:
Name: fido.hubahuba.su
Address: 2001:470:1f0b:879:f1d0:2:5020:715
^^^^^^^^^^^^^^^
If you'd like, I can send you the SFP and help to setup it in
compatible router.
Alternatively, you could try configuring your router as a bridge. Is
that possible?
You could then connect it to another intelligent router. I had this
setup in Moscow for a while, but, once again, I can't teleport there
to resolve any issues. However, this might not be a concern in your
case.
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.
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.
Another option is a dumb GPON-to-Ethernet bridge as separate device,
but I've never tried them myself. The main issue with these 3rd-party devices is to obtain all required parameters from provider's router,
which is sometimes not possible without the provider's support :(
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,042 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 00:19:42 |
| Calls: | 500,919 |
| Calls today: | 6 |
| Files: | 109,372 |
| D/L today: |
14,736 files (2,323M bytes) |
| Messages: | 305,057 |
| Posted today: | 7 |