Topics

1

Other modules / Multiple domains to same ip address

« on: October 31, 2018, 11:06:55 am »

Hello,
I have Zentyal Development Edition 5.1.
I need more DNS domains that link to same address IP.

The Zentyal domain is "bs.lan" and I need set some DNS, for example "gitea.bs.lan" and "site.com" to same ip address (192.168.1.6).

For "gitea.bs.lan" I doesn't have problems: I can add it as new Hostname of "bs.lan" domain of DNS section and set the IP address.
I don't know how to configure "site.com". If I add the new domain "site.com", then I cannot set the same IP address because I have the "The IP '192.168.1.6' is already in 'gitea.bs.lan'" message error.

Someone can help me?

Thanks,
Davide.

2

Other modules / Automatic mounting nfs shared folder

« on: October 23, 2018, 09:06:11 am »

Hello,
I searched everywhere but I didn't find the information I need.

I have Zentyal 5.1 and I would like to move the dovecot email path to NAS folder.

I need automatic mounting a NFS filesystem on Zentyal 5.1.
If I execute the manual mount with:

Code: [Select]

sudo mount -t nfs 192.168.1.2:/imap /var/vmailthe mount works correctly.

But if I insert in file "/etc/fstab" the row:

Code: [Select]

192.168.1.2:/imap /var/vmail nfs rsize=8192,wsize=8182,timeo=14,intrthe mount doesn't work.
Can you help me?

Thanks.
Davide.

Here I paste some parts of "journalctl.txt" file. I cannot attach the entire file because the Attach section doesn't work correctly.

Code: [Select]

......................

