WireGuard VPN Issue – Connectivity Fails on Same ISP ( Afrihost)

[Nick555]

Hi all


I’m experiencing an issue with inbound WireGuard VPN connectivity and would like to check whether this could be related to Afrihost network behavior.

Setup​

• Router: Cudy M3000 running WireGuard server
• Port forwarding configured (UDP)
• DDNS hostname (DuckDNS) resolving correctly
• VPN subnet: 10.10.0.0/24
• LAN subnet: 10.0.0.0/24

What works​

• VPN connections from mobile data (LTE) establish successfully
• Connections from a different ISP also work correctly
• Traffic routes as expected once connected

The issue​

• When a client on a different network but also using Afrihost attempts to connect:
  • Connection fails or times out
  • No WireGuard handshake is established

Additional context​

• This setup previously worked without issue, including connections from other Afrihost clients
• The problem appears to be a recent change and is now only affecting connections where the client is also on Afrihost

Observations​

• Client and server have different public IP addresses
• DNS resolution is correct and points to the public IP
• Port forwarding is confirmed working via external testing
• The issue appears specific to traffic originating from within the Afrihost network

Query​

• Could CGNAT or internal routing policies be affecting this, and is there a way to resolve it as this appears to be caused by a recent change?

 

[rustypup]

So much sad here I'm going to need some counselling.

 

[Afrigirl]

Hi all


I’m experiencing an issue with inbound WireGuard VPN connectivity and would like to check whether this could be related to Afrihost network behavior.

Setup​

• Router: Cudy M3000 running WireGuard server
• Port forwarding configured (UDP)
• DDNS hostname (DuckDNS) resolving correctly
• VPN subnet: 10.10.0.0/24
• LAN subnet: 10.0.0.0/24

What works​

• VPN connections from mobile data (LTE) establish successfully
• Connections from a different ISP also work correctly
• Traffic routes as expected once connected

The issue​

• When a client on a different network but also using Afrihost attempts to connect:
  • Connection fails or times out
  • No WireGuard handshake is established

Additional context​

• This setup previously worked without issue, including connections from other Afrihost clients
• The problem appears to be a recent change and is now only affecting connections where the client is also on Afrihost

Observations​

• Client and server have different public IP addresses
• DNS resolution is correct and points to the public IP
• Port forwarding is confirmed working via external testing
• The issue appears specific to traffic originating from within the Afrihost network

Query​

• Could CGNAT or internal routing policies be affecting this, and is there a way to resolve it as this appears to be caused by a recent change?

Hi.

Please share the source and destination IP.

 

[Nick555]

Hi.

Please share the source and destination IP.

Thanks i will dm you the public ips

 

[waynehooper]

I am also having this issue - is there a resolution to the problem

Have sent you a DM with the IP's

 

[Afrigirl]

I am also having this issue - is there a resolution to the problem

Have sent you a DM with the IP's

Hi.

We are aware of an issue affecting connectivity between some clients on our network. Our network team and upstream provider have identified the cause and are working on a permanent solution.

In the meantime, temporary adjustments are being made to minimise the impact and restore connectivity where required. The permanent fix has already been approved by the provider and is currently awaiting implementation.

 

[netstrider]

Sounds like a NAT hairpin that's not working.

 

[waynehooper]

Hi.

We are aware of an issue affecting connectivity between some clients on our network. Our network team and upstream provider have identified the cause and are working on a permanent solution.

In the meantime, temporary adjustments are being made to minimise the impact and restore connectivity where required. The permanent fix has already been approved by the provider and is currently awaiting implementation.

@AfriGuy any update on when this will be fixed