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


Присутствуют сообщения из эхоконференции IPV6 с датами от 31 Jul 11 14:37:00 до 03 Oct 24 21:46:09, всего сообщений: 7440
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 4377 из 7440 ============================================= IPV6 =
От   : Tony Langdon                     3:633/410          01 May 17 08:40:00
Кому : Ben Ritchey                                         01 May 17 08:40:00
Тема : Re: ipv6
FGHI : area://IPV6?msgid=2833.fido-ipv6@3:633/410+1d6bb477
На   : area://IPV6?msgid=1:393/68+5906464d
= Кодировка сообщения определена как: ASCII ==================================
Ответ: area://IPV6?msgid=1:393/68+59068105
==============================================================================
-=> Ben Ritchey wrote to All <=-

BR> My internet feed supports ipv4+6, what needs to be done to extend this
BR> to Fidonet, if anything?

You need an IPv6 capable mailer (I use binkd), and the hostname that is in the
nodelist needs an AAAA record, as well as an A record.  One caveat, you may
have a situation where FTN can use IPv6, but the BBS can't.  In this instance,
it's better to use different hostnames for FTN transfers (i.e. in the nodelist)
and user access.  This prevents IPv6 capable users getting lengthy delays in
connecting, if they use an IPv6 capable terminal.  How my system is setup is:

freeway.vkradio.com (A and AAAA records) - this is my nodelisted address.
binkd handles both IPv4 and IPv6 connections, and a couple of my feeds
routinely exchange mail over IPv6.

freeway.apana.org.au (A only) - this is my user accessible address.  It has
only an A record, so IPv6 capable terminals won't attempt a (futile) IPv6
connection.  I'm running Synchronet 3.16c, which does not support IPv6.

Of course, if both your mailer and BBS support IPv6, then you don't need the
second hostname.

On the BBS bachine itself, I use a manually configured static IP for both v4
and v6 (easier for me to recognise by eye), but SLAAC addresses could be used
instead, which is simpler to setup.

And odds are your router has a firewall that blocks incoming IPv6 connections
by default.  You will need to open the port that your mailer listens on (by
default, binkp connections are on TCP port 24554).  Many routers erroneously
call this "IPv6 port forwarding", it's actually a packet filter, and you're
telling the filter to let incoming binkp traffic pass.

Same for your OS, make sure any firewall (e.g. Windows Firewall on Windows, or
iptables on Linux) is configured to pass incoming binkp connections.


... At the end of the day, it gets dark.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)

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