Como migrar tus equipos en Weaved a

Para los que tenemos dispositivos a los que accedemos de forma remota usando el servicio de Weaved muy probablemente les llego el correo que cuenta con una nueva plataforma llamada a la cual debemos migrar, el proceso es súper sencillo, ingresamos primero al sitio usando las mismas credenciales que usábamos en Weaved.

Nos mostrara un mensaje donde dice que aun no hemos agregado ningún dispositivo, ahora nos vamos a nuestro dispositivo (yo tengo un par de raspberry pi) y desde una terminal ejecutamos los siguientes comandos.

$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo weavedinstaller

El ultimo comando nos abrira el asistente de configuracion de Weaved que notaremos que en esta ocacion se conecta a, nos pedira que ingresemos el correo y la clave con la que nos conectamos a como puedes ver en la pantalla siguiente.

Luego, nos pedirá que ingresemos un nombre para nuestro dispositivo, al final nos mostrara los servicios que ya están publicados si queremos aprovechar y agregar o quitar uno este es el momento, de lo contrario presionamos el 4 para salir, luego si refrescas la pantalla de notaras que ya esta tu dispositivo y al hacer clic en el una pantalla te mostrara los servicios que puedes acceder de forma remota.

Cerca de 10 millones de IPs involucradas en el pasado ataque DDoS a Dyn

Sobre el ataque DDoS a Dyn que afecto los servicios muchos sitios web entre ellos Twitter, Spotify, Reddit y The New York Times el pasado 21 de Octubre de 2016, Kyle York (Chief Strategy Officer de Dyn) en un comunicado hace unos días expreso como datos preliminares que según las investigaciones que aun están en proceso el ataque provino de la botnet Mirai la cual involucro un aproximado de 10 millones de IPs.

A continuación les dejo el comunicado completo que se publico en el blog de Dyn.

It’s likely that at this point you’ve seen some of the many news accounts of the Distributed Denial of Service (DDoS) attack Dyn sustained against our Managed DNS infrastructure this past Friday, October 21. We’d like to take this opportunity to share additional details and context regarding the attack. At the time of this writing, we are carefully monitoring for any additional attacks. Please note that our investigation regarding root cause continues and will be the topic of future updates. It is worth noting that we are unlikely to share all details of the attack and our mitigation efforts to preserve future defenses.

I also don’t want to get too far into this post without:

1. Acknowledging the tremendous efforts of Dyn’s operations and support teams in doing battle with what’s likely to be seen as an historic attack.

2. Acknowledging the tremendous support of Dyn’s customers, many of whom reached out to support our mitigation efforts even as they were impacted. Service to our customers is always our number one priority, and we appreciate their understanding as that commitment means Dyn is often the first responder of the internet.

3. Thanking our partners in the technology community, from the operations teams of the world’s top internet companies, to law enforcement and the standards community, to our competition and vendors, we’re humbled and grateful for the outpouring of support.

Attack Timeline

Starting at approximately 7:00 am ET, Dyn began experiencing a DDoS attack. While it’s not uncommon for Dyn’s Network Operations Center (NOC) team to mitigate DDoS attacks, it quickly became clear that this attack was different (more on that later). Approximately two hours later, the NOC team was able to mitigate the attack and restore service to customers. Unfortunately, during that time, internet users directed to Dyn servers on the East Coast of the US were unable to reach some of our customers’ sites, including some of the marquee brands of the internet. We should note that Dyn did not experience a system-wide outage at any time – for example, users accessing these sites on the West Coast would have been successful.

After restoring service, Dyn experienced a second wave of attacks just before noon ET. This second wave was more global in nature (i.e. not limited to our East Coast POPs), but was mitigated in just over an hour; service was restored at approximately 1:00 pm ET. Again, at no time was there a network-wide outage, though some customers would have seen extended latency delays during that time.

News reports of a third attack wave were verified by Dyn based on our information. While there was a third attack attempted, we were able to successfully mitigate it without customer impact.

Dyn’s operations and security teams initiated our mitigation and customer communications process through our incident management system. We practice and prepare for scenarios like this on a regular basis, and we run constantly evolving playbooks and work with mitigation partners to address scenarios like these.

What We Know

At this point we know this was a sophisticated, highly distributed attack involving 10s of millions of IP addresses. We are conducting a thorough root cause and forensic analysis, and will report what we know in a responsible fashion. The nature and source of the attack is under investigation, but it was a sophisticated attack across multiple attack vectors and internet locations. We can confirm, with the help of analysis from Flashpoint and Akamai, that one source of the traffic for the attacks were devices infected by the Mirai botnet. We observed 10s of millions of discrete IP addresses associated with the Mirai botnet that were part of the attack.

Thank You Internet Community

On behalf of Dyn, I’d like to extend our sincere thanks and appreciation to the entire internet infrastructure community for their ongoing show of support. We’re proud of the way the Dyn team and the internet community of which we’re a part came together to meet yesterday’s challenge. Dyn is collaborating with the law enforcement community, other service providers, and members of the internet community who have helped and offered to help. The number and type of attacks, the duration, the scale, and the complexity of these attacks are all on the rise. As a company, we have for years worked closely with the internet community to assist when others encountered attacks like these and will continue to do so.

It is said that eternal vigilance is the price of liberty. As a company and individuals, we’re committed to a free and open internet, which has been the source of so much innovation. We must continue to work together to make the internet a more resilient place to work, play and communicate. That’s our commercial vision as a company and our collective mission as an internet infrastructure community. Thank you.

Kyle York Chief Strategy Officer

Cambios de precios en planes Web Hosting

A continuación les dejo los cambios de precio mas recientes en planes de Shared Web Hosting o Alojamiento Web Compartido. Para mayor detalle, otros proveedores y comparativas visita

iPage sube su precio introductorio de $1.99 US a $3.25 USD mensuales.

JustHost baja su precio introductorio de $3.95 US a $2.95 USD mensuales.

BlueHost sube su precio introductorio de $3.95 US a $2.95 USD mensuales.

HostMonster baja su precio introductorio de $4.95 US a $2.95 USD mensuales.

Hostgator sube su precio introductorio de $3.45 US a $3.95 USD mensuales.