...
In the VPC configuration window, enter
- the VPC name, and
- the subnet name, region and address, and
- optionally, an alternative MTU size (at the bottom of the window).
Click on Create at the bottom of the window to create the VPC.
...
After restarting the network (systemctl restart network), the configuration as defined in the ifcfg-files should be set for the interfaces. On RHEL/CentOS 8 systems restart the NetworkManager instead (systemctl restart NetworkManager).
Please note: if your instance normally would detect the network MTU automatically, this will not work if DHCP is disabled, and the correct MTU must be set manually.
| Div | ||
|---|---|---|
| ||
Additional GCP-specific Information
...
If this is not enabled, host and guest system can only communicate via the external IP addresses, not via the internal IP addresses.
Network Interface MTU
The A VPC network has a maximum default transmission unit (MTU) of 1460 bytes . Interfaces should be configured to this value for Linux images and Windows Server images. During the creation of a VPC you can choose an alternative MTU size of 1500. Google-provided Linux system images are already automatically configured with the appropriate MTU at start. For custom images (especially, if they do not rely on DHCP), set the MTU to the same value as configured for the VPC to avoid the increased latency and packet overhead caused by fragmentation. Client , or even connectivity problems. For an MTU size of 1460, client applications that communicate with GCP instances over UDP should have a maximum payload of 1432 bytes to avoid fragmentation.
...