Changing Your MAC Address Using Macchanger

Macchanger is a free utility used to change the MAC address of the network adapter. Macchanger can randomly assign a MAC address or assign a specific MAC address of your choosing.

Usage

There are several instances changing the MAC address is necessary, but I use the utility while pentesting a wireless network with MAC filtering enabled and have to assign an approved MAC address to the wireless adapter.

Install

The Macchanger utility is included with Kali Linux, but to install the application, update it, or verify your using the most up to date version run the following command. In the screen shot that follows the install command confirms that the newest version is already installed.

#apt-get install macchanger

macchangeinstall

Help

Help with Macchanger can be accessed by running the following two commands.

#macchanger --help

#man macchanger

Assign a Random MAC Address

I’m using an Alfa USB wireless adapter and I will run the following commands to verify the adapters interface and the permanent MAC address.

#ifconfig

#ifconfig wlan1

Macchanger can also be used to verify the manufacture burned in MAC address by running the following command.

#macchanger--show wlan1

Change the MAC address using one of the following commands.

#macchanger -r  Continue reading

3Com / H3C / HP Comware based Switches – Edged-port + BPDU Protection

Today we’ll comment on the two features that work as a complement to the Spanning-Tree. The edged-port command gathers many benefits to the STP, for example, the timeout prevention concerning the DHCP process. As for the bpdu-protection, it prevents loop in the “edged” configured ports within the network via HUBs, “Switches HUB”, etc.

Edged-port

The edged-port feature allows the interface to skip the Listening and Learning states of the Spanning-Tree Protocol, setting the ports into the Forwarding state immediately.  The STP’s configuration edged-port enable, forces the interface to ignore the convergence states of the STP, including the notification of topology change messages (TCN messages).

The command must be applied to the access ports connected to servers, workstations, printers, etc.

edge-port
Configuration

[Switch]interface gigabitethernet 1/0/1
[Switch-GigabitEthernet1/0/1]stp edged-port enable
[Switch-GigabitEthernet1/0/1]quit
[Switch]interface gigabitethernet 1/0/2
[Switch-GigabitEthernet1/0/2]stp edged-port enable
[Switch-GigabitEthernet1/0/2]quit

PS: When a port is configured as a edged-port receives a BPDU, the interface will return to participate on the STP like any other interface.
PS:An Edged-port send BPDUs normally. The edged-port feature is also known as Portfast.

 BPDU Protection

The utilization of the edged-port feature is restricted to ports connected to the final equipment such as servers and workstations. Continue reading

Network Management Challenges of 2014

Network Management Challenges of 2014


by Brian Boyko, Technology Commentator - March 4, 2014

No matter how much virtualization or abstraction or automation we place into the network, it still has to run on a physical infrastructure somewhere. And you still need to understand how the underlying network is performing, which route the traffic is taking, how much bandwidth each application needs and during what time periods, etc. 

So no matter how much the venerable router is under assault and in danger of becoming a commodity, we know that you will never be able to abstract all physical devices – or humans for that matter – from the network. But we will all need to adapt. 

This is the perspective we’re taking in this blog. Welcome to the first post of the Packet Design blog, where we will delve into all things network management, route analytics, SDN, IT and beyond. We’ll be covering issues for everyone affected by network management concerns. 

That’s a broader audience than you’d think at first glance. It of course includes the planners, architects and engineers who design, set up and maintain the network, the NOC staff who oversee it, the managers responsible Continue reading

DEW Testimony

