Security is a big issue, since I was previously behind the router's firewall, so everything was open within my network, and ASUS's firmware does not support ipv6 firewall.

Wouldn't a host based firewall block unsolicited tcp connections as well?

Your CCTV/IP camera needs to support IPV6. It is useless and most ones I have seen does not even have ipv6 stack installed (my cctv for instance runs on old linux 2.4.x kenrel without ipv6 compiled). So it is useless , even if my Telco network supports ipv6 and my router is able to handle IPV6 , but the device itself is not compatible with IPV6

Yay, managed to configure IPv6 on my router

wKkaY: For the router database:

Router model	ASUS RT-N56U
Firmware	Padavan RT-N56U_3.4.3.6-069 (firmware link)
Broadband package	UniFi Home VIP20

wKkaY How come the forum does not show I have posted from an IPv6 address when I'm on my iPad?

/64 ought to be enough for anybody.

oh i get it. If your limited by having only 1 router cause of it, thats a big issue :/

cause take for example the living where your iptv is; to connect there you need either a homeplug...... or..... use wireless e.g. setting up a client router to do wireless to your main router.

yeah hm 

when did you suddenly talk for every1 ?    kid your a joke
prasys test prove there is difference  y should i run test ? i haven't played wow in years.... if you got something to prove, you run the test and post here, dun troll 

To anyone else wondering, a /64 is the smallest subnet allowable in IPv6.

3. Subnet Prefix Considerations


  An important part of an IPv4 addressing plan is deciding the length
  of each subnet prefix.  Unlike in IPv4, the IPv6 addressing
  architecture [RFC4291] specifies that all subnets using Globally
  Unique Addresses and ULAs always have the same prefix length of 64
  bits.  (This also applies to the deprecated 6bone and site-local
  addresses.)

  The only exception to this rule are special addresses starting with
  the binary value 000, such as IPv4-compatible IPv6 addresses.  These
  exceptions are largely beyond the scope of this document.

  Using a subnet prefix length other than a /64 will break many
  features of IPv6, including Neighbor Discovery (ND), Secure Neighbor
  Discovery (SEND) [RFC3971], privacy extensions [RFC4941], parts of
  Mobile IPv6 [RFC4866], Protocol Independent Multicast - Sparse Mode
  (PIM-SM) with Embedded-RP [RFC3956], and Site Multihoming by IPv6
  Intermediation (SHIM6) [SHIM6], among others.  A number of other
  features currently in development, or being proposed, also rely on
  /64 subnet prefixes.

  Nevertheless, many IPv6 implementations do not prevent the
  administrator from configuring a subnet prefix length shorter or
  longer than 64 bits.  Using subnet prefixes shorter than /64 would
  rarely be useful; see Appendix B.1 for discussion.

  However, some network administrators have used prefixes longer than
  /64 for links connecting routers, usually just two routers on a
  point-to-point link.  On links where all the addresses are assigned
  by manual configuration, and all nodes on the link are routers (not
  end hosts) that are known by the network, administrators do not need
  any of the IPv6 features that rely on /64 subnet prefixes, this can
  work.  Using subnet prefixes longer than /64 is not recommended for
  general use, and using them for links containing end hosts would be
  an especially bad idea, as it is difficult to predict what IPv6
  features the hosts will use in the future.

  Appendix B.2 describes some practical considerations that need to be
  taken into account when using prefixes longer than /64 in limited
  cases.  In particular, a number of IPv6 features use interface
  identifiers that have a special form (such as a certain fixed value
  in some bit positions).  When using prefixes longer than /64, it is
  prudent to avoid certain subnet prefix values so that nodes who
  assume that the prefix is /64 will not incorrectly identify the
  addresses in that subnet as having a special form.  Appendix B.2
  describes the subnet prefix values that are currently believed to be
  potentially problematic; however, the list is not exhaustive and can
  be expected to grow in the future.

  Using /64 subnets is strongly recommended, also for links connecting
  only routers.  A deployment compliant with the current IPv6
  specifications cannot use other prefix lengths.  However, the V6OPS
  WG believes that despite the drawbacks (and a potentially expensive
  network redesign, if IPv6 features relying on /64 subnets are needed
  in the future), some networks administrators will use prefixes longer
  than /64.

In my situation, only local hosted website are accessible with IPV6. When I try to open international website, it loads forever. No idea whether it's my exchange/BRAS are not IPV6 ready yet or it lies between my hardware itself... 

wanna to ask, is the /64 provided static? As I'm planning to use cloudflare's ipv6 to ipv4 so that I can access my computer from anywhere and I don't want ending up accessing other people's computer because of the change in the /64 as you reboot your router

with temporary ipv6 address implementation in place on most OSes with slaac, you will not be able to statically map nodes to ipv6 address in conventional sense.

use dynamic dns.

Hmm, is this could be my exchange still have not deployed IPv6?

using ASUS RT-AC68U

why else the ridiculous lockdown on preventing other router models from being used 

just want to check, does UNIFI allow us to use google ipv6 dns? as if i use google dns, i cant get connected to ipv6, if let it to automatic obtain, no issue,, btw, google dns 2001:4860:4860::8888 and
2001:4860:4860::8844

Ping and tracert looks ok.