Why can't I type the Frontend IP manually; what should I do to use an IP that is not in the list (e.g. IPv6) on a vService?
Short answer
Because the Frontend IP field is not free text; it shows an IP record defined on an interface in the network configuration of TR7. A vService can listen only on an address the device actually owns; this is why only the IPs defined under Network → Interfaces appear in the list. An IP that is not in the list is first added to an interface: without leaving the form with the + Add IP button in the vService form, or from the Network → Interfaces screen. The added IP is then selected from the list.
Problem: Why Must the IP First Be Defined on the Network Side?
In TR7, IP addresses live in the network layer: each IP is bound to an interface and a route table. The vService refers to this record; even if the vService is deleted, the IP remains in the network configuration. When the IP is added, TR7 checks the validity of the address, the subnet length (CIDR), and whether it collides with another IP in the same route table. A manually typed address would be an address that has not passed these checks and is not defined on the device.
Solution: Two Methods
| Your situation | Suitable method |
|---|---|
| The IP will be added to an existing interface, and I am in the vService form | Method 1: + Add IP from the vService form |
| A new interface, VLAN or route table is also needed | Method 2: Network → Interfaces |
Method 1: + Add IP from the vService Form Recommended
- How it works The + Add IP button in the Frontend IP list opens the IP add form in Network as a window; the added IP arrives in the frontend table as a new row.
- Where it is opened vService → Frontend → Frontend IP list → + Add IP
- Requirement The interface to which the IP will be added must exist; the user must have the permission to change the network configuration; if there is no permission, the button does not appear
- vService type HTTP, L7 TCP, Network
Step-by-Step Configuration
In the vService form, the Frontend IP list is opened and the + Add IP button above the list is clicked.
In the IP Interface field, the interface to which the IP will be added is selected. The window opens with the first interface selected; this field must be checked. If there is more than one route table, the Route Table field also appears.
The address and the CIDR are written to the IP table. The CIDR field also comes with 24 for IPv6; for IPv6, the correct value (e.g. 64) is entered manually. In a cluster setup, VIP is selected as the Ip Type so that the vService is published redundantly.
The Add IP button is clicked.
The added IP arrives in the frontend table as a new row; the row opens with port 80 and unencrypted HTTP. Port and Protocol are corrected as needed.
The Save button is clicked.
Verification
The status of the added IP is checked in the Network → Interfaces list.
First Absent in system, Up shortly after@interface name.Method 2: Network → Interfaces
- How it works The IP is added to an interface on the network configuration screen; then it is selected from the list in the vService form.
- Where it is openedNetwork → Interfaces → Add IP
- Requirement If a new VLAN or interface is needed, it must be added first
- vService type HTTP, L7 TCP, Network
Step-by-Step Configuration
If there is not yet an interface on TR7 for the network to which the IP will be added, first the route table (if needed) and then the VLAN interface are created. Order and details: What do I need to do on the network side first to open a vService on an IP in a different subnet / VLAN?
In the Configuration Menu opened with the TR7 logo at the bottom left, the Network → Interfaces screen is opened; the relevant interface is right-clicked and Add IP is selected (it also opens from the Actions menu or from the IP tab of the preview panel).
It is checked that the correct interface is selected in the IP Interface field; the IP and the CIDR are written.
The Add IP button is clicked.
On the Load Balancer → Load Balancer vService List screen, the vService is opened and the new IP is selected from the Frontend IP list.
The Save button is clicked.
Verification
curl -v http://203.0.113.90/The response of the vServiceCommon Mistakes
- Adding the IP to the wrong interface. The window opens with the first interface selected; an IP added without checking the IP Interface field is defined on the wrong network.
- Leaving the CIDR at 24 for IPv6. The field does not change automatically for IPv6; the correct value such as /64 is entered.
- Looking for an IP in another route table on a Network vService. The list of a Network vService is limited to the IPs in the selected Route Table.
- Leaving the new row at 80/HTTP. The row that comes with + Add IP opens with port 80 and unencrypted HTTP.
- Adding an IP that already exists in the same route table. The record is rejected with the IP collision error.
How it is done in the documentation
