Outline ·
[ Standard ] ·
Linear+
Unifi TMnet Streamyx/Unifi & IPv6, Now live!
|
TSwKkaY
|
Oct 1 2013, 12:35 AM, updated 9y ago
|
misutā supākoru
|
I just heard that TMnet launched IPv6 on September 27th, so I did some experiments tonight and confirm that it is live!
What I've seen so far from packet dumps: - PPP IPCP6 negotiates link-local addresses - SLAAC Router Advertisement gives you a dynamically-assigned /64 - DHCPv6 assigns DNS servers In addition, asellus reports that DHCPv6-PD is supported. The prefix delegated is dynamic. DNS servers from DHCPv6: - 2001:e68::b:68 - 2001:e68:2005:29:202:188:0:133 (does this look familiar?  ) Attached is a pcap of the IPv6 assignment process. PDF doc from TMnet about enabling IPv6: http://www.tm.com.my/OnlineHelp/CustomerSu...able%20IPv6.pdfKnown working configurations: - Asus RT N-12 - Asus RT N-16 - ASUS RT-N56U - D-Link DSL-2730E - D-Link DSL-2730U - D-Link DIR-615 - Linksys E4200 with Tomato RAF by Victek- Mikrotik - TMnet "L7" - TMnet TM6841G - Windows 7 PPPoE You can use this site to test your IPv6 connectivity: http://www.test-ipv6.com/This post has been edited by OKLY: Nov 26 2013, 08:45 PM Attached File(s)
ipv6.pcap.zip ( 922bytes )
Number of downloads: 1041
|
|
|
|
|
|
TSwKkaY
|
Oct 1 2013, 01:49 AM
|
misutā supākoru
|
Can't get the Mikrotik to work with it as it dosen't support SLAAC.
Gonna hook up Linux to this tomorrow and see if TM assigns prefixes over DHCPv6-PD.
|
|
|
|
|
|
TSwKkaY
|
Oct 1 2013, 02:29 AM
|
misutā supākoru
|
No idea... I'm still at very early stages of figuring out their setup. Hopefully someone who knows more can chip in.
The good thing with pfsense though is that being FreeBSD, I'm sure it's possible to hack it to work the same way as the Windows 7 setup.
|
|
|
|
|
|
TSwKkaY
|
Oct 1 2013, 11:48 AM
|
misutā supākoru
|
QUOTE(paultantk @ Oct 1 2013, 08:29 AM) Slaac or dhcp6 doesn't work so far. tried it on my pppoe interface as well as on my vlan500 interface. my ACNAME is BSRKLJ03, could be this one doesnt have ipv6? yours? I'm on JRC here with a Unifi home account. Just throwing out a thought, are you on Unifi Biz with static IP?
|
|
|
|
|
|
TSwKkaY
|
Oct 1 2013, 04:06 PM
|
misutā supākoru
|
QUOTE(aneip @ Oct 1 2013, 02:24 PM) Tested slaac on pfsense. Not working, maybe need tweaking. U using direct pppoe on windows? Yeah, my experiment was on direct pppoe on windows. I stripped out the VLAN 500 tag.
|
|
|
|
|
|
TSwKkaY
|
Oct 1 2013, 06:43 PM
|
misutā supākoru
|
QUOTE(dimenxion @ Oct 1 2013, 06:08 PM) i saw your screenshot on the ipv6 part it doesnt show ipv6 dns server. do u added the ipv6 dns manually after connected or u received it via dhcpv6? I think I saw them in wireshark, sent by TM's DHCPv6. I don't know if Windows 7 honors it.
|
|
|
|
|
|
TSwKkaY
|
Oct 1 2013, 09:20 PM
|
misutā supākoru
|
QUOTE(aneip @ Oct 1 2013, 09:06 PM) Tested on windows 7.. ACNAME "BSRBGI01". Window 7 using 6TO4 adapter.. Then enable 6TO4 on pfsense. Able to get the IP.. but speedtest show very low speed.. 5Mbps on IPV4, 800Kbps using ipv6.. Tested using http://ipv6-test.com/speedtest/I think certain place still not support ipv6 natively. You're doing it wrong if you're using 6to4. It works with practically any ISP that gives you a public IP, and is the stuff of yesterday. TMnet has native IPv6 now which obsoletes the need to use it.
|
|
|
|
|
|
TSwKkaY
|
Oct 2 2013, 12:23 AM
|
misutā supākoru
|
QUOTE(paultantk @ Oct 1 2013, 10:42 PM) Just tried again, getting same error messages. Maybe my area not yet. CODE ppp: [wan] IPV6CP: protocol was rejected by peer I guess the BRAS where you and aneip are isn't dual-stack yet. I'll try it out at my office tomorrow which is hooked up to the KLJ BRAS
|
|
|
|
|
|
TSwKkaY
|
Oct 2 2013, 12:34 AM
|
misutā supākoru
|
Found out a few more things today: 1) They use SLAAC only to assign addresses. DHCPv6 IA and PD are both not used. 2) I've been told that we should be hearing official news "very soon"  3) Added a pcap to my first post, here's the text version: » Click to show Spoiler - click again to hide... « CODE 1 0.000000 Vmware_68:69:05 -> Broadcast PPPoED 24 Active Discovery Initiation (PADI) 2 0.012483 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPPoED 60 Active Discovery Offer (PADO) 3 0.012634 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPPoED 24 Active Discovery Request (PADR) 4 0.026163 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP LCP 60 Configuration Request 5 0.031494 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPPoED 60 Active Discovery Session-confirmation (PADS) 6 0.999786 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP LCP 34 Configuration Request 7 1.004977 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP LCP 60 Configuration Reject 8 1.005680 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP LCP 32 Configuration Request 9 1.010866 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP LCP 60 Configuration Ack 10 3.048058 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP LCP 60 Configuration Request 11 3.049239 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP LCP 40 Configuration Ack 12 3.049452 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP LCP 30 Echo Request 13 3.049554 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP PAP 57 Authenticate-Request 14 3.054364 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP LCP 60 Echo Reply 15 3.110182 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP PAP 60 Authenticate-Ack 16 3.110189 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP IPCP 60 Configuration Request 17 3.110192 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP IPV6CP 60 Configuration Request 18 3.111350 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP CCP 37 Configuration Request 19 3.111502 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP IPCP 38 Configuration Request 20 3.111686 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP IPV6CP 36 Configuration Request 21 3.111796 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP IPCP 32 Configuration Ack 22 3.111934 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP IPV6CP 36 Configuration Ack 23 3.116036 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP LCP 60 Protocol Reject 24 3.116038 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP IPCP 60 Configuration Reject 25 3.116853 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP IPCP 32 Configuration Request 26 3.138327 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP IPV6CP 60 Configuration Ack 27 3.140283 fe80::cd6f:9c27:7b59:273b -> ff02::2 ICMPv6 70 Router Solicitation 28 3.142862 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP IPCP 60 Configuration Nak 29 3.143443 Vmware_68:69:05 -> IETF-VRRP-VRID_02 PPP IPCP 32 Configuration Request 30 3.143774 fe80::225:9eff:fe83:9cc8 -> ff02::1 ICMPv6 126 Router Advertisement from 00:00:5e:00:01:02 31 3.153379 IETF-VRRP-VRID_02 -> Vmware_68:69:05 PPP IPCP 60 Configuration Ack 32 3.157832 fe80::225:9eff:fe83:9cc8 -> ff02::1 ICMPv6 126 Router Advertisement from 00:00:5e:00:01:02
|
|
|
|
|
|
TSwKkaY
|
Oct 2 2013, 01:01 PM
|
misutā supākoru
|
Alpha_Tay Looks like you managed to get it working! (note that your posts will have an "IPv6" tag in the upper right if you post from IPv6)
|
|
|
|
|
|
TSwKkaY
|
Oct 2 2013, 06:45 PM
|
misutā supākoru
|
QUOTE(asellus @ Oct 2 2013, 06:40 PM) Man, so lacking in details as usual. Many of their supplied Steamyx modem doesn't even support IPv6. I understand that's supposed to be an internal announcement. We should be hearing more Soon .
|
|
|
|
|
|
TSwKkaY
|
Oct 3 2013, 12:22 AM
|
misutā supākoru
|
QUOTE(asellus @ Oct 2 2013, 11:45 PM) DHCPv6-PD is supported. wKkaY please fix info in first page. Cool! I guess there are implementation differences between Unifi and Streamyx as it stands now. When I try to request for PD, TMnet's DHCP server returns a UnspecFail status code. Looks like you can remove your Hurricane IPv6 tunnel now
|
|
|
|
|
|
TSwKkaY
|
Oct 3 2013, 12:26 AM
|
misutā supākoru
|
asellus can you check whether DHCP assigns you a static or dynamic prefix? Try reconnecting PPPoE and see if you get the same prefix.
|
|
|
|
|
|
TSwKkaY
|
Oct 3 2013, 12:36 AM
|
misutā supākoru
|
QUOTE(asellus @ Oct 3 2013, 12:31 AM) If you run routerOS, just run a DHCPv6-PD client on your Streamyx PPP interface, and it should pull down a random /64 from the access concentrator. Add the /64 to an address pool, then bind + advertise the address pool on the bridge interface, and the computer will automatically get two IPv6 addresses in a default Windows install. Can you check if you can request for something larger than a /64, for exapmle a /63 ?
|
|
|
|
|
|
TSwKkaY
|
Oct 3 2013, 01:53 PM
|
misutā supākoru
|
QUOTE(tezro @ Oct 3 2013, 08:25 AM) Hi, You can refer this PDF doc from TM: Guideline to Enable IPv6Thanks, I have updated the first post with this info.
|
|
|
|
|
|
TSwKkaY
|
Oct 4 2013, 10:07 PM
|
misutā supākoru
|
QUOTE(JohnnyDicaprio @ Oct 4 2013, 07:47 PM) below are my config for l7 router i can get ipv6 address for my windows 7 but not for my debian, dont know why.. i have to put image in spoiler, lazy to resize 2 scenarios I can think of: 1) router only supports dhcpv6, doesn't support slaac. solution: install dhcpv6 client in your debian box, eg wide-dhcpv6-client or dibbler. 2) router does support SLAAC, but it is disabled in your debian kernel /proc/sys/net settings
|
|
|
|
|
|
TSwKkaY
|
Oct 4 2013, 11:51 PM
|
misutā supākoru
|
QUOTE(Anonymous34 @ Oct 4 2013, 11:49 PM) Just knew this news when I look at LYN's tag beside the post#xx number. Haven't seen this post before, but then headed to: http://test-ipv6.com/ to test! Sure enough, iPv6 is live on UniFi now! Welcome to IPv6 land  (PS: your sig is too tall, can you shorten it?)
|
|
|
|
|
|
TSwKkaY
|
Oct 5 2013, 04:35 PM
|
misutā supākoru
|
QUOTE(asellus @ Oct 5 2013, 04:31 PM) Well, if the first page info about TP-Link WDR4300 being working fine, I think there should be nothing to worry about. At least TM used standardized protocols like ICMPv6 RA/RD and DHCPv6-PD at least to provide the dual-stack support. wKkaY, maybe you can update us if DHCPv6-PD works now with UNIFI or not? Unifi uses standardized protocols, however the specific combination of PPPoE over 802.1q is uncommon. There's one member report that PD works, but where I am it doesn't.
|
|
|
|
|
|
TSwKkaY
|
Oct 6 2013, 12:48 AM
|
misutā supākoru
|
QUOTE(Eoma @ Oct 5 2013, 08:37 PM) That info is misleading. It does not work correctly at the moment. They have a seperate WANv4 and WANv6 dialer. Sent some emails to them, we'll see how it turns out. The latest WDR4300 firmware for MY, has VLAN support but no IPv6 support (although it states it does on their page). Oh sorry I saw that you were posting from IPv6 so I assumed that your WDR4300 is working. How were you posting at the time, were you using Windows PPPoE?
|
|
|
|
|
|
TSwKkaY
|
Oct 6 2013, 01:10 AM
|
misutā supākoru
|
QUOTE(soulfly @ Oct 6 2013, 12:04 AM) What modem/router are you using? I'd like to add you to the database.
|
|
|
|
|