The use of AI (Artifical Intelligence) to generate message text is discouraged.
Please note the new rule effective imnidiately
The use of AI (Artifical Intelligence) to generate message text is discouraged.
The use of AI (Artifical Intelligence) to generate message text is >discouraged.
Sadly, we have reached that point in our history where this is
possible and, on the internet anyway, likely to happen.
Michiel van der Vlist wrote to Mike Powell <=-
The use of AI (Artifical Intelligence) to generate message text is >discouraged.
Sadly, we have reached that point in our history where this is
possible and, on the internet anyway, likely to happen.
I hope that at least in Fidonet we can manage it. AI can be a usefull tool, even to help people configure their IPv6. But we should not use
it to generate text in echomail messages.
Speaking about IPv6: how are you doing? Does your provider support it?
Speaking about IPv6: how are you doing? Does your provider support
it?
No, they do not at this point. I am guessing it will be one of those things that happens that we are not told about until we just notice
it. ;)
Speaking about IPv6: how are you doing? Does your provider support it?
No, they do not at this point. I am guessing it will be one of those things that happens that we are not told about until we just notice it. ;)
If you take a look at the list, which Michiel has updated for the Fidonews like clockwork every Sunday at 22:00 CET for years, you'll
see that around 80% have Native (i.e. from their provider) IPv6.
You'll also see that the remaining 20% all but one use a tunnel
from he.net. So why do you have to wait? Get ready for the future, already.
It is my understanding that in many parts of the rest of the world
the situation is different. Many poviders still do not offer IPv6
and there is no competition between providers.
So to all sysops that still have that bit of pioneer spirit left in> them end who are stuck with a provider that offers no native IPv6 I
say: Use the service of he.net to join the Fidonet IPv6 club!
It is my understanding that in many parts of the rest of the
world the situation is different. Many poviders still do not
offer IPv6 and there is no competition between providers.
Here in my city in Canada my cable provider (Rogers) supports native
IPv6 but Bell Fibe (fibre direct to the house) does not.
To make things more confusing, if I were to buy cable internet from a reseller (e.g. Teksavvy), they don't support IPv6 over cable. If I
were to buy fibre internet from Teksavvy, they do support IPv6 but
getting it to work involves using your own router, SFP module &
knowing how to configure it.
So Rogers Cable is the only "plug & play" IPv6 provider in my neighbourhood at the moment.
If I were to buy fibre internet from Teksavvy, they do support IPv6
but getting it to work involves using your own router, SFP module & knowing how to configure it.
Keep in mind, there is a fairly large population - and it's probably a bigger population than the people actually interested in IPv6 even -
that have no clue what an IPv4 or IPv6 address is, nor do they care if
you try to explain it to them, as long as they can stream their TV
shows and connect to the internet.. that is all that matters.
So to all sysops that still have that bit of pioneer spirit left in>
them end who are stuck with a provider that offers no native IPv6 I
say: Use the service of he.net to join the Fidonet IPv6 club!
While I agree with this, some sysops can't even configure their BBS or Golded properly. So if you care to hold their hand and walk them
through setting up a he.net tunnel, you're more than welcome to and I commend you for doing so.. but don't get upset when you point them to
all of your terriffic Fidonews articles and they get mad at you for pointing them to documentation. ;)
If I were to buy fibre internet from Teksavvy, they do support
IPv6 but getting it to work involves using your own router, SFP
module & knowing how to configure it.
This is how it works for me. My own router, two ISPs at the same time
and I know how to set it up. ;)
Of course. But I hope and expect that different statistics apply to
the Fidonet community. Joining Fidonet always required above
technical knowledge and although it may be easier than in the early
days, the average Fidonet sysop still is not an average internet
consumer.
He.net has stopped giving away T-shirts many years ago, but I still
have mine. I was very impressed that they managed to get it deliverd exactly on my birth day. A nice and welcome borthday present. :)
All in all 100 Fidonet sysops who's node supports IPv6 isn't really
that bad.
Considering that there is a substantial amount of dead wood in the nodelist. I regulatly test the systems in the IPv6 list for activity. Contrary to the nodelist in general the vast majority of systems in
the IPv6 list are active Fidonet systems.
This is how it works for me. My own router, two ISPs at the same time
and I know how to set it up. ;)
One of them supports IPv6 DHCP and advertise me
/64 network. From he.net I get /64 and /48
prefixes.
This is how it works for me. My own router, two ISPs at the same
time and I know how to set it up. ;)
By own hands. ;)
Mikrotik hAP ac3. It can do any port to be WAN port.
Simultaneously - no.
One of them supports IPv6 DHCP and advertise me /64 network.
From he.net I get /64 and /48 prefixes.
My two isp's provide me dynamic /64.
In addition to that, I have
static /64 and /48 from he.net.
Static is always nice. ;)
I think at this point applications are accepted as long as applicants
can make a binkp connection, and send a netmail.
But, I would like to also hope that most of us have some kind of
technical knowledge. I bet we'd both be surprised with what is really
the case, though. ;)
All in all 100 Fidonet sysops who's node supports IPv6 isn't really
that bad.
I agree. While there may be more nodelisted sysops than IPv6 systems, There's definitely less than 100 people that regularly participate in
the English speaking side of Fidonet these days.
So if the IPv6 list is bigger than that active participants list, I'd
say it's doing pretty dang good.
Static is always nice. ;)
Michiel van der Vlist wrote to Nick Boel <=-
I think at this point applications are accepted as long as applicants
can make a binkp connection, and send a netmail.
Yes that seems to be the case. But once they are accepted, they are seldom checked again. If checked, only for a responding server, not for responding to netmail. So we have many ghost systems in the nodelist...
Still... As I mentioned before, when promoting IPv6 in Fidonet I sometimes run into a brick wall. The first brick wall is that of
denial. No, denial is not a river in Egypt. (Roy Witt) IPv6 is a hype, there is noo need for it, IPv4 is functioning well and will remain to
do so, if not for the rest of the century, then at least for the coming decades.
IPv4 exhaustion may not be a serious problem for the incumbents in
parts of the world where IPv4 was historically issued as if it would
last forever. But for newcomers getting enough IPv4 to give all their potential customers a globally routable IPv4 address is a serious problem. So serious that some of the newcomers in the fast gowing fibre glass sector here in Europe have stopped doing it.
Yes that seems to be the case. But once they are accepted, they are
seldom checked again. If checked, only for a responding server, not
for responding to netmail. So we have many ghost systems in the
nodelist...
I agree. While there may be more nodelisted sysops than IPv6
systems, There's definitely less than 100 people that regularly
participate in the English speaking side of Fidonet these days.
Don't forget that these days many if not most messages in Fidonet are written in the Cyrillic alphabet...
Still... As I mentioned before, when promoting IPv6 in Fidonet I
sometimes run into a brick wall. The first brick wall is that of
denial. No, denial is not a river in Egypt. (Roy Witt) IPv6 is a
hype, there is noo need for it, IPv4 is functioning well and will
remain to do so, if not for the rest of the century, then at least
for the coming decades.
For those confronted with te reality of IPv4 exhaustion and the
shattered brick wall of denial, there is brick wall #2. Hang on to
IPv4 no matter what tricks it needs.
IPv4 exhaustion may not be a serious problem for the incumbents in
parts of the world where IPv4 was historically issued as if it would
last forever.
Yes that seems to be the case. But once they are accepted, they are
seldom checked again. If checked, only for a responding server, not
for responding to netmail. So we have many ghost systems in the
nodelist...
I'd say that is the fault of the NC. There are no dead nodes in my Net.
Static is always nice. ;)My fibre provider gives me a "persistent" IPv6
prefix. Technically it is not static, it is
dynamic, but they say by making it "persistent"
they follow best practice. It does not chance as
long as the router does not change. And indeed
it has not changed since my last router change.
My coax provider offers a dynamic IPv6 pefix. It
does not change very often, once or twice a
year, but there is no discernable pattern.
Sometimes with a firmware update but also
sometimes without any traceable trigger.
Almost sounds like the last famous words from flip phone owners
when smartphones arrived.
But not static. ;)
And you always will run into those walls. This is somewhat comparable
to sysops that still wish to run BBS software from the 80s/90s, that
don't and will never support things like a TZUTC kludge. It's
ultimately their choice.
For those confronted with te reality of IPv4 exhaustion and the
shattered brick wall of denial, there is brick wall #2. Hang on to
IPv4 no matter what tricks it needs.
Some people don't like change, until they're ultimately forced to do
so. If IPv4 is ever fully phased out, my guess is Fidonet will lose another big chunk of nodelisted sysops. Much like when darktech.org
and no-ip.com were abandoned, but on a bigger scale.
IPv4 exhaustion may not be a serious problem for the incumbents in
parts of the world where IPv4 was historically issued as if it
would last forever.
I imagine some of these bigger ISPs, mine included (Spectrum), bought
up a ton of IPv4 blocks because they saw all of this coming and could afford to take it all away from smaller ISPs for themselves. Heck,
there may even be enough IPv4 addresses at these large ISPs to go
around still, but they are hoarding them for their own (current and future) customers.
While I don't follow the situation very much, nor do I have any
experience with it (I have native "dynamic that never changes unless I change hardware" IPv4 that I have always had, as well as native
"dynamic that never changes unless I change hardware" IPv6), but do
you think these bigger ISPs rent out some IPv4 addresses to smaller
ISPs just so they can do said DSLite kind of setups?
Is this DSLite setup a bunch of private addresses not open to the
outside, that run off of one or a few public addresses so they
basically disable any incoming traffic so they can make more use of a single IPv4 address?
Mikrotik hAP ac3. It can do any port to be WAN port.
Simultaneously - no.
One of them supports IPv6 DHCP and advertise me /64 network.
My two isp's provide me dynamic /64.
In addition to that, I have
static /64 and /48 from he.net.
Static is always nice. ;)
Hello, Michiel van der Vlist.
On 26/07/2025 11.43 you wrote:
Hello Tommi, On Friday July 25 2025 19:34, you
wrote to Stas Mishchenkov:
Static is always nice. ;)
Not always. It depends... My fibre provider
(Delta) issues by default a "static" IPv4 address
to new customers. In the range 100.64.0.0/10.
I thought we were talking about ipv6..
Oddly enough, I still know a couple people with analog flip phones,
Enabled prefix-hint=2a0b:db80:85:9bca::/64. Let's see if this helps me
get the same prefix.
That will not happen tomorow. I may or may not live to see it. What
will happen in the foreseaable future and is already happening in sone parts of the Internet is that providers no longer offer a globally routable IPv4 address to their customers, they will have to make do
with CGNAT.
Mikrotik hAP ac3. It can do any port to be WAN port.
It's very similar to Linux, except the scripts, but I figured it out quickly.
Simultaneously - no.
Stability. If one of them doesn't work for some reason, I still have internet.
One of them supports IPv6 DHCP and advertise me /64 network.
Yes. We have what we have.
27 Jul 25 12:00, you wrote to Nick Boel:
That will not happen tomorow. I may or may not live to see it.
What will happen in the foreseaable future and is already
happening in some parts of the Internet is that providers no
longer offer a globally routable IPv4 address to their customers,
they will have to make do with CGNAT.
Most providers (well the main decent ones) here in Australia are
putting "new" customers onto CGNAT. Some do offer the ability to get a public routable address.
It's either by a phone call or a option on the isp's portal. They all charge $5-10 per month for a static IPv4 address. A dynamic one is
free.
With speed changes happening here on the NBN (National Broadband
Network) in September, 500mb is going to be the entry level speed for
the current 100mb price. One provider has gone with a one plan, one
price trick. I say trick as they are forcing people onto CGNAT with NO option to opt out, even if you're previous plan was with a public IP.
For 98% of customers this won't be a issue, but for the remaning it
will be.
Off all the ones that support IPv6, they are offering it for free.
With either dynamic or a static range.
Enabled prefix-hint=2a0b:db80:85:9bca::/64. Let's see if this helps
me
get the same prefix.
Enabled prefix-hint=2a0b:db80:85:9bca::/64. Let's see if this
helps me get the same prefix.
KCT, It's a local one.
Still?
Stability. If one of them doesn't work for some reason, I still have
internet.
Stability. If one of them doesn't work for some reason, I still
have internet.
Unfortunately, in my case the connection is lost once a month or two,
but for several hours, or even a day or more.
In my case, this does not work. Different ISPs enter my area from different directions.
In my case, this does not work. Different ISPs enter my area from
different directions.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 10:05:38 |
Calls: | 349 |
Files: | 6,078 |
Messages: | 232,991 |