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


Присутствуют сообщения из эхоконференции IPV6 с датами от 31 Jul 11 14:37:00 до 03 Oct 24 21:46:09, всего сообщений: 7440
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 4046 из 7440 ============================================= IPV6 =
От   : Tony Langdon                     3:633/410          13 Jan 17 08:22:00
Кому : Michiel van der Vlist                               13 Jan 17 08:22:00
Тема : Re: What happens if a power supply lowers the voltage by 90%
FGHI : area://IPV6?msgid=2503.fido-ipv6@3:633/410+1cdd3917
На   : area://IPV6?msgid=2:280/5555+5877b440
= Кодировка сообщения определена как: CP866 ==================================
==============================================================================
-=> Michiel van der Vlist wrote to Richard Menedetter <=-

MvV> Indeed. "Normal" customers should not be bothered with these details.
MvV> My UPC has been telling me that customers would not notice the
MvV> transition to IPv6. They have been telling that since about 2010. Ans
MvV> indeed I haven't noticed anything until last summer. No IPv6, no
MvV> nothing. The they went quiet. And now I have IPv6. But they stopped
MvV> mentioing it on their official publications. So my IPv6 is
MvV> "unopfficial". It may be gone tomorrow.

As someone who transitioned officially to native dual stack IPv4/IPv6, I will
attest to the fact that I could not tell the difference, unless something was
borked on the other end, such as the time last year when I needed to access a
government website and couldn't, until I disabled IPv6 in my browser.  I did
send them feedback and the problem was quickly fixed.  There was also the time
that members of an international ham radio club complained that their website
was down, but I couldn't reproduce the problem.  Turns out that something broke
on IPv4 at the hosting provider, but I was accessing the site fine via IPv6.

I'm particular how I setup any hosting I have, to avoid issues with either
protocol.  This is the reason I have two hostnames for this BBS - one is IPv4
only for user/QWK access, as the BBS side is IPv4 only, the other hostname is
in the various nodelists I'm in, because my mailer is fully IPv6 capable
(binkd), and I want to encourage IPv6 adoption on Fidonet and the othernets I'm
on.

MvV> True. My syster lives in a home for the elderlt people. She has a
MvV> laptop, but no internet connection of her own. She uses the WiFi
MvV> network of the home. So she is behind a NAT. No IPv6 and so she only
MvV> has an IPv4 address in the private range. She does not know that. She
MvV> does not know what a NAT is, she does not know what a public IPv4
MvV> address is. People like her do not have to know.

My partner also doesn't notice that we have IPv6 capabilities, neither does the
occasional visitor who uses our wifi.  Everything "just works". :)

In some ways, IPv6 may be a victim of its own effective transition mechanisms.

I _do_ notice the difference, but that's because (1) I look, I have extensions
in my browser to report what IP version is being used, and (2) I like to host
servers.  I have 3 IPv4 and one IPv6 networks overlaid on the same wire here:

IPv4 LAN (RFC1918 addresses - default DHCP)
IPv4 public - a /29 for hosting servers, including the 2 BBSs.  Provided by a
VPN.
IPv4 AMPRnet/HAMnet - I have a /24 allocation in 44.x, I use a /29 for the LAN
and the rest is for RF and other networks.  I'm using IP in IP tunneling.
IPv6 global - I have a /56 IPv6 allocation, which I'm currently using a /64 of
for my LAN, and am considering experimenting with another /64 for ham radio.


... Because of BBSing, reading and writing actually pay off!
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

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