alsg wrote

May I know what kind of broadband connection you're having?

Of course. Hungarian DIGINet 200/100, PPPoE with a CPE (CPE in PPPoE bridge mode, router make PPPoE connection). I upgraded the U-boot too.

wwenigma wrote

Of course. Hungarian DIGINet 200/100, PPPoE with a CPE (CPE in PPPoE bridge mode, router make PPPoE connection). I upgraded the U-boot too.

Thank for sharing.

Ever since I downgraded to V2 (3.19.32 Build 150717 Rel.53114n), I don't encounter the problem anymore. So hopefully this is fix in future V3 firmware release.

The firmware also had other problems. IPv6 didnt working for me. My provider use dual stack PPPoE, but router reject ipv6 address...instead that alvays try to connect via PPPoEv6.

wwenigma wrote

The firmware also had other problems. IPv6 didnt working for me. My provider use dual stack PPPoE, but router reject ipv6 address...instead that alvays try to connect via PPPoEv6.

Not sure if this particular version 3.16.9 Build 151021 Rel.74655n able to resolve your issue. It is meant for US release so can't change the wireless region settings but I do noticed that under IPv6 Support, there is option to disable it which was missing in 3.16.9 Build 150514 Rel.72381n.

Well, build 151021 does resolve my earlier problem post here. Hope they release the global version so that wireless region is not locked just to US (not that it matter that much to me).

Thanks for hint but not working for me. Same IPv6 error. Router drop IPv6 address from IP6CP.

Dec 7 10:05:16 PPP INFO rcvd [IPV6CP ConfReq local Peer Ipv6 Address = fe80::c484:dd05:cc63:8d1d]
Dec 7 10:05:16 PPP INFO sent [LCP ProtRej]

Many reports from other TP Link router (with IPv6 support) owners, not working, doesnt matter which type, 1043ND or Archer C7 :D

mod: need serial cable reflash after that US firmware, i updated bootloader too and recovery didnt working.

For those who PM me requesting for copy of the stripped u-boot file or instruction, kindly refer to my signature for the link.

As for questions regarding the instruction, sarmad's write-up is pretty clear so do go through especially the point on [hint]. Newer or latest Gargoyle can be used instead of 1.6.2, main objective is to have SSH access.

Although, TP-Link didn't post the latest firmware for v3, refer to my earlier posts and use google to search for it.

Kindly use this thread as the point of discussion rather than using PM. :cool:

Ka-EM wrote

How do you know, how many bytes are needed to stripp out? Has the boot size sector same size at v2 and v3?

This is well documented in OpenWRT and many forum sites. Google for it and you have your answer.

I have been googling it before I wrote here, but I did not find exactly what I need. The only answer I found (OpenWRT forum) is that v2 boot sector has size 128 KiB, but I can not found size of v3 boot sector. I silently assume that size_of(v2_boot_sector) == size_of(v3_boot_sector) == 128 KiB. So it would be OK. But, when I compare size of full original/stock FW (8 258 048 bytes) and size of stripped FW (8 126 464 bytes), there are still 512 bytes missing! And I am asking why and where, because I do not want to brick my device... I do not know if I can discuss this "problem" here in official forum, or should I write to another forum e.g. OpenWRT. Thanks a lot !