[GH-ISSUE #986] No local network access

bsakaguchi commented

2026-10-13 20:18:26 +00:00

Owner

Originally created by @alexbalkan on GitHub (Aug 19, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/986

Describe the bug
When connected, access to local network resources is lost. Including I have a local secure dns
Today I installed this miracle and started testing it. Out of 10 connections, the local network was not blocked once, at the moment when I started writing about the problem).

To Reproduce

Expected behavior

Add local networks exception

Log files

Screenshots

Desktop (please complete the following information):

Desktop

OS: Windows 10
Version 22H2 Build 19045.4780

Server (please complete the following information):

OS: Debian 10

Additional context
Please forgive me for my English.
There is a very big problem. Once connected, I will lose access to all my local network management services. Yes, I saw separate connections of networks. Isn’t it better to do it according
to Feng Shui and add the exclusion of local network addresses? Another problem, on my network I use my own secure DNS servers, after connecting to the VPN they also became unavailable.

Originally created by @alexbalkan on GitHub (Aug 19, 2024). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/986 **Describe the bug** When connected, access to local network resources is lost. Including I have a local secure dns Today I installed this miracle and started testing it. Out of 10 connections, the local network was not blocked once, at the moment when I started writing about the problem). **To Reproduce** **Expected behavior** Add local networks exception **Log files** **Screenshots** **Desktop (please complete the following information):** Desktop - OS: Windows 10 - Version 22H2 Build 19045.4780 **Server (please complete the following information):** - OS: Debian 10 **Additional context** Please forgive me for my English. There is a very big problem. Once connected, I will lose access to all my local network management services. Yes, I saw separate connections of networks. Isn’t it better to do it according to Feng Shui and add the exclusion of local network addresses? Another problem, on my network I use my own secure DNS servers, after connecting to the VPN they also became unavailable.

bsakaguchi commented

2026-10-13 20:18:26 +00:00

Author

Owner

@hunterxp commented on GitHub (Aug 27, 2024):

Same problem with sharing resources to LAN clients from WSL.
Split tunneling doesn't work properly.

If I turn AmneziaVPN off everything works fine.

@hunterxp commented on GitHub (Aug 27, 2024): Same problem with sharing resources to LAN clients from WSL. Split tunneling doesn't work properly. ![image](https://github.com/user-attachments/assets/c8ffb0f5-2954-40b9-a5f7-c289c6b22e86) If I turn AmneziaVPN off everything works fine.

bsakaguchi commented

2026-10-13 20:18:27 +00:00

Author

Owner

@Shoker2 commented on GitHub (Oct 16, 2024):

Попробуй добавить в раздельное тунелирование 192.168.0.0/16
Try adding in split tunneling 192.168.0.0/16

@Shoker2 commented on GitHub (Oct 16, 2024): Попробуй добавить в раздельное тунелирование 192.168.0.0/16 Try adding in split tunneling 192.168.0.0/16

bsakaguchi commented

2026-10-13 20:18:28 +00:00

Author

Owner

@hunterxp commented on GitHub (Oct 23, 2024):

Попробуй добавить в раздельное тунелирование 192.168.0.0/16 Try adding in split tunneling 192.168.0.0/16

