SixXS::Sunset 2017-06-06

Testing tunnel on several machines
[us] Shadow Hawkins on Monday, 08 December 2008 00:03:26
I am trying to get direct ipv6 access to some wireless motes, which are now internet accessible through vista v4tov6 forwarding (see http://dakx.com:8080 for the setup, the motes are ports 8081-8083). I don't want to disrupt the existing setup too much, so am testing on another vista laptop and xp desktop. My home network connects through a NetGear WGR614v6 router and Xytel DSL Modem. The DMZ had been set to a linux box, but apparently I had to change that to get the tunnel working. After appropriate port forwarding the linux web and mail servers seem to be working again. Setting the DMZ to xp, the tunnel seems to work ok, the AYIYA diagnostic runs with no errors, and it can access kame, ipv6.google.com, and an ipv6 newsservers for example. At the same time, the tunnel seems working on the vista box but with no ip6 nameserver (direct addresses work e.g. http://[2001:200:0:8002:203:47ff:fea5:3085]/ gets the dancing turtle). One thing that is weird, on both machines the AICCU status shows only sent packets, none received. Can they be issuing ipv6 requests and receiving ip4 packets? Before I do any more experimentation, I'd like to know is it OK to have two machines with the same local endpoint? Will I lose points for screwing around too much? I would also appreciate any advice on how to connect the motes. Can it be done in ipv6 without registering a subnet? I have access to the dakx.com DynDNS name server and can make AAAA records there.
Testing tunnel on several machines
[ch] Jeroen Massar SixXS Staff on Monday, 08 December 2008 00:11:11
AYIYA doesn't require any 'port forwarding', as NAT will already take care of that. (In case of proto-41, it is 'protocol forwarding' of course, which the DMZ setting does).
One thing that is weird, on both machines the AICCU status shows
only sent packets, none received. Can they be issuing ipv6
requests and receiving ip4 packets?
What "AICCU status" shows this? I am not aware of any status thing inside AICCU that shows packets sent/received counters. To really diagnose this, I guess you will have to show us routes/interfaces/firewall tables etc. A Wireshark dump is of course also useful for you to figure out what is going on.
I would also appreciate any advice on how to connect the motes.
Can it be done in ipv6 without registering a subnet?
Then you need to do either IPv6 NAT (which is simply evil) or you would need to setup an application proxy. The latter probably is the correct thing to do unless your 'motes' (You didn't tell what they actually are, what they do etc etc) can really talk IPv6 themselves, if they talk IPv6, get a subnet and hook them all up, that is what IPv6 is supposed to be for. (Proper firewalling is most likely advised then though. One sidenote there: at the moment the Windows edition of AICCU can't do subnets in combination with AYIYA. The linux version does work.
Testing tunnel on several machines
[us] Shadow Hawkins on Monday, 08 December 2008 00:35:37
Regarding AICCU status, http://dakx.com:8080/vista_aiccu_tunnel.gif is a screen dump from Vista, XP has something similar. The motes are contiki ipv6 webservers, I'd like to get both ipv4 and ipv6 access to them. I don't mind experimenting if it can't turn Chicago into an ipv6 crater :)
Testing tunnel on several machines
[ch] Jeroen Massar SixXS Staff on Monday, 08 December 2008 00:47:59
Those are the "interface statistics", that the interface is called AICCU is one thing, doesn't mean this comes from AICCU though (new version actually will include this though ;) As for the reason why no traffic comes through it: maybe your tunnel is not even functioning and you are using a different kind of connectivity, and as you are using Vista, there are plenty of those available (Teredo, 6to4, ISATAP). If they speak IPv6, get a subnet.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker