Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - pete83

Pages: [1]
1
I had a fine working vpn.
This morning I had to reboot our zentyal server, after the system came up again the vpn client could connect but they can't ping any systems in our advertised network.

Can someone please help me, here are my config files. Please let me know if more info is needed.

/etc/openvpn/openvpn.conf
Code: [Select]
# EBox OpenVPN 2.0 config file for  server zentyal01

# Which local IP address should OpenVPN
# listen on? (optional)

local 192.168.100.19

# Which TCP/UDP port should OpenVPN listen on?

port 1194

# TCP or UDP server?

proto udp

# virtual device

dev tap0

# SSL/TLS root certificate (ca), certificate

# (cert), and private key (key).

ca '/var/lib/ebox/CA/cacert.pem'

cert '/var/lib/ebox/CA/certs/D35979196B6CBFF6.pem'

key '/var/lib/ebox/CA/private/zentyal01.pem'
 # This file should be kept secret

# check peer certificate against certificate revokation list

crl-verify /var/lib/ebox/CA/crl/latest.pem


# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
#dh /etc/openvpn/dh1024.pem

dh /etc/openvpn/ebox-dh1024.pem


# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
server 10.10.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.
ifconfig-pool-persist '/etc/openvpn/zentyal01-ipp.txt'


# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN
;push "redirect-gateway"

# Uncomment this directive to allow different
# clients to be able to "see" each other.

client-to-client


# The keepalive directive causes ping-like
# messages to be sent back and forth over
keepalive 10 120


# client certificate common name authentication



# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
;tls-auth ta.key 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# group and user for the OpenVPN
# daemon's privileges after initialization.

user nobody


group nogroup


# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status '/var/log/ebox/openvpn/status-zentyal01.log'

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
log-append  '/var/log/ebox/openvpn/zentyal01.log'

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 5

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

   push "route 192.168.0.0 255.255.0.0"


client.conf

Code: [Select]
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server.     #
#                                            #
# This configuration can be used by multiple #
# clients, however each client should have   #
# its own cert and key files.                #
#                                            #
# On Windows, you might want to rename this  #
# file so it has a .ovpn extension           #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
dev tap

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one.  On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.

# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote  195.XX.XX.XX 1194

# Choose a random host from the remote
# list for load-balancing.  Otherwise
# try hosts in the order specified.
remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server.  Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind


# Comment out user and group if you wish to increase security. Be advised you
# can experience some issues when reconnecting
# user nobody
# the group option may be wrong for some distributions
# normally distributions use wether 'nobody' (Fedora) or 'nogroup'
# for the no-priviligies group name
# group nogroup


# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here.  See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets.  Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description.  It's best to use
# a separate .crt/.key file pair
# for each client.  A single ca
# file can be used for all clients.
ca   "XXXX.pem"
cert "XXXXXXX.pem"
key  "XXXXXX.pem"

# Verify server certificate by common name
tls-remote zentyal01


# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server".  This is an
# important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server".  The build-key-server
# script in the easy-rsa folder will do this.
;ns-cert-type server

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Explicitly notify disconnections
explicit-exit-notify 3

# Silence repeating messages
;mute 20


ip route:


2
Installation and Upgrades / File locking issue samba
« on: February 23, 2012, 10:53:52 am »
I'm using zentyal 2.1 and my users have problems with saving MS Office files on the samba shares:

This is a example of the problem we also have, which I found here:

If a user opens an existing file, smbstatus looks like this:

Code: [Select]
10781        11021      DENY_WRITE 0x2019f     RDWR       NONE
 /usr/test/dssg   test1234ecg2.pptx   Fri Oct 23 17:21:52 2009
10517        11021      DENY_NONE  0x100001    RDONLY     NONE
 /usr/test/dssg   .   Fri Oct 23 17:06:08 2009
10517        11021      DENY_NONE  0x100001    RDONLY     NONE
 /usr/test/dssg   .   Fri Oct 23 17:06:08 2009
10781        11021      DENY_NONE  0x100001    RDONLY     NONE
 /usr/test/dssg   .   Fri Oct 23 17:16:19 2009
10781        11021      DENY_NONE  0x100001    RDONLY     NONE
 /usr/test/dssg   .   Fri Oct 23 17:16:19 2009
10781        11021      DENY_WRITE 0x3019f     RDWR       EXCLUSIVE+BATCH
 /usr/test/dssg   ~$test1234ecg2.pptx   Fri Oct 23 17:21:52 2009

Notice, there are both test1234ecg2.pptx and ~$test1234ecg2.pptx.

If the user saves, once in awhile (some as often as 1 in 4, some more like 1 in 20 saves), they'll be told that the file is read-only and get offered to save as a new file name. When this happens, smbstatus only shows the ~$test1234ecg2.pptx version of the file.

Is there someone with similar problems?



3
I've enabled password expiry and my users have to change their password every 90 days. The users who logon through windows clients can change their passwords without a problem.

However there are also a few users that use Linux clients and they can't connect to the samba shares any more due to their expired password. When they change their password in the "User corner" the samba log still says that the password is expired. Even when I as administrator change the password for the user in the Zentyal control panel it won't work and keeps saying that the password is expired.

Is there someone who has the same problem? Or is there someone that can help me?

4
Dutch / VPN achter een proxy server
« on: June 24, 2011, 04:53:15 pm »
Ik zie dat er nog weinig Nederlandse posts geplaatst zijn daarom probeer ik het maar.

Wij willen graag een VPN oplossing voor onze medewerkers om thuis toegang te krijgen tot netwerk shares (die ook binnen zentyal gedefinieerd zijn), ssh toegang naar systemen binnen het bedrijfsnetwerk en internettoegang vanaf het bedrijfsnetwerk.

Mijn vraag is, wat is de beste opstelling wanneer het bedrijfsnetwerk zich bevindt op 192.168.0.0 met subnet 255.255.0.0. De werkstations en servers hebben als gateway 192.168.100.1, dit is een proxy server waar tevens een shorewall firewall op draait.

De zentyal server heeft als ip 192.168.100.19 op eth0 er zit nog een tweede netwerkkaart in de server eth1.

Bedrijfsnetwerk: 192.168.0.0/16
Gateway:           192.168.100.1
zentyal-server:   192.168.100.19 (eth0)

Ik ben al een hele tijd aan het stoeien en zie nu door de bomen het bos even niet meer vandaar zou ik graag input krijgen van iemand van jullie hoe jullie dit zouden aanpakken zonder dat ik meteen aangeef wat ik al geprobeerd heb. Wat ik wel wil aangeven is dat ik probeer de vpn server te draaien over 1 interface (eth0) omdat ik liever geen subnet aanpas voor het lokale netwerk.

Ben benieuwd of iemand me een eindje op weg kan helpen.




Pages: [1]