Oct 08 16:51:11 zentyal-mail systemd-journald[303]: Journal started
Oct 08 16:51:11 zentyal-mail systemd-udevd[322]: Network interface NamePolicy= disabled on kernel command line, ignoring.
Oct 08 16:51:11 zentyal-mail systemd[1]: Started Remount Root and Kernel File Systems.
Oct 08 16:51:11 zentyal-mail kernel: EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro,usrquota,grpquota,acl,user_xattr
Oct 08 16:51:11 zentyal-mail systemd[1]: Started LVM2 metadata daemon.
Oct 08 16:51:11 zentyal-mail systemd[1]: Starting Initial Check File System Quotas...
Oct 08 16:51:11 zentyal-mail systemd[1]: Starting Load/Save Random Seed...
Oct 08 16:51:11 zentyal-mail systemd[1]: Starting udev Coldplug all Devices...
Oct 08 16:51:11 zentyal-mail systemd[1]: Starting Flush Journal to Persistent Storage...
Oct 08 16:51:11 zentyal-mail kernel: RPC: Registered named UNIX socket transport module.
Oct 08 16:51:11 zentyal-mail kernel: RPC: Registered udp transport module.
Oct 08 16:51:11 zentyal-mail kernel: RPC: Registered tcp transport module.
Oct 08 16:51:11 zentyal-mail kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Oct 08 16:51:11 zentyal-mail systemd[1]: Mounted RPC Pipe File System.
Oct 08 16:51:11 zentyal-mail systemd[1]: Started udev Kernel Device Manager.
Oct 08 16:51:11 zentyal-mail systemd[1]: Started Nameserver information manager.
Oct 08 16:51:11 zentyal-mail systemd[1]: Started Load/Save Random Seed.
Oct 08 16:51:11 zentyal-mail systemd[1]: Reached target Network (Pre).
Oct 08 16:51:12 zentyal-mail loadkeys[306]: Loading /etc/console-setup/cached.kmap.gz
Oct 08 16:51:12 zentyal-mail systemd[1]: Started Set console keymap.
Oct 08 16:51:12 zentyal-mail systemd[1]: Started Flush Journal to Persistent Storage.
Oct 08 16:51:12 zentyal-mail systemd[1]: Started udev Coldplug all Devices.
Oct 08 16:51:12 zentyal-mail systemd[1]: Starting Show Plymouth Boot Screen...
Oct 08 16:51:12 zentyal-mail systemd[1]: Started Show Plymouth Boot Screen.
Oct 08 16:51:12 zentyal-mail systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Oct 08 16:51:12 zentyal-mail kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 08 16:51:12 zentyal-mail kernel: piix4_smbus 0000:00:01.3: SMBus Host Controller at 0x700, revision 0
Oct 08 16:51:12 zentyal-mail systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Oct 08 16:51:12 zentyal-mail systemd[1]: Started Initial Check File System Quotas.
Oct 08 16:51:12 zentyal-mail systemd[1]: Starting File System Quota Check...
Oct 08 16:51:12 zentyal-mail resolvconf[353]: invoke-rc.d: could not determine current runlevel
Oct 08 16:51:12 zentyal-mail systemd[1]: Started File System Quota Check.
Oct 08 16:51:12 zentyal-mail systemd[1]: Starting Enable File System Quotas...
Oct 08 16:51:12 zentyal-mail systemd[1]: Found device 82540EM Gigabit Ethernet Controller (QEMU Virtual Machine).
Oct 08 16:51:12 zentyal-mail systemd[1]: squid.service: Unit cannot be reloaded because it is inactive.
Oct 08 16:51:12 zentyal-mail resolvconf[353]: squid.service is not active, cannot reload.
Oct 08 16:51:12 zentyal-mail resolvconf[353]: invoke-rc.d: initscript squid, action "reload" failed.
Oct 08 16:51:12 zentyal-mail systemd[1]: Started Enable File System Quotas.
Oct 08 16:51:12 zentyal-mail systemd[1]: Received SIGRTMIN+20 from PID 420 (plymouthd).
Oct 08 16:51:12 zentyal-mail kernel: random: crng init done
Oct 08 16:51:12 zentyal-mail kernel: random: 7 urandom warning(s) missed due to ratelimiting
Oct 08 16:51:12 zentyal-mail lvm[305]:   2 logical volume(s) in volume group "zentyal51-vg" monitored
Oct 08 16:51:12 zentyal-mail systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Oct 08 16:51:12 zentyal-mail systemd[1]: Reached target Local File Systems (Pre).
Oct 08 16:51:13 zentyal-mail systemd[1]: Received SIGRTMIN+20 from PID 420 (plymouthd).
Oct 08 16:52:41 zentyal-mail systemd[1]: dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device: Job dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device/start timed out.
Oct 08 16:52:41 zentyal-mail systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device.
Oct 08 16:52:41 zentyal-mail systemd[1]: Dependency failed for /boot.
Oct 08 16:52:41 zentyal-mail systemd[1]: Dependency failed for Local File Systems.
Oct 08 16:52:41 zentyal-mail systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Oct 08 16:52:41 zentyal-mail systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Oct 08 16:52:41 zentyal-mail systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
Oct 08 16:52:41 zentyal-mail systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/61cece02-ff1e-4702-aecd-6092ea298a09.
Oct 08 16:52:41 zentyal-mail systemd[1]: systemd-fsck@dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.service: Job systemd-fsck@dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.service/start failed with result 'dependency'.
Oct 08 16:52:41 zentyal-mail systemd[1]: dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device: Job dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device/start failed with result 'timeout'.
Oct 08 16:52:41 zentyal-mail systemd[1]: dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device: Job dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device/start timed out.
Oct 08 16:52:41 zentyal-mail systemd[1]: Timed out waiting for device dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device.
Oct 08 16:52:41 zentyal-mail systemd[1]: Dependency failed for /dev/mapper/zentyal33--vg-swap_1.
Oct 08 16:52:41 zentyal-mail systemd[1]: Dependency failed for Swap.
Oct 08 16:52:41 zentyal-mail systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Oct 08 16:52:41 zentyal-mail systemd[1]: dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.swap: Job dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.swap/start failed with result 'dependency'.
Oct 08 16:52:41 zentyal-mail systemd[1]: dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device: Job dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device/start failed with result 'timeout'.
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting Preprocess NFS configuration...
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting Set console font and keymap...
Oct 08 16:52:41 zentyal-mail systemd[1]: Closed ACPID Listen Socket.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped target Graphical Interface.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Getty on tty1.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped target RPC Port Mapper.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped getty on tty2-tty6 if dbus and logind are not available.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped target Multi-User System.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped MySQL Community Server.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: Apache2 web server.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: start and stop the Quagga routing suite.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped System Logging Service.
Oct 08 16:52:41 zentyal-mail systemd[1]: Closed Syslog Socket.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Run anacron jobs.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Cgroup management proxy.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: Startup script for amavis snmp subagent.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped RPC Remote Quota Server.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped RPC bind portmap service.
Oct 08 16:52:41 zentyal-mail systemd[1]: Closed RPCbind Server Activation Socket.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Login Service.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: init-Script for system wide fetchmail daemon.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Zentyal LXDE Display Manager.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Zentyal start/stop task.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Advanced key-value store.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: Startup script for amavis master supervisor.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: Set the CPU Frequency Scaling governor to "ondemand".
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target Login Prompts.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped ACPI Events Check.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped memcached daemon.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: Start the GNUstep distributed object mapper.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped ISC DHCP IPv6 server.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Hold until boot process finishes up.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped /etc/rc.local Compatibility.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped LSB: Record successful boot for GRUB.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Daily apt upgrade and clean activities.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Daily apt download activities.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped OpenBSD Secure Shell server.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Cgroup management daemon.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Regular background program processing daemon.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Deferred execution scheduler.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Permit User Sessions.
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting Set console scheme...
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped OpenVPN service.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped D-Bus System Message Bus.
Oct 08 16:52:41 zentyal-mail systemd[1]: Closed D-Bus System Message Bus Socket.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped target Basic System.
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target Paths.
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target Sockets.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Oct 08 16:52:41 zentyal-mail systemd[1]: Stopped target System Initialization.
Oct 08 16:52:41 zentyal-mail systemd[1]: Started Emergency Shell.
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting Create Volatile Files and Directories...
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target Emergency Mode.
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting LSB: AppArmor initialization...
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target Timers.
Oct 08 16:52:41 zentyal-mail systemd[1]: Started Preprocess NFS configuration.
Oct 08 16:52:41 zentyal-mail systemd-tmpfiles[588]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting RPC security service for NFS client and server...
Oct 08 16:52:41 zentyal-mail systemd[1]: Started Create Volatile Files and Directories.
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target System Time Synchronized.
Oct 08 16:52:41 zentyal-mail systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Oct 08 16:52:41 zentyal-mail systemd[1]: Started Update UTMP about System Boot/Shutdown.
Oct 08 16:52:41 zentyal-mail systemd[1]: Started Set console scheme.
Oct 08 16:52:41 zentyal-mail systemd[1]: Starting Update UTMP about System Runlevel Changes...
Oct 08 16:52:41 zentyal-mail systemd[1]: Started Update UTMP about System Runlevel Changes.
Oct 08 16:52:41 zentyal-mail apparmor[589]:  * Starting AppArmor profiles
Oct 08 16:52:41 zentyal-mail systemd[1]: Started RPC security service for NFS client and server.
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target NFS client services.
Oct 08 16:52:41 zentyal-mail systemd[1]: Reached target Remote File Systems (Pre).
Oct 08 16:52:42 zentyal-mail apparmor[589]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Oct 08 16:52:42 zentyal-mail apparmor[589]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.clamd

