Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:user-guide:advanced:benchmark.nat [2018/02/17 18:23] – ↷ Page moved from doc:howto:benchmark.nat to docs:user-guide:advanced:benchmark.nat bobafetthotmail | docs:guide-user:perf_and_log:benchmark.nat [2020/06/19 23:11] – [Rationale] Link for JPerf download does not address to the correct site. sopalajoarrierez | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Benchmark Network Address Translation ====== | + | ====== |
| - | After you install | + | After you install |
| + | |||
| + | The diagram below shows the general layout of the benchmark test described below: | ||
| + | |||
| + | {{: | ||
| ===== Rationale ===== | ===== Rationale ===== | ||
| Line 9: | Line 13: | ||
| In order to make full use of the bandwidth you are paying for, the router has to be able to process network packets at rates that exceed the bandwidth of the subscription you are paying for. | In order to make full use of the bandwidth you are paying for, the router has to be able to process network packets at rates that exceed the bandwidth of the subscription you are paying for. | ||
| - | You should not take benchmarks found online as a reference because it is now using OpenWRT | + | You should not take benchmarks found online as a reference because it is now using OpenWrt |
| For a graphical approach to testing you can follow the methods to utilise jperf to benchmark Network Address Translation performance as described below: | For a graphical approach to testing you can follow the methods to utilise jperf to benchmark Network Address Translation performance as described below: | ||
| - | [[http:// | + | [[http:// |
| ===== Prerequisites ===== | ===== Prerequisites ===== | ||
| Line 29: | Line 33: | ||
| - In order to simplify the steps involved we will use 10.1.1.0/24 as the WAN Network and the default 192.168.1.0/ | - In order to simplify the steps involved we will use 10.1.1.0/24 as the WAN Network and the default 192.168.1.0/ | ||
| - | ==== Client | + | ==== WAN Network Settings ==== |
| On the Client Computer using Web Browser, | On the Client Computer using Web Browser, | ||
| - | | Protocol | Static | | + | ^ Protocol |
| - | |IP Address | 10.1.1.1 | | + | ^ IP Address |
| - | |Subnet Mask | 255.255.255.0 | | + | ^ Subnet Mask |
| - | |Default Gateway | | + | ^ Default Gateway |
| {{media: | {{media: | ||
| Line 46: | Line 50: | ||
| On the Server use its own network configuration tool to set the network settings to | On the Server use its own network configuration tool to set the network settings to | ||
| - | | Protocol | Static | | + | ^ Protocol |
| - | | IP Address | 10.1.1.2 | | + | ^ IP Address |
| - | |Subnet Mask | 255.255.255.0 | | + | ^ Subnet Mask |
| - | |Default Gateway | 10.1.1.1 | | + | ^ Default Gateway |
| {{media: | {{media: | ||
| Line 60: | Line 64: | ||
| < | < | ||
| You should get a series of ping echo response if not recheck your network settings or turn off your firewall on both the Client and the Server. | You should get a series of ping echo response if not recheck your network settings or turn off your firewall on both the Client and the Server. | ||
| - | There is no need to change the LAN Settings as by default | + | There is no need to change the LAN Settings as by default |
| ===== Setting Up Jperf ===== | ===== Setting Up Jperf ===== | ||
| Line 73: | Line 77: | ||
| You should be able to see the jperf main screen. | You should be able to see the jperf main screen. | ||
| + | |||
| You need to set the Jperf on the Server to listen first before we can run the Client. | You need to set the Jperf on the Server to listen first before we can run the Client. | ||
| + | |||
| For the Server, simply select Server and change the metric to Mbits for easy reference and comparison as shown below. | For the Server, simply select Server and change the metric to Mbits for easy reference and comparison as shown below. | ||
| + | |||
| Then click run Iperf to set the Server to listening mode. | Then click run Iperf to set the Server to listening mode. | ||
| + | |||
| + | For TCP select TCP as shown below, for UDP select UDP | ||
| {{media: | {{media: | ||
| Line 84: | Line 93: | ||
| {{media: | {{media: | ||
| + | |||
| + | For UDP, you need to set the bandwidth to line rate eg. 900Mbits and observe the actual throughput on the receiver Server as shown below | ||
| + | |||
| + | {{: | ||
| When you are ready click run Iperf to start the test. | When you are ready click run Iperf to start the test. | ||
| - | After the test ends you should analyse the result on the Server for accuracy instead of the Client since only the network packets that get through matters not the packets generated. | + | After the test ends you should |
| {{media: | {{media: | ||
| Line 92: | Line 105: | ||
| For the above picture it indicates that the Router will be generally sufficiently powerful enough for a < 250Mbps Internet Subscription Plan. | For the above picture it indicates that the Router will be generally sufficiently powerful enough for a < 250Mbps Internet Subscription Plan. | ||
| - | |Note that OpenWRT | + | <WRAP center round important 80%> |
| + | Note that OpenWrt | ||
| + | </ | ||
| - | {{tag> | ||