Maybe a temporary glitch. Someone else may want to try it:
+ 13 Mar 09:57:39 [4880] call to 3:712/848@fidonet
13 Mar 09:57:44 [4880] trying sysgod.org [2001:470:480f:fc10::4]...
? 13 Mar 09:58:05 [4880] connection to 3:712/848@fidonet failed: {W32
API error 10060} Connection timed out 13 Mar 09:58:05 [4880] trying sysgod.org [203.206.223.152]:24554... 13 Mar 09:58:06 [4880] connected
Maybe a temporary glitch. Someone else may want to try it:
+ 13 Mar 09:57:39 [4880] call to 3:712/848@fidonet
13 Mar 09:57:44 [4880] trying sysgod.org [2001:470:480f:fc10::4]...
? 13 Mar 09:58:05 [4880] connection to 3:712/848@fidonet failed: {W32
API error 10060} Connection timed out 13 Mar 09:58:05 [4880] trying sysgod.org [203.206.223.152]:24554... 13 Mar 09:58:06 [4880] connected
binkp.net web interface does not support AAAA records, that's why.
Update failed: Host '2a0b:2bc0:ffff:21b:f1d0:2:463:877' not found
Edit data for node 2:463/877
On 06-07-19 00:46, Benny Pedersen wrote to Alex Shuman <=-
put a static hostname into nodelist, change that ip on dns, job done,
no need to wait to next weeks nodelist update
That works, then binkp.ner uses CNAME, which can point to AAAA
records.
binkp.net web interface does not support AAAA records, that's why.is this host a webinterface to edit nodelists ?
Edit data for node 2:463/877put a static hostname into nodelist, change that ip on dns, job done,
no need to wait to next weeks nodelist update
Putting a CNAME in binkp.net instead of IP address will make it
dependent on another DNS entry.
Avshalom sent me a netmail. Just in case he did not sent a copy to
the list keeper:
Hello Bjorn!
I must change VPS with my node and new provider has no IPv6. So, I ask
you delete my system from IPv6 list on the FidoNews.
Regards, Avshalom Donskoi
Avshalom sent me a netmail. Just in case he did not sent a copy to
the list keeper:
I must change VPS with my node and new provider has no IPv6. So, I ask
you delete my system from IPv6 list on the FidoNews.
It's very sad. Is strange that in our imperfect world there are still providers that do not provide IPv6 on VPS/VDS.
MvdV> Sad indeed.It's very sad. Is strange that in our imperfect world there are still
providers that do not provide IPv6 on VPS/VDS.
On 10-04-19 08:54, Alexander Kruglikov wrote to Bjrn Felten <=-
It's very sad. Is strange that in our imperfect world there are still providers that do not provide IPv6 on VPS/VDS.
It's very sad. Is strange that in our imperfect world there are stillIf push comes to shove, there's always he.net for a tunnel. :)
providers that do not provide IPv6 on VPS/VDS.
On 10-04-19 15:13, Alexander Kruglikov wrote to Tony Langdon <=-
Good ${greeting_time}, Tony!
*** Answering a msg posted in area CarbonArea ( ).
04 Oct 19 18:48, you wrote to me:
It's very sad. Is strange that in our imperfect world there are stillIf push comes to shove, there's always he.net for a tunnel. :)
providers that do not provide IPv6 on VPS/VDS.
In Russia i use the broker http://ipv6.ip4market.ru/ =)
It's very sad. Is strange that in our imperfect world there are
still providers that do not provide IPv6 on VPS/VDS.
If push comes to shove, there's always he.net for a tunnel. :)
In Russia i use the broker http://ipv6.ip4market.ru/ =)Whichever works. :) Not a lot of choice down here in Australia, but fortunately, I have native IPv6. :)
Michiel van der Vlist wrote to Alexander Kruglikov <=-
It's very sad. Is strange that in our imperfect world there are still providers that do not provide IPv6 on VPS/VDS.
Sad indeed.
I have come across sysops who's provider offers IPv6 but they
refuse to make use of it. IPv6 is too fat and too complicated and
it is not needed they say. :(
Sad indeed.
I don't find it "sad", just "reality".
I have no option to get/use IPv6 here where I live. It's not offered
by any ISP that I know of.
I have come across sysops who's provider offers IPv6 but they
refuse to make use of it. IPv6 is too fat and too complicated
and it is not needed they say. :(
Well, it's not actually *needed*, is it? Fidonet is working just
fine here on IPv4, just as it always has.
Most people (including me) don't care.
When the v4's run out, things will be different.
For now..... it's not needed.
On 10-04-19 15:59, Alexander Kruglikov wrote to Tony Langdon <=-
Good ${greeting_time}, Tony!
*** Answering a msg posted in area CarbonArea ( ).
04 Oct 19 21:26, you wrote to me:
It's very sad. Is strange that in our imperfect world there are
still providers that do not provide IPv6 on VPS/VDS.
If push comes to shove, there's always he.net for a tunnel. :)
In Russia i use the broker http://ipv6.ip4market.ru/ =)Whichever works. :) Not a lot of choice down here in Australia, but fortunately, I have native IPv6. :)
Yes, i also have native IPv6 almost everywhere.
(With blackjack and hookers (c) ) =))))
But perhaps this information will help someone and come in handy.
Only place I don't have native IPv6 is on mobile Internet (4G, etc).
On 10-05-19 10:34, Tommi Koivula wrote to Tony Langdon <=-
Hi Tony.
05 Oct 19 11:04, you wrote to Alexander Kruglikov:
Only place I don't have native IPv6 is on mobile Internet (4G, etc).
It is the opposite here. I have native ipv6 on mobile but not in the
DSL. :)
AFAIK, you can't get IPv6 on mobile in Australia, but I'd like to beproven wrong. :)
On 10-06-19 21:46, Deon George wrote to Tony Langdon <=-
Re: Re: List of IPv6 nodes
By: Tony Langdon to Tommi Koivula on Sat Oct 05 2019 07:24 pm
AFAIK, you can't get IPv6 on mobile in Australia, but I'd like to be
proven wrong. :)
I'll proove you wrong.
Telstra are doing NAT64, just discovered that this week...
AFAIK, you can't get IPv6 on mobile in Australia, but I'd like to be
proven wrong. :)Thanks, now I hope to prove you right. :)
I'll proove you wrong.
On 10-06-19 21:46, Deon George wrote to Tony Langdon <=-
Re: Re: List of IPv6 nodes
By: Tony Langdon to Tommi Koivula on Sat Oct 05 2019 07:24 pm
AFAIK, you can't get IPv6 on mobile in Australia, but I'd like to be
proven wrong. :)
I'll proove you wrong.
Telstra are doing NAT64, just discovered that this week...
...*
On 10-07-19 09:51, Deon George wrote to Tony Langdon <=-
Re: Re: List of IPv6 nodes
By: Tony Langdon to Deon George on Mon Oct 07 2019 08:28 am
AFAIK, you can't get IPv6 on mobile in Australia, but I'd like to be
proven wrong. :)Thanks, now I hope to prove you right. :)
I'll proove you wrong.
No need.
Sad indeed.I don't find it "sad", just "reality".
I have no option to get/use IPv6 here where I live. It's not offered
by any ISP that I know of.
Well, it's not actually *needed*, is it? Fidonet is working just
fine here on IPv4, just as it always has.
Most people (including me) don't care. When the v4's run out,
things will be different. For now..... it's not needed.
IPv4 HAS run out!!!
New ISPs only receive an emergency IPv4 allocation. (/22 I think).
New ISPs only receive an emergency IPv4 allocation.Nope. That last reserve has run out as well. At least here in RIPE territory.
(/22 I think).
Native Qwest 6DWN 37 2:5083/444 Peter Khanin
Native OVH 6DWN
Native Qwest 6DWN 37 2:5083/444 Peter Khanin
Native OVH 6DWN
Why is that?
Native Qwest 6DWN 37 2:5083/444 Peter Khanin
Native OVH 6DWN
Why is that?
Why is what? That you were removed fom the list? That is because the
host name published in the nodelist does not have an AAAA record any
more so your node is not reachable via IPv6. If your node supports
IPv6, please have the DNS for thw hostame in the nodelist updated to reflect the actual situation.
Why is what? That you were removed fom the list? That is because
the host name published in the nodelist does not have an AAAA
record any more so your node is not reachable via IPv6. If your
node supports IPv6, please have the DNS for thw hostame in the
nodelist updated to reflect the actual situation.
I just wonder because nobody touched bind's settings... I didn't know
why my node was added and why it was removed now. Now I fixed the
settings so that:
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: f444.n5083.z2.homelabs.org
Addresses: 2607:5300:100:200::d88
167.114.36.232
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 29 Nov 2019
7 2:221/6 Tommi Koivula T-6in4 he.net f
7 2:221/6 Tommi Koivula T-6in4 he.net f
I haven't checked your list for a long time but this should be:
7 2:221/6 Tommi Koivula Native OVH
Node Nr. Sysop TypeProvider Remark
1 2:280/464 Wilfred van Velzen NativeXs4All f
2 2:280/5003 Kees van Eeten NativeXs4All f
3 2:5019/40 Konstantin Kuzov T-6in4he.net f
4 2:280/5555 Michiel van der Vlist Native Ziggo 5 1:320/219 Andrew Leary NativeComcast f
6 2:221/1 Tommi Koivula T-6in4he.net f
7 2:221/6 Tommi Koivula NativeOH f
8 2:5053/54 Denis Mikhlevich Native TTK-Volga
9 2:5030/257 Vova Uralsky Native PCextreme
I noticed that Jeff posted a message in an echomail area, so I decided
to test his node. 1:14/6 Doesn't exist anymore in the nodelist,
so I tested 1:14/0, which has an IPv6 address, with the following
result:
+ 03 Aug 10:19:03 [10843] call to 1:14/0@fidonet
03 Aug 10:19:03 [10843] trying ftn.region14.org [2001:470:1f10:abd::2]... 03 Aug 10:19:03 [10843] connected + 03 Aug 10:19:03 [10843] outgoing session with ftn.region14.org:24554 [2001:470:1f10:abd::2] ? 03 Aug 10:19:05 [10843] got M_BSY: Blocked +
03 Aug 10:19:05 [10843] done (to 1:14/0@fidonet, failed, S/R: 0/0 (0/0 bytes)) 03 Aug 10:19:05 [10843] session closed, quitting...
And I get the same on his regular node which has a different host
name, but resolves to the same IPv6 address.
Could be a misconfigured Mystic system, which by default blocks
systems of which it doesn't have a secure link with...
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.
Just had to plug into a different board to get power to the BBS again.
Try again. :)
There seem to be some lines missing!? ;)
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.
? 03 Aug 10:19:05 [10843] got M_BSY: Blocked
Could be a misconfigured Mystic system, which by default blocks
systems of which it doesn't have a secure link with...
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...
Maybe outgoing was still working at your end, so mail was still
flowing and you did not notice there was no incoming?
Mail was coming in as well. :)
On 08-05-20 12:54, Michiel van der Vlist wrote to Tony Langdon <=-
Mail was coming in as well. :)
Incoming mail != incoming calls...
37 2:5083/444 Peter Khanin Native OVH 6DWN
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.
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.
I've had the opposite happen, because my IPv6 is native and my IPv4 is unneled.
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?
^^^^^^^^^^^^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?
Depends, some networks would go down, though both my Fido feed and
busiest othernet both have IPv6 capability.
Remarks:
f Has a ::f1d0:<zone>:<net>:<node> style host address.
f Has a ::f1d0:<zone>:<net>:<node> style host address.
Very nice!, can i get these address using he.net tunnel?
f Has a ::f1d0:<zone>:<net>:<node> style host address.
Very nice!, can i get these address using he.net tunnel?
Remarks:
f Has a ::f1d0:<zone>:<net>:<node> style host address.
Very nice!, can i get these address using he.net tunnel?
f Has a ::f1d0:<zone>:<net>:<node> style host address.
Very nice!, can i get these address using he.net tunnel?
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,-Unpublished-,300
,MO,CM,IBN,INA:[2001:470:dcd0:1000:f1d0:2:460:5858],INO4
JFYI ;)
[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
Node Nr. Sysop Type Provider Remark
6 2:221/1 Tommi Koivula T-6in4 he.net f
Ooops --- 153/7715, please. :-)
I've switched from my he.net tunnel to the native IPv6 stack from my
provider (Deutsche Telekom).
This whole geolocation stuff is just meeehh...
I never understood why providers still issue dynamic adresses to their customers.
I deliberately change my geolocation (VPN) to extend my various
streaming services (e.g. Netflix, Prime, BBS, NRK) by a magnitude. Unfortunately I still haven't found a VPN service that handles IPv6.
It'll probably take another decade or so before they catch up.
So they can charge extra for static addresses?
Hello Alexey,
On Wednesday January 05 2022 20:02, you wrote to Bjrn 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.
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?
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.
I have a wireguard server running in my VPS (Ubuntu 20.04.3 LTS).Do you mean to say you can have a /64 network on your VPS' main
It is using a /112 of /64 for it's clients.
interface and at the same time a /112 from the *same* *network*
on a wg0 interface? Is this even permitted by the OS?
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.
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?
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?
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...
Basically a 50 MBit/s (downstream) / 10 MBit/s (upstream) is around
40 EUR/month for consumers
Do you know if the 2000::/3 global pool can be extended if
necessary?
Sure. When 2000::/3 runs out, there is 4000::/3. And when that runs
out, there is 6000::/3. Up until c000::/3.
I do not expect to live to see that happen.
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.
Basically a 50 MBit/s (downstream) / 10 MBit/s (upstream) is aroundWOW! That's a lot. I pay EUR40 per month for my 100/100.
40 EUR/month for consumers
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. :)
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?
Obviously.
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.
That's a limitation of BSD-style IP stack.
A 50/10 fiber costs less than EUR20 here in Sweden.
Asymmetric? Why?
^^^^^^^A 50/10 fiber costs less than EUR20 here in Sweden.
Asymmetric? Why?Maybe the cheap solution: Only one fiber; downstream and upstream
on different wavelengths.
Maybe the cheap solution: Only one fiber; downstream and upstream
on different wavelengths.
Yes, but this technology is symmetric.
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. :)
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.
MvdV> It is not that 2^64 addresses are not enough for all my devices,Doesn't a /64 contain 2^64 addresses? Not enough? The entire IPv4
pool is 2^32...
designed. A /64 is the smallest subnet. I might have designed it different but I was not involved at the time.
So... if one wants/needs more than one subnet, one needs more than one /64. That is the way it is.
In another part of the city, the municipal services are searching for
fiber (FTTH) clients, but it also won't be cheap and you'll only get
a "dual stack lite" connection :-(
Same here. Although how much of "a lot" it costs more depends on the
speed and other extras that you wish to have.
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...
I use /80's a lot, which in reality could be /96's but I'm being generous to the network that I use the /80's on.
But why? When you can have enough space to make /64 subnets?
And some thing will not work any more.
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.
Correct.
But as long as IPv6 is not the default case for accessing the
Internet, I still want to have a 'real' IPv4 address to be able to
access my home devices from the Internet.
And in my case, I don't have IPv6 at work, for example.
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 :)
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....
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.
On 01-10-22 13:39, Michiel van der Vlist wrote to Victor Sudakov <=-
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.
On 01-10-22 14:38, Richard Menedetter wrote to Michiel van der Vlist <=-
Or a /64 for residential.
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
;)
:) 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...
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.
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,Or simply route more /64 subnets through that address. Or /56 at once.
different subnet on different LAN port, etc.)
That is added complexity for a low cost product, where most ofThat violates the KISS principle.
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.Indeed. It is easier to just give every customer a /56. And just route
the first /64 to the LAN, so that the user need not configure anything
if he only needs one /64. And the provider does not need to configure anything if the customer needs more.
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.
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.
On 01-19-22 12:21, Michiel van der Vlist wrote to Tony Langdon <=-
I did just that a couple of years ago to test prefix delegation. I connected a second router behind my primary router and IIRC it got a
/61 out of the /56 assigned to me. Of that /61, one /64 was routed to
the local LAN of the second router. I presume the process allows for cascading routers until the /56 is exhausted, but I did not explore
that. I was satisfied that I demonstrated prefix delegation worked.
On 01-19-22 12:36, Michiel van der Vlist wrote to Tony Langdon <=-
We also have to get rid of IPv4 think. On top of that list are:
1) NAT is not a security feature.
2) There is no shortage of addresses. Address space is no longer a
scarce commodity.
With the mind still in IPv4 think mode, giving out a /56 to everyone while the vast majority will get no further than using 1 or 2% of that looks like a terrible waste.
Then consider that "waste" is only an issue if there is shortage. With IPv6 there is no shortage of addreses. Thinking "waste" is IPv4 think.
We have to get rid of that.
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...
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 14 May 2022
Node Nr. Sysop Type Provider Remark
6 2:221/1 Tommi Koivula Native Hetzner f
Node Nr. Sysop Type Provider Remark
6 2:221/1 Tommi Koivula Native Hetzner f
^
Elisa
I think I mentioned about that in this echo some time ago?
6 2:221/1 Tommi Koivula Native Hetzner f
^
Elisa
I think I mentioned about that in this echo some time ago?
Please check your entry. Ig it needs updateing, please let me know.
96 2:5020/736 Egor Glukhov Native RUWEB f
97 2:221/10 Tommi Koivula Native Hetzner f INO4
97 1:266/420 Scott Street Native Comcast OO
99 1:218/850 John Nicpon Native LINODE-US
97 2:221/10 Tommi Koivula Native Hetzner f INO4
97 1:266/420 Scott Street Native Comcast
Just a nit pick, 97 appears twice, though the count is correct. :)
107 1:214/22 Ray Quinn t-6in4 he.net
T-6in4 Static 6in4
f Has a ::f1d0:<zone>:<net>:<node> style host address.
(zone, net, node in decimal notation)
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)
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)
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,-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
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 ?
; 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
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. ;-)
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: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 505 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 79:42:04 |
| Calls: | 9,931 |
| Calls today: | 7 |
| Files: | 13,807 |
| Messages: | 6,347,730 |
| Posted today: | 2 |