Changes between Version 1 and Version 2 of Gigabit_Networks_Linux
- Timestamp:
- 05/02/11 10:57:08 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Gigabit_Networks_Linux
v1 v2 6 6 7 7 For this setup several machines were used, all connected to gigabit switches: 8 * two servers running CentOS 5.5 64bit, with an Intel E5440 CPU @ 2.83GHz; the L2 cache size is 6 MB 9 * a server running CentOS 5.5 64bit, with an Intel X5660 @ 2.80GHz; the L2 cache size is 12 MB. This CPU has support for the AES-NI instructions 10 * a laptop running Fedora 14 64bit, with an Intel i5-560M @ 2.66GHz; the L2 cache size is 3 MB. This CPU also has support for the AES-NI instructions 8 * two servers running CentOS 5.5 64bit, with an Intel E5440 CPU running @ 2.83GHz; the L2 cache size is 6 MB. 9 * a server running CentOS 5.5 64bit, with an Intel X5660 CPU running @ 2.80GHz; the L2 cache size is 12 MB. This CPU has support for the AES-NI instructions. 10 * a laptop running Fedora 14 64bit, with an Intel i5-560M CPU running @ 2.66GHz; the L2 cache size is 3 MB. This CPU also has support for the AES-NI instructions. 11 11 12 Before starting, the "raw" network speed was measured using 'iperf'. As expected, '''iperf''' reported consistent numbers arou dn 940 Mbps, which is (almost) optimal for a gigabit LAN. The MTU size on all switches in the gigabit LAN was set to 1500.12 Before starting, the "raw" network speed was measured using 'iperf'. As expected, '''iperf''' reported consistent numbers around '''940 Mbps''', which is (almost) optimal for a gigabit LAN. The MTU size on all switches in the gigabit LAN was set to 1500. 13 13 14 = Understanding the flow of packets 14 15 16 It is important to understand how packets flow from the 'iperf' client via the OpenVPN tunnel to the 'iperf' server. The following diagram helps to clarify the flow: 15 17 16 18 [[OpenVPN_packetflow.png]]