Can we at least get a canned response that you are aware of the updater causing modems/routers to crash? I finally got my system stable again after all of the problems the launcher caused last night, and I won't even attempt to log in until a dev says that its fixed.
And yes, I have read the work around fix for it, and I appreciate the effort that Scott put into it. But I don't think anyone here should be forced to start altering their networks for a change that Cryptic made.
Your resident devlurker is at a conference this week, so it is being worked on by others. I do not know the current status beyond what SuperMartin has posted.
Your resident devlurker is at a conference this week, so it is being worked on by others. I do not know the current status beyond what SuperMartin has posted.
Are you referring to the other launcher that he posted?
How is that possible? The only thing that I can think of that could explain this would be a particular brand of modem or firewall that has a bug that is now being triggered by something the launcher is doing.
Have you checked for a firmware update for your modem/firewall?
How is that possible? The only thing that I can think of that could explain this would be a particular brand of modem or firewall that has a bug that is now being triggered by something the launcher is doing.
Have you checked for a firmware update for your modem/firewall?
There is a 13+ page thread on it in this forum. Seems to be numerous models/brands of routers and modems. It was something that was changed with the last patch that caused it.
There is a 13+ page thread on it in this forum. Seems to be numerous models/brands of routers and modems. It was something that was changed with the last patch that caused it.
I don't usually browse individual forums, I tend to stick to the Dev Tracker.
I have over a decade of IT experience, and I currently manage 150 Servers (each with their own firewall and on different networks). That isn't to say that I can't be wrong, because I learn new stuff every day, but in my experience it shouldn't be possible for a particular piece of software to have a problem that crashes network equipment.
We once had a particular firmware revision on the firewalls we deploy with our servers that had a bug in it. The bug would cause the firewall to crash if it received too much of a particular UDP broadcast. The problem wasn't with the software though -- it was making perfectly reasonable broadcasts. The problem was with the firewalls. The problem you are describing sounds like this kind of issue.
See, I didn't think that the software could be causing it either until I read the 13 page thread in here that has numerous people having the exact same problem all after the patch on Friday. Either way, I forgot to update this last night, but I got the new launcher to work. I had to try it several times but it finally got going. Thanks coderanger, and sorry for the ****y thread.
Comments
Are you referring to the other launcher that he posted?
How is that possible? The only thing that I can think of that could explain this would be a particular brand of modem or firewall that has a bug that is now being triggered by something the launcher is doing.
Have you checked for a firmware update for your modem/firewall?
There is a 13+ page thread on it in this forum. Seems to be numerous models/brands of routers and modems. It was something that was changed with the last patch that caused it.
I just tried the new launcher. It says loading please wait, and thats it
I don't usually browse individual forums, I tend to stick to the Dev Tracker.
I have over a decade of IT experience, and I currently manage 150 Servers (each with their own firewall and on different networks). That isn't to say that I can't be wrong, because I learn new stuff every day, but in my experience it shouldn't be possible for a particular piece of software to have a problem that crashes network equipment.
We once had a particular firmware revision on the firewalls we deploy with our servers that had a bug in it. The bug would cause the firewall to crash if it received too much of a particular UDP broadcast. The problem wasn't with the software though -- it was making perfectly reasonable broadcasts. The problem was with the firewalls. The problem you are describing sounds like this kind of issue.