Worth Reading: Plumgrid, Cumulus, and SDN
The post Worth Reading: Plumgrid, Cumulus, and SDN appeared first on 'net work.
Can != Should, Is != Ought
Maybe I’m getting too old for my own good. Or maybe studying philosophy is making me older. Here in the US, though, it is Memorial Day, a day where people normally grill burgers and dogs, throw a few back, and forget to ask why. It’s just another day off, and days off are good for—well, for something.
Memorial Day, in the US, stands in memorial for those who fought—and, specifically died—for our freedom. But what is freedom? In my world, there are two types of freedom: freedom from, and freedom to. Two pieces this week made me think through this difference once again, and how we are increasingly confusing the two concepts.
But the big thing that changed this week is a Google home device is no longer a theoretical possibility. It’s here. And on a sunny day at the outdoor amphitheater, just a half mile away from the Googleplex, the audience watched as a video showed the device at work in the home of a typical American family. There was laughter when the dad broadcast his playlist into every room in the home, waking up his sleeping children — and then later remotely turned on the lights to make Continue reading
Worth Reading: The Problem with Analytics
The post Worth Reading: The Problem with Analytics appeared first on 'net work.
Migrating to BGP
The post Migrating to BGP appeared first on Noction.
MIT WiFi Technology Promises Precise Location Tracking
Researchers develop Chronos, a new method for determining the location of WiFi devices with decimeter accuracy.
Strain relief
I’ve got a problem with sagging cables, and I’ve got a simple solution. Examine the side-by-side images below which show the same fiber connection between a switch and a firewall. The image on the left shows a sagging cable which crosses in front of the switch in the rack unit just below it.
As you may know, this cabling install is a violation of the 167th rule of networking:
Thou shalt contain your cables to your own rack unit and shalt not, under any circumstances, impede access to other rack units or blades.
The image on the right ticks the box for me. There’s no room for a dedicated 1RU horizontal cable manager, but there is room for a zero-RU strain relief bar (as seen below). The result is a relatively neat cabling job. It’s no work of art, but it’s functional.
A strain-relief bar is a cheap metal bar that you can bolt on when you rack-mount your switch. It allows you to velcro your fiber patches to the bar, taking the strain to help prevent breaks and preventing the dreaded cable droop. You should, of course, take care to ensure you don’t block access to any field-replaceable units, cards or ports on your network device.
The strain-relief bar Continue reading
Strain relief
I’ve got a problem with sagging cables, and I’ve got a simple solution. Examine the side-by-side images below which show the same fiber connection between a switch and a firewall. The image on the left shows a sagging cable which crosses in front of … Continue reading
The post Strain relief appeared first on The Network Sherpa.
Building a L2 Fabric on top of VXLAN: Arista or Cisco?
One of my readers working as an enterprise data center architect sent me this question:
I've just finished a one-week POC with Arista. For fabric provisioning and automation, we were introduced to CloudVision. My impression is that there are still a lot of manual processes when using CloudVision.
Arista initially focused on DIY people and those people loved the tools Arista EOS gave them: Linux on the box, programmability, APIs… However
Read more ...Doing a ‘full scan’ of the Internet right now
So I'm doing a "full" scan of the Internet, all TCP ports 0-65535 on all addresses. This explains the odd stuff you see from 209.126.230.7x.
I'm scanning at only 125kpps from 4 source IP addresses, or roughly 30kpps from each source address. This is so that I'll get below many thresholds for IDSs, which trigger when they see fast scans from a single address. The issue isn't to avoid detection, but to avoid generating work for people who get unnecessarily paranoid about the noise they see in their IDS logs.
This scan won't finish at this speed, of course, it won't get even close. Technically, it'd take 50 years to complete at this rate.
The point isn't create a comprehensive scan, but to do sampling scan. I'll let it run a week like this, which will get 0.1% of the Internet, and then stop the scan.
What am I looking for? I don't know. I'm just doing something weird in order to see what happens. With that said, I am testing any port I connect to with Heartbleed. This should give us an estimation of how many Internet-of-Things devices are still vulnerable to that bug. I'm Continue reading