Since I got the tunnel running, I've noticed that utm uses cpu heavily when I try to display the ipv6 lease table, even when there is little or no load network load. The browser spins for a while, sometimes utm posts a dialog asking if I want to wait 30 more seconds to finish the request. Even if I select yes, it usually doesn't display the lease table. ipv4 leases are displayed quickly. There are only a small number of leases in total, under 15. If I reboot utm, it works okay for a while, then the same thing happens again.
utm is running as a guest on a lightly loaded hyperv2012 server.
Anyone else experiencing this problem?
This thread was automatically locked due to age.