......................


Oct 08 16:52:42 zentyal-mail systemd[1]: Started LSB: AppArmor initialization.
Oct 08 16:52:42 zentyal-mail systemd[1]: Started ifup for eth0.
Oct 08 16:52:42 zentyal-mail systemd[1]: Started ifup for eth1.
Oct 08 16:52:42 zentyal-mail systemd[1]: Starting Raise network interfaces...
Oct 08 16:52:42 zentyal-mail systemd[1]: Started Set console font and keymap.
Oct 08 16:52:42 zentyal-mail systemd[1]: Created slice system-getty.slice.
Oct 08 16:52:42 zentyal-mail kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Oct 08 16:52:42 zentyal-mail kernel: e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Oct 08 16:52:42 zentyal-mail ifup[725]: /sbin/ifup: waiting for lock on /run/network/ifstate.eth0
Oct 08 16:52:42 zentyal-mail ifup[725]: /sbin/ifup: waiting for lock on /run/network/ifstate.eth1
Oct 08 16:52:42 zentyal-mail systemd[1]: Started Raise network interfaces.
Oct 08 16:52:42 zentyal-mail systemd[1]: Reached target Network.
Oct 08 16:52:42 zentyal-mail systemd[1]: Reached target Network is Online.
Oct 08 16:52:42 zentyal-mail systemd[1]: Mounting /var/vmail...
Oct 08 16:52:42 zentyal-mail kernel: FS-Cache: Loaded
Oct 08 16:52:42 zentyal-mail kernel: FS-Cache: Netfs 'nfs' registered for caching
Oct 08 16:52:42 zentyal-mail kernel: NFS: Registering the id_resolver key type
Oct 08 16:52:42 zentyal-mail kernel: Key type id_resolver registered
Oct 08 16:52:42 zentyal-mail kernel: Key type id_legacy registered
Oct 08 16:52:42 zentyal-mail systemd[1]: Reached target Host and Network Name Lookups.
Oct 08 16:52:42 zentyal-mail systemd[1]: Stopped target Emergency Mode.
Oct 08 16:52:47 zentyal-mail systemd[1]: Stopped Emergency Shell.
Oct 08 16:54:12 zentyal-mail systemd[1]: dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device: Job dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device/start timed out.
Oct 08 16:54:12 zentyal-mail systemd[1]: Timed out waiting for device dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device.
Oct 08 16:54:12 zentyal-mail systemd[1]: Dependency failed for /dev/mapper/zentyal33--vg-swap_1.
Oct 08 16:54:12 zentyal-mail systemd[1]: Dependency failed for Swap.
Oct 08 16:54:12 zentyal-mail systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Oct 08 16:54:12 zentyal-mail systemd[1]: dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.swap: Job dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.swap/start failed with result 'dependency'.
Oct 08 16:54:12 zentyal-mail systemd[1]: dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device: Job dev-mapper-zentyal33\x2d\x2dvg\x2dswap_1.device/start failed with result 'timeout'.
Oct 08 16:54:12 zentyal-mail systemd[1]: dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device: Job dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device/start timed out.
Oct 08 16:54:12 zentyal-mail systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device.
Oct 08 16:54:12 zentyal-mail mount[950]: Job for rpc-statd.service canceled.
Oct 08 16:54:12 zentyal-mail systemd[1]: Dependency failed for /boot.
Oct 08 16:54:12 zentyal-mail systemd[1]: Dependency failed for Local File Systems.
Oct 08 16:54:12 zentyal-mail systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Oct 08 16:54:12 zentyal-mail systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Oct 08 16:54:12 zentyal-mail systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
Oct 08 16:54:12 zentyal-mail systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/61cece02-ff1e-4702-aecd-6092ea298a09.
Oct 08 16:54:12 zentyal-mail systemd[1]: systemd-fsck@dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.service: Job systemd-fsck@dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.service/start failed with result 'dependency'.
Oct 08 16:54:12 zentyal-mail systemd[1]: dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device: Job dev-disk-by\x2duuid-61cece02\x2dff1e\x2d4702\x2daecd\x2d6092ea298a09.device/start failed with result 'timeout'.
Oct 08 16:54:12 zentyal-mail systemd[1]: var-vmail.mount: Mounting timed out. Stopping.
Oct 08 16:54:12 zentyal-mail systemd[1]: Mounted /var/vmail.
Oct 08 16:54:12 zentyal-mail systemd[1]: Reached target Remote File Systems.
Oct 08 16:54:12 zentyal-mail systemd[1]: Starting Notify NFS peers of a restart...
Oct 08 16:54:12 zentyal-mail systemd[1]: Stopped NFS status monitor for NFSv2/3 locking..
Oct 08 16:54:12 zentyal-mail systemd[1]: Closed RPCbind Server Activation Socket.
Oct 08 16:54:12 zentyal-mail systemd[1]: Stopped target System Initialization.
Oct 08 16:54:12 zentyal-mail systemd[1]: Started Emergency Shell.
Oct 08 16:54:12 zentyal-mail systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Oct 08 16:54:12 zentyal-mail systemd[1]: Reached target Emergency Mode.
Oct 08 16:54:12 zentyal-mail sm-notify[987]: Version 1.2.8 starting
Oct 08 16:54:12 zentyal-mail systemd[1]: Started Notify NFS peers of a restart.
Oct 08 16:54:12 zentyal-mail systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Oct 08 16:54:12 zentyal-mail systemd[1]: Startup finished in 1.952s (kernel) + 3min 718ms (userspace) = 3min 2.671s.
Oct 08 16:54:12 zentyal-mail systemd[1]: Received SIGRTMIN+21 from PID 420 (plymouthd).


