Bjorn Felten wrote to All <=-
@MSGID: <56C22BB9.1625.2ipv6@tequilamockingbirdonline.net>
@TZ: 003c
Is it only my system, or have some other of you had problems reaching Bill's system (1:266/404) lately.
When he calls in it's IPv6 but not when I call out.
Is it only my system, or have some other of you had problems reaching Bill's system (1:266/404) lately.
When he calls in it's IPv6 but not when I call out.
..
--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)
It's fixed.... For some reason Comcast changed my IP and I had to
update my AAAA.
It's fixed.... For some reason Comcast changed my IP and I had to
update my
AAAA.
Hello Bill!
15 Feb 16 16:37, you wrote to Bj”rn Felten:
It's fixed.... For some reason Comcast changed my IP and I had to
update my
AAAA.
I've noticed that Comcast tends to change their IPv6 assignments occasionally
for no apparent reason. When I notice connects falling back to IPv4, I have
to log into my Linux box, use ifconfig to determine the newly assigned
IPv6
/64 prefix, adjust my "static" IPv6 address accordingly, and update the AAAA
record to re-enable full inbound IPv6 connectivity. It wouldn't surprise me
if this was done by Comcast to discourage the use of server applications
on
their residential service. However, it doesn't happen very often, so I
can
live with it.
Benny Pedersen wrote to Bill McGarrity <=-
15 Feb 2016 16:37, Bill McGarrity wrote to Bj.rn Felten:
It's fixed.... For some reason Comcast changed my IP and I had to
update my AAAA.
shit happens, oh finaly something to make a patch for in noip.com :=)
since it only support ipv4, and all my own ipv6 is static, that make
the patch only usefull for some
Andrew Leary wrote to Bill McGarrity <=-
15 Feb 16 16:37, you wrote to Bj.rn Felten:
It's fixed.... For some reason Comcast changed my IP and I had to
update my
AAAA.
I've noticed that Comcast tends to change their IPv6 assignments occasionally for no apparent reason. When I notice connects falling
back to IPv4, I have to log into my Linux box, use ifconfig to
determine the newly assigned IPv6 /64 prefix, adjust my "static" IPv6 address accordingly, and update the AAAA record to re-enable full
inbound IPv6 connectivity. It wouldn't surprise me if this was done by Comcast to discourage the use of server applications on their
residential service. However, it doesn't happen very often, so I can
live with it.
I've noticed that Comcast tends to change their IPv6 assignments occasionally for no apparent reason.
[..] It wouldn't surprise me if this was done by Comcast to discourage
the use of server applications on their residential service.
It wouldn't surprise me if this was done by Comcast to discourage the
use of server applications on their residential service. However, it
doesn't happen very often, so I can live with it.
I agree... just strange but one of the few things so you're right...
just have to live with it.
Michiel van der Vlist wrote to Bill McGarrity <=-
On Tuesday February 16 2016 10:10, you wrote to Andrew Leary:
It wouldn't surprise me if this was done by Comcast to discourage the
use of server applications on their residential service. However, it
doesn't happen very often, so I can live with it.
I agree... just strange but one of the few things so you're right...
just have to live with it.
Don't forget Hanlon's law...
Roger Nelson wrote to Andrew Leary <=-
I don't pretend to know how things work where you are, but I have a
static address, which I pay extra for, and it cannot be changed. On
the other hand, and as you probably know, a dynamic address may be
changed at any time.
Many of my colleagues and friends tried to convince me that what I have isn't worth it, but to me it is, and after all, it is my money. (-:
I've noticed that Comcast tends to change their IPv6 assignments occasionally for no apparent reason. When I notice connects falling
back to IPv4, I have to log into my Linux box, use ifconfig to
determine the newly assigned IPv6 /64 prefix, adjust my "static" IPv6 address accordingly, and update the AAAA record to re-enable full
inbound IPv6 connectivity. It wouldn't surprise me if this was done
by Comcast to discourage the use of server applications on their residential service. However, it doesn't happen very often, so I can
live with it.
I don't pretend to know how things work where you are, but I have a
static address, which I pay extra for, and it cannot be changed. On
the other hand, and as you probably know, a dynamic address may be
changed at any time.
Many of my colleagues and friends tried to convince me that what I
have isn't worth it, but to me it is, and after all, it is my money.
(-:
since it only support ipv4, and all my own ipv6 is static, that
make the patch only usefull for some
NoIp offers a dynamic update client for ipv4 but, according to them,
the ipv6 version is in the works.... for the past two years. Not
holding my breath.
Roger Nelson wrote to Andrew Leary <=-
I don't pretend to know how things work where you are, but I have a TL>RN> static address, which I pay extra for, and it cannot be changed. On TL>RN> the other hand, and as you probably know, a dynamic address may be TL>RN> changed at any time.
I have a static /64 that I pay for here, so I can assign static IPv6 addresses on servers on the LAN.
Many of my colleagues and friends tried to convince me that what I TL>RN> have isn't worth it, but to me it is, and after all, it is my money. (-:
Exactly. :) Static is worth it. In my case, it's only an extra
$10/month. :)
Roger Nelson wrote to Tony Langdon <=-
I have a static /64 that I pay for here, so I can assign static IPv6 addresses on servers on the LAN.
I have a temporary IPv6 address, but my IP is a little sluggish in implementing it. Until I know more about their situation, I'll defer
to them.
-:Many of my colleagues and friends tried to convince me that what I
have isn't worth it, but to me it is, and after all, it is my money.
Exactly. :) Static is worth it. In my case, it's only an extra $10/month. :)
It was FREE at one time. I think bellsouth did that back in the
Nineties when some smooth-talking woman called me and convinced me to upgrade my DSL to a faster speed. With that came the aforementioned
free static address and once hooked, I stayed hooked. It turned out to
be a wise decision after the change at DYNDNS and so I no longer needed the Updater program. The cost is $15/month here.
Nicholas Boel wrote to Bill McGarrity <=-
Or, you could just setup your system (not sure how you would do it on Windows) to create your own static IPv6 address for that specific
system. Mine happens to end in :f1d0:1:154:10, thanks to the other guys that came up with that idea. :)
Now that's cute, I like it! :) I've traditionally been using the same last digit for my IPv4 (private LAN) and IPv6 (public) addresses. If
I had read this message a few hours ago, I might have made my BBS IPv6
end in
:f1d0:3:633:410. :)
Nicholas Boel wrote to Tony Langdon <=-
Now that's cute, I like it! :) I've traditionally been using the same last digit for my IPv4 (private LAN) and IPv6 (public) addresses. If
I had read this message a few hours ago, I might have made my BBS IPv6
end in
:f1d0:3:633:410. :)
There's nothing stopping you, brother. :)
create your own static IPv6 address for that specific system.
Mine happens to end in :f1d0:1:154:10, thanks to the other
guys that came up with that idea. :)
Now that's cute, I like it! :) I've traditionally been using
the same last digit for my IPv4 (private LAN) and IPv6 (public)
addresses. If I had read this message a few hours ago, I might
have made my BBS IPv6 end in :f1d0:3:633:410. :)
Alexey Vissarionov wrote to Tony Langdon <=-
That idea was first published in FSP-1035, now FTS-5004 (http://ftsc.org/docs/fts-5004.001). Nowever, "hexspeak" is much older.
And yes, I've used it well before that publication :-)
Now that's cute, I like it! :) I've traditionally been using
the same last digit for my IPv4 (private LAN) and IPv6 (public)
addresses. If I had read this message a few hours ago, I might
have made my BBS IPv6 end in :f1d0:3:633:410. :)
Why not to set up additional address just for a Fidonet node?
That idea was first published in FSP-1035, now FTS-5004Yeah, there's a few words spely using hex and numbers that have
(http://ftsc.org/docs/fts-5004.001). Nowever, "hexspeak"
is much older.
appeared in IPv6 addresses over the years, like dead:beef :)
Yeah, there's a few words spely using hex and numbers that haveWords???
appeared in IPv6 addresses over the years, like dead:beef :)
Phrases!
gremlin@nb:~ > host -t aaaa hren.tebe.ru
hren.tebe.ru has IPv6 address 2a01:4f8:131:32aa:900d:f001:dead:f001
Alexey Vissarionov wrote to Tony Langdon <=-
Yeah, there's a few words spely using hex and numbers that have
appeared in IPv6 addresses over the years, like dead:beef :)
Words???
Phrases!
I'm Irish... so I follow Murphy's... ;)
Static IPv6 address (which I believe is what this conversation is
about)? I'm not so sure those can be purchased just yet.
Many of my colleagues and friends tried to convince me that what I
have isn't worth it, but to me it is, and after all, it is my money.
(-:
Completely agreed there. You do what you want with your money, and
I'd have to agree that if my dynamic IPv4 address didn't stay the
same for the past few years, I would have bought one too. :)
Yeah, there's a few words spely using hex and numbers that have
appeared in IPv6 addresses over the years, like dead:beef :)
On 16 Feb 16 09:58, Roger Nelson wrote to Andrew Leary:
I don't pretend to know how things work where you are, but I have a NB>RN> static address, which I pay extra for, and it cannot be changed. On NB>RN> the other hand, and as you probably know, a dynamic address may be NB>RN> changed at any time.
Static IPv6 address (which I believe is what this conversation is about)? I'm not so sure those can be purchased just yet.
Many of my colleagues and friends tried to convince me that what I NB>RN> have isn't worth it, but to me it is, and after all, it is my money. NB>RN> (-:
Completely agreed there. You do what you want with your money, and I'd
have to agree that if my dynamic IPv4 address didn't stay the same for
the past few years, I would have bought one too. :)
I see. I managed to get onto one of the first ISPs here that
offered native IPv6 addresses. When I first enabled IPv6, it was a
beta service, but now it's been production for a few years.
I've found static to be more convenient in a lot of ways, that even dynamic DNS can't help with. Nothing worse than having a SSH
session die because the modem reconnected. With a static IP,
that's less likely to happen (it would require a timeout, otherwise
the session will keep going). :)
... He who seeks a friend without a fault remains friendless ---
I'm pretty sure I have native IPv6 here, but it's unstable, or at
the very least, nowhere near as stable as my he.net tunnel. So I'll
stick with that for now.
Markus Reschke wrote to Tony Langdon <=-
Yeah, there's a few words spely using hex and numbers that have
appeared in IPv6 addresses over the years, like dead:beef :)
I've seen that one quite often. But I prefer a cup of coffee and a
piece of cake in a nice :cafe: ;)
Roger Nelson wrote to Tony Langdon <=-
I see. I managed to get onto one of the first ISPs here that
offered native IPv6 addresses. When I first enabled IPv6, it was a
beta service, but now it's been production for a few years.
I suspect Congress and the FCC are taking their time, especially this
year since it's an election year. I tire of the drama.
I've found static to be more convenient in a lot of ways, that even dynamic DNS can't help with. Nothing worse than having a SSH
session die because the modem reconnected. With a static IP,
that's less likely to happen (it would require a timeout, otherwise
the session will keep going). :)
Until the specified disconnect time, whatever its default is.
Markus Reschke wrote to Nicholas Boel <=-
The point is that your IP address is part of your ISP's allocation.
When you change your ISP you'll get a new IP address. But you can get
your own allocation (by becoming a member of a RIR) or PI address space (Provider Independent address assingment) which will stay with you independently from any ISP. It's all about routing ;)
Shawn Highfield wrote to Nicholas Boel <=-
My ISP offers it to everyone on DSL (Teksavvy) my problem is I don't currently have the extra funds to replace a perfectly good router with
one that supports IPV6. I've logged in directly from the "dsl modem"
and the testmyipv6.com page shows me as compatable.
My ISP offers it to everyone on DSL (Teksavvy) my problem is I don't currently have the extra funds to replace a perfectly good router with
one that supports IPV6. I've logged in directly from the "dsl modem"
and the testmyipv6.com page shows me as compatable.
My ISP offers it to everyone on DSL (Teksavvy) my problem is I don't currently have the extra funds to replace a perfectly good router with one that
supports IPV6. I've logged in directly from the "dsl modem" and the testmyipv6.com page shows me as compatable.
One day. ;)
Hello Andrew,
On Tuesday February 16 2016 04:04, you wrote to Bill McGarrity:
I've noticed that Comcast tends to change their IPv6 assignments
occasionally for no apparent reason.
Why not just ask them?
[..] It wouldn't surprise me if this was done by Comcast to
discourage the use of server applications on their residential
service.
That, or they are resetting their systems for maintenance or taking
care of child diseases. Maybe the IPv6 part of their network is still
a bit unstable.
If it is indeed to discourage running servers, I predict it will not
be effective. People have found work arounds for dynamic IPv4
adresses. Similar methods will emerge for IPv6 if ISPs are making a
habit of it.
Or, you could just setup your system (not sure how you would do it on Windows) to create your own static IPv6 address for that specific
system. Mine happens to end in :f1d0:1:154:10, thanks to the other guys that came up with that idea. :)
Hello Michiel!
16 Feb 16 17:00, you wrote to me:
Hello Andrew,
On Tuesday February 16 2016 04:04, you wrote to Bill McGarrity:
I've noticed that Comcast tends to change their IPv6 assignments
occasionally for no apparent reason.
Why not just ask them?
Based on past experience, it takes nearly an hour on the phone before
you get to someone in their support department that has any clue what
they are talking about, and that is with IPv4 issues. Most of their
staff seems to have no clue whatsoever what IPv6 is.
[..] It wouldn't surprise me if this was done by Comcast to
discourage the use of server applications on their residential
service.
That, or they are resetting their systems for maintenance or
taking care of child diseases. Maybe the IPv6 part of their
network is still a bit unstable.
This is possible. The assignments don't change very often, but I
haven't been able to nail down the exact time frame.
If it is indeed to discourage running servers, I predict it will
not be effective. People have found work arounds for dynamic IPv4
adresses. Similar methods will emerge for IPv6 if ISPs are making
a habit of it.
Agreed. A FidoNet node, even one carrying the full backbone and
filebone, doesn't put nearly the load on the network that streaming services such as NetFlix and the like do.
Andrew
--- GoldED+/LNX 1.1.5-b20160201
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
If you have an old WRT54GL lying around, you could follow my example
and flash it with OpenWrt.
Or, you could just setup your system (not sure how you would doI'm wondering if I can do this with the SIXXS tunnel address I have
it on Windows) to create your own static IPv6 address for that
specific system. Mine happens to end in :f1d0:1:154:10, thanks to
the other guys that came up with that idea. :)
been allocated? It's been a while since I've looked at all of this. [ponders]
Paul Hayton wrote to Nicholas Boel <=-
I'm wondering if I can do this with the SIXXS tunnel address I have
been allocated? It's been a while since I've looked at all of this. [ponders]
One could also argue that your router is not "perfectly good", it's obsolete. ;) Are there any firmware updates (manufacturer or third
party) that you could apply to get IPv6 support?
Yeah, I have the same ISP. My router was having some problems, so I
got one that was IPv6 capable <G>. Took a while to figure out how
to set it up, and I think Teksavvy must have changed something
between my first attempt and the successfull attempt (a couple of
months). After all it is still in Beta after all those years of
testing <G>
It's still a supported product, but hardware version 1.3 and of
course IPV6 was added for hardware version 3.x. That isn't a bad argument though maybe I'll bite the bullet the same TPLink unit with
ipv6 is just over $100 here so not a huge expense.
Yeah, I have the same ISP. My router was having some problems, so I
got one that was IPv6 capable <G>. Took a while to figure out how
to set it up, and I think Teksavvy must have changed something
between my first attempt and the successfull attempt (a couple of
months). After all it is still in Beta after all those years of
testing <G>
When I get the new router I know who to bother now. ;)
It's still a supported product, but hardware version 1.3 and ofTP-Link started to ship some routers with a locked firmware, i.e.
course IPV6 was added for hardware version 3.x. That isn't a bad
argument though maybe I'll bite the bullet the same TPLink unit
with ipv6 is just over $100 here so not a huge expense.
they are trying to suppress the installation of alternative
firmwares. That's done to comply with new FCC rules regarding
radio transmitters. There are similar rules in the EU.
Other manufactures will follow.
TP-Link started to ship some routers with a locked firmware, i.e.
they are trying to suppress the installation of alternative
firmwares. That's done to comply with new FCC rules regarding
radio transmitters. There are similar rules in the EU.
That affects only ISPs and, possibly, retailers.
Shawn Highfield wrote to Tony Langdon <=-
One could also argue that your router is not "perfectly good", it's obsolete. ;) Are there any firmware updates (manufacturer or third
party) that you could apply to get IPv6 support?
It's still a supported product, but hardware version 1.3 and of
course IPV6 was added for hardware version 3.x. That isn't a bad
argument though maybe I'll bite the bullet the same TPLink unit with
ipv6 is just over $100 here so not a huge expense.
... What do you get when you cross a Sysop with*^*(#%$&*@#%NO CARRIER
Shawn Highfield wrote to Joe Delahaye <=-
When I get the new router I know who to bother now. ;)
I'm wondering if I can do this with the SIXXS tunnel address I have
been allocated? It's been a while since I've looked at all of this. [ponders]
SiXXs by default gives you a /64 block that is routed through the
tunnel. If you will need more than that, you can request a /48 block.
In my case, I never found the need for more than a /64.
You should be able to manually configure your FidoNet machine using that prefix followed by :f1d0:3:770:100/64.
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 513 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 03:31:44 |
| Calls: | 8,292 |
| Calls today: | 5 |
| Files: | 15,520 |
| Messages: | 929,005 |