{"id":9330,"date":"2022-03-25T10:33:40","date_gmt":"2022-03-25T14:33:40","guid":{"rendered":"https:\/\/www.redline13.com\/blog\/?p=9330"},"modified":"2022-03-25T10:33:41","modified_gmt":"2022-03-25T14:33:41","slug":"enabling-public-ips-on-your-redline13-load-generators","status":"publish","type":"post","link":"https:\/\/www.redline13.com\/blog\/2022\/03\/enabling-public-ips-on-your-redline13-load-generators\/","title":{"rendered":"Enabling Public IPs on your RedLine13 Load Generators"},"content":{"rendered":"

\"Enabling<\/strong><\/p>\n

One thing you must be aware of is ensuring that your load generators are visible to RedLine13.\u00a0 This is accomplished through assigning public IP addresses.\u00a0 In this post we will show you how to configure that and successfully run your first load test<\/a>.<\/p>\n

<\/a>What is a Public versus a Private IP?<\/h3>\n

A public IP address refers to its ability to be accessed from external networks \u2013 e.g.<\/em>, the internet.\u00a0 On the other hand, a private IP address is restricted to only other devices on the same local network.\u00a0 On a local area network, devices will have a private IP address to communicate with each other.\u00a0 They may or may not additionally have a public IP address to receive communications from outside networks.<\/p>\n

<\/a>Why is a Public IP necessary?<\/h3>\n

RedLine13 utilizes a unique approach to cloud-based load testing.\u00a0 By interfacing with your AWS account<\/a>, we can keep costs extremely low<\/a>.\u00a0 This necessitates communicating with instances we provision on your behalf.\u00a0 Since we take care of startup, configuration, results collection, and eventual termination of those instances automatically, our service needs to reach these instances over the internet.<\/p>\n

<\/a>How do you make sure load generators have Public IPs?<\/h3>\n

Load generators in most cases are configured by default to have public IP addresses assigned.\u00a0 However, every network and test configuration is unique.\u00a0 There are two places to check your configuration to ensure this is enabled. The first and most straightforward check is to ensure that for your test on RedLine13 you have enabled public IP assignment for load generators:<\/p>\n

\"Setting
This setting is normally set by default, and should be checked to make sure load generators are getting assigned public IP addresses.<\/figcaption><\/figure>\n

The above setting is enabled by default in your RedLine13 account.\u00a0 The second thing to check is your subnet configuration<\/a> in AWS.\u00a0 This is a more technical setting that is usually configured when you set up your VPC network.\u00a0 Here is an example subnet which is configured for public IP address assignment:<\/p>\n

\"AWS
Configuring an AWS subnet to automatically assign public IP addresses.<\/figcaption><\/figure>\n

The important setting is ensuring \u201cAuto-assign public IPv4 addresses<\/em>\u201d is set to \u201cYes<\/em>\u201d.\u00a0 (We also have another blog post<\/a> that covers more advanced configurations.)<\/p>\n

<\/a>Two signs you are using a Private IP address:<\/h3>\n

There are two easy to tell if your load generators are configured incorrectly with a private IP address.\u00a0 The first and most obvious sign is that your load test will unexpectedly terminate with the message \u201cTest automatically canceled due to no communication from load agent.<\/em><\/span>\u201d\u00a0 While this message may be received for other reasons, a private IP assignment should be at the top of the suspect list. The reason is fairly evident \u2013 if a load generator has a private IP, then RedLine13 cannot communicate with it.<\/p>\n

The second sign to look for when a private IP assignment is suspected is the actual address format.\u00a0 The administrative body on the matter is the Internet Engineering Task Force<\/em> (IETF) which has outlined ranges<\/a> reserved for private addresses.\u00a0 These are as follows:<\/p>\n