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.
Whenever we get to the end of a year we have this tendency to reflect on what has happened in the past year and how we can improve in the coming year. It’s natural to use the change of calendar year as a point in time to think back, even though practically speaking it is usually the most chaotic time of the year between shopping, family and year and quarter end at work.
Almost every industry will go through waves of change and transformation. Real change and transformation is driven by powerful market forces of demand coupled with technology leaps that allow an escape from incremental changes that drive day to day improvements. Networking has gone through several of these transformations. From dedicated main frame based connectivity, to coax based shared ethernet to switches ethernet in local area networks. From 1200 baud dialup serial connections through X.25 (yes, that’s the European in me) to leased T1 to ATM, to Frame Relay, to Packet over SONET to MPLS and various flavors of wide area ethernet services. Some of these were incremental, some of them truly transformational.
When you look back, each of these changes in network technology was very much Continue reading
HP is making more resources available to help with learning Comware. They’ve added free labs and courses to the already published simulators and virtual routers. This is a good resource for those looking to get started with Comware.
HP’s Network Simulator (HNS) is a modelling tool for simulating HP Comware networks. It includes Layer-2 functionality, and lets you test things like LACP & IRF. I found it too slow when I first tried it, but this has improved significantly with current versions. It is free to download.
HP has now started publishing simple labs you can work through with HNS:
These are short labs that cover HNS setup, and device configuration. Quick and easy, they show how to use the tool, and give you a taste of Comware configuration. They’ve also released a free 1-hour online course that goes through how to use HNS.
I’ve covered the HP VSR1000 previously. This Continue reading
An article came out this week that really made me sigh. The title was “Six Aging Protocols That Could Cripple The Internet“. I dove right in, expecting to see how things like Finger were old and needed to be disabled and removed. Imagine my surprise when I saw things like BGP4 and SMTP on the list. I really tried not to smack my own forehead as I flipped through the slideshow of how the foundation of the Internet is old and is at risk of meltdown.
If It Ain’t Broke
Engineers love the old adage “If it ain’t broke, don’t fix it!”. We spend our careers planning and implementing. We also spend a lot of time not touching things afterwards in order to prevent it from collapsing in a big heap. Once something is put in place, it tends to stay that way until something necessitates a change.
BGP is a perfect example. The basics of BGP remain largely the same from when it was first implemented years ago. BGP4 has been in use since 1994 even though RFC 4271 didn’t officially formalize it until 2006. It remains a critical part of how the Continue reading
Happy Holidays from Packet Design
It is that time of year again… and what a difference a year makes! We grew leaps and bounds in 2014, increasing our headcount as an organization and working hard to provide our customers with the best in route analytics technology.
To give back for all our good fortune in 2014, we adopted two families in the Austin area and provided additional "cheer" to make their holidays bright. Everyone at Packet Design came together to donate gifts and their time, and we could not have been happier at the participation in such a worthy endeavor. Packet Design would like to extend a special thanks to Angela Reyna, a key member of our marketing team, for putting it all together. It is moments like these that give us pause to remember that people, working as a team, make our organization a success. So from our Packet Design family to yours, we wish you Happy Holidays and a spirited New Year!
Below are photos from our wrapping party, where the Packet Design elves showed off their gift-wrapping and logistics skills:
HP Helion is the cloud platform HP is bringing to Enterprise for private cloud and used by HP to build their Helion public cloud. In this show, recorded at HP Discover as part of our show coverege, we talk about Virtual Cloud Network (VCN) for OpenStack that uses OpenFlow and OVSDB as a basis for implementing features in the physical network in OpenStack and Helion.
The post PQ Show 38 – HP Networking, Helion, OpenStack and Cloud Networking appeared first on Packet Pushers Podcast and was written by Greg Ferro.
I wanted to take a moment to wish all PacketU readers a Merry Christmas and a Happy New Year. With that, I leave you with a short video clip of my son playing Silent Night at a church program last week. Longtime friends know that we had a pretty serious health scare with him 5 years ago and we count ourselves very blessed to have him in our lives.
The post Merry Christmas to the PacketU Community appeared first on PacketU.
North Korea went off the Internet Monday, 22 December 2014, at 16:15 UTC (01:15 UTC Tuesday in Pyongyang) after more than 24 hours of sustained weekend instability. Dyn continually measures the connectivity and performance of more than 510,000 individual networks worldwide, identifying impairments to Internet commerce. It’s a rare event these days when an entire country leaves the Internet (as Egypt did, or Syria). Even so, when North Korea’s four networks went dark, we were not entirely surprised, based on the fragility of their national connectivity to the global Internet.
Who caused this, and how? A long pattern of up-and-down connectivity, followed by a total outage, seems consistent with a fragile network under external attack. But it’s also consistent with more common causes, such as power problems. Point causes such as breaks in fiberoptic cables, or deliberate upstream provider disconnections, seem less likely because they don’t generate prolonged instability before a total failure. We can only guess. The data themselves don’t speak to motivations, or distinguish human factors from physical infrastructure problems.
As the sun rises in Pyongyang, the national Internet disconnection continues. An outage of this duration is not without precedent for North Korea. As we’ve written before, Continue reading