Messages

1

Installation and Upgrades / CLI exporting Users/Computers from 6.2 for use in version 7.x

« on: August 04, 2021, 08:49:58 pm »

Hi All,
Not sure when to find step by step docs on exporting and importing users and computers VIA CLI (version 6.2)  (docs a little vague)
Anyone have info or step by step CLI for this. (UI version just available for Commercial Server Edition) I would like to test 7.x with previous data.

thanks in advance.

2

Other modules / Firewall issue with DROPPED TCP to a proxmox server, seems no reason?

« on: December 31, 2020, 08:36:02 pm »

Hi All,
was finding this difficult to trace cause, thinking this was firewall issue
(It may have been able to be solved via a network config but I lack the info for such an endeavor.)
Setup:

proxmox (PVE1@ 192.168.1.2/24) (working fine for several months)
      VM Zentyal 6.3 VM (192.168.1.1/24)
      VM CenOS etc
      ...

Client (PC@ 192.168.1.116/32 DHCP via Zentyal, wont allow /24 not sure why that is)
...
Now installing additional Proxmox server to host further research VM's
Installation went fine.. (The new proxmox report its ready on the https://192.168.1.29:8006)

proxmox (PVE2@ 192.168.1.29/32)
issues:

I can ping Zentyal (192.168.1.1/32) from proxmox (PVE2@ 192.168.1.29/32)
I can ping proxmox (192.168.1.29/32) from zentyal (192.168.1.1/24)

I can not ping proxmox (192.168.1.29/32)  from client (192.168.1.116/32)
I can not ping proxmox (192.168.1.29/32)  from proxmox (192.168.1.2/24) (mask issue?)

thus the GUI to proxmox (192.168.1.29/32) from a client machine (192.168.1.116) does not come up.
Checking the log from the Zentyal firewall module reports ACCESS was dropped

2020-12-31 20:15:57  eth1  eth1   192.168.1.29    192.168.1.116   TCP  8006    51359    DROP
also
2020-12-31 20:15:57      eth1             192.168.1.1     192.168.1.116   TCP    8006    51359    DROP

As the firewall rules are open and at defaults the issue points to static address may be required for proxmox and
reserved in Zentyal.

*FIXED:

reinstalled proxmox with a IPaddress as static 192.168.1.7/24 (note the mask is not 32)

and reserved the address in Zentyal (DHCP Advanced and added the defined object)

I can now ping from the client  (192.168.1.116/32)  to (192.168.1.7/24)
and also ping from PVE1 to PVE2

Hopefully this is the correct method for this type of setup,
Help understanding why ZENTYAL dhcp wont work for this would be appreciated.

3

Other modules / Firewall "Filtering rules for traffic coming out from Zentyal", lockout

« on: May 16, 2020, 02:00:37 pm »

Versions 6.1

I played around with the "Filtering rules for traffic coming out from Zentyal " (stupid deny rule)
and locked myself out from the web interface.
These two CLI commands I found in the forum arn't working ( as the service does not exist):

Code: [Select]

sudo /etc/init.d/zentyal firewall stop
sudo /etc/init.d/service firewall stop
update found the needed CLI command to temporally stop the firewall

Code: [Select]

sudo zs firewall stopMade the appropriate changes in the WEB interface and now all is good with the world.
then restarted firewall

Code: [Select]

sudo zs firewall start
Thanks to all who where going to reply but I got there first.