I attached the Public Gateway to my Private Network, but the services provided by the gateway are not working (NAT etc)
You may need certain IAM permissions to carry out some actions described on this page. This means:
First, check whether the gateway is properly plugged into the Private Network. We currently have a known issue where the GatewayNetwork gets created successfully without the gateway actually getting plugged into the network. To check whether this is the issue you are experiencing, do the following:
Identify the Private Network’s network interface on your Instance (which is attached to a Public Gateway). We will use
priv0as an example.
Set it as
UPto be able to use it:
ip link set priv0 up
Go here, and paste the MAC address to get the IPv6 Link-Local Address of your gateway. In our example, using priv0, it is
From your Instance, ping the gateway on its IPv6 link-local address, taking care to specify the Private Network interface. In our example, using
priv0, the command is
If the address does not ping, then you are indeed experiencing this known issue. The best way to fix it is either to delete and recreate the GatewayNetwork (you can keep the same DHCP configuration by specifying a
dhcp_idupon creation), or attach a dummy Private Network to the gateway.
If the address does ping, then you may be either experiencing another issue, where the interface gets misconfigured, or just have an error in your configuration. To test for this, update any property of your GatewayNetwork or the associated DHCP configuration in order to trigger a reconfiguration. If this does not fix it, check your configuration.
It may also be useful to try the steps outlined in this troubleshooting.
If the problem persists, do not hesitate to contact us on the #public-gateway channel on the Scaleway Community Slack.