К сожалению, не помогло :(
Unfortunately, it doesn't work.

@hunterxp commented on GitHub (Oct 23, 2024): > Попробуй добавить в раздельное тунелирование 192.168.0.0/16 Try adding in split tunneling 192.168.0.0/16 К сожалению, не помогло :( Unfortunately, it doesn't work.

bsakaguchi commented

2026-10-13 20:18:28 +00:00

Author

Owner

@inovikov78 commented on GitHub (Oct 23, 2024):

I have the same issue.
Once VPN is connected, I can't open the admin panel of my router and even have no access to the network printer (all the printer jobs will be printed once I disconnect VPN).
Is this normal behavior or need to change something in settings?
Let me know if you need any debug information from my side.
Thank you in advance.

@inovikov78 commented on GitHub (Oct 23, 2024): I have the same issue. Once VPN is connected, I can't open the admin panel of my router and even have no access to the network printer (all the printer jobs will be printed once I disconnect VPN). Is this normal behavior or need to change something in settings? Let me know if you need any debug information from my side. Thank you in advance.

bsakaguchi commented

2026-10-13 20:18:28 +00:00

Author

Owner

@Shoker2 commented on GitHub (Oct 23, 2024):

https://en.m.wikipedia.org/wiki/Private_network
Try add:
Private IPv4:
0.0.0.0
10.0.0.0/24
172.16.0.0/20 or 172.16.0.0/12
192.168.0.0/16

Dedicated space for carrier-grade NAT deployment:
100.64.0.0/10

Private IPv6:
fd00::/8

Link-local addresses:
169.254.0.0/16
fe80::/10
127.0.0.0/8

@Shoker2 commented on GitHub (Oct 23, 2024): https://en.m.wikipedia.org/wiki/Private_network Try add: Private IPv4: 0.0.0.0 10.0.0.0/24 172.16.0.0/20 or 172.16.0.0/12 192.168.0.0/16 Dedicated space for carrier-grade NAT deployment: 100.64.0.0/10 Private IPv6: fd00::/8 Link-local addresses: 169.254.0.0/16 fe80::/10 127.0.0.0/8

bsakaguchi commented

2026-10-13 20:18:29 +00:00

Author

Owner

@inovikov78 commented on GitHub (Oct 23, 2024):

Are you suggesting to add these networks into "Separate Tunelling" section?

@inovikov78 commented on GitHub (Oct 23, 2024): Are you suggesting to add these networks into "Separate Tunelling" section?

bsakaguchi commented

2026-10-13 20:18:29 +00:00

Author

Owner

@inovikov78 commented on GitHub (Oct 23, 2024):

Added one network 192.168.0.0/16 that works for me into "Separate Tuneling" and - it works!
Thank you very much!

@inovikov78 commented on GitHub (Oct 23, 2024): Added one network 192.168.0.0/16 that works for me into "Separate Tuneling" and - it works! Thank you very much!

bsakaguchi commented

2026-10-13 20:18:29 +00:00

Author

Owner

@Shoker2 commented on GitHub (Oct 23, 2024):

Предлагаете ли вы добавить эти сети в раздел «Раздельное туннелирование»?

Yes

@Shoker2 commented on GitHub (Oct 23, 2024): > Предлагаете ли вы добавить эти сети в раздел «Раздельное туннелирование»? Yes

bsakaguchi commented

2026-10-13 20:18:29 +00:00

Author

Owner

@hunterxp commented on GitHub (Oct 23, 2024):

@Shoker2 Thanks for the idea!
I was using WSL2 + portproxy over LAN, and my addresses were:
192.168.0.0/16
172.25.0.0/16
172.31.0.0/16

After adding them, it worked!

Thanks again!

@hunterxp commented on GitHub (Oct 23, 2024): @Shoker2 Thanks for the idea! I was using WSL2 + portproxy over LAN, and my addresses were: 192.168.0.0/16 172.25.0.0/16 172.31.0.0/16 After adding them, it worked! Thanks again!

bsakaguchi commented

2026-10-13 20:18:30 +00:00

Author

Owner

@itb55 commented on GitHub (Nov 15, 2024):

For each PC in my network, I always add 4 specific routes to the split tunneling configuration:

0.0.0.0
10.0.0.0/24
192.168.0.0/16
127.0.0.0/8

@itb55 commented on GitHub (Nov 15, 2024): For each PC in my network, I always add 4 specific routes to the split tunneling configuration: 0.0.0.0 10.0.0.0/24 192.168.0.0/16 127.0.0.0/8

bsakaguchi commented

2026-10-13 20:18:30 +00:00

Author

Owner

@komelgman commented on GitHub (Dec 18, 2024):

fe80::/10

there is any way to add ipv6 to split tunneling?

@komelgman commented on GitHub (Dec 18, 2024): > fe80::/10 there is any way to add ipv6 to split tunneling?

bsakaguchi commented

2026-10-13 20:18:30 +00:00

Author

Owner

@Shm-Alex commented on GitHub (Mar 31, 2025):

For each PC in my network, I always add 4 specific routes to the split tunneling configuration:

0.0.0.0 10.0.0.0/24 192.168.0.0/16 127.0.0.0/8

I'll try it . Is this rule send all local net requests to ip with pattern (192.168.*.*) like Localhost => 192.168.1.254 direct to resource ? (Not Localhost => Amnezia Client=> Vpn Server => 192.168.*.* ... ip with pattern 192.168.*.* is not awailable for Vpn Server )

@Shm-Alex commented on GitHub (Mar 31, 2025): > For each PC in my network, I always add 4 specific routes to the split tunneling configuration: > > 0.0.0.0 10.0.0.0/24 192.168.0.0/16 127.0.0.0/8 I'll try it . Is this rule send all local net requests to ip with pattern (192.168.\*.\*) like Localhost => 192.168.1.254 direct to resource ? (Not Localhost => Amnezia Client=> Vpn Server => 192.168.\*.\* ... ip with pattern 192.168.\*.\* is not awailable for Vpn Server )

bsakaguchi commented

2026-10-13 20:18:31 +00:00

Author

Owner

@muzzy124 commented on GitHub (Aug 3, 2025):

For each PC in my network, I always add 4 specific routes to the split tunneling configuration:

0.0.0.0 10.0.0.0/24 192.168.0.0/16 127.0.0.0/8

correct networks are:
0.0.0.0
10.0.0.0/8 (not /24!)
192.168.0.0/16
127.0.0.0/8
172.16.0.0/12

@muzzy124 commented on GitHub (Aug 3, 2025): > For each PC in my network, I always add 4 specific routes to the split tunneling configuration: > > 0.0.0.0 10.0.0.0/24 192.168.0.0/16 127.0.0.0/8 correct networks are: 0.0.0.0 10.0.0.0/8 (not /24!) 192.168.0.0/16 127.0.0.0/8 172.16.0.0/12

bsakaguchi commented

2026-10-13 20:18:31 +00:00

Author

Owner

@VasVW commented on GitHub (Aug 24, 2025):

when I add 192.168.0.0/16, AmneziaVPN stops working. My IP becomes my usual ip

@VasVW commented on GitHub (Aug 24, 2025): when I add 192.168.0.0/16, AmneziaVPN stops working. My IP becomes my usual ip

bsakaguchi commented

2026-10-13 20:18:31 +00:00

Author

Owner

@vabka commented on GitHub (Nov 19, 2025):

Попробуй добавить в раздельное тунелирование 192.168.0.0/16 Try adding in split tunneling 192.168.0.0/16

Спасибо, для меня это помогло. Только я ставил 192.168.3.0/24, так как у меня такой адрес локальной сети.

@vabka commented on GitHub (Nov 19, 2025): > Попробуй добавить в раздельное тунелирование 192.168.0.0/16 Try adding in split tunneling 192.168.0.0/16 Спасибо, для меня это помогло. Только я ставил 192.168.3.0/24, так как у меня такой адрес локальной сети.

bsakaguchi commented

2026-10-13 20:18:32 +00:00

Author

Owner

@Sleepwalkerx commented on GitHub (Nov 26, 2025):

Получилось починить!
Использую WSL2, не проходили соединения.
Узнал адрес с помощью wsl hostname -I и заработало!

@Sleepwalkerx commented on GitHub (Nov 26, 2025): Получилось починить! Использую WSL2, не проходили соединения. Узнал адрес с помощью wsl hostname -I и заработало!

bsakaguchi commented

2026-10-13 20:18:32 +00:00

Author

Owner

@DmitriyYukhanov commented on GitHub (Dec 23, 2025):

Added all of those and quickconnect.to as well but can't get the local Synology NAS quickconnect working.

When your PC and NAS are both in the same local network, it usually redirects to the local address, but it doesn't work while Amnezia VPN is connected.

Usual flow:

Enter Quick Connect address, i.e. https://mynas.quickconnect.to
If NAS is in the same network, it redirects to the i.e. https://192-168-0-12.mynas.direct.quickconnect.to:5001/

With Amnezia, it can't redirect with error:

https://192-168-0-12.mynas.direct.quickconnect.to:5001/webman/pingpong.cgi?action=cors&quickconnect=true
net::ERR_NAME_NOT_RESOLVED

I'm also using Amnezia DNS if it's related.

When accessing NAS directly through SMB or http://192.168.0.12:5001, it works fine with connected Amnezia.

@DmitriyYukhanov commented on GitHub (Dec 23, 2025): Added all of those and `quickconnect.to` as well but can't get the local Synology NAS quickconnect working. When your PC and NAS are both in the same local network, it usually redirects to the local address, but it doesn't work while Amnezia VPN is connected. Usual flow: 1. Enter Quick Connect address, i.e. `https://mynas.quickconnect.to` 2. If NAS is in the same network, it redirects to the i.e. `https://192-168-0-12.mynas.direct.quickconnect.to:5001/` With Amnezia, it can't redirect with error: ``` https://192-168-0-12.mynas.direct.quickconnect.to:5001/webman/pingpong.cgi?action=cors&quickconnect=true net::ERR_NAME_NOT_RESOLVED ``` I'm also using Amnezia DNS if it's related. When accessing NAS directly through SMB or `http://192.168.0.12:5001`, it works fine with connected Amnezia.

bsakaguchi commented

2026-10-13 20:18:33 +00:00

Author

Owner

@a-kruchinin commented on GitHub (Dec 28, 2025):

С AmneziaVPN и WSL через NAT у меня получилось очень просто, даже без запуска гостевых Linux (спасибо всем камрадам выше):

заходим в "Настройки параметров адаптера",
находим подключение "Hyper-V Virtual Ethernet Adapter", которым пользуется WSL (у меня называется "vEthernet (WSL)")
в его "Свойствах" открываем "Свойства" "IP версии 4" и смотрим "IP-адрес" (у меня 172.xxx.xxx.1 (HEX: ACXXXX01) и "Маску подсети" (у меня 255.255.240.0, т.е. размер 20) и вычисляем адрес подсети (в моем случае верхние 20 битов IP-адреса (HEX: ACXXX001))
в клиенте Amnezia Настройки->Соединение->Раздельное туннелирование сайтов, выбираем "Адреса из списка не должны открываться через VPN", добавляем в список наши адрес и маску подсети (в моем случае 172.xxx.xxx.0/20), чекаем "Вкл" для "Раздельное туннелирование..."
запускаем клиента Amnezia, WSL Linux, проверяем обновления, пинги и т.п.
PROFIT
Для ipv6, думаю, то же самое. Если не менять настройки адаптера на Windows хосте, все гостевые WSL Linux (и созданные после) будут иметь инет и локалку. С Mirrored еще не пробовал.

@a-kruchinin commented on GitHub (Dec 28, 2025): С AmneziaVPN и WSL через NAT у меня получилось очень просто, даже без запуска гостевых Linux (спасибо всем камрадам выше): - заходим в "**Настройки параметров адаптера**", - находим подключение "**Hyper-V Virtual Ethernet Adapter**", которым пользуется WSL (у меня называется "**vEthernet (WSL)**") - в его "Свойствах" открываем "Свойства" "**IP версии 4**" и смотрим "**IP-адрес**" (у меня 172.xxx.xxx.1 (HEX: ACXXXX01) и "**Маску подсети**" (у меня 255.255.240.0, т.е. размер 20) и вычисляем адрес подсети (в моем случае верхние 20 битов IP-адреса (HEX: ACXXX001)) - в клиенте Amnezia **Настройки**->**Соединение**->**Раздельное туннелирование сайтов**, выбираем "**Адреса из списка не должны открываться через VPN**", добавляем в список наши адрес и маску подсети (в моем случае 172.xxx.xxx.0/20), чекаем "Вкл" для "**Раздельное туннелирование...**" - запускаем клиента Amnezia, WSL Linux, проверяем обновления, пинги и т.п. - PROFIT Для ipv6, думаю, то же самое. Если не менять настройки адаптера на Windows хосте, все гостевые WSL Linux (и созданные после) будут иметь инет и локалку. С Mirrored еще не пробовал.

bsakaguchi referenced this issue

2026-10-13 20:47:32 +00:00

[PR #308] [CLOSED] Make check_user_in_sudo.sh use sudo -l #1737

Rows
Columns

[GH-ISSUE #986] No local network access #308