Although I wasn't actively blogging this year, I've still been tracking views on the site and keeping an eye on number of visitors. I am looking forward to blogging again in 2015 so I wanted to collect the 2014 viewership statistics so I had something to compare to at the end of 2015.
Despite the lack of new content, I'm pretty happy that people are reading the existing articles and continue to post comments and email me questions. Please keep them coming!
HP Networking has three solutions for overlay or virtual networking in the Data Centre. Each solution meets different customer needs Show Notes HP Networking has three products for network virtualization and each product addresses different customers needs. NSX Federation – physical networking integrating with NSX Distributed Cloud Networking (DCN) Virtual Cloud Networking (VCN) NSX Federations […]
The post PQ Show 39 – HP Networking – 3 Virtual Network Strategies Compared appeared first on Packet Pushers Podcast and was written by Greg Ferro.
Picking up where we left off on the first series, I want to discuss the other trunking option that we have in regards to PVLAN trunks. We might need a quick review on our PVLAN structure before we begin, however:
vlan 100 private-vlan primary private-vlan association 200-201 vlan 200 private-vlan community vlan 201 private-vlan isolated
This second trunk type is actually called the secondary, or isolated trunk. Much like the promiscuous trunk, this one has a pretty specific purpose, and that is to flip the VLAN tag when a frame is traversing a trunk. This time however, rather than removing the secondary VLAN tag, and replacing it with the primary tag, we are going to be doing the opposite! Remember how we were doing it with the promiscuous trunk? What happened here is the node with MAC A ingresses and is placed in VLAN 200. However, when it needs to reach the L3 GW (the router), we have to remove the secondary VLAN tag and replace it with the primary VLAN ID of 100 (so that it will hit the proper sub-interface on the router).
The routers return traffic will naturally be in VLAN 100 based on the sub-interface configuration. But Continue reading
Many old-style marketing people believe that capturing your contact information is the first step in making a sale. But any capture of your personal information is also leaking critical security information about your organisation, technology and personnel that are perfect for reconnaisance.
The post Vendor Marketing as a Security Risk – Badge Scans and Sign-up Attack Vectors appeared first on EtherealMind.
Last time, we talked a little about making certain your presentation has a point — or a porpoise, as the case might be. This time I want to talk about a few other common mistakes I see network engineers make when building presentations, and actually presenting them.
First, you put too much text on your slides. I know you’re afraid you’re not going to remember everything you want to say, but that’s no excuse to have a 500 word essay on every slide. The bullet points on a slide are supposed to be just that — bullet points. They’re supposed to remind you of what you mean to say at this point in the presentation, not to be the actual words you’re planning on saying.
Okay, I understand we’re running head in to another problem here — what about folks who print my presentation out and take it home to read it later? That’s what hidden slides are for. Put all the text you really want to put into a slide on a hidden slide just after the slide itself. Then pull out just enough words for you to remember what’s on the hidden slide when you’re doing the presentation. Continue reading
Let’s return to our simple four AS network to look at a number of issues with BGPSEC — the bits you won’t often hear discussed in just about any forum. Assume, for a moment, that AS65000 advertises some route, say 192.0.2.0/24, to AS65001, and not to AS65002. For whatever reason, a few days pater, the […]
The post BGPSEC: Replays, Timers, and Performance appeared first on Packet Pushers Podcast and was written by Russ White.
A long time ago, Packet Pushers ran an OSPF Design Part 1 show. That show went after the default design guides that network engineers have been reading for years, making the big point that you can scale a single OSPF area quite large indeed. But…that’s not the entire story about OSPF areas. Areas still have their use cases, […]
The post Show 218 – OSPF Design Part 2 appeared first on Packet Pushers Podcast and was written by Ethan Banks.
Recently I have read a question on GNS3 forum asking whether Qemu supports more than 8 network adapters. According to Google search, maximum number of adapters for Qemu virtual machines can be configured with a parameter #define MAX_NICS 8 in a file ./include/net/net.h under Qemu source tree. After you set desirable value you must compile and install Qemu from source.
However I have noticed that changing the integer value in the line #define MAX_NICS has no effect on the maximum number of NIC allowed for Qemu VMs. I notice that I can start Core Linux Qemu machine with 18 network adapters even Qemu 2.2.0 was compiled with parameter #define MAX_NICS set to 1.
Now we know that Qemu itself does not limit the maximum network adapters to 8. We will go ahead and investigate GNS3. Navigate to Edit -> Preferences -> QEMU VMs and click on existing Qemu VM. Click on Edit button for this VM and navigate to Network tab. Increase the number of Adapters to 9.
The GNS3 1.2.1 allows to add maximum 8 NICs for a particular Qemu virtual machine. To avoid this limitation we have edit GNS3 source files and recompile GNS3 GUI and server. Here are the the steps for Linux.
1. Download and extract GNS3 1.2.1 Linux Continue reading
In an effort to educate myself on the inner workings of WebEx, I recently looked at a session with Wireshark. Knowing that WebEx audio has the ability to use UDP or TCP, I wanted to isolate the protocol being employed in my configuration. I watched for a new stream of traffic as I enabled the audio portion of a meeting. I found that the audio was using UDP port 9000.
I next applied a filter to see only this traffic. What immediately jumped out at me was what appeared to be malformed and fragmented packets. I also noticed a lot of strange IP addresses like 1.0.0.0, 1.0.0.1, 0.0.0.30, 0.0.0.31 and so on.
Knowing that the audio was working perfectly, I could have easily concluded that my eyes were deceiving me. When I looked closer, I quickly realized that Wireshark was recognizing and decoding this as if the packets were Lawful Intercept.
This is a common scenario and the solution is straightforward. In Wireshark, right-click any of the packets and choose Decode As…
At this point, a new window will appear. Make sure the Transport tab is selected then choose Do Continue reading
Another week of looking critically and cynically at the technology market, especially networking and storage.
The post Network Break 25 appeared first on Packet Pushers Podcast and was written by Greg Ferro.
As a special year-end promotion, our 12 Days of Christmas AND our Black Friday promotions are back!
Be sure to visit this URL for savings of upwards of 80%!:https://www.ipexpert.com/products/twelve-days for details.
I would like to start by saying Merry Christmas and Happy Holidays season to all. In between spending time with my family, decorating the Christmas three and opening presents, I did find some time to play around with my hobby and testing something in the lab.
