On 08-02-20 17:26, Michiel van der Vlist wrote to All <=-
27 3:633/410 Tony Langdon Native IINET DOWN
27 3:633/410 Tony Langdon Native IINET
DOWN
I'm up and running. I did have a temporary glitch for a few hours the other day, due to a dead power board.
On 08-04-20 15:53, Michiel van der Vlist wrote to Tony Langdon <=-
I'm up and running. I did have a temporary glitch for a few hours the other day, due to a dead power board.
More like a few days than a few hours...
Just had to plug into a different board to get power to the BBS again.
Good to see you'r back on line.
Try again. :)
Check. ;-)
On 08-05-20 11:12, Stephen Walsh wrote to Tony Langdon <=-
Hello Tony!
04 Aug 20 21:15, you wrote to Michiel van der Vlist:
27 3:633/410 Tony Langdon Native IINET
DOWN
I'm up and running. I did have a temporary glitch for a few hours the other day, due to a dead power board.
It was more than a few hours! #-( But by the time I could send you a email, you'd hit the thing with a
hammer.! %_)
More like a few days than a few hours...
Hmm, now that is strange, I've been using it all this time, and mail
has been moving.
Weird, was only down for no more than a few hours this end! However, there are possible circumstances that result in IPv4 going down, but
IPv6 is much less likely to fall over.
On 08-05-20 09:44, Michiel van der Vlist wrote to Tony Langdon <=-
Maybe outgoing was still working at your end, so mail was still flowing and you did not notice there was no incoming?
If it is only your IPv4 that goes down, I would not notice. My system tries IPv6 first, If IPv6 is up and running, IPv4 is never tried...
On 08-06-20 13:11, Michiel van der Vlist wrote to All <=-
Hello All,
Wednesday August 05 2020 09:53, I wrote to you:
37 2:5083/444 Peter Khanin Native OVH 6DWN
He's back.
One of the problems with Dual Stack is that it can take a long time to notice something is wrong when IPv6 drops out. In almost all cases mail just keeps flowing via IPv4.
On 08-07-20 11:47, Michiel van der Vlist wrote to Tony Langdon <=-
So your IPv4 is more vulnerable. But as the majority of active Fidonet
is still IPv4 only, failing IPv4 would be noticed much sooner than failing IPv6 wouldn't it?
Remarks:
f Has a ::f1d0:<zone>:<net>:<node> style host address.
7 2:221/6 Tommi Koivula Native OH f
58 2:5005/49 Victor Sudakov T-6in4 he.net
$ host box.imzadi.de
box.imzadi.de is an alias for box.my.imzadi.de.
box.my.imzadi.de has address 91.35.159.214
box.my.imzadi.de has IPv6 address 2001:470:540b:0:f1d0:2:240:5824
$ host box.imzadi.de
box.imzadi.de is an alias for box.my.imzadi.de.
box.my.imzadi.de has address 91.35.159.214
box.my.imzadi.de has IPv6 address 2001:470:540b:0:f1d0:2:240:5824
Thank you for pointing this out!
I indeed forgot to change the IPv6 address in my firewall...
It should work now.
Where are the first two?
Why don't you automate sending this text from a file?
Have a nice night.
Thanks. After my wife dies, I try not to get drunk every night and sometimes I even get it.
[fido@host-187 nodelist]$ grep -i ',5858' ./nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpublishe
d -,300 ,MO,CM,IBN,INA:[2001:470:dcd0:1000:f1d0:2:460:5858],INO4
18:16 [10307] trying 2001:470:dcd0:1000:f1d0:2:460:5858 [2001:470:dcd0:1000:f1d0:2:460:5858]... 18:18 [10307] connection to 2:460/5858@fidonet failed: Connection timed out 18:18 [10307] trying f5858.n460.z2.binkp.net [2001:470:dcd0:1000:f1d0:2:460:5858]... 18:20 [10307] connection to 2:460/5858@fidonet failed: Connection timed out 18:20 [10307] holding 2:460/5858@fidonet (2021/03/07 18:30:28)
JFYI ;)
JFYI ;)
[fido@host-187 nodelist]$ grep -i ',5858' ./nodelist.36718:16 [10307] trying 2001:470:dcd0:1000:f1d0:2:460:5858 [2001:470:dcd0:1000:f1d0:2:460:5858]...
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,
-Unpublished-,300,MO,CM,IBN,
INA:[2001:470:dcd0:1000:f1d0:2:460:5858],INO4
18:18 [10307] connection to 2:460/5858@fidonet failed: Connection
timed out
JFYI ;)JFYI ;)
48 2:467/239 Mihail Kapitanov T-6in4 he.net f
48 2:467/239 Mihail Kapitanov T-6in4 he.net f
Mykhailo Kapitanov, Native, Vultr :)
Node Nr. Sysop Type Provider Remark
6 2:221/1 Tommi Koivula T-6in4 he.net f
Ooops --- 153/7715, please. :-)
Hello Alexey,
On Wednesday January 05 2022 20:02, you wrote to BjФrn Felten:
If you were a really smart ass, you'd search for some cheap VPS
instead.
Then I am not a smart ass. I LIKE to run my Fidonet stuff from home. With whatever I can put together to make it
work.
So maybe it is just to save a bit on addresses? If only 1% of
customers isn't online at any give time, if you have a milion
customers that is still 10000 addresses...
1) For IPv6 it is no issue. There is no shortage on IPv6 adresses.
(yet)
You can have a VPS with static /64 and run your own VPN server there. That's exactly how I have a static ipv6 address everywhere I want. For example at home to run fidonet stuff. :)
I think, today it is a way to sell their 'business' rates which
include static IPv4 and IPv6 prefix...
My first boss once told me: If something is to be done more than one
time, it's worth writing a script to automate it :)
But besides, you have to be noticed somehow that the IP/prefix has
been changed - or how do you know when to manually update your DNS?
You can have a VPS with static /64 and run your own VPN server
there. That's exactly how I have a static ipv6 address everywhere
I want. For example at home to run fidonet stuff. :)
I have a Vultr VPS with a static /64 on its interface. But to use it
as a VPN server, you need to carve some IPv6 subnet out of this /64,
how do you do it?
Then I am not a smart ass. I LIKE to run my Fidonet stuff from
home. With whatever I can put together to make it work.
If you read the message thread again, you will notice that they
were not talking about running fidonet stuff. They were talking
about VPN.
That is not how I read Alexey's message.
You can have a VPS with static /64 and run your own VPN server
there. That's exactly how I have a static ipv6 address everywhere
I want. For example at home to run fidonet stuff. :)
Ok... So you run your Fidonet server at home and you have a VPN
conection to a server in a data centre. You have a /64 from the
address range of the data centre and all your IPv6 traffic goes
through the data centre. Yes?
Hmm... It seems to me that the same description fits a tunnel...
MvdV> That is not how I read Alexey's message.Then I am not a smart ass. I LIKE to run my Fidonet stuff from
home. With whatever I can put together to make it work.
If you read the message thread again, you will notice that they
were not talking about running fidonet stuff. They were talking
about VPN.
MvdV> Ok... So you run your Fidonet server at home and you have a VPNYou can have a VPS with static /64 and run your own VPN server
there. That's exactly how I have a static ipv6 address everywhere
I want. For example at home to run fidonet stuff. :)
If you were a really smart ass, you'd search for some cheap VPS
instead.
Then I am not a smart ass. I LIKE to run my Fidonet stuff from home.
With whatever I can put together to make it work.
Okay, so it can happen that your IPv6 connection isn't reachable for
some time (via DNS). So it's good that IPv4 is still working :)
Hmm... It seems to me that the same description fits a tunnel...
Of course VPN (virtual private network) is a tunnel. :D
And so you have the same geolocation issues...
I have a wireguard server running in my VPS (Ubuntu 20.04.3
LTS). It is using a /112 of /64 for it's clients.
Do you mean to say you can have a /64 network on your VPS' main
interface and at the same time a /112 from the *same* *network*
on a wg0 interface? Is this even permitted by the OS?
Yes - at least properly configured Linux allows this.What do you mean by "properly configured"? You mean the
out-of-the-box configuration still does not allow this?
A Cisco router would not allow the same L2 network on two different
L3 interfaces IMHO, even if one of the prefixes is more specific.
Maybe the cheap solution: Only one fiber; downstream and upstream
on different wavelengths.
(I agree with Alexey, the above quote looks like shit, what crappy abandonware is responsible for this?)
Basically a 50 MBit/s (downstream) / 10 MBit/s (upstream) is around
40 EUR/month for consumers
WOW! That's a lot. I pay EUR40 per month for my 100/100. A 50/10 fiber costs less than EUR20 here in Sweden. And we are a loooong country, with a lot of rural space, we need long fibres. :)
MvdV> Yes, now that you mention it, I remember yuo experimentingAnd on my early experiments, when the /64 was the only block
I had, that was really great.
MvdV> OK, so I stand corrected, it is possible.No. The /64 is the default subnet size, and people normally
SHOULD NOT (as in FTA-1006) split these blocks further, but
that IS possible and NOT prohibited.
MvdV> So most people in Russia do not need more than one subnet....Here in Russia the de-facto standard is one MAC-based IPv6 address
for the outer-side link and /64 subnet routed via that address to
the customer's LAN. Additional subnets may be requested as well,
but ISP admins say most people don't request them.
Sure. When 2000::/3 runs out, there is 4000::/3. And when that
runs out, there is 6000::/3. Up until c000::/3.
That's great news!
It is not really news I'd say.
Ans I suppose when push come to shove
1000::/4 coild also be used. And even 0::/4 with the exeption of
0::/64.
I agree. The only reason I can figure out, is that some ISPs don't
want people to run servers,
they want their customers to buy their
contents (usually lots of encoded TV channels).
Here in Russia the de-facto standard is one MAC-based IPv6
address for the outer-side link and /64 subnet routed via that
address to the customer's LAN. Additional subnets may be
requested as well, but ISP admins say most people don't request
them.
So most people in Russia do not need more than one subnet....
You're absolutely right!
And in my case, I don't have IPv6 at work, for example.
:) I'm working for the local public library, a part of the
municipality.
And as I'm living in Germany, I'm happy that I do have a working
computer and not only a typewriter and a fax machine. Our library
building still has some IBM Type-1 cabling (from Token Ring-days) that we're using for Ethernet via some adapters... I don't think that IPv6
days will come soon here...
I didn't know that page, thanks for that info :)
But I'm happy that my setup is working at the moment as I've set it up
But all my (own, private) servers do have IPv6 enabled and
reachable for years now (and I also have the IPv6 T-Shirt from
he.net *g*), so at least I'm prepared :)
Hehe, nice try :) I guess it's looking basically the same :)
Or a /64 for residential.There are arguments for more than a /64 for residential use. That
And you don't have to fuss around with how to subnet.
The CPE simply announces the IPv6 net on the LAN side and you are
done ;)
allows for different subnets with different security profiles, such as
for IoT, the car, whatever other network of smart devices you want.
For many, I suspect a /60 would be sufficient.
:) I'm working for the local public library, a part of the
municipality.
And as I'm living in Germany, I'm happy that I do have a working
computer and not only a typewriter and a fax machine. Our library
building still has some IBM Type-1 cabling (from Token Ring-days) that AN>> we're using for Ethernet via some adapters... I don't think that IPv6
days will come soon here...
And I suppose when push come to shove 1000::/4 coild also be used.
And even 0::/4 with the exeption of 0::/64.
BTW what is already in use within 0000::/1 and 8000::/1 besides
2000::/3?
There are a lot of better options to run a server than a home
connection IMHO.
Most people in Russia cannot even get one *native* IPv6 address for
their home connection, let alone a static one. Well, probably not most
but the majority, I'm for one. I have not noticed ISPs here willing to adopt IPv6.
Mobile operators (mts.ru for sure) give you a dynamic IPv6 address for each mobile device by default (to go together with an RFC1918 IPv4 address).
Many ISPs only offer a /48 to business accounts. For consumer
accounts it is often a /56. A /56 is plenty for most I'd say.
Yeah, I can't see myself using my /56 in my lifetime. What will I do
with 256 networks? :)
There are arguments for more than a /64 for residential use. That
allows for different subnets with different security profiles, such as
for IoT, the car, whatever other network of smart devices you want.
For many, I suspect a /60 would be sufficient.
There are arguments for more than a /64 for residential use. ThatSure ... I agree. My reply was more from the ISP point of view.
allows for different subnets with different security profiles, such
as for IoT, the car, whatever other network of smart devices you
want. For many, I suspect a /60 would be sufficient.
With 1 v6 subnet it is easy, you just announce the subnet.
If you allow more, you need a way to configure them. (eg. VLANs,
different subnet on different LAN port, etc.)
That is added complexity for a low cost product, where most of your residential customers will have no clue what this is all about. So
it makes more sense to offer that on higher tier (and more expensive) services.
Sure ... I agree. My reply was more from the ISP point of view.
With 1 v6 subnet it is easy, you just announce the subnet.
No: when you need to provide the customer with IPv6, you assign one
fixed address for a link, and route a /64 subnet through that address.
Plastic routers (those sold for 20 EUR) deal with this setup just
fine.
If you allow more, you need a way to configure them. (eg. VLANs,
different subnet on different LAN port, etc.)
Or simply route more /64 subnets through that address. Or /56 at once.
That is added complexity for a low cost product, where most of
your residential customers will have no clue what this is all
about. So it makes more sense to offer that on higher tier (and
more expensive) services.
That violates the KISS principle.
On 01-16-22 11:35, Richard Menedetter wrote to Tony Langdon <=-
There are arguments for more than a /64 for residential use. That
allows for different subnets with different security profiles, such as
for IoT, the car, whatever other network of smart devices you want.
For many, I suspect a /60 would be sufficient.
Sure ... I agree.
My reply was more from the ISP point of view.
With 1 v6 subnet it is easy, you just announce the subnet.
If you allow more, you need a way to configure them. (eg. VLANs,
different subnet on different LAN port, etc.)
That is added complexity for a low cost product, where most of your residential customers will have no clue what this is all about.
So it makes more sense to offer that on higher tier (and more
expensive) services.
On 01-16-22 18:06, Michiel van der Vlist wrote to Tony Langdon <=-
Neither can I, but I can imagine some wanting/needing more than a /60. The "rule" should be "give them so much they will never come back for more". That wey they avoid having to make administrative exceptions for some customers. There is enough to give every customer a /56.
I know I can add a router behind the primary router. The main manual setup will be to assign a /64 to the LAN side of that router. The existing router will pick up the advertisements, setup routing and optionally open the firewall for that /64 (so that filtering can be controlled by the second router).
I haven't put that to the test yet, but tempted to give it a try
sometime, as a learning exercise. :)
Neither can I, but I can imagine some wanting/needing more than
a /60. The "rule" should be "give them so much they will never
come back for more". That wey they avoid having to make
administrative exceptions for some customers. There is enough to
give every customer a /56.
Yeah, there is that argument. Over time, I can see myself using 3 or
4 /64s. More than 16 is unlikely, unless I start doing a lot of funky
VPN stuff. ;)
It is for you, if your provider only gives you the bare minimum, and
tries to sell you more... :-/
Except when they think they can make an extra buck... :-/
Except when they think they can make an extra buck... :-/
No, that's my full time job (and I get payed - lucky me *g*).
And although I'm in the IT department of the library, there are other
departments 'above' us who run the city-wide IT.
Well, you're right (and yes, I know that even via 'real' Token Ring,
you can use IPv6 *g*).
That isn't always as simpel as it sounds...
There are probably lots of places where providers still more or less
have a monopoly.
Same here. The IPv6 connection for my BBS also had problems on friday
because Dynv6 'forgot' the AAAA record that I've configured - but it
seems to be a known problem. Maybe I rewrite the update script (and
recreate the AAAA record on every prefix change) or switch to my own
dyndns solution...
MvdV>> We patiently wait... ;-) Please share your experience with us.Same here. The IPv6 connection for my BBS also had problems on
friday because Dynv6 'forgot' the AAAA record that I've configured
I just noticed that Dynv6 lost my AAAA record again, so I chose to
update my update script. Dynv6 is offering the use of 'nsupdate',
and as I'm already using nsupdate for my own DynDNS solution, I just added a nsupdate call for my Dynv6 zone to the script.
[...]
I hope that this solves the Dynv6 AAAA problem now - I hope that my
IPv6 prefix changes more often than Dynv6 forgets my AAAA record :)
I just noticed that Dynv6 lost my AAAA record again, so I chose to
update my update script. Dynv6 is offering the use of 'nsupdate', and
as I'm already using nsupdate for my own DynDNS solution, I just added
a nsupdate call for my Dynv6 zone to the script. It's basically
working as noted in the API documentation: https://dynv6.com/docs/apis
f Has a ::f1d0:<zone>:<net>:<node> style host address.
(zone, net, node in decimal notation)
I once had mine set up for this. For the life of me, I cannot find out what I did to make it work. It seems that I failed to backup the network settings when "upgrading" the last time. Can someone point me in the right direction? Using Debian 11 (bullseye)
Tuesday November 01 2022 22:55, you wrote to All:
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367 ,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
Tuesday November 01 2022 22:55, you wrote to All:
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[fido@brorabbit inbound]$ 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
This node is on my desktop computer. It is used for debugging and
testing software.
Tuesday November 01 2022 22:55, you wrote to All:
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
[fido@brorabbit inbound]$ grep ',5858,' ~/nodelist/nodelist.367
,5858,For_Technical_Purposes,Simferopol_Crimea,Brother_Rabbit,-Unpubli
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
space after 300
shed-,300 ,MO,CM,IBN,INA:burrow.g0x.ru,INO4
space after 300
space after 300
It's not my. :)
space after 300
It's not my. :)
Of course not. That would have caused an ;E line in the nodelist, if I recall correctly from my MakeNl reverse engineering days. 8-)
36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
08 Oct 22 19:40, you wrote to all:
36 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
I think this should be changed to 2:240/5413 after net 2:2452 shut
down.
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 ?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
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. ;)
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: | Coz |
|---|---|
| Location: | Anoka, MN |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 73:40:21 |
| Calls: | 340 |
| Files: | 5,989 |
| Messages: | 231,968 |