Whats next…

I have a lot of non-technical related projects in the pipeline, but study wise, whats next up for me is the IOS XR specialist exam.

I think the blueprint for it looks interesting and it provides a way for me to learn more about IOS XR.

I don’t really have a date for the exam just yet as I’m taking it easy and trying to lab out as much as i can to have it stick.

I will be posting about anything i find interesting or different from Classic IOS. Right now I’m trying to figure out the details on the LPTS implemented on XR platforms. A way of protecting the management/control plane of the router.

Take care!

Why You Should Learn to Code

I took a few C++ and Visual Basic courses back in high shcool. Now, at that time, they didn’t teach the STL (Standard Template Library), I remember using conio.h allot...

[[ Summary content only, you can read everything now, just visit the site for full story ]]

Impact of the FCC 5 GHz U-NII Report & Order on Wi-Fi Networks

Following the news release of the FCC's actions to change some technical rules for the 5 GHz U-NII bands, the official Report and Order was released on Tuesday.

I've read through the R&O, and here are the technical modifications that were approved:
  • U-NII 1 band (5.150 - 5.250 GHz) indoor operation restriction is removed. This allows use of the band for outdoor hotspots, WISPs, and bridge links. The growth of public hotspots will clearly benefit from this change.

  • U-NII 1 band (5.150 - 5.250 GHz) power level restrictions are changed. 
  • AP power levels at the Intentional Radiator may be 1W (previously 50mW) and the EIRP may be 4W using a 6dBi antenna (previously 200mW), and following the 1dB reduction rule in transmitter power for every 1dB of antenna gain above 6dBi. 
  • Client power levels at the IR may be 250mW and the EIRP may be 1W, following the 1:1 dB reduction rule for antenna gain above 6dBi.
  • WISPs may use up to 23dBi antennas on fixed point-to-point links without any corresponding reduction in transmitter power.

    These changes help to unify the U-NII 1 band with the U-NII 2A/2C and U-NII 3 bands so Continue reading

Learn to Code

Background I took a few C++ and Visual Basic courses back in high shcool. Now, at that time, they didn’t teach the STL (Standard Template Library), I remember using conio.h allot, not really...

[[ Summary content only, you can read everything now, just visit the site for full story ]]

Learn to Code

Background I took a few C++ and Visual Basic courses back in high shcool. Now, at that time, they didn’t teach the STL (Standard Template Library), I remember using conio.h allot, not really...

[[ Summary content only, you can read everything now, just visit the site for full story ]]

Learn to Code

Background I took a few C++ and Visual Basic courses back in high shcool. Now, at that time, they didn’t teach the STL (Standard Template Library), I remember using conio.h allot, not really...

[[ Summary content only, you can read everything now, just visit the site for full story ]]

Cisco, ACI, OpFlex and OpenDaylight

Cisco's April 2nd, 2014 announcement - Cisco and Industry Leaders Will Deliver Open, Multi-Vendor, Standards-Based Networks for Application Centric Infrastructure with OpFlex Protocol - has drawn mixed reviews from industry commentators.

In, Cisco Submits Its (Very Different) SDN to IETF & OpenDaylight, SDNCentral editor Craig Matsumoto comments, "You know how, early on, people were all worried Cisco would 'take over' OpenDaylight? This is pretty much what they were talking about. It’s not a 'takeover,' literally, but OpFlex and the group policy concept steer OpenDaylight into a new direction that it otherwise wouldn’t have, one that Cisco happens to already have taken."

CIMI Corp. President, Tom Nolle, remarks "We’re all in business to make money, and if Cisco takes a position in a key market like SDN that seems to favor…well…doing nothing much different, you have to assume they have good reason to believe that their approach will resonate with buyers." - Cisco’s OpFlex: We Have Sound AND Fury

This article will look at some of the architectural issues raised by Cisco's announcement based on the following documents:
The diagram at the top of this article illustrates the Continue reading

Parsing a Routing Table with Python – Part 2

In the previous article (they’re split to make them easier to read) I talked about the theory and representation. How a properly formatted data structure and a non-formatted data structure look like....

[[ Summary content only, you can read everything now, just visit the site for full story ]]

Parsing a Routing Table with Python – Part 2

In the previous article (they’re split to make them easier to read) I talked about the theory and representation. How a properly formatted data structure and a non-formatted data structure look like....

[[ Summary content only, you can read everything now, just visit the site for full story ]]

Parsing a Routing Table with Python – Part 1

It’s all in the API’s, well, not exactly, not everything you want to get or parse is handed down in a nicely formatted XML file or JSON format. These file structures translate to some type of data...

[[ Summary content only, you can read everything now, just visit the site for full story ]]

7 all-in-one security suites: Anti-malware for all your devices

Let's face it: No matter what device you use, you're in danger. Security threats and malware lurk on Windows PCs, Macs, and Android and iOS devices. If you use more than one device -- like most of us do -- that makes it even more difficult and expensive to be vigilant and keep yourself safe.That's where all-in-one security suites come in. They protect not just a single device, but multiple ones, and offer comprehensive security for a far lower price than if you had to buy software individually for each of your devices.All of the suites reviewed here protect Windows, Macs and Android devices. A few add iOS security as well. Most offer some kind of Web-based dashboard for installing and managing the software on each individual device.To read this article in full or to leave a comment, please click here

Indonesia Hijacks the World

