Quote:
I could log on if I saw somebody else on there, I might log on and hang around vesper bridges.
I'm hoping to be about once or twice over the next week or so, my usual - make some stuff, bash a monster or two 
Quote:
I am -really- -REALLY- sorry about this.
So I went under contract for a house in december.
It finally closed near the end of februrary, with some contingent repairs. I've been rushing those as fast as possible, and they just finished the inside today. Lots outside to do but enough i can move in.
I'm moving sunday.
What this means for you guys:
2 periods of downtime.
First one is when i move the actual server and get the DNS updated to the new address. This one should be sunday CST about 7-8am to probably 11-12/ish + dns propagation time.
Second one will be later when i take it down to bring the proper network online. With any luck that will be a very quick changeover and any prolonged downtime will be getting the new network layers working.
However in return for this slight hiccup, it will finally be out of the rather poor cable based internet the server was hosted on, and on to gigabit fiber that should have drastically better uptime and relatively low levels of latency(unmeasured but initial install tests were in the 20-40 range vs current connection of 80-160 during peak). Also when the proper networking comes on after the second time, the server will not only be isolated but have proper priority on the channel like it used to, as well as a new gateway that should eliminate the clog issue a small percent experienced in large changes due to the older protocol.
It will literally be the last thing disconnected and the first thing hooked up in the initial move.
I hope it all goes nice and smooth for you Bob So I went under contract for a house in december.
It finally closed near the end of februrary, with some contingent repairs. I've been rushing those as fast as possible, and they just finished the inside today. Lots outside to do but enough i can move in.
I'm moving sunday.
What this means for you guys:
2 periods of downtime.
First one is when i move the actual server and get the DNS updated to the new address. This one should be sunday CST about 7-8am to probably 11-12/ish + dns propagation time.
Second one will be later when i take it down to bring the proper network online. With any luck that will be a very quick changeover and any prolonged downtime will be getting the new network layers working.
However in return for this slight hiccup, it will finally be out of the rather poor cable based internet the server was hosted on, and on to gigabit fiber that should have drastically better uptime and relatively low levels of latency(unmeasured but initial install tests were in the 20-40 range vs current connection of 80-160 during peak). Also when the proper networking comes on after the second time, the server will not only be isolated but have proper priority on the channel like it used to, as well as a new gateway that should eliminate the clog issue a small percent experienced in large changes due to the older protocol.
It will literally be the last thing disconnected and the first thing hooked up in the initial move.
