Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции IPV6
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции IPV6 с датами от 31 Jul 11 14:37:00 до 08 Oct 24 18:47:55, всего сообщений: 7442
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 605 из 7442 ============================================== IPV6 =
От   : Michiel van der Vlist            2:280/5555         30 Apr 14 10:59:05
Кому : Scott Little                                        30 Apr 14 10:59:05
Тема : test me
FGHI : area://IPV6?msgid=2:280/5555+5360c112
На   : area://IPV6?msgid=3:712/848+53606133
= Кодировка сообщения определена как: CP850 ==================================
Ответ: area://IPV6?msgid=3:712/848+536108ac
==============================================================================
Hello Scott,

On Wednesday April 30 2014 12:34, you wrote to me:

MV>> [2002:cbce:df98::4]... 23:03 [8688] connected + 23:03 [8688]
MV>> outgoing session with 2002:cbce:df98::4 Welcome to the club!

SL> Thanks!

You'r the first in Z3.

MV>> How about outgoing?

SL> Outgoing I probably won't bother with until either we start getting
SL> enough IPv6 only nodes to cause trouble, or until my ISP goes native
SL> IPv6 (which will be sometime around the heat death of the universe).

I am a bit surprised the ISPs down undah don't put more pressure on it. APNIC was the first RIR to deplete its IPv4 stock three years ago. By now IPv4 adresses should be scarse in the ASIAN-PACIFIC region.

SL> Do I remember correctly there being talk about a flag for v6-only
SL> nodes?

An FTSC proposal was filed. Now I will have to convince Ward to allow the INO4 flag it for 2:280/5006.

SL> ATM I'm using 6to4,

6to4, Arghhh, that explains a few things.

SL> which for some reason my ISP managed to partially break

You can blame your ISP for choosing 6to4 as their official method for IP46, you can not blame them for breaking it. 6to4 is broken all by itself! Hunt the net for "problems with 6to4" and you wil get lots of articles.

The brokennes of 6to4 is the main reason why most OS's/applications first try IPv4 instead of IPv6. Windows normally tries IPv6 first, but if the destination is a 6to4 tunnel, it only tries IPv6 if Ipv4 fails.

That explains why you did nog get any IPv6 connect until you asked for it and me and others sepcifically forced IPv6 to make the connection.

SL>  - it works from some of my IPs but not others (confirmed on
SL> their end).  How they managed the screw up routing for half the IPs in
SL> the same subnet to their own 6to4 gateway is beyond me.  Hopefully
SL> they don't break it any more.

SL> When I get a round tuit I'll set up their 6RD tunnel as well.

Forget about 6RD.

I suggest you get a decent 6in4 or AYIYA tunnel from a decent tunnel broker like he.net or SixXs.


Cheers, Michiel

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

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.046552 секунды