In order to use SORACOM Gate, you must set up a server within your private network environment to act as the gate peer, and register it to the VPG where you want Gate enabled.
When registering your server as a gate peer, you must provide its IP address within your network environment (for example, the private IPv4 address of the EC2 instance in your AWS VPC), which is referred to as the outerIpAddress of your gate peer.
Once registered, you will be assigned an innerIpAddress which your server will use in order to send packets to your Air SIM devices using the VXLAN (virtual L2 connection). You must configure the VXLAN interface and routing rules inside your server as explained in the Gate setup guide.
In summary:
-
outerIpAddress
- When registering a server as a gate peer, this refers to your server's private IP address (for example, the 192.168.x.x private IP address of the EC2 instance in your network environment)
- Similarly, when configuring routing rules in your gate peer, this refers to the two VPG gate peers' corresponding IP addresses within the SORACOM network environment (normally 100.64.x.x)
- innerIpAddress refers to the IP addresses assigned to your gate peer(s) and the two VPG gate peers, which are used for the VXLAN connection.
Note:
When querying the list of gate peers in a VPG, a ownedByCustomer key will be returned with each peer to indicate whether it is a gate peer in your private network environment (if true), or a gate peer in the VPG (if false).
Additionally, when viewing your VPG's Advanced Settings in the User Console, gate peers will be organized by the Gate Peers in your network and Gate Peers in VPG sections, and the IP addresses will correspond as follows:
- Tunnel Endpoint IP address = outerIpAddress
- Device Subnet IP address = innerIpAddress