more seeders for eps 70

[Kumiriko]

Well i know i should have downloaded the second it came out but i dint. can i get some more people to seed this? it is going kinda slow. any seeders be grate

[itachi_]

Well, there are already enough seeders to provide everyone... Because of all leechers, gotwoot are beeing slowed down..

[Dungwader]

I know that I downloaded 22% of episode 70 easily enough but my download and upload has been stuck at 0 for the last hour...

[Aegis Runestone]

I can't get a single seeder and sometimes I get a message that says: "Operation timed out" >_<

Okay... I need some help here.

[Everon]

Currently there are over 2000 seeders so that shouldn't be a prob

[Vagabond]

2000 seeders? or leechers?
Anyways i can seed for bakasan 70. If you want that. But i would assume you want anbu/aone since it is out.
Actually didn't they pull it back? I dunno if anyone can d/l anbu/aone.

[Kakashi-Senpai]

If you are complaining, go to aone&#39;s mirc channel and get it. Its <u>much</u> faster there.

[Aegis Runestone]

Well i&#39;m in there... and everyone is saying: &quot;Go d/l it off the main page.&quot;

O_o

I&#39;m getting sent in circles&#33;

[itachi_]

Just go to irc @ #animeone. type /msg AonE|botname xdcc send #. to get packet number writhe /msg AonE|botname xdcc list. That&#39;s very easy... And you&#39;ll get around maximum download speed.

[Aegis Runestone]

Thanx, itachi&#33; That&#39;s very helpful&#33; Whoa.... #animeone has 3000+ chatters o.o That&#39;s quite a bit. o.o

[L8r]

my download has stoped at 97%
&quot;problem connecting to tracker&quot;

[To Young]

I think there are plenty of seeders.

May be it is tracker problem. lookes like it is overloaded.
I can&#39;t connect to tracker at all.

[sangai]

im at 0.6 percent at 0k a sec so it will take a while before i can get this

[Kumiriko]

Mine stopped at 99.8% and it runs. that was odd but i got the error. anywas

[Noir]

I stopped at 57% to shut my PC down as I left for work. Came back, resumed, and yeah error, error, error, (you know problem connect with tracker)... ooh 4th time I got the error, Ah hopefully it&#39;ll be done by morn.

[Dan Mc]

well I decided to goto IRC, but im getting people uploading the file from me now, so ill leave it open for now an maybe a few days to help others out...

[hiroshi]

