[Vadim Smirnov]

Thank you for reaching out and for your interest in the NDISAPI project. I completely understand the confusion—licensing details can sometimes be tricky.

You’re correct that the NDISAPI library source code is open-source under the MIT license, which allows for a lot of flexibility. However, the Windows Packet NDIS drivers are a bit different—they’re free for personal and non-commercial use, but if you’re planning to use them for commercial purposes, I believe it’s fair to share a portion of the revenue.

I understand that as a small business, you might have a tight budget. If the licensing costs are a concern, I’m open to discussing flexible options, such as installment payments or perhaps a profit-sharing arrangement. My goal is to find a solution that works for both of us.

Looking forward to hearing your thoughts.

[Vadim Smirnov]

Do you have Virtual Adapter mode enabled in the WireSockUI settings?

I’m also a bit confused about the AllowedIPs value. In this context, 0.0.0.0/24 represents the IP range from 0.0.0.0 to 0.0.0.255. However, this is typically not a useful or valid range because 0.0.0.0 is a non-routable meta-address used to designate an invalid, unknown, or non-applicable target (often referred to as the default route).

Usually, AllowedIPs would be set to a range of IPs that are meaningful for the network, such as 192.168.1.0/24 to route a local network, or 0.0.0.0/0 to route all traffic through the VPN. Therefore, 0.0.0.0/24 is likely a mistake and should be corrected to reflect the intended IP range.

[Vadim Smirnov]

Could you share your Wireguard configuration, excluding the keys and server endpoint? Additionally, I have a question: Are you using WireSock in transparent mode or virtual adapter mode (-lac)?

[Vadim Smirnov]

In this context, “no-UWP” simply means that a few classes unavailable on Windows 7 are excluded from this build. These classes are specifically used for Toast notifications and checking for new releases on GitHub. Aside from these exclusions, the builds are identical.

[Vadim Smirnov]

С этим действительно существует ряд сложностей. В целом, добавить еще один или несколько тоннелей в так называемом прозрачном режиме несложно: пакеты в этом случае маршрутизируются вручную. Однако сделать то же самое в режиме с виртуальными адаптерами гораздо сложнее. Для каждого адаптера добавляются соответствующие записи в таблицу маршрутизации, что может создать значительную путаницу, и определить, на какой адаптер в итоге пойдет трафик, будет очень сложно. Скорее всего, придется ограничиться одним сетевым интерфейсом, а для дополнительных тоннелей использовать трансляцию адресов. Дополнительно возникают сложности с конфигурированием, приоритезацией, поддержкой в UI и т.д.

В общем, работы много, а свободного времени у меня очень мало.☺️

[Vadim Smirnov]

Thank you for your kind words. I believe users are requesting a specific ‘kill switch’ UI control. For instance, the official WireGuard for Windows includes a checkbox for this feature, which impacts the AllowedIPs settings.

Regarding the notifications, I noticed that you are using a WireSock UI build without UWP. This version lacks certain features, including notifications, and was designed for compatibility with Windows 7.

[Vadim Smirnov]

Hi Roberts,

Thank you for your question.

This is how VPNs are generally designed. However, the WireSock VPN Client allows you to stay connected to both your LAN and VPN simultaneously through split tunneling features. This should enable you to access both networks without issue.

It’s worth noting that the WireSock VPN Client is currently only available for Windows and does not have a client for smartphones.

I hope this helps.

[Vadim Smirnov]

While the WireSock client does not support this feature at the moment, it looks interesting and aligns with some of our future goals. I am considering a configuration deployment system that would involve an appliance on the server side and support in the WireSock client.

Currently, you would need to create and configure the client files manually. However, the idea of automatically generating client WireGuard files and making adjustments for specific IP assignments is compelling. I will keep this in mind for future developments.

[Vadim Smirnov]

I’ve heard about it and I’m genuinely interested in exploring it further. However, my schedule is quite tight, and I’m not sure if I’ll have enough time to dedicate to it.

[Vadim Smirnov]

I have some ideas about what might be happening and just need to allocate some time to address this issue. I also suspect the problem does not occur in Transparent Mode (without the -lac command line switch). Can you confirm this?

[Vadim Smirnov]

The setup depends on the type of machine you intend to use for the WireGuard server. If you’re using a Windows machine, you can set it up with WireSock VPN Gateway. I’ve personally set up several Intel NUC machines with Windows for personal use using it. If you’re using a Linux machine, I recommend using this script to install and manage your WireGuard server.

[Vadim Smirnov]

Please check this post https://www.ntkernel.com/wireguard-vpn-server-on-windows/

[Vadim Smirnov]

EthernetBridge was originally not intended for production use. However, wrapping it into a Windows service should not be a major issue. The service could be designed to read parameters from a configuration file or accept them via the command line.

However, I must mention that finding spare time to implement this might be challenging for me at the moment.

[Vadim Smirnov]

Эти локализации от компоненты TaskScheduler.

[Vadim Smirnov]

Если вопрос касается https://github.com/wiresock/WireSockUI, то в проекте пока нет русской локализации. Интерфейс достаточно простой, и пока не возникала острая необходимость в переводе. Однако, возможно, стоит рассмотреть добавление языковых локализаций в будущем. 🤔

[Author]

Posts