92.168.50.10/32 via his unique connection.
Thanks
Richard
--
LinuxCabal Asociación Civil
Ing. Richard Couture
Novell CNE, ECNE, MCNE
HP/Compaq ASE
Cel.: (+52) 333 377-7505
Web: http://www.LinuxCabal.org
E-Mail: r...@linuxcabal.org
Hosted en la nube Cloud Sigma - www.CloudSigma.com
How do I get rid of these warnings?
I have not declared link-mtu in either server of client conf
I have not declared auth in either client or server
I have not declared keysize in either client or server
Is script-security 2 relevant in 2.5x?
inconsistently, local='link-mtu 1549', remote='lin
ipv4 forwarding is and has been enabled on both server and client
Richard
On 31/12/23 04:03, Gert Doering wrote:
hi,
On Sat, Dec 30, 2023 at 04:06:44PM -0600, Richard Couture wrote:
The original server from which I took all of these initial settings was and
still is working perfectly.
I am
On 30/12/2023 21:35, Richard Couture wrote:
Things look good but I can NOT reach the desired net 192.168.51.0/24
via the VPN
First of all, I'd like to say that here we are moving from problem to
problem and they are all being *addressed* one by one :-)
You started with easy-rsa and now
ent
# plugin /usr/lib/openvpn/openvpn-auth-pam.so "login login USERNAME
password PASSWORD"
# plugin /usr/lib/openvpn/openvpn-auth-pam.so system-auth
# plugin /usr/lib64/openvpn/plugins/openvpn-plugin-auth-pam.so "login
login USERNAME password PASSWORD"
#plugin /usr/lib64/openvpn
ut hte server is pushing some
p2p-like parameters, which does not make sense.
However, I cannot see the problem in the config you posted.
Does the client have a CCD file with IP specific directive in it?
If yes, please post them.
Regards.
On 29/12/2023 23:26, Richard Couture wrote:
I DO a
I DO and DID have keepalive 10 120 in the server.conf
betweentopology subnet and maxclients 50
Richard
On 12/29/23 16:05, tincantech wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On Friday, 29 December 2023 at 20:29, Richard Couture
wrote:
I have totally reinitialized
scope link
valid_lft forever preferred_lft forever
12: tun0: mtu 1500 qdisc
fq_codel state UNKNOWN group default qlen 500
link/none
inet 10.34.0.1/24 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::8723:a327:57ee:193a/64 scope link stable-privacy
8efRb0d2
-END CERTIFICATE-
Richard
On 12/28/23 15:10, Antonio Quartulli wrote:
Hi,
On 28/12/2023 21:15, Richard Couture wrote:
the following is the actual reason for clients to not be able to connect:
2023-12-28 14:01:01 187.251.133.221:1194 VERIFY ERROR: depth=0,
error=CRL s
2.5 and
reference to any tricks that might be needed is greatly appreciated
I only have 5 users who will be connecting to IBM SAP via the vpn
Thanks much
Richard
--
LinuxCabal Asociación Civil
Ing. Richard Couture
Novell CNE, ECNE, MCNE
HP/Compaq ASE
Cel.: (+52) 333 377-7505
Web: h
10 matches
Mail list logo
