Hi All,
One more update, with some good news and bad news.
tl;dr: I (temporarily) solved the network issues causing major packet
delays and some packet loss, however this required turning off
my IPv6 tunnel.
The good news is that I finally found the trigger for the network
issues, so I now have a clean network. I discovered this last night
while trying to debug it further, and tested overnight with positive
results. The bad news is that the issue is (was?) my IPv6 tunnel, which
means to fix the issue I had to turn off v6. This has the side-effect
that if you're using v6 you will see a delay when trying to access the
GnuCash infrastructure, at least until I can determine how to resolve
this issue.
At least this gives me somewhere to focus and search; I can limit the
testing, and focus my testing efforts there. It does appear that only
upstream IPv6 traffic is causing the problem, so incoming data isn't
causing it. This means I can keep myself in good shape just by keeping
the routing table empty. It also *looks* like I can trigger the issue
just by running mtr -6 www.google.com (although it's possible that there
is other v6 traffic going on).
I plan to continue testing, but in the short term I expect to keep my v6
network turned off. I will require some network downtime to perform
further tests, so I'll ask on IRC before I pull the plug to run my tests.
My apologies if this affects you in an negative way.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warl...@mit.edu PGP key available
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
