Hello,
Le 29/04/2024 à 09:08, Gert Doering a écrit :
Hi,
On Mon, Apr 29, 2024 at 03:22:38AM +, tincantech via Openvpn-users wrote:
FTR, the reason that the square brackets [] do not show information is
to preserve Client privacy.
This is news to me...
To me too.
Before posting I had a
Hello,
One of my users has just had his work laptop changed, and now when he
connects to our network via OpenVPN, his connection isn't working (seems
up but no packet gets through), and in the server logs, we're getting
the classical "MULTI: bad source address from client" errors. The
Le 03/09/2023 à 15:23, Jason Long a écrit :
Hello,
As I said, I have some scenario and I want to learn more.
By abusively relying on others? Strange way to achieve your goals.
Do you mean "ccd-exclusive"? If yes, then I edited the Server.conf as below:
ifconfig 20.1.0.1 255.255.255.0
mode
Le 03/09/2023 à 08:48, Jason Long via Openvpn-users a écrit :
Hello,
When I use "server 10.8.0.0 255.255.255.0" in the Server.conf file, then
OpenVPN assigns IP addresses to clients respectively. What should I do if I want to
assign a specific IP address to a client with a specific computer
Le 29/08/2023 à 09:02, Jason Long via Openvpn-users a écrit :
Hello,
Why in the OpenVPN log, I see the following line:
Protocol options: explicit-exit-notify 1, protocol-flags cc-exit tls-ekm
dyn-tls-crypt
Thank you.
Hello Jason,
Sorry to interfere, and sorry also if I look a bit harsh,
Le 14/08/2023 à 23:19, Jason Long a écrit :
Hi Bruno,
Thank you so much for your reply.
Both (Server and Client) can ping each other and without the local
statement my client can connect to the OpenVPN server.
My client connecting to the server via an internal network:
Hello,
Le 14/08/2023 à 15:59, Jason Long via Openvpn-users a écrit :
Hi,
Thank you so much.
But I am sure that in a real environment such a scenario can also exist.
Consider an internal network where users connect to an internal OpenVPN server
and this server has several NICs with different IP
Hi Selva, hi Gert,
Le 08/08/2023 à 19:07, Selva Nair a écrit :
Hi Bruno,
Another reason which incited me to continue using the "Connect"
client
was the fact that for rather old people not very accustomed to
VPNs and
the like (my "customers" are mostly retired people in
Le 07/08/2023 à 22:39, Selva Nair a écrit :
Hi,
Hi Gert, many thanks, everything's fine, the "block-outside-dns" option
works perfectly, but we'll have to use OpenVPN GUI only, as OpenVPN
Connect rejects this as an unknown option. Not a big deal, at least we
have a working
Le 07/08/2023 à 07:55, Gert Doering a écrit :
Besides that, Windows also likes to query *all* DNS servers, internal
and external, and use who answers first. So in a split DNS setup,
results can be inconsistent. There's an openvpn option for that
(windows only), "block-outside-dns"
Fine!
Hi Gert,
Le 07/08/2023 à 07:55, Gert Doering a écrit :
Hi,
On Mon, Aug 07, 2023 at 01:11:23AM +0200, Bruno Tréguier via Openvpn-users
wrote:
For a few Windows 11 client machines, however, things are a bit weird: when
connected to the VPN, everything is ok for internal servers, but for public
Hello dear OpenVPN users,
Sorry to bother, but I'm facing a rather strange problem, apparently
with some of my Windows 11 users.
We use a rather classical configuration similar to what is usually
called "split horizon DNS, but using 2 different servers:
- 1 public DNS server, on which only
12 matches
Mail list logo
