fix(pgw): add message

Author: RoRoJ

pages/public-gateways/concepts.mdx

@@ -14,6 +14,9 @@ categories:
 
 ## Allowed IPs
 
+The Allowed IPs feature is only available to [IPAM-mode](#ipam) Public Gateways. Legacy gateways are not compatible with this feature.
+</Message>
+
 Allowed IPs is a feature of [SSH bastion](#ssh-bastion). It allows you to specify a list of IP address ranges which should be allowed to connect to the SSH bastion and the resources behind it. All other IP addresses will be blocked from connecting. Find out more in the [SSH bastion](/public-gateways/how-to/use-ssh-bastion/#how-to-configure-allowed-ips) documentation.
 
 ## Default route

pages/public-gateways/how-to/use-ssh-bastion.mdx

@@ -41,6 +41,10 @@ The [Allowed IPs](#how-to-configure-allowed-ips) feature lets you control which
 
 ## How to configure allowed IPs
 
+<Message type="note">
+The Allowed IPs feature is only available to [IPAM-mode](/public-gateways/concepts/#ipam) Public Gateways. Legacy gateways are not compatible with this feature.
+</Message>
+
 The [Allowed IPs](#how-to-configure-allowed-ips) feature lets you control which public IPs can connect to resources behind the bastion. All IPs are blocked except those specified in your Allowed IPs list. 
 
 When you first activate SSH bastion, the Allowed IPs list has one entry: a default IP range of `0.0.0.0/0` which gives access to **all** public IPs.
@@ -101,7 +105,7 @@ The command to use is:
 ```bash
 ssh -J bastion@PUBLIC_IP_OF_PUBLIC_GATEWAY:61000 user@FQDN
 ```
-
+q
 The FQDN is `<resource-name>.<private-network-name>.internal`.
 
 When connecting as the user `alex` on an Instance named `scw-frosty-cannon` on a Private Network named `pvn-silly-goodall`, where the Public Gateway has an IP `51.158.125.88` and SSH bastion is configured on port 6100, the full connection command  would therefore be:
@@ -112,7 +116,7 @@ ssh -J [email protected]:61000 [email protected]
 
 <Message type="note">
 
-For [Legacy Private Networks](/network/public-gateways/concepts/#ipam) not in IPAM mode and still using DHCP configuration objects, the FQDN may be different. The domain to use was set when the Public Gateway was attached to the Private Network. Therefore, the FQDN to use depends on how you made this attachment:
+For [Legacy Private Networks](/public-gateways/concepts/#ipam) not in IPAM mode and still using DHCP configuration objects, the FQDN may be different. The domain to use was set when the Public Gateway was attached to the Private Network. Therefore, the FQDN to use depends on how you made this attachment:
 
 - **Via the Scaleway console**: The FQDN takes the form `resource-name.priv`
 - **Via Terraform**: The FQDN takes the form `resource-name.dns_local_name` where `dns_local_name` is [this](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/vpc_public_gateway_dhcp#dns_local_name) Terraform option.