3

Installation and Upgrades / Filter users access by IP address

« on: July 03, 2014, 04:09:52 pm »

Hello,
 the image show the current  configuration of our corporate LAN network.
 The LAN is divided into two sub-networks: 192.168.1.* and 192.168.2.*. Each computer is connected to both the QNAP NAS TS-469L (through its two network cards 192.168.1.2 and 192.168.2.2) and to a pc with Zentyal server (through its two network cards 192.168.1.1 and 192.168.2.1).
 User accounts are managed by Zentyal LDAP server, the permissions on the NAS are taken by users list on Zentyal LDAP server.
 Users of the two sub-networks belong to two different LDAP groups.
 
 The question is: can we define a list of users who have access to the NAS when connected to the sub-net 192.168.1.* and a list of users who have access only when connected instead to the sub-net 192.168.2.* ?
 
 A user can authenticate itself on any PC on the corporate LAN, but if you authenticate on the PC in the sub-network is not within its competence, should not be able to access the NAS (no resources in the NAS). Example: if the "user 2" is authenticated on the "user 3" PC, he must be inhibited access to shared resources by the NAS.
 
 We have already asked on the QNAP forum but they said that is not possible because of the specific protocol TCP/IP.
 It's possible to do this with a specific configuration of LDAP on the Zentyal server?
 
 Thank you.