Thanks to God !! Finally all the effort to be Design Expert is paid off!
I really appreciate to Himawan for his knowledge and passion about CCDE mindset, insight and learning strategy to help my CCDE journey.
They are really enlightening and accelerating.
“Learn from the best to be the best” really works for me.
Thanks Him, great to have you as my mentor!!
All the best, brother :
)
(Hinwoto – CCDE #2014::4 / CCIE #15026 RS & SP)

Thanks, Hinwoto, for the kind words.
And congratulations once again for your CCDE.

I can't make anyone to pass CCDE. And I don't think anyone can give promise that he or she can make you pass CCDE exam. The only person who can make you become CCDE is yourself. I, and all other CCDE study groups, training vendors, or individuals who spend time to help others to pass CCDE, can only help with knowledge and tips to prepare for the exam. You are the one who has to push yourself to continue learning. You have to gain experience and real design skills. You are the one who will make decision to get certified or not.

I can only show you the Continue reading

Has SDN Changed Networking?

Software Defined Everything, NFV, OpenFlow, SDDC and Orchestrators are buzz words of DC networking. An interesting point would be to check whether these proposed solutions change our understanding of DC Networks? A good analogy to start with is chassis based switches (e.g Cisco’s Cat6500, Juniper’s EX8200). Regardless of how convoluted it may seem, any networking […]

Author information

Karim Jamali

Karim Jamali

Karim is a network engineer, blogger, and CCIE #25064. His main focus areas are Data Center, Virtualization and Security..Karim has been working in the industry for more than 6 years covering both pre-sales & post-sales functions.

The post Has SDN Changed Networking? appeared first on Packet Pushers Podcast and was written by Karim Jamali.

Capture your fancy, part one, PFC3

It's often incredibly useful to be able to capture transit traffic, it's quick way to prove that you're actually receiving some frames and with any luck have good idea how and where you are sending them. It's unfortunately common, especially in 7600/6500 PFC3 to have bug where packets are not going where software FIB suggests they are. Luckily there is quite good tooling to inspect what really is happening. So we're taking a peek at 'ELAM'.

We have traffic coming in unlabeled to 7600 and going out labeled. Let's see how to capture it

psl2-pe2.hel.fi#show platform capture elam asic superman slot 5 psl2-pe2.hel.fi#show platform capture elam trigger dbus ipv4 help SEQ_NUM [5] QOS [3] QOS_TYPE [1] TYPE [4] STATUS_BPDU [1] IPO [1] NO_ESTBLS [1] RBH [3] CR [1] TRUSTED [1] NOTIFY_IL [1] NOTIFY_NL [1] DISABLE_NL [1] DISABLE_IL [1] DONT_FWD [1] INDEX_DIRECT [1] DONT_LEARN [1] COND_LEARN [1] BUNDLE_BYPASS [1] QOS_TIC [1] INBAND [1] IGNORE_QOSO [1] IGNORE_QOSI [1] IGNORE_ACLO [1] IGNORE_ACLI [1] PORT_QOS [1] CACHE_CNTRL [2] VLAN [12] SRC_FLOOD [1] SRC_INDEX [19] LEN [16] FORMAT [2] MPLS_EXP [3] REC [1] NO_STATS [1] VPN_INDEX [10] PACKET_TYPE [3] L3_PROTOCOL [4] L3_PT [8] MPLS_TTL [8] SRC_XTAG [4] DEST_XTAG [4] FF [1] Continue reading

Network Configuration: The Case for Normalization

I’ve had network configuration tools and protocols on my mind for the last few weeks. Everyone’s got some hot new API or configuration protocol - and on the outside looking in, it’s easy to assume that they’re all just different flavors of the same general concept - network configuration. So are they basically competing standards (VHS vs Betamax, anyone?)? Or is there a method to this madness? Just to name a few, OVSDB and Netconf are actually established JSON-RPC and XML-RPC (respectively) based standardized formats for accomplishing network configuration on the wire, rather than chase down each vendor’s individual XML/JSON API.

Network Configuration: The Case for Normalization

I’ve had network configuration tools and protocols on my mind for the last few weeks. Everyone’s got some hot new API or configuration protocol - and on the outside looking in, it’s easy to assume that they’re all just different flavors of the same general concept - network configuration. So are they basically competing standards (VHS vs Betamax, anyone?)? Or is there a method to this madness? Just to name a few, OVSDB and Netconf are actually established JSON-RPC and XML-RPC (respectively) based standardized formats for accomplishing network configuration on the wire, rather than chase down each vendor’s individual XML/JSON API.

Server Brawn + Switch Brains = Infrastructure Fabric

Last week I attended Networking Field Day 7, and was introduced to Pluribus Networks. Pluribus is taking an interesting approach to building the data center fabric, by combining high-performance data center top-of-rack (ToR) switching with powerful server internals in a platform they’ve dubbed the Freedom Server-Switch.

Source: pluribusnetworks.com

Source: pluribusnetworks.com

The Freedom platform can be loaded to bare with RAM and storage along with some pretty powerful CPUs (this data sheet provides all the details), which enables embedding various network (and not-so-network) services right in the network at every edge. The platform runs the NetVisor operating system, based on BSD. This software can be had in various feature levels:
Source: pluribusnetworks.com

Source: pluribusnetworks.com

Various services that can be enabled beyond typical L2/L3 network services include DHCP, DNS, PXE, load balancing, CDN functions, NAT, NAS (yes, really), and traffic analytics. Since these switches are designed for deployment as leaf nodes in leaf-spine architecture datacenters, this embeds these services right at the network ingress point for each connected device.
You may be thinking about the potential administrative overhead included with performing advanced network services on each ToR switch, but that burden is eased with fabric-wide management features that allow an administrator to Continue reading

Show 181 – Intro to I2RS with Joel Halpern & Russ White

Traditionally, routing protocols running on a router will perform calculations to determine the best forwarding path. The RIB with be then populated with next-hop information. Ultimately, that information will be populated into the FIB (forwarding information base), the FIB taking the guesswork of how to get to the next hop and easing CPU utilization on […]

Author information

Ethan Banks

Ethan Banks, CCIE #20655, has been managing networks for higher ed, government, financials and high tech since 1995. Ethan co-hosts the Packet Pushers Podcast, which has seen over 2M downloads and reaches over 10K listeners. With whatever time is left, Ethan writes for fun & profit, studies for certifications, and enjoys science fiction. @ecbanks

The post Show 181 – Intro to I2RS with Joel Halpern & Russ White appeared first on Packet Pushers Podcast and was written by Ethan Banks.

Orhan Ergun CCDE Story

Once I decided for the CCDE exam I was thinking it is a hard challenge but surprisingly I will say it is not as much as you think.This is good news and you started to smile ? Hope once you finished the article you continue to it     Yes it is not since I […]

Author information

Orhan Ergun

Orhan Ergun, CCIE, CCDE, is a network architect mostly focused on service providers, data centers, virtualization and security.

He has more than 10 years in IT, and has worked on many network design and deployment projects.

In addition, Orhan is a:

Blogger at Network Computing.
Blogger and podcaster at Packet Pushers.
Manager of Google CCDE Group.
On Twitter @OrhanErgunCCDE

The post Orhan Ergun CCDE Story appeared first on Packet Pushers Podcast and was written by Orhan Ergun.

Embedded Packet Capture, let’s go fishing for some packets!

EPC (Embedded Packet Capture) is another useful troubleshooting tool to occasionally capture traffic to be analyzed locally or exported to remote device. Occasionally, in contrast with RITE (Router IP Traffic Export) or SPAN on switches which are meant to have permanent flow of copied traffic directed to a traffic analyzer or IDS (Intrusion Detection System). […]

Avoiding Bogus Alerts Using AWS-Based Proxies & Outsourced BGP for Distributed Monitoring

Jeff Behl, Chief Network Architect with LogicMonitor, is our guest author for this post. Jeff has been in the IT industry for over 20 years.  He has an extensive background on architecting enterprise networks and data centers and brings real world knowledge around network operations from start-ups to enterprise companies. These companies range from UC […]

Author information

Sponsored Blog Posts

The Packet Pushers work with our vendors to present a limited number of sponsored blog posts to our community. This is one. If you're a vendor and think you have some blog content you'd like to sponsor, contact us via [email protected].

The post Avoiding Bogus Alerts Using AWS-Based Proxies & Outsourced BGP for Distributed Monitoring appeared first on Packet Pushers Podcast and was written by Sponsored Blog Posts.

DEW: SP Design in Jakarta – March 2014!


The final installment of DEW trilogy will happen in Jakarta, 15-16 March 2014!

After the first Design Expert Weekend in Riyadh focusing on IPv4/IPv6 Routing Design, the second DEW in Dubai for MPLS/Tunneling Design, the third and last DEW will be held in Jakarta, Indonesia, for Service Provider Design.


Please note: this is NOT a free event. I'm going to visit several universities in Indonesia to share my knowledge and experience during the same week. The profits we make from this DEW will be used to fund my trip. If you have to fly from outside Indonesia to attend this, we will provide all the food and accommodation during the weekend.

What:
Design Expert Weekend in Jakarta on 15-16 March will focus on Service Provider Design. Agenda will cover:

- Physical Network Design
- Layer 2 Design
- IGP/MPLS/BGP/Multicast as Transport
- MPLS Based Services L3VPN, L2VPN
- Internet Services
- IPTV Services
- High Availability Design
- SP QoS Design
- Security and Management
- CCDE exam tips and tricks
- CCDE sample questions and scenario to practice ability to analyze design requirements, develop network designs, implement network design, validate and optimize network design

The other two DEW are Continue reading

Are certifications tests still worth your resources in the day of Hybrid IT?

Let me start by laying out this disclaimer:  This is in no way intended to devalue or criticize any vendor or vendor neutral certified folks or programs. Since the mid-1990s I’ve done many certification programs. In fact, I’ve actually lost track and  I can’t even remember them all, so this is not a commentary by someone […]

Author information

Nick Buraglio

Nick has been involved in the networking industry for the last 16 years. In the past, Nick has been employed by the University of Illinois as a Lead Network Engineer working on research and HPC networks, campus networks and wide area connectivity. In this role, Nick also functioned as the Lead Network Engineer for the National Association of Telecommunications Officers and Advisors (NATOA) broadband project of the year, UC2B, and helped to deploy production IPv6 and testbed OpenFlow networks at large scale. Additionally, Nick has held Network Engineering [and by necessity network security] positions at early regional broadband internet providers as well as at the National Center for Supercomputing Applications. Nick has participated in the SCinet working group on several occasions and has been involved in Research, Education and high performance networking and security for the last 11 Continue reading

My Dotfiles. Now on Github

Dotfiles are all those . files that sit in your ~ and customize your system. Here are mine.

Until a few weeks ago I had no idea that people hosted their dotfiles on GitHub, and now I am one of them... There are two reasons for this:

  1. For sharing awesome customizations with the community
  2. As a backup plan. I can now clone this repo and customize a new system.

To point 2, I've gone one step further than just including my dotfiles. I've also included all of my system customizations and installers for the packages I use most. Why a new repository and not a fork you might ask? The honest answer is that there wasn't one repo that fit my tastes well enough so I ended up taking what I considered to be the "best" elements from a number of other repos. This is still a work-in-progress and I am comitting changes every time I find somehting new and exciting, or tire of a specific setting.

What I like about my dotfiles:

  • Uses the Base16 Ocean theme
  • Nicely Organised
    • Top-level folder for each function
    • Files with extension .symlink are symlinked to the home folder
  • Multi-Platform MakeFile-based installer

The next fashion

By now just about everyone has realized that OpenFlow is just vaporware. Technically, there was never any content behind the hype. The arguments used to promote OpenFlows revolutionary properties where simply the ignorance of all previous technologies that used the exact same design ideas from SS7 to PBB-TE.

Rumor has it that even the most religious OpenFlow supporters from Mountain View to Tokyo have realized that OpenFlow is pretty much dead. If you look back at it, it was a pretty silly set of assumptions to start with: that hardware design and not software the the limiting factor in network devices; and that you can define a low-level forwarding language based on the concept of a TCAM match that is going to be efficient across general purpose CPUs; ASICs and NPUs. Both assumptions can easily be proven to be false.

But OpenFlow’s promise was “too good to be true”. So a lot of people preferred to ignore any hard questions in search of the illusory promises of a revolution in networking. By now though, everyone gets it.

As an industry, what is the expected reaction to the OpenFlow hangover ? One would expect a more down-to-earth approach. Instead we get “Segment Continue reading