= Сообщение: 1655 из 7440 ============================================= IPV6 = От : Paul Hayton 3:770/100 22 Sep 15 20:08:17 Кому : Michiel van der Vlist 22 Sep 15 20:08:17 Тема : Debugging PING FGHI : area://IPV6?msgid=3:770/100+4736a108 На : area://IPV6?msgid=2:280/5555+5600568c = Кодировка сообщения определена как: CP866 ================================== Ответ: area://IPV6?msgid=2:280/5555+56011e56 ============================================================================== On 09/21/15, Michiel van der Vlist pondered and said...
Mv> If you have another machine that is IPv6 capable you could connect it to Mv> the LAN and than you will see it has IPv6 adresses, In particular you Mv> will see a links local address starting with fe80. If you see that, you Mv> could try to ping the fe80 address on your BBS machine. Yuo could also Mv> try to ping6 agency.bbs.geek.nz. Mv> Mv> If that works it is not a local problem. If it does not work, it is a Mv> local problem that should be fixed first.
Well I can ping the BBS system across the LAN using it's fe80 address from a Win 10 system also on the LAN. The fe80 address I can ping is the one associated with the physical network card that handles ipv4 also.
If I try and ping the fe80 address reported by the secondary network connection created by the TAP driver this fails to ping and ping reports destination host unreachable then resuest timed out etc. Should that be the case?
I also note that the activity stats for the secondary network connection show lots of bytes sent byt 0 received.
Best, Paul
-- Agency BBS, New Zealand | bbs.geek.nz | telnet: agency.bbs.geek.nz:23
