and thus my claim earlier ipv6 latency is good for gaming is proved true 

......small print: server needs to be ipv6 supported  which apparently diablo 3 isn't surprisingly 

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.

no one believes your claimlah. it's useless.

it's just a case of tm adjusting/not adjusting ipv6 traffic for unifi subs.

you do traceroute lah, sure different routing path for ipv6.

So in other words, a /64 is the norm that everyone gets, and /48, /56 or /60 are for 'special' cases/scenarios..

so anyone had luck configuring IPv6 on pfSense ?:unsure:

Select dhcp6 on the WAN, set the prefix delegation size to 64 bits.
Go to the LAN interface, for IPv6 select "Track Interface". Set it to interface "WAN" and the network prefix is always 0 for you.

testing office ipv6

Or you can script it for when router boots up, if you know how (i don't).
step2
I suspect i needed to disable, then enable back my desktop pcs ethernet port. So i did that, then ran the test at
http://ipv6test.google.com/
http://test-ipv6.com/

i'm not quite sure how to do that.

also with the help of a friend, we found that my internet connection for ipv6

not sure why, also haven't found a fix for it yet. But if i when i reboot my router and wait 10-15mins then i can get around this problem. it's annoying but, i have to live with it