Sunday, August 14, 2011

Motorola Surfboard SB6580 Playing Nice With Apple's Airport Extreme


This past week my Zoom cable modem was dropping my connection a lot due to the increased speeds that Cox was delivering in my Premium Internet package. The current service should deliver around 25Mpbs down and about 15Mbps up but I was not seeing anywhere near that.  I had the Cox technician come out to adjust some of the connections inside and outside the house and he recommended using a Docsis 3.0 compliant cable modem.  I did some research and found the Motorola Surfboard SBG-6580 which has a DOCSis 3.0 cabel modem coupled with a dual Wireless N router that can have both a internal and guest wireless broadcast.

Inside the house I have the first generation N Wirelless Apple Airport Extreme which has been functioning as my router for the past 3 or so years.  First I read a couple of posts on just disabling NAT on the Surfboard and keeping my router configuration on the Aiport the same.  This worked alright but was prone to losing connectivity since there is really no way to completely disable the router portion of the Surfboard. This resulted in both devices being disconnected and then the Surfboard being put back online followed by the Airport.  

To avoid this issue, I opted to do the following:

  1. Use the Motorola router's NAT (aquiring the public IP from the ISP)
  2. Setup the Airport to hand out a series of addresses on the same submet (10.0.x.10 - 25)

Below are the setup screens for the settings in both the Surfboard and Airport:


Once the Surfboard's modem connects, it will establish that verified handshake with your ISP, then the router gets the public address and distributes an address to the Airport.  The airport is given a specific range of address which get marked STATIC on the Surfboard and all your devices are now talking to the Airport without any disruption.  This has been bomber even if the power goes out and the system comes back up.  Below are my connection stats:


Thursday, August 4, 2011

ChromeBook Experiment, and It Looks Promising


On June 15, 2011 Google's official Chrome operating system was finally released and hit the market on a couple of models by Samsung and Acer.  ChromeOS is a lightweight operating system built on a striped down version of Linux to run the Chrome browser.

Since I live on Google and our company is also on Google Apps, I wanted to see how feasable it was to function on a device so forward thinking.  Obviously this is not a replacement device for a superuser or someone who has specific needs like running SolidWorks or doing long form video editing.  What it does offer is a sleak device that boots in 8 seconds, (6 to the login screen) from the off state and gets you on the Internet to do what we all do there, browse, research, email, socialize, share...and the list goes on and on.

With so many companies attempting to move today's desktop applications like video editing, engineering tools like CAD and other CAE applications,  even going as far as hosting full sofware developement environments to offload the resources need by the user. 

Personally I have been interested in this for a couple years and had purchased a eee701 on Amazon for about $140 USD and installed ChromiumOS, the open source project of Google's ChromeOS, in order to get a feel for how this could be.  The early days were rough, as many open source tools are at first, but I have to say Google has really moved this product forward and it is a pretty good V1 product.  Don't get me wrong, there is still room for improvement but instead of focusing on what an internet browser only operating system can't do, focus on what it can.  

So over the next month or so I am going to put the 11" Acer Chromebook to the test and see how it stacks up to other secondary computing devices like tablets and smartphones. So far the only major issues I have run into would be:

  • GoToMeeting is not supported
  • Skype is not yet supported for the full experience
  • VPN for Cisco (although the current build does support L2TP/IPSEC (with shared key or user cert)
So far most of my usage is very doable on the Chromebook.  Server management for Linux is simply done via SSH by doing a CTRL+ALT+T and that lands you in terminal and away you go.  Remote Desktop for Windows can be done with certain extensions but does require a VPN connection so I am personally out of luck till the CISCO VPN support is available, which Google promises.  More information to come in the weeks to follow. ~Lou