Messages

1

French / Disque saturé par Squid

« on: July 08, 2014, 08:17:47 am »

Salut,

J'ai une passerelle sous zentyal dont le disque est saturé par le proxy squid qui enregistre le trafique dans des DB mysql.

Le dossier /var/lib/mysql/zentyal contient les fichiers suivants :

squid_traffic_hourly.MYD
squid_traffic_daily.MYD
squid_traffic_weekly.MYD
squid_traffic_monthly.MYD

Je n'ai plus accès à l'interface d'administration mais je peux m'y connecter via ssh.

Quelqu'un pourrait m'aider pour

• soit me renseigner une commande qui force squid à purger son historique?
• soit me dire comment me connecter directement à mysql pour purger les tables incriminées?
• soit me donner une autre piste?

Merci 

2

Installation and Upgrades / Re: Lan -> Wan -> Lan

« on: April 02, 2013, 09:27:04 pm »

In order to reach your server from the LAN using external domain name, you do have to maintain, in the internal DNS (the Zentyal one), zone for domain.ext pointing to the internal IP, that's as simple as this

Thank you christian, this was the right angle
So to have this working (cf. first post message)...

As a sample (replace with your own ips and names) :
WAN DNS for domain.ext : some registrar dns (I do not handle DNS localy)
WAN A record for server.domain.ext : 1.2.3.4

Primary Domain Controler and Exchange server
Ms SBS 2003 PDC (lan) : 192.168.0.2
LAN IP : 192.168.0.2
DNS : 192.168.0.2 (so selfish is he  )
Forwarder : 192.168.0.1 (the zentyal gateway)
Be sure to clear the cache for the local DNS if you do it "on the air"
Exchange server 2003 running on port : 443
I want to reach it on server.domain.ext BOTH from wan and lan.

Gateway
Zentyal Community Edition 3.0.17
LAN IP : 192.168.0.1
WAN IP : 1.2.3.4
System > General > Hostname (zentyal), Domain (domain.local), Admin TCP port (443)
Network > DNS > 127.0.0.1, FAI dns 1, FAI dns 2
Network > Objects > your-group-name > zentyal with ip 192.168.0.1/32
Firewall > Port Forwarding > Interface (wan), Original Destination (zentyal), Protocol (tcp), Or. Dest. Port (443), Source (any), Dest. IP (192.168.0.2), Repl. Src. Add. (yes)
DNS > Domains > I did the following :

• added server.domain.ext
• validate
• under Domain IP Addresses, I removed the automatically added IPs and set an IP to 192.168.0.2 (the exchange/pdc lan IP)
• saved

And ... tadaaam  !

To be sure
You can test it from a lan machine configured to use 192.16.0.2 as a DNS with nslookup :

Code: [Select]

nslookup server.domain.extGives you 192.168.0.2

Code: [Select]

nslookup server.domain.ext 8.8.8.8Gives you 1.2.3.4, 8.8.8.8 are some Google dns

From the LAN and WAN I was able to reach server.domain.ext with IP 192.168.0.2 (from the lan) and 1.2.3.4 (from the wan).
This is useful for mobile devices which does not have VPN access and that connects from mobile network (out of office) and from wireless (in the office).

Correct me if you think this was stupid or if I've made a mistake.

Thanks again.
Regards

3

Installation and Upgrades / Re: Lan -> Wan -> Lan

« on: April 02, 2013, 05:10:19 pm »

It's not possible to have the port for Zentyal-Backen the same as https-Port for web-Services. Change the port-Nr for the Zentyal-backend and it should work.

Thanks for the idea koecse I tried already ... but it does not works.
I set the Zentyal Admin 443 to 10443 and if I try to reach server.domain.ext:443 for the LAN, I just have a timeout.
I still be able to access server.domain.ext:443 from the WAN.

I think this is something about IP/NAT, iptables or?? But I'm not good enough with IP/NAT/Routing ...
Any other idea?
Regards

4

Installation and Upgrades / Lan -> Wan -> Lan

« on: April 02, 2013, 04:45:24 pm »

Hello,

Situation (as a sample):

Server : server.domain.ext (ip = 12.34.56.78)

zentyal.wan : 12.34.56.78
zentyal.lan: 192.168.0.1
server.lan: 192.168.0.2

I've configured the port forwarding to zentyal.wan:443 to server.lan:443 and it is working from the WAN.

From the LAN, if I go to https://server.domain.ext ... I reach the Zentyal web interface instead of server.lan:443 
From the WAN, if I go to https://server.domain.ext ... I reach the right server on port 443 

Can somebody help me to be able to reach server.domain.ext:443 from the LAN and still being able to access zentyal.lan:443

I hope that what I ask is understandable 

Thanks for your help,
Regards

5

Installation and Upgrades / Re: Zentyal: NO NETWORK TO KVM VIRTUAL MACHNES POSSIBLE AT all

« on: February 08, 2012, 09:31:57 am »

Hello,

I've a Zentyal 2.2.5 freshly installed with the Virtual Manager module and I cannot use network on the virtual machines.
The NAT, Bridged or Internal are "Bridged to no interface".  I see this in the web admin tool of zentyal.  The column "Bridged to" is always filed with the value "none".

For instance if I chose "Bridge Type" the "Bridge To" drop down list is empty.  There is only "none" in the list and if I apply this selection I have this error in the zentyal.log.

Exit value: 1
2012/02/08 09:21:37 ERROR> GlobalImpl.pm:612 EBox::GlobalImpl::__ANON__ - Failed to save changes in module virt: root command /var/lib/zentyal/machines/Bonjour/manage.sh start failed.
Error output: error: Failed to create domain from /var/lib/zentyal/machines/Bonjour/domain.xml
 error: Failed to add tap interface to bridge 'none': No such device

If I chose "NAT", I do not have the error message but my virtual machine have no network interface.

What can I do to "add an interface into the drop down list of the virtual manager"? Sorry but I'm quite a noob.
The network is working on the zentyal host and there are 2 Ethernet controller: Broadcom Corporation NetXtreme BCM5714 Gigabit Ethernet (rev a3).  I use only one.

Thanks for any advises, clues, or whateveri