Error 10054 And Other Chat Fun

[Fiia]

 

not what I meant sorry, posted the vonage to make sure it wasn't using the same ports. also not sure if it shows the port numbers when you log in there.

No worries, I changed it back and it worked fine after that. No, it does not show numbers, only that the box has two ports (1, and 2) and 1 was in use and 2 is available.

This is why I changed to port 2 but it caused issue and could not see the internet at all.

Hopefully today the 10/100/1000Mbps 5-Port Gigabit Green Ethernet Desktop Switch I ordered will arrive and that may take care of the problem.

I am trying all that I know and have been instructed to try; the chat is very stubborn to get to work though.

[Auxeus]

For 3 days 10060 presist and not a temporal solution being offered by DE, i feels like this is more like "deal with it" slap in the face situation.

 

Glen did mention this is no longer on his top-priority, since is the server's fault that won't respond then he can do anything about.

 

Sad to see this coming.

[GTG3000]

You should totally start selling t-shirts with those errors.

[Sherbniz]

Auxeus, on 26 Jun 2013 - 2:17 PM, said:

For 3 days 10060 presist and not a temporal solution being offered by DE, i feels like this is more like "deal with it" slap in the face situation.

I know how you feel, but picture this: My chat hasn't worked since the beginning of April, and you don't see me throwing tantrums.

That is because I know for a fact they (Glen, and everyone involved) are doing their best to fix it.

And they'll fix it for you as well. So don't worry.

 

Auxeus, on 26 Jun 2013 - 2:17 PM, said:

Glen did mention this is no longer on his top-priority, since is the server's fault that won't respond then he can do anything about.

Sad to see this coming.

To the contrary, I can report from first hand that DE_Glen has not abandoned this issue, but in fact been staying way late in office days on end to get the chat working for everyone (much to the chagrin of his wife).

It's really has been hard for him, the cause of these errors is rather weird, contrived and was only uncovered with extensive research, live tests with a lot of users and a lot of experimentation...

BUT I also know that he's made major strides, and I think we will see some results soon.

Please be a bit more patient!

Edited June 26, 2013 by Sherbniz

[Dolmur]

Regarding the clan MOTD - it is not sent through our chat server. The message is stored with your other clan data such as member list and simply displayed in the chat window. This means that the presence of an MOTD doesn't point to any improvement or regression in chat functionality.

[Auxeus]

I know how you feel, but picture this: My chat hasn't worked since the beginning of April, and you don't see me throwing tantrums.

That is because I know for a fact they (Glen, and everyone involved) are doing their best to fix it.

And they'll fix it for you as well. So don't worry.

 

To the contrary, I can report from first hand that DE_Glen has not abandoned this issue, but in fact been staying way late in office days on end to get the chat working for everyone (much to the chagrin of his wife).

It's really has been hard for him, the cause of these errors is rather weird, contrived and was only uncovered with extensive research, live tests with a lot of users and a lot of experimentation...

BUT I also know that he's made major strides, and I think we will see some results soon.

Please be a bit more patient!

 

Maybe you don't know how i feel since you enjoy communicate as a forumer with 640+ post counts, but we need an ingame real time communications with everyone else. Note that my main frustration is from seeing the issue is taken "a few notchs down" the priority because this only happen to a few people that doesn't seem to be important.

 

And how can you tell me to be patient of this problem is going to presist and we're not hearing any development from DE? And for you, not working since early April, should i applause and ask how long will you be patient further more?

 

[[DE]Glen]

Just be cool. I've spent the majority of my time on this issue for last few weeks and there are 2 workarounds coming out in a hotfix today. I can give gory details in another post if people care but the two major problems we're working around in this update are 1) ISPs that block the default IRC port, and 2) Routers that corrupt IRC traffic with NAT substitutions. I should point out that neither of these are our fault and yet regardless I spent a huge amount of time finding workarounds (hell, we've even purchased malfunctioning routers to try to work around bugs in devices we can't change).

It's only been with the tireless help from several users that we've been able to isolate several of these problems(Sherbniz, nebulosa, and Krjal especially). We're working around bugs in hardware we don't even have remote access to and so I hope you can appreciate how time consuming this is.

[Auxeus]

@DE_Glen

 

Many thanks for the status report.

 

But troubleshoot with hardwares sound ineffective as the cost and time consuming are high, the problem is iirc itself that has port and packets incompatibility as far you diagnosed. There should be a generic way to communicate like in most MMOs without problems with router and ISPs.

 

I know is not cool to push, yet i'm frustrated at the same time since i only play this nowdays and gotten into it.

[Fiia]

Sherbniz, I want to say THANK YOU for all you have done to get my chat working. The 0/100/1000Mbps 5-Port Gigabit Ethernet Desktop Switch worked like a charm (once I hooked the cables up properly!).

Problem solved for about $24.00.

I now have a phone, internet, and WF chat. This is a great day, thank you so much, and who knows, I may even see you in chat at some point. :)

Edited June 26, 2013 by Fiia

[GBTW]

It seems like the latest hotfix or something done around that time broke the chat again. I changed nothing in my PC or router configuration. It had been working since the 12th of June updates.

 

Its weird since I can connect fine to the IRC server using an outside client:

 

* Looking up 96.47.186.233

* Connecting to 96.47.186.233:6668 (96.47.186.233:6668)

