---
title: I attached the Public Gateway to my Private Network, but the services provided by the gateway are not working (NAT etc)
description: This page explains how to troubleshoot connection problems after attaching a Public Gateway to a Private Network but finding that the services provided by the gateway are not working (NAT etc)
tags: public-gateway private-network public gateway private network error nat dns 
dates:
  validation: 2025-07-16
  posted: 2021-05-26
---
import Requirements from '@macros/iam/requirements.mdx'


<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization

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:

1. Identify the Private Network's network interface on your Instance (which is attached to a Public Gateway). We will use `priv0` as an example.
2. Set it as `UP` to be able to use it: `ip link set priv0 up`
3. Identify the MAC address of the gateway in your Private Network using either the [Scaleway console](https://console.scaleway.com/) or the [API](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateway-networks) (`mac_address` field of the GatewayNetwork). We'll use `02:00:b1:ac:ca:fe` as an example.
4. Go [here](https://ben.akrin.com/?p=1347), and paste the MAC address to get the IPv6 Link-Local Address of your gateway. In our example, using priv0, it is `fe80::000:b1ff:feac:cafe`
5. 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 `ping fe80::000:b1ff:feac:cafe%priv0`.

    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, 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 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](/vpc/troubleshooting/autoconfig-not-working/).

If the problem persists, do not hesitate to [contact us on the #public-gateway channel on the Scaleway Community Slack](https://scaleway-community.slack.com/archives/C01NTFET64D).