my updated INA for IPv6.
my updated INA for IPv6.
What will it be? I tried the ftn.* that you mentioned and it
resolved to IPv6 OK, but there were no mailer answering.
What will it be? I tried the ftn.* that you mentioned and it
resolved to IPv6 OK, but there were no mailer answering.
On 01-06-15 18:39, Andrew Leary wrote to Bj.rn Felten <=-
06 Jan 15 11:49, you wrote to Bill McGarrity:
What will it be? I tried the ftn.* that you mentioned and it
resolved to IPv6 OK, but there were no mailer answering.
I get "connection refused" for the current IPv6 address of ftn.tequilamockingbirdonline.net.
I do note that this IPv6 address is not the same one that was posted in Michiel's log segment earlier.
This is the current IPv6 I am getting:
2601:c:3a80:22a:6450:8391:63af:c72bI
Try this one..
2601:c:3a80:22a:89a0:1f59:d57d:61da
Let me know...
On 01-07-15 05:59, Andrew Leary wrote to Bill McGarrity <=-
07 Jan 15 00:29, you wrote to me:
Try this one..
2601:c:3a80:22a:89a0:1f59:d57d:61da
Let me know...
This one is working, so you need to update ftn.tequilamockingbirdonline.net to point to it.
Already done... thanks!!
2601:c:3a80:22a:89a0:1f59:d57d:61da
Let me know...
This one is working, so you need to update
ftn.tequilamockingbirdonline.net to point to it.
Already done... thanks!!
On 01-07-15 16:36, Michiel van der Vlist wrote to Bill McGarrity <=-
On Wednesday January 07 2015 08:46, you wrote to Andrew Leary:
2601:c:3a80:22a:89a0:1f59:d57d:61da
Let me know...
This one is working, so you need to update
ftn.tequilamockingbirdonline.net to point to it.
Already done... thanks!!
So Welcome to the Fido IPv6 Club!
On 01-07-15 16:36, Bj.rn Felten wrote to Bill McGarrity <=-
Already done... thanks!!
Now it works.
+ 07 Jan 16:33:26 [1400] outgoing session with ftn.tequilamockingbirdonline.net:24554 [2601:c:3a80:22a:89a0:1f59:d57d:61da]
Whatever you do: DON'T CHANGE ANYTHING NOW! 8-)
This one is working, so you need to update
ftn.tequilamockingbirdonline.net to point to it.
Already done... thanks!!
Don't plan on it.... but I do have to keep an eye on it and update the AAAA staticly for now till they come up with a utility that will do it dynamic, which is in the works.
Ehhh??? That makes no sense to me. One of the advantages of IPv6 is
that it would free us from this "dynamic IP" burden. IPv6 adresses are supposed to be STATIC. If your IPv6 address keeps changing, there is something that should not be as it is...
So Welcome to the Fido IPv6 Club!
Thank you sir. Got my reply from noip. They do not offer dynamic
IPv6 updates at this time so I have to keep an eye on it for any
changes. They say it's "in the works"...
On 01-07-15 19:49, Michiel van der Vlist wrote to Bill McGarrity <=-
On Wednesday January 07 2015 11:31, you wrote to me:
So Welcome to the Fido IPv6 Club!
Thank you sir. Got my reply from noip. They do not offer dynamic
IPv6 updates at this time so I have to keep an eye on it for any
changes. They say it's "in the works"...
Ehhh??? That makes no sense to me. One of the advantages of IPv6 is
that it would free us from this "dynamic IP" burden. IPv6 adresses are supposed to be STATIC. If your IPv6 address keeps changing, there is something that should not be as it is...
On 01-07-15 12:26, Andrew Leary wrote to Bill McGarrity <=-
Wednesday January 07 2015 08:46, Bill McGarrity wrote to Andrew Leary:
This one is working, so you need to update
ftn.tequilamockingbirdonline.net to point to it.
Already done... thanks!!
Confirmed. It looks like you are ready to be included on the IPv6
Nodes Listing. ;-)
On 01-07-15 17:16, Nicholas Boel wrote to Bill McGarrity <=-
On 07 Jan 15 12:50, Bill McGarrity wrote to Bj.rn Felten:
Don't plan on it.... but I do have to keep an eye on it and update the AAAA staticly for now till they come up with a utility that will do it dynamic, which is in the works.
Both my v4 and v6 addresses only seem to change when I do something to affect the MAC address, which in your case would have been unplugging
your router.
Don't unplug your router and you may not have to change your AAAA for quite some time. :)
Ehhh??? That makes no sense to me. One of the advantages of IPv6
is that it would free us from this "dynamic IP" burden. IPv6
adresses are supposed to be STATIC. If your IPv6 address keeps
changing, there is something that should not be as it is...
Well, then I guess they didn't get the memo about it being static
either. I thought it was just like Normally4.
I'll keep checking anyway for awhile.
Normally I never lose my IPv4 address as well unless I'm disconnected
from Comcast for 30+ minutes or so.
Either way I'm learning... :)
Normally I never lose my IPv4 address as well unless I'm disconnected
from Comcast for 30+ minutes or so.
Either way I'm learning... :)
Actually the user gets two prefixes, one for the WAN connection
(mostly a /64) and one for the LAN (/48, /56 or just a /64).
Let's say, it's not necessary for technical reasons. But if you take privacy issues into account things change ;)
My provider assigns a new IPv4 address when re-connecting. But there
seems to be a time window for the IPv6 LAN prefix.
In theory I should get new addresses every 6 months, if there would be
no outages or maintenance windows :)
Let's say, it's not necessary for technical reasons. But if you take
privacy issues into account things change ;)
My provider assigns a new IPv4 address when re-connecting. But there
seems to be a time window for the IPv6 LAN prefix.
In theory I should get new addresses every 6 months, if there would
be no outages or maintenance windows :)
My guess is something in the range of a few minutes.
My guess is something in the range of a few minutes.
That sounds really strange. What's your TTL?
I know for a fact that I must stay unconnected for more than 24
hours before I *may* get a new IP -- something that's only happened
three or four times within the last decade.
I fully agree. SLAAC is based on the NIC's MAC address, it's a dead give-away.
Cookies, super-cookies, cache spotting, the entropy of your
web browser and so on. The problem is that a lot of people think
dynamic prefixes create privacy, like their router would be sprinkled
with the security fairy's magic dust. My original remark was meant ironically.
<irony & facepalm>
My provider has a nice solution for customers who realy care about
their privacy. You can log into the customer support web interface and request a new prefix inside an 8 bit range. </irony & facepalm>
<irony & facepalm>
My provider has a nice solution for customers who realy care about
their privacy. You can log into the customer support web interface
and request a new prefix inside an 8 bit range. </irony & facepalm>
DTAG assigns a /56 to the customer.
The randomization gives you a new /56 inside the /48. I haven't
checked if they actually assign a /48 internally per customer and just give a /56 to the customer,
or if they assign all/multiple /56s of the /48 to customers.
Have you heard about their idea of prefix coloring for IPv6?
Have you heard about their idea of prefix coloring for IPv6?
You're lucky, it's a very bad idea. Prefix coloring uses some bits of
the prefix to categorize services, e.g. web, VoIP and video-on-demand.
The customer gets a dedicated prefix for each service. In the case of three services he'll get three prefixes. That design would make
filtering and QoS in the provider's routers more easy,
if supported. But the customer's devices have to select the right
prefix, i.e. the VoIP telephone has to select the VoIP prefix, the PC
the web prefix and so on. If you got a softphone on your PC the OS has
to select the VoIP prefix for the softphone and the web prefix for the
web browser. Do you see the problems?
On 01-06-15 11:49, Bjorn Felten wrote to Bill McGarrity <=-
@MSGID: <54ABD7E9.641.2ipv6@tequilamockingbirdonline.net>
@REPLY: <54AB327B.639.2ipv6@tequilamockingbirdonline.net>
@TZ: 003c
my updated INA for IPv6.
What will it be? I tried the ftn.* that you mentioned and it
resolved to IPv6 OK, but there were no mailer answering.
the ftn address is not in the nodelist yet.
On 01-23-15 02:18, Bjorn Felten wrote to Bill McGarrity <=-
the ftn address is not in the nodelist yet.
No worries mate. Like most binkd users I don't use the nodelist directly. I have your node manually changed to ftn.* and it still works like a charm, AFAICS.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 611 |
Nodes: | 10 (1 / 9) |
Uptime: | 49:32:31 |
Calls: | 9,831 |
Files: | 16,216 |
Messages: | 1,080,647 |