Hallo Michiel,
I've switched from my he.net tunnel to the native IPv6 stack from my provider (Deutsche Telekom).
As the prefix may change from time to time, I'm using the Dynv6 DynDNS
service to keep track of my IPv6 prefix. (Before, I chose the he.net tunnel to ensure a static prefix, but I had more and more trouble
because of GeoIP stuff for some services...)
I've switched from my he.net tunnel to the native IPv6 stack from my
provider (Deutsche Telekom).
I even tried a website which should tell me where my IP address is
located and one even told me I'm in Germany when using one of the
he.net tunnels...
This whole geolocation stuff is just meeehh...
This whole geolocation stuff is just meeehh...
I did not use SixXs, but it stopped its service anyway some years ago.
The he.net tunnel ran fine for many, many years - and I had my fixed prefix where I even could provide my reverse DNS for.
The native IPv4+IPv6 connection from Telekom does work, but as it's
only a consumer-grade connection, I don't get fixed addresses or a
fixed prefix. But I found a workaround using Dynv6 :)
So my router (Fritz!Box) calls a script on one of my rented vServers
(via a https request), which in turn sets the IPv4 address and the
IPv6 prefix on Dynv6 and on my own DNS zone. And it seems to work fine
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?
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?
So they can charge extra for static addresses?
Hi Michiel!
05 Jan 2022 13:41, from Michiel van der Vlist -> Anna Christina Nass:
I never understood why providers still issue dynamic adresses to
their customers.
Same here.
But I learned something.
It seems many customers see that as a privacy enhancing thing.
Also some services use the IP to meter free usage.
I have heared of people that reboot their modem to get a new IP and
start with 0 MB downlaoded all over ;)
If you were a really smart ass, you'd search for some cheap VPS
instead.
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...
And it's probably easier to "administer" dynamic addresses.
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. :)
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.
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?
I think, today it is a way to sell their 'business' rates which
include static IPv4 and IPv6 prefix...
As far as I've read, at least as a customer of Deutsche Telekom it is
also possible to get the business packages. I don't know how other
ISPs handle it, though.
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?
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
Running the Fidonet node is not (and can not ever be) restricted by
GeoIP services.
Or several tunnels.
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?
Of course VPN (virtual private network) is a tunnel. :D
And so you have the same geolocation issues...
What issues? I'm not following you now... I have no geolocation issues with the vpn server located in Finland.
The he.net tunnel to Amsterdam causes websites to speak dutch to me,
but I'm not using that tunnel for web.
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.
^^^^^^^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. :)
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...
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!
I do not expect to live to see that happen.
Things do happen. We may reach a technological singularity where every
AI will request a /48 for itself and its minions, for example.
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 :-(
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.
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.
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
;)
Doesn't a /64 contain 2^64 addresses? Not enough? The entire IPv4
pool is 2^32...
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...
[Top-secret, burn before reading!]
And on my early experiments, when the /64 was the only block I had,
that was really great.
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.
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... if one wants/needs more than one subnet, one needs more than
one /64. That is the way it is.
Sure it can!
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.
Certainly, having a /64 is "simplier" - its, in many cases, no configuration required (or minimal "enabling" in your router). But anything smaller, its pretty much manual.
Yep, I know :) And thus the 'newer' ISPs don't had the chance to get enough IPv4 addresses for all new customers, while 'older' ISPs (like
Deutsche Telekom in my case) have bigger IPv4 address pools.
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 :)
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....
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 :)
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
;)
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.
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.
At least the use of DS-Lite ISP connections makes it a little more apparent to the customers that IPv4 has some disadvantages over IPv6 nowadays.
But I guess the vast majority of 'consumers' who only use simple web browsing, email and media streaming services won't notice it anyway.
So in theory, the transition for those consumers can continue as long
as the services that most people use are reachable via IPv6.
:) I'm working for the local public library, a part of the
municipality.
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*).
My point was more in the direction of the mentality of German
bureaucracy. Changes here take ages. We are still stuck to Microsoft (Windows, Office, AD... all the nice things that malware loves) and
until this year we're still using Lotus Notes (Exchange/Outlook will follow ... *shiver*).
And I'm trying to update things. We've moved out library management
system to Linux servers some years ago (and now it's running much more stable and reliable than before) and are updating hardware as good as
we can. But as said before, we're not on the top of the hierarchy in
the municipality, we are dependant on others who run the network. So
we can't move to IPv6 on our own :)
That's always a good idea!
I could set up a VPN tunnel to one of my vServers, or use some kind of service that you mentioned, to be reachable from outside again. Let's
see how all this will turn out.
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.
It is even simpler to just to hand out a /64 ;)
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... :-/
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...
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
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,-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.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 766 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 03:07:29 |
| Calls: | 10,581 |
| Calls today: | 1 |
| Files: | 185,898 |
| Messages: | 1,676,694 |
| Posted today: | 1 |