• binkd completed...

    From Bill McGarrity@1:266/404 to All on Mon Jan 5 19:55:23 2015
    Good day all...

    Just a head's up, I am done with the conversion over to binkd and hopefully the new nodelist this week will have my updated INA for IPv6.

    Thanks to all who helped me along the way on getting this thing setup. I always used .MSG style and it takes some time and twisted logic in figuring out FLO... but I have a pretty good grasp on it now...

    Enjoy!!



    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: 6697
    Radio: radio.tequilamockingbirdonline.net:8010/live

    ... Look TWICE.... Save a life.... Motorcycles are EVERYWHERE!!
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Björn Felten@2:203/2 to Bill McGarrity on Tue Jan 6 11:49:20 2015
    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.

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://felten.yi.org (2:203/2)
  • From Michiel van der Vlist@2:280/5555 to Björn Felten on Tue Jan 6 12:01:30 2015
    Hello Bj”rn,

    On Tuesday January 06 2015 11:49, you wrote to Bill McGarrity:

    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.

    There is a mailer answering at 2601:c:3a80:22a:89a0:1f59:d57d:61da though. So I too wonder what is going on with all these addresses...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Tue Jan 6 15:40:33 2015
    MvdV> So I too wonder what is going on with all these addresses...

    Another node range, with a confusing number of addresses, that changes ever so often, is 221/*.

    Does anyone know what URL to use to get IPv6 connections there nowadays?

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://felten.yi.org (2:203/2)
  • From Andrew Leary@1:320/219 to Björn Felten on Tue Jan 6 18:39:41 2015
    Hello Bjorn!

    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.

    Andrew

    --- GoldED+/LNX 1.1.5-b20130910
    * Origin: Phoenix BBS * phoenix.bnbbbs.net:2323 (1:320/219)
  • From Bill McGarrity@1:266/404 to Andrew Leary on Tue Jan 6 20:05:00 2015
    On 01-06-15 18:39, Andrew Leary wrote to Bj.rn Felten <=-

    Hiya Andrew...

    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.

    This is the current IPv6 I am getting:

    2601:c:3a80:22a:6450:8391:63af:c72bI


    I do note that this IPv6 address is not the same one that was posted in Michiel's log segment earlier.

    I know from I that point I had to disconnect my router and it is possible my IP gave me a different one. But as of now, I have a utility here that will update the DNS if my IP changes. I know it works for IPv4 and I've posted a message to them if it works for IPv6 as well.

    I'll keep you posted...


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Andrew Leary@1:320/219 to Bill McGarrity on Tue Jan 6 23:50:51 2015
    Hello Bill!

    06 Jan 15 20:05, you wrote to me:

    This is the current IPv6 I am getting:

    2601:c:3a80:22a:6450:8391:63af:c72bI

    This IPv6 address yields "connection refused" when trying to connect via BinkP.

    Regards,

    Andrew

    --- GoldED+/LNX 1.1.5-b20130910
    * Origin: Phoenix BBS * phoenix.bnbbbs.net:2323 (1:320/219)
  • From Bill McGarrity@1:266/404 to Andrew Leary on Wed Jan 7 00:29:33 2015
    Re: binkd completed...
    By: Andrew Leary to Bill McGarrity on Tue Jan 06 2015 23:50:51

    Hiya Andrew....

    Try this one..

    2601:c:3a80:22a:89a0:1f59:d57d:61da

    Let me know...



    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: 6697
    Radio: radio.tequilamockingbirdonline.net:8010/live

    ... Look TWICE.... Save a life.... Motorcycles are EVERYWHERE!!
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Andrew Leary@1:320/219 to Bill McGarrity on Wed Jan 7 05:59:12 2015
    Hello Bill!

    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.

    Regards,

    Andrew

    --- GoldED+/LNX 1.1.5-b20130910
    * Origin: Phoenix BBS * phoenix.bnbbbs.net:2323 (1:320/219)
  • From Bill McGarrity@1:266/404 to Andrew Leary on Wed Jan 7 08:46:00 2015
    On 01-07-15 05:59, Andrew Leary wrote to Bill McGarrity <=-

    Hiya Andrew...

    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!!


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Björn Felten@2:203/2 to Bill McGarrity on Wed Jan 7 16:36:27 2015
    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-)

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://felten.yi.org (2:203/2)
  • From Michiel van der Vlist@2:280/5555 to Bill McGarrity on Wed Jan 7 16:36:34 2015
    Hello Bill,

    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!


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Bill McGarrity@1:266/404 to Michiel van der Vlist on Wed Jan 7 11:31:00 2015
    On 01-07-15 16:36, Michiel van der Vlist wrote to Bill McGarrity <=-

    Hiya Michiel...

    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!

    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"...

    Enjoy!!


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Björn Felten on Wed Jan 7 12:50:00 2015
    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-)

    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.

    Enjoy!!


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Andrew Leary@1:320/119 to Bill McGarrity on Wed Jan 7 12:26:22 2015
    Hello Bill!

    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. ;-)

    Andrew

    ---
    * Origin: Bits & Bytes BBS * V.Everything! * 860/535-4284 (1:320/119)
  • From Nicholas Boel@1:154/701 to Bill McGarrity on Wed Jan 7 17:16:52 2015
    Hello Bill,

    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. :)

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20130910
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)
  • From Nicholas Boel@1:154/701 to Michiel van der Vlist on Wed Jan 7 17:19:04 2015
    Hello Michiel,

    On 07 Jan 15 19:49, Michiel van der Vlist wrote to Bill McGarrity:

    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...

    If you notice, his v6 address only changed for a short period while he kept rebooting his router. Now it seems to have gone back to one of the originals, which is probably the one based on his MAC address.

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20130910
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)
  • From Michiel van der Vlist@2:280/5555 to Bill McGarrity on Wed Jan 7 19:49:27 2015
    Hello Bill,

    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...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Bill McGarrity@1:266/404 to Michiel van der Vlist on Wed Jan 7 19:57:00 2015
    On 01-07-15 19:49, Michiel van der Vlist wrote to Bill McGarrity <=-

    Hiya Michiel...

    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...

    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... :)

    Thanks!!


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Andrew Leary on Wed Jan 7 19:58:00 2015
    On 01-07-15 12:26, Andrew Leary wrote to Bill McGarrity <=-

    Hiya Andrew...

    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. ;-)

    :)


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Bill McGarrity@1:266/404 to Nicholas Boel on Thu Jan 8 02:18:00 2015
    On 01-07-15 17:16, Nicholas Boel wrote to Bill McGarrity <=-

    Hiya Nick...


    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. :)

    Good to know... :)


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    --- SBBSecho 2.12-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Michiel van der Vlist@2:280/5555 to Bill McGarrity on Thu Jan 8 12:13:34 2015
    Hello Bill,

    On Wednesday January 07 2015 19:57, you wrote to me:

    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 do not know what you mean by "Normally4". Address assigment for IPv4 is very different from that of IPv6 however. With IPv4 you get ONE address from your ISP. That address has to be shared by every device on your LAN that uses the internet. The mechanism for sharing is NAT.

    With IPv6 you get a RANGE of addresses. Large enough to give every device on your LAN its own globally routable IPv6 address. The first 64 bits of the range is called the prefix. Actually the range is larger than that, but we will ignore that for the moment. The ISP communicates the range to the customer's router by prefix delegation.

    The last 64 bits of the IPv6 address is called the host part. They are assigned locally. Either by DHCP6, SLAAC or manually by the user. The ISP has no part in that.

    Correct me if I am wrong, but what I have seen from the addresses that you published is that they all had the same prefix. Only the last 64 bits changed. This means that these address changes occur locally. It is not a dynamic address coming from your ISP.

    In theory IPv6 addresses could be dynamic, but in that case it would be the prefix that changes. This does not seem to be the case with you.

    Dynamic addresses were used with IPv4 to conserve addresses. An IP adrees could be assigned to another user when the previous one logged out. This made sense in the age of dial up IP. It does not make sense with IPv6 with (semi) permanent connections and no shortage of addresses.

    I'll keep checking anyway for awhile.

    Keep doing that.

    Normally I never lose my IPv4 address as well unless I'm disconnected
    from Comcast for 30+ minutes or so.

    My IPv4 address is also dynamic in theory. In practise it is static. I do not know how long I have to disconnect to lose it, but it is longer than a day.

    My IP addresses are tunnels, they are static.

    Either way I'm learning... :)

    We all are. ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Markus Reschke@2:240/1661 to Michiel van der Vlist on Thu Jan 8 13:49:10 2015
    Hi Michiel!

    Jan 08 12:13 2015, Michiel van der Vlist wrote to Bill McGarrity:

    MvdV> With IPv6 you get a RANGE of addresses. Large enough to give every
    MvdV> device on your LAN its own globally routable IPv6 address. The
    MvdV> first 64 bits of the range is called the prefix. Actually the range
    MvdV> is larger than that, but we will ignore that for the moment. The
    MvdV> ISP communicates the range to the customer's router by prefix
    MvdV> delegation.

    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).

    MvdV> Dynamic addresses were used with IPv4 to conserve addresses. An IP
    MvdV> adrees could be assigned to another user when the previous one
    MvdV> logged out. This made sense in the age of dial up IP. It does not
    MvdV> make sense with IPv6 with (semi) permanent connections and no
    MvdV> shortage of addresses.

    Let's say, it's not necessary for technical reasons. But if you take privacy issues into account things change ;)

    Normally I never lose my IPv4 address as well unless I'm disconnected
    from Comcast for 30+ minutes or so.

    MvdV> My IPv4 address is also dynamic in theory. In practise it is
    MvdV> static. I do not know how long I have to disconnect to lose it, but
    MvdV> it is longer than a day.

    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 :)

    Either way I'm learning... :)

    MvdV> We all are. ;-)

    Very true!

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Michiel van der Vlist@2:280/5555 to Markus Reschke on Fri Jan 9 01:22:29 2015
    Hello Markus,

    On Thursday January 08 2015 13:49, you wrote to me:

    MvdV>> With IPv6 you get a RANGE of addresses. Large enough to give
    MvdV>> every device on your LAN its own globally routable IPv6
    MvdV>> address. The first 64 bits of the range is called the prefix.
    MvdV>> Actually the range is larger than that, but we will ignore that
    MvdV>> for the moment. The ISP communicates the range to the
    MvdV>> customer's router by prefix delegation.

    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).

    I didn't want to make it too complicated, so I ignored that as it wasn't relevant for the issue at hand: his changing IPv6 address. And I am still puzzled about it as it is obviously not an ISP related issue, the prefix does not change...

    MvdV>> Dynamic addresses were used with IPv4 to conserve addresses. An
    MvdV>> IP address could be assigned to another user when the previous
    MvdV>> one logged out. This made sense in the age of dial up IP. It
    MvdV>> does not make sense with IPv6 with (semi) permanent connections
    MvdV>> and no shortage of addresses.

    Let's say, it's not necessary for technical reasons. But if you take privacy issues into account things change ;)

    Dynamic addresses are a nuisance when running servers and they are of very little help for preserving privacy. It is of no use against governments or the NSA. It is also of little help against Google et al. There are so many other ways to identify a user than just the IP number.

    My provider assigns a new IPv4 address when re-connecting. But there
    seems to be a time window for the IPv6 LAN prefix.

    Any idea how long?

    In theory I should get new addresses every 6 months, if there would be
    no outages or maintenance windows :)

    Why a new prefix every six month? For privacy that is far too long a period to be of use.
    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Markus Reschke@2:240/1661 to Michiel van der Vlist on Fri Jan 9 11:59:58 2015
    Hi Michiel!

    Jan 09 01:22 2015, Michiel van der Vlist wrote to Markus Reschke:

    Let's say, it's not necessary for technical reasons. But if you take
    privacy issues into account things change ;)

    MvdV> Dynamic addresses are a nuisance when running servers and they are
    MvdV> of very little help for preserving privacy. It is of no use against
    MvdV> governments or the NSA. It is also of little help against Google et
    MvdV> al. There are so many other ways to identify a user than just the
    MvdV> IP number.

    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.

    My provider assigns a new IPv4 address when re-connecting. But there
    seems to be a time window for the IPv6 LAN prefix.

    MvdV> Any idea how long?

    My guess is something in the range of a few minutes.

    In theory I should get new addresses every 6 months, if there would
    be no outages or maintenance windows :)

    MvdV> Why a new prefix every six month? For privacy that is far too long
    MvdV> a period to be of use.

    <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>

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Björn Felten@2:203/2 to Markus Reschke on Fri Jan 9 13:19:42 2015
    MvdV>> Any idea how long?

    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.

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://felten.yi.org (2:203/2)
  • From Markus Reschke@2:240/1661 to Bj÷rn Felten on Fri Jan 9 14:10:58 2015
    Hi Björn!

    Jan 09 13:19 2015, Björn Felten wrote to Markus Reschke:

    My guess is something in the range of a few minutes.

    That sounds really strange. What's your TTL?

    Which TTL do you mean?

    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.

    It's simply how the provider configured RADIUS/DIAMETER/DHCPv6/etc, and each provider has his own ideas about that.

    cu,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Michiel van der Vlist@2:280/5555 to Markus Reschke on Sat Jan 10 01:24:34 2015
    Hello Markus,

    On Friday January 09 2015 11:59, you wrote to me:

    MvdV>> Dynamic addresses are a nuisance when running servers and they
    MvdV>> are of very little help for preserving privacy. It is of no use
    MvdV>> against governments or the NSA. It is also of little help
    MvdV>> against Google et al. There are so many other ways to identify
    MvdV>> a user than just the IP number.

    I fully agree. SLAAC is based on the NIC's MAC address, it's a dead give-away.

    Indeed it is. But when you are running servers - like we all do in Fdionet - there is no way to hide.

    And the so called privacy extensions are a joke as well. It may help to avoid being followed when traveling with a mobile device, but for a fixed connection, the prefix will lead to your home anyway.

    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.

    Ah, I missed the irony. Sorry...

    MvdV>> Why a new prefix every six month? For privacy that is far too
    MvdV>> long a period to be of use.

    <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>

    An 8 bit range? But that's within the /56 or/48 that you would have been assigned anyway.

    I can see they really thought about that...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Markus Reschke@2:240/1661 to Michiel van der Vlist on Sat Jan 10 14:06:04 2015
    Hi Michiel!

    Jan 10 01:24 2015, Michiel van der Vlist wrote to Markus Reschke:

    <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>

    MvdV> An 8 bit range? But that's within the /56 or/48 that you would have
    MvdV> been assigned anyway.

    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.

    MvdV> I can see they really thought about that...

    Have you heard about their idea of prefix coloring for IPv6?

    Regards,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Michiel van der Vlist@2:280/5555 to Markus Reschke on Sun Jan 11 10:47:51 2015
    Hello Markus,

    On Saturday January 10 2015 14:06, you wrote to me:

    MvdV>> An 8 bit range? But that's within the /56 or/48 that you would
    MvdV>> have been assigned anyway.

    DTAG assigns a /56 to the customer.

    Cheapskates! ;-)

    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,

    In that case, why don't they just make the whole /48 available to the customer and let the customer play around with the subnets any way he wants?

    or if they assign all/multiple /56s of the /48 to customers.

    In the latter case, that randomization of the new /56 is limited to those that are still free within the /48...

    MvdV>> I can see they really thought about that...

    Have you heard about their idea of prefix coloring for IPv6?

    Vaguely. It was one of the things that I filed under: "Hmmm.. if this turns out to be a good idea, I will have a look at it when I get a rountoit.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Markus Reschke@2:240/1661 to Michiel van der Vlist on Sun Jan 11 12:13:40 2015
    Hi Michiel!

    Jan 11 10:47 2015, Michiel van der Vlist wrote to Markus Reschke:

    Have you heard about their idea of prefix coloring for IPv6?

    MvdV> Vaguely. It was one of the things that I filed under: "Hmmm.. if
    MvdV> this turns out to be a good idea, I will have a look at it when I
    MvdV> get a rountoit.

    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?

    Regards,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Michiel van der Vlist@2:280/5555 to Markus Reschke on Sun Jan 11 15:21:34 2015
    Hello Markus,

    On Sunday January 11 2015 12:13, you wrote to me:

    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,

    It would also make it easier for them to create wormholes to bypass any legally imposed net neutrality. :-(

    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?

    I can see several. For starters: what prefix do I use for binkp?

    I too think this is a bad idea. An IP address should point to an interface, not to a service. It is mixing layers.


    Cheers, Michiel

    --- GoldED+/W32-MINGW 1.1.5-b20110320
    * Origin: 2001:470:1f15:1117::1 (2:280/5555)
  • From Bill McGarrity@1:266/404 to Björn Felten on Tue Jan 6 08:39:00 2015
    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. I'm not sure the address without the ftn will resolve to IPv6. I've sent email to NC advising hw the him to make the change... :) I know it works as Michiel has connected. :)

    i need to do a little more reading how it uses the nodelist. Whole new learning curve with this mailer... :)


    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!
    === MultiMail/Win32 v0.50
    --- SBBSecho 2.27-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Björn Felten@2:203/2 to Bill McGarrity on Fri Jan 23 02:18:04 2015
    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.

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://felten.yi.org (2:203/2)
  • From Bill McGarrity@1:266/404 to Björn Felten on Thu Jan 22 23:06:00 2015
    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.

    Everything is up to date now.. :)


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!! Motorcycles are Everywhere!!!
    === MultiMail/Win32 v0.50
    --- SBBSecho 2.27-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)