# Wireguard on KimSuffi slows down or blocks network access

**URL:** <https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847>\
**Category:** Bare Metal et VPS\
**Tags:** vps\
**Created:** [September 7, 2026, 12:00pm UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847 "2026-09-07T12:00:46Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![MartinR2](https://community.ovhcloud.com/letter_avatar/martinr2/32/6_22734026db12803ebb3e059622ac3534.png) [@MartinR2](https://community.ovhcloud.com/u/MartinR2)\
**Post date:** [September 7, 2026, 12:00pm UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/1 "2026-09-07T12:00:46Z")

</div>

Hello

On a KimSuffi server I installed WireGuard to connect to a VPN on a Freebox, with the following configuration:

```auto
[Interface]
PrivateKey = **************************************
Address = 192.168.27.71/32
DNS = 212.27.38.253
MTU = 1360

[Peer]
PublicKey = PJ61Y3lfxoChmdXLUlDs3IKB9PIEUXWkmUCmGbPq0mk=
Endpoint = xxx.xxx.xxx.xxx:44570
AllowedIPs =192.168.27.64/27
PersistentKeepalive = 0

```

I removed the 0.0.0.0/0 mask generated by the Freebox to avoid blocking everything (thanks @sturpin!) and also 192.168.1.0/24 without any noticeable effect.

When I activate WireGuard with: `wg-quick up wg0` it works fine, but some network accesses from the server to the outside (outside the WireGuard VPN) stop working, and the website hosted by the server becomes very heavily slowed down.

Everything returns to normal as soon as WireGuard is stopped.

What can I do to keep WireGuard active, preferably permanently, and have normal network access to and from the server?

Thanks for your suggestions!

---

<div class="post-metadata">

**Author:** ![sturpin](https://community.ovhcloud.com/user_avatar/community.ovhcloud.com/sturpin/32/30025_2.png) [@sturpin](https://community.ovhcloud.com/u/sturpin)\
**Post date:** [September 7, 2026, 2:44pm UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/2 "2026-09-07T14:44:55Z")

</div>

Hello @MartinR2

When you use `wg-quick up wg0`, the WireGuard script reconfigures your server's network routes. Even though you have limited `AllowedIPs` to `192.168.27.64/27`, the script may be adding a default route that points to the tunnel, or it may be modifying the main routing table.

The solution is to make sure WireGuard only manages traffic destined for your Freebox network and does not interfere with the default route for the rest of the traffic 😏

Let's do the following, to see if we achieve the desired effect:

1. Activate WireGuard as you normally do:  
`sudo wg-quick up wg0`
2. Add a static route so that VPN traffic goes through the tunnel:  
`sudo ip route add 192.168.27.64/27 dev wg0`
3. Force the default route to be that of your public interface:  
`sudo ip route del default`  
`sudo ip route add default via YOUR_GATEWAY dev eth0`  
🗒 To find **your\_gateway** you can do so with the command `ip route show default`

Additionally we will use `Table = Off` inside the `[Interface]` section. With this option the traffic destined for the 192.168.27.64/27 network will not be automatically routed. For it to work, you will need to **add the route manually** with `sudo ip route add 192.168.27.64/27 dev wg0`.

Then, to **make it permanent** , you can add this line to the `wg-quick` script by editing the file `/etc/wireguard/wg0.conf` with the `PostUp` option, placed after Table = Off:

```bash
[Interface]
...
Table = off
PostUp = ip route add 192.168.27.64/27 dev wg0

```

Finally, save the file and **restart WireGuard** 😉

P.S.: Bit by bit I am reaching the level of explanations that my colleague @Asterix usually gives 😀

Cheers,  
Sergio Turpín

---

<div class="post-metadata">

**Author:** ![MartinR2](https://community.ovhcloud.com/letter_avatar/martinr2/32/6_22734026db12803ebb3e059622ac3534.png) [@MartinR2](https://community.ovhcloud.com/u/MartinR2)\
**Post date:** [September 7, 2026, 4:51pm UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/3 "2026-09-07T16:51:37Z")

</div>

Thank you for this information.

Before trying them, I notice that the command `wg-quick up wg0` executes `ip ` **`-4`** ` route add 192.168.27.64/27 dev wg0`, i.e., what you suggest with the additional -4 parameter. Unless I'm mistaken, nothing in the Freebox restricts me to IPv4, so I don't know why this parameter is present.

Should I still run this command `ip route add192.168.27.64/27 dev wg0` or rather `ip **-6** route add <the corresponding IPv6 address> dev wg0`? Or should I refrain from launching this `first command?`

---

<div class="post-metadata">

**Author:** ![MartinR2](https://community.ovhcloud.com/letter_avatar/martinr2/32/6_22734026db12803ebb3e059622ac3534.png) [@MartinR2](https://community.ovhcloud.com/u/MartinR2)\
**Post date:** [September 7, 2026, 6:13pm UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/4 "2026-09-07T18:13:05Z")

</div>

I did `sudo ip route del default comme suggéré.`

My SSH connection got blocked and I can no longer access the server!

I tried booting in rescue mode, I attempted `ip route add default via 144.217.72.254 dev eth0` but I got an error: `RTNETLINK answers: File exists`

`What should I do to regain access to my server (even without Wireguard)??`

---

<div class="post-metadata">

**Author:** ![MartinR2](https://community.ovhcloud.com/letter_avatar/martinr2/32/6_22734026db12803ebb3e059622ac3534.png) [@MartinR2](https://community.ovhcloud.com/u/MartinR2)\
**Post date:** [September 7, 2026, 7:02pm UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/5 "2026-09-07T19:02:29Z")

</div>

After about 15 minutes and several reboots, but without trying anything else, I finally regained access to my server...

---

<div class="post-metadata">

**Author:** ![sturpin](https://community.ovhcloud.com/user_avatar/community.ovhcloud.com/sturpin/32/30025_2.png) [@sturpin](https://community.ovhcloud.com/u/sturpin)\
**Post date:** [September 7, 2026, 10:28pm UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/6 "2026-09-07T22:28:18Z")

</div>

Hello @MartinR2

Wow, what a scare! I’m glad you were able to regain access 👌

Indeed, the command `sudo ip route del default` removed the default route from your server, which was the one it used to reach the Internet and therefore for your SSH connection to get back to you 😏

To avoid this problem and keep WireGuard running without affecting other services, I recommend using the `Table = off` option and configuring the routes with `PostUp`. It’s the cleanest way and avoids touching the default route.

```bash
[Interface]
PrivateKey = ***...***
Address = 192.168.27.71/32
DNS = 212.27.38.253
MTU = 1360
Table = off
PostUp = ip -4 route add 192.168.27.64/27 dev wg0

```

Based on what you told me, the `-4` parameter you see in the `ip` command in the PostUp that wg‑quick runs is correct because you’re working with IPv4 addresses. If your Freebox also handles IPv6, you might need a similar line with `-6` for the IPv6 routes you want, but for what you need, the IPv4 configuration is sufficient.

Restart WireGuard ➡ with `sudo wg-quick down wg0` and then `sudo wg-quick up wg0` so the changes take effect.

With this configuration, WireGuard will not modify your server’s default route.

Let me know how it goes, cheers.  
Sergio Turpín

---

<div class="post-metadata">

**Author:** ![MartinR2](https://community.ovhcloud.com/letter_avatar/martinr2/32/6_22734026db12803ebb3e059622ac3534.png) [@MartinR2](https://community.ovhcloud.com/u/MartinR2)\
**Post date:** [September 8, 2026, 6:28am UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/7 "2026-09-08T06:28:02Z")

</div>

Hello  
I only changed the configuration, as suggested, and didn’t touch the default route.

The server remains reachable and my SSH is no longer blocked 🫠, but I still have the same problem.

As soon as I enable Wireguard, there is no access (ping especially) from the server to external sites, and a significant slowdown of the websites hosted on this server (20 seconds for a page instead of half a second; perhaps a consequence of the first issue). It returns to normal when I stop Wireguard.

For your information, when I start Wireguard with `wg-quick up` it displays:

`[#] ip link add wg0 type wireguard`  
`[#] wg setconf wg0 /dev/fd/63`  
`[#] ip -4 address add 192.168.27.71/32 dev wg0`  
`[#] ip link set mtu 1360 up dev wg0`  
`[#] resolvconf -a wg0 -m 0 -x`  
`[#] ip -4 route add 192.168.27.64/27 dev wg0`

---

<div class="post-metadata">

**Author:** ![sturpin](https://community.ovhcloud.com/user_avatar/community.ovhcloud.com/sturpin/32/30025_2.png) [@sturpin](https://community.ovhcloud.com/u/sturpin)\
**Post date:** [September 8, 2026, 7:56am UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/8 "2026-09-08T07:56:42Z")

</div>

Hello @MartinR2

Have you verified that you only have one default route?  
`ip route show | grep default`

If you see more than one, remove the one that points to `wg0`. This ensures that general Internet traffic doesn’t try to go through the tunnel.

What we’ll also do to test is disable WireGuard’s DNS. Comment out the line `DNS = 212.27.38.253` in `wg0.conf`

Let me know if we solve anything with this suggestion.

Best regards,  
Sergio Turpín

---

<div class="post-metadata">

**Author:** ![MartinR2](https://community.ovhcloud.com/letter_avatar/martinr2/32/6_22734026db12803ebb3e059622ac3534.png) [@MartinR2](https://community.ovhcloud.com/u/MartinR2)\
**Post date:** [September 8, 2026, 8:51am UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/9 "2026-09-08T08:51:18Z")

</div>

There was only one default route.

By disabling WireGuard’s DNS in the configuration, the problem seems to disappear.

Thanks for your help.

However, let me wait a few days before marking it "resolved"...

---

<div class="post-metadata">

**Author:** ![sturpin](https://community.ovhcloud.com/user_avatar/community.ovhcloud.com/sturpin/32/30025_2.png) [@sturpin](https://community.ovhcloud.com/u/sturpin)\
**Post date:** [September 8, 2026, 9:32am UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/10 "2026-09-08T09:32:38Z")

</div>

Perfect! Keep me informed 😉 👍

---

<div class="post-metadata">

**Author:** ![MartinR2](https://community.ovhcloud.com/letter_avatar/martinr2/32/6_22734026db12803ebb3e059622ac3534.png) [@MartinR2](https://community.ovhcloud.com/u/MartinR2)\
**Post date:** [September 9, 2026, 6:35am UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/11 "2026-09-09T06:35:02Z")

</div>

Everything seems settled now.  
Thanks again for your time.

---

<div class="post-metadata">

**Author:** ![system](https://community.ovhcloud.com/user_avatar/community.ovhcloud.com/system/32/5_2.png) [@system](https://community.ovhcloud.com/u/system)\
**Post date:** [September 11, 2026, 6:35am UTC](https://community.ovhcloud.com/t/wireguard-sur-kimsuffi-ralentit-ou-bloque-des-acces-reseau/53847/12 "2026-09-11T06:35:25Z")

</div>

Ce sujet a été automatiquement fermé après 2 jours. Aucune réponse n'est permise dorénavant.
