FS#1763 - 18.06 doesn't obtain IPv6 address on mt76 #7049
Comments
|
jedimage: No IPV6
So it’s not just mt76 also ar71 and may be others. I am also a concast / xfinity customer so it may be related to them. |
|
hsgg: Brian wrote:
Hm, that might imply that something went wrong when I did "git bisect"? Would you be willing to bisect on the ar71, or at least verify my bisection result for mt76? |
|
wiIIiam: I can confirm this issue exists on edgerouter-x running 18.06.1 (r7258) using Comcast. Tcpdump on wan interface (eth0.2) shows periodic dhcp6 solicit, without any response. |
|
dtaht: I confirm this exists on comcast on an apu2 running 18.06.1 also. Sigh. |
|
dtaht: I turned off ip6tables entirely, and took a packet cap. I see (on my hardware) a bad udp checksum... (but you would normally see that if you have checksum offloading enabled) :/tmp# 09:12:17.404257 IP6 (flowlabel 0xdfff4, hlim 1, next-header UDP (17) payload length: 159) fe80::20d:b9ff:fe43:a06c.546 > ff02::1:2.547: [bad udp cksum 0x58f4 -> 0xc4a1!] |
|
dtaht: This arm box IS getting dhcpv6-pd correctly. root@gw1:~# cat /etc/openwrt_release My mips and x86_64 boxes aren't |
|
byrneta: Still appears to be an issue on Ubiquiti Edgerouter ER-X (OpenWrt SNAPSHOT r8284-212aa33226). ISP is Spectrum (legacy Charter) |
|
jburgess777: Did you try turning off the NET_MEDIATEK_OFFLOAD and NET_MEDIATEK_HW_QOS config options that the 424a9ae patch added? |
|
byrneta: Jon Burgess wrote:
Where should these config options be changed? |
|
burianvlastimil: I tackled this 3 days... 3 days of non-stop work, so I would like someone to:
All of my provided information is / will be tracked on superuser.com: https://superuser.com/questions/1372769/ipv6-home-set-up-openwrt-18-06-1-how-to THANK YOU. |
|
hsgg: Jon Burgess wrote:
I finally had time to test this. Such an obvious thing to try! It works! I have IPv6 now! If others want to test as well: I added the line after line 62 of the file target/linux/ramips/files-4.14/drivers/net/ethernet/mtk/mtk_eth_soc.c. My understanding is that the other option doesn't affect my hardware; it only affects MT7623. |
|
fearless: I also have this bug on a wrt32x (cortexa9) with 18.06.02. IPv6 works from my ISP (Optimum Online in north New Jersey US): If I connect my Windows 7 computer to my modem then test-ipv6.com says everything works. From the OpenWrt device: ping6 ipv6.google.comPING ipv6.google.com (2607:f8b0:4006:81b::200e): 56 data bytes ifstatus wan6{ |
|
jchulce: Here's the commit that broke IPv6: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=424a9ae128bd2045cd4bfd6e3229f2529d150a25 Supports IPv4 flow offloading on MT7621 for Routing, SNAT and DNAT Supported are regular ethernet->ethernet connections, including one |
|
unquietwiki: Henry's solution worked for me on my EdgeRouter-X, using OpenWRT 18.06.2. Wasn't getting DHCPv6-PD from cable modem otherwise. |
|
nbd: Please try this patch: http://nbd.name/offload-ttl0.patch |
|
hsgg: Your offload-ttl0.patch works great! Thank you! |
|
hsgg: Hm, now I occasionally get FS#1618, even after reversing the offline-ttl0 patch. I haven't seen that bug before. Might it be related? |
|
nbd: Fix pushed in r9707-bee7ff7cf3 (master) r7722-4336cfda12 (18.06) |
|
nbd: I don't think the FS#1618 issues are related to this. |
hsgg:
OpenWRT-18.06 doesn't obtain an IPv6 address on the wan6 interface since commit 424a9ae. IPv6 works before that commit. The git bisect output is
$ git bisect goodThere are only 'skip'ped commits left to test.
The first bad commit could be any of:
424a9ae128bd2045cd4bfd6e3229f2529d150a25
bfed38254076d576914251689a2e1f85d514783d
We cannot bisect more!
The WAN6 interface status when not working is
root@OpenWrt:~# ifstatus wan6
{
"up": false,
"pending": true,
"available": true,
"autostart": true,
"dynamic": false,
"proto": "dhcpv6",
"device": "eth0.2",
"data": {
}
}
The device is a Netgear R6220, and my ISP is Comcast in Pennsylvania.
I attach dmesg when running the last working commit.
Other users also have this problem, see [[https://forum.openwrt.org/t/openwrt-18-06-rc1-doesnt-obtain-ipv6-address/16759/4|this forum thread]]. (I'm the OP of that thread.)
Would be great to have IPv6 working again. Thank you!
Steps to reproduce:
0. Delete .config file, in "make menuconfig" select appropriate target (MediaTek Ralink MIPS), subtarget (MT7621), and target profile (Netgear R6220).
1a. Compile image prior to above commits, upload to router
1b. Run "sysupgrade -v -n /tmp/.tar"
1c. Confirm that IPv6 is working, e.g. by pointing browser to ipv6-test.com, or "ifstatus wan6" on the router
2a. Compile image from source after above mentioned commits, e.g. tag "v18.06.0", upload to router
2b. Run "sysupgrade -v -n /tmp/.tar"
2c. Confirm that IPv6 is not working
The text was updated successfully, but these errors were encountered: