1. Forum
  2. Fidonet
  3. IPV6

  • Another observation

    From Michiel van der Vlist@2:280/5555 to All on Sun Dec 4 22:59:16 2016
    Hello All,

    I run a website, but it does not have high priority as yu cab see when you go take a look. De webserver is a10+ year old freeby named key focus webserver. It does not have IPv6. To make available via IPv6, I used the netsh portproxy method that has been discussed here before.

    It did not work very well. It did not work very well. The website was available after a reboot but didn;t stay available for very long. Often just a few hours, sometimes a day or two.

    That was then when I had tunnels. But now that I have native IPv6, it has been stable for a week. My website has been reacheable over IPv6 all the time...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Tommi Koivula@2:221/6 to Michiel van der Vlist on Mon Dec 5 09:07:38 2016
    Hi Michiel.

    04 Dec 16 22:59, you wrote to All:

    I run a website, but it does not have high priority as yu cab see when you go take a look. De webserver is a10+ year old freeby named key focus webserver. It does not have IPv6. To make available via IPv6, I used the netsh portproxy method that has been discussed here before.

    It did not work very well. It did not work very well. The website was available after a reboot but didn;t stay available for very long. Often just a few hours, sometimes a day or two.

    That was then when I had tunnels. But now that I have native IPv6, it has been stable for a week. My website has been reacheable over IPv6 all the time...

    It has to be your XP, because I'm running portproxy at win2003 server without any problems.

    'Tommi

    ---
    * Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Mon Dec 5 11:44:24 2016
    Hello Tommi,

    On Monday December 05 2016 09:07, you wrote to me:

    That was then when I had tunnels. But now that I have native
    IPv6, it has been stable for a week. My website has been
    reacheable over IPv6 all the time...

    It has to be your XP, because I'm running portproxy at win2003 server without any problems.

    I think it is AICCU or the combination of AICCU and XP. Since I have disabled my SixXs tunnel, the portproxy works OK.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Tommi Koivula@2:221/1.1 to Michiel van der Vlist on Mon Dec 5 13:26:10 2016

    05 Dec 16 11:44, you wrote to me:

    That was then when I had tunnels. But now that I have native
    IPv6, it has been stable for a week. My website has been
    reacheable over IPv6 all the time...

    It has to be your XP, because I'm running portproxy at win2003 server
    without any problems.

    I think it is AICCU or the combination of AICCU and XP. Since I have disabled my SixXs tunnel, the portproxy works OK.

    Ok.. Never heard of AICCU, but after quick googling it seems to be sixxs-only crap. <g>

    I'm glad I never got sixxs account. ;)

    'Tommi

    ... he.net certified sage
    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0::4] (2:221/1.1)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Mon Dec 5 13:52:40 2016
    Hello Tommi,

    On Monday December 05 2016 13:26, you wrote to me:

    I think it is AICCU or the combination of AICCU and XP. Since I
    have disabled my SixXs tunnel, the portproxy works OK.

    Ok.. Never heard of AICCU, but after quick googling it seems to be sixxs-only crap. <g>

    AICCU is the demon that handles the tunnel endpoint and heartbeat for an AYIYA tunnel. The AYIYA (Anything In Anything) protoclo has the remarkable property that it can run from behind a NAT. Behind multiple NAT actually. No public IPv4 address required.

    It was written by Jeroen Massar but the program and the protocol was made public, so others can use it as well.

    I'm glad I never got sixxs account. ;)

    OK, ;-)

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Alexey Vissarionov@2:5020/545 to Michiel van der Vlist on Tue Dec 6 13:02:00 2016
    Good ${greeting_time}, Michiel!

    05 Dec 2016 11:44:24, you wrote to Tommi Koivula:

    That was then when I had tunnels. But now that I have native
    IPv6, it has been stable for a week. My website has been
    reacheable over IPv6 all the time...
    It has to be your XP, because I'm running portproxy at win2003
    server without any problems.
    MvdV> I think it is AICCU or the combination of AICCU and XP. Since
    MvdV> I have disabled my SixXs tunnel, the portproxy works OK.

    I'd rather use nginx instead.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: http://openwall.com/Owl (2:5020/545)
  • From Michiel van der Vlist@2:280/5555 to Alexey Vissarionov on Tue Dec 6 13:19:31 2016
    Hello Alexey,

    On Tuesday December 06 2016 13:02, you wrote to me:

    MvdV>> I think it is AICCU or the combination of AICCU and XP. Since
    MvdV>> I have disabled my SixXs tunnel, the portproxy works OK.

    I'd rather use nginx instead.

    In my case that would be shooting at a musquito with a canon.

    The netsh portproxy works for now. I admit it is a kludge and replacing the KeyFocus webserver with something that can handle IPv6 by itself would be the "proper" solution. It is not high on my list of priorities. It may or may not rise to the top some day. Or not...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)