Tagged: network


Cox Communications is Looking for a Lawsuit

For the love of data caps Batman! Cox Communications is taking its ability to be a very bad corporate citizen to the next level this week. Not only are they throttling users with “unlimited” data, but they are punishing the whole network segment these users are on as well. Ars Technica reports, and Cox confirms, that they are doing this to keep their network experience consistent for all users… And by consistent they mean consistently bad.

Not only are their “gigabit” plans not actually gigabit (you only get “gigabit” download speeds, Cox caps you at 35 Mbps upload all the time), their “unlimited” data appears to not be the case either. When I hear of “unlimited” data that means that you can use all the data you want at the speed of the service tier you pay for. Apparently for Cox this means that you can do that until they decide that you have used too much data in your “unlimited” data plan and then the throttle you to 10 Mbps maximum for uploads. Then they start to threaten to terminate your account because you have used too much “unlimited” data on their network. So rather than getting what you paid extra for, you now get 72% less upload bandwidth and threatening phone calls.

The kicker is that not only does Cox take out their corporate wrath on the customer using more than their allotted “unlimited” amount of data, they also also take it out on everyone attached to that segment of the cable modem network. This is why I think the class action lawsuit is going to start really soon, likely for the following reasons:

  1. Cox is punishing others for a situation they didn’t cause nor can control.
  2. Cox is punishing people for using the service in a way that they reasonably should expect to be able to do given the plans they paid for.
  3. The “unlimited” data add-on is clearly false advertising if they are throttling connections based on using too much data.
  4. Cox is threatening the termination of contracts based on usage patterns that a reasonable person would expect to be allowed given the plans they are paying for.

I’m waiting to see the pandemonium that ensues when the attorneys start trying to pile on to this one. While Mike, who spoke to Ars, may only get a few bucks, the attorney fees will certainly be very enticing.

Aside from the class action lawsuit though, this is yet another example of cable companies abusing their customers because they can’t actually provide the service levels they promise. Or at the very least, this is a greed ridden money grab targeted at the customers that are already paying more for services to supposedly guarantee a positive experience. Instead of improving their networks, or better yet, just running fiber, carriers choose to act as parasites. They get away with this because in many areas there is only one broadband provider available so consumers have no choice. The perfect example of why monopolies are not supposed to be allowed by US laws and regulations.

What can you do to try and avoid Mike’s fate, or if you can’t avoid it, at least try and improve your situation? Start with these:

  1. Avoid cable companies whenever possible, or if you can’t try and sign up for fiber service if they offer it. Always choose fiber over a cable modem.
  2. Complain loudly and frequently to the carrier. The squeaky wheel gets the grease.
  3. Push for net neutrality regulation. Don’t let the FCC off the hook for pandering to big carriers and not the consumers that have to put up with this type of abuse.
  4. Report deceptive or unethical business practices to federal, state, and local regulators.
  5. Talk to news outlets about what you are experiencing. Nothing is better than shining the light on these situations. If the negative PR gets bad enough, these carriers will backpedal.
  6. And if you really feel like the case warrants it, talk to an Attorney.

I am curious to see what happens to Cox over the coming weeks as this story gains traction. Will they backpedal? Will we see a class action lawsuit? Will Cox realize the error of their ways and become a beacon of corporate benevolence in a corrupt world?

Who knows, but it will certainly be interesting to watch.


pfSense + Ubiquiti = <3

So I have a new weekend DIY project to work on over the next several days. I just bought a new pfSense firewall appliance along with some Ubiquiti WiFi access points for the house. I decided that it is time to get serious about securing our home network since we have so many IoT devices around these days.

At this point I have ordered the hardware and am beginning to get things planned out. for the install. I will continue to document the experience here as I go.


  • QOTOM-Q190G4-S02 Barebone Industrial PC Gateway Router for pfSense – Intel J1900 4 Gigabit NICs
  • Crucial 8GB Single DDR3/DDR3L 1600 MT/S (PC3-12800) Unbuffered SODIMM 204-Pin Memory – CT102464BF160B
  • Dogfish Msata 120GB Internal Solid State Drive Mini Sata SSD Disk
  • Ubiquiti Unifi Ap-AC Lite – Wireless Access Point – 802.11 B/A/G/n/AC (UAPACLITEUS)
  • Ubiquiti Unifi Cloud Key – Remote Control Device (UC-CK)

Installing pfSense

First thing’s first, I had to open up my QOTOM PC and install the RAM and mSATA SSD in on the board. This was very easy to do, all that was required was to remove the four case screws using a Philips head screw driver. From there, the RAM and mSATA job just slide into their respective slots on the motherboard. You will need to hold the mSATA drive in place with a screw as well that is already on the motherboard when you open the PC case.

Once all of this was set, I downloaded (https://www.pfsense.org/download/) and burned a copy of pfSense to a DVD and connected a USB external DVD-ROM to the QOTOM PC along with a keyboard, mouse, and VGA based monitor. I powered everything up and… failure. The PC hung at the pfSense “booting” prompt. After some quick Google searching it was clear I was not the first to experience this with the latest version of pfSense. The short explanation is that the version of freeBSD that pfSense uses doesn’t like some graphics chipsets so the console hangs. To get around this you need to add the following line to your boot settings:

set kern.vty=sc

Once this was done everything very well. Installation proceeded without any other major issues. I essentially took all of the defaults in the installation and had the installer partition my SSD automatically.

pfSense Console Options

The QOTOM comes with four ethernet ports so you will need to tell pfSense what to do with all of them once the PC boots for the first time after installation. When the system has booted you will get to a menu with a list of console administration options to choose from. You will need to select the menu item for assigning interfaces for pfSense system. The console program will then walk you assigning your WAN, LAN and optional interfaces. In my case I did the following:

igb2Opt 1
igb2Opt 2