Opened 7 years ago
Closed 7 years ago
#1181 closed defect (wontfix)
After switching to IPv6-only mode, network status stays "Testing"
| Reported by: | _Vi | Owned by: | zzz |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.11 |
| Component: | router/transport | Version: | 0.9.10 |
| Keywords: | Cc: | ||
| Parent Tickets: | Sensitive: | no |
Description
The router itself more works (although with high lags and performance issues).
NTCP connection count fluctuate around 6-9, plus 3-4 UDP connections, more outbounds that inbounds.
BANDWIDTH IN/OUT
3 sec: 5.46 / 9.35 KBps
5 min: 9.78 / 19.12 KBps
http://ipv6-speedtest.net/ shows "3.17 Mbps down, 0.8 Mbps up"
Tunnel sharing is turned off.
The router is in that mode for about 2 hours. Bandwidth plot looks similar to what was before (IPv6+IPv4 configuration, with "Networking: OK" degrading to "Networking: Firewalled with inbound TCP enabled" - probably separate issue).
P.S. the ticked is submitted though the router in question.
Subtickets
Change History (2)
comment:1 Changed 7 years ago by
| Component: | unspecified → router/transport |
|---|---|
| Owner: | set to zzz |
comment:2 Changed 7 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
The only way to do IPv6-only would be restricted routes, which isn't going to happen anytime soon.
IPv6-only doesn't work well because we are a full-mesh network. Now marked experimental on /confignet, shouldn't we really just remove it from the UI?