CopperGate Communications today announced the purchase of the HomePlug AV business from Conexant Systems. CopperGate said it is now the first semiconductor company with home networking technologies supporting all three wire types coax, phone and power.
Having introduced Iperf and Jperf, as well as covering details on TCP throughput tests by adjusting Window Size values, it's time to complete this series with comments on adjusting MSS and Buffer Length values. I'm also going to touch on using the results of Jperf testing to make changes to a PC to improve network performance.
Free and openly available, Iperf is a command line tool useful for measuring network performance. In my last post, I introduced some basic command line instructions to run Iperf between two endpoints and showed how the tool can be used to generate and measure both TCP and UDP performance. This time, I'll discuss Iperf's graphical cousin: Jperf.
The HomePNA Alliance wants us to know that it is still in the fight as an alternative (to Ethernet) networking technology. It today announced HomePNA 3.1 certification of nine new products and the first 320 Mbps chipset reference design from CopperGate.
The newly-certified products include VDSL2 and ADSL2+ residential gateways, Ethernet to coax bridges and a set top box. Companies included 2Wire, D-Link, SMC, SendTek and Scientific Atlanta.
One of the cool things about networks is there are many free tools to work with if you know where to look and how to use them. I've looked at a couple free network tools on this blog so far, including Wireshark and NetMeter. This time, I'm going to take a look at another network tool known as Iperf, a network performance tool used for measuring the bandwidth and the performance of TCP and UDP data flows between two endpoints.
With all the component and configuration options for constructing and managing a small network, it is important to numerically evaluate network performance. Performance measurements provide facts and statistics about the amount of data on your network and identify opportunities for improvement. Without measuring performance, the only indications of functionality are simple up and down states, as well as subjective statements based on user experience.
The Ethernet Alliance today announced that the IEEE P802.3at task force has created IEEE P802.3at/Draft 3.0 and has submitted it to the IEEE 802.3 working group ballot for technical review of the draft standard. This task force expects to complete standard ratification by 2009.
I've covered some of the basic elements of Multicasting, such as IGMP and the Layer 2 switching components in my previous posts (Part 2). This article will go into the technology behind Multicasts at Layer 3 and some of the issues limiting wider use of Multicast technology.
As you recall in my first post, I observed that Yahoo's transmissions of live NHL games would seem to be good candidates for Multicast, yet were being sent as unicast. Then I covered the simple issue of enabling Multicast within a local area network. Coming full circle, here we are diving into Multicast technology to understand why it isn't more widespread.
In my last post, I discussed multicasts and some of the basic concepts. This time, I'm going to discuss technologies used by switches and routers to enable and configure multicasts. Specifically, I'm going to dive into addressing and IGMP. Understanding the details behind multicasts helps understand configuring multicasts as well as the issues limiting the use of multicasts on the web.
It's occurred to me that readers monitoring our RSS feeds can't tell when we add new products to the charts. So, starting now, I'll be announcing additions via short news items.
Peplink's Balance 30 has been added to the Router Charts. It's a three-WAN router with about 20 Mbps routing throughput and built-in four port 10/100 switch.
With the growth of IPTV and other IP media streaming technologies, applications for multicast technology are increasing. Live Video broadcasts and VoIP applications are viable uses for real time transmissions over an IP network from a single source to multiple recipients.
Most data transmissions are unicasts, which are a one-to-one data stream sent from one device to another device. Email, web surfing, and file downloads are all examples of unicasts, even for the busiest sites or most downloaded files. Although a single web page may be visited thousands of times each day, each time it is viewed it is individually transmitted to the requestor's PC as a unicast.
D-Link today announced the expansion of its "Green Ethernet" switch line with the addition of 16 and 24 port unmanaged gigabit models.
New hardware revisions of the DGS-1016D 16-port and DGS-1024 24-port unmanaged gigabit switches now support the same power-saving features introduced on the DGS-2205 and DGS-2208 5 and 8 port switches last October.
In my last two posts on this subject, I've covered some of the basics and tools used to perform packet captures, highlighting the well known software from Wireshark. In this installment, I'm going to show how I used Wireshark packet captures to solve a real network problem.
Using packet papture software like Wireshark is a useful troubleshooting technique that can be used to examine packets and gather details to help find the root of a problem. In my previous post, I talked a little bit about how to use Wireshark and walked through some steps to run a simple packet capture from a PC. This time, I'm going to go a bit deeper into the how to for doing packet captures.
One of the features I've seen in newer small network routers is the inclusion of a packet sniffer/capture/trace tool within the diagnostic menus of the device. Routers I've recently tested with this functionality include the SonicWall TZ190W, D-Link DFLCPG310, and Netgear's newly released FVX538 and FVS336G.
In each case, these devices have the ability to capture packets on a specific WAN port and/or on the LAN interface. Some of these routers have more sophisticated filtering capabilities than the other, but they all seem to have the same basic functionality of capturing packets.
Page 10 of 17