</div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (Moonlight &#064; Feb 14 2004, 05:54 AM)</td></tr><tr><td id='QUOTE'> When I started trying to download #70, the tracker was giving me 30-40x the same IP (69.56.211.107) which traced back to an IP owned by &quot;ThePlanet.com&quot;, which happens to be the co-location company where GotWoot is hosted from - I wonder what this was all about.

If it weren&#39;t for the fact that the &#39;junk&#39; IPs that filled the tracker were from the same co-location company that hosts GotWoot, I would have thought this was a DoS of some sort... but unless the tracker is brain-dead, this should not be happening unless it was due to an internal issue - at least not with what appeared to be internal IPs.

Well, it looks like the tracker was restarted moments ago... let&#39;s see if the oddities will come back. So far, I am seeing a much more sane 2-3 IPs that start with 69. </td></tr></table><div class='postcolor'>
That&#39;s probably due to the fact we&#39;ve actually run out of possible IP Addresses in our current system. That&#39;s why Microsoft have developed the IP v6 now. However, a lot of people arn&#39;t using IP v6 because of course everyone else is using IP v5 (The current system).

IP v6 was either going to be a Hexadecimal system instead of a standard number system, or it was just going to have another point added in. I think, in the end Microsoft decided to simply add another point rather than move to the Hexadecimal system.

Conflicting IP Addresses means someone is using an Illegal IP Address, and it hasn&#39;t been properly authorised by the correct people for usage. Someone isn&#39;t doing their job properly

Edit:
Ok, forget what i just said. I misunderstood what you had typed. =.=;

[SirCharlesIII]

moved to BT support

[Moonlight]

</div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE </td></tr><tr><td id='QUOTE'>That&#39;s probably due to the fact we&#39;ve actually run out of possible IP Addresses in our current system. That&#39;s why Microsoft have developed the IP v6 now. However, a lot of people arn&#39;t using IP v6 because of course everyone else is using IP v5 (The current system).</td></tr></table><div class='postcolor'>

Unless the transition from IPv4 to IPv5 was so transparent that nobody ever noticed it, I am pretty sure most people are still using IPv4 since there is no such thing as IPv5 AFAIK.

Also, IPv6 is not a Microsoft thing, it is an IETF thing and Microsoft is not in much of a hurry to implement full support for it, just like almost everyone else.

</div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE </td></tr><tr><td id='QUOTE'>Ok, forget what i just said. I misunderstood what you had typed. =.=;</td></tr></table><div class='postcolor'>

It happens all the time

In any case, the reason why yesterday&#39;s Naruto release was doing so badly is because duplicate/erroneous/expired &quot;peer&quot; entries (apparently from within GotWoot&#39;s hosting) accounted for the majority of them. Things cleared up when the tracker was restarted/reset.

I thought most trackers would at least have some code to prevent one IP from occuring 100+ times with different Client IDs. IMO, this makes for a fairly effective DoS attack on any tracker that does not do so, as we have seen yesterday. (Intentional or not, only the end-result matters - the tracker was useless until it was reset either way.)

[hiroshi]

</div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (Moonlight @ Feb 15 2004, 12:20 AM)</td></tr><tr><td id='QUOTE'> </div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE </td></tr><tr><td id='QUOTE'>That&#39;s probably due to the fact we&#39;ve actually run out of possible IP Addresses in our current system. That&#39;s why Microsoft have developed the IP v6 now. However, a lot of people arn&#39;t using IP v6 because of course everyone else is using IP v5 (The current system).</td></tr></table><div class='postcolor'>

Unless the transition from IPv4 to IPv5 was so transparent that nobody ever noticed it, I am pretty sure most people are still using IPv4 since there is no such thing as IPv5 AFAIK.

Also, IPv6 is not a Microsoft thing, it is an IETF thing and Microsoft is not in much of a hurry to implement full support for it, just like almost everyone else.

</div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE </td></tr><tr><td id='QUOTE'>Ok, forget what i just said. I misunderstood what you had typed. =.=;</td></tr></table><div class='postcolor'>

It happens all the time

In any case, the reason why yesterday&#39;s Naruto release was doing so badly is because duplicate/erroneous/expired &quot;peer&quot; entries (apparently from within GotWoot&#39;s hosting) accounted for the majority of them. Things cleared up when the tracker was restarted/reset.

I thought most trackers would at least have some code to prevent one IP from occuring 100+ times with different Client IDs. IMO, this makes for a fairly effective DoS attack on any tracker that does not do so, as we have seen yesterday. (Intentional or not, only the end-result matters - the tracker was useless until it was reset either way.) </td></tr></table><div class='postcolor'>
*blinks*
*Stares at post.*

*thinks all this over in his head*
Wth?

*Admits certain things:*
I presumed we were already using v5, seeing as v6 was simply released without any notification of v5 in the first place.

I also presumed that Microsoft played a part in the development of v6, due to the fact that they were one of the first to send out the v6 patch to download via their update website. With this in mind, seeing as they&#39;re offering the patch on the update website, it would also lead you to conclude that they are beginning to support the system. However i did state that a lot of people aren&#39;t using it because nobody else is, thus the idea that no-one is really offering to support it, was mentioned by my post and verified by your post.

However.....
I am rather perplexed and confused now of this issue. For instance, just what the hell happened to v5 in the first place? And why did Microsoft offer the patch so soon after it&#39;s development, if they&#39;re not willing to support it? Isn&#39;t that contradictory? Also, sorry for my ignorance and i should probably know this. You can shoot me for asking the question, as i probably deserve it, but who exactly is IETF? o_O; related to IEEE in any way?