|
10 days and no +5 credits
![[ro]](/s/countries/ro.gif) Shadow Hawkins on Tuesday, 02 March 2004 08:52:08
You currently have 10 credits.
2004-02-21 17:55:14 Tunnel to xx.xx.xx.xx was user enabled
this is the last message in my log
there are no -credits due to downtime and im not using a heartbeat tunnel
any ideas why i didnt get the credits?
10 days and no +5 credits
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 04 March 2004 01:01:03
It's the same for me, any solutions?
10 days and no +5 credits
![[nl]](/s/countries/nl.gif) Carmen Sandiego on Thursday, 04 March 2004 13:09:02
It seems that they forgot to give me credits too. Perhaps we should wait some more time?
10 days and no +5 credits
Shadow Hawkins on Friday, 05 March 2004 00:05:52
I received my last credits on 2004-02-12 01:15:54. How long am I supposed to wait, or what can I do?
10 days and no +5 credits
You have a heartbeat tunnel those only get credits once, this is mentioned in the FAQ quite explicitly.
10 days and no +5 credits
Shadow Hawkins on Friday, 05 March 2004 07:27:07
Oops, sorry. I must have overlooked that...
10 days and no +5 credits
You have extremely high loss, nearly 100% continuesly, do you really expect credits then ? See the graphs and solve your issues.
10 days and no +5 credits
Carmen Sandiego on Friday, 05 March 2004 10:20:47
Ah well, that explains. Sorry for that and I'll be more careful.
10 days and no +5 credits
Carmen Sandiego on Friday, 05 March 2004 12:31:52
Well, I've been doing some checking, and it seems that 'on my side' there is not much cause for loss. My host pings perfectly from other IPv6 hosts. What could be wrong?
10 days and no +5 credits
A lot:
- your routing
- your filtering
- connectivity between you and the POP being filtered
- rate limits applied, even in IPv4
etc... apparently you have an average of 95% lossm having only a few packets that actually get delivered. Better start tcpdumping and checking what goes wrong.
10 days and no +5 credits
Carmen Sandiego on Saturday, 06 March 2004 01:30:02
Well, I found the problem: since I was not doing very much v6 traffic, my tunnel 'was sleeping' sometimes. The first ping (and only that one) that was sent took a long time to generate a pong. Since I am making some 'noise' over my tunnel, the packet loss was reduced to an average 0%.
I found it a very strange problem, since my v6 traffic which was initiated by myself (ie web/ftp, etc) had no problems at all: connectivity was good. But only SixXS pings seemd to get lost.
10 days and no +5 credits
03-04 01:15 Tunnel endpoint 2001:6f8:900:15c::2 didn't ping for 2 days
03-05 01:15 Tunnel endpoint 2001:6f8:900:15c::2 didn't ping for 3 days
And it doesn't ping according to that same log.
|
![[ch]](/s/countries/ch.gif)
on Friday, 05 March 2004 03:04:02
Posting is only allowed when you are