All that look good. I don’t think that you need to run those other tests, as your box and your Internet connection are sound.
Although, I cannot say that I understand your Ethernet status. In my case, I have only one line referring to local-link IPv6, where you also have one permanent and a couple of temp IPv6 addresses. Maybe you can check that one section after few minutes, and see whether any of those IPv6 addresses are rotating (and repeat after 5 mins or so a couple of times)? Here is my section:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : burrow.int.
Link-local IPv6 Address . . . . . : fd80::53ae:c1bd:bf5a:8ae3%5
IPv4 Address. . . . . . . . . . . : 192.168.01.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.01.1
I kill IPv6 on my router, that is the reason that I have just that local-link (a private one).
My understanding is that the wallet up/down bytes are just local exchanges between the full node or UI and wallet. This is why we see some numbers there.
Again, I am still running v1.2.6 (1.2.7 is about the same). v…8 was badly broken, v…9 was a quick hack to fix v…8, but stable enough. v…10 had some issues, and again v…11 is a quick hack where potentially a lot of changes were around peer connections. Maybe those last two versions have some issues around IPv6 protocol (just grasping for straws).
There are more people reporting problems with v10/11 comparing to previous upgrades. Based on what you stated, that is the only thing that got changed for you, so that is for me the main reason to focus on those versions.
I am out of bullets right now. The only thing that I would suggest is to drop your version to v1.2.7. Although, don’t rush, as maybe others will be able to see more in the info you provided.
Oh, and I would not be removing any of those peers by hand (as was suggested before).
traceroute is trying to do a DNS lookup for all notes that it hits. Some of those don’t have DNS names, and that is where it is stuck. It is also looking for responses, and not all nodes respond properly, that is where you see those stars. Either way, nothing to worry about.
If that version worked for you before, then no need to drop to v1.2.7. Other people dropped to v1.2.9, so maybe someone that did it will chime in.
Lastly, maybe someone with a fast upload could let you have blockchain db. It zip-compresses to about 15GB. This will not fix anything, but will get you closer to be synced.
Oh, and I would try to disable that IPv6. You go to Control Panel / Network and Internet / Network and Sharing Center / (In the Access type click that blue) WiFi (or whatever you see there) / Properties (on this new dialog) / uncheck Internet Protoco Version 6 (TCP/IPv6) line. I guess, you will need to reboot.
In case you will have any problems (not likely), you just go back there and tick that line to bring it back. Maybe this is the fastest test you could do. (Again, grasping for straws.)
One more thing that you could do, and what was already suggested - setup another full node.
