Just for info, if in the future you run across threads that you want to get notifications about, but don't really want to say anything, you can subscribe to them. It's in the upper right corner of a thread. Click on Subscribe.
Good morning dodgeball024,
Thanks for checking in. So far only one beam, 68, has the fix, but the rest of the beams in its gateway (SDO- 64 and 66) will get it next week. Eventually the fix will be rolled out to all beams, depending on how this update goes for these preliminary beams. We'll let you know once we find out when this might be.
Your patience and understanding are much appreciated.
This article explains how to figure out many things about your system... Specifically what beam you are on, and which gateway it's tied to.
If you are using a 3rd party DNS, the link to the System Control Center on the site Corrosive listed may not work. In that case, you can get to it here... http://192.168.0.1/#!/usage
To find your beam, go to http://192.168.0.1/#!/usage, then click on System Information. The beam ID is listed in the box labeled Satellite.
How do I know what "beam" I'm in?
You can use this direct link, too... http://192.168.0.1/#!/home/information
The Satellite Box is on that page.
@maratsade I was just reading through this and it made me laugh a little, as eranch asked such a simple question, yet we keep giving links that nearly get him/her there. LOL. It just struck me as funny.
I didn't mean to really go off topic, but it just hit my funny bone.
I thought that was funny too. LOL
I was just reading through this and it made me laugh a little, as eranch asked such a simple question, yet we keep giving links that nearly get him/her there. LOL. It just struck me as funny.
Wondering when the rest of the beams will be updated. I actually worked for an entire day last week with out losing connection once but have already lost it twice within the first hour today. I'm on beam 33, Gateway 17.