I don't know how many of us are affected by this, but I got this message this morning (I'm still waiting to see how it affects my three SixXS tunnels):

Dear Bjorn Felten,

Unfortunately static is not always static and after almost 11 years of operation on 82.96.56.14 we are having to change the IPv4 address of
the sesto01 PoP to a new one due to network consolidations at Availo.

The new IPv4 address of sesto01 is: 83.140.32.162

There is a special brand new version of sixxsd running on sesto01 which
will use the latest IP destination as the PoP's side of the tunnel.

Thus the moment a packet to the new IP address arrives the PoP will
switch your tunnel over to use that address as a source address for
packets send to you.

For static tunnels one has to reconfigure the tunnel to point to
the new IP address.

For dynamic tunnels (AYIYA, heartbeat), a restart of AICCU will
refetch the details of the PoP which include the new PoP parameters.


Note that everything IPv6 remains the same.

Please complete this change as soon as possible.
We will deconfigure the old IPv4 address before the end of the week.

We apologize for the short notice, unfortunately work and travel are
a rather major drain in available time to properly implement and test
a seamless changeover system as has now been implemented in sixxsd.

Kind regards,
SixXS

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

Hello Bj”rn,

On Monday October 12 2015 14:47, you wrote to All:

I don't know how many of us are affected by this, but I got this
message this morning (I'm still waiting to see how it affects my three SixXS tunnels):

As I read it, it will only affect those that make use of the sesto01 POP. Since you are the only Fdionet IPv6 node in Scandinavia making use of SixXs, my guess is that you are the only one of us affected.

Unfortunately static is not always static and after almost 11 years of operation on 82.96.56.14 we are having to change the IPv4 address of
the sesto01 PoP to a new one due to network consolidations at Availo.

The new IPv4 address of sesto01 is: 83.140.32.162

One change in eleven yers. That's not bad...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: 2001:470:1f15:1117::1 (2:280/5555)

MvdV> As I read it, it will only affect those that make use of the sesto01
MvdV> POP. Since you are the only Fdionet IPv6 node in Scandinavia making use
MvdV> of SixXs, my guess is that you are the only one of us affected.

Yeah, I wasn't really sure about that. I seem to recall that you too recently had some issues with your SixXS tunnel.

I just wanted you all to know that there seems to be changes on the SixXS tunnels going on.

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

Hello Bj”rn,

On Monday October 12 2015 15:42, you wrote to me:

MvdV>> As I read it, it will only affect those that make use of the
MvdV>> sesto01 POP. Since you are the only Fdionet IPv6 node in
MvdV>> Scandinavia making use of SixXs, my guess is that you are the
MvdV>> only one of us affected.

Yeah, I wasn't really sure about that. I seem to recall that you
too recently had some issues with your SixXS tunnel.

Yes, there was a temporary glitch. Most likely not related.

I just wanted you all to know that there seems to be changes on the SixXS tunnels going on.

OK.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: 2001:470:1f15:1117::1 (2:280/5555)

On 10/12/15, Michiel van der Vlist pondered and said...

I don't know how many of us are affected by this, but I got this message this morning (I'm still waiting to see how it affects my thre SixXS tunnels):

As I read it, it will only affect those that make use of the sesto01
POP. Since you are the only Fdionet IPv6 node in Scandinavia making use
of SixXs, my guess is that you are the only one of us affected.

Agreed... Thanks Bjorn for the info :)

Best, Paul

--- Mystic BBS v1.10 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)