* Connected. Now logging in.

 

And using Wireshark I can see the connection going through just fine, Warframe sends the NICK and USER commands and the game receives the "Welcome to the warframe IRC network GBTW" etc.

There are however a bunch of retransmission packets for the JOIN command, it keeps trying to join a channel but not reply is ever received, this is when the 100054 error shows up.

 

I can provide the .pcapng file for this capture if needed.

[insane99]

@DE_Glen

i also wanted to thank you for spending time on this and really appreciate it i really dont understand why this problem suddenly occur after new patch but tks to you i can hope that it will be resolver as soon as it can be tks again and please don give up on us we are huge fans of the game and the reason we are frustrated is because it is such an awesome game.:)

[[DE]Glen]

It seems like the latest hotfix or something done around that time broke the chat again. I changed nothing in my PC or router configuration. It had been working since the 12th of June updates.

 

Its weird since I can connect fine to the IRC server using an outside client:

 

 

 

 

And using Wireshark I can see the connection going through just fine, Warframe sends the NICK and USER commands and the game receives the "Welcome to the warframe IRC network GBTW" etc.

There are however a bunch of retransmission packets for the JOIN command, it keeps trying to join a channel but not reply is ever received, this is when the 100054 error shows up.

 

I can provide the .pcapng file for this capture if needed.

This sounds exactly like the issue we rolled out a workaround for 10 minutes ago. Try now?

[ChrizzieCostanzie]

THANK YOUUUUUU DE_GLEN THE HOTFIX FIXED MY ERROR 10060 XD

[Kamentari]

I can use the chat again :D thanks again Glen!

and I don't knwo what to say there haha, at least now I can let people know when rare material have dropped and invite to void runs to people in my clan yess!

[GBTW]

This sounds exactly like the issue we rolled out a workaround for 10 minutes ago. Try now?

 

Yep, fixed. Thank you so much.

[Auxeus]

Chat works now, thanks so much for the hardwork.

[Sherbniz]

The chat works for me... You are a magician!

Thank you SO VERY much for all the hard work you put into this!

Your perseverance and ingenuity in solving these problems is unparalleled!

I won't forget this! And I have a feeling I owe you... big time! :D

Thanks again!

[Melonade]

Hey, I can see words! Thank you so much.

[Ronindream]

I owe a drink to you, DE_Glenn, and those who helped you fix this. I can finally chat. Cheers.

[Snowbrush]

YAY! Chat is finally fixed for me! Thank you so much!!

[Krjal]

Glen, you're brilliant!

 

I was just logging in to send you some mIRC caps (which you probably never want to see now! :D) and saw the changelog.

I can't thank you enough.

 

If it's possible, would you mind letting us know how you got around the problem? I'd love to get a couple of other IRC things working now. Totally understand if you don't have the time though. I imagine there are a million other things you want to do instead of think about recv errors :p

 

Thanks again. I'll see you all around the system, Tenno!

[insane99]

@DE_Glen

tks sooo sooo much it works i got the error for a sec but then was resolved on is working fine thank you soo much 

[Doitordie]

I dont wanna be rude but the hotfix didn't solve my problem i got the Error 10013 can you please help me?

[[DE]Glen]

I dont wanna be rude but the hotfix didn't solve my problem i got the Error 10013 can you please help me?

Looks like firewall rule is preventing you from even making the outbound connection.

[[DE]Glen]

If it's possible, would you mind letting us know how you got around the problem? I'd love to get a couple of other IRC things working now.

Your NAT router was corrupting data; I personally confirmed this with packet captures from 3 different people and I wouldn't have believed it unless I'd seen it with my own eyes -- it's happening deliberately.

Normally NAT routers translate addresses in the packet headers (which is what you want) but in this case it's translating data in the body of the packet (bat-shit crazy).

Evidence: in your packet capture look at the welcome message line and check the IP address (it says we see you as coming from); you'll notice that this has been set to your router's internal address, something our IRC server couldn't possibly have known!

When comparing packet captures of what we send and what people receive I noticed this discrepancy (when I went back I checked and all the captures I had showed this abuse!). This may sound benign, helpful even, but it causes HUGE problems when it changes the length of the network packet and your ACKs don't line up with the data we think we sent; in some cases this makes you try to ACK data we haven't even sent you yet and these ACKS are dropped for being bogus -- this makes you unable to ACK data, so you go silent, and we assume you've been disconnected, and 10054 happens.

This has less impact on many public IRC servers because they do reverse-DNS lookups for your IP address so instead of welcoming you by your 64.12.13.111 IP you get welcomed as dyn1234.comcast.west.com or something non-numeric that your router doesn't try to substitute. However, to support 30,000 users at once on the same IRC server we turn off these reverse-lookups to save time and this leaves use wide open to being screwed over by bad routers. My fix was to modify the server software to avoid every sending you a packet with your IP address in it.

The 10060 errors are almost certainly bad ISPs blocking the default IRC port; we used to use several ports but we noticed that there was a conflict with another protocol so we changed to the standard 6667; suddenly people stopped being able to connect at all. Again, how were we to know that by following the standard we'd actually have more problems? The hotfix includes an incremental search of a number of ports we have open so that if your ISP blocks 6667 you might still get through (and this seemed to work for a lot of people).