-----------------------------------------------------------------------------------------------------------------


Ciao,
 l'immagine indica l'attuale situazione della connessione dei PC aziendali.
 La LAN è divisa in due parti fisicamente sconnesse ognuna facente parte di una specifica sotto-rete: 192.168.1.* e 192.168.2.*. Ogni computer è collegato sia al NAS QNAP TS-469L (attraverso le sue due schede di rete 192.168.1.2 e 192.168.2.2) che al server Zentyal (attraverso le sue due schede di rete 192.168.1.1 e 192.168.2.1).
 Gli account utente sono gestiti tramite LDAP del server Zentyal, le autorizzazioni sul NAS cono prelevate dagli utenti LDAP del server Zentyal.
 Gli utenti delle due sotto-reti fanno parte di due gruppi LDAP diversi.
 
 La domanda è: possiamo definire una lista di utenti che ha accesso al NAS quando connessi alla sotto-rete 192.168.1.* e una lista di utenti che hanno invece accesso solo quando connessi alla sotto-rete 192.168.2.* ?
 
 Un utente può autenticarsi su qualsiasi PC della LAN aziendale, però se si autentica sui PC della sotto-rete non di sua competenza, non deve poter accedere al NAS (a nessuna risorsa del NAS).
 
 
 Abbiamo già chiesto sul forum QNAP ma ci hanno risposto che non è possibile per via delle specifiche del protocollo tcp/ip.
 E' possibile ottenere ciò con una specifica configurazione sul server Zentyal?
 
 Grazie.