= Сообщение: 1621 из 7440 ============================================= IPV6 = От : Paul Hayton 3:770/100 19 Sep 15 13:29:09 Кому : Michiel van der Vlist 19 Sep 15 13:29:09 Тема : Re: Basic Steps / Checks to look at IPv6 FGHI : area://IPV6?msgid=3:770/100+47336ba4 На : area://IPV6?msgid=2:280/5555+55fc9a26 = Кодировка сообщения определена как: CP866 ================================== Ответ: area://IPV6?msgid=2:280/5555+55fd6abb ============================================================================== On 09/19/15, Michiel van der Vlist pondered and said...
Mv> This is how I set up my first tunnel. It is relatively easy. The Mv> endpoint will be behind a NAT, so your tunnel type must be AYAIYA. You Mv> need to set up AICCU and the TAP driver on the target machine. The
Sounds like the less painful approach, sadly I did not set that up with SixXS so at the moment I am down the harder but perhaps more rewarding path of trying to figure out Case 2
Mv> Case 2. Have the tunnel end at the router.
Mv> LAN. The disadvantage is that the router must support it and that you do Mv> not just need a tunnel, you need a subnet as well,
So the internet settings on my router seems to allow me to specify IPv6 addressing type. Currently set to SLAAC and on my status screen it just says 'connecting..' all the time. I know my ISP is not offering native IPv6 so that makes sence. The other options for IPv6 addressing type are DHCP and Static.
Static opens up options to load an IPv6 address, default gateway and primary and secondary DNS server. Do you think I could somehow use those settings with the SixXS POP?
There is also a section in the router for VPN and a sub section in that area called Tunnel.
If I enable it I can select my fibre WAN interface and the default tunnel type is DSLite. And the mode is automatic. If I uncheck automatic it allows me to enter a peer address. Again, unsure if any of this may help me connect to the SixXS POP?
I did try adding my POP as the peer address but it remains in a disconnected status with a tunnel type still as DSLite. :(
I have also bee using some web based tools to test if I can ping my static IP and found both IPv4 and IPv6 were not responding. I could not find any easy setting in the router to enable IMCP response. But I did find some success when I found a section in the router entitled DMZ.
When I added the BBS box as the DMZ machine I could get IPv4 ping replies to ICMP requests coming in from the WAN. But I'm also aware the machine was likely exposed to every other possible port query from the WAN side also. Not so good. The IPv6 ping tests did not work.
I did find an ACL setting in the router that allowed me to enable ICMP as a service type and set WAN as the access direction. IPv4 external pings now work but again IPv6 do not.
I'm hopeful that I set my AAAA record for agency.bbs.geek.nz correctly. I have it pointed to my IPv6 address according to SixXS which is 2001:4428:200:16c::2
When I do a TraceRoute IPv6 using a web based service I see the following now
TraceRoute IPv6 Output:
traceroute to agency.bbs.geek.nz (2001:4428:200:16c::2), 30 hops max, 40 byte packets 1 2a02:348:82::1 (2a02:348:82::1) 0.312 ms 0.353 ms 0.545 ms 2 te0-22.cr1.nkf.as49685.net (2001:4cb8:40b:1::1d01) 0.883 ms 0.912 ms 0.952 ms 3 30gigabitethernet1-3.core1.ams1.he.net (2001:7f8:1::a500:6939:1) 0.375 ms 0.389 ms 0.375 ms 4 100ge9-1.core1.lon2.he.net (2001:470:0:2d0::1) 8.034 ms 11.291 ms 7.444 ms 5 100ge1-1.core1.nyc4.he.net (2001:470:0:2cf::2) 73.170 ms 73.152 ms 73.125 ms 6 100ge7-2.core1.chi1.he.net (2001:470:0:298::1) 118.882 ms 118.905 ms 118.882 ms 7 10ge5-7.core1.mci3.he.net (2001:470:0:270::2) 111.684 ms 108.207 ms 111.638 ms 8 10ge15-4.core1.den1.he.net (2001:470:0:240::1) 113.437 ms 113.388 ms 113.360 ms 9 10ge13-1.core1.lax2.he.net (2001:470:0:15d::2) 158.627 ms 158.579 ms 158.558 ms 10 acs-data-llc.10gigabitethernet12.switch2.lax2.he.net (2001:470:1:2fa::2) 144.306 ms 141.450 ms 141.574 ms 11 ge0-0-0-809.v4akl1.acsdata.co.nz (2001:4428:1:329::4) 268.636 ms 268.322 ms 266.428 ms 12 ge0-0-801.v4wlg0.acsdata.co.nz (2001:4428:0:321::1) 276.634 ms 276.643 ms 275.940 ms 13 nzwlg01.sixxs.net (2001:4428:0:401::122) 274.754 ms 277.472 ms 274.626 ms 14 gw-365.wlg-01.nz.sixxs.net (2001:4428:200:16c::1) 274.548 ms 273.527 ms 273.473 ms 15 * * * 16 * * * 17 * * * 18 * * *
So it seems I get as far as the NZ based POP but no further. Humm..
Best, Paul
-- Agency BBS, New Zealand | bbs.geek.nz | telnet: agency.bbs.geek.nz:23