Yesterday, Indosat, one of Indonesia’s largest telecommunications providers, leaked large portions of the global routing table multiple times over a two-hour period. This means that, in effect, Indosat claimed that it “owned” many of the world’s networks. Once someone makes such an assertion, typically via an honest mistake in their routing policy, the only question remaining is how much of the world ends up believing them and hence, what will be the scale of the damage they inflict? Events of this nature, while relatively rare, are certainly not unheard of and can have geopolitical implications, such as when China was involved in a similar incident in 2010.

Keep in mind that this is how the Internet is designed to work, namely, on the honor system. Like Twitter and Facebook, where you can claim to be anyone you want, Internet routing allows you to lay claim to any network you want. There is no authentication or validation. None. But unlike Twitter and Facebook, such false claims propagate through the world in a matter of seconds and decisions, good or bad, are made algorithmically by routers, not humans. This means that innocent errors can have immediate global impacts. In this incident, Continue reading

Hijack event today by Indosat

Today we observed a large-scale ‘hijack’ event that affected many of the prefixes on the Internet. This blog post is to provide you with some additional information.

What happened?
Indosat, AS4761, one of Indonesia’s largest telecommunication networks normally originates about 300 prefixes. Starting at 18:26 UTC (April 2, 2014) AS4761 began to originate 417,038 new prefixes normally announced by other Autonomous Systems such as yours. The ‘mis-origination’ event by Indosat lasted for several hours affecting different prefixes at different times until approximately 21:15 UTC.

What caused this?
Given the large scale of this event we presume this is not malicious or intentional but rather the result of an operational issue. Other sources report this was the result of a maintenance window gone bad. Interestingly we documented a similar event involving Indosat in 2011, more details regarding that incident can be found here: http://www.bgpmon.net/hijack-by-as4761-indosat-a-quick-report/

Impact
The impact of this event was different per network, many of the hijacked routes were seen by several providers in Thailand. This means that it’s likely that communication between these providers in Thailand (as well as Indonesia) and your prefix may have been affected.
One of the heuristics we look at to determine the Continue reading

10 Wi-Fi Terms You’ve Probably Been Using Incorrectly

Sometimes we fall into bad habits. Unfortunately, the improper use of terminology is quite common in the Wi-Fi industry. This can cause a great deal of confusion when people discuss technical topics. Therefore, as a Wi-Fi industry, I think we should start referring to the following terms using more accurate terminology so we are all on the same page.

Here goes:

  1. Over-the-Air Rogue APs - if it's not on your wired network, it's NOT a "Rogue AP" so let's start calling them Neighboring APs so we all know what someone is talking about rather than having to inquire each and every time someone mentions a rogue for clarification. And let's reserve using the term Rogue APs for when unauthorized APs are on the internal wired network.
    Correct Term: Neighboring APs

  2. Co-Channel Interference (CCI) - APs and clients that are operating on the same channel don't cause interference with one another, they contend for the same airtime and backoff if another one is transmitting. This is distinctly different from interference where a transmission cannot be properly decoded because the receiver can't distinguish the valid signal from noise.
    Correct Term: Co-Channel Contention (CCC)

  3. Collision - okay, here is one that most of Continue reading

Fun with Router IP Traffic Export and NSM

The Basics
I finally got around to setting up Security Onion (the best network security monitoring package available) to monitor my home network, only to discover that my Cisco 891 router doesn't support support the right form of SPAN. Here's how I worked around it. The topology looks like this:


The 891 router has an integrated 8-port switch module, so the simple case would have been a traditional SPAN setup; something like this:

! vlan 10 is the user VLAN
monitor session 1 source interface vlan 10
monitor session 1 destination interface FastEthernet0

with the server's monitoring NIC connected to FastEthernet0.

The problem is that the 891 doesn't support using a VLAN as a source interface, and because of the way the embedded WAP works, a physical source interface won't work either. Hence, I turned to an obscure feature that's helped me occasionally in the past: Router IP Traffic Export. This is a feature for IOS software platforms that enables you to enable SPAN-like functions for almost any source interface.

The configuration looks like this:

ip traffic-export profile RITE_MIRROR
  interface FastEthernet0
  bidirectional
  mac-address 6805.ca21.2ddd


interface Vlan10
 ip traffic-export apply RITE_MIRROR

This takes all traffic routed across Continue reading

Fun with Router IP Traffic Export and NSM

The Basics
I finally got around to setting up Security Onion (the best network security monitoring package available) to monitor my home network, only to discover that my Cisco 891 router doesn't support support the right form of SPAN. Here's how I worked around it. The topology looks like this:


The 891 router has an integrated 8-port switch module, so the simple case would have been a traditional SPAN setup; something like this:

! vlan 10 is the user VLAN
monitor session 1 source interface vlan 10
monitor session 1 destination interface FastEthernet0

with the server's monitoring NIC connected to FastEthernet0.

The problem is that the 891 doesn't support using a VLAN as a source interface, and because of the way the embedded WAP works, a physical source interface won't work either. Hence, I turned to an obscure feature that's helped me occasionally in the past: Router IP Traffic Export. This is a feature for IOS software platforms that enables you to enable SPAN-like functions for almost any source interface.

The configuration looks like this:

ip traffic-export profile RITE_MIRROR
  interface FastEthernet0
  bidirectional
  mac-address 6805.ca21.2ddd


interface Vlan10
 ip traffic-export apply RITE_MIRROR

This takes all traffic routed across Continue reading