diff --git a/agoss b/agoss
new file mode 100755
index 0000000..dfd1264
--- /dev/null
+++ b/agoss
@@ -0,0 +1,10 @@
+#!/bin/bash
+HOST=$(hostname)
+FHOST=$(pwd)/goss/$HOST
+if [ -r "$FHOST".yaml ] ; then
+ goss -gossfile "$FHOST".yaml v --no-color
+else
+ echo $0 : erreur lecture fichier "$FHOST".yaml
+ exit 1
+fi
+
diff --git a/changelog b/changelog
new file mode 100644
index 0000000..6bf1759
--- /dev/null
+++ b/changelog
@@ -0,0 +1,7 @@
+v5.0.2.j : 2019-01-25 -kb
+ ejout role s-nas-cliet et s-nas-server
+v5.0.1 : 2019-01-24 - ps
+ reorganisation : anciens playbooks et roles deplaces dans repertoire old
+v3.2.0 : 2017-11-16 - ps
+ ajout changelog
+
diff --git a/doc/Docker-openvas.txt b/doc/Docker-openvas.txt
new file mode 100644
index 0000000..92d4638
--- /dev/null
+++ b/doc/Docker-openvas.txt
@@ -0,0 +1,38 @@
+Fichier de documentation fait par Adnan Baljic, le 31/01/2019
+
+Configuration machine:
+Système: Carte Mère: Mémoire Vive: 2048
+Stockage: Contrôleur SATA: Ajouter un disque dur VDI de 8Go
+Réseau 1: n-adm
+Réseau 2: n-infra
+USB: Décocher "Activer le contrôleur USB"
+
+Important: Avant exécution du playbook, veillez à ne pas oublier de créer une partition sur /dev/sdb:
+-fdisk /dev/sdb
+-o
+-n
+-p
+-1
+-w
+
+La configuration de docker se fait automatiquement via le playbook s-docker.yml
+De base, s-docker.yml installera seulement docker-openvas-ab. Cependant, vous pouvez aussi installer docker-iredmail-ab en décommentant sa ligne et en
+commentant la ligne docker-openvas-ab. (Tous les 2 sont accessible depuis le port 443, si les 2 sont installés en même temps, il pourrait y avoir conflit.
+
+Manipulation à faire pour la mise en place d'Openvas via Docker:
+Après exécution de gsbboot et du pull-config, il faudra redémarrer la machine (prise en compte des modifications telles que
+les interfaces...) et exécuter la commande ci-dessous:
+docker run -d -p 443:443 -e PUBLIC_HOSTNAME=172.16.0.19 --name openvas mikesplain/openvas
+
+Manipulation à faire pour la mise en place d'Openvas via Docker:
+Après exécution de gsbboot et du pull-config, il faudra redémarrer la machine (prise en compte des modifications telles que
+les interfaces...) et exécuter la commande ci-dessous:
+docker run -d -p 443:443 -e PUBLIC_HOSTNAME=172.16.0.19 --name openvas lejmr/iredmail
+
+Ensuite, il faudra faire: "docker start nom_du_container" pour le démarrer.
+L'accès au container se fait via une machine virtuelle windows 7 avec Mozilla Firefox à jour, via https://172.16.0.19:443.
+
+Le changement du système de fichier de /dev/sdb1 et le montage sur /var/lib/docker se fera automatiquement via le playbook.
+
+Les tests effectués:
+Jeudi 31 janvier 2019, 15:38 par Adnan Baljic= TEST OpenVAS OK
\ No newline at end of file
diff --git a/doc/icinga.txt b/doc/icinga.txt
new file mode 100644
index 0000000..a9457f7
--- /dev/null
+++ b/doc/icinga.txt
@@ -0,0 +1,3 @@
+Roles fait par Adnan Baljic, le 17/01/2019
+Installation de icinga, nagios3-plugins, copie des fichiers de configuration vers /etc/icinga/ (=commands.cfg, hostgroups.cfg)
+et /etc/icinga/objects/ (=namevm.cfg, services_icinga.cfg, contacts_icinga.cfg)
\ No newline at end of file
diff --git a/doc/pics/e4-SAN-V2.dia b/doc/pics/e4-SAN-V2.dia
new file mode 100644
index 0000000..b163443
Binary files /dev/null and b/doc/pics/e4-SAN-V2.dia differ
diff --git a/doc/pics/e4-adm.dia b/doc/pics/e4-adm.dia
new file mode 100644
index 0000000..198cfe5
Binary files /dev/null and b/doc/pics/e4-adm.dia differ
diff --git a/doc/pics/e4-adm.png b/doc/pics/e4-adm.png
new file mode 100644
index 0000000..a7937af
Binary files /dev/null and b/doc/pics/e4-adm.png differ
diff --git a/doc/pics/e4-agence.dia b/doc/pics/e4-agence.dia
new file mode 100644
index 0000000..1513680
Binary files /dev/null and b/doc/pics/e4-agence.dia differ
diff --git a/doc/pics/e4-agence.png b/doc/pics/e4-agence.png
new file mode 100644
index 0000000..9f8b6a1
Binary files /dev/null and b/doc/pics/e4-agence.png differ
diff --git a/doc/pics/e4-dmz-ab.png b/doc/pics/e4-dmz-ab.png
new file mode 100644
index 0000000..cd5a539
Binary files /dev/null and b/doc/pics/e4-dmz-ab.png differ
diff --git a/doc/pics/e4-dmz-ha.dia b/doc/pics/e4-dmz-ha.dia
new file mode 100644
index 0000000..35dcb4a
Binary files /dev/null and b/doc/pics/e4-dmz-ha.dia differ
diff --git a/doc/pics/e4-dmz-ha.png b/doc/pics/e4-dmz-ha.png
new file mode 100644
index 0000000..ce3d64d
Binary files /dev/null and b/doc/pics/e4-dmz-ha.png differ
diff --git a/doc/pics/e4-dmz-old.png b/doc/pics/e4-dmz-old.png
new file mode 100644
index 0000000..d9a8940
Binary files /dev/null and b/doc/pics/e4-dmz-old.png differ
diff --git a/doc/pics/e4-dmz.dia b/doc/pics/e4-dmz.dia
new file mode 100644
index 0000000..480f6dd
Binary files /dev/null and b/doc/pics/e4-dmz.dia differ
diff --git a/doc/pics/e4-dmz.png b/doc/pics/e4-dmz.png
new file mode 100644
index 0000000..80f542c
Binary files /dev/null and b/doc/pics/e4-dmz.png differ
diff --git a/doc/pics/e4-v2.3.dia b/doc/pics/e4-v2.3.dia
new file mode 100644
index 0000000..1850c57
Binary files /dev/null and b/doc/pics/e4-v2.3.dia differ
diff --git a/doc/pics/e4-v2.3.png b/doc/pics/e4-v2.3.png
new file mode 100644
index 0000000..5bec9ce
Binary files /dev/null and b/doc/pics/e4-v2.3.png differ
diff --git a/doc/pics/e4-v2.3x.dia b/doc/pics/e4-v2.3x.dia
new file mode 100644
index 0000000..fe64d5c
Binary files /dev/null and b/doc/pics/e4-v2.3x.dia differ
diff --git a/doc/pics/e4-v2.dia b/doc/pics/e4-v2.dia
new file mode 100644
index 0000000..8dc3c40
Binary files /dev/null and b/doc/pics/e4-v2.dia differ
diff --git a/doc/pics/e4-vpn-infra-v1.2.dia b/doc/pics/e4-vpn-infra-v1.2.dia
new file mode 100644
index 0000000..7c7c70c
Binary files /dev/null and b/doc/pics/e4-vpn-infra-v1.2.dia differ
diff --git a/doc/pics/e4-vpn-infra-v1.2.png b/doc/pics/e4-vpn-infra-v1.2.png
new file mode 100644
index 0000000..db97574
Binary files /dev/null and b/doc/pics/e4-vpn-infra-v1.2.png differ
diff --git a/doc/pics/e4-vpn-infra.dia b/doc/pics/e4-vpn-infra.dia
new file mode 100644
index 0000000..a61f87f
Binary files /dev/null and b/doc/pics/e4-vpn-infra.dia differ
diff --git a/doc/pics/e4.dia b/doc/pics/e4.dia
new file mode 100644
index 0000000..8dc3c40
Binary files /dev/null and b/doc/pics/e4.dia differ
diff --git a/doc/pics/e4.png b/doc/pics/e4.png
new file mode 100644
index 0000000..64603db
Binary files /dev/null and b/doc/pics/e4.png differ
diff --git a/doc/r-vp.txt b/doc/r-vp.txt
new file mode 100644
index 0000000..bf1c939
--- /dev/null
+++ b/doc/r-vp.txt
@@ -0,0 +1,23 @@
+Fichier de documentation fait par Adnan Baljic, le 24/01/2019
+
+Manipulation à faire pour la mise en place de r-vp1 et r-vp2:
+Après exécution de gsbboot et du pull-config, il faudra désactiver l'interface
+de n-adm pour éviter une boucle. Pour cela, il suffit de faire "ifdown enp0sx"
+
+Pour ce qui est des tests pour vérifier que l'agence passe bien par le tunnel
+chiffré, vous pouvez stopper le service ipsec ou strongswan ("service
+strongswan stop" ou "service ipsec stop", cela revient à faire la même chose)
+
+Important: sur r-vp2, si la route par défaut est celui de s-adm, veuillez
+supprimer cette route en faisant "route del default" sinon l'agence ne passera
+pas par le tunnel chiffré mais vers s-adm
+cf. Schéma GSB/E4 - VPN/Infra - Version 1.2 - 2019-01-23
+
+La mise en place de strongswan via les certificats se fait via le playbook
+r-vpx-x509.yml. La manipulation ci-dessus n'est pas à faire pour les vpn avec
+certificat si r-vp2-x509 et r-vp1-x509 n'ont pas de route par défaut. Si ils ont
+une route par défaut, veuillez effectuer la même manipulation que pour r-vp2.
+Il faudra tout de même désactiver l'interface de n-adm sur les 2 r-vpx-x509.
+
+Les tests effectués:
+Jeudi 24 janvier 2019, 14:45 par Adnan Baljic= TEST OK
\ No newline at end of file
diff --git a/doc/s-fog.txt b/doc/s-fog.txt
new file mode 100644
index 0000000..a4eff88
--- /dev/null
+++ b/doc/s-fog.txt
@@ -0,0 +1,11 @@
+fichier de documentation réalier par Olivier Soares et Gaetan Maillard, le 25/01/2019
+
+Pour mettre en oeuvre le serveur fog, il faut déployer une machine virtuel debian (une ova), de la mettre à jour, de la renommer (s-fog), puis de récupérer gsbboot et faire un bash pull-config.
+
+Après avoir avoir fait l'installation de base, il suffit d'éxécuter le playbook "s-fog.yml" avec la commande ansible-playbooks -i hosts s-fog.yml". Ce playbook va récupérer le fichier d'installation de fog, le décompacter et configurer les différentes cartes réseaux de s-fog sachant qu'il y en a trois:
+
+L'interface enp0s3 permet d'avoir accès internet via le réseau "n-adm"
+L'interface enp0s8 permet de communiquer avec le réseau "n-infra"
+L'interface enp0s9 permet d'avoir accès et deployer des postes sur le réseau "n-user"
+
+Maintenant le serveur fog est prêt à être installer, avant de commencer l'installation il faut tout d'abord vérifier que l'accès à tous les réseaux soit correcte. Pour ça il suffit d'éxécuter le fichier de test goss
diff --git a/goss/r-ext.yaml b/goss/r-ext.yaml
new file mode 100644
index 0000000..1c3d20e
--- /dev/null
+++ b/goss/r-ext.yaml
@@ -0,0 +1,42 @@
+command:
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+ ping -c 4 172.16.0.1:
+ exit-status: 0
+ stdout:
+ - 0% packet loss
+ stderr: []
+ timeout: 10000
+ ping -c 4 172.16.0.254:
+ exit-status: 0
+ stdout:
+ - 0% packet loss
+ stderr: []
+ timeout: 10000
+ ping -c 4 192.168.200.254:
+ exit-status: 0
+ stdout:
+ - 0% packet loss
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.13/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.100.254/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.0.36/24
+ enp0s16:
+ exists: true
+ addrs:
+ - 192.168.200.253/24
diff --git a/goss/r-int.yaml b/goss/r-int.yaml
new file mode 100644
index 0000000..7726a62
--- /dev/null
+++ b/goss/r-int.yaml
@@ -0,0 +1,35 @@
+package:
+ isc-dhcp-server:
+ installed: true
+service:
+ isc-dhcp-server:
+ enabled: true
+ running: true
+command:
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.12/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.200.254/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 172.16.65.254/24
+ enp0s10:
+ exists: true
+ addrs:
+ - 172.16.64.254/24
+ enp0s16:
+ exists: true
+ addrs:
+ - 172.16.0.254/24
diff --git a/goss/r-vp1-cs.yaml b/goss/r-vp1-cs.yaml
new file mode 100644
index 0000000..916495d
--- /dev/null
+++ b/goss/r-vp1-cs.yaml
@@ -0,0 +1,106 @@
+file:
+ /etc/ipsec.d/cacerts/strongswanCert.pem:
+ exists: true
+ mode: "0644"
+ size: 1834
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp1Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp2Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp1Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1675
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp2Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1679
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+package:
+ strongswan:
+ installed: true
+ versions:
+ - 5.2.1-6+deb8u2
+service:
+ strongswan:
+ enabled: true
+ running: true
+user:
+ strongswan:
+ exists: true
+ uid: 112
+ gid: 65534
+ groups:
+ - nogroup
+ home: /var/lib/strongswan
+ shell: /usr/sbin/nologin
+command:
+ Associations:
+ exit-status: 127
+ stdout: []
+ stderr:
+ - 'sh: 1: Associations: not found'
+ timeout: 10000
+ ip r|grep default:
+ exit-status: 0
+ stdout:
+ - default via 192.168.1.1 dev enp0s9
+ stderr: []
+ timeout: 10000
+ ipsec listcacerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=Root CA"'
+ stderr: []
+ timeout: 10000
+ ipsec listcerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=r-vp1"'
+ - 'subject: "C=CH, O=GSB, CN=r-vp2"'
+ stderr: []
+ timeout: 10000
+ ipsec statusall|grep Security:
+ exit-status: 0
+ stdout:
+ - 'Security Associations (1 up, 0 connecting):'
+ stderr: []
+ timeout: 10000
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.0.51/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.1.2/24
diff --git a/goss/r-vp1-old.yaml b/goss/r-vp1-old.yaml
new file mode 100644
index 0000000..916495d
--- /dev/null
+++ b/goss/r-vp1-old.yaml
@@ -0,0 +1,106 @@
+file:
+ /etc/ipsec.d/cacerts/strongswanCert.pem:
+ exists: true
+ mode: "0644"
+ size: 1834
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp1Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp2Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp1Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1675
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp2Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1679
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+package:
+ strongswan:
+ installed: true
+ versions:
+ - 5.2.1-6+deb8u2
+service:
+ strongswan:
+ enabled: true
+ running: true
+user:
+ strongswan:
+ exists: true
+ uid: 112
+ gid: 65534
+ groups:
+ - nogroup
+ home: /var/lib/strongswan
+ shell: /usr/sbin/nologin
+command:
+ Associations:
+ exit-status: 127
+ stdout: []
+ stderr:
+ - 'sh: 1: Associations: not found'
+ timeout: 10000
+ ip r|grep default:
+ exit-status: 0
+ stdout:
+ - default via 192.168.1.1 dev enp0s9
+ stderr: []
+ timeout: 10000
+ ipsec listcacerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=Root CA"'
+ stderr: []
+ timeout: 10000
+ ipsec listcerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=r-vp1"'
+ - 'subject: "C=CH, O=GSB, CN=r-vp2"'
+ stderr: []
+ timeout: 10000
+ ipsec statusall|grep Security:
+ exit-status: 0
+ stdout:
+ - 'Security Associations (1 up, 0 connecting):'
+ stderr: []
+ timeout: 10000
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.0.51/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.1.2/24
diff --git a/goss/r-vp1.yaml b/goss/r-vp1.yaml
new file mode 100644
index 0000000..08f1581
--- /dev/null
+++ b/goss/r-vp1.yaml
@@ -0,0 +1,67 @@
+package:
+# ferm:
+# installed: true
+ strongswan:
+ installed: true
+port:
+ udp:68:
+ listening: true
+service:
+# dnsmasq:
+# enabled: true
+# running: true
+ strongswan:
+ enabled: true
+ running: true
+ ssh:
+ enabled: true
+ running: true
+command:
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+command:
+ ping -c 4 192.168.0.52:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+command:
+ ping -c 4 192.168.1.1:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+command:
+ ping -c 4 192.168.200.254:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+command:
+ ping -c 4 172.16.0.1:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+#process:
+# dnsmasq:
+# running: true
+# squid:
+# running: true
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.0.51/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.1.2/24
\ No newline at end of file
diff --git a/goss/r-vp2-cs.yaml b/goss/r-vp2-cs.yaml
new file mode 100644
index 0000000..40cd178
--- /dev/null
+++ b/goss/r-vp2-cs.yaml
@@ -0,0 +1,105 @@
+file:
+ /etc/ipsec.d/cacerts/strongswanCert.pem:
+ exists: true
+ mode: "0644"
+ size: 1834
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp1Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp2Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp1Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1675
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp2Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1679
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+package:
+ strongswan:
+ installed: true
+ versions:
+ - 5.2.1-6+deb8u2
+service:
+ strongswan:
+ enabled: true
+ running: true
+user:
+ strongswan:
+ exists: true
+ gid: 65534
+ groups:
+ - nogroup
+ home: /var/lib/strongswan
+ shell: /usr/sbin/nologin
+command:
+ Associations:
+ exit-status: 127
+ stdout: []
+ stderr:
+ - 'sh: 1: Associations: not found'
+ timeout: 10000
+ ip r|grep default:
+ exit-status: 0
+ stdout:
+ - default via 192.168.99.99 dev enp0s3
+ stderr: []
+ timeout: 10000
+ ipsec listcacerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=Root CA"'
+ stderr: []
+ timeout: 10000
+ ipsec listcerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=r-vp2"'
+ - 'subject: "C=CH, O=GSB, CN=r-vp1"'
+ stderr: []
+ timeout: 10000
+ ipsec statusall|grep Security:
+ exit-status: 0
+ stdout:
+ - 'Security Associations (1 up, 0 connecting):'
+ stderr: []
+ timeout: 10000
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.128.254/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.0.52/24
diff --git a/goss/r-vp2-old.yaml b/goss/r-vp2-old.yaml
new file mode 100644
index 0000000..40cd178
--- /dev/null
+++ b/goss/r-vp2-old.yaml
@@ -0,0 +1,105 @@
+file:
+ /etc/ipsec.d/cacerts/strongswanCert.pem:
+ exists: true
+ mode: "0644"
+ size: 1834
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp1Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/certs/r-vp2Cert.pem:
+ exists: true
+ mode: "0644"
+ size: 1509
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp1Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1675
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+ /etc/ipsec.d/private/r-vp2Key.pem:
+ exists: true
+ mode: "0600"
+ size: 1679
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+package:
+ strongswan:
+ installed: true
+ versions:
+ - 5.2.1-6+deb8u2
+service:
+ strongswan:
+ enabled: true
+ running: true
+user:
+ strongswan:
+ exists: true
+ gid: 65534
+ groups:
+ - nogroup
+ home: /var/lib/strongswan
+ shell: /usr/sbin/nologin
+command:
+ Associations:
+ exit-status: 127
+ stdout: []
+ stderr:
+ - 'sh: 1: Associations: not found'
+ timeout: 10000
+ ip r|grep default:
+ exit-status: 0
+ stdout:
+ - default via 192.168.99.99 dev enp0s3
+ stderr: []
+ timeout: 10000
+ ipsec listcacerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=Root CA"'
+ stderr: []
+ timeout: 10000
+ ipsec listcerts|grep subject:
+ exit-status: 0
+ stdout:
+ - 'subject: "C=CH, O=GSB, CN=r-vp2"'
+ - 'subject: "C=CH, O=GSB, CN=r-vp1"'
+ stderr: []
+ timeout: 10000
+ ipsec statusall|grep Security:
+ exit-status: 0
+ stdout:
+ - 'Security Associations (1 up, 0 connecting):'
+ stderr: []
+ timeout: 10000
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.128.254/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.0.52/24
diff --git a/goss/r-vp2goss.yaml b/goss/r-vp2goss.yaml
new file mode 100644
index 0000000..0035b48
--- /dev/null
+++ b/goss/r-vp2goss.yaml
@@ -0,0 +1,67 @@
+package:
+ ferm:
+ installed: true
+ ipsec:
+ installed: true
+port:
+ tcp:53:
+ listening: true
+ udp:67:
+ listening: true
+ udp:68:
+ listening: true
+service:
+ dnsmasq:
+ enabled: true
+ running: true
+ ferm:
+ enabled: true
+ running: true
+ ssh:
+ enabled: true
+ running: true
+command:
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+ sysctl ping -c 4 192.168.0.51:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+ sysctl ping -c 4 192.168.1.1:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+ sysctl ping -c 4 192.168.200.254:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+ sysctl ping -c 4 172.16.0.1:
+ exit-status: 0
+ stdout:
+ - 4 received = 1
+ stderr: []
+ timeout: 10000
+process:
+ dnsmasq:
+ running: true
+ squid3:
+ running: true
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.128.254/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.0.52/24
\ No newline at end of file
diff --git a/goss/s-adm.yaml b/goss/s-adm.yaml
new file mode 100644
index 0000000..7137c20
--- /dev/null
+++ b/goss/s-adm.yaml
@@ -0,0 +1,80 @@
+package:
+ dnsmasq:
+ installed: true
+ squid:
+ installed: true
+addr:
+ tcp://depl.sio.lan:80:
+ reachable: true
+ timeout: 500
+port:
+ tcp:53:
+ listening: true
+ ip:
+ - 0.0.0.0
+ tcp6:53:
+ listening: true
+ ip:
+ - '::'
+ tcp6:8080:
+ listening: true
+ ip:
+ - '::'
+ udp:53:
+ listening: true
+ ip:
+ - 0.0.0.0
+ udp:67:
+ listening: true
+ ip:
+ - 0.0.0.0
+ udp6:53:
+ listening: true
+ ip:
+ - '::'
+service:
+ dnsmasq:
+ enabled: true
+ running: true
+ squid:
+ enabled: true
+ running: true
+ ssh:
+ enabled: true
+ running: true
+user:
+ dnsmasq:
+ exists: true
+ uid: 107
+ gid: 65534
+ groups:
+ - nogroup
+ home: /var/lib/misc
+ shell: /usr/sbin/nologin
+group:
+ ssh:
+ exists: true
+ gid: 111
+command:
+ /sbin/sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 1
+ stderr: []
+ timeout: 10000
+dns:
+ depl.sio.lan:
+ resolveable: true
+ addrs:
+ - 10.121.38.10
+ timeout: 500
+process:
+ dnsmasq:
+ running: true
+ squid:
+ running: true
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.99.99/24
diff --git a/goss/s-appli.yaml b/goss/s-appli.yaml
new file mode 100644
index 0000000..2023aba
--- /dev/null
+++ b/goss/s-appli.yaml
@@ -0,0 +1,35 @@
+service:
+ mariadb:
+ enabled: true
+ running: true
+
+ apache2:
+ enabled: true
+ running: true
+
+file:
+ /var/www/html/wordpress:
+ exists: true
+ owner: www-data
+ group: www-data
+ filetype: directory
+
+ /var/www/html/wordpress-5.3.2-fr_FR.tar.gz:
+ exists: true
+
+ /var/www/html/wordpress/wp-config-sample.php:
+ exists: true
+
+ /etc/apache2/sites-enabled/000-default.conf:
+ exists: true
+
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.3/24
+
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.0.3/24
diff --git a/goss/s-fog.yaml b/goss/s-fog.yaml
new file mode 100644
index 0000000..4929081
--- /dev/null
+++ b/goss/s-fog.yaml
@@ -0,0 +1,28 @@
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.16/24
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.0.16/24
+interface:
+ enp0s9:
+ exists: true
+ addrs:
+ - 172.16.64.16/24
+command:
+ ping -c 4 192.168.99.99:
+ exit-status: 0
+ stdout:
+ - 0% packet loss
+ stderr: []
+ timeout: 10000
+ ping -c 4 google.fr:
+ exit-status: 0
+ stdout:
+ - 0% packet loss
+ stderr: []
+ timeout: 10000
diff --git a/goss/s-infra.yaml b/goss/s-infra.yaml
new file mode 100644
index 0000000..99b2e5d
--- /dev/null
+++ b/goss/s-infra.yaml
@@ -0,0 +1,90 @@
+package:
+ bind9:
+ installed: true
+ lighttpd:
+ installed: true
+addr:
+ tcp://192.168.99.99:8080:
+ reachable: true
+ timeout: 500
+port:
+ tcp:80:
+ listening: true
+ ip:
+ - 0.0.0.0
+ tcp6:80:
+ listening: true
+ ip:
+ - '::'
+service:
+ bind9:
+ enabled: true
+ running: true
+ lighttpd:
+ enabled: true
+ running: true
+command:
+ host 172.16.0.2:
+ exit-status: 0
+ stdout:
+ - 2.0.16.172.in-addr.arpa domain name pointer s-proxy.gsb.lan.
+ stderr: []
+ timeout: 10000
+ host 172.16.0.9:
+ exit-status: 0
+ stdout:
+ - 9.0.16.172.in-addr.arpa domain name pointer s-itil.gsb.lan.
+ stderr: []
+ timeout: 10000
+ host free.fr:
+ exit-status: 0
+ stdout:
+ - free.fr has address 212.27.48.10
+ - free.fr has IPv6 address 2a01:e0c:1::1
+ - free.fr mail is handled by 10 mx1.free.fr.
+ - free.fr mail is handled by 20 mx2.free.fr.
+ stderr: []
+ timeout: 10000
+ host s-infra:
+ exit-status: 0
+ stdout:
+ - s-infra.gsb.lan has address 172.16.0.1
+ stderr: []
+ timeout: 10000
+ host s-infra.gsb.lan:
+ exit-status: 0
+ stdout:
+ - s-infra.gsb.lan has address 172.16.0.1
+ stderr: []
+ timeout: 10000
+ host s-mon:
+ exit-status: 0
+ stdout:
+ - s-mon.gsb.lan has address 172.16.0.8
+ stderr: []
+ timeout: 10000
+ host s-mon.gsb.lan:
+ exit-status: 0
+ stdout:
+ - s-mon.gsb.lan has address 172.16.0.8
+ stderr: []
+ timeout: 10000
+process:
+ lighttpd:
+ running: true
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.1/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.0.1/24
+http:
+ http://localhost/wpad.dat:
+ status: 200
+ allow-insecure: false
+ no-follow-redirects: false
+ timeout: 5000
+ body: []
diff --git a/goss/s-itil.yaml b/goss/s-itil.yaml
new file mode 100644
index 0000000..1fa5904
--- /dev/null
+++ b/goss/s-itil.yaml
@@ -0,0 +1,36 @@
+file:
+ /var/www/html/glpi:
+ exists: true
+ mode: "0755"
+ owner: www-data
+ group: www-data
+ filetype: directory
+
+ /var/www/html/ficlients:
+ exists: true
+ mode: "0775"
+ owner: www-data
+ group: www-data
+ filetype: directory
+
+ /var/www/html/glpi/plugins:
+ exists: true
+ mode: "0777"
+ filetype: directory
+
+ /var/www/html/index.nginx-debian.html:
+ exists: true
+ mode: "0775"
+ owner: www-data
+ group: www-data
+ filetype: file
+
+service:
+ mariadb:
+ enabled: true
+ running: true
+
+ nginx:
+ enabled: true
+ running: true
+
diff --git a/goss/s-lb-bd.yaml b/goss/s-lb-bd.yaml
new file mode 100644
index 0000000..3e9710f
--- /dev/null
+++ b/goss/s-lb-bd.yaml
@@ -0,0 +1,21 @@
+package:
+ mysql-server:
+ installed: true
+ versions:
+ - 5.5.54-0+deb8u1
+command:
+ egrep "#bind-address" /etc/mysql/my.cnf:
+ exit-status: 0
+ stdout:
+ - "#bind-address\t\t= 127.0.0.1"
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.13/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.102.50/24
diff --git a/goss/s-lb-web1.yaml b/goss/s-lb-web1.yaml
new file mode 100644
index 0000000..368118f
--- /dev/null
+++ b/goss/s-lb-web1.yaml
@@ -0,0 +1,63 @@
+package:
+ apache2:
+ installed: true
+ versions:
+ - 2.4.10-10+deb8u7
+ php5:
+ installed: true
+ versions:
+ - 5.6.29+dfsg-0+deb8u1
+port:
+ tcp:22:
+ listening: true
+ ip:
+ - 0.0.0.0
+ tcp6:22:
+ listening: true
+ ip:
+ - '::'
+ tcp6:80:
+ listening: true
+ ip:
+ - '::'
+service:
+ apache2:
+ enabled: true
+ running: true
+ sshd:
+ enabled: true
+ running: true
+user:
+ sshd:
+ exists: true
+ uid: 105
+ gid: 65534
+ groups:
+ - nogroup
+ home: /var/run/sshd
+ shell: /usr/sbin/nologin
+command:
+ egrep 192.168.102.14:/export/www /etc/fstab:
+ exit-status: 0
+ stdout:
+ - 192.168.102.14:/export/www /var/www/html nfs _netdev rw 0 0
+ stderr: []
+ timeout: 10000
+process:
+ apache2:
+ running: true
+ sshd:
+ running: true
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.11/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.101.1/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.102.1/24
diff --git a/goss/s-lb-web2.yaml b/goss/s-lb-web2.yaml
new file mode 100644
index 0000000..8df18aa
--- /dev/null
+++ b/goss/s-lb-web2.yaml
@@ -0,0 +1,63 @@
+package:
+ apache2:
+ installed: true
+ versions:
+ - 2.4.10-10+deb8u7
+ php5:
+ installed: true
+ versions:
+ - 5.6.29+dfsg-0+deb8u1
+port:
+ tcp:22:
+ listening: true
+ ip:
+ - 0.0.0.0
+ tcp6:22:
+ listening: true
+ ip:
+ - '::'
+ tcp6:80:
+ listening: true
+ ip:
+ - '::'
+service:
+ apache2:
+ enabled: true
+ running: true
+ sshd:
+ enabled: true
+ running: true
+user:
+ sshd:
+ exists: true
+ uid: 105
+ gid: 65534
+ groups:
+ - nogroup
+ home: /var/run/sshd
+ shell: /usr/sbin/nologin
+command:
+ egrep 192.168.102.14:/export/www /etc/fstab:
+ exit-status: 0
+ stdout:
+ - 192.168.102.14:/export/www /var/www/html nfs _netdev rw 0 0
+ stderr: []
+ timeout: 10000
+process:
+ apache2:
+ running: true
+ sshd:
+ running: true
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.12/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.101.2/24
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.102.2/24
diff --git a/goss/s-lb.yaml b/goss/s-lb.yaml
new file mode 100644
index 0000000..ad0a150
--- /dev/null
+++ b/goss/s-lb.yaml
@@ -0,0 +1,28 @@
+port:
+ tcp:80:
+ listening: true
+ ip:
+ - 192.168.100.11
+service:
+ haproxy:
+ enabled: true
+ running: true
+ sshd:
+ enabled: true
+ running: true
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.100/24
+ mtu: 1500
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.100.11/24
+ mtu: 1500
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.101.254/24
+ mtu: 1500
diff --git a/goss/s-lb.yaml.old b/goss/s-lb.yaml.old
new file mode 100644
index 0000000..3f723ed
--- /dev/null
+++ b/goss/s-lb.yaml.old
@@ -0,0 +1,65 @@
+file:
+ /etc/haproxy/haproxy.cfg:
+ exists: true
+ mode: "0644"
+ size: 1518
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+package:
+ haproxy:
+ installed: true
+port:
+ tcp:80:
+ listening: true
+ ip:
+ - 192.168.100.10
+service:
+ haproxy:
+ enabled: true
+ running: true
+user:
+ haproxy:
+ exists: true
+ uid: 111
+ gid: 117
+ groups:
+ - haproxy
+ home: /var/lib/haproxy
+ shell: /bin/false
+group:
+ haproxy:
+ exists: true
+ gid: 117
+command:
+ egrep "balance\s+roundrobin" /etc/haproxy/haproxy.cfg:
+ exit-status: 0
+ stdout:
+ - balance roundrobin
+ stderr: []
+ timeout: 10000
+ egrep "bind\s+192.168.100.10:80" /etc/haproxy/haproxy.cfg:
+ exit-status: 0
+ stdout:
+ - bind 192.168.100.10:80
+ stderr: []
+ timeout: 10000
+ egrep "mode\s+http" /etc/haproxy/haproxy.cfg:
+ exit-status: 0
+ stdout:
+ - "mode\thttp"
+ stderr: []
+ timeout: 10000
+process:
+ haproxy:
+ running: true
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.10/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.100.10/24
diff --git a/goss/s-mon.yaml b/goss/s-mon.yaml
new file mode 100644
index 0000000..10c5be1
--- /dev/null
+++ b/goss/s-mon.yaml
@@ -0,0 +1,62 @@
+file:
+ /etc/icinga/htpasswd.users:
+ exists: true
+ mode: "0644"
+ size: 26
+ owner: root
+ group: root
+ filetype: file
+ contains: []
+package:
+ apache2:
+ installed: true
+ nagios-snmp-plugins:
+ installed: true
+ icinga:
+ installed: true
+ snmp:
+ installed: true
+port:
+ tcp6:80:
+ listening: true
+ ip:
+ - '::'
+ udp:514:
+ listening: true
+ ip:
+ - 0.0.0.0
+service:
+ apache2:
+ enabled: true
+ running: true
+ icinga:
+ enabled: true
+ running: true
+command:
+ sysctl net.ipv4.ip_forward:
+ exit-status: 0
+ stdout:
+ - net.ipv4.ip_forward = 0
+ stderr: []
+ timeout: 10000
+process:
+ apache2:
+ running: true
+ icinga:
+ running: true
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.8/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.0.8/24
+http:
+ http://localhost/icinga:
+ status: 401
+ allow-insecure: false
+ no-follow-redirects: false
+ timeout: 5000
+ body: []
diff --git a/goss/s-proxy.yaml b/goss/s-proxy.yaml
new file mode 100644
index 0000000..5f4cc9b
--- /dev/null
+++ b/goss/s-proxy.yaml
@@ -0,0 +1,42 @@
+package:
+ squid:
+ installed: true
+addr:
+ tcp://192.168.99.99:8080:
+ reachable: true
+ timeout: 500
+port:
+ tcp6:8080:
+ listening: true
+ ip:
+ - '::'
+ squid:
+ enabled: true
+ running: true
+command:
+ host 172.16.0.2:
+ exit-status: 0
+ stdout:
+ - 2.0.16.172.in-addr.arpa domaine name pointer s-proxy.gsb.lan
+ stderr: []
+ timeout: 10000
+interface:
+ enp0s3:
+ exists: true
+ addrs:
+ - 192.168.99.1/24
+ enp0s8
+ exists: true
+ addrs:
+ - 192.168.99.1/24
+ enp0s8:
+ exists: true
+ addrs:
+ - 172.16.0.1/24
+http:
+ http://localhost/wpad.dat:
+ status: 200
+ allow-insecure: false
+ no-follow-redirects: false
+ timeout: 5000
+ body: []
diff --git a/graylog-pont.yml b/graylog-pont.yml
new file mode 100644
index 0000000..901115d
--- /dev/null
+++ b/graylog-pont.yml
@@ -0,0 +1,8 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - goss
+ - docker-graylog-pont
+ - post
\ No newline at end of file
diff --git a/gsbchk b/gsbchk
new file mode 100755
index 0000000..f9f5e51
--- /dev/null
+++ b/gsbchk
@@ -0,0 +1,14 @@
+#!/bin/bash
+
+filename=/root/tools/ansible/gsb/goss/$HOSTNAME.yaml
+
+if ! [ -e $filename ] ; then
+ echo gsbchk : erreur ouverture $filename
+ exit 1
+
+fi
+if [ $# == 1] ; then
+ goss -g $filename v
+else
+ goss $*
+fi
diff --git a/gsbstart b/gsbstart
new file mode 100755
index 0000000..84a0feb
--- /dev/null
+++ b/gsbstart
@@ -0,0 +1,179 @@
+#!/usr/bin/perl
+
+#use strict;
+#use warnings;
+#SCRIPT PERMETTANT DE METTRE LES INTERFACES APPROPRIEES POUR LA MACHINE ENTREE EN PARAMETRE ET DE LA DEMARRER
+my %machines = (
+ 's-infra' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-proxy' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-spec' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-mon' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-mess' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-itil' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-proxy' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-backup' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 's-appli' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-infra'
+ },
+ 'r-int' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-link',
+ netif3 => 'n-wifi',
+ netif4 => 'n-user',
+ netif5 => 'n-infra'
+ },
+ 'r-ext' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-dmz',
+ netif3 => 'enp0s3',
+ netif4 => 'n-linkv',
+ netif5 => 'n-link'
+ },
+ 'r-vp2' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-agence',
+ netif3 => 'enp0s3'
+ },
+ 'r-vp1' => {
+ netif1 => 'n-adm',
+ netif2 => 'enp0s3',
+ netif3 => 'n-linkv'
+ },
+ 's-lb' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-dmz',
+ netif3 => 'n-dmz-lb'
+ },
+ 's-lb-bd' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-dmz-db'
+
+ },
+ 's-lb-web1' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-dmz-lb',
+ netif3 => 'n-dmz-db'
+ },
+ 's-lb-web2' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-dmz-lb',
+ netif3 => 'n-dmz-db'
+ },
+ 's-nas' => {
+ netif1 => 'n-adm',
+ netif2 => 'n-dmz-db',
+ }
+
+
+
+
+
+
+
+);
+
+
+my ($net1, $net2, $net3, $net4, $net5);
+
+my $machine = shift;
+die "usage : gsbstart <machine>" unless ( $machine);
+
+#print $machines { $machine } "\n";
+if (%{$machines{$machine}}) {
+# print $machines { $machine } {netif1}, "\n";
+ $net1 = $machines { $machine } {netif1};
+ $net2 = $machines { $machine } {netif2};
+ $net3 = $machines { $machine } {netif3};
+ $net4 = $machines { $machine } {netif4};
+ $net5 = $machines { $machine } {netif5};
+
+
+
+} else {
+ print "machine $machine inconnue\n";
+}
+#
+
+my $ninfra = "VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"";
+
+my $rint = "VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"\nVBoxManage modifyvm ".$machine. " --nic3 intnet\nVBoxManage modifyvm ".$machine. " --intnet3 \"". $net3."\"\nVBoxManage modifyvm ".$machine. " --nic4 intnet\nVBoxManage modifyvm ".$machine. " --intnet4 \"". $net4."\"\nVBoxManage modifyvm ".$machine. " --nic5 intnet\nVBoxManage modifyvm ".$machine. " --intnet5 \"". $net5."\"";
+
+my $rext = "VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"\nVBoxManage modifyvm ".$machine. " --nic3 bridged\nVBoxManage modifyvm ".$machine. " --bridgeadapter1 ". $net3."\nVBoxManage modifyvm ".$machine. " --nic4 intnet\nVBoxManage modifyvm ".$machine. " --intnet4 \"". $net4."\"\nVBoxManage modifyvm ".$machine. " --nic5 intnet\nVBoxManage modifyvm ".$machine. " --intnet5 \"". $net5."\"";
+
+my $rvp2 = "VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"\nVBoxManage modifyvm ".$machine. " --nic3 bridged\nVBoxManage modifyvm ".$machine. " --bridgeadapter1 ". $net3."\n";
+
+my $rvp1 = "VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 bridged\nVBoxManage modifyvm ".$machine. " --bridgeadapter1 ". $net2 ."\nVBoxManage modifyvm ".$machine. " --nic3 intnet\nVBoxManage modifyvm ".$machine. " --intnet3 \"". $net3."\"\n";
+
+my $lb = "VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"\nVBoxManage modifyvm ".$machine. " --nic3 intnet\nVBoxManage modifyvm ".$machine. " --intnet3 ". $net3."\n";
+
+my $lbbd ="VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"\n";
+
+my $lbweb = "VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"\nVBoxManage modifyvm ".$machine. " --nic3 intnet\nVBoxManage modifyvm ".$machine. " --intnet3 \"". $net3."\"\n";
+
+my $snas ="VBoxManage modifyvm ".$machine. " --nic1 intnet\nVBoxManage modifyvm ".$machine. " --intnet1 \"". $net1."\"\nVBoxManage modifyvm ".$machine. " --nic2 intnet\nVBoxManage modifyvm ".$machine. " --intnet2 \"". $net2."\"\n";
+
+#print $routeur;
+
+
+if ($machine eq "r-int") {
+ qx($rint);
+ print "la création des interfaces du routeur $machine a fonctionné!\n";
+}else{
+ if ($machine eq "r-ext") {
+ qx($rext);
+ }else{
+ qx($ninfra);
+ print "la création des interfaces de $machine a fonctionné!\n";
+ }
+}
+if ($machine eq "r-vp2") {
+ qx($rvp2);
+}
+if ($machine eq "r-vp1") {
+ qx($rvp1);
+}
+if ($machine eq "s-lb"){
+ qx($lb);
+}
+if ($machine eq "s-lb-web1"){
+ qx($lbweb);
+}
+if ($machine eq "s-lb-web2"){
+ qx($lbweb);
+}
+if ($machine eq "s-lb-bd"){
+ qx($lbbd);
+}
+if ($machine eq "s-nas"){
+ qx($snas);
+}
+
+qx(VBoxManage startvm $machine);
+
+
+
diff --git a/gsbstartl b/gsbstartl
new file mode 100755
index 0000000..11da13b
--- /dev/null
+++ b/gsbstartl
@@ -0,0 +1,28 @@
+#!/usr/bin/perl
+
+use strict;
+use warnings;
+
+while ($_ = shift @ARGV) {
+ if ($_ eq "-a"){
+ qx(./gsbstart s-infra);
+ qx(./gsbstart s-spec);
+ qx(./gsbstart s-proxy);
+ qx(./gsbstart s-mon);
+ qx(./gsbstart s-mess);
+ qx(./gsbstart s-itil);
+ qx(./gsbstart s-backup);
+ qx(./gsbstart s-appli);
+ qx(./gsbstart r-vp1);
+ qx(./gsbstart r-vp2);
+ qx(./gsbstart r-int);
+ qx(./gsbstart r-ext);
+ qx(./gsbstart s-lb);
+ qx(./gsbstart s-lb-web-1);
+ qx(./gsbstart s-lb-web-2);
+ qx(./gsbstart s-lb-bd);
+
+ }else{
+ qx(./gsbstart $_);
+ }
+}
diff --git a/lisezmoi.txt b/lisezmoi.txt
new file mode 100644
index 0000000..c14a693
--- /dev/null
+++ b/lisezmoi.txt
@@ -0,0 +1,14 @@
+lisezmoi.txt
+------------
+
+Ce document décrit les divers élements du projet GSB du BTS SIO utilisé pour l'Epreuve E4
+
+
+Le projet GSB décrit les diférents playbooks permttant d'installer les
+machines du projet GSB
+
+Les répertoires :
+
+- roles : les roles
+- goss : les outils de test
+
diff --git a/pre/inst-depl b/pre/inst-depl
new file mode 100644
index 0000000..a1610db
--- /dev/null
+++ b/pre/inst-depl
@@ -0,0 +1,48 @@
+#!/bin/bash
+set -o errexit
+set -o pipefail
+GITUSR=gitgsb
+GITPRJ=gsb
+apt update && apt upgrade
+apt install -y apache2 git
+getent passwd "${GITUSR}" >> /dev/null
+if [[ $? != 0 ]]; then
+ echo "creation utilisateur "${GITUSR}" ..."
+ /sbin/useradd -m -d /home/"${GITUSR}" -s /bin/bash "${GITUSR}"
+ echo "${GITUSR}:${GITUSR}" | /sbin/chpasswd
+else
+ echo "utilisateur "${GITUSR}" existant..."
+fi
+su -c "git init --share --bare /home/${GITUSR}/${GITPRJ}.git" "${GITUSR}"
+su -c "cd ${GITPRJ}.git/.git/hooks && mv post-update.sample post-update" "${GITUSR}"
+[[ -h /var/www/html/"${GITPRJ}".git ]]|| ln -s /home/"${GITUSR}"/"${GITPRJ}".git /var/www/html/"${GITPRJ}".git
+[[ -d /var/www/html/gsbstore ]]|| mkdir /var/www/html/gsbstore
+
+(cat <<EOT > /var/www/html/gsbstore/getall
+
+#!/bin/bash
+
+set -o errexit
+set -o pipefail
+
+GLPIREL=9.4.5
+wget -nc https://github.com/glpi-project/glpi/releases/download/\${GLPIREL}/glpi-\${GLPIREL}.tgz
+
+FIREL=9.4+2.4
+wget -nc -O fusioninventory-glpi\${FIREL}.tag.gz https://github.com/fusioninventory/fusioninventory-for-glpi/archive/glpi\${FIREL}.tar.gz
+#https://github.com/fusioninventory/fusioninventory-for-glpi/archive/glpi9.4+2.4.tar.g
+
+FIAGREL=2.5.2
+wget -nc https://github.com/fusioninventory/fusioninventory-agent/releases/download/\${FIAGREL}/fusioninventory-agent_windows-x64_\${FIAGREL}.exe
+
+wget -nc https://github.com/fusioninventory/fusioninventory-agent/releases/download/\$FIAGREL/fusioninventory-agent_windows-x86_\${FIAGREL}.exe
+
+FOGREL=1.5.7
+wget -nc https://github.com/FOGProject/fogproject/archive/\${FOGREL}.tar.gz -O fogproject-\${FOGREL}.tar.gz
+
+wget -nc https://fr.wordpress.org/wordpress-5.3.2-fr_FR.tar.gz
+
+EOT
+)
+cat /var/www/html/gsbstore/getall
+
diff --git a/pre/pull-config b/pre/pull-config
new file mode 100644
index 0000000..25d4cd1
--- /dev/null
+++ b/pre/pull-config
@@ -0,0 +1,24 @@
+#!/bin/bash
+
+dir=/root/tools/ansible
+host=depl
+hostf=$host.sio.lan
+repo=gsb
+
+[ -e $dir ] || mkdir -p $dir
+
+grep $hostf /etc/hosts > /dev/null || echo "10.121.38.10 $hostf $host" >> /etc/hosts
+
+cd $dir
+
+hostname > hosts
+
+#git clone http://$host/$repo.git
+
+cd $repo
+git pull
+
+ansible-playbook -c local -i 'localhost,' $(hostname).yml
+#ansible-pull -i $dir/hosts -d $repo -U http://$host/$repo.git
+
+exit 0
diff --git a/pull-config b/pull-config
new file mode 100644
index 0000000..25d4cd1
--- /dev/null
+++ b/pull-config
@@ -0,0 +1,24 @@
+#!/bin/bash
+
+dir=/root/tools/ansible
+host=depl
+hostf=$host.sio.lan
+repo=gsb
+
+[ -e $dir ] || mkdir -p $dir
+
+grep $hostf /etc/hosts > /dev/null || echo "10.121.38.10 $hostf $host" >> /etc/hosts
+
+cd $dir
+
+hostname > hosts
+
+#git clone http://$host/$repo.git
+
+cd $repo
+git pull
+
+ansible-playbook -c local -i 'localhost,' $(hostname).yml
+#ansible-pull -i $dir/hosts -d $repo -U http://$host/$repo.git
+
+exit 0
diff --git a/r-ext.yml b/r-ext.yml
new file mode 100644
index 0000000..3a16f4b
--- /dev/null
+++ b/r-ext.yml
@@ -0,0 +1,12 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - r-ext
+ - snmp-agent
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/r-int.yml b/r-int.yml
new file mode 100644
index 0000000..32fde49
--- /dev/null
+++ b/r-int.yml
@@ -0,0 +1,13 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - r-int
+ - ssh-cli
+ - syslog-cli
+ - dhcp
+ - snmp-agent
+ - post
diff --git a/r-vp1.yml b/r-vp1.yml
new file mode 100644
index 0000000..f764b6a
--- /dev/null
+++ b/r-vp1.yml
@@ -0,0 +1,20 @@
+---
+- hosts: localhost
+ connection: local
+
+ vars:
+ - ip1: 192.168.0.51
+ - remip: 192.168.0.52
+ - mynet: 192.168.1.0
+ - remnet: 172.16.128.0
+
+ roles:
+ - base
+ - goss
+ - snmp-agent
+ - vpn-stg-r
+# - x509-r
+# - firewall-vpn-r
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/r-vp2.yml b/r-vp2.yml
new file mode 100644
index 0000000..b03d553
--- /dev/null
+++ b/r-vp2.yml
@@ -0,0 +1,22 @@
+---
+- hosts: localhost
+ connection: local
+
+ vars:
+ - ip1: 192.168.0.52
+ - remip: 192.168.0.51
+ - mynet: 172.16.128.0
+ - remnet: 192.168.1.0
+
+ roles:
+ - base
+ - goss
+ - dhcp-ag
+ - dns-agence
+ - snmp-agent
+ - vpn-stg-l
+# - x509-l
+# - firewall-vpn-l
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/roles/apache2/handlers/main.yml b/roles/apache2/handlers/main.yml
new file mode 100644
index 0000000..645ca3a
--- /dev/null
+++ b/roles/apache2/handlers/main.yml
@@ -0,0 +1,6 @@
+---
+ - name: restart apache2
+ service: name=apache2 state=restarted
+
+ - name: restart mysql-server
+ service: name=mysql-server state=restarted
diff --git a/roles/apache2/tasks/main.yml b/roles/apache2/tasks/main.yml
new file mode 100644
index 0000000..6769f3a
--- /dev/null
+++ b/roles/apache2/tasks/main.yml
@@ -0,0 +1,14 @@
+---
+- name: Update apt cache
+ apt: update_cache=yes cache_valid_time=3600
+
+- name: Install required software
+ apt: name={{ item }} state=present
+ with_items:
+ - apache2
+ - mysql-server
+ - php-mysql
+ - php
+ - libapache2-mod-php
+ - php-mcrypt
+ - python-mysqldb
diff --git a/roles/appli/handlers/main.yml b/roles/appli/handlers/main.yml
new file mode 100644
index 0000000..f041d80
--- /dev/null
+++ b/roles/appli/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+- name: restart apache
+ service: name=apache2 state=restarted
+ become: yes
diff --git a/roles/appli/tasks/main.yml b/roles/appli/tasks/main.yml
new file mode 100644
index 0000000..ee207af
--- /dev/null
+++ b/roles/appli/tasks/main.yml
@@ -0,0 +1,73 @@
+
+---
+- name: Installation des packets
+ apt:
+ name: "{{ item }}"
+ state: latest
+ with_items:
+ - php
+ - php-fpm
+ - php-mbstring
+ - php-ssh2
+ - php-gd
+ - php-mysql
+ - python-mysqldb
+ - libapache2-mod-php
+ - mariadb-server
+ - apache2
+ - python
+
+- name: Création du répertoire pour wordpress
+ file:
+ path: /var/www/html/wordpress
+ state: directory
+
+- name: Téléchargement de wordpress
+ get_url:
+ url: http://depl/gsbstore/wordpress-5.3.2-fr_FR.tar.gz
+ dest: /var/www/html
+
+- name: Extraction du fichier wordpress
+ unarchive:
+ src: /var/www/html/wordpress-5.3.2-fr_FR.tar.gz
+ dest: /var/www/html
+
+- name: Fix permissions owner
+ shell: chown -R www-data /var/www/html/wordpress
+
+- name: Fix permissions groups
+ shell: chgrp -R www-data /var/www/html/wordpress
+
+- name: Mettre à jour le site Apache par défaut
+ lineinfile:
+ dest: /etc/apache2/sites-enabled/000-default.conf
+ regexp: "(.)+DocumentRoot /var/www/html"
+ line: "DocumentRoot /var/www/html/wordpress"
+
+- name: restart apache2
+ service:
+ name: apache2
+ state: restarted
+
+- name: Mettre à jour le fichier de configuration WordPress
+ lineinfile:
+ dest: /var/www/html/wordpress/wp-config-sample.php
+ backup: yes
+ regexp: "{{ item.regexp }}"
+ line: "{{ item.line }}"
+ with_items:
+ - {'regexp': "define\\('DB_NAME', '(.)+'\\);", 'line': "define('DB_NAME', 'wordpress');"}
+ - {'regexp': "define\\('DB_HOST', '(.)+'\\);", 'line': "define('DB_HOST', 'localhost');"}
+ - {'regexp': "define\\('DB_USER', '(.)+'\\);", 'line': "define('DB_USER', 'wp');"}
+ - {'regexp': "define\\('DB_PASSWORD', '(.)+'\\);", 'line': "define('DB_PASSWORD', 'wp');"}
+
+- name: Création de la base de donnée mysql
+ mysql_db:
+ name: wordpress
+ state: present
+
+- name: Création de l'utilisateur mysql
+ mysql_user:
+ name: wordpress
+ password: wp
+ priv: "*.*:ALL"
diff --git a/roles/base/files/apt.conf b/roles/base/files/apt.conf
new file mode 100644
index 0000000..def8cbb
--- /dev/null
+++ b/roles/base/files/apt.conf
@@ -0,0 +1 @@
+Acquire::http::Proxy "http://192.168.99.99:8080";
diff --git a/roles/base/files/resolv.conf b/roles/base/files/resolv.conf
new file mode 100644
index 0000000..afafa6b
--- /dev/null
+++ b/roles/base/files/resolv.conf
@@ -0,0 +1,4 @@
+domain gsb.lan
+search gsb.lan
+nameserver 192.168.99.99
+
diff --git a/roles/base/files/sources.list b/roles/base/files/sources.list
new file mode 100644
index 0000000..9fa923c
--- /dev/null
+++ b/roles/base/files/sources.list
@@ -0,0 +1,10 @@
+#
+
+deb http://ftp.fr.debian.org/debian/ wheezy main contrib non-free
+
+deb http://security.debian.org/ wheezy/updates main
+
+deb http://ftp.fr.debian.org/debian/ wheezy-updates main
+
+deb http://http.debian.net/debian wheezy-backports main
+
diff --git a/roles/base/files/sources.list.Debian b/roles/base/files/sources.list.Debian
new file mode 100644
index 0000000..520e104
--- /dev/null
+++ b/roles/base/files/sources.list.Debian
@@ -0,0 +1,9 @@
+
+#deb http://ftp.fr.debian.org/debian/ stretch main contrib non-free
+#deb http://security.debian.org/ stretch/updates main
+#deb http://ftp.fr.debian.org/debian/ stretch-updates main
+
+deb http://deb.debian.org/debian/ buster main contrib non-free
+deb http://security.debian.org/debian-security buster/updates main contrib non-free
+deb http://deb.debian.org/debian/ buster-updates main contrib non-free
+
diff --git a/roles/base/files/sources.list.Ubuntu b/roles/base/files/sources.list.Ubuntu
new file mode 100644
index 0000000..8d1643a
--- /dev/null
+++ b/roles/base/files/sources.list.Ubuntu
@@ -0,0 +1,13 @@
+#------------------------------------------------------------------------------#
+# OFFICIAL UBUNTU REPOS #
+#------------------------------------------------------------------------------#
+
+
+###### Ubuntu Main Repos
+deb http://fr.archive.ubuntu.com/ubuntu/ wily main restricted universe
+
+###### Ubuntu Update Repos
+deb http://fr.archive.ubuntu.com/ubuntu/ wily-security main restricted universe
+deb http://fr.archive.ubuntu.com/ubuntu/ wily-updates main restricted universe
+
+
diff --git a/roles/base/files/sources.list.jessie b/roles/base/files/sources.list.jessie
new file mode 100644
index 0000000..cad9227
--- /dev/null
+++ b/roles/base/files/sources.list.jessie
@@ -0,0 +1,22 @@
+#
+
+# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 NETINST Binary-1 20110205-14:34]/ jessie main
+
+#deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 NETINST Binary-1 20110205-14:34]/ jessie main
+
+
+deb http://ftp.fr.debian.org/debian/ jessie main contrib non-free
+#deb-src http://ftp.fr.debian.org/debian/ jessie main
+
+deb http://security.debian.org/ jessie/updates main
+#deb-src http://security.debian.org/ jessie/updates main
+
+deb http://ftp.fr.debian.org/debian/ jessie-updates main
+#deb-src http://ftp.fr.debian.org/debian/ jessie-updates main
+#deb http://backports.debian.org/debian-backports jessie-backports main
+#deb http://packages.steve.org.uk/slaughter/jessie/ ./
+#deb https://rex.linux-files.org/debian/ jessie rex
+
+
+#deb http://http.debian.net/debian jessie-backports main
+
diff --git a/roles/base/files/sources.list.wheezy b/roles/base/files/sources.list.wheezy
new file mode 100644
index 0000000..e8a28d8
--- /dev/null
+++ b/roles/base/files/sources.list.wheezy
@@ -0,0 +1,22 @@
+#
+
+# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 NETINST Binary-1 20110205-14:34]/ wheezy main
+
+#deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 NETINST Binary-1 20110205-14:34]/ wheezy main
+
+
+deb http://ftp.fr.debian.org/debian/ wheezy main contrib non-free
+#deb-src http://ftp.fr.debian.org/debian/ wheezy main
+
+deb http://security.debian.org/ wheezy/updates main
+#deb-src http://security.debian.org/ wheezy/updates main
+
+deb http://ftp.fr.debian.org/debian/ wheezy-updates main
+#deb-src http://ftp.fr.debian.org/debian/ wheezy-updates main
+#deb http://backports.debian.org/debian-backports wheezy-backports main
+#deb http://packages.steve.org.uk/slaughter/wheezy/ ./
+#deb https://rex.linux-files.org/debian/ wheezy rex
+
+
+deb http://http.debian.net/debian wheezy-backports main
+
diff --git a/roles/base/tasks/main.yml b/roles/base/tasks/main.yml
new file mode 100644
index 0000000..c4b3c00
--- /dev/null
+++ b/roles/base/tasks/main.yml
@@ -0,0 +1,49 @@
+---
+
+- name: Copie sources.list
+ copy: src=sources.list.{{ ansible_distribution }} dest=/etc/apt/sources.list
+
+- name: Copie apt.conf pour proxy
+ copy: src=apt.conf dest=/etc/apt/apt.conf
+ when: ansible_hostname != "s-adm"
+
+- name: Update + Upgrade
+ apt:
+ upgrade: yes
+ update_cache: yes
+ cache_valid_time: 86400 #One day
+
+- name: Install paquets
+ apt:
+ state: present
+ name:
+ - vim
+ - ntp
+ - mc
+ - tcpdump
+ - curl
+ - net-tools
+ - rsync
+ - sudo
+
+- name: Desinstall paquets
+ apt:
+ state: absent
+ name:
+ - nfs-common
+ - rpcbind
+ - bluetooth
+
+- name: Configure Vim
+ alternatives: name=editor path=/usr/bin/vim
+
+#- name: copie fichier
+# copy: src=mesg.txt dest=/root/tools/mesg.txt
+
+- name: Generation /etc/hosts
+ template: src=hosts.j2 dest=/etc/hosts
+ when: ansible_hostname != "s-proxy"
+
+- name: Generation /etc/hosts pour s-proxy
+ template: src=hosts.s-proxy.j2 dest=/etc/hosts
+ when: ansible_hostname == "s-proxy"
diff --git a/roles/base/templates/hosts.j2 b/roles/base/templates/hosts.j2
new file mode 100644
index 0000000..fb36931
--- /dev/null
+++ b/roles/base/templates/hosts.j2
@@ -0,0 +1,27 @@
+127.0.0.1 localhost
+127.0.1.1 {{ ansible_nodename }} {{ ansible_hostname }}
+127.0.0.1 localhost ip6-localhost ip6-loopback
+
+10.121.38.10 depl.sio.lan depl
+
+192.168.99.99 s-adm.gsb.adm
+192.168.99.1 s-infra.gsb.adm
+192.168.99.2 s-proxy.gsb.adm
+192.168.99.3 s-appli.gsb.adm
+192.168.99.4 s-backup.gsb.adm
+192.168.99.5 s-puppet.gsb.adm
+192.168.99.6 s-win.gsb.adm
+192.168.99.7 s-mess.gsb.adm
+192.168.99.8 s-mon.gsb.adm
+192.168.99.9 s-itil.gsb.adm
+192.168.99.10 s-sspec.gsb.adm
+192.168.99.11 s-web-ext.gsb.adm
+192.168.99.10 s-dns.gsb.adm
+192.168.99.12 r-int.gsb.adm
+192.168.99.13 r-ext.gsb.adm
+192.168.99.14 s-nas.gsb.adm
+192.168.99.15 s-san.gsb.adm
+192.168.99.16 s-fog.gsb.adm
+
+192.168.99.8 syslog.gsb.adm
+
diff --git a/roles/base/templates/hosts.s-proxy.j2 b/roles/base/templates/hosts.s-proxy.j2
new file mode 100644
index 0000000..3b90331
--- /dev/null
+++ b/roles/base/templates/hosts.s-proxy.j2
@@ -0,0 +1,26 @@
+127.0.0.1 localhost
+127.0.1.1 {{ ansible_nodename }} {{ ansible_hostname }}
+127.0.0.1 localhost ip6-localhost ip6-loopback
+172.16.0.2 s-proxy.gsb.lan s-proxy
+
+10.121.38.10 depl
+
+192.168.99.99 s-adm.gsb.adm
+192.168.99.1 s-infra.gsb.adm
+192.168.99.2 s-proxy.gsb.adm
+192.168.99.3 s-appli.gsb.adm
+192.168.99.4 s-backup.gsb.adm
+192.168.99.5 s-puppet.gsb.adm
+192.168.99.6 s-win.gsb.adm
+192.168.99.7 s-mess.gsb.adm
+192.168.99.8 s-mon.gsb.adm
+192.168.99.9 s-itil.gsb.adm
+192.168.99.10 s-sspec.gsb.adm
+192.168.99.11 s-web-ext.gsb.adm
+192.168.99.10 s-dns.gsb.adm
+192.168.99.12 r-int.gsb.adm
+192.168.99.13 r-ext.gsb.adm
+192.168.99.14 s-nas.gsb.adm
+
+192.168.99.8 syslog.gsb.adm
+
diff --git a/roles/db-user/tasks/main.yml b/roles/db-user/tasks/main.yml
new file mode 100644
index 0000000..296de75
--- /dev/null
+++ b/roles/db-user/tasks/main.yml
@@ -0,0 +1,7 @@
+---
+- name: Create mysql user
+ mysql_user:
+ host: "{{ cli_ip }}"
+ name: "{{ maria_dbuser }}"
+ password: "{{ maria_dbpasswd }}"
+ priv: "*.*:ALL"
diff --git a/roles/dhcp-ag/files/dhcpd.conf b/roles/dhcp-ag/files/dhcpd.conf
new file mode 100644
index 0000000..caca080
--- /dev/null
+++ b/roles/dhcp-ag/files/dhcpd.conf
@@ -0,0 +1,152 @@
+#
+# Sample configuration file for ISC dhcpd for Debian
+#
+#
+
+# The ddns-updates-style parameter controls whether or not the server will
+# attempt to do a DNS update when a lease is confirmed. We default to the
+# behavior of the version 2 packages ('none', since DHCP v2 didn't
+# have support for DDNS.)
+ddns-update-style none;
+
+# option definitions common to all supported networks...
+option domain-name "gsb.lan";
+option domain-name-servers 172.16.0.1;
+
+default-lease-time 86400;
+max-lease-time 86400;
+
+# If this DHCP server is the official DHCP server for the local
+# network, the authoritative directive should be uncommented.
+#authoritative;
+
+# Use this to send dhcp log messages to a different log file (you also
+# have to hack syslog.conf to complete the redirection).
+log-facility local7;
+
+# No service will be given on this subnet, but declaring it helps the
+# DHCP server to understand the network topology.
+
+#subnet 10.152.187.0 netmask 255.255.255.0 {
+#}
+
+# This is a very basic subnet declaration.
+
+#subnet 10.254.239.0 netmask 255.255.255.224 {
+# range 10.254.239.10 10.254.239.20;
+# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
+#}
+
+# This declaration allows BOOTP clients to get dynamic addresses,
+# which we don't really recommend.
+
+#subnet 10.254.239.32 netmask 255.255.255.224 {
+# range dynamic-bootp 10.254.239.40 10.254.239.60;
+# option broadcast-address 10.254.239.31;
+# option routers rtr-239-32-1.example.org;
+#}
+
+# A slightly different configuration for an internal subnet.
+#subnet 10.5.5.0 netmask 255.255.255.224 {
+# range 10.5.5.26 10.5.5.30;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
+# Hosts which require special configuration options can be listed in
+# host statements. If no address is specified, the address will be
+# allocated dynamically (if possible), but the host-specific information
+# will still come from the host declaration.
+
+#host passacaglia {
+# hardware ethernet 0:0:c0:5d:bd:95;
+# filename "vmunix.passacaglia";
+# server-name "toccata.fugue.com";
+#}
+
+# Fixed IP addresses can also be specified for hosts. These addresses
+# should not also be listed as being available for dynamic assignment.
+# Hosts for which fixed IP addresses have been specified can boot using
+# BOOTP or DHCP. Hosts for which no fixed address is specified can only
+# be booted with DHCP, unless there is an address range on the subnet
+# to which a BOOTP client is connected which has the dynamic-bootp flag
+# set.
+#host fantasia {
+# hardware ethernet 08:00:07:26:c0:a5;
+# fixed-address fantasia.fugue.com;
+#}
+
+# You can declare a class of clients and then do address allocation
+# based on that. The example below shows a case where all clients
+# in a certain class get addresses on the 10.17.224/24 subnet, and all
+# other clients get addresses on the 10.0.29/24 subnet.
+
+#class "foo" {
+# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
+#}
+
+#shared-network 224-29 {
+# subnet 10.17.224.0 netmask 255.255.255.0 {
+# option routers rtr-224.example.org;
+# }
+# subnet 10.0.29.0 netmask 255.255.255.0 {
+# option routers rtr-29.example.org;
+# }
+# pool {
+# allow members of "foo";
+# range 10.17.224.10 10.17.224.250;
+# }
+# pool {
+# deny members of "foo";
+# range 10.0.29.10 10.0.29.230;
+# }
+#}
+
+#DHCP pour le réseau wifi
+#subnet 172.16.65.0 netmask 255.255.255.0 {
+# range 172.16.65.1 172.16.65.100;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
+#DHCP pour le réseau USER
+
+#subnet 172.16.64.0 netmask 255.255.255.0 {
+# range 172.16.64.20 172.16.64.120;
+# option domain-name-servers 172.16.0.6, 172.16.0.1 ;
+# option routers 172.16.64.254;
+# option broadcast-address 172.16.64.255;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
+#DHCP pour le réseau INFRA
+
+#subnet 172.16.0.0 netmask 255.255.255.0 {
+# range 172.16.0.1 172.16.0.100;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
+#DHCP pour le réseau AGENCE
+
+subnet 172.16.128.0 netmask 255.255.255.0 {
+ range 172.16.128.10 172.16.128.50;
+ option domain-name-servers 172.16.0.1;
+ option routers 172.16.128.254;
+ option broadcast-address 172.16.128.255;
+ default-lease-time 86400;
+ max-lease-time 86400;
+}
diff --git a/roles/dhcp-ag/files/isc-dhcp-server b/roles/dhcp-ag/files/isc-dhcp-server
new file mode 100644
index 0000000..26ec0d9
--- /dev/null
+++ b/roles/dhcp-ag/files/isc-dhcp-server
@@ -0,0 +1,18 @@
+# Defaults for isc-dhcp-server (sourced by /etc/init.d/isc-dhcp-server)
+
+# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
+DHCPDv4_CONF=/etc/dhcp/dhcpd.conf
+#DHCPDv6_CONF=/etc/dhcp/dhcpd6.conf
+
+# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
+DHCPDv4_PID=/var/run/dhcpd.pid
+#DHCPDv6_PID=/var/run/dhcpd6.pid
+
+# Additional options to start dhcpd with.
+# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
+#OPTIONS=""
+
+# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
+# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
+INTERFACESv4="enp0s8"
+INTERFACESv6=""
diff --git a/roles/dhcp-ag/handlers/main.yml b/roles/dhcp-ag/handlers/main.yml
new file mode 100644
index 0000000..27f226d
--- /dev/null
+++ b/roles/dhcp-ag/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart dhcp
+ service: name=isc-dhcp-server state=restarted
diff --git a/roles/dhcp-ag/tasks/main.yml b/roles/dhcp-ag/tasks/main.yml
new file mode 100644
index 0000000..063a625
--- /dev/null
+++ b/roles/dhcp-ag/tasks/main.yml
@@ -0,0 +1,11 @@
+---
+ - name: Installation serveur dhcp
+ apt: name=isc-dhcp-server state=present update_cache=yes
+
+ - name: copie dhcpd.conf
+ copy: src=dhcpd.conf dest=/etc/dhcp
+ # notify: restart dhcp
+
+ - name: copie conf isc-dhcp-server
+ copy: src=isc-dhcp-server dest=/etc/default/isc-dhcp-server
+ # notify: restart dhcp
diff --git a/roles/dhcp-fog/files/dhcpd.conf b/roles/dhcp-fog/files/dhcpd.conf
new file mode 100644
index 0000000..4371dc6
--- /dev/null
+++ b/roles/dhcp-fog/files/dhcpd.conf
@@ -0,0 +1,142 @@
+#
+# Sample configuration file for ISC dhcpd for Debian
+#
+#
+
+# The ddns-updates-style parameter controls whether or not the server will
+# attempt to do a DNS update when a lease is confirmed. We default to the
+# behavior of the version 2 packages ('none', since DHCP v2 didn't
+# have support for DDNS.)
+ddns-update-style none;
+
+# option definitions common to all supported networks...
+option domain-name "gsb.lan";
+option domain-name-servers 172.16.0.1;
+
+default-lease-time 86400;
+max-lease-time 86400;
+
+# If this DHCP server is the official DHCP server for the local
+# network, the authoritative directive should be uncommented.
+#authoritative;
+
+# Use this to send dhcp log messages to a different log file (you also
+# have to hack syslog.conf to complete the redirection).
+log-facility local7;
+
+# No service will be given on this subnet, but declaring it helps the
+# DHCP server to understand the network topology.
+
+#subnet 10.152.187.0 netmask 255.255.255.0 {
+#}
+
+# This is a very basic subnet declaration.
+
+#subnet 10.254.239.0 netmask 255.255.255.224 {
+# range 10.254.239.10 10.254.239.20;
+# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
+#}
+
+# This declaration allows BOOTP clients to get dynamic addresses,
+# which we don't really recommend.
+
+#subnet 10.254.239.32 netmask 255.255.255.224 {
+# range dynamic-bootp 10.254.239.40 10.254.239.60;
+# option broadcast-address 10.254.239.31;
+# option routers rtr-239-32-1.example.org;
+#}
+
+# A slightly different configuration for an internal subnet.
+#subnet 10.5.5.0 netmask 255.255.255.224 {
+# range 10.5.5.26 10.5.5.30;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
+# Hosts which require special configuration options can be listed in
+# host statements. If no address is specified, the address will be
+# allocated dynamically (if possible), but the host-specific information
+# will still come from the host declaration.
+
+#host passacaglia {
+# hardware ethernet 0:0:c0:5d:bd:95;
+# filename "vmunix.passacaglia";
+# server-name "toccata.fugue.com";
+#}
+
+# Fixed IP addresses can also be specified for hosts. These addresses
+# should not also be listed as being available for dynamic assignment.
+# Hosts for which fixed IP addresses have been specified can boot using
+# BOOTP or DHCP. Hosts for which no fixed address is specified can only
+# be booted with DHCP, unless there is an address range on the subnet
+# to which a BOOTP client is connected which has the dynamic-bootp flag
+# set.
+#host fantasia {
+# hardware ethernet 08:00:07:26:c0:a5;
+# fixed-address fantasia.fugue.com;
+#}
+
+# You can declare a class of clients and then do address allocation
+# based on that. The example below shows a case where all clients
+# in a certain class get addresses on the 10.17.224/24 subnet, and all
+# other clients get addresses on the 10.0.29/24 subnet.
+
+#class "foo" {
+# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
+#}
+
+#shared-network 224-29 {
+# subnet 10.17.224.0 netmask 255.255.255.0 {
+# option routers rtr-224.example.org;
+# }
+# subnet 10.0.29.0 netmask 255.255.255.0 {
+# option routers rtr-29.example.org;
+# }
+# pool {
+# allow members of "foo";
+# range 10.17.224.10 10.17.224.250;
+# }
+# pool {
+# deny members of "foo";
+# range 10.0.29.10 10.0.29.230;
+# }
+#}
+
+#DHCP pour le réseau wifi
+#subnet 172.16.65.0 netmask 255.255.255.0 {
+# range 172.16.65.1 172.16.65.100;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
+#DHCP pour le réseau USER
+
+subnet 172.16.64.0 netmask 255.255.255.0 {
+ range 172.16.64.20 172.16.64.120;
+ option domain-name-servers 172.16.0.1 ;
+ option routers 172.16.64.254;
+ option broadcast-address 172.16.64.255;
+# default-lease-time 600;
+# max-lease-time 7200;
+}
+
+#DHCP pour le réseau INFRA
+
+#subnet 172.16.0.0 netmask 255.255.255.0 {
+# range 172.16.0.1 172.16.0.100;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
diff --git a/roles/dhcp-fog/files/isc-dhcp-server b/roles/dhcp-fog/files/isc-dhcp-server
new file mode 100644
index 0000000..a2f7704
--- /dev/null
+++ b/roles/dhcp-fog/files/isc-dhcp-server
@@ -0,0 +1,18 @@
+# Defaults for isc-dhcp-server (sourced by /etc/init.d/isc-dhcp-server)
+
+# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
+DHCPDv4_CONF=/etc/dhcp/dhcpd.conf
+#DHCPDv6_CONF=/etc/dhcp/dhcpd6.conf
+
+# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
+DHCPDv4_PID=/var/run/dhcpd.pid
+#DHCPDv6_PID=/var/run/dhcpd6.pid
+
+# Additional options to start dhcpd with.
+# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
+#OPTIONS=""
+
+# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
+# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
+INTERFACESv4="enp0s9"
+INTERFACESv6=""
diff --git a/roles/dhcp-fog/handlers/main.yml b/roles/dhcp-fog/handlers/main.yml
new file mode 100644
index 0000000..e2bb399
--- /dev/null
+++ b/roles/dhcp-fog/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart isc-dhcp-server
+ service: name=isc-dhcp-server state=restarted
diff --git a/roles/dhcp-fog/tasks/main.yml b/roles/dhcp-fog/tasks/main.yml
new file mode 100644
index 0000000..9b51946
--- /dev/null
+++ b/roles/dhcp-fog/tasks/main.yml
@@ -0,0 +1,14 @@
+---
+
+- name: Installation du dhcp
+ apt: name=isc-dhcp-server state=present
+
+- name: Copie du fichier isc-dhcp-server
+ copy: src=isc-dhcp-server dest=/etc/default/
+
+- name: Copie du fichier dhcpd.conf
+ copy: src=dhcpd.conf dest=/etc/dhcp/
+ notify:
+ - restart isc-dhcp-server
+
+
diff --git a/roles/dhcp/files/dhcpd.conf b/roles/dhcp/files/dhcpd.conf
new file mode 100644
index 0000000..0b565f1
--- /dev/null
+++ b/roles/dhcp/files/dhcpd.conf
@@ -0,0 +1,142 @@
+#
+# Sample configuration file for ISC dhcpd for Debian
+#
+#
+
+# The ddns-updates-style parameter controls whether or not the server will
+# attempt to do a DNS update when a lease is confirmed. We default to the
+# behavior of the version 2 packages ('none', since DHCP v2 didn't
+# have support for DDNS.)
+ddns-update-style none;
+
+# option definitions common to all supported networks...
+option domain-name "gsb.lan";
+option domain-name-servers 172.16.0.1;
+
+default-lease-time 86400;
+max-lease-time 86400;
+
+# If this DHCP server is the official DHCP server for the local
+# network, the authoritative directive should be uncommented.
+#authoritative;
+
+# Use this to send dhcp log messages to a different log file (you also
+# have to hack syslog.conf to complete the redirection).
+log-facility local7;
+
+# No service will be given on this subnet, but declaring it helps the
+# DHCP server to understand the network topology.
+
+#subnet 10.152.187.0 netmask 255.255.255.0 {
+#}
+
+# This is a very basic subnet declaration.
+
+#subnet 10.254.239.0 netmask 255.255.255.224 {
+# range 10.254.239.10 10.254.239.20;
+# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
+#}
+
+# This declaration allows BOOTP clients to get dynamic addresses,
+# which we don't really recommend.
+
+#subnet 10.254.239.32 netmask 255.255.255.224 {
+# range dynamic-bootp 10.254.239.40 10.254.239.60;
+# option broadcast-address 10.254.239.31;
+# option routers rtr-239-32-1.example.org;
+#}
+
+# A slightly different configuration for an internal subnet.
+#subnet 10.5.5.0 netmask 255.255.255.224 {
+# range 10.5.5.26 10.5.5.30;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+#}
+
+# Hosts which require special configuration options can be listed in
+# host statements. If no address is specified, the address will be
+# allocated dynamically (if possible), but the host-specific information
+# will still come from the host declaration.
+
+#host passacaglia {
+# hardware ethernet 0:0:c0:5d:bd:95;
+# filename "vmunix.passacaglia";
+# server-name "toccata.fugue.com";
+#}
+
+# Fixed IP addresses can also be specified for hosts. These addresses
+# should not also be listed as being available for dynamic assignment.
+# Hosts for which fixed IP addresses have been specified can boot using
+# BOOTP or DHCP. Hosts for which no fixed address is specified can only
+# be booted with DHCP, unless there is an address range on the subnet
+# to which a BOOTP client is connected which has the dynamic-bootp flag
+# set.
+#host fantasia {
+# hardware ethernet 08:00:07:26:c0:a5;
+# fixed-address fantasia.fugue.com;
+#}
+
+# You can declare a class of clients and then do address allocation
+# based on that. The example below shows a case where all clients
+# in a certain class get addresses on the 10.17.224/24 subnet, and all
+# other clients get addresses on the 10.0.29/24 subnet.
+
+#class "foo" {
+# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
+#}
+
+#shared-network 224-29 {
+# subnet 10.17.224.0 netmask 255.255.255.0 {
+# option routers rtr-224.example.org;
+# }
+# subnet 10.0.29.0 netmask 255.255.255.0 {
+# option routers rtr-29.example.org;
+# }
+# pool {
+# allow members of "foo";
+# range 10.17.224.10 10.17.224.250;
+# }
+# pool {
+# deny members of "foo";
+# range 10.0.29.10 10.0.29.230;
+# }
+#}
+
+#DHCP pour le réseau wifi
+subnet 172.16.65.0 netmask 255.255.255.0 {
+ range 172.16.65.1 172.16.65.100;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+}
+
+#DHCP pour le réseau USER
+
+subnet 172.16.64.0 netmask 255.255.255.0 {
+ range 172.16.64.20 172.16.64.120;
+ option domain-name-servers 172.16.0.1 ;
+ option routers 172.16.64.254;
+ option broadcast-address 172.16.64.255;
+# default-lease-time 600;
+# max-lease-time 7200;
+}
+
+#DHCP pour le réseau INFRA
+
+subnet 172.16.0.0 netmask 255.255.255.0 {
+# range 172.16.0.1 172.16.0.100;
+# option domain-name-servers ns1.internal.example.org;
+# option domain-name "internal.example.org";
+# option routers 10.5.5.1;
+# option broadcast-address 10.5.5.31;
+# default-lease-time 600;
+# max-lease-time 7200;
+}
+
diff --git a/roles/dhcp/files/isc-dhcp-server b/roles/dhcp/files/isc-dhcp-server
new file mode 100644
index 0000000..3930248
--- /dev/null
+++ b/roles/dhcp/files/isc-dhcp-server
@@ -0,0 +1,18 @@
+# Defaults for isc-dhcp-server (sourced by /etc/init.d/isc-dhcp-server)
+
+# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
+DHCPDv4_CONF=/etc/dhcp/dhcpd.conf
+#DHCPDv6_CONF=/etc/dhcp/dhcpd6.conf
+
+# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
+DHCPDv4_PID=/var/run/dhcpd.pid
+#DHCPDv6_PID=/var/run/dhcpd6.pid
+
+# Additional options to start dhcpd with.
+# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
+#OPTIONS=""
+
+# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
+# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
+INTERFACESv4="enp0s9 enp0s10"
+INTERFACESv6=""
diff --git a/roles/dhcp/handlers/main.yml b/roles/dhcp/handlers/main.yml
new file mode 100644
index 0000000..e2bb399
--- /dev/null
+++ b/roles/dhcp/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart isc-dhcp-server
+ service: name=isc-dhcp-server state=restarted
diff --git a/roles/dhcp/tasks/main.yml b/roles/dhcp/tasks/main.yml
new file mode 100644
index 0000000..9b51946
--- /dev/null
+++ b/roles/dhcp/tasks/main.yml
@@ -0,0 +1,14 @@
+---
+
+- name: Installation du dhcp
+ apt: name=isc-dhcp-server state=present
+
+- name: Copie du fichier isc-dhcp-server
+ copy: src=isc-dhcp-server dest=/etc/default/
+
+- name: Copie du fichier dhcpd.conf
+ copy: src=dhcpd.conf dest=/etc/dhcp/
+ notify:
+ - restart isc-dhcp-server
+
+
diff --git a/roles/dns-ag-cs/files/named.conf.options b/roles/dns-ag-cs/files/named.conf.options
new file mode 100644
index 0000000..d0daf3f
--- /dev/null
+++ b/roles/dns-ag-cs/files/named.conf.options
@@ -0,0 +1,23 @@
+// 0.2 - putconf - vendredi 12 avril 2013, 08:54:33 (UTC+0200)
+
+options {
+ directory "/var/cache/bind";
+
+ // If there is a firewall between you and nameservers you want
+ // to talk to, you may need to fix the firewall to allow multiple
+ // ports to talk. See http://www.kb.cert.org/vuls/id/800113
+
+ // If your ISP provided one or more IP addresses for stable
+ // nameservers, you probably want to use them as forwarders.
+ // Uncomment the following block, and insert the addresses replacing
+ // the all-0's placeholder.
+
+ forwarders {
+ 172.16.0.1;
+
+ };
+
+ auth-nxdomain no; # conform to RFC1035
+ listen-on-v6 { any; };
+};
+
diff --git a/roles/dns-ag-cs/handlers/main.yml b/roles/dns-ag-cs/handlers/main.yml
new file mode 100644
index 0000000..33d4f98
--- /dev/null
+++ b/roles/dns-ag-cs/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+ - name: restart bind9
+ service: name=bind9 state=restarted
+
diff --git a/roles/dns-ag-cs/tasks/main.yml b/roles/dns-ag-cs/tasks/main.yml
new file mode 100644
index 0000000..d3a88a6
--- /dev/null
+++ b/roles/dns-ag-cs/tasks/main.yml
@@ -0,0 +1,11 @@
+---
+
+- name: Installation bind9
+ apt: name=bind9 state=present update_cache=yes
+
+- name: Copie named.conf.options
+ copy: src=named.conf.options dest=/etc/bind
+ notify:
+ - restart bind9
+
+
diff --git a/roles/dns-agence/files/named.conf.options b/roles/dns-agence/files/named.conf.options
new file mode 100644
index 0000000..d0daf3f
--- /dev/null
+++ b/roles/dns-agence/files/named.conf.options
@@ -0,0 +1,23 @@
+// 0.2 - putconf - vendredi 12 avril 2013, 08:54:33 (UTC+0200)
+
+options {
+ directory "/var/cache/bind";
+
+ // If there is a firewall between you and nameservers you want
+ // to talk to, you may need to fix the firewall to allow multiple
+ // ports to talk. See http://www.kb.cert.org/vuls/id/800113
+
+ // If your ISP provided one or more IP addresses for stable
+ // nameservers, you probably want to use them as forwarders.
+ // Uncomment the following block, and insert the addresses replacing
+ // the all-0's placeholder.
+
+ forwarders {
+ 172.16.0.1;
+
+ };
+
+ auth-nxdomain no; # conform to RFC1035
+ listen-on-v6 { any; };
+};
+
diff --git a/roles/dns-agence/handlers/main.yml b/roles/dns-agence/handlers/main.yml
new file mode 100644
index 0000000..33d4f98
--- /dev/null
+++ b/roles/dns-agence/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+ - name: restart bind9
+ service: name=bind9 state=restarted
+
diff --git a/roles/dns-agence/tasks/main.yml b/roles/dns-agence/tasks/main.yml
new file mode 100644
index 0000000..d3a88a6
--- /dev/null
+++ b/roles/dns-agence/tasks/main.yml
@@ -0,0 +1,11 @@
+---
+
+- name: Installation bind9
+ apt: name=bind9 state=present update_cache=yes
+
+- name: Copie named.conf.options
+ copy: src=named.conf.options dest=/etc/bind
+ notify:
+ - restart bind9
+
+
diff --git a/roles/dns-master/files/db.gsb.lan b/roles/dns-master/files/db.gsb.lan
new file mode 100644
index 0000000..0dbcd49
--- /dev/null
+++ b/roles/dns-master/files/db.gsb.lan
@@ -0,0 +1,30 @@
+; 0.2 - putconf - vendredi 12 avril 2013, 08:54:33 (UTC+0200)
+
+;
+; BIND data file for local loopback interface
+;
+$TTL 604800
+@ IN SOA s-infra.gsb.lan. root.s-infra.gsb.lan. (
+ 2016011401 ; Serial
+ 7200 ; Refresh
+ 86400 ; Retry
+ 8419200 ; Expire
+ 604800 ) ; Negative Cache TTL
+;
+@ IN NS s-infra.gsb.lan.
+@ IN NS s-backup.gsb.lan.
+@ IN A 127.0.0.1
+@ IN AAAA ::1
+s-infra IN A 172.16.0.1
+s-backup IN A 172.16.0.4
+s-proxy IN A 172.16.0.2
+s-appli IN A 172.16.0.3
+s-win IN A 172.16.0.6
+s-mess IN A 172.16.0.7
+s-mon IN A 172.16.0.8
+s-itil IN A 172.16.0.9
+r-int IN A 172.16.0.254
+r-int-lnk IN A 192.168.200.254
+r-ext IN A 192.168.200.253
+ns IN CNAME s-infra.gsb.lan.
+wpad IN CNAME s-infra.gsb.lan.
diff --git a/roles/dns-master/files/db.gsb.lan.rev b/roles/dns-master/files/db.gsb.lan.rev
new file mode 100644
index 0000000..43b480e
--- /dev/null
+++ b/roles/dns-master/files/db.gsb.lan.rev
@@ -0,0 +1,24 @@
+; 0.2 - putconf - vendredi 12 avril 2013, 08:54:33 (UTC+0200)
+
+;
+; BIND data file for local loopback interface
+;
+$TTL 604800
+@ IN SOA s-infra.gsb.lan. root.s-infra.gsb.lan. (
+ 2015121701 ; Serial
+ 7200 ; Refresh
+ 86400 ; Retry
+ 8419200 ; Expire
+ 604800 ) ; Negative Cache TTL
+;
+@ IN NS s-infra.gsb.lan.
+@ IN NS s-backup.gsb.lan.
+1.0 IN PTR s-infra.gsb.lan.
+4.0 IN PTR s-backup.gsb.lan.
+2.0 IN PTR s-proxy.gsb.lan.
+3.0 IN PTR s-appli.gsb.lan.
+6.0 IN PTR s-win.gsb.lan.
+7.0 IN PTR s-mess.gsb.lan.
+8.0 IN PTR s-mon.gsb.lan.
+9.0 IN PTR s-itil.gsb.lan.
+254.0 IN PTR r-int.gsb.lan.
diff --git a/roles/dns-master/files/forbidden.html b/roles/dns-master/files/forbidden.html
new file mode 100644
index 0000000..648fafc
--- /dev/null
+++ b/roles/dns-master/files/forbidden.html
@@ -0,0 +1,2 @@
+<center><img src="http://sio.lyc-lecastel.fr/~nicolas.denizot/warning.jpg" alt="Bloque"></img></center>
+<center><h1>Vous n'avez pas les droits requis pour acceder a cette page, veuillez contacter votre Administrateur.</h1></center>
diff --git a/roles/dns-master/files/hosts b/roles/dns-master/files/hosts
new file mode 100644
index 0000000..3c35fbd
--- /dev/null
+++ b/roles/dns-master/files/hosts
@@ -0,0 +1,7 @@
+127.0.0.1 localhost
+127.0.1.1 s-infra
+
+# The following lines are desirable for IPv6 capable hosts
+::1 localhost ip6-localhost ip6-loopback
+ff02::1 ip6-allnodes
+ff02::2 ip6-allrouters
diff --git a/roles/dns-master/files/named.conf.local b/roles/dns-master/files/named.conf.local
new file mode 100644
index 0000000..28e3aaa
--- /dev/null
+++ b/roles/dns-master/files/named.conf.local
@@ -0,0 +1,20 @@
+// 0.2 - putconf - vendredi 12 avril 2013, 08:54:33 (UTC+0200)
+
+//
+// Do any local configuration here
+//
+
+// Consider adding the 1918 zones here, if they are not used in your
+// organization
+//include "/etc/bind/zones.rfc1918";
+
+zone "gsb.lan" {
+ type master;
+ file "/etc/bind/db.gsb.lan";
+};
+
+zone "16.172.in-addr.arpa"{
+ type master;
+ notify no;
+ file "/etc/bind/db.gsb.lan.rev";
+};
diff --git a/roles/dns-master/files/named.conf.options b/roles/dns-master/files/named.conf.options
new file mode 100644
index 0000000..ca26456
--- /dev/null
+++ b/roles/dns-master/files/named.conf.options
@@ -0,0 +1,25 @@
+// 0.2 - putconf - vendredi 12 avril 2013, 08:54:33 (UTC+0200)
+
+options {
+ directory "/var/cache/bind";
+
+ // If there is a firewall between you and nameservers you want
+ // to talk to, you may need to fix the firewall to allow multiple
+ // ports to talk. See http://www.kb.cert.org/vuls/id/800113
+
+ // If your ISP provided one or more IP addresses for stable
+ // nameservers, you probably want to use them as forwarders.
+ // Uncomment the following block, and insert the addresses replacing
+ // the all-0's placeholder.
+
+ forwarders {
+ 192.168.99.99;
+
+ };
+
+ auth-nxdomain no; # conform to RFC1035
+ listen-on-v6 { any; };
+ allow-query { 172.16.0.0/16; } ;
+ allow-recursion { 172.16.0.0/16; } ;
+};
+
diff --git a/roles/dns-master/files/resolv.conf b/roles/dns-master/files/resolv.conf
new file mode 100644
index 0000000..13b8bd5
--- /dev/null
+++ b/roles/dns-master/files/resolv.conf
@@ -0,0 +1,4 @@
+domain gsb.lan
+search gsb.lan
+nameserver 127.0.0.1
+
diff --git a/roles/dns-master/handlers/main.yml b/roles/dns-master/handlers/main.yml
new file mode 100644
index 0000000..33d4f98
--- /dev/null
+++ b/roles/dns-master/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+ - name: restart bind9
+ service: name=bind9 state=restarted
+
diff --git a/roles/dns-master/tasks/main.yml b/roles/dns-master/tasks/main.yml
new file mode 100644
index 0000000..e8e3598
--- /dev/null
+++ b/roles/dns-master/tasks/main.yml
@@ -0,0 +1,33 @@
+---
+
+- name: Installation bind9
+ apt: name=bind9 state=present update_cache=yes
+
+- name: Copie named.conf.options
+ copy: src=named.conf.options dest=/etc/bind
+ notify:
+ - restart bind9
+
+- name: Copie named.conf.local
+ copy: src=named.conf.local dest=/etc/bind
+ notify:
+ - restart bind9
+
+- name: Copie db.gsb.lan
+ copy: src=db.gsb.lan dest=/etc/bind
+ notify:
+ - restart bind9
+
+- name: Copie db.gsb.lan.rev
+ copy: src=db.gsb.lan.rev dest=/etc/bind
+ notify:
+ - restart bind9
+
+- name: Copie resolv.conf
+ copy: src=resolv.conf dest=/etc
+ notify:
+ - restart bind9
+
+- name: Copie page squidguard
+ copy: src=forbidden.html dest=/var/www/
+
diff --git a/roles/dnsmasq/files/dnsmasq.conf b/roles/dnsmasq/files/dnsmasq.conf
new file mode 100644
index 0000000..bb3077c
--- /dev/null
+++ b/roles/dnsmasq/files/dnsmasq.conf
@@ -0,0 +1,531 @@
+# Configuration file for dnsmasq.
+#
+# Format is one option per line, legal options are the same
+# as the long options legal on the command line. See
+# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.
+
+# Listen on this specific port instead of the standard DNS port
+# (53). Setting this to zero completely disables DNS function,
+# leaving only DHCP and/or TFTP.
+#port=5353
+
+# The following two options make you a better netizen, since they
+# tell dnsmasq to filter out queries which the public DNS cannot
+# answer, and which load the servers (especially the root servers)
+# unnecessarily. If you have a dial-on-demand link they also stop
+# these requests from bringing up the link unnecessarily.
+
+# Never forward plain names (without a dot or domain part)
+#domain-needed
+# Never forward addresses in the non-routed address spaces.
+#bogus-priv
+
+# Uncomment these to enable DNSSEC validation and caching:
+# (Requires dnsmasq to be built with DNSSEC option.)
+#conf-file=%%PREFIX%%/share/dnsmasq/trust-anchors.conf
+#dnssec
+
+# Replies which are not DNSSEC signed may be legitimate, because the domain
+# is unsigned, or may be forgeries. Setting this option tells dnsmasq to
+# check that an unsigned reply is OK, by finding a secure proof that a DS
+# record somewhere between the root and the domain does not exist.
+# The cost of setting this is that even queries in unsigned domains will need
+# one or more extra DNS queries to verify.
+#dnssec-check-unsigned
+
+# Uncomment this to filter useless windows-originated DNS requests
+# which can trigger dial-on-demand links needlessly.
+# Note that (amongst other things) this blocks all SRV requests,
+# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
+# This option only affects forwarding, SRV records originating for
+# dnsmasq (via srv-host= lines) are not suppressed by it.
+#filterwin2k
+
+# Change this line if you want dns to get its upstream servers from
+# somewhere other that /etc/resolv.conf
+#resolv-file=
+
+# By default, dnsmasq will send queries to any of the upstream
+# servers it knows about and tries to favour servers to are known
+# to be up. Uncommenting this forces dnsmasq to try each query
+# with each server strictly in the order they appear in
+# /etc/resolv.conf
+#strict-order
+
+# If you don't want dnsmasq to read /etc/resolv.conf or any other
+# file, getting its servers from this file instead (see below), then
+# uncomment this.
+#no-resolv
+
+# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
+# files for changes and re-read them then uncomment this.
+#no-poll
+
+# Add other name servers here, with domain specs if they are for
+# non-public domains.
+#server=/localnet/192.168.0.1
+
+# Example of routing PTR queries to nameservers: this will send all
+# address->name queries for 192.168.3/24 to nameserver 10.1.2.3
+#server=/3.168.192.in-addr.arpa/10.1.2.3
+
+# Add local-only domains here, queries in these domains are answered
+# from /etc/hosts or DHCP only.
+#local=/localnet/
+
+# Add domains which you want to force to an IP address here.
+# The example below send any host in double-click.net to a local
+# web-server.
+#address=/double-click.net/127.0.0.1
+
+# --address (and --server) work with IPv6 addresses too.
+#address=/www.thekelleys.org.uk/fe80::20d:60ff:fe36:f83
+
+# Add the IPs of all queries to yahoo.com, google.com, and their
+# subdomains to the vpn and search ipsets:
+#ipset=/yahoo.com/google.com/vpn,search
+
+# You can control how dnsmasq talks to a server: this forces
+# queries to 10.1.2.3 to be routed via enp0s8
+# server=10.1.2.3@enp0s8
+
+# and this sets the source (ie local) address used to talk to
+# 10.1.2.3 to 192.168.1.1 port 55 (there must be a interface with that
+# IP on the machine, obviously).
+# server=10.1.2.3@192.168.1.1#55
+
+# If you want dnsmasq to change uid and gid to something other
+# than the default, edit the following lines.
+#user=
+#group=
+
+# If you want dnsmasq to listen for DHCP and DNS requests only on
+# specified interfaces (and the loopback) give the name of the
+# interface (eg enp0s3) here.
+# Repeat the line for more than one interface.
+interface=enp0s8
+# Or you can specify which interface _not_ to listen on
+#except-interface=
+# Or which to listen on by address (remember to include 127.0.0.1 if
+# you use this.)
+#listen-address=
+# If you want dnsmasq to provide only DNS service on an interface,
+# configure it as shown above, and then use the following line to
+# disable DHCP and TFTP on it.
+#no-dhcp-interface=enp0s3
+
+# On systems which support it, dnsmasq binds the wildcard address,
+# even when it is listening on only some interfaces. It then discards
+# requests that it shouldn't reply to. This has the advantage of
+# working even when interfaces come and go and change address. If you
+# want dnsmasq to really bind only the interfaces it is listening on,
+# uncomment this option. About the only time you may need this is when
+# running another nameserver on the same machine.
+#bind-interfaces
+
+# If you don't want dnsmasq to read /etc/hosts, uncomment the
+# following line.
+#no-hosts
+# or if you want it to read another file, as well as /etc/hosts, use
+# this.
+#addn-hosts=/etc/banner_add_hosts
+
+# Set this (and domain: see below) if you want to have a domain
+# automatically added to simple names in a hosts-file.
+#expand-hosts
+
+# Set the domain for dnsmasq. this is optional, but if it is set, it
+# does the following things.
+# 1) Allows DHCP hosts to have fully qualified domain names, as long
+# as the domain part matches this setting.
+# 2) Sets the "domain" DHCP option thereby potentially setting the
+# domain of all systems configured by DHCP
+# 3) Provides the domain part for "expand-hosts"
+#domain=thekelleys.org.uk
+
+# Set a different domain for a particular subnet
+#domain=wireless.thekelleys.org.uk,192.168.2.0/24
+
+# Same idea, but range rather then subnet
+#domain=reserved.thekelleys.org.uk,192.68.3.100,192.168.3.200
+
+# Uncomment this to enable the integrated DHCP server, you need
+# to supply the range of addresses available for lease and optionally
+# a lease time. If you have more than one network, you will need to
+# repeat this for each network on which you want to supply DHCP
+# service.
+#dhcp-range=192.168.0.50,192.168.0.150,12h
+
+# This is an example of a DHCP range where the netmask is given. This
+# is needed for networks we reach the dnsmasq DHCP server via a relay
+# agent. If you don't know what a DHCP relay agent is, you probably
+# don't need to worry about this.
+#dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
+dhcp-range=192.168.99.100,192.168.99.120,255.255.255.0,12h
+
+# This is an example of a DHCP range which sets a tag, so that
+# some DHCP options may be set only for this network.
+#dhcp-range=set:red,192.168.0.50,192.168.0.150
+
+# Use this DHCP range only when the tag "green" is set.
+#dhcp-range=tag:green,192.168.0.50,192.168.0.150,12h
+
+# Specify a subnet which can't be used for dynamic address allocation,
+# is available for hosts with matching --dhcp-host lines. Note that
+# dhcp-host declarations will be ignored unless there is a dhcp-range
+# of some type for the subnet in question.
+# In this case the netmask is implied (it comes from the network
+# configuration on the machine running dnsmasq) it is possible to give
+# an explicit netmask instead.
+#dhcp-range=192.168.0.0,static
+
+# Enable DHCPv6. Note that the prefix-length does not need to be specified
+# and defaults to 64 if missing/
+#dhcp-range=1234::2, 1234::500, 64, 12h
+
+# Do Router Advertisements, BUT NOT DHCP for this subnet.
+#dhcp-range=1234::, ra-only
+
+# Do Router Advertisements, BUT NOT DHCP for this subnet, also try and
+# add names to the DNS for the IPv6 address of SLAAC-configured dual-stack
+# hosts. Use the DHCPv4 lease to derive the name, network segment and
+# MAC address and assume that the host will also have an
+# IPv6 address calculated using the SLAAC alogrithm.
+#dhcp-range=1234::, ra-names
+
+# Do Router Advertisements, BUT NOT DHCP for this subnet.
+# Set the lifetime to 46 hours. (Note: minimum lifetime is 2 hours.)
+#dhcp-range=1234::, ra-only, 48h
+
+# Do DHCP and Router Advertisements for this subnet. Set the A bit in the RA
+# so that clients can use SLAAC addresses as well as DHCP ones.
+#dhcp-range=1234::2, 1234::500, slaac
+
+# Do Router Advertisements and stateless DHCP for this subnet. Clients will
+# not get addresses from DHCP, but they will get other configuration information.
+# They will use SLAAC for addresses.
+#dhcp-range=1234::, ra-stateless
+
+# Do stateless DHCP, SLAAC, and generate DNS names for SLAAC addresses
+# from DHCPv4 leases.
+#dhcp-range=1234::, ra-stateless, ra-names
+
+# Do
+# default (1, 3, 6, 12, 28) the same line will send a zero-length option
+# for all other option numbers.
+#dhcp-option=3
+
+# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
+#dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5
+
+# Send DHCPv6 option. Note [] around IPv6 addresses.
+#dhcp-option=option6:dns-server,[1234::77],[1234::88]
+
+# Send DHCPv6 option for namservers as the machine running
+# dnsmasq and another.
+#dhcp-option=option6:dns-server,[::],[1234::88]
+
+# Ask client to poll for option changes every six hours. (RFC4242)
+#dhcp-option=option6:information-refresh-time,6h
+
+# Set the NTP time server address to be the same machine as
+# is running dnsmasq
+#dhcp-option=42,0.0.0.0
+
+# Set the NIS domain name to "welly"
+#dhcp-option=40,welly
+
+# Set the default time-to-live to 50
+#dhcp-option=23,50
+
+# Set the "all subnets are local" flag
+#dhcp-option=27,1
+
+# Send the etherboot magic flag and then etherboot options (a string).
+#dhcp-option=128,e4:45:74:68:00:00
+#dhcp-option=129,NIC=eepro100
+
+# Specify an option which will only be sent to the "red" network
+# (see dhcp-range for the declaration of the "red" network)
+# Note that the tag: part must precede the option: part.
+#dhcp-option = tag:red, option:ntp-server, 192.168.1.1
+
+# The following DHCP options set up dnsmasq in the same way as is specified
+# for the ISC dhcpcd in
+# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
+# adapted for a typical dnsmasq installation where the host running
+# dnsmasq is also the host running samba.
+# you may want to uncomment some or all of them if you use
+# Windows clients and Samba.
+#dhcp-option=19,0 # option ip-forwarding off
+#dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
+#dhcp-option=45,0.0.0.0 # netbios datagram distribution server
+#dhcp-option=46,8 # netbios node type
+
+# Send an empty WPAD option. This may be REQUIRED to get windows 7 to behave.
+#dhcp-option=252,"\n"
+
+# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
+# probably doesn't support this......
+#dhcp-option=option:domain-search,eng.apple.com,marketing.apple.com
+
+# Send RFC-3442 classless static routes (note the netmask encoding)
+#dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8
+
+# Send vendor-class specific options encapsulated in DHCP option 43.
+# The meaning of the options is defined by the vendor-class so
+# options are sent only when the client supplied vendor class
+# matches the class given here. (A substring match is OK, so "MSFT"
+# matches "MSFT" and "MSFT 5.0"). This example sets the
+# mtftp address to 0.0.0.0 for PXEClients.
+#dhcp-option=vendor:PXEClient,1,0.0.0.0
+
+# Send microsoft-specific option to tell windows to release the DHCP lease
+# when it shuts down. Note the "i" flag, to tell dnsmasq to send the
+# value as a four-byte integer - that's what microsoft wants. See
+# http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true
+#dhcp-option=vendor:MSFT,2,1i
+
+# Send the Encapsulated-vendor-class ID needed by some configurations of
+# Etherboot to allow is to recognise the DHCP server.
+#dhcp-option=vendor:Etherboot,60,"Etherboot"
+
+# Send options to PXELinux. Note that we need to send the options even
+# though they don't appear in the parameter request list, so we need
+# to use dhcp-option-force here.
+# See http://syslinux.zytor.com/pxe.php#special for details.
+# Magic number - needed before anything else is recognised
+#dhcp-option-force=208,f1:00:74:7e
+# Configuration file name
+#dhcp-option-force=209,configs/common
+# Path prefix
+#dhcp-option-force=210,/tftpboot/pxelinux/files/
+# Reboot time. (Note 'i' to send 32-bit value)
+#dhcp-option-force=211,30i
+
+# Set the boot filename for netboot/PXE. You will only need
+# this is you want to boot machines over the network and you will need
+# a TFTP server; either dnsmasq's built in TFTP server or an
+# external one. (See below for how to enable the TFTP server.)
+#dhcp-boot=pxelinux.0
+
+# The same as above, but use custom tftp-server instead machine running dnsmasq
+#dhcp-boot=pxelinux,server.name,192.168.1.100
+
+# Boot for Etherboot gPXE. The idea is to send two different
+# filenames, the first loads gPXE, and the second tells gPXE what to
+# load. The dhcp-match sets the gpxe tag for requests from gPXE.
+#dhcp-match=set:gpxe,175 # gPXE sends a 175 option.
+#dhcp-boot=tag:!gpxe,undionly.kpxe
+#dhcp-boot=mybootimage
+
+# Encapsulated options for Etherboot gPXE. All the options are
+# encapsulated within option 175
+#dhcp-option=encap:175, 1, 5b # priority code
+#dhcp-option=encap:175, 176, 1b # no-proxydhcp
+#dhcp-option=encap:175, 177, string # bus-id
+#dhcp-option=encap:175, 189, 1b # BIOS drive code
+#dhcp-option=encap:175, 190, user # iSCSI username
+#dhcp-option=encap:175, 191, pass # iSCSI password
+
+# Test for the architecture of a netboot client. PXE clients are
+# supposed to send their architecture as option 93. (See RFC 4578)
+#dhcp-match=peecees, option:client-arch, 0 #x86-32
+#dhcp-match=itanics, option:client-arch, 2 #IA64
+#dhcp-match=hammers, option:client-arch, 6 #x86-64
+#dhcp-match=mactels, option:client-arch, 7 #EFI x86-64
+
+# Do real PXE, rather than just booting a single file, this is an
+# alternative to dhcp-boot.
+#pxe-prompt="What system shall I netboot?"
+# or with timeout before first available action is taken:
+#pxe-prompt="Press F8 for menu.", 60
+
+# Available boot services. for PXE.
+#pxe-service=x86PC, "Boot from local disk"
+
+# Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
+#pxe-service=x86PC, "Install Linux", pxelinux
+
+# Loads <tftp-root>/pxelinux.0 from TFTP server at 1.2.3.4.
+# Beware this fails on old PXE ROMS.
+#pxe-service=x86PC, "Install Linux", pxelinux, 1.2.3.4
+
+# Use bootserver on network, found my multicast or broadcast.
+#pxe-service=x86PC, "Install windows from RIS server", 1
+
+# Use bootserver at a known IP address.
+#pxe-service=x86PC, "Install windows from RIS server", 1, 1.2.3.4
+
+# If you have multicast-FTP available,
+# information for that can be passed in a similar way using options 1
+# to 5. See page 19 of
+# http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
+
+
+# Enable dnsmasq's built-in TFTP server
+#enable-tftp
+
+# Set the root directory for files available via FTP.
+#tftp-root=/var/ftpd
+
+# Make the TFTP server more secure: with this set, only files owned by
+# the user dnsmasq is running as will be send over the net.
+#tftp-secure
+
+# This option stops dnsmasq from negotiating a larger blocksize for TFTP
+# transfers. It will slow things down, but may rescue some broken TFTP
+# clients.
+#tftp-no-blocksize
+
+# Set the boot file name only when the "red" tag is set.
+#dhcp-boot=tag:red,pxelinux.red-net
+
+# An example of dhcp-boot with an external TFTP server: the name and IP
+# address of the server are given after the filename.
+# Can fail with old PXE ROMS. Overridden by --pxe-service.
+#dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3
+
+# If there are multiple external tftp servers having a same name
+# (using /etc/hosts) then that name can be specified as the
+# tftp_servername (the third option to dhcp-boot) and in that
+# case dnsmasq resolves this name and returns the resultant IP
+# addresses in round robin fasion. This facility can be used to
+# load balance the tftp load among a set of servers.
+#dhcp-boot=/var/ftpd/pxelinux.0,boothost,tftp_server_name
+
+# Set the limit on DHCP leases, the default is 150
+#dhcp-lease-max=150
+
+# The DHCP server needs somewhere on disk to keep its lease database.
+# This defaults to a sane location, but if you want to change it, use
+# the line below.
+#dhcp-leasefile=/var/lib/misc/dnsmasq.leases
+
+# Set the DHCP server to authoritative mode. In this mode it will barge in
+# and take over the lease for any client which broadcasts on the network,
+# whether it has a record of the lease or not. This avoids long timeouts
+# when a machine wakes up on a new network. DO NOT enable this if there's
+# the slightest chance that you might end up accidentally configuring a DHCP
+# server for your campus/company accidentally. The ISC server uses
+# the same option, and this URL provides more information:
+# http://www.isc.org/files/auth.html
+#dhcp-authoritative
+
+# Run an executable when a DHCP lease is created or destroyed.
+# The arguments sent to the script are "add" or "del",
+# then the MAC address, the IP address and finally the hostname
+# if there is one.
+#dhcp-script=/bin/echo
+
+# Set the cachesize here.
+#cache-size=150
+
+# If you want to disable negative caching, uncomment this.
+#no-negcache
+
+# Normally responses which come from /etc/hosts and the DHCP lease
+# file have Time-To-Live set as zero, which conventionally means
+# do not cache further. If you are happy to trade lower load on the
+# server for potentially stale date, you can set a time-to-live (in
+# seconds) here.
+#local-ttl=
+
+# If you want dnsmasq to detect attempts by Verisign to send queries
+# to unregistered .com and .net hosts to its sitefinder service and
+# have dnsmasq instead return the correct NXDOMAIN response, uncomment
+# this line. You can add similar lines to do the same for other
+# registries which have implemented wildcard A records.
+#bogus-nxdomain=64.94.110.11
+
+# If you want to fix up DNS results from upstream servers, use the
+# alias option. This only works for IPv4.
+# This alias makes a result of 1.2.3.4 appear as 5.6.7.8
+#alias=1.2.3.4,5.6.7.8
+# and this maps 1.2.3.x to 5.6.7.x
+#alias=1.2.3.0,5.6.7.0,255.255.255.0
+# and this maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
+#alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
+
+# Change these lines if you want dnsmasq to serve MX records.
+
+# Return an MX record named "maildomain.com" with target
+# servermachine.com and preference 50
+#mx-host=maildomain.com,servermachine.com,50
+
+# Set the default target for MX records created using the localmx option.
+#mx-target=servermachine.com
+
+# Return an MX record pointing to the mx-target for all local
+# machines.
+#localmx
+
+# Return an MX record pointing to itself for all local machines.
+#selfmx
+
+# Change the following lines if you want dnsmasq to serve SRV
+# records. These are useful if you want to serve ldap requests for
+# Active Directory and other windows-originated DNS requests.
+# See RFC 2782.
+# You may add multiple srv-host lines.
+# The fields are <name>,<target>,<port>,<priority>,<weight>
+# If the domain part if missing from the name (so that is just has the
+# service and protocol sections) then the domain given by the domain=
+# config option is used. (Note that expand-hosts does not need to be
+# set for this to work.)
+
+# A SRV record sending LDAP for the example.com domain to
+# ldapserver.example.com port 389
+#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389
+
+# A SRV record sending LDAP for the example.com domain to
+# ldapserver.example.com port 389 (using domain=)
+#domain=example.com
+#srv-host=_ldap._tcp,ldapserver.example.com,389
+
+# Two SRV records for LDAP, each with different priorities
+#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
+#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2
+
+# A SRV record indicating that there is no LDAP server for the domain
+# example.com
+#srv-host=_ldap._tcp.example.com
+
+# The following line shows how to make dnsmasq serve an arbitrary PTR
+# record. This is useful for DNS-SD. (Note that the
+# domain-name expansion done for SRV records _does_not
+# occur for PTR records.)
+#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
+
+# Change the following lines to enable dnsmasq to serve TXT records.
+# These are used for things like SPF and zeroconf. (Note that the
+# domain-name expansion done for SRV records _does_not
+# occur for TXT records.)
+
+#Example SPF.
+#txt-record=example.com,"v=spf1 a -all"
+
+#Example zeroconf
+#txt-record=_http._tcp.example.com,name=value,paper=A4
+
+# Provide an alias for a "local" DNS name. Note that this _only_ works
+# for targets which are names from DHCP or /etc/hosts. Give host
+# "bert" another name, bertrand
+#cname=bertand,bert
+
+# For debugging purposes, log each DNS query as it passes through
+# dnsmasq.
+#log-queries
+
+# Log lots of extra information about DHCP transactions.
+#log-dhcp
+
+# Include another lot of configuration options.
+#conf-file=/etc/dnsmasq.more.conf
+#conf-dir=/etc/dnsmasq.d
+
+# Include all the files in a directory except those ending in .bak
+#conf-dir=/etc/dnsmasq.d,.bak
+
+# Include all files in a directory which end in .conf
+#conf-dir=/etc/dnsmasq.d/*.conf
diff --git a/roles/dnsmasq/handlers/main.yml b/roles/dnsmasq/handlers/main.yml
new file mode 100644
index 0000000..a9d7c7f
--- /dev/null
+++ b/roles/dnsmasq/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart dnsmasq
+ service: name=dnsmasq state=restarted
diff --git a/roles/dnsmasq/tasks/main.yml b/roles/dnsmasq/tasks/main.yml
new file mode 100644
index 0000000..0a8132e
--- /dev/null
+++ b/roles/dnsmasq/tasks/main.yml
@@ -0,0 +1,11 @@
+---
+
+- name: Installation dnsmasq
+ apt: name=dnsmasq state=present
+
+- name: Copie du fichier dnsmasq.conf
+ copy: src=dnsmasq.conf dest=/etc/
+ notify:
+ - restart dnsmasq
+
+
diff --git a/roles/docker-graylog-pont/files/docker-compose.yml b/roles/docker-graylog-pont/files/docker-compose.yml
new file mode 100644
index 0000000..b9bce7f
--- /dev/null
+++ b/roles/docker-graylog-pont/files/docker-compose.yml
@@ -0,0 +1,44 @@
+version: '2'
+services:
+ # MongoDB: https://hub.docker.com/_/mongo/
+ mongodb:
+ image: mongo:3
+ # Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/6.x/docker.html
+ elasticsearch:
+ image: docker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
+ environment:
+ - http.host=192.168.0.50
+ - transport.host=localhost
+ - network.host=0.0.0.0
+ - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
+ ulimits:
+ memlock:
+ soft: -1
+ hard: -1
+ mem_limit: 1g
+ # Graylog: https://hub.docker.com/r/graylog/graylog/
+ graylog:
+ image: graylog/graylog:2.5
+ environment:
+ # CHANGE ME!
+ - GRAYLOG_PASSWORD_SECRET=somepasswordpepper
+ # Password: admin
+ - GRAYLOG_ROOT_PASSWORD_SHA2=8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
+ - GRAYLOG_WEB_ENDPOINT_URI=http://127.0.0.1:9000/api
+ links:
+ - mongodb:mongo
+ - elasticsearch
+ depends_on:
+ - mongodb
+ - elasticsearch
+ ports:
+ # Graylog web interface and REST API
+ - 9000:9000
+ # Syslog TCP
+ - 515:514
+ # Syslog UDP
+ - 515:514/udp
+ # GELF TCP
+ - 12201:12201
+ # GELF UDP
+ - 12201:12201/udp
\ No newline at end of file
diff --git a/roles/docker-graylog-pont/files/fstab b/roles/docker-graylog-pont/files/fstab
new file mode 100644
index 0000000..c86a33e
--- /dev/null
+++ b/roles/docker-graylog-pont/files/fstab
@@ -0,0 +1,13 @@
+# /etc/fstab: static file system information.
+#
+# Use 'blkid' to print the universally unique identifier for a
+# device; this may be used with UUID= as a more robust way to name devices
+# that works even if disks are added and removed. See fstab(5).
+#
+# <file system> <mount point> <type> <options> <dump> <pass>
+/dev/mapper/stretch64--vg-root / ext4 errors=remount-ro 0 1
+# /boot was on /dev/sda1 during installation
+UUID=8f340ef0-94a1-4730-8da3-81ce5e38d666 /boot ext2 defaults 0 2
+/dev/mapper/stretch64--vg-swap_1 none swap sw 0 0
+/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
+/dev/sdb1 /var/lib/containers ext4 defaults 0 0
\ No newline at end of file
diff --git a/roles/docker-graylog-pont/files/https_proxy.conf b/roles/docker-graylog-pont/files/https_proxy.conf
new file mode 100644
index 0000000..18e9112
--- /dev/null
+++ b/roles/docker-graylog-pont/files/https_proxy.conf
@@ -0,0 +1,2 @@
+[Service]
+Environment="HTTPS_PROXY=http://10.121.38.1:8080/"
\ No newline at end of file
diff --git a/roles/docker-graylog-pont/handlers/main.yml b/roles/docker-graylog-pont/handlers/main.yml
new file mode 100644
index 0000000..0ccee7e
--- /dev/null
+++ b/roles/docker-graylog-pont/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart docker
+ service: name=docker state=restarted
\ No newline at end of file
diff --git a/roles/docker-graylog-pont/tasks/main.yml b/roles/docker-graylog-pont/tasks/main.yml
new file mode 100644
index 0000000..cc34ce4
--- /dev/null
+++ b/roles/docker-graylog-pont/tasks/main.yml
@@ -0,0 +1,62 @@
+---
+- name: Installation de apt-transport-https
+ apt: name=apt-transport-https state=present
+
+- name: Installation de ca-certificates
+ apt: name=ca-certificates state=present
+
+- name: Installation de gnupg2
+ apt: name=gnupg2 state=present
+
+- name: Installation de software-properties-common
+ apt: name=software-properties-common state=present
+
+- name: Installation de sudo
+ apt: name=sudo state=present
+
+- name: Installation de docker
+ shell: export https_proxy=http://10.121.38.1:8080 && curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
+
+- name: Récupération des paquets docker-ce et docker-compose
+ shell: sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
+
+- name: Création du répertoire docker.service.d
+ file:
+ path: /etc/systemd/system/docker.service.d
+ state: directory
+ owner: root
+ group: root
+ mode: 0775
+ recurse: yes
+
+- name: Copie https_proxy.conf
+ copy: src=https_proxy.conf dest=/etc/systemd/system/docker.service.d/
+ notify:
+ - restart docker
+
+- name: Vérification des nouveaux paquets
+ shell: sudo apt-get update
+
+- name: Installation de docker-ce
+ shell: sudo apt-get install -y docker-ce
+
+- name: Installation de docker-compose
+ shell: export https_proxy=http://10.121.38.1:8080 && curl -L "https://github.com/docker/compose/releases/download/1.23.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
+
+- name: Modification des droits de docker-compose
+ shell: chmod +x /usr/local/bin/docker-compose
+
+- name: Copie du fichier fstab
+ copy: src=fstab dest=/etc/
+
+- name: Création du répertoire graylog
+ shell: mkdir /root/graylog
+
+- name: Copie du docker-compose.yml graylog
+ copy: src=docker-compose.yml dest=/root/graylog
+
+- name: Changement du système de fichier de /dev/sdb1 en ext4
+ shell: mkfs.ext4 /dev/sdb1
+
+- name: Montage /dev/sdb1 sur /var/lib/docker
+ shell: mount /dev/sdb1 /var/lib/docker
diff --git a/roles/docker-graylog/files/docker-compose.yml b/roles/docker-graylog/files/docker-compose.yml
new file mode 100644
index 0000000..9eddacf
--- /dev/null
+++ b/roles/docker-graylog/files/docker-compose.yml
@@ -0,0 +1,44 @@
+version: '2'
+services:
+ # MongoDB: https://hub.docker.com/_/mongo/
+ mongodb:
+ image: mongo:3
+ # Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/6.x/docker.html
+ elasticsearch:
+ image: docker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
+ environment:
+ - http.host=172.16.0.20
+ - transport.host=localhost
+ - network.host=0.0.0.0
+ - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
+ ulimits:
+ memlock:
+ soft: -1
+ hard: -1
+ mem_limit: 1g
+ # Graylog: https://hub.docker.com/r/graylog/graylog/
+ graylog:
+ image: graylog/graylog:2.5.1
+ environment:
+ # CHANGE ME!
+ - GRAYLOG_PASSWORD_SECRET=somepasswordpepper
+ # Password: admin
+ - GRAYLOG_ROOT_PASSWORD_SHA2=8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
+ - GRAYLOG_WEB_ENDPOINT_URI=http://127.0.0.1:9000/api
+ links:
+ - mongodb:mongo
+ - elasticsearch
+ depends_on:
+ - mongodb
+ - elasticsearch
+ ports:
+ # Graylog web interface and REST API
+ - 9000:9000
+ # Syslog TCP
+ - 515:514
+ # Syslog UDP
+ - 515:514/udp
+ # GELF TCP
+ - 12201:12201
+ # GELF UDP
+ - 12201:12201/udp
\ No newline at end of file
diff --git a/roles/docker-graylog/files/fstab b/roles/docker-graylog/files/fstab
new file mode 100644
index 0000000..c86a33e
--- /dev/null
+++ b/roles/docker-graylog/files/fstab
@@ -0,0 +1,13 @@
+# /etc/fstab: static file system information.
+#
+# Use 'blkid' to print the universally unique identifier for a
+# device; this may be used with UUID= as a more robust way to name devices
+# that works even if disks are added and removed. See fstab(5).
+#
+# <file system> <mount point> <type> <options> <dump> <pass>
+/dev/mapper/stretch64--vg-root / ext4 errors=remount-ro 0 1
+# /boot was on /dev/sda1 during installation
+UUID=8f340ef0-94a1-4730-8da3-81ce5e38d666 /boot ext2 defaults 0 2
+/dev/mapper/stretch64--vg-swap_1 none swap sw 0 0
+/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
+/dev/sdb1 /var/lib/containers ext4 defaults 0 0
\ No newline at end of file
diff --git a/roles/docker-graylog/files/https_proxy.conf b/roles/docker-graylog/files/https_proxy.conf
new file mode 100644
index 0000000..ebff942
--- /dev/null
+++ b/roles/docker-graylog/files/https_proxy.conf
@@ -0,0 +1,2 @@
+[Service]
+Environment="HTTPS_PROXY=http://192.168.99.99:8080/"
\ No newline at end of file
diff --git a/roles/docker-graylog/handlers/main.yml b/roles/docker-graylog/handlers/main.yml
new file mode 100644
index 0000000..0ccee7e
--- /dev/null
+++ b/roles/docker-graylog/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart docker
+ service: name=docker state=restarted
\ No newline at end of file
diff --git a/roles/docker-graylog/tasks/main.yml b/roles/docker-graylog/tasks/main.yml
new file mode 100644
index 0000000..828462d
--- /dev/null
+++ b/roles/docker-graylog/tasks/main.yml
@@ -0,0 +1,62 @@
+---
+- name: Installation de apt-transport-https
+ apt: name=apt-transport-https state=present
+
+- name: Installation de ca-certificates
+ apt: name=ca-certificates state=present
+
+- name: Installation de gnupg2
+ apt: name=gnupg2 state=present
+
+- name: Installation de software-properties-common
+ apt: name=software-properties-common state=present
+
+- name: Installation de sudo
+ apt: name=sudo state=present
+
+- name: Installation de docker
+ shell: export https_proxy=http://192.168.99.99:8080 && curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
+
+- name: Récupération des paquets docker-ce et docker-compose
+ shell: sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
+
+- name: Création du répertoire docker.service.d
+ file:
+ path: /etc/systemd/system/docker.service.d
+ state: directory
+ owner: root
+ group: root
+ mode: 0775
+ recurse: yes
+
+- name: Copie https_proxy.conf
+ copy: src=https_proxy.conf dest=/etc/systemd/system/docker.service.d/
+ notify:
+ - restart docker
+
+- name: Vérification des nouveaux paquets
+ shell: sudo apt-get update
+
+- name: Installation de docker-ce
+ shell: sudo apt-get install -y docker-ce
+
+- name: Installation de docker-compose
+ shell: export https_proxy=http://192.168.99.99:8080 && curl -L "https://github.com/docker/compose/releases/download/1.23.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
+
+- name: Modification des droits de docker-compose
+ shell: chmod +x /usr/local/bin/docker-compose
+
+- name: Copie du fichier fstab
+ copy: src=fstab dest=/etc/
+
+- name: Création du répertoire graylog
+ shell: mkdir /root/graylog
+
+- name: Copie du docker-compose.yml graylog
+ copy: src=docker-compose.yml dest=/root/graylog
+
+- name: Changement du système de fichier de /dev/sdb1 en ext4
+ shell: mkfs.ext4 /dev/sdb1
+
+- name: Montage /dev/sdb1 sur /var/lib/docker
+ shell: mount /dev/sdb1 /var/lib/docker
diff --git a/roles/docker-iredmail-ab/files/fstab b/roles/docker-iredmail-ab/files/fstab
new file mode 100644
index 0000000..c86a33e
--- /dev/null
+++ b/roles/docker-iredmail-ab/files/fstab
@@ -0,0 +1,13 @@
+# /etc/fstab: static file system information.
+#
+# Use 'blkid' to print the universally unique identifier for a
+# device; this may be used with UUID= as a more robust way to name devices
+# that works even if disks are added and removed. See fstab(5).
+#
+# <file system> <mount point> <type> <options> <dump> <pass>
+/dev/mapper/stretch64--vg-root / ext4 errors=remount-ro 0 1
+# /boot was on /dev/sda1 during installation
+UUID=8f340ef0-94a1-4730-8da3-81ce5e38d666 /boot ext2 defaults 0 2
+/dev/mapper/stretch64--vg-swap_1 none swap sw 0 0
+/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
+/dev/sdb1 /var/lib/containers ext4 defaults 0 0
\ No newline at end of file
diff --git a/roles/docker-iredmail-ab/files/https_proxy.conf b/roles/docker-iredmail-ab/files/https_proxy.conf
new file mode 100644
index 0000000..ebff942
--- /dev/null
+++ b/roles/docker-iredmail-ab/files/https_proxy.conf
@@ -0,0 +1,2 @@
+[Service]
+Environment="HTTPS_PROXY=http://192.168.99.99:8080/"
\ No newline at end of file
diff --git a/roles/docker-iredmail-ab/files/iredmail.sh b/roles/docker-iredmail-ab/files/iredmail.sh
new file mode 100644
index 0000000..cba0bdf
--- /dev/null
+++ b/roles/docker-iredmail-ab/files/iredmail.sh
@@ -0,0 +1,14 @@
+#!/bin/bash
+
+docker run --privileged -p 80:80 -p 443:443 \
+ -h s-mess.sio.lan \
+ -e "DOMAIN=sio.lan" \
+ -e "MYSQL_ROOT_PASSWORD=iredmail" \
+ -e "SOGO_WORKERS=1" \
+ -e "TIMEZONE=Europe/Paris" \
+ -e "POSTMASTER_PASSWORD=Azertyuiop1+" \
+ -e "IREDAPD_PLUGINS=['reject_null_sender', 'reject_sender_login_mismatch', 'greylisting', 'throttle', 'amavisd_wblist', 'sql_alias_access_policy']" \
+ -v /root/mysql:/var/lib/mysql \
+ -v /root/vmail:/var/vmail \
+ -v /root/clamav:/var/lib/clamav \
+ --name=iredmail lejmr/iredmail:mysql-latest
diff --git a/roles/docker-iredmail-ab/handlers/main.yml b/roles/docker-iredmail-ab/handlers/main.yml
new file mode 100644
index 0000000..0ccee7e
--- /dev/null
+++ b/roles/docker-iredmail-ab/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart docker
+ service: name=docker state=restarted
\ No newline at end of file
diff --git a/roles/docker-iredmail-ab/tasks/main.yml b/roles/docker-iredmail-ab/tasks/main.yml
new file mode 100644
index 0000000..fd967fa
--- /dev/null
+++ b/roles/docker-iredmail-ab/tasks/main.yml
@@ -0,0 +1,83 @@
+---
+- name: Installation de apt-transport-https
+ apt: name=apt-transport-https state=present
+
+- name: Installation de ca-certificates
+ apt: name=ca-certificates state=present
+
+- name: Installation de gnupg2
+ apt: name=gnupg2 state=present
+
+- name: Installation de software-properties-common
+ apt: name=software-properties-common state=present
+
+- name: Installation de sudo
+ apt: name=sudo state=present
+
+- name: Installation de docker
+ shell: export https_proxy=http://192.168.99.99:8080 && curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
+
+- name: Récupération des paquets docker-ce et docker-compose
+ shell: sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
+
+- name: Création du répertoire docker.service.d
+ file:
+ path: /etc/systemd/system/docker.service.d
+ state: directory
+ owner: root
+ group: root
+ mode: 0775
+ recurse: yes
+
+- name: Copie https_proxy.conf
+ copy: src=https_proxy.conf dest=/etc/systemd/system/docker.service.d/
+ notify:
+ - restart docker
+
+- name: Vérification des nouveaux paquets
+ shell: sudo apt-get update
+
+- name: Installation de docker-ce
+ shell: sudo apt-get install -y docker-ce
+
+- name: Installation de docker-compose
+ shell: export https_proxy=http://192.168.99.99:8080 && curl -L "https://github.com/docker/compose/releases/download/1.23.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
+
+- name: Modification des droits de docker-compose
+ shell: chmod +x /usr/local/bin/docker-compose
+
+- name: Copie du fichier fstab
+ copy: src=fstab dest=/etc/
+
+- name: Copie du script bash Iredmail
+ copy: src=iredmail.sh dest=/root/tools/ansible
+
+- name: Changement du système de fichier de /dev/sdb1 en ext4
+ shell: mkfs.ext4 /dev/sdb1
+
+- name: Montage /dev/sdb1 sur /var/lib/docker
+ shell: mount /dev/sdb1 /var/lib/docker
+
+- name: Droit pour le script Iredmail
+ shell: chmod a+x /root/tools/ansible/iredmail.sh
+
+- name: Création du répertoire mysql
+ shell: mkdir /root//mysql
+
+- name: Création du répertoire vmail
+ shell: mkdir /root/vmail
+
+- name: Création du répertoire clamav
+ shell: mkdir /root/clamav
+
+- name: Exécution du script Iredmail
+ debug: msg="Exécuter le script iredmail.sh qui se trouve dans tools/ansible"
+
+- name: Montage /dev/sdb1
+ debug: msg="Pour vérifier que /dev/sdb1 est bien monté sur le répertoire /var/lib/docker, utiliser la commande df -h"
+
+- name: Test docker
+ debug: msg="Effectuer la commande docker run hello-world pour vérifier l'installation de docker-ce et effectuer la commande docker-compose --version pour vérifier que la version est bien la 1.23.1"
+
+- name: Démarrer le container
+ debug: msg="Pour démarrer le container openvas, utiliser la commande docker start nom_du_container_ (/var/lib/docker/containers), accéder à la page via l'adresse https://172.16.0.19:443"
diff --git a/roles/docker-openvas-ab/files/fstab b/roles/docker-openvas-ab/files/fstab
new file mode 100644
index 0000000..c86a33e
--- /dev/null
+++ b/roles/docker-openvas-ab/files/fstab
@@ -0,0 +1,13 @@
+# /etc/fstab: static file system information.
+#
+# Use 'blkid' to print the universally unique identifier for a
+# device; this may be used with UUID= as a more robust way to name devices
+# that works even if disks are added and removed. See fstab(5).
+#
+# <file system> <mount point> <type> <options> <dump> <pass>
+/dev/mapper/stretch64--vg-root / ext4 errors=remount-ro 0 1
+# /boot was on /dev/sda1 during installation
+UUID=8f340ef0-94a1-4730-8da3-81ce5e38d666 /boot ext2 defaults 0 2
+/dev/mapper/stretch64--vg-swap_1 none swap sw 0 0
+/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
+/dev/sdb1 /var/lib/containers ext4 defaults 0 0
\ No newline at end of file
diff --git a/roles/docker-openvas-ab/files/https_proxy.conf b/roles/docker-openvas-ab/files/https_proxy.conf
new file mode 100644
index 0000000..ebff942
--- /dev/null
+++ b/roles/docker-openvas-ab/files/https_proxy.conf
@@ -0,0 +1,2 @@
+[Service]
+Environment="HTTPS_PROXY=http://192.168.99.99:8080/"
\ No newline at end of file
diff --git a/roles/docker-openvas-ab/handlers/main.yml b/roles/docker-openvas-ab/handlers/main.yml
new file mode 100644
index 0000000..0ccee7e
--- /dev/null
+++ b/roles/docker-openvas-ab/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart docker
+ service: name=docker state=restarted
\ No newline at end of file
diff --git a/roles/docker-openvas-ab/tasks/main.yml b/roles/docker-openvas-ab/tasks/main.yml
new file mode 100644
index 0000000..2ffb798
--- /dev/null
+++ b/roles/docker-openvas-ab/tasks/main.yml
@@ -0,0 +1,77 @@
+---
+- name: Installation de apt-transport-https
+ apt: name=apt-transport-https state=present
+
+- name: Installation de ca-certificates
+ apt: name=ca-certificates state=present
+
+- name: Installation de gnupg2
+ apt: name=gnupg2 state=present
+
+- name: Installation de software-properties-common
+ apt: name=software-properties-common state=present
+
+- name: Installation de sudo
+ apt: name=sudo state=present
+
+- name: Installation de docker
+ shell: export https_proxy=http://192.168.99.99:8080 && curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
+
+- name: Récupération des paquets docker-ce et docker-compose
+ shell: sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
+
+- name: Création du répertoire docker.service.d
+ file:
+ path: /etc/systemd/system/docker.service.d
+ state: directory
+ owner: root
+ group: root
+ mode: 0775
+ recurse: yes
+
+- name: Copie https_proxy.conf
+ copy: src=https_proxy.conf dest=/etc/systemd/system/docker.service.d/
+ notify:
+ - restart docker
+
+- name: Vérification des nouveaux paquets
+ shell: sudo apt-get update
+
+- name: Installation de docker-ce
+ shell: sudo apt-get install -y docker-ce
+
+- name: Installation de docker-compose
+ shell: export https_proxy=http://192.168.99.99:8080 && curl -L "https://github.com/docker/compose/releases/download/1.23.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
+
+- name: Modification des droits de docker-compose
+ shell: chmod +x /usr/local/bin/docker-compose
+
+- name: Création du docker portainer_data
+ shell: docker volume create portainer_data
+
+- name: Initialisation de portainer
+ shell: docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
+
+- name: Copie du fichier fstab
+ copy: src=fstab dest=/etc/
+
+- name: Changement du système de fichier de /dev/sdb1 en ext4
+ shell: mkfs.ext4 /dev/sdb1
+
+- name: Montage /dev/sdb1 sur /var/lib/docker
+ shell: mount /dev/sdb1 /var/lib/docker
+
+- name: Installation d'OpenVAS
+ debug: msg="Exécuter la commande suivante pour mettre en place openvas > docker run -d -p 443:443 -e PUBLIC_HOSTNAME=172.16.0.19 --name openvas mikesplain/openvas puis redémarrer docker avec service docker restart"
+
+ #- name: Installation d'IredMail
+ #debug: msg="Exécuter la commande suivante pour mettre en place openvas > docker run -d -p 443:443 -e PUBLIC_HOSTNAME=172.16.0.19 --name iredmail lejmr/iredmail puis redémarrer docker avec service docker restart"
+
+- name: Montage /dev/sdb1
+ debug: msg="Pour vérifier que /dev/sdb1 est bien monté sur le répertoire /var/lib/docker, utiliser la commande df -h"
+
+- name: Test docker
+ debug: msg="Effectuer la commande docker run hello-world pour vérifier l'installation de docker-ce et effectuer la commande docker-compose --version pour vérifier que la version est bien la 1.23.1"
+
+- name: Démarrer le container
+ debug: msg="Pour démarrer le container openvas, utiliser la commande docker start nom_du_container_ (/var/lib/docker/containers), accéder à la page via l'adresse https://172.16.0.19:443"
diff --git a/roles/firewall-vpn-l-cs/files/iptables-vpn b/roles/firewall-vpn-l-cs/files/iptables-vpn
new file mode 100644
index 0000000..c363d43
--- /dev/null
+++ b/roles/firewall-vpn-l-cs/files/iptables-vpn
@@ -0,0 +1,58 @@
+#!/bin/bash
+
+#renommage des interfaces
+IFPUB=enp0s9
+IFINT=enp0s8
+
+iptables -F
+#iptables -F -t nat
+
+#bloquer tout
+iptables -P INPUT DROP
+iptables -P OUTPUT DROP
+iptables -P FORWARD ACCEPT
+
+iptables -A INPUT -i lo
+iptables -A OUTPUT -o lo
+
+#autorise l'acces SSH
+iptables -A INPUT -p tcp --dport 22 -j ACCEPT
+iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
+
+#Autorise les requete DNS en tant que client
+iptables -A OUTPUT -p udp --dport 53 -j ACCEPT
+iptables -A INPUT -p udp --sport 53 -j ACCEPT
+iptables -A INPUT -p udp --dport 53 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 53 -j ACCEPT
+
+#autorise isakmp
+iptables -A OUTPUT -p udp --dport 500 -j ACCEPT
+iptables -A INPUT -p udp --sport 500 -j ACCEPT
+iptables -A INPUT -p udp --dport 500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 500 -j ACCEPT
+
+#autorise nat-t-ike
+iptables -A OUTPUT -p udp --dport 4500 -j ACCEPT
+iptables -A INPUT -p udp --sport 4500 -j ACCEPT
+iptables -A INPUT -p udp --dport 5500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 4500 -j ACCEPT
+
+
+# allow IPsec IKE negotiations
+#iptables -I INPUT -p udp --sport 500 --dport 500 -j ACCEPT
+#iptables -I OUTPUT -p udp --sport 500 --dport 500 -j ACCEPT
+# ESP encryption and authentication
+iptables -I INPUT -p 50 -j ACCEPT
+iptables -I OUTPUT -p 50 -j ACCEPT
+
+#autorise la supervision ( SNMP )
+iptables -A OUTPUT -p udp --dport 161 -j ACCEPT
+iptables -A INPUT -p udp --sport 161 -j ACCEPT
+
+#autorise NTP
+iptables -A OUTPUT -p udp --dport 123 -j ACCEPT
+iptables -A INPUT -p udp --sport 123 -j ACCEPT
+
+#autoriser les ping sauf de l'exterieur
+iptables -A INPUT -p icmp -m limit --limit 30/minute -j ACCEPT
+iptables -A OUTPUT -p icmp -j ACCEPT
\ No newline at end of file
diff --git a/roles/firewall-vpn-l-cs/tasks/main.yml b/roles/firewall-vpn-l-cs/tasks/main.yml
new file mode 100644
index 0000000..c171284
--- /dev/null
+++ b/roles/firewall-vpn-l-cs/tasks/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: fichier parefeu pour VPN
+ copy: src=iptables-vpn dest=/root/
diff --git a/roles/firewall-vpn-l/files/ferm.conf b/roles/firewall-vpn-l/files/ferm.conf
new file mode 100644
index 0000000..60550bb
--- /dev/null
+++ b/roles/firewall-vpn-l/files/ferm.conf
@@ -0,0 +1,122 @@
+# -*- shell-script -*-
+#
+# Configuration file for ferm(1).
+#
+
+@def $DEV_ADM = enp0s3;
+@def $DEV_VPN = enp0s8;
+@def $DEV_EXT = enp0s9;
+
+@def $NET_ADM=192.168.99.0/24;
+@def $NET_VPN=192.168.0.0/24;
+@def $NET_EXT=192.168.1.0/30;
+
+table filter {
+ chain INPUT {
+ policy DROP;
+
+ # connection tracking
+ mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+
+ # allow local packet
+ interface lo ACCEPT;
+
+ # allow SSH connections
+ #interface ($DEV_ADM) {
+ proto tcp dport ssh ACCEPT;
+ #}
+
+ # allow DNS connections
+ #interface ($DEV_INT) {
+ proto udp sport domain ACCEPT;
+ proto udp dport domain ACCEPT;
+ #}
+
+ # DHCP
+ proto udp dport (67 68) ACCEPT;
+
+ # allow IPsec
+ interface ($DEV_VPN $DEV_EXT) {
+ proto udp sport 500 ACCEPT;
+ proto udp dport 500 ACCEPT;
+ proto esp ACCEPT;
+ }
+
+ # Autoriser nat-t-ike
+ # interface ($DEV_VPN) {
+ proto udp sport 4500 ACCEPT;
+ proto udp dport 5500 ACCEPT;
+# }
+
+ # allow DNS connections
+ #interface ($DEV_INT) {
+ proto (udp tcp) dport domain ACCEPT;
+ #}
+
+ # autoriser supervision
+ proto udp sport 161 ACCEPT;
+
+ # autoriser NTP
+ proto udp sport 123 ACCEPT;
+
+ # respond to ping
+ proto icmp mod limit limit 30/minut ACCEPT;
+
+ }
+ chain OUTPUT {
+ policy DROP;
+# interface ($DEV_PUB) {
+
+ # Autoriser SSH
+ proto tcp sport ssh ACCEPT;
+
+ # Autoriser DNS
+ proto udp dport domain ACCEPT;
+ proto udp sport domain ACCEPT;
+
+ # DHCP
+ proto udp sport (67 68) ACCEPT;
+
+ # Autoriser ipsec
+ proto udp dport 500 ACCEPT;
+ proto udp sport 500 ACCEPT;
+
+ # Autoriser nat-t-ike
+ proto udp dport 4500 ACCEPT;
+ proto udp sport 4500 ACCEPT;
+
+ # Autoriser supervision
+ proto udp dport 161 ACCEPT;
+
+ # Autoriser NTP
+ proto udp dport 123 ACCEPT;
+
+ # respond to ping
+ proto icmp ACCEPT;
+
+# }
+
+ # connection tracking
+ #mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+ }
+ chain FORWARD {
+ policy ACCEPT;
+
+ # connection tracking
+ mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+ }
+}
+
+# IPv6:
+#domain ip6 {
+# table filter {
+# chain INPUT {
+# policy ACCEPT;
+# # ...
+# }
+# # ...
+# }
+#}
diff --git a/roles/firewall-vpn-l/files/iptables-vpn b/roles/firewall-vpn-l/files/iptables-vpn
new file mode 100644
index 0000000..c363d43
--- /dev/null
+++ b/roles/firewall-vpn-l/files/iptables-vpn
@@ -0,0 +1,58 @@
+#!/bin/bash
+
+#renommage des interfaces
+IFPUB=enp0s9
+IFINT=enp0s8
+
+iptables -F
+#iptables -F -t nat
+
+#bloquer tout
+iptables -P INPUT DROP
+iptables -P OUTPUT DROP
+iptables -P FORWARD ACCEPT
+
+iptables -A INPUT -i lo
+iptables -A OUTPUT -o lo
+
+#autorise l'acces SSH
+iptables -A INPUT -p tcp --dport 22 -j ACCEPT
+iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
+
+#Autorise les requete DNS en tant que client
+iptables -A OUTPUT -p udp --dport 53 -j ACCEPT
+iptables -A INPUT -p udp --sport 53 -j ACCEPT
+iptables -A INPUT -p udp --dport 53 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 53 -j ACCEPT
+
+#autorise isakmp
+iptables -A OUTPUT -p udp --dport 500 -j ACCEPT
+iptables -A INPUT -p udp --sport 500 -j ACCEPT
+iptables -A INPUT -p udp --dport 500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 500 -j ACCEPT
+
+#autorise nat-t-ike
+iptables -A OUTPUT -p udp --dport 4500 -j ACCEPT
+iptables -A INPUT -p udp --sport 4500 -j ACCEPT
+iptables -A INPUT -p udp --dport 5500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 4500 -j ACCEPT
+
+
+# allow IPsec IKE negotiations
+#iptables -I INPUT -p udp --sport 500 --dport 500 -j ACCEPT
+#iptables -I OUTPUT -p udp --sport 500 --dport 500 -j ACCEPT
+# ESP encryption and authentication
+iptables -I INPUT -p 50 -j ACCEPT
+iptables -I OUTPUT -p 50 -j ACCEPT
+
+#autorise la supervision ( SNMP )
+iptables -A OUTPUT -p udp --dport 161 -j ACCEPT
+iptables -A INPUT -p udp --sport 161 -j ACCEPT
+
+#autorise NTP
+iptables -A OUTPUT -p udp --dport 123 -j ACCEPT
+iptables -A INPUT -p udp --sport 123 -j ACCEPT
+
+#autoriser les ping sauf de l'exterieur
+iptables -A INPUT -p icmp -m limit --limit 30/minute -j ACCEPT
+iptables -A OUTPUT -p icmp -j ACCEPT
\ No newline at end of file
diff --git a/roles/firewall-vpn-l/handlers/main.yml b/roles/firewall-vpn-l/handlers/main.yml
new file mode 100644
index 0000000..e427fa2
--- /dev/null
+++ b/roles/firewall-vpn-l/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: Restart ferm
+ service: name=ferm state=restarted
diff --git a/roles/firewall-vpn-l/tasks/main.yml b/roles/firewall-vpn-l/tasks/main.yml
new file mode 100644
index 0000000..034dd32
--- /dev/null
+++ b/roles/firewall-vpn-l/tasks/main.yml
@@ -0,0 +1,8 @@
+---
+ - name : installer ferm
+ apt: name=ferm state=present
+ - name: fichier parefeu pour VPN
+ copy: src=ferm.conf dest=/etc/ferm/ferm.conf
+ notify:
+ - Restart ferm
+
diff --git a/roles/firewall-vpn-r-cs/files/iptables-vpn b/roles/firewall-vpn-r-cs/files/iptables-vpn
new file mode 100644
index 0000000..5ed337d
--- /dev/null
+++ b/roles/firewall-vpn-r-cs/files/iptables-vpn
@@ -0,0 +1,58 @@
+#!/bin/bash
+
+#renommage des interfaces
+IFPUB=enp0s8
+IFINT=enp0s9
+
+iptables -F
+#iptables -F -t nat
+
+#bloquer tout
+iptables -P INPUT DROP
+iptables -P OUTPUT DROP
+iptables -P FORWARD ACCEPT
+
+iptables -A INPUT -i lo
+iptables -A OUTPUT -o lo
+
+#autorise l'acces SSH
+iptables -A INPUT -p tcp --dport 22 -j ACCEPT
+iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
+
+#Autorise les requete DNS en tant que client
+iptables -A OUTPUT -p udp --dport 53 -j ACCEPT
+iptables -A INPUT -p udp --sport 53 -j ACCEPT
+iptables -A INPUT -p udp --dport 53 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 53 -j ACCEPT
+
+#autorise isakmp
+iptables -A OUTPUT -p udp --dport 500 -j ACCEPT
+iptables -A INPUT -p udp --sport 500 -j ACCEPT
+iptables -A INPUT -p udp --dport 500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 500 -j ACCEPT
+
+#autorise nat-t-ike
+iptables -A OUTPUT -p udp --dport 4500 -j ACCEPT
+iptables -A INPUT -p udp --sport 4500 -j ACCEPT
+iptables -A INPUT -p udp --dport 5500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 4500 -j ACCEPT
+
+
+# allow IPsec IKE negotiations
+#iptables -I INPUT -p udp --sport 500 --dport 500 -j ACCEPT
+#iptables -I OUTPUT -p udp --sport 500 --dport 500 -j ACCEPT
+# ESP encryption and authentication
+iptables -I INPUT -p 50 -j ACCEPT
+iptables -I OUTPUT -p 50 -j ACCEPT
+
+#autorise la supervision ( SNMP )
+iptables -A OUTPUT -p udp --dport 161 -j ACCEPT
+iptables -A INPUT -p udp --sport 161 -j ACCEPT
+
+#autorise NTP
+iptables -A OUTPUT -p udp --dport 123 -j ACCEPT
+iptables -A INPUT -p udp --sport 123 -j ACCEPT
+
+#autoriser les ping sauf de l'exterieur
+iptables -A INPUT -p icmp -m limit --limit 30/minute -j ACCEPT
+iptables -A OUTPUT -p icmp -j ACCEPT
\ No newline at end of file
diff --git a/roles/firewall-vpn-r-cs/tasks/main.yml b/roles/firewall-vpn-r-cs/tasks/main.yml
new file mode 100644
index 0000000..c171284
--- /dev/null
+++ b/roles/firewall-vpn-r-cs/tasks/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: fichier parefeu pour VPN
+ copy: src=iptables-vpn dest=/root/
diff --git a/roles/firewall-vpn-r/files/ferm.conf b/roles/firewall-vpn-r/files/ferm.conf
new file mode 100644
index 0000000..45ed360
--- /dev/null
+++ b/roles/firewall-vpn-r/files/ferm.conf
@@ -0,0 +1,116 @@
+# -*- shell-script -*-
+#
+# Configuration file for ferm(1).
+#
+
+@def $DEV_ADM = enp0s3;
+@def $DEV_VPN = enp0s8;
+@def $DEV_EXT = enp0s9;
+
+@def $NET_ADM=192.168.99.0/24;
+@def $NET_VPN=192.168.0.0/24;
+@def $NET_EXT=192.168.1.0/30;
+
+table filter {
+ chain INPUT {
+ policy DROP;
+
+ # connection tracking
+ mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+
+ # allow local packet
+ interface lo ACCEPT;
+
+ # allow SSH connections
+ #interface ($DEV_ADM) {
+ proto tcp dport ssh ACCEPT;
+ #}
+
+ # allow DNS connections
+ #interface ($DEV_INT) {
+ proto udp sport domain ACCEPT;
+ proto udp dport domain ACCEPT;
+ #}
+
+ # allow IPsec
+ interface ($DEV_VPN) {
+ proto udp sport 500 ACCEPT;
+ proto udp dport 500 ACCEPT;
+ proto esp ACCEPT;
+ }
+
+ # Autoriser nat-t-ike
+ interface ($DEV_VPN) {
+ proto udp sport 4500 ACCEPT;
+ proto udp dport 5500 ACCEPT;
+ }
+
+ # allow DNS connections
+ #interface ($DEV_INT) {
+# proto (udp tcp) dport domain ACCEPT;
+ #}
+
+ # autoriser supervision
+ proto udp sport 161 ACCEPT;
+
+ # autoriser NTP
+ proto udp sport 123 ACCEPT;
+
+ # respond to ping
+ proto icmp mod limit limit 30/minut ACCEPT;
+
+ }
+ chain OUTPUT {
+ policy DROP;
+# interface ($DEV_PUB) {
+
+ # Autoriser SSH
+ proto tcp sport ssh ACCEPT;
+
+ # Autoriser DNS
+ proto udp dport domain ACCEPT;
+ proto udp sport domain ACCEPT;
+
+ # Autoriser ipsec
+ proto udp dport 500 ACCEPT;
+ proto udp sport 500 ACCEPT;
+
+ # Autoriser nat-t-ike
+ proto udp dport 4500 ACCEPT;
+ proto udp sport 4500 ACCEPT;
+
+ # Autoriser supervision
+ proto udp dport 161 ACCEPT;
+
+ # Autoriser NTP
+ proto udp dport 123 ACCEPT;
+
+ # respond to ping
+ proto icmp ACCEPT;
+
+# }
+
+ # connection tracking
+ #mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+ }
+ chain FORWARD {
+ policy ACCEPT;
+
+ # connection tracking
+ mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+ }
+}
+
+# IPv6:
+#domain ip6 {
+# table filter {
+# chain INPUT {
+# policy ACCEPT;
+# # ...
+# }
+# # ...
+# }
+#}
diff --git a/roles/firewall-vpn-r/files/iptables-vpn b/roles/firewall-vpn-r/files/iptables-vpn
new file mode 100644
index 0000000..5ed337d
--- /dev/null
+++ b/roles/firewall-vpn-r/files/iptables-vpn
@@ -0,0 +1,58 @@
+#!/bin/bash
+
+#renommage des interfaces
+IFPUB=enp0s8
+IFINT=enp0s9
+
+iptables -F
+#iptables -F -t nat
+
+#bloquer tout
+iptables -P INPUT DROP
+iptables -P OUTPUT DROP
+iptables -P FORWARD ACCEPT
+
+iptables -A INPUT -i lo
+iptables -A OUTPUT -o lo
+
+#autorise l'acces SSH
+iptables -A INPUT -p tcp --dport 22 -j ACCEPT
+iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
+
+#Autorise les requete DNS en tant que client
+iptables -A OUTPUT -p udp --dport 53 -j ACCEPT
+iptables -A INPUT -p udp --sport 53 -j ACCEPT
+iptables -A INPUT -p udp --dport 53 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 53 -j ACCEPT
+
+#autorise isakmp
+iptables -A OUTPUT -p udp --dport 500 -j ACCEPT
+iptables -A INPUT -p udp --sport 500 -j ACCEPT
+iptables -A INPUT -p udp --dport 500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 500 -j ACCEPT
+
+#autorise nat-t-ike
+iptables -A OUTPUT -p udp --dport 4500 -j ACCEPT
+iptables -A INPUT -p udp --sport 4500 -j ACCEPT
+iptables -A INPUT -p udp --dport 5500 -j ACCEPT
+iptables -A OUTPUT -p udp --sport 4500 -j ACCEPT
+
+
+# allow IPsec IKE negotiations
+#iptables -I INPUT -p udp --sport 500 --dport 500 -j ACCEPT
+#iptables -I OUTPUT -p udp --sport 500 --dport 500 -j ACCEPT
+# ESP encryption and authentication
+iptables -I INPUT -p 50 -j ACCEPT
+iptables -I OUTPUT -p 50 -j ACCEPT
+
+#autorise la supervision ( SNMP )
+iptables -A OUTPUT -p udp --dport 161 -j ACCEPT
+iptables -A INPUT -p udp --sport 161 -j ACCEPT
+
+#autorise NTP
+iptables -A OUTPUT -p udp --dport 123 -j ACCEPT
+iptables -A INPUT -p udp --sport 123 -j ACCEPT
+
+#autoriser les ping sauf de l'exterieur
+iptables -A INPUT -p icmp -m limit --limit 30/minute -j ACCEPT
+iptables -A OUTPUT -p icmp -j ACCEPT
\ No newline at end of file
diff --git a/roles/firewall-vpn-r/handlers/main.yml b/roles/firewall-vpn-r/handlers/main.yml
new file mode 100644
index 0000000..e427fa2
--- /dev/null
+++ b/roles/firewall-vpn-r/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: Restart ferm
+ service: name=ferm state=restarted
diff --git a/roles/firewall-vpn-r/tasks/main.yml b/roles/firewall-vpn-r/tasks/main.yml
new file mode 100644
index 0000000..7d85a62
--- /dev/null
+++ b/roles/firewall-vpn-r/tasks/main.yml
@@ -0,0 +1,15 @@
+---
+ - name: redemarrer interfaces
+ command: ifdown enp0s8
+ - name: redemarrer interfaces
+ command: ifup enp0s8
+ - name: redemarrer interfaces
+ command: ifdown enp0s9
+ - name: redemarrer interfaces
+ command: ifup enp0s9
+ - name: redemarrer interfaces
+ apt: name=ferm state=present
+ - name: fichier parefeu pour VPN
+ copy: src=ferm.conf dest=/etc/ferm/ferm.conf
+ notify:
+ - Restart ferm
diff --git a/roles/fog/tasks/main.yml b/roles/fog/tasks/main.yml
new file mode 100644
index 0000000..9f826ea
--- /dev/null
+++ b/roles/fog/tasks/main.yml
@@ -0,0 +1,15 @@
+---
+ - name: creation d'un repertoire fog
+ file:
+ path: /root/fog
+ state: directory
+
+ - name: recuperation du fichier d'installation de fog
+ get_url:
+ url: http://depl/gsbstore/fogproject-1.5.7.tar.gz
+ dest: /root/fog
+
+ - name: decompression du fichier d'installation de fog
+ unarchive:
+ src: /root/fog/fogproject-1.5.7.tar.gz
+ dest: /root/fog
diff --git a/roles/goss/tasks/main.yml b/roles/goss/tasks/main.yml
new file mode 100644
index 0000000..4af44da
--- /dev/null
+++ b/roles/goss/tasks/main.yml
@@ -0,0 +1,10 @@
+---
+
+- name: goss binary exists
+ stat: path=/usr/local/bin/goss
+ register: gossbin
+
+- name: install goss
+ shell: export https_proxy=http://10.121.38.1:8080 && curl -fsSL https://goss.rocks/install | sh
+ when: gossbin.stat.exists == False
+
diff --git a/roles/icinga-ab/files/cfg/contacts_icinga.cfg b/roles/icinga-ab/files/cfg/contacts_icinga.cfg
new file mode 100644
index 0000000..8a66285
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email icinga.ppe31@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-ab/files/cfg/extinfo_icinga.cfg b/roles/icinga-ab/files/cfg/extinfo_icinga.cfg
new file mode 100644
index 0000000..07bd594
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/extinfo_icinga.cfg
@@ -0,0 +1,13 @@
+##
+## Extended Host and Service Information
+##
+
+define hostextinfo{
+ hostgroup_name debian-servers
+ notes Debian GNU/Linux servers
+# notes_url http://webserver.localhost.localdomain/hostinfo.pl?host=netware1
+ icon_image base/debian.png
+ icon_image_alt Debian GNU/Linux
+ vrml_image debian.png
+ statusmap_image base/debian.gd2
+ }
diff --git a/roles/icinga-ab/files/cfg/generic-host_icinga.cfg b/roles/icinga-ab/files/cfg/generic-host_icinga.cfg
new file mode 100644
index 0000000..ed48590
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/generic-host_icinga.cfg
@@ -0,0 +1,19 @@
+ Generic host definition template - This is NOT a real host, just a template!
+
+define host{
+ name generic-host ; The name of this host template
+ notifications_enabled 1 ; Host notifications are enabled
+ event_handler_enabled 1 ; Host event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ check_command check-host-alive
+ max_check_attempts 10
+ notification_interval 0
+ notification_period 24x7
+ notification_options d,u,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-ab/files/cfg/generic-service_icinga.cfg b/roles/icinga-ab/files/cfg/generic-service_icinga.cfg
new file mode 100644
index 0000000..4d60c79
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/generic-service_icinga.cfg
@@ -0,0 +1,26 @@
+# generic service template definition
+define service{
+ name generic-service ; The 'name' of this service template
+ active_checks_enabled 1 ; Active service checks are enabled
+ passive_checks_enabled 1 ; Passive service checks are enabled/accepted
+ parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems)
+ obsess_over_service 1 ; We should obsess over this service (if necessary)
+ check_freshness 0 ; Default is to NOT check service 'freshness'
+ notifications_enabled 1 ; Service notifications are enabled
+ event_handler_enabled 1 ; Service event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ notification_interval 0 ; Only send notifications on status change by default.
+ is_volatile 0
+ check_period 24x7
+ normal_check_interval 5
+ retry_check_interval 1
+ max_check_attempts 4
+ notification_period 24x7
+ notification_options w,u,c,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-ab/files/cfg/gwsio2.cfg b/roles/icinga-ab/files/cfg/gwsio2.cfg
new file mode 100644
index 0000000..c09b7d2
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/gwsio2.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name gwsio2
+ alias Passerelle
+ address 192.168.0.1
+ icon_image cook/linux_server.gif
+ statusmap_image cook/linux_server.gd2
+ }
diff --git a/roles/icinga-ab/files/cfg/localhost.cfg b/roles/icinga-ab/files/cfg/localhost.cfg
new file mode 100644
index 0000000..4e4e190
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/localhost.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host
+ host_name localhost
+ alias Serveur monitoring
+ address localhost
+ }
+
diff --git a/roles/icinga-ab/files/cfg/localhost_icinga.cfg b/roles/icinga-ab/files/cfg/localhost_icinga.cfg
new file mode 100644
index 0000000..c15cda4
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/localhost_icinga.cfg
@@ -0,0 +1,60 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in icinga-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name localhost
+ alias localhost
+ address 127.0.0.1
+ parents gwsio2
+ }
+
+# Define a service to check the disk space of the root partition
+# on the local machine. Warning if < 20% free, critical if
+# < 10% free space on partition.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Disk Space
+ check_command check_all_disks!20%!10%
+ }
+
+
+
+# Define a service to check the number of currently logged in
+# users on the local machine. Warning if > 20 users, critical
+# if > 50 users.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Users
+ check_command check_users!20!50
+ }
+
+
+# Define a service to check the number of currently running procs
+# on the local machine. Warning if > 250 processes, critical if
+# > 400 processes.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Total Processes
+ check_command check_procs!250!400
+ }
+
+
+
+# Define a service to check the load on the local machine.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Load
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
diff --git a/roles/icinga-ab/files/cfg/netgear.cfg b/roles/icinga-ab/files/cfg/netgear.cfg
new file mode 100644
index 0000000..c35984a
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/netgear.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name netgear
+ alias switch
+ address 192.168.0.2
+ parents gwsio4
+ icon_image cook/switch.gif
+ statusmap_image cook/switch.gd2
+}
+
diff --git a/roles/icinga-ab/files/cfg/r-ext.cfg b/roles/icinga-ab/files/cfg/r-ext.cfg
new file mode 100644
index 0000000..4c14bef
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/r-ext.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-ext
+ alias Routeur externe
+ address 192.168.200.253
+ parents localhost
+ }
diff --git a/roles/icinga-ab/files/cfg/r-int.cfg b/roles/icinga-ab/files/cfg/r-int.cfg
new file mode 100644
index 0000000..77ebe3d
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/r-int.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-int
+ alias Routeur interne
+ address 172.16.0.254
+ parents r-ext
+ }
diff --git a/roles/icinga-ab/files/cfg/s-adm.cfg b/roles/icinga-ab/files/cfg/s-adm.cfg
new file mode 100644
index 0000000..aeadbee
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/s-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-adm
+ alias debian-servers
+ address 192.168.99.99
+ parents r-int
+ }
+
diff --git a/roles/icinga-ab/files/cfg/s-infra.cfg b/roles/icinga-ab/files/cfg/s-infra.cfg
new file mode 100644
index 0000000..c369ff6
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/s-infra.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra
+ alias debian-servers
+ address 172.16.0.1
+ parents r-int
+ }
+
diff --git a/roles/icinga-ab/files/cfg/s-proxy.cfg b/roles/icinga-ab/files/cfg/s-proxy.cfg
new file mode 100644
index 0000000..de4f3c9
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/s-proxy.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-proxy
+ alias serveur proxy
+ address 172.16.0.2
+ parents r-int
+ }
diff --git a/roles/icinga-ab/files/cfg/s-test.cfg b/roles/icinga-ab/files/cfg/s-test.cfg
new file mode 100644
index 0000000..204262d
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/s-test.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-test
+ alias machine test
+ address 172.16.0.18
+ parents r-int
+ }
diff --git a/roles/icinga-ab/files/cfg/services_icinga.cfg b/roles/icinga-ab/files/cfg/services_icinga.cfg
new file mode 100644
index 0000000..4ea25d8
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-ab/files/cfg/srv-2012.cfg b/roles/icinga-ab/files/cfg/srv-2012.cfg
new file mode 100644
index 0000000..8ff28a9
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/srv-2012.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name srv-2012
+ alias windows-servers
+ address 172.16.0.6
+ parents r-int
+ icon_image base/win40.gif
+ statusmap_image base/win40.gd2
+ }
+
diff --git a/roles/icinga-ab/files/cfg/timeperiods_icinga.cfg b/roles/icinga-ab/files/cfg/timeperiods_icinga.cfg
new file mode 100644
index 0000000..55ecf9d
--- /dev/null
+++ b/roles/icinga-ab/files/cfg/timeperiods_icinga.cfg
@@ -0,0 +1,50 @@
+###############################################################################
+# timeperiods.cfg
+###############################################################################
+
+# This defines a timeperiod where all times are valid for checks,
+# notifications, etc. The classic "24x7" support nightmare. :-)
+
+define timeperiod{
+ timeperiod_name 24x7
+ alias 24 Hours A Day, 7 Days A Week
+ sunday 00:00-24:00
+ monday 00:00-24:00
+ tuesday 00:00-24:00
+ wednesday 00:00-24:00
+ thursday 00:00-24:00
+ friday 00:00-24:00
+ saturday 00:00-24:00
+ }
+
+# Here is a slightly friendlier period during work hours
+define timeperiod{
+ timeperiod_name workhours
+ alias Standard Work Hours
+ monday 09:00-17:00
+ tuesday 09:00-17:00
+ wednesday 09:00-17:00
+ thursday 09:00-17:00
+ friday 09:00-17:00
+ }
+
+# The complement of workhours
+define timeperiod{
+ timeperiod_name nonworkhours
+ alias Non-Work Hours
+ sunday 00:00-24:00
+ monday 00:00-09:00,17:00-24:00
+ tuesday 00:00-09:00,17:00-24:00
+ wednesday 00:00-09:00,17:00-24:00
+ thursday 00:00-09:00,17:00-24:00
+ friday 00:00-09:00,17:00-24:00
+ saturday 00:00-24:00
+ }
+
+# This one is a favorite: never :)
+define timeperiod{
+ timeperiod_name never
+ alias Never
+ }
+
+# end of file
diff --git a/roles/icinga-ab/files/check_iftraffic3.pl b/roles/icinga-ab/files/check_iftraffic3.pl
new file mode 100755
index 0000000..62ddbd1
--- /dev/null
+++ b/roles/icinga-ab/files/check_iftraffic3.pl
@@ -0,0 +1,643 @@
+#!/usr/bin/perl -w
+#
+# check_iftraffic.pl - Nagios(r) network traffic monitor plugin
+# Copyright (C) 2004 Gerd Mueller / Netways GmbH
+# $Id: check_iftraffic.pl 1119 2006-02-09 10:30:09Z gmueller $
+#
+# mw = Markus Werner mw+nagios@wobcom.de
+# Remarks (mw):
+#
+# I adopted as much as possible the programming style of the origin code.
+#
+# There should be a function to exit this programm,
+# instead of calling print and exit statements all over the place.
+#
+#
+# minor changes by mw
+# The snmp if_counters on net devices can have overflows.
+# I wrote this code to address this situation.
+# It has no automatic detection and which point the overflow
+# occurs but it will generate a warning state and you
+# can set the max value by calling this script with an additional
+# arg.
+#
+# minor cosmetic changes by mw
+# Sorry but I couldn't sustain to clean up some things.
+#
+# gj = Greg Frater gregATfraterfactory.com
+# Remarks (gj):
+# minor (gj):
+#
+# * fixed the performance data, formating was not to spec
+# * Added a check of the interfaces status (up/down).
+# If down the check returns a critical status.
+# * Allow either textual or the numeric index value.
+# * If the interface speed is not specified on the command line
+# it gets it automatically from IfSpeed
+# * Added option for second ifSpeed to allow for asymetrcal links
+# such as a DSL line or cable modem where the download and upload
+# speeds are different
+# * Added -B option to display results in bits/sec instead of Bytes/sec
+# * Added the current usage in Bytes/s (or bit/s) to the perfdata output
+# * Added ability for plugin to determine interface to query by matching IP
+# address of host with entry in ipAdEntIfIndex (.1.3.6.1.2.1.4.20.1.2)
+# * Added -L flag to list entries found in the ipAdEntIfIndex table
+# Otherwise, it works as before.
+#
+#
+#
+#
+# based on check_traffic from Adrian Wieczorek, <ads (at) irc.pila.pl>
+#
+# Send us bug reports, questions and comments about this plugin.
+# Latest version of this software: http://www.nagiosexchange.org
+#
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307
+
+use strict;
+
+use Net::SNMP;
+use Getopt::Long;
+&Getopt::Long::config('bundling');
+
+use Data::Dumper;
+
+my $host_ip;
+my $host_address;
+my $iface_number;
+my $iface_descr;
+my $iface_speed;
+my $iface_speedOut;
+my $index_list;
+my $opt_h;
+my $units;
+
+my $session;
+my $error;
+my $port = 161;
+my $snmp_version = 1;
+
+my @snmpoids;
+
+# SNMP OIDs for Traffic
+my $snmpIfOperStatus = '1.3.6.1.2.1.2.2.1.8';
+my $snmpIfInOctets = '1.3.6.1.2.1.2.2.1.10';
+my $snmpIfOutOctets = '1.3.6.1.2.1.2.2.1.16';
+my $snmpIfDescr = '1.3.6.1.2.1.2.2.1.2';
+my $snmpIfSpeed = '1.3.6.1.2.1.2.2.1.5';
+my $snmpIPAdEntIfIndex = '1.3.6.1.2.1.4.20.1.2';
+
+my $response;
+
+# Path to tmp files
+my $TRAFFIC_FILE = "/tmp/traffic";
+
+# changes sos 20090717 UNKNOWN must bes 3
+my %STATUS_CODE =
+ ( 'UNKNOWN' => '3', 'OK' => '0', 'WARNING' => '1', 'CRITICAL' => '2' );
+
+#default values;
+my $state = "UNKNOWN";
+my $if_status = '4';
+my ( $in_bytes, $out_bytes ) = 0;
+my $warn_usage = 85;
+my $crit_usage = 98;
+my $COMMUNITY = "public";
+my $use_reg = undef; # Use Regexp for name
+my $output = "";
+my $bits = undef;
+my $suffix = "Bs";
+my $label = "MBytes";
+
+#added 20050614 by mw
+my $max_value;
+my $max_bytes;
+
+#cosmetic changes 20050614 by mw, see old versions for detail
+# Added options for bits and second max ifspeed 20100202 by gj
+# Added options for specificy IP addr to match 20100405 by gj
+my $status = GetOptions(
+ "h|help" => \$opt_h,
+ 'B' => \$bits,
+ 'bits' => \$bits,
+ "C|community=s" => \$COMMUNITY,
+ "w|warning=s" => \$warn_usage,
+ "c|critical=s" => \$crit_usage,
+ "b|bandwidth|I|inBandwidth=i" => \$iface_speed,
+ "O|outBandwidth=i" => \$iface_speedOut,
+ 'r' => \$use_reg,
+ 'noregexp' => \$use_reg,
+ "p|port=i" => \$port,
+ "u|units=s" => \$units,
+ "i|interface=s" => \$iface_number,
+ "A|address=s" => \$host_ip,
+ "H|hostname=s" => \$host_address,
+ 'L' => \$index_list,
+ 'list' => \$index_list,
+
+ #added 20050614 by mw
+ "M|max=i" => \$max_value
+);
+
+if ( $status == 0 ) {
+ print_help();
+ exit $STATUS_CODE{'OK'};
+}
+
+# Changed 20091214 gj
+# Check for missing options
+#if ( ( !$host_address ) or ( !$iface_descr ) ) {
+if ( !$host_address ) {
+ print "\nMissing host address!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speed ) and ( !$units ) ){
+ print "\nMissing units!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $units ) and ( ( !$iface_speed ) and ( !$iface_speedOut ) ) ) {
+ print "\nMissing interface maximum speed!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speedOut ) and ( !$units ) ) {
+ print "\nMissing units for Out maximum speed!\n\n";
+ stop(print_usage(),"OK");
+}
+
+
+if ($bits) {
+ $suffix = "bs"
+}
+
+if ( !$iface_speed ) {
+ # Do nothing
+}else{
+
+ #change 20050414 by mw
+ # Added iface_speedOut 20100202 by gj
+ # Convert interface speed to kiloBytes
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+ if ( $iface_speedOut ) {
+ $iface_speedOut = bits2bytes( $iface_speedOut, $units ) / 1024;
+ }
+ if ( !$max_value ) {
+
+ # If no -M Parameter was set, set it to 32Bit Overflow
+ $max_bytes = 4194304 ; # the value is (2^32/1024)
+ }
+ else {
+ $max_bytes = unit2bytes( $max_value, $units );
+ }
+}
+
+if ( $snmp_version =~ /[12]/ ) {
+ ( $session, $error ) = Net::SNMP->session(
+ -hostname => $host_address,
+ -community => $COMMUNITY,
+ -port => $port,
+ -version => $snmp_version
+ );
+
+ if ( !defined($session) ) {
+ stop("UNKNOWN: $error","UNKNOWN");
+ }
+}
+elsif ( $snmp_version =~ /3/ ) {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v3 yet\n",$state);
+}
+else {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v$snmp_version yet\n",$state);
+}
+
+# Neither Interface Index nor Host IP address were specified
+if ( !$iface_descr ) {
+ if ( !$host_ip ){
+ # try to resolve host name and find index from ip addr
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_address );
+ } else {
+ # Use ip addr to find index
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_ip );
+ }
+}
+
+#push( @snmpoids, $snmpIPAdEntIfIndex . "." . $host_address );
+
+# Added 20091209 gj
+# Detect if a string description was given or a numberic interface index number
+if ( $iface_descr =~ /[^0123456789]+/ ) {
+ $iface_number = fetch_ifdescr( $session, $iface_descr );
+}else{
+ $iface_number = $iface_descr;
+}
+
+push( @snmpoids, $snmpIfSpeed . "." . $iface_number );
+push( @snmpoids, $snmpIfOperStatus . "." . $iface_number );
+push( @snmpoids, $snmpIfInOctets . "." . $iface_number );
+push( @snmpoids, $snmpIfOutOctets . "." . $iface_number );
+
+if ( !defined( $response = $session->get_request(@snmpoids) ) ) {
+ my $answer = $session->error;
+ $session->close;
+
+ stop("WARNING: SNMP error: $answer\n", "WARNING");
+}
+
+# Added 20091209 gj
+# Get interface speed from device if not provided on command line
+# Convert to kiloBytes
+if ( !$iface_speed ) {
+ $iface_speed = $response->{ $snmpIfSpeed . "." . $iface_number };
+ $units = "b";
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+}
+
+# Added 20100201 gj
+# Check if Out max speed was provided, use same if speed for both if not
+if (!$iface_speedOut) {
+ $iface_speedOut = $iface_speed;
+}
+
+$if_status = $response->{ $snmpIfOperStatus . "." . $iface_number };
+$in_bytes = $response->{ $snmpIfInOctets . "." . $iface_number } / 1024; # in kiloBytes
+$out_bytes = $response->{ $snmpIfOutOctets . "." . $iface_number } / 1024; # in kiloBytes
+
+$session->close;
+
+my $row;
+my $last_check_time = time - 1;
+my $last_in_bytes = $in_bytes;
+my $last_out_bytes = $out_bytes;
+
+if (
+ open( FILE,
+ "<" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address
+ )
+ )
+{
+ while ( $row = <FILE> ) {
+
+ #cosmetic change 20050416 by mw
+ #Couldn't sustain;-)
+## chomp();
+ ( $last_check_time, $last_in_bytes, $last_out_bytes ) =
+ split( ":", $row );
+
+ ### by sos 17.07.2009 check for last_bytes
+ if ( ! $last_in_bytes ) { $last_in_bytes=$in_bytes; }
+ if ( ! $last_out_bytes ) { $last_out_bytes=$out_bytes; }
+
+ if ($last_in_bytes !~ m/\d/) { $last_in_bytes=$in_bytes; }
+ if ($last_out_bytes !~ m/\d/) { $last_out_bytes=$out_bytes; }
+ }
+ close(FILE);
+}
+
+my $update_time = time;
+
+open( FILE, ">" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address )
+ or die "Can't open $TRAFFIC_FILE for writing: $!";
+
+printf FILE ( "%s:%.0ld:%.0ld\n", $update_time, $in_bytes, $out_bytes );
+close(FILE);
+
+my $db_file;
+
+#added 20050614 by mw
+#Check for and correct counter overflow (if possible).
+#See function counter_overflow.
+$in_bytes = counter_overflow( $in_bytes, $last_in_bytes, $max_bytes );
+$out_bytes = counter_overflow( $out_bytes, $last_out_bytes, $max_bytes );
+
+# Calculate traffic since last check (RX\TX) in kiloBytes
+my $in_traffic = sprintf( "%.2lf",
+ ( $in_bytes - $last_in_bytes ) / ( time - $last_check_time ) );
+my $out_traffic = sprintf( "%.2lf",
+ ( $out_bytes - $last_out_bytes ) / ( time - $last_check_time ) );
+
+# sos 20090717 changed due to rrdtool needs bytes
+my $in_traffic_absolut = $in_bytes * 1024 ;
+my $out_traffic_absolut = $out_bytes * 1024;
+
+# Calculate usage percentages
+my $in_usage = sprintf( "%.2f", ( 1.0 * $in_traffic * 100 ) / $iface_speed );
+my $out_usage = sprintf( "%.2f", ( 1.0 * $out_traffic * 100 ) / $iface_speedOut );
+
+
+if ($bits) {
+ # Convert output from Bytes to bits
+ $in_bytes = $in_bytes * 8;
+ $out_bytes = $out_bytes * 8;
+ $in_traffic = $in_traffic * 8;
+ $out_traffic = $out_traffic * 8;
+ $label = "Mbits";
+}
+
+my $in_prefix = "K";
+my $out_prefix = "K";
+
+if ( $in_traffic > 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 );
+ $in_prefix = "M";
+}
+if ( $out_traffic > 1024 ) {
+ $out_traffic = sprintf( "%.2f", $out_traffic / 1024 );
+ $out_prefix = "M";
+}
+if ( $in_traffic > 1024 * 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 * 1024 );
+ $in_prefix = "G";
+}
+if ( $out_traffic > 1024 * 1024 ) {
+ $out_traffic = sprintf( "%.2f",$out_traffic / 1024 * 1024 );
+ $out_prefix = "G";
+}
+
+# Convert from kiloBytes to megaBytes
+$in_bytes = sprintf( "%.2f", $in_bytes / 1024 );
+$out_bytes = sprintf( "%.2f", $out_bytes / 1024 );
+
+$state = "OK";
+
+# Added 20091209 by gj
+if ( $if_status != 1 ) {
+ $output = "Interface $iface_descr is down!";
+
+}else{
+ $output =
+ "Average IN: "
+ . $in_traffic . $in_prefix . $suffix . " (" . $in_usage . "%), "
+ . "Average OUT: " . $out_traffic . $out_prefix . $suffix . " (" . $out_usage . "%)<br>";
+ $output .= "Total RX: $in_bytes $label, Total TX: $out_bytes $label";
+}
+
+# Changed 20091209 gj
+if ( ( $in_usage > $crit_usage ) or ( $out_usage > $crit_usage ) or ( $if_status != 1 ) ) {
+ $state = "CRITICAL";
+}
+
+if ( ( $in_usage > $warn_usage )
+ or ( $out_usage > $warn_usage ) && $state eq "OK" )
+{
+ $state = "WARNING";
+}
+
+# Changed 20091209 gj
+$output = "$state - $output"
+ if ( $state ne "OK" );
+
+# Changed 20091214 gj - commas should have been semi colons
+$output .=
+"|inUsage=$in_usage%;$warn_usage;$crit_usage outUsage=$out_usage%;$warn_usage;$crit_usage"
+ . " inBandwidth=" . $in_traffic . $in_prefix . $suffix . " outBandwidth=" . $out_traffic . $out_prefix . $suffix
+ . " inAbsolut=$in_traffic_absolut outAbsolut=$out_traffic_absolut";
+
+stop($output, $state);
+
+
+sub fetch_Ip2IfIndex {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $host ) = @_;
+
+
+ # Determine if we have a host name or IP addr
+ if ( $host =~ /\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/ ){
+ #print "\nI found an IP address\n\n";
+ } else {
+ $host = get_ip ( $host );
+ #print "\nWe have a host name $host\n\n";
+ }
+
+ # Quit if results not found
+ if ( !defined( $response = $session->get_table($snmpIPAdEntIfIndex) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+
+ my %resp = %{$response};
+# foreach $key ( keys %{$response} ) {
+
+ if ( $index_list ){
+ print ("\nInterfaces found:\n");
+ print (" IP Addr\tIndex\n");
+ print ("------------------------\n");
+ }
+ # Check each returned value
+ foreach $key ( keys %resp ) {
+
+ if ( $index_list ){
+ my $index_addr = substr $key, 21;
+ print ($index_addr,"\t ",$resp{$key},"\n");
+ }
+
+ # Check for ip address mathcin in returned index results
+ if ( $key =~ /$host$/ ) {
+ $snmpkey = $resp{$key};
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $host \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+sub fetch_ifdescr {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $ifdescr ) = @_;
+
+ if ( !defined( $response = $session->get_table($snmpIfDescr) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+ foreach $key ( keys %{$response} ) {
+
+ # added 20070816 by oer: remove trailing 0 Byte for Windows :-(
+ my $resp=$response->{$key};
+ $resp =~ s/\x00//;
+
+
+ my $test = defined($use_reg)
+ ? $resp =~ /$ifdescr/
+ : $resp eq $ifdescr;
+
+ if ($test) {
+
+ ###if ( $resp =~ /^$ifdescr$/ ) {
+ ###if ( $resp =~ /$ifdescr/ ) {
+ ### print "$resp \n";
+ ###if ( $response->{$key} =~ /^$ifdescr$/ ) {
+
+ $key =~ /.*\.(\d+)$/;
+ $snmpkey = $1;
+
+ # print "$ifdescr = $key / $snmpkey \n"; #debug
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $ifdescr \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bits
+sub bits2bytes {
+ return unit2bytes(@_) / 8;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bytes
+sub unit2bytes {
+ my ( $value, $unit ) = @_;
+
+ if ( $unit eq "g" ) {
+ return $value * 1024 * 1024 * 1024;
+ }
+ elsif ( $unit eq "m" ) {
+ return $value * 1024 * 1024;
+ }
+ elsif ( $unit eq "k" ) {
+ return $value * 1024;
+ }
+ elsif ( $unit eq "b" ) {
+ return $value * 1;
+ }
+ else {
+ print "You have to supply a supported unit\n";
+ exit $STATUS_CODE{'UNKNOWN'};
+ }
+}
+
+#added 20050414 by mw
+#This function detects if an overflow occurs. If so, it returns
+#a computed value for $bytes.
+#If there is no counter overflow it simply returns the origin value of $bytes.
+#IF there is a Counter reboot wrap, just use previous output.
+sub counter_overflow {
+ my ( $bytes, $last_bytes, $max_bytes ) = @_;
+
+ $bytes += $max_bytes if ( $bytes < $last_bytes );
+ $bytes = $last_bytes if ( $bytes < $last_bytes );
+ return $bytes;
+}
+
+# Added 20100202 by gj
+# Print results and exit script
+sub stop {
+ my $result = shift;
+ my $exit_code = shift;
+ print $result . "\n";
+ exit ( $STATUS_CODE{$exit_code} );
+}
+
+# Added 20100405 by gj
+# Lookup hosts ip address
+sub get_ip {
+ use Net::DNS;
+
+ my ( $host_name ) = @_;
+
+ my $res = Net::DNS::Resolver->new;
+ my $query = $res->search($host_name);
+
+ if ($query) {
+ foreach my $rr ($query->answer) {
+ next unless $rr->type eq "A";
+ #print $rr->address, "\n";
+ return $rr->address;
+ }
+ } else {
+
+ stop("Error: IP address not resolved\n","UNKNOWN");
+ }
+}
+
+#cosmetic changes 20050614 by mw
+#Couldn't sustain "HERE";-), either.
+sub print_usage {
+ print <<EOU;
+ Usage: check_iftraffic3.pl -H host [ -C community_string ] [ -i if_index|if_descr ] [ -r ] [ -b if_max_speed_in | -I if_max_speed_in ] [ -O if_max_speed_out ] [ -u ] [ -B ] [ -A IP Address ] [ -L ] [ -M ] [ -w warn ] [ -c crit ]
+
+ Example 1: check_iftraffic3.pl -H host1 -C sneaky
+ Example 2: check_iftraffic3.pl -H host1 -C sneaky -i "Intel Pro" -r -B
+ Example 3: check_iftraffic3.pl -H host1 -C sneaky -i 5
+ Example 4: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 100 -u m
+ Example 5: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 20 -O 5 -u m
+ Example 6: check_iftraffic3.pl -H host1 -C sneaky -A 192.168.1.1 -B -b 100 -u m
+
+ Options:
+
+ -H, --host STRING or IPADDRESS
+ Check interface on the indicated host.
+ -B, --bits
+ Display results in bits per second b/s (default: Bytes/s)
+ -C, --community STRING
+ SNMP Community.
+ -r, --regexp
+ Use regexp to match NAME in description OID
+ -i, --interface STRING
+ Interface Name
+ -b, --bandwidth INTEGER
+ -I, --inBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ both IN and OUT if no second (-O) max speed is provided.
+ -O, --outBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ OUT traffic. Uses the same units value given for -b.
+ -u, --units STRING
+ g=gigabits/s,m=megabits/s,k=kilobits/s,b=bits/s. Required if -b, -I, or
+ -O are used.
+ -w, --warning INTEGER
+ % of bandwidth usage necessary to result in warning status (default: 85%)
+ -c, --critical INTEGER
+ % of bandwidth usage necessary to result in critical status (default: 98%)
+ -M, --max INTEGER
+ Max Counter Value of net devices in kilo/mega/giga/bytes.
+ -A, --address STRING (IP Address)
+ IP Address to use when determining the interface index to use. Can be
+ used when the index changes frequently or as in the case of Windows
+ servers the index is different depending on the NIC installed.
+ -L, --list FLAG (on/off)
+ Tell plugin to list available interfaces. This is not supported inside
+ of Nagios, but may be useful from the command line.
+EOU
+
+}
+
diff --git a/roles/icinga-ab/files/commands.cfg b/roles/icinga-ab/files/commands.cfg
new file mode 100644
index 0000000..1ceea2c
--- /dev/null
+++ b/roles/icinga-ab/files/commands.cfg
@@ -0,0 +1,90 @@
+###############################################################################
+# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
+###############################################################################
+
+
+################################################################################
+# NOTIFICATION COMMANDS
+################################################################################
+
+
+# 'notify-host-by-email' command definition
+define command{
+ command_name notify-host-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$
+ }
+
+# 'notify-service-by-email' command definition
+define command{
+ command_name notify-service-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$
+ }
+
+
+
+
+
+################################################################################
+# HOST CHECK COMMANDS
+################################################################################
+
+# On Debian, check-host-alive is being defined from within the
+# nagios-plugins-basic package
+define command{
+ command_name check_snmp_storage
+ command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -m $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_load
+ command_line $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -T $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_mem
+ command_line $USER1$/check_snmp_mem.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_int
+ command_line $USER1$/check_snmp_netint.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -a -m -k -M -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_iftraffic3
+ #command_name check_win_int
+ #command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$
+ #command_line $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -k -M -g -w $ARG4$ -c $ARG5$
+ command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$ -i $ARG2$ -w $ARG3$ -c $ARG4$
+}
+
+define command{
+ command_name check_snmp
+ command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
+}
+###############################
+##WINDOWS
+###############################
+
+define command{
+ command_name check_nt
+ command_line $USER1$/check_nt -H $HOSTADDRESS$ -s root -p 12489 -v $ARG1$ $ARG2$
+}
+
+################################################################################
+# PERFORMANCE DATA COMMANDS
+################################################################################
+
+
+# 'process-host-perfdata' command definition
+define command{
+ command_name process-host-perfdata
+ command_line /usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /var/lib/nagios3/host-perfdata.out
+ }
+
+
+# 'process-service-perfdata' command definition
+define command{
+ command_name process-service-perfdata
+ command_line /usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /var/lib/nagios3/service-perfdata.out
+ }
diff --git a/roles/icinga-ab/files/contacts_icinga.cfg b/roles/icinga-ab/files/contacts_icinga.cfg
new file mode 100644
index 0000000..8a66285
--- /dev/null
+++ b/roles/icinga-ab/files/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email icinga.ppe31@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-ab/files/dns.cfg b/roles/icinga-ab/files/dns.cfg
new file mode 100644
index 0000000..5b69aca
--- /dev/null
+++ b/roles/icinga-ab/files/dns.cfg
@@ -0,0 +1,11 @@
+# 'check_dns' command definition
+define command{
+ command_name check_dns
+ command_line /usr/lib/nagios/plugins/check_dns -H www.dfco.fr -s '$HOSTADDRESS$'
+}
+
+# 'check_dig' command definition
+define command{
+ command_name check_dig
+ command_line /usr/lib/nagios/plugins/check_dig -H '$HOSTADDRESS$' -l '$ARG1$'
+}
diff --git a/roles/icinga-ab/files/hostgroups_icinga.cfg b/roles/icinga-ab/files/hostgroups_icinga.cfg
new file mode 100644
index 0000000..621646b
--- /dev/null
+++ b/roles/icinga-ab/files/hostgroups_icinga.cfg
@@ -0,0 +1,74 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-infra, s-proxy, r-int, r-ext, s-adm, s-test
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-adm, s-infra, s-proxy, r-int, r-ext, localhost, s-test, gwsio2
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-infra, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members r-int, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+#define hostgroup {
+# hostgroup_name email-servers
+# alias serveurs-email
+# members s-mess
+# }
+
+define hostgroup {
+ hostgroup_name proxy-servers
+ alias serveurs-proxy
+ members s-proxy
+}
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members srv-2012
+}
+
+#define hostgroup{
+# hostgroup_name switch
+# alias switch
+# members netgear
+#}
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members s-infra, s-proxy, r-int, r-ext, s-adm, s-test
+}
+
diff --git a/roles/icinga-ab/files/icinga.cfg b/roles/icinga-ab/files/icinga.cfg
new file mode 100644
index 0000000..fde1780
--- /dev/null
+++ b/roles/icinga-ab/files/icinga.cfg
@@ -0,0 +1,1494 @@
+##############################################################################
+#
+# ICINGA.CFG - Sample Main Config File for Icinga
+#
+# Read the documentation for more information on this configuration
+# file. I've provided some comments here, but things may not be so
+# clear without further explanation.
+#
+##############################################################################
+
+
+# LOG FILE
+# This is the main log file where service and host events are logged
+# for historical purposes. This should be the first option specified
+# in the config file!!!
+
+log_file=/var/log/icinga/icinga.log
+
+# Commands definitions
+cfg_file=/etc/icinga/commands.cfg
+
+# Debian also defaults to using the check commands defined by the debian
+# nagios-plugins package
+cfg_dir=/etc/nagios-plugins/config
+
+# OBJECT CONFIGURATION FILE(S)
+# These are the object configuration files in which you define hosts,
+# host groups, contacts, contact groups, services, etc.
+# Hint: Check the docs/wiki on how to monitor remote hosts with different
+# transport methods and plugins
+
+# Debian uses by default a configuration directory where icinga-common,
+# other packages and the local admin can dump or link configuration
+# files into.
+cfg_dir=/etc/icinga/objects/
+
+# Definitions for ido2db process checks
+#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg
+
+# Definitions for broker modules like idoutils.cfg
+cfg_dir=/etc/icinga/modules
+
+
+
+# OBJECT CACHE FILE
+# This option determines where object definitions are cached when
+# Icinga starts/restarts. The CGIs read object definitions from
+# this cache file (rather than looking at the object config files
+# directly) in order to prevent inconsistencies that can occur
+# when the config files are modified after Icinga starts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the objects cache file entirely.
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+# Tip: Use that file to debug your configuration with fully resolved
+# objects like the core sees them.
+
+object_cache_file=/var/cache/icinga/objects.cache
+
+
+
+# PRE-CACHED OBJECT FILE
+# This options determines the location of the precached object file.
+# If you run Icinga with the -p command line option, it will preprocess
+# your object configuration file(s) and write the cached config to this
+# file. You can then start Icinga with the -u option to have it read
+# object definitions from this precached file, rather than the standard
+# object configuration files (see the cfg_file and cfg_dir options above).
+# Using a precached object file can speed up the time needed to (re)start
+# the Icinga process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Icinga to find our more
+# about how this feature works.
+
+precached_object_file=/var/cache/icinga/objects.precache
+
+
+
+# RESOURCE FILE
+# This is an optional resource file that contains $USERx$ macro
+# definitions. Multiple resource files can be specified by using
+# multiple resource_file definitions. The CGIs will not attempt to
+# read the contents of resource files, so information that is
+# considered to be sensitive (usernames, passwords, etc) can be
+# defined as macros in this file and restrictive permissions (600)
+# can be placed on this file.
+
+resource_file=/etc/icinga/resource.cfg
+
+
+
+# STATUS FILE
+# This is where the current status of all monitored services and
+# hosts is stored. Its contents are read and processed by the CGIs.
+# The contents of the status file are deleted every time Icinga
+# restarts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the status file entirely. This becomes handy when using other methods
+# for data retrieval (e.g. IDOUtils DB)
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+
+status_file=/var/lib/icinga/status.dat
+
+
+
+# STATUS FILE UPDATE INTERVAL
+# This option determines the frequency (in seconds) that
+# Icinga will periodically dump program, host, and
+# service status data.
+# Increase the value, if you don't require it that often.
+
+#status_update_interval=30
+status_update_interval=10
+
+
+
+# ICINGA USER
+# This determines the effective user that Icinga should run as.
+# You can either supply a username or a UID.
+
+icinga_user=nagios
+
+
+
+# ICINGA GROUP
+# This determines the effective group that Icinga should run as.
+# You can either supply a group name or a GID.
+
+icinga_group=nagios
+
+
+
+# EXTERNAL COMMAND OPTION
+# This option allows you to specify whether or not Icinga should check
+# for external commands (in the command file defined below). By default
+# Icinga will *not* check for external commands, just to be on the
+# cautious side. If you want to be able to use the CGI command interface
+# you will have to enable this.
+# Values: 0 = disable commands, 1 = enable commands
+
+check_external_commands=1
+
+
+
+# EXTERNAL COMMAND CHECK INTERVAL
+# This is the interval at which Icinga should check for external commands.
+# This value works of the interval_length you specify later. If you leave
+# that at its default value of 60 (seconds), a value of 1 here will cause
+# Icinga to check for external commands every minute. If you specify a
+# number followed by an "s" (i.e. 15s), this will be interpreted to mean
+# actual seconds rather than a multiple of the interval_length variable.
+# Note: In addition to reading the external command file at regularly
+# scheduled intervals, Icinga will also check for external commands after
+# event handlers are executed.
+# NOTE: Setting this value to -1 causes Icinga to check the external
+# command file as often as possible.
+
+#command_check_interval=15s
+command_check_interval=-1
+
+
+
+# EXTERNAL COMMAND FILE
+# This is the file that Icinga checks for external command requests.
+# It is also where the command CGI will write commands that are submitted
+# by users, so it must be writeable by the user that the web server
+# is running as (usually 'nobody'). Permissions should be set at the
+# directory level instead of on the file, as the file is deleted every
+# time its contents are processed.
+# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
+# time to do it.
+
+command_file=/var/lib/icinga/rw/icinga.cmd
+
+
+
+# EXTERNAL COMMAND BUFFER SLOTS
+# This settings is used to tweak the number of items or "slots" that
+# the Icinga daemon should allocate to the buffer that holds incoming
+# external commands before they are processed. As external commands
+# are processed by the daemon, they are removed from the buffer.
+# Increase the value, if you are using addons like check_mk supplying
+# more external commands (passive check results) than usual.
+
+#external_command_buffer_slots=32768
+external_command_buffer_slots=4096
+
+
+
+# LOCK FILE
+# This is the lockfile that Icinga will use to store its PID number
+# in when it is running in daemon mode.
+
+lock_file=/var/run/icinga/icinga.pid
+
+
+
+# TEMP FILE
+# This is a temporary file that is used as scratch space when Icinga
+# updates the status log, cleans the comment file, etc. This file
+# is created, used, and deleted throughout the time that Icinga is
+# running.
+
+temp_file=/var/cache/icinga/icinga.tmp
+
+
+
+# TEMP PATH
+# This is path where Icinga can create temp files for service and
+# host check results, etc.
+
+temp_path=/tmp
+
+
+
+# EVENT BROKER OPTIONS
+# Controls what (if any) data gets sent to the event broker.
+# Values: 0 = Broker nothing
+# -1 = Broker everything
+# <other> = See documentation
+
+event_broker_options=-1
+
+
+
+# EVENT BROKER MODULE(S)
+# ----> use the new *module definition* instead:
+# ----> http://docs.icinga.org/latest/en/objectdefinitions.html
+#
+# Example definitions can be found in the '/etc/icinga/modules/' directory.
+# If you want to enable idoutils in Debian install icinga-idoutils and copy
+# /usr/share/doc/icinga-idoutils/examples/idoutils.cfg-sample to
+# /etc/icinga/modules/idoutils.cfg.
+# Don't forget to also enable the daemon in /etc/default/icinga
+
+# LOG ROTATION METHOD
+# This is the log rotation method that Icinga should use to rotate
+# the main log file. Values are as follows..
+# n = None - don't rotate the log
+# h = Hourly rotation (top of the hour)
+# d = Daily rotation (midnight every day)
+# w = Weekly rotation (midnight on Saturday evening)
+# m = Monthly rotation (midnight last day of month)
+
+log_rotation_method=d
+
+
+
+# LOG ARCHIVE PATH
+# This is the directory where archived (rotated) log files should be
+# placed (assuming you've chosen to do log rotation).
+
+log_archive_path=/var/log/icinga/archives
+
+
+
+# LOGGING OPTIONS FOR DAEMON
+# If you want messages logged to the daemon log file (usually icinga.log).
+# Default option is 1 (yes), the other valid option is 0 (no)
+
+use_daemon_log=1
+
+
+
+# LOGGING OPTIONS FOR SYSLOG
+# If you want messages logged to the syslog facility, as well as the
+# Icinga log file set this option to 1. If not, set it to 0.
+
+use_syslog=1
+
+
+
+# SYSLOG FACILITY
+# If you enabled use_syslog you can set icinga to use a local facility
+# instead of the default.To enable set this option to 1, if not, set it to 0.
+
+use_syslog_local_facility=0
+
+
+
+# SYSLOG LOCAL FACILITY
+# If you specified the use_syslog_local_facility you can chose which
+# local facility to use. Valid values are from 0 to 7
+
+syslog_local_facility=5
+
+
+
+# NOTIFICATION LOGGING OPTION
+# If you don't want notifications to be logged, set this value to 0.
+# If notifications should be logged, set the value to 1.
+
+log_notifications=1
+
+
+
+# SERVICE RETRY LOGGING OPTION
+# If you don't want service check retries to be logged, set this value
+# to 0. If retries should be logged, set the value to 1.
+
+log_service_retries=1
+
+
+
+# HOST RETRY LOGGING OPTION
+# If you don't want host check retries to be logged, set this value to
+# 0. If retries should be logged, set the value to 1.
+
+log_host_retries=1
+
+
+
+# EVENT HANDLER LOGGING OPTION
+# If you don't want host and service event handlers to be logged, set
+# this value to 0. If event handlers should be logged, set the value
+# to 1.
+
+log_event_handlers=1
+
+
+
+# INITIAL STATES LOGGING OPTION
+# If you want Icinga to log all initial host and service states to
+# the main log file (the first time the service or host is checked)
+# you can enable this option by setting this value to 1. If you
+# are not using an external application that does long term state
+# statistics reporting, you do not need to enable this option. In
+# this case, set the value to 0.
+
+log_initial_states=0
+
+
+
+# CURRENT STATES LOGGING OPTION
+# If you don't want Icinga to log all current host and service states
+# after log has been rotated to the main log file, you can disable this
+# option by setting this value to 0. Default value is 1.
+
+log_current_states=1
+
+
+
+# EXTERNAL COMMANDS LOGGING OPTION
+# If you don't want Icinga to log external commands, set this value
+# to 0. If external commands should be logged, set this value to 1.
+# Note: This option does not include logging of passive service
+# checks - see the option below for controlling whether or not
+# passive checks are logged.
+
+log_external_commands=1
+
+
+
+# LOG ANONYMIZED EXTERNAL COMMAND AUTHOR !!EXPERIMENTAL!!
+# This option substitutes the user name on external commands with
+# the string "<anon>" if the command gets logged. It is
+# anonymized in log files only. This option was added to make
+# icinga compliant with data retention laws on various countries.
+# This option is disabled by default.
+
+log_anonymized_external_command_author=0
+
+
+
+# PASSIVE CHECKS LOGGING OPTION
+# If you don't want Icinga to log passive host and service checks, set
+# this value to 0. If passive checks should be logged, set
+# this value to 1.
+
+log_passive_checks=1
+
+
+
+# LONG PLUGIN OUTPUT LOGGING OPTION
+# If you want Icinga to log the complete text of the plugin output
+# to the log instead of only the first line then set this value to 1.
+# Default value is 0.
+
+log_long_plugin_output=0
+
+
+
+# GLOBAL HOST AND SERVICE EVENT HANDLERS
+# These options allow you to specify a host and service event handler
+# command that is to be run for every host or service state change.
+# The global event handler is executed immediately prior to the event
+# handler that you have optionally specified in each host or
+# service definition. The command argument is the short name of a
+# command definition that you define in your host configuration file.
+# Read the HTML docs for more information.
+
+#global_host_event_handler=somecommand
+#global_service_event_handler=somecommand
+
+
+
+# SERVICE INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" service checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all service checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)! This is not a
+# good thing for production, but is useful when testing the
+# parallelization functionality.
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+service_inter_check_delay_method=s
+
+
+
+# MAXIMUM SERVICE CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all services should
+# be completed. Default is 30 minutes.
+
+max_service_check_spread=30
+
+
+
+# SERVICE CHECK INTERLEAVE FACTOR
+# This variable determines how service checks are interleaved.
+# Interleaving the service checks allows for a more even
+# distribution of service checks and reduced load on remote
+# hosts. Setting this value to 1 is equivalent to how versions
+# of Icinga previous to 0.0.5 did service checks. Set this
+# value to s (smart) for automatic calculation of the interleave
+# factor unless you have a specific reason to change it.
+# s = Use "smart" interleave factor calculation
+# x = Use an interleave factor of x, where x is a
+# number greater than or equal to 1.
+
+service_interleave_factor=s
+
+
+
+# HOST INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" host checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all host checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)!
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+host_inter_check_delay_method=s
+
+
+
+# MAXIMUM HOST CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all hosts should
+# be completed. Default is 30 minutes.
+
+max_host_check_spread=30
+
+
+
+# MAXIMUM CONCURRENT SERVICE CHECKS
+# This option allows you to specify the maximum number of
+# service checks that can be run in parallel at any given time.
+# Specifying a value of 1 for this variable essentially prevents
+# any service checks from being parallelized. A value of 0
+# will not restrict the number of concurrent checks that are
+# being executed.
+
+max_concurrent_checks=0
+
+
+
+# HOST AND SERVICE CHECK REAPER FREQUENCY
+# This is the frequency (in seconds!) that Icinga will process
+# the results of host and service checks.
+# Lower this value in larger environments to allow faster
+# check result processing (requires more cpu power).
+
+#check_result_reaper_frequency=1
+check_result_reaper_frequency=10
+
+
+
+
+# MAX CHECK RESULT REAPER TIME
+# This is the max amount of time (in seconds) that a single
+# check result reaper event will be allowed to run before
+# returning control back to Icinga so it can perform other
+# duties.
+
+max_check_result_reaper_time=30
+
+
+
+
+# CHECK RESULT PATH
+# This is directory where Icinga stores the results of host and
+# service checks that have not yet been processed.
+#
+# Note: Make sure that only one instance of Icinga has access
+# to this directory!
+
+check_result_path=/var/lib/icinga/spool/checkresults
+
+
+
+
+# MAX CHECK RESULT FILE AGE
+# This option determines the maximum age (in seconds) which check
+# result files are considered to be valid. Files older than this
+# threshold will be mercilessly deleted without further processing.
+
+max_check_result_file_age=3600
+
+
+
+
+# MAX CHECK RESULT LIST ITEMS !!EXPERIMENTAL!!
+# This experimental option allows you to set the max number of items
+# the checkresult reaper will put onto the checkresult list for further
+# processing by the core. If there are too many, the reaping will be
+# terminated early, allowing the core to process the results sooner.
+# On larger setups, that list might grow too much, and decrease
+# performance on processing. You might experiment with that value, the
+# inner core default is set to 0, disabling that feature.
+# Values:
+# 0 = Disable max check result list items
+# number = set max check result list items
+
+#max_check_result_list_items=1024
+
+
+
+
+# CACHED HOST CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous host check is considered current.
+# Cached host states (from host checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to the host check logic.
+# Too high of a value for this option may result in inaccurate host
+# states being used by Icinga, while a lower value may result in a
+# performance hit for host checks. Use a value of 0 to disable host
+# check caching.
+
+cached_host_check_horizon=15
+
+
+
+# CACHED SERVICE CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous service check is considered current.
+# Cached service states (from service checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to predictive dependency checks.
+# Use a value of 0 to disable service check caching.
+
+cached_service_check_horizon=15
+
+
+
+# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of hosts when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# host dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_host_dependency_checks=1
+
+
+
+# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of service when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# service dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_service_dependency_checks=1
+
+
+
+# SOFT STATE DEPENDENCIES
+# This option determines whether or not Icinga will use soft state
+# information when checking host and service dependencies. Normally
+# Icinga will only use the latest hard host or service state when
+# checking dependencies. If you want it to use the latest state (regardless
+# of whether its a soft or hard state type), enable this option.
+# Values:
+# 0 = Don't use soft state dependencies (default)
+# 1 = Use soft state dependencies
+
+soft_state_dependencies=0
+
+
+
+# TIME CHANGE ADJUSTMENT THRESHOLDS
+# These options determine when Icinga will react to detected changes
+# in system time (forward into the future).
+
+#time_change_threshold=900
+
+
+
+# AUTO-RESCHEDULING OPTION
+# This option determines whether or not Icinga will attempt to
+# automatically reschedule active host and service checks to
+# "smooth" them out over time. This can help balance the load on
+# the monitoring server.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_reschedule_checks=0
+
+
+
+# AUTO-RESCHEDULING INTERVAL
+# This option determines how often (in seconds) Icinga will
+# attempt to automatically reschedule checks. This option only
+# has an effect if the auto_reschedule_checks option is enabled.
+# Default is 30 seconds.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_interval=30
+
+
+
+# AUTO-RESCHEDULING WINDOW
+# This option determines the "window" of time (in seconds) that
+# Icinga will look at when automatically rescheduling checks.
+# Only host and service checks that occur in the next X seconds
+# (determined by this variable) will be rescheduled. This option
+# only has an effect if the auto_reschedule_checks option is
+# enabled. Default is 180 seconds (3 minutes).
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_window=180
+
+
+
+# SLEEP TIME
+# This is the number of seconds to sleep between checking for system
+# events and service checks that need to be run.
+
+sleep_time=0.25
+
+
+
+# TIMEOUT VALUES
+# These options control how much time Icinga will allow various
+# types of commands to execute before killing them off. Options
+# are available for controlling maximum time allotted for
+# service checks, host checks, event handlers, notifications, the
+# ocsp command, and performance data commands. All values are in
+# seconds.
+# Increase the timeout values in case you are experiencing a lot
+# of check timeouts. Addons like e.g. check_mk will perform
+# one combined active servicecheck which could take longer than
+# the default of 60sec.
+
+#service_check_timeout=120
+service_check_timeout=60
+host_check_timeout=30
+event_handler_timeout=30
+notification_timeout=30
+ocsp_timeout=5
+perfdata_timeout=5
+
+
+
+# RETAIN STATE INFORMATION
+# This setting determines whether or not Icinga will save state
+# information for services and hosts before it shuts down. Upon
+# startup Icinga will reload all saved service and host state
+# information before starting to monitor. This is useful for
+# maintaining long-term data on state statistics, etc, but will
+# slow Icinga down a bit when it (re)starts. Since its only
+# a one-time penalty, I think its well worth the additional
+# startup delay.
+
+retain_state_information=1
+
+
+
+# STATE RETENTION FILE
+# This is the file that Icinga should use to store host and
+# service state information before it shuts down. The state
+# information in this file is also read immediately prior to
+# starting to monitor the network when Icinga is restarted.
+# This file is used only if the retain_state_information
+# variable is set to 1.
+
+state_retention_file=/var/cache/icinga/retention.dat
+
+
+
+# SYNC FILE
+# This is an advanced facility to pass a subset of retention
+# information into Icinga on a running system. This is similar
+# to the state retention file with the following difference:
+#
+# - if the last_check value is less than the current last_check,
+# then the state information is ignored (this must be specified
+# immediately after the object identifiers)
+#
+# - downtimes and comments are not identified by an id number, but
+# by other "similar characteristics". This is required to work in
+# a distributed Nagios environment
+# * downtimes: hostname, servicename (if appropriate), author,
+# comment, start_time, end_time, fixed, duration
+# * comments: hostname, servicename, author, comment
+#
+# If this variable is set, then on Icinga startup, the sync file
+# will be read after the retention file has been processed. If the
+# file is read successfully, it will be removed.
+# If the file does not exist, no error will appear.
+# There is also an API that will force a read of the sync file.
+
+#sync_retention_file=/var/cache/icinga/sync.dat
+
+
+
+# RETENTION DATA UPDATE INTERVAL
+# This setting determines how often (in minutes) that Icinga
+# will automatically save retention data during normal operation.
+# If you set this value to 0, Icinga will not save retention
+# data at regular interval, but it will still save retention
+# data before shutting down or restarting. If you have disabled
+# state retention, this option has no effect.
+
+retention_update_interval=60
+
+
+
+# USE RETAINED PROGRAM STATE
+# This setting determines whether or not Icinga will set
+# program status variables based on the values saved in the
+# retention file. If you want to use retained program status
+# information, set this value to 1. If not, set this value
+# to 0.
+
+use_retained_program_state=1
+
+
+# DUMP RETAINED HOST SERVICE STATES TO NEB
+# This setting determines wether or not Icinga will dump host
+# and service states based on the values saved in the retention
+# file to the neb modules. It will already do that on event loop
+# initialization.
+# Changed in Icinga 1.10 to disabled - re-enable if you require it.
+
+dump_retained_host_service_states_to_neb=0
+
+
+
+# USE RETAINED SCHEDULING INFO
+# This setting determines whether or not Icinga will retain
+# the scheduling info (next check time) for hosts and services
+# based on the values saved in the retention file. If you
+# If you want to use retained scheduling info, set this
+# value to 1. If not, set this value to 0.
+
+use_retained_scheduling_info=1
+
+
+
+# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
+# The following variables are used to specify specific host and
+# service attributes that should *not* be retained by Icinga during
+# program restarts.
+#
+# The values of the masks are bitwise ANDs of values specified
+# by the "MODATTR_" definitions found in include/common.h.
+# For example, if you do not want the current enabled/disabled state
+# of flap detection and event handlers for hosts to be retained, you
+# would use a value of 24 for the host attribute mask...
+# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
+
+# This mask determines what host attributes are not retained
+retained_host_attribute_mask=0
+
+# This mask determines what service attributes are not retained
+retained_service_attribute_mask=0
+
+# These two masks determine what process attributes are not retained.
+# There are two masks, because some process attributes have host and service
+# options. For example, you can disable active host checks, but leave active
+# service checks enabled.
+retained_process_host_attribute_mask=0
+retained_process_service_attribute_mask=0
+
+# These two masks determine what contact attributes are not retained.
+# There are two masks, because some contact attributes have host and
+# service options. For example, you can disable host notifications for
+# a contact, but leave service notifications enabled for them.
+retained_contact_host_attribute_mask=0
+retained_contact_service_attribute_mask=0
+
+
+
+# INTERVAL LENGTH
+# This is the seconds per unit interval as used in the
+# host/contact/service configuration files. Setting this to 60 means
+# that each interval is one minute long (60 seconds). Other settings
+# have not been tested much, so your mileage is likely to vary...
+
+interval_length=60
+
+
+
+# AGGRESSIVE HOST CHECKING OPTION
+# If you don't want to turn on aggressive host checking features, set
+# this value to 0 (the default). Otherwise set this value to 1 to
+# enable the aggressive check option. Read the docs for more info
+# on what aggressive host check is or check out the source code in
+# base/checks.c
+
+use_aggressive_host_checking=0
+
+
+
+# SERVICE CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# service checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of service checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_service_checks=1
+
+
+
+# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# service checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_service_checks=1
+
+
+
+# HOST CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# host checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of host checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_host_checks=1
+
+
+
+# PASSIVE HOST CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# host checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_host_checks=1
+
+
+
+# NOTIFICATIONS OPTION
+# This determines whether or not Icinga will sent out any host or
+# service notifications when it is initially (re)started.
+# Values: 1 = enable notifications, 0 = disable notifications
+
+enable_notifications=1
+
+
+
+# EVENT HANDLER USE OPTION
+# This determines whether or not Icinga will run any host or
+# service event handlers when it is initially (re)started. Unless
+# you're implementing redundant hosts, leave this option enabled.
+# Values: 1 = enable event handlers, 0 = disable event handlers
+
+enable_event_handlers=1
+
+
+
+# STATE BASED ESCALATION RANGES !!!Experimental!!!
+# This option allows you to enable state based escalation ranges which
+# will allow a more detailed granularity on when an escalation notification
+# may happen, adding a filter based on the current host or service state
+# when checking the escalation for notification viability.
+# This is a behavioural change to the default, and therefore intentionally
+# disabled. Enable at your own risk, as this remains an experimental feature.
+# Values: 1 = enable state based escalation ranges,
+# 0 = disable state based escalation ranges
+
+#enable_state_based_escalation_ranges=0
+
+
+
+# PROCESS PERFORMANCE DATA OPTION
+# This determines whether or not Icinga will process performance
+# data returned from service and host checks. If this option is
+# enabled, host performance data will be processed using the
+# host_perfdata_command (defined below) and service performance
+# data will be processed using the service_perfdata_command (also
+# defined below). Read the HTML docs for more information on
+# performance data.
+# Values: 1 = process performance data, 0 = do not process performance data
+
+process_performance_data=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
+# These commands are run after every host and service check is
+# performed. These commands are executed only if the
+# process_performance_data option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on performance data.
+
+#host_perfdata_command=process-host-perfdata
+#service_perfdata_command=process-service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILES
+# These files are used to store host and service performance data.
+# Performance data is only written to these files if the
+# process_performance_data option (above) is set to 1.
+
+#host_perfdata_file=/tmp/host-perfdata
+#service_perfdata_file=/tmp/service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
+# These options determine what data is written (and how) to the
+# performance data files. The templates may contain macros, special
+# characters (\t for tab, \r for carriage return, \n for newline)
+# and plain text. A newline is automatically added after each write
+# to the performance data file. Some examples of what you can do are
+# shown below.
+
+#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
+#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE MODES
+# This option determines whether or not the host and service
+# performance data files are opened in write ("w") or append ("a")
+# mode. If you want to use named pipes, you should use the special
+# pipe ("p") mode which avoid blocking at startup, otherwise you will
+# likely want the defult append ("a") mode.
+
+#host_perfdata_file_mode=a
+#service_perfdata_file_mode=a
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
+# These options determine how often (in seconds) the host and service
+# performance data files are processed using the commands defined
+# below. A value of 0 indicates the files should not be periodically
+# processed.
+
+#host_perfdata_file_processing_interval=0
+#service_perfdata_file_processing_interval=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
+# These commands are used to periodically process the host and
+# service performance data files. The interval at which the
+# processing occurs is determined by the options above.
+
+#host_perfdata_file_processing_command=process-host-perfdata-file
+#service_perfdata_file_processing_command=process-service-perfdata-file
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
+# THese options determine wether the core will process empty perfdata
+# results or not. This is needed for distributed monitoring, and intentionally
+# turned on by default.
+# If you don't require empty perfdata - saving some cpu cycles
+# on unwanted macro calculation - you can turn that off. Be careful!
+# Values: 1 = enable, 0 = disable
+
+#host_perfdata_process_empty_results=1
+#service_perfdata_process_empty_results=1
+
+
+
+# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
+# This boolean option determines whether services assigned to empty
+# host groups (host groups with no host members) will cause Icinga to
+# exit with error on start up (or during a configuration check) or not.
+# It's useful to be able to assign services to empty hostgroups when
+# configuration files or pre-cached object files are distributed to
+# various pollers, or when the process of generating Icinga config is
+# automated, or when a set of services is slowly being phased out but
+# should be kept around.
+# The default behavior if the option is not present in the main
+# configuration file is for Icinga to exit with error if services are
+# associated with host groups that have no hosts associated with them.
+
+#allow_empty_hostgroup_assignment=0
+
+
+
+# OBSESS OVER SERVICE CHECKS OPTION
+# This determines whether or not Icinga will obsess over service
+# checks and run the ocsp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over services, 0 = do not obsess (default)
+
+obsess_over_services=0
+
+
+
+# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
+# This is the command that is run for every service check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_services option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ocsp_command=somecommand
+
+
+
+# OBSESS OVER HOST CHECKS OPTION
+# This determines whether or not Icinga will obsess over host
+# checks and run the ochp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over hosts, 0 = do not obsess (default)
+
+obsess_over_hosts=0
+
+
+
+# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
+# This is the command that is run for every host check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_hosts option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ochp_command=somecommand
+
+
+
+# TRANSLATE PASSIVE HOST CHECKS OPTION
+# This determines whether or not Icinga will translate
+# DOWN/UNREACHABLE passive host check results into their proper
+# state for this instance of Icinga. This option is useful
+# if you have distributed or failover monitoring setup. In
+# these cases your other Icinga servers probably have a different
+# "view" of the network, with regards to the parent/child relationship
+# of hosts. If a distributed monitoring server thinks a host
+# is DOWN, it may actually be UNREACHABLE from the point of
+# this Icinga instance. Enabling this option will tell Icinga
+# to translate any DOWN or UNREACHABLE host states it receives
+# passively into the correct state from the view of this server.
+# Values: 1 = perform translation, 0 = do not translate (default)
+
+translate_passive_host_checks=0
+
+
+
+# PASSIVE HOST CHECKS ARE SOFT OPTION
+# This determines whether or not Icinga will treat passive host
+# checks as being HARD or SOFT. By default, a passive host check
+# result will put a host into a HARD state type. This can be changed
+# by enabling this option.
+# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
+
+passive_host_checks_are_soft=0
+
+
+
+# ORPHANED HOST/SERVICE CHECK OPTIONS
+# These options determine whether or not Icinga will periodically
+# check for orphaned host service checks. Since service checks are
+# not rescheduled until the results of their previous execution
+# instance are processed, there exists a possibility that some
+# checks may never get rescheduled. A similar situation exists for
+# host checks, although the exact scheduling details differ a bit
+# from service checks. Orphaned checks seem to be a rare
+# problem and should not happen under normal circumstances.
+# If you have problems with service checks never getting
+# rescheduled, make sure you have orphaned service checks enabled.
+# Values: 1 = enable checks, 0 = disable checks
+
+check_for_orphaned_services=1
+check_for_orphaned_hosts=1
+
+
+
+# SERVICE CHECK TIMEOUT STATE
+# This setting determines the state Icinga will report when a
+# service check times out meaning it does not respond within
+# service_check_timeout seconds. The default is set to Unknown
+# and not Critical.
+# Valid settings are:
+# c - Critical
+# u - Unknown (default)
+# w - Warning
+# o - OK
+
+service_check_timeout_state=u
+
+
+
+# SERVICE FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of service results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_service_freshness=1
+
+
+
+# SERVICE FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of service check results. If you have
+# disabled service freshness checking, this option has no effect.
+
+service_freshness_check_interval=60
+
+
+
+# HOST FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of host results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_host_freshness=0
+
+
+
+# HOST FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of host check results. If you have
+# disabled host freshness checking, this option has no effect.
+
+host_freshness_check_interval=60
+
+
+
+
+# ADDITIONAL FRESHNESS THRESHOLD LATENCY
+# This setting determines the number of seconds that Icinga
+# will add to any host and service freshness thresholds that
+# it calculates (those not explicitly specified by the user).
+
+additional_freshness_latency=15
+
+
+
+
+# FLAP DETECTION OPTION
+# This option determines whether or not Icinga will try
+# and detect hosts and services that are "flapping".
+# Flapping occurs when a host or service changes between
+# states too frequently. When Icinga detects that a
+# host or service is flapping, it will temporarily suppress
+# notifications for that host/service until it stops
+# flapping. Flap detection is very experimental, so read
+# the HTML documentation before enabling this feature!
+# Values: 1 = enable flap detection
+# 0 = disable flap detection (default)
+
+enable_flap_detection=1
+
+
+
+# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
+# Read the HTML documentation on flap detection for
+# an explanation of what this option does. This option
+# has no effect if flap detection is disabled.
+
+low_service_flap_threshold=5.0
+high_service_flap_threshold=20.0
+low_host_flap_threshold=5.0
+high_host_flap_threshold=20.0
+
+
+
+# DATE FORMAT OPTION
+# This option determines how short dates are displayed. Valid options
+# include:
+# us (MM-DD-YYYY HH:MM:SS)
+# euro (DD-MM-YYYY HH:MM:SS)
+# iso8601 (YYYY-MM-DD HH:MM:SS)
+# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
+#
+
+date_format=iso8601
+
+
+
+
+# TIMEZONE OFFSET
+# This option is used to override the default timezone that this
+# instance of Icinga runs in. If not specified, Icinga will use
+# the system configured timezone.
+#
+# NOTE: In order to display the correct timezone in the CGIs, you
+# will also need to alter the Apache directives for the CGI path
+# to include your timezone. Example:
+#
+# <Directory "/usr/local/icinga/sbin/">
+# SetEnv TZ "Australia/Brisbane"
+# ...
+# </Directory>
+
+#use_timezone=US/Mountain
+#use_timezone=Australia/Brisbane
+
+
+
+
+# P1.PL FILE LOCATION
+# This value determines where the p1.pl perl script (used by the
+# embedded Perl interpreter) is located. If you didn't compile
+# Icinga with embedded Perl support, this option has no effect.
+
+p1_file=/usr/lib/icinga/p1.pl
+
+
+
+# EMBEDDED PERL INTERPRETER OPTION
+# This option determines whether or not the embedded Perl interpreter
+# will be enabled during runtime. This option has no effect if Icinga
+# has not been compiled with support for embedded Perl.
+# This option is intentionally disabled by default, because embedded
+# perl can cause memory leaks and make Icinga unstable if not properly
+# used.
+# Only enable this setting when you really know what you are doing!
+# Values: 0 = disable interpreter, 1 = enable interpreter
+
+enable_embedded_perl=1
+
+
+
+# EMBEDDED PERL USAGE OPTION
+# This option determines whether or not Icinga will process Perl plugins
+# and scripts with the embedded Perl interpreter if the plugins/scripts
+# do not explicitly indicate whether or not it is okay to do so. Read
+# the HTML documentation on the embedded Perl interpreter for more
+# information on how this option works.
+
+use_embedded_perl_implicitly=1
+
+
+
+# EVENT HANDLERS FOR STALKED HOSTS/SERVICES
+# Allow running event handlers for stalked hosts/services in order
+# to forward to external systems.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_event_handlers_for_hosts=0
+stalking_event_handlers_for_services=0
+
+
+
+# NOTIFICATIONS FOR STALKED HOSTS/SERVICES
+# Allow notifications for stalked hosts/services globally
+# for all contacts in order to notify about a stalking
+# alert.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_notifications_for_hosts=0
+stalking_notifications_for_services=0
+
+
+
+# ILLEGAL OBJECT NAME CHARACTERS
+# This option allows you to specify illegal characters that cannot
+# be used in host names, service descriptions, or names of other
+# object types.
+
+illegal_object_name_chars=`~!$%^&*|'"<>?,()=
+
+
+
+# ILLEGAL MACRO OUTPUT CHARACTERS
+# This option allows you to specify illegal characters that are
+# stripped from macros before being used in notifications, event
+# handlers, etc. This DOES NOT affect macros used in service or
+# host check commands.
+# The following macros are stripped of the characters you specify:
+# $HOSTOUTPUT$
+# $HOSTPERFDATA$
+# $HOSTACKAUTHOR$
+# $HOSTACKCOMMENT$
+# $SERVICEOUTPUT$
+# $SERVICEPERFDATA$
+# $SERVICEACKAUTHOR$
+# $SERVICEACKCOMMENT$
+
+illegal_macro_output_chars=`~$&|'"<>
+
+
+
+# KEEP UNKNOWN MACROS
+# This option can be used to keep unknown macros within the output.
+# e.g. check_proc -C $foo$ will remain.
+# This was the default in versions older than Icinga 1.8, but now
+# the default is to remove those macros from the output, causing
+# the shell to interpret $foo and leaving a single $ there. See
+# #2291 for further information.
+# Make sure to escape single dollar signs with another '$', as the
+# docs describe. Other than that, enable this setting to revert to
+# the old behaviour.
+
+keep_unknown_macros=1
+
+
+
+# REGULAR EXPRESSION MATCHING
+# This option controls whether or not regular expression matching
+# takes place in the object config files. Regular expression
+# matching is used to match host, hostgroup, service, and service
+# group names/descriptions in some fields of various object types.
+# Values: 1 = enable regexp matching, 0 = disable regexp matching
+
+use_regexp_matching=0
+
+
+
+# "TRUE" REGULAR EXPRESSION MATCHING
+# This option controls whether or not "true" regular expression
+# matching takes place in the object config files. This option
+# only has an effect if regular expression matching is enabled
+# (see above). If this option is DISABLED, regular expression
+# matching only occurs if a string contains wildcard characters
+# (* and ?). If the option is ENABLED, regexp matching occurs
+# all the time (which can be annoying).
+# Values: 1 = enable true matching, 0 = disable true matching
+
+use_true_regexp_matching=0
+
+
+
+# ADMINISTRATOR EMAIL/PAGER ADDRESSES
+# The email and pager address of a global administrator (likely you).
+# Icinga never uses these values itself, but you can access them by
+# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
+# commands.
+
+admin_email=root@localhost
+admin_pager=pageroot@localhost
+
+
+
+# DAEMON CORE DUMP OPTION
+# This option determines whether or not Icinga is allowed to create
+# a core dump when it runs as a daemon. Note that it is generally
+# considered bad form to allow this, but it may be useful for
+# debugging purposes. Enabling this option doesn't guarantee that
+# a core file will be produced, but that's just life...
+# Values: 1 - Allow core dumps
+# 0 - Do not allow core dumps (default)
+
+daemon_dumps_core=0
+
+
+
+# LARGE INSTALLATION TWEAKS OPTION
+# This option determines whether or not Icinga will take some shortcuts
+# which can save on memory and CPU usage in large Icinga installations.
+# Read the documentation for more information on the benefits/tradeoffs
+# of enabling this option.
+# Values: 1 - Enabled tweaks
+# 0 - Disable tweaks (default)
+
+use_large_installation_tweaks=0
+
+
+
+# ENABLE ENVIRONMENT MACROS
+# This option determines whether or not Icinga will make all standard
+# macros available as environment variables when host/service checks
+# and system commands (event handlers, notifications, etc.) are
+# executed. Enabling this option can cause performance issues in
+# large installations, as it will consume a bit more memory and (more
+# importantly) consume more CPU.
+# Keep in mind that various addons/plugins will require this setting
+# to be enabled (e.g. check_oracle_health) for special usage.
+# Values: 1 - Enable environment variable macros
+# 0 - Disable environment variable macros (default)
+
+enable_environment_macros=1
+
+
+
+# CHILD PROCESS MEMORY OPTION
+# This option determines whether or not Icinga will free memory in
+# child processes (processed used to execute system commands and host/
+# service checks). If you specify a value here, it will override
+# program defaults.
+# Value: 1 - Free memory in child processes
+# 0 - Do not free memory in child processes
+
+#free_child_process_memory=1
+
+
+
+# CHILD PROCESS FORKING BEHAVIOR
+# This option determines how Icinga will fork child processes
+# (used to execute system commands and host/service checks). Normally
+# child processes are fork()ed twice, which provides a very high level
+# of isolation from problems. Fork()ing once is probably enough and will
+# save a great deal on CPU usage (in large installs), so you might
+# want to consider using this. If you specify a value here, it will
+# program defaults.
+# Value: 1 - Child processes fork() twice
+# 0 - Child processes fork() just once
+
+#child_processes_fork_twice=1
+
+
+
+# DEBUG LEVEL
+# This option determines how much (if any) debugging information will
+# be written to the debug file. OR values together to log multiple
+# types of information.
+# Values:
+# -1 = Everything
+# 0 = Nothing
+# 1 = Functions
+# 2 = Configuration
+# 4 = Process information
+# 8 = Scheduled events
+# 16 = Host/service checks
+# 32 = Notifications
+# 64 = Event broker
+# 128 = External commands
+# 256 = Commands
+# 512 = Scheduled downtime
+# 1024 = Comments
+# 2048 = Macros
+
+debug_level=0
+
+
+
+# DEBUG VERBOSITY
+# This option determines how verbose the debug log out will be.
+# Values: 0 = Brief output
+# 1 = More detailed
+# 2 = Very detailed
+
+debug_verbosity=2
+
+
+
+# DEBUG FILE
+# This option determines where Icinga should write debugging information.
+
+debug_file=/var/log/icinga/icinga.debug
+
+
+
+# MAX DEBUG FILE SIZE
+# This option determines the maximum size (in bytes) of the debug file. If
+# the file grows larger than this size, it will be renamed with a .old
+# extension. If a file already exists with a .old extension it will
+# automatically be deleted. This helps ensure your disk space usage doesn't
+# get out of control when debugging Icinga.
+
+# 100M
+max_debug_file_size=100000000
diff --git a/roles/icinga-ab/files/nt.cfg b/roles/icinga-ab/files/nt.cfg
new file mode 100644
index 0000000..b461aca
--- /dev/null
+++ b/roles/icinga-ab/files/nt.cfg
@@ -0,0 +1,15 @@
+# If you are confused about this command definition, cause you was
+# reading other suggestions, please have a look into
+# /usr/share/doc/nagios-plugins/README.Debian
+
+# 'check_nt' command definition
+#define command {
+# command_name check_nt
+# command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -v '$ARG1$'
+#}
+
+# 'check_nscp' command definition
+define command {
+ command_name check_nscp
+ command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -p 12489 -v '$ARG1$'
+}
diff --git a/roles/icinga-ab/files/services_icinga.cfg b/roles/icinga-ab/files/services_icinga.cfg
new file mode 100644
index 0000000..4ea25d8
--- /dev/null
+++ b/roles/icinga-ab/files/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-ab/handlers/main.yml b/roles/icinga-ab/handlers/main.yml
new file mode 100644
index 0000000..721651e
--- /dev/null
+++ b/roles/icinga-ab/handlers/main.yml
@@ -0,0 +1,12 @@
+---
+ - name: restart icinga
+ service: name=icinga state=restarted
+
+ - name: stop icinga
+ service: name=icinga state=stopped
+
+ - name: start icinga
+ service: name=icinga state=started
+
+ - name: restart apache
+ service: name=apache2 state=restarted
diff --git a/roles/icinga-ab/tasks/main.yml b/roles/icinga-ab/tasks/main.yml
new file mode 100644
index 0000000..8829708
--- /dev/null
+++ b/roles/icinga-ab/tasks/main.yml
@@ -0,0 +1,161 @@
+---
+- name: Installation apache2
+ apt: name=apache2 state=present
+
+- name: Installation snmp
+ apt: name=snmp state=present
+
+- name: Installation de icinga
+ apt: name=icinga state=present
+
+- name: Installation de nagios-plugins
+ apt: name=nagios-plugins state=present
+
+- name: Installation de nagios-snmp-plugins
+ apt: name=nagios-snmp-plugins state=present
+
+- name: Installation des dépendances dns
+ apt: name=libnet-dns-perl state=present
+
+#- name: Copie de fichier apache.conf
+# copy: remote_src=true src=/etc/icinga/apache2.conf dest=/etc/apache2/sites-available/icinga.conf
+
+#- name: activation du site de icinga
+# shell: a2ensite icinga
+# notify:
+# - restart icinga
+
+- name: changement de mot de passe de icingaadmin
+ shell: htpasswd -dbc /etc/icinga/htpasswd.users icingaadmin root
+
+- name: Copie du fichier commands.cfg
+ copy: src=commands.cfg dest=/etc/icinga/commands.cfg
+
+- name: Copie du fichier icinga.cfg
+ copy: src=icinga.cfg dest=/etc/icinga
+
+- name: Copie du fichier contact
+ copy: src=contacts_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-infra.cfg
+ copy: src=cfg/s-infra.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier s-proxy.cfg
+ copy: src=cfg/s-proxy.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier s-adm.cfg
+ copy: src=cfg/s-adm.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier r-int.cfg
+ copy: src=cfg/r-int.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier r-ext.cfg
+ copy: src=cfg/r-ext.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+#- name: Copie du fichier netgear
+# copy: src=cfg/netgear.cfg dest=/etc/icinga/objects
+# notify:
+# - restart icinga
+
+- name: Copie du fichier serveur
+ copy: src=cfg/srv-2012.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier gwsio2
+ copy: src=cfg/gwsio2.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier s-test
+ copy: src=cfg/s-test.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier hostgroup
+ copy: src=hostgroups_icinga.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier services
+ copy: src=services_icinga.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+#- name: attribution des droits dossier icinga rw
+# file:
+# path: /var/lib/icinga/rw
+# owner: nagios
+# mode: 2710
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- name: attribution des droits dossier icinga
+# file:
+# path: /var/lib/icinga
+# owner: nagios
+# mode: 751
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- file:
+# path: /var/lib/icinga/rw
+# state: directory
+# mode: 2770
+# notify:
+# - stop icinga
+
+#- name: attribution des droits dossier var lib icinga
+# shell: chmod 2770 /var/lib/icinga/rw
+# notify:
+# - stop icinga
+
+#- name: attribution des droits dossier var lib icinga
+# file:
+# path: /var/lib/icinga/rw
+# owner: www-data
+# mode: 2710
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- service:
+# name: apache2
+# state: restarted
+# notify:
+# - start icinga
+
+#- name: attribution des droits dossier var lib icinga
+# shell: apache2ctl restart
+# notify:
+# - start icinga
+
+- name: Changement droit notif
+ shell: chmod 644 /var/log/icinga/icinga.log
+
+- name: copie nt.cfg
+ copy: src=nt.cfg dest=/etc/nagios-plugins/config
+
+#- name: copie dns.cfg
+# copy: remote_src=true src=dns.cfg dest=/etc/nagios-plugins/config
+
+- name: copie check traffic
+ copy: src=check_iftraffic3.pl dest=/usr/lib/nagios/plugins
+
+- name: modif des droits plugin traffic
+ shell: chmod 755 /usr/lib/nagios/plugins/check_iftraffic3.pl
+
+- name: message d'information
+ debug: msg="Pour superviser le Windows, il faut installer NSClient++"
diff --git a/roles/icinga-ed/files/cfg/contacts_icinga.cfg b/roles/icinga-ed/files/cfg/contacts_icinga.cfg
new file mode 100644
index 0000000..a07a853
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email supervisiongsb@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-ed/files/cfg/extinfo_icinga.cfg b/roles/icinga-ed/files/cfg/extinfo_icinga.cfg
new file mode 100644
index 0000000..07bd594
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/extinfo_icinga.cfg
@@ -0,0 +1,13 @@
+##
+## Extended Host and Service Information
+##
+
+define hostextinfo{
+ hostgroup_name debian-servers
+ notes Debian GNU/Linux servers
+# notes_url http://webserver.localhost.localdomain/hostinfo.pl?host=netware1
+ icon_image base/debian.png
+ icon_image_alt Debian GNU/Linux
+ vrml_image debian.png
+ statusmap_image base/debian.gd2
+ }
diff --git a/roles/icinga-ed/files/cfg/generic-host_icinga.cfg b/roles/icinga-ed/files/cfg/generic-host_icinga.cfg
new file mode 100644
index 0000000..e6d96ac
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/generic-host_icinga.cfg
@@ -0,0 +1,19 @@
+# Generic host definition template - This is NOT a real host, just a template!
+
+define host{
+ name generic-host ; The name of this host template
+ notifications_enabled 1 ; Host notifications are enabled
+ event_handler_enabled 1 ; Host event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ check_command check-host-alive
+ max_check_attempts 10
+ notification_interval 0
+ notification_period 24x7
+ notification_options d,u,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-ed/files/cfg/generic-service_icinga.cfg b/roles/icinga-ed/files/cfg/generic-service_icinga.cfg
new file mode 100644
index 0000000..4d60c79
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/generic-service_icinga.cfg
@@ -0,0 +1,26 @@
+# generic service template definition
+define service{
+ name generic-service ; The 'name' of this service template
+ active_checks_enabled 1 ; Active service checks are enabled
+ passive_checks_enabled 1 ; Passive service checks are enabled/accepted
+ parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems)
+ obsess_over_service 1 ; We should obsess over this service (if necessary)
+ check_freshness 0 ; Default is to NOT check service 'freshness'
+ notifications_enabled 1 ; Service notifications are enabled
+ event_handler_enabled 1 ; Service event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ notification_interval 0 ; Only send notifications on status change by default.
+ is_volatile 0
+ check_period 24x7
+ normal_check_interval 5
+ retry_check_interval 1
+ max_check_attempts 4
+ notification_period 24x7
+ notification_options w,u,c,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-ed/files/cfg/gwsio4.cfg b/roles/icinga-ed/files/cfg/gwsio4.cfg
new file mode 100644
index 0000000..bdac8fd
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/gwsio4.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name gwsio4
+ alias Passerelle
+ address 192.168.0.1
+ icon_image cook/linux_server.gif
+ statusmap_image cook/linux_server.gd2
+ }
diff --git a/roles/icinga-ed/files/cfg/hostgroups_icinga.cfg b/roles/icinga-ed/files/cfg/hostgroups_icinga.cfg
new file mode 100644
index 0000000..a2f39d7
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/hostgroups_icinga.cfg
@@ -0,0 +1,74 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-infra, s-proxy, r-int, r-ext, s-adm
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-infra, s-proxy, r-int, r-ext, localhost, gwsio4, s-adm
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-infra, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members r-int, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+#define hostgroup {
+# hostgroup_name email-servers
+# alias serveurs-email
+# members s-mess
+# }
+
+define hostgroup {
+ hostgroup_name proxy-servers
+ alias serveurs-proxy
+ members s-proxy
+}
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members srv-2012
+}
+
+define hostgroup{
+ hostgroup_name switch
+ alias switch
+ members netgear
+}
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members netgear, s-infra, s-proxy, r-int, r-ext, s-adm
+}
+
diff --git a/roles/icinga-ed/files/cfg/localhost.cfg b/roles/icinga-ed/files/cfg/localhost.cfg
new file mode 100644
index 0000000..4e4e190
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/localhost.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host
+ host_name localhost
+ alias Serveur monitoring
+ address localhost
+ }
+
diff --git a/roles/icinga-ed/files/cfg/localhost_icinga.cfg b/roles/icinga-ed/files/cfg/localhost_icinga.cfg
new file mode 100644
index 0000000..3e3fa93
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/localhost_icinga.cfg
@@ -0,0 +1,51 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name localhost
+ alias localhost
+ address 127.0.0.1
+ parents r-int
+ }
+
+# Define a service to check the disk space of the root partition
+# on the local machine. Warning if < 20% free, critical if
+# < 10% free space on partition.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Disk Space
+ check_command check_all_disks!20%!10%
+ }
+
+
+
+# Define a service to check the number of currently logged in
+# users on the local machine. Warning if > 20 users, critical
+# if > 50 users.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Users
+ check_command check_users!20!50
+ }
+
+
+# Define a service to check the number of currently running procs
+# on the local machine. Warning if > 250 processes, critical if
+# > 400 processes.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Total Processes
+ check_command check_procs!250!400
+ }
+
+
diff --git a/roles/icinga-ed/files/cfg/netgear.cfg b/roles/icinga-ed/files/cfg/netgear.cfg
new file mode 100644
index 0000000..55909c8
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/netgear.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name netgear
+ alias switch
+ address 192.168.0.2
+ parents gwsio4
+ icon_image cook/switch.gif
+ statusmap_image cook/switch.gd2
+}
+
diff --git a/roles/icinga-ed/files/cfg/r-ext.cfg b/roles/icinga-ed/files/cfg/r-ext.cfg
new file mode 100644
index 0000000..2d47698
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/r-ext.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-ext
+ alias Routeur externe
+ address 192.168.200.253
+ parents netgear
+ }
diff --git a/roles/icinga-ed/files/cfg/r-int.cfg b/roles/icinga-ed/files/cfg/r-int.cfg
new file mode 100644
index 0000000..77ebe3d
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/r-int.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-int
+ alias Routeur interne
+ address 172.16.0.254
+ parents r-ext
+ }
diff --git a/roles/icinga-ed/files/cfg/s-adm.cfg b/roles/icinga-ed/files/cfg/s-adm.cfg
new file mode 100644
index 0000000..aeadbee
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/s-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-adm
+ alias debian-servers
+ address 192.168.99.99
+ parents r-int
+ }
+
diff --git a/roles/icinga-ed/files/cfg/s-infra.cfg b/roles/icinga-ed/files/cfg/s-infra.cfg
new file mode 100644
index 0000000..c369ff6
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/s-infra.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra
+ alias debian-servers
+ address 172.16.0.1
+ parents r-int
+ }
+
diff --git a/roles/icinga-ed/files/cfg/s-proxy.cfg b/roles/icinga-ed/files/cfg/s-proxy.cfg
new file mode 100644
index 0000000..de4f3c9
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/s-proxy.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-proxy
+ alias serveur proxy
+ address 172.16.0.2
+ parents r-int
+ }
diff --git a/roles/icinga-ed/files/cfg/services_icinga.cfg b/roles/icinga-ed/files/cfg/services_icinga.cfg
new file mode 100644
index 0000000..5627ed9
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/services_icinga.cfg
@@ -0,0 +1,120 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!80!90!
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Traffic
+ check_command check_iftraffic3!public
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version Client
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name switch
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-ed/files/cfg/srv-2012.cfg b/roles/icinga-ed/files/cfg/srv-2012.cfg
new file mode 100644
index 0000000..8ff28a9
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/srv-2012.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name srv-2012
+ alias windows-servers
+ address 172.16.0.6
+ parents r-int
+ icon_image base/win40.gif
+ statusmap_image base/win40.gd2
+ }
+
diff --git a/roles/icinga-ed/files/cfg/timeperiods_icinga.cfg b/roles/icinga-ed/files/cfg/timeperiods_icinga.cfg
new file mode 100644
index 0000000..55ecf9d
--- /dev/null
+++ b/roles/icinga-ed/files/cfg/timeperiods_icinga.cfg
@@ -0,0 +1,50 @@
+###############################################################################
+# timeperiods.cfg
+###############################################################################
+
+# This defines a timeperiod where all times are valid for checks,
+# notifications, etc. The classic "24x7" support nightmare. :-)
+
+define timeperiod{
+ timeperiod_name 24x7
+ alias 24 Hours A Day, 7 Days A Week
+ sunday 00:00-24:00
+ monday 00:00-24:00
+ tuesday 00:00-24:00
+ wednesday 00:00-24:00
+ thursday 00:00-24:00
+ friday 00:00-24:00
+ saturday 00:00-24:00
+ }
+
+# Here is a slightly friendlier period during work hours
+define timeperiod{
+ timeperiod_name workhours
+ alias Standard Work Hours
+ monday 09:00-17:00
+ tuesday 09:00-17:00
+ wednesday 09:00-17:00
+ thursday 09:00-17:00
+ friday 09:00-17:00
+ }
+
+# The complement of workhours
+define timeperiod{
+ timeperiod_name nonworkhours
+ alias Non-Work Hours
+ sunday 00:00-24:00
+ monday 00:00-09:00,17:00-24:00
+ tuesday 00:00-09:00,17:00-24:00
+ wednesday 00:00-09:00,17:00-24:00
+ thursday 00:00-09:00,17:00-24:00
+ friday 00:00-09:00,17:00-24:00
+ saturday 00:00-24:00
+ }
+
+# This one is a favorite: never :)
+define timeperiod{
+ timeperiod_name never
+ alias Never
+ }
+
+# end of file
diff --git a/roles/icinga-ed/files/check_iftraffic3.pl b/roles/icinga-ed/files/check_iftraffic3.pl
new file mode 100755
index 0000000..62ddbd1
--- /dev/null
+++ b/roles/icinga-ed/files/check_iftraffic3.pl
@@ -0,0 +1,643 @@
+#!/usr/bin/perl -w
+#
+# check_iftraffic.pl - Nagios(r) network traffic monitor plugin
+# Copyright (C) 2004 Gerd Mueller / Netways GmbH
+# $Id: check_iftraffic.pl 1119 2006-02-09 10:30:09Z gmueller $
+#
+# mw = Markus Werner mw+nagios@wobcom.de
+# Remarks (mw):
+#
+# I adopted as much as possible the programming style of the origin code.
+#
+# There should be a function to exit this programm,
+# instead of calling print and exit statements all over the place.
+#
+#
+# minor changes by mw
+# The snmp if_counters on net devices can have overflows.
+# I wrote this code to address this situation.
+# It has no automatic detection and which point the overflow
+# occurs but it will generate a warning state and you
+# can set the max value by calling this script with an additional
+# arg.
+#
+# minor cosmetic changes by mw
+# Sorry but I couldn't sustain to clean up some things.
+#
+# gj = Greg Frater gregATfraterfactory.com
+# Remarks (gj):
+# minor (gj):
+#
+# * fixed the performance data, formating was not to spec
+# * Added a check of the interfaces status (up/down).
+# If down the check returns a critical status.
+# * Allow either textual or the numeric index value.
+# * If the interface speed is not specified on the command line
+# it gets it automatically from IfSpeed
+# * Added option for second ifSpeed to allow for asymetrcal links
+# such as a DSL line or cable modem where the download and upload
+# speeds are different
+# * Added -B option to display results in bits/sec instead of Bytes/sec
+# * Added the current usage in Bytes/s (or bit/s) to the perfdata output
+# * Added ability for plugin to determine interface to query by matching IP
+# address of host with entry in ipAdEntIfIndex (.1.3.6.1.2.1.4.20.1.2)
+# * Added -L flag to list entries found in the ipAdEntIfIndex table
+# Otherwise, it works as before.
+#
+#
+#
+#
+# based on check_traffic from Adrian Wieczorek, <ads (at) irc.pila.pl>
+#
+# Send us bug reports, questions and comments about this plugin.
+# Latest version of this software: http://www.nagiosexchange.org
+#
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307
+
+use strict;
+
+use Net::SNMP;
+use Getopt::Long;
+&Getopt::Long::config('bundling');
+
+use Data::Dumper;
+
+my $host_ip;
+my $host_address;
+my $iface_number;
+my $iface_descr;
+my $iface_speed;
+my $iface_speedOut;
+my $index_list;
+my $opt_h;
+my $units;
+
+my $session;
+my $error;
+my $port = 161;
+my $snmp_version = 1;
+
+my @snmpoids;
+
+# SNMP OIDs for Traffic
+my $snmpIfOperStatus = '1.3.6.1.2.1.2.2.1.8';
+my $snmpIfInOctets = '1.3.6.1.2.1.2.2.1.10';
+my $snmpIfOutOctets = '1.3.6.1.2.1.2.2.1.16';
+my $snmpIfDescr = '1.3.6.1.2.1.2.2.1.2';
+my $snmpIfSpeed = '1.3.6.1.2.1.2.2.1.5';
+my $snmpIPAdEntIfIndex = '1.3.6.1.2.1.4.20.1.2';
+
+my $response;
+
+# Path to tmp files
+my $TRAFFIC_FILE = "/tmp/traffic";
+
+# changes sos 20090717 UNKNOWN must bes 3
+my %STATUS_CODE =
+ ( 'UNKNOWN' => '3', 'OK' => '0', 'WARNING' => '1', 'CRITICAL' => '2' );
+
+#default values;
+my $state = "UNKNOWN";
+my $if_status = '4';
+my ( $in_bytes, $out_bytes ) = 0;
+my $warn_usage = 85;
+my $crit_usage = 98;
+my $COMMUNITY = "public";
+my $use_reg = undef; # Use Regexp for name
+my $output = "";
+my $bits = undef;
+my $suffix = "Bs";
+my $label = "MBytes";
+
+#added 20050614 by mw
+my $max_value;
+my $max_bytes;
+
+#cosmetic changes 20050614 by mw, see old versions for detail
+# Added options for bits and second max ifspeed 20100202 by gj
+# Added options for specificy IP addr to match 20100405 by gj
+my $status = GetOptions(
+ "h|help" => \$opt_h,
+ 'B' => \$bits,
+ 'bits' => \$bits,
+ "C|community=s" => \$COMMUNITY,
+ "w|warning=s" => \$warn_usage,
+ "c|critical=s" => \$crit_usage,
+ "b|bandwidth|I|inBandwidth=i" => \$iface_speed,
+ "O|outBandwidth=i" => \$iface_speedOut,
+ 'r' => \$use_reg,
+ 'noregexp' => \$use_reg,
+ "p|port=i" => \$port,
+ "u|units=s" => \$units,
+ "i|interface=s" => \$iface_number,
+ "A|address=s" => \$host_ip,
+ "H|hostname=s" => \$host_address,
+ 'L' => \$index_list,
+ 'list' => \$index_list,
+
+ #added 20050614 by mw
+ "M|max=i" => \$max_value
+);
+
+if ( $status == 0 ) {
+ print_help();
+ exit $STATUS_CODE{'OK'};
+}
+
+# Changed 20091214 gj
+# Check for missing options
+#if ( ( !$host_address ) or ( !$iface_descr ) ) {
+if ( !$host_address ) {
+ print "\nMissing host address!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speed ) and ( !$units ) ){
+ print "\nMissing units!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $units ) and ( ( !$iface_speed ) and ( !$iface_speedOut ) ) ) {
+ print "\nMissing interface maximum speed!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speedOut ) and ( !$units ) ) {
+ print "\nMissing units for Out maximum speed!\n\n";
+ stop(print_usage(),"OK");
+}
+
+
+if ($bits) {
+ $suffix = "bs"
+}
+
+if ( !$iface_speed ) {
+ # Do nothing
+}else{
+
+ #change 20050414 by mw
+ # Added iface_speedOut 20100202 by gj
+ # Convert interface speed to kiloBytes
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+ if ( $iface_speedOut ) {
+ $iface_speedOut = bits2bytes( $iface_speedOut, $units ) / 1024;
+ }
+ if ( !$max_value ) {
+
+ # If no -M Parameter was set, set it to 32Bit Overflow
+ $max_bytes = 4194304 ; # the value is (2^32/1024)
+ }
+ else {
+ $max_bytes = unit2bytes( $max_value, $units );
+ }
+}
+
+if ( $snmp_version =~ /[12]/ ) {
+ ( $session, $error ) = Net::SNMP->session(
+ -hostname => $host_address,
+ -community => $COMMUNITY,
+ -port => $port,
+ -version => $snmp_version
+ );
+
+ if ( !defined($session) ) {
+ stop("UNKNOWN: $error","UNKNOWN");
+ }
+}
+elsif ( $snmp_version =~ /3/ ) {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v3 yet\n",$state);
+}
+else {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v$snmp_version yet\n",$state);
+}
+
+# Neither Interface Index nor Host IP address were specified
+if ( !$iface_descr ) {
+ if ( !$host_ip ){
+ # try to resolve host name and find index from ip addr
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_address );
+ } else {
+ # Use ip addr to find index
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_ip );
+ }
+}
+
+#push( @snmpoids, $snmpIPAdEntIfIndex . "." . $host_address );
+
+# Added 20091209 gj
+# Detect if a string description was given or a numberic interface index number
+if ( $iface_descr =~ /[^0123456789]+/ ) {
+ $iface_number = fetch_ifdescr( $session, $iface_descr );
+}else{
+ $iface_number = $iface_descr;
+}
+
+push( @snmpoids, $snmpIfSpeed . "." . $iface_number );
+push( @snmpoids, $snmpIfOperStatus . "." . $iface_number );
+push( @snmpoids, $snmpIfInOctets . "." . $iface_number );
+push( @snmpoids, $snmpIfOutOctets . "." . $iface_number );
+
+if ( !defined( $response = $session->get_request(@snmpoids) ) ) {
+ my $answer = $session->error;
+ $session->close;
+
+ stop("WARNING: SNMP error: $answer\n", "WARNING");
+}
+
+# Added 20091209 gj
+# Get interface speed from device if not provided on command line
+# Convert to kiloBytes
+if ( !$iface_speed ) {
+ $iface_speed = $response->{ $snmpIfSpeed . "." . $iface_number };
+ $units = "b";
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+}
+
+# Added 20100201 gj
+# Check if Out max speed was provided, use same if speed for both if not
+if (!$iface_speedOut) {
+ $iface_speedOut = $iface_speed;
+}
+
+$if_status = $response->{ $snmpIfOperStatus . "." . $iface_number };
+$in_bytes = $response->{ $snmpIfInOctets . "." . $iface_number } / 1024; # in kiloBytes
+$out_bytes = $response->{ $snmpIfOutOctets . "." . $iface_number } / 1024; # in kiloBytes
+
+$session->close;
+
+my $row;
+my $last_check_time = time - 1;
+my $last_in_bytes = $in_bytes;
+my $last_out_bytes = $out_bytes;
+
+if (
+ open( FILE,
+ "<" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address
+ )
+ )
+{
+ while ( $row = <FILE> ) {
+
+ #cosmetic change 20050416 by mw
+ #Couldn't sustain;-)
+## chomp();
+ ( $last_check_time, $last_in_bytes, $last_out_bytes ) =
+ split( ":", $row );
+
+ ### by sos 17.07.2009 check for last_bytes
+ if ( ! $last_in_bytes ) { $last_in_bytes=$in_bytes; }
+ if ( ! $last_out_bytes ) { $last_out_bytes=$out_bytes; }
+
+ if ($last_in_bytes !~ m/\d/) { $last_in_bytes=$in_bytes; }
+ if ($last_out_bytes !~ m/\d/) { $last_out_bytes=$out_bytes; }
+ }
+ close(FILE);
+}
+
+my $update_time = time;
+
+open( FILE, ">" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address )
+ or die "Can't open $TRAFFIC_FILE for writing: $!";
+
+printf FILE ( "%s:%.0ld:%.0ld\n", $update_time, $in_bytes, $out_bytes );
+close(FILE);
+
+my $db_file;
+
+#added 20050614 by mw
+#Check for and correct counter overflow (if possible).
+#See function counter_overflow.
+$in_bytes = counter_overflow( $in_bytes, $last_in_bytes, $max_bytes );
+$out_bytes = counter_overflow( $out_bytes, $last_out_bytes, $max_bytes );
+
+# Calculate traffic since last check (RX\TX) in kiloBytes
+my $in_traffic = sprintf( "%.2lf",
+ ( $in_bytes - $last_in_bytes ) / ( time - $last_check_time ) );
+my $out_traffic = sprintf( "%.2lf",
+ ( $out_bytes - $last_out_bytes ) / ( time - $last_check_time ) );
+
+# sos 20090717 changed due to rrdtool needs bytes
+my $in_traffic_absolut = $in_bytes * 1024 ;
+my $out_traffic_absolut = $out_bytes * 1024;
+
+# Calculate usage percentages
+my $in_usage = sprintf( "%.2f", ( 1.0 * $in_traffic * 100 ) / $iface_speed );
+my $out_usage = sprintf( "%.2f", ( 1.0 * $out_traffic * 100 ) / $iface_speedOut );
+
+
+if ($bits) {
+ # Convert output from Bytes to bits
+ $in_bytes = $in_bytes * 8;
+ $out_bytes = $out_bytes * 8;
+ $in_traffic = $in_traffic * 8;
+ $out_traffic = $out_traffic * 8;
+ $label = "Mbits";
+}
+
+my $in_prefix = "K";
+my $out_prefix = "K";
+
+if ( $in_traffic > 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 );
+ $in_prefix = "M";
+}
+if ( $out_traffic > 1024 ) {
+ $out_traffic = sprintf( "%.2f", $out_traffic / 1024 );
+ $out_prefix = "M";
+}
+if ( $in_traffic > 1024 * 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 * 1024 );
+ $in_prefix = "G";
+}
+if ( $out_traffic > 1024 * 1024 ) {
+ $out_traffic = sprintf( "%.2f",$out_traffic / 1024 * 1024 );
+ $out_prefix = "G";
+}
+
+# Convert from kiloBytes to megaBytes
+$in_bytes = sprintf( "%.2f", $in_bytes / 1024 );
+$out_bytes = sprintf( "%.2f", $out_bytes / 1024 );
+
+$state = "OK";
+
+# Added 20091209 by gj
+if ( $if_status != 1 ) {
+ $output = "Interface $iface_descr is down!";
+
+}else{
+ $output =
+ "Average IN: "
+ . $in_traffic . $in_prefix . $suffix . " (" . $in_usage . "%), "
+ . "Average OUT: " . $out_traffic . $out_prefix . $suffix . " (" . $out_usage . "%)<br>";
+ $output .= "Total RX: $in_bytes $label, Total TX: $out_bytes $label";
+}
+
+# Changed 20091209 gj
+if ( ( $in_usage > $crit_usage ) or ( $out_usage > $crit_usage ) or ( $if_status != 1 ) ) {
+ $state = "CRITICAL";
+}
+
+if ( ( $in_usage > $warn_usage )
+ or ( $out_usage > $warn_usage ) && $state eq "OK" )
+{
+ $state = "WARNING";
+}
+
+# Changed 20091209 gj
+$output = "$state - $output"
+ if ( $state ne "OK" );
+
+# Changed 20091214 gj - commas should have been semi colons
+$output .=
+"|inUsage=$in_usage%;$warn_usage;$crit_usage outUsage=$out_usage%;$warn_usage;$crit_usage"
+ . " inBandwidth=" . $in_traffic . $in_prefix . $suffix . " outBandwidth=" . $out_traffic . $out_prefix . $suffix
+ . " inAbsolut=$in_traffic_absolut outAbsolut=$out_traffic_absolut";
+
+stop($output, $state);
+
+
+sub fetch_Ip2IfIndex {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $host ) = @_;
+
+
+ # Determine if we have a host name or IP addr
+ if ( $host =~ /\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/ ){
+ #print "\nI found an IP address\n\n";
+ } else {
+ $host = get_ip ( $host );
+ #print "\nWe have a host name $host\n\n";
+ }
+
+ # Quit if results not found
+ if ( !defined( $response = $session->get_table($snmpIPAdEntIfIndex) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+
+ my %resp = %{$response};
+# foreach $key ( keys %{$response} ) {
+
+ if ( $index_list ){
+ print ("\nInterfaces found:\n");
+ print (" IP Addr\tIndex\n");
+ print ("------------------------\n");
+ }
+ # Check each returned value
+ foreach $key ( keys %resp ) {
+
+ if ( $index_list ){
+ my $index_addr = substr $key, 21;
+ print ($index_addr,"\t ",$resp{$key},"\n");
+ }
+
+ # Check for ip address mathcin in returned index results
+ if ( $key =~ /$host$/ ) {
+ $snmpkey = $resp{$key};
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $host \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+sub fetch_ifdescr {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $ifdescr ) = @_;
+
+ if ( !defined( $response = $session->get_table($snmpIfDescr) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+ foreach $key ( keys %{$response} ) {
+
+ # added 20070816 by oer: remove trailing 0 Byte for Windows :-(
+ my $resp=$response->{$key};
+ $resp =~ s/\x00//;
+
+
+ my $test = defined($use_reg)
+ ? $resp =~ /$ifdescr/
+ : $resp eq $ifdescr;
+
+ if ($test) {
+
+ ###if ( $resp =~ /^$ifdescr$/ ) {
+ ###if ( $resp =~ /$ifdescr/ ) {
+ ### print "$resp \n";
+ ###if ( $response->{$key} =~ /^$ifdescr$/ ) {
+
+ $key =~ /.*\.(\d+)$/;
+ $snmpkey = $1;
+
+ # print "$ifdescr = $key / $snmpkey \n"; #debug
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $ifdescr \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bits
+sub bits2bytes {
+ return unit2bytes(@_) / 8;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bytes
+sub unit2bytes {
+ my ( $value, $unit ) = @_;
+
+ if ( $unit eq "g" ) {
+ return $value * 1024 * 1024 * 1024;
+ }
+ elsif ( $unit eq "m" ) {
+ return $value * 1024 * 1024;
+ }
+ elsif ( $unit eq "k" ) {
+ return $value * 1024;
+ }
+ elsif ( $unit eq "b" ) {
+ return $value * 1;
+ }
+ else {
+ print "You have to supply a supported unit\n";
+ exit $STATUS_CODE{'UNKNOWN'};
+ }
+}
+
+#added 20050414 by mw
+#This function detects if an overflow occurs. If so, it returns
+#a computed value for $bytes.
+#If there is no counter overflow it simply returns the origin value of $bytes.
+#IF there is a Counter reboot wrap, just use previous output.
+sub counter_overflow {
+ my ( $bytes, $last_bytes, $max_bytes ) = @_;
+
+ $bytes += $max_bytes if ( $bytes < $last_bytes );
+ $bytes = $last_bytes if ( $bytes < $last_bytes );
+ return $bytes;
+}
+
+# Added 20100202 by gj
+# Print results and exit script
+sub stop {
+ my $result = shift;
+ my $exit_code = shift;
+ print $result . "\n";
+ exit ( $STATUS_CODE{$exit_code} );
+}
+
+# Added 20100405 by gj
+# Lookup hosts ip address
+sub get_ip {
+ use Net::DNS;
+
+ my ( $host_name ) = @_;
+
+ my $res = Net::DNS::Resolver->new;
+ my $query = $res->search($host_name);
+
+ if ($query) {
+ foreach my $rr ($query->answer) {
+ next unless $rr->type eq "A";
+ #print $rr->address, "\n";
+ return $rr->address;
+ }
+ } else {
+
+ stop("Error: IP address not resolved\n","UNKNOWN");
+ }
+}
+
+#cosmetic changes 20050614 by mw
+#Couldn't sustain "HERE";-), either.
+sub print_usage {
+ print <<EOU;
+ Usage: check_iftraffic3.pl -H host [ -C community_string ] [ -i if_index|if_descr ] [ -r ] [ -b if_max_speed_in | -I if_max_speed_in ] [ -O if_max_speed_out ] [ -u ] [ -B ] [ -A IP Address ] [ -L ] [ -M ] [ -w warn ] [ -c crit ]
+
+ Example 1: check_iftraffic3.pl -H host1 -C sneaky
+ Example 2: check_iftraffic3.pl -H host1 -C sneaky -i "Intel Pro" -r -B
+ Example 3: check_iftraffic3.pl -H host1 -C sneaky -i 5
+ Example 4: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 100 -u m
+ Example 5: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 20 -O 5 -u m
+ Example 6: check_iftraffic3.pl -H host1 -C sneaky -A 192.168.1.1 -B -b 100 -u m
+
+ Options:
+
+ -H, --host STRING or IPADDRESS
+ Check interface on the indicated host.
+ -B, --bits
+ Display results in bits per second b/s (default: Bytes/s)
+ -C, --community STRING
+ SNMP Community.
+ -r, --regexp
+ Use regexp to match NAME in description OID
+ -i, --interface STRING
+ Interface Name
+ -b, --bandwidth INTEGER
+ -I, --inBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ both IN and OUT if no second (-O) max speed is provided.
+ -O, --outBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ OUT traffic. Uses the same units value given for -b.
+ -u, --units STRING
+ g=gigabits/s,m=megabits/s,k=kilobits/s,b=bits/s. Required if -b, -I, or
+ -O are used.
+ -w, --warning INTEGER
+ % of bandwidth usage necessary to result in warning status (default: 85%)
+ -c, --critical INTEGER
+ % of bandwidth usage necessary to result in critical status (default: 98%)
+ -M, --max INTEGER
+ Max Counter Value of net devices in kilo/mega/giga/bytes.
+ -A, --address STRING (IP Address)
+ IP Address to use when determining the interface index to use. Can be
+ used when the index changes frequently or as in the case of Windows
+ servers the index is different depending on the NIC installed.
+ -L, --list FLAG (on/off)
+ Tell plugin to list available interfaces. This is not supported inside
+ of Nagios, but may be useful from the command line.
+EOU
+
+}
+
diff --git a/roles/icinga-ed/files/commands.cfg b/roles/icinga-ed/files/commands.cfg
new file mode 100644
index 0000000..1ceea2c
--- /dev/null
+++ b/roles/icinga-ed/files/commands.cfg
@@ -0,0 +1,90 @@
+###############################################################################
+# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
+###############################################################################
+
+
+################################################################################
+# NOTIFICATION COMMANDS
+################################################################################
+
+
+# 'notify-host-by-email' command definition
+define command{
+ command_name notify-host-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$
+ }
+
+# 'notify-service-by-email' command definition
+define command{
+ command_name notify-service-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$
+ }
+
+
+
+
+
+################################################################################
+# HOST CHECK COMMANDS
+################################################################################
+
+# On Debian, check-host-alive is being defined from within the
+# nagios-plugins-basic package
+define command{
+ command_name check_snmp_storage
+ command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -m $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_load
+ command_line $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -T $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_mem
+ command_line $USER1$/check_snmp_mem.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_int
+ command_line $USER1$/check_snmp_netint.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -a -m -k -M -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_iftraffic3
+ #command_name check_win_int
+ #command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$
+ #command_line $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -k -M -g -w $ARG4$ -c $ARG5$
+ command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$ -i $ARG2$ -w $ARG3$ -c $ARG4$
+}
+
+define command{
+ command_name check_snmp
+ command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
+}
+###############################
+##WINDOWS
+###############################
+
+define command{
+ command_name check_nt
+ command_line $USER1$/check_nt -H $HOSTADDRESS$ -s root -p 12489 -v $ARG1$ $ARG2$
+}
+
+################################################################################
+# PERFORMANCE DATA COMMANDS
+################################################################################
+
+
+# 'process-host-perfdata' command definition
+define command{
+ command_name process-host-perfdata
+ command_line /usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /var/lib/nagios3/host-perfdata.out
+ }
+
+
+# 'process-service-perfdata' command definition
+define command{
+ command_name process-service-perfdata
+ command_line /usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /var/lib/nagios3/service-perfdata.out
+ }
diff --git a/roles/icinga-ed/files/contacts_icinga.cfg b/roles/icinga-ed/files/contacts_icinga.cfg
new file mode 100644
index 0000000..a07a853
--- /dev/null
+++ b/roles/icinga-ed/files/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email supervisiongsb@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-ed/files/dns.cfg b/roles/icinga-ed/files/dns.cfg
new file mode 100644
index 0000000..5b69aca
--- /dev/null
+++ b/roles/icinga-ed/files/dns.cfg
@@ -0,0 +1,11 @@
+# 'check_dns' command definition
+define command{
+ command_name check_dns
+ command_line /usr/lib/nagios/plugins/check_dns -H www.dfco.fr -s '$HOSTADDRESS$'
+}
+
+# 'check_dig' command definition
+define command{
+ command_name check_dig
+ command_line /usr/lib/nagios/plugins/check_dig -H '$HOSTADDRESS$' -l '$ARG1$'
+}
diff --git a/roles/icinga-ed/files/hostgroups_icinga.cfg b/roles/icinga-ed/files/hostgroups_icinga.cfg
new file mode 100644
index 0000000..a2f39d7
--- /dev/null
+++ b/roles/icinga-ed/files/hostgroups_icinga.cfg
@@ -0,0 +1,74 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-infra, s-proxy, r-int, r-ext, s-adm
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-infra, s-proxy, r-int, r-ext, localhost, gwsio4, s-adm
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-infra, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members r-int, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+#define hostgroup {
+# hostgroup_name email-servers
+# alias serveurs-email
+# members s-mess
+# }
+
+define hostgroup {
+ hostgroup_name proxy-servers
+ alias serveurs-proxy
+ members s-proxy
+}
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members srv-2012
+}
+
+define hostgroup{
+ hostgroup_name switch
+ alias switch
+ members netgear
+}
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members netgear, s-infra, s-proxy, r-int, r-ext, s-adm
+}
+
diff --git a/roles/icinga-ed/files/icinga.cfg b/roles/icinga-ed/files/icinga.cfg
new file mode 100644
index 0000000..fde1780
--- /dev/null
+++ b/roles/icinga-ed/files/icinga.cfg
@@ -0,0 +1,1494 @@
+##############################################################################
+#
+# ICINGA.CFG - Sample Main Config File for Icinga
+#
+# Read the documentation for more information on this configuration
+# file. I've provided some comments here, but things may not be so
+# clear without further explanation.
+#
+##############################################################################
+
+
+# LOG FILE
+# This is the main log file where service and host events are logged
+# for historical purposes. This should be the first option specified
+# in the config file!!!
+
+log_file=/var/log/icinga/icinga.log
+
+# Commands definitions
+cfg_file=/etc/icinga/commands.cfg
+
+# Debian also defaults to using the check commands defined by the debian
+# nagios-plugins package
+cfg_dir=/etc/nagios-plugins/config
+
+# OBJECT CONFIGURATION FILE(S)
+# These are the object configuration files in which you define hosts,
+# host groups, contacts, contact groups, services, etc.
+# Hint: Check the docs/wiki on how to monitor remote hosts with different
+# transport methods and plugins
+
+# Debian uses by default a configuration directory where icinga-common,
+# other packages and the local admin can dump or link configuration
+# files into.
+cfg_dir=/etc/icinga/objects/
+
+# Definitions for ido2db process checks
+#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg
+
+# Definitions for broker modules like idoutils.cfg
+cfg_dir=/etc/icinga/modules
+
+
+
+# OBJECT CACHE FILE
+# This option determines where object definitions are cached when
+# Icinga starts/restarts. The CGIs read object definitions from
+# this cache file (rather than looking at the object config files
+# directly) in order to prevent inconsistencies that can occur
+# when the config files are modified after Icinga starts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the objects cache file entirely.
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+# Tip: Use that file to debug your configuration with fully resolved
+# objects like the core sees them.
+
+object_cache_file=/var/cache/icinga/objects.cache
+
+
+
+# PRE-CACHED OBJECT FILE
+# This options determines the location of the precached object file.
+# If you run Icinga with the -p command line option, it will preprocess
+# your object configuration file(s) and write the cached config to this
+# file. You can then start Icinga with the -u option to have it read
+# object definitions from this precached file, rather than the standard
+# object configuration files (see the cfg_file and cfg_dir options above).
+# Using a precached object file can speed up the time needed to (re)start
+# the Icinga process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Icinga to find our more
+# about how this feature works.
+
+precached_object_file=/var/cache/icinga/objects.precache
+
+
+
+# RESOURCE FILE
+# This is an optional resource file that contains $USERx$ macro
+# definitions. Multiple resource files can be specified by using
+# multiple resource_file definitions. The CGIs will not attempt to
+# read the contents of resource files, so information that is
+# considered to be sensitive (usernames, passwords, etc) can be
+# defined as macros in this file and restrictive permissions (600)
+# can be placed on this file.
+
+resource_file=/etc/icinga/resource.cfg
+
+
+
+# STATUS FILE
+# This is where the current status of all monitored services and
+# hosts is stored. Its contents are read and processed by the CGIs.
+# The contents of the status file are deleted every time Icinga
+# restarts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the status file entirely. This becomes handy when using other methods
+# for data retrieval (e.g. IDOUtils DB)
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+
+status_file=/var/lib/icinga/status.dat
+
+
+
+# STATUS FILE UPDATE INTERVAL
+# This option determines the frequency (in seconds) that
+# Icinga will periodically dump program, host, and
+# service status data.
+# Increase the value, if you don't require it that often.
+
+#status_update_interval=30
+status_update_interval=10
+
+
+
+# ICINGA USER
+# This determines the effective user that Icinga should run as.
+# You can either supply a username or a UID.
+
+icinga_user=nagios
+
+
+
+# ICINGA GROUP
+# This determines the effective group that Icinga should run as.
+# You can either supply a group name or a GID.
+
+icinga_group=nagios
+
+
+
+# EXTERNAL COMMAND OPTION
+# This option allows you to specify whether or not Icinga should check
+# for external commands (in the command file defined below). By default
+# Icinga will *not* check for external commands, just to be on the
+# cautious side. If you want to be able to use the CGI command interface
+# you will have to enable this.
+# Values: 0 = disable commands, 1 = enable commands
+
+check_external_commands=1
+
+
+
+# EXTERNAL COMMAND CHECK INTERVAL
+# This is the interval at which Icinga should check for external commands.
+# This value works of the interval_length you specify later. If you leave
+# that at its default value of 60 (seconds), a value of 1 here will cause
+# Icinga to check for external commands every minute. If you specify a
+# number followed by an "s" (i.e. 15s), this will be interpreted to mean
+# actual seconds rather than a multiple of the interval_length variable.
+# Note: In addition to reading the external command file at regularly
+# scheduled intervals, Icinga will also check for external commands after
+# event handlers are executed.
+# NOTE: Setting this value to -1 causes Icinga to check the external
+# command file as often as possible.
+
+#command_check_interval=15s
+command_check_interval=-1
+
+
+
+# EXTERNAL COMMAND FILE
+# This is the file that Icinga checks for external command requests.
+# It is also where the command CGI will write commands that are submitted
+# by users, so it must be writeable by the user that the web server
+# is running as (usually 'nobody'). Permissions should be set at the
+# directory level instead of on the file, as the file is deleted every
+# time its contents are processed.
+# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
+# time to do it.
+
+command_file=/var/lib/icinga/rw/icinga.cmd
+
+
+
+# EXTERNAL COMMAND BUFFER SLOTS
+# This settings is used to tweak the number of items or "slots" that
+# the Icinga daemon should allocate to the buffer that holds incoming
+# external commands before they are processed. As external commands
+# are processed by the daemon, they are removed from the buffer.
+# Increase the value, if you are using addons like check_mk supplying
+# more external commands (passive check results) than usual.
+
+#external_command_buffer_slots=32768
+external_command_buffer_slots=4096
+
+
+
+# LOCK FILE
+# This is the lockfile that Icinga will use to store its PID number
+# in when it is running in daemon mode.
+
+lock_file=/var/run/icinga/icinga.pid
+
+
+
+# TEMP FILE
+# This is a temporary file that is used as scratch space when Icinga
+# updates the status log, cleans the comment file, etc. This file
+# is created, used, and deleted throughout the time that Icinga is
+# running.
+
+temp_file=/var/cache/icinga/icinga.tmp
+
+
+
+# TEMP PATH
+# This is path where Icinga can create temp files for service and
+# host check results, etc.
+
+temp_path=/tmp
+
+
+
+# EVENT BROKER OPTIONS
+# Controls what (if any) data gets sent to the event broker.
+# Values: 0 = Broker nothing
+# -1 = Broker everything
+# <other> = See documentation
+
+event_broker_options=-1
+
+
+
+# EVENT BROKER MODULE(S)
+# ----> use the new *module definition* instead:
+# ----> http://docs.icinga.org/latest/en/objectdefinitions.html
+#
+# Example definitions can be found in the '/etc/icinga/modules/' directory.
+# If you want to enable idoutils in Debian install icinga-idoutils and copy
+# /usr/share/doc/icinga-idoutils/examples/idoutils.cfg-sample to
+# /etc/icinga/modules/idoutils.cfg.
+# Don't forget to also enable the daemon in /etc/default/icinga
+
+# LOG ROTATION METHOD
+# This is the log rotation method that Icinga should use to rotate
+# the main log file. Values are as follows..
+# n = None - don't rotate the log
+# h = Hourly rotation (top of the hour)
+# d = Daily rotation (midnight every day)
+# w = Weekly rotation (midnight on Saturday evening)
+# m = Monthly rotation (midnight last day of month)
+
+log_rotation_method=d
+
+
+
+# LOG ARCHIVE PATH
+# This is the directory where archived (rotated) log files should be
+# placed (assuming you've chosen to do log rotation).
+
+log_archive_path=/var/log/icinga/archives
+
+
+
+# LOGGING OPTIONS FOR DAEMON
+# If you want messages logged to the daemon log file (usually icinga.log).
+# Default option is 1 (yes), the other valid option is 0 (no)
+
+use_daemon_log=1
+
+
+
+# LOGGING OPTIONS FOR SYSLOG
+# If you want messages logged to the syslog facility, as well as the
+# Icinga log file set this option to 1. If not, set it to 0.
+
+use_syslog=1
+
+
+
+# SYSLOG FACILITY
+# If you enabled use_syslog you can set icinga to use a local facility
+# instead of the default.To enable set this option to 1, if not, set it to 0.
+
+use_syslog_local_facility=0
+
+
+
+# SYSLOG LOCAL FACILITY
+# If you specified the use_syslog_local_facility you can chose which
+# local facility to use. Valid values are from 0 to 7
+
+syslog_local_facility=5
+
+
+
+# NOTIFICATION LOGGING OPTION
+# If you don't want notifications to be logged, set this value to 0.
+# If notifications should be logged, set the value to 1.
+
+log_notifications=1
+
+
+
+# SERVICE RETRY LOGGING OPTION
+# If you don't want service check retries to be logged, set this value
+# to 0. If retries should be logged, set the value to 1.
+
+log_service_retries=1
+
+
+
+# HOST RETRY LOGGING OPTION
+# If you don't want host check retries to be logged, set this value to
+# 0. If retries should be logged, set the value to 1.
+
+log_host_retries=1
+
+
+
+# EVENT HANDLER LOGGING OPTION
+# If you don't want host and service event handlers to be logged, set
+# this value to 0. If event handlers should be logged, set the value
+# to 1.
+
+log_event_handlers=1
+
+
+
+# INITIAL STATES LOGGING OPTION
+# If you want Icinga to log all initial host and service states to
+# the main log file (the first time the service or host is checked)
+# you can enable this option by setting this value to 1. If you
+# are not using an external application that does long term state
+# statistics reporting, you do not need to enable this option. In
+# this case, set the value to 0.
+
+log_initial_states=0
+
+
+
+# CURRENT STATES LOGGING OPTION
+# If you don't want Icinga to log all current host and service states
+# after log has been rotated to the main log file, you can disable this
+# option by setting this value to 0. Default value is 1.
+
+log_current_states=1
+
+
+
+# EXTERNAL COMMANDS LOGGING OPTION
+# If you don't want Icinga to log external commands, set this value
+# to 0. If external commands should be logged, set this value to 1.
+# Note: This option does not include logging of passive service
+# checks - see the option below for controlling whether or not
+# passive checks are logged.
+
+log_external_commands=1
+
+
+
+# LOG ANONYMIZED EXTERNAL COMMAND AUTHOR !!EXPERIMENTAL!!
+# This option substitutes the user name on external commands with
+# the string "<anon>" if the command gets logged. It is
+# anonymized in log files only. This option was added to make
+# icinga compliant with data retention laws on various countries.
+# This option is disabled by default.
+
+log_anonymized_external_command_author=0
+
+
+
+# PASSIVE CHECKS LOGGING OPTION
+# If you don't want Icinga to log passive host and service checks, set
+# this value to 0. If passive checks should be logged, set
+# this value to 1.
+
+log_passive_checks=1
+
+
+
+# LONG PLUGIN OUTPUT LOGGING OPTION
+# If you want Icinga to log the complete text of the plugin output
+# to the log instead of only the first line then set this value to 1.
+# Default value is 0.
+
+log_long_plugin_output=0
+
+
+
+# GLOBAL HOST AND SERVICE EVENT HANDLERS
+# These options allow you to specify a host and service event handler
+# command that is to be run for every host or service state change.
+# The global event handler is executed immediately prior to the event
+# handler that you have optionally specified in each host or
+# service definition. The command argument is the short name of a
+# command definition that you define in your host configuration file.
+# Read the HTML docs for more information.
+
+#global_host_event_handler=somecommand
+#global_service_event_handler=somecommand
+
+
+
+# SERVICE INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" service checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all service checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)! This is not a
+# good thing for production, but is useful when testing the
+# parallelization functionality.
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+service_inter_check_delay_method=s
+
+
+
+# MAXIMUM SERVICE CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all services should
+# be completed. Default is 30 minutes.
+
+max_service_check_spread=30
+
+
+
+# SERVICE CHECK INTERLEAVE FACTOR
+# This variable determines how service checks are interleaved.
+# Interleaving the service checks allows for a more even
+# distribution of service checks and reduced load on remote
+# hosts. Setting this value to 1 is equivalent to how versions
+# of Icinga previous to 0.0.5 did service checks. Set this
+# value to s (smart) for automatic calculation of the interleave
+# factor unless you have a specific reason to change it.
+# s = Use "smart" interleave factor calculation
+# x = Use an interleave factor of x, where x is a
+# number greater than or equal to 1.
+
+service_interleave_factor=s
+
+
+
+# HOST INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" host checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all host checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)!
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+host_inter_check_delay_method=s
+
+
+
+# MAXIMUM HOST CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all hosts should
+# be completed. Default is 30 minutes.
+
+max_host_check_spread=30
+
+
+
+# MAXIMUM CONCURRENT SERVICE CHECKS
+# This option allows you to specify the maximum number of
+# service checks that can be run in parallel at any given time.
+# Specifying a value of 1 for this variable essentially prevents
+# any service checks from being parallelized. A value of 0
+# will not restrict the number of concurrent checks that are
+# being executed.
+
+max_concurrent_checks=0
+
+
+
+# HOST AND SERVICE CHECK REAPER FREQUENCY
+# This is the frequency (in seconds!) that Icinga will process
+# the results of host and service checks.
+# Lower this value in larger environments to allow faster
+# check result processing (requires more cpu power).
+
+#check_result_reaper_frequency=1
+check_result_reaper_frequency=10
+
+
+
+
+# MAX CHECK RESULT REAPER TIME
+# This is the max amount of time (in seconds) that a single
+# check result reaper event will be allowed to run before
+# returning control back to Icinga so it can perform other
+# duties.
+
+max_check_result_reaper_time=30
+
+
+
+
+# CHECK RESULT PATH
+# This is directory where Icinga stores the results of host and
+# service checks that have not yet been processed.
+#
+# Note: Make sure that only one instance of Icinga has access
+# to this directory!
+
+check_result_path=/var/lib/icinga/spool/checkresults
+
+
+
+
+# MAX CHECK RESULT FILE AGE
+# This option determines the maximum age (in seconds) which check
+# result files are considered to be valid. Files older than this
+# threshold will be mercilessly deleted without further processing.
+
+max_check_result_file_age=3600
+
+
+
+
+# MAX CHECK RESULT LIST ITEMS !!EXPERIMENTAL!!
+# This experimental option allows you to set the max number of items
+# the checkresult reaper will put onto the checkresult list for further
+# processing by the core. If there are too many, the reaping will be
+# terminated early, allowing the core to process the results sooner.
+# On larger setups, that list might grow too much, and decrease
+# performance on processing. You might experiment with that value, the
+# inner core default is set to 0, disabling that feature.
+# Values:
+# 0 = Disable max check result list items
+# number = set max check result list items
+
+#max_check_result_list_items=1024
+
+
+
+
+# CACHED HOST CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous host check is considered current.
+# Cached host states (from host checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to the host check logic.
+# Too high of a value for this option may result in inaccurate host
+# states being used by Icinga, while a lower value may result in a
+# performance hit for host checks. Use a value of 0 to disable host
+# check caching.
+
+cached_host_check_horizon=15
+
+
+
+# CACHED SERVICE CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous service check is considered current.
+# Cached service states (from service checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to predictive dependency checks.
+# Use a value of 0 to disable service check caching.
+
+cached_service_check_horizon=15
+
+
+
+# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of hosts when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# host dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_host_dependency_checks=1
+
+
+
+# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of service when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# service dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_service_dependency_checks=1
+
+
+
+# SOFT STATE DEPENDENCIES
+# This option determines whether or not Icinga will use soft state
+# information when checking host and service dependencies. Normally
+# Icinga will only use the latest hard host or service state when
+# checking dependencies. If you want it to use the latest state (regardless
+# of whether its a soft or hard state type), enable this option.
+# Values:
+# 0 = Don't use soft state dependencies (default)
+# 1 = Use soft state dependencies
+
+soft_state_dependencies=0
+
+
+
+# TIME CHANGE ADJUSTMENT THRESHOLDS
+# These options determine when Icinga will react to detected changes
+# in system time (forward into the future).
+
+#time_change_threshold=900
+
+
+
+# AUTO-RESCHEDULING OPTION
+# This option determines whether or not Icinga will attempt to
+# automatically reschedule active host and service checks to
+# "smooth" them out over time. This can help balance the load on
+# the monitoring server.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_reschedule_checks=0
+
+
+
+# AUTO-RESCHEDULING INTERVAL
+# This option determines how often (in seconds) Icinga will
+# attempt to automatically reschedule checks. This option only
+# has an effect if the auto_reschedule_checks option is enabled.
+# Default is 30 seconds.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_interval=30
+
+
+
+# AUTO-RESCHEDULING WINDOW
+# This option determines the "window" of time (in seconds) that
+# Icinga will look at when automatically rescheduling checks.
+# Only host and service checks that occur in the next X seconds
+# (determined by this variable) will be rescheduled. This option
+# only has an effect if the auto_reschedule_checks option is
+# enabled. Default is 180 seconds (3 minutes).
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_window=180
+
+
+
+# SLEEP TIME
+# This is the number of seconds to sleep between checking for system
+# events and service checks that need to be run.
+
+sleep_time=0.25
+
+
+
+# TIMEOUT VALUES
+# These options control how much time Icinga will allow various
+# types of commands to execute before killing them off. Options
+# are available for controlling maximum time allotted for
+# service checks, host checks, event handlers, notifications, the
+# ocsp command, and performance data commands. All values are in
+# seconds.
+# Increase the timeout values in case you are experiencing a lot
+# of check timeouts. Addons like e.g. check_mk will perform
+# one combined active servicecheck which could take longer than
+# the default of 60sec.
+
+#service_check_timeout=120
+service_check_timeout=60
+host_check_timeout=30
+event_handler_timeout=30
+notification_timeout=30
+ocsp_timeout=5
+perfdata_timeout=5
+
+
+
+# RETAIN STATE INFORMATION
+# This setting determines whether or not Icinga will save state
+# information for services and hosts before it shuts down. Upon
+# startup Icinga will reload all saved service and host state
+# information before starting to monitor. This is useful for
+# maintaining long-term data on state statistics, etc, but will
+# slow Icinga down a bit when it (re)starts. Since its only
+# a one-time penalty, I think its well worth the additional
+# startup delay.
+
+retain_state_information=1
+
+
+
+# STATE RETENTION FILE
+# This is the file that Icinga should use to store host and
+# service state information before it shuts down. The state
+# information in this file is also read immediately prior to
+# starting to monitor the network when Icinga is restarted.
+# This file is used only if the retain_state_information
+# variable is set to 1.
+
+state_retention_file=/var/cache/icinga/retention.dat
+
+
+
+# SYNC FILE
+# This is an advanced facility to pass a subset of retention
+# information into Icinga on a running system. This is similar
+# to the state retention file with the following difference:
+#
+# - if the last_check value is less than the current last_check,
+# then the state information is ignored (this must be specified
+# immediately after the object identifiers)
+#
+# - downtimes and comments are not identified by an id number, but
+# by other "similar characteristics". This is required to work in
+# a distributed Nagios environment
+# * downtimes: hostname, servicename (if appropriate), author,
+# comment, start_time, end_time, fixed, duration
+# * comments: hostname, servicename, author, comment
+#
+# If this variable is set, then on Icinga startup, the sync file
+# will be read after the retention file has been processed. If the
+# file is read successfully, it will be removed.
+# If the file does not exist, no error will appear.
+# There is also an API that will force a read of the sync file.
+
+#sync_retention_file=/var/cache/icinga/sync.dat
+
+
+
+# RETENTION DATA UPDATE INTERVAL
+# This setting determines how often (in minutes) that Icinga
+# will automatically save retention data during normal operation.
+# If you set this value to 0, Icinga will not save retention
+# data at regular interval, but it will still save retention
+# data before shutting down or restarting. If you have disabled
+# state retention, this option has no effect.
+
+retention_update_interval=60
+
+
+
+# USE RETAINED PROGRAM STATE
+# This setting determines whether or not Icinga will set
+# program status variables based on the values saved in the
+# retention file. If you want to use retained program status
+# information, set this value to 1. If not, set this value
+# to 0.
+
+use_retained_program_state=1
+
+
+# DUMP RETAINED HOST SERVICE STATES TO NEB
+# This setting determines wether or not Icinga will dump host
+# and service states based on the values saved in the retention
+# file to the neb modules. It will already do that on event loop
+# initialization.
+# Changed in Icinga 1.10 to disabled - re-enable if you require it.
+
+dump_retained_host_service_states_to_neb=0
+
+
+
+# USE RETAINED SCHEDULING INFO
+# This setting determines whether or not Icinga will retain
+# the scheduling info (next check time) for hosts and services
+# based on the values saved in the retention file. If you
+# If you want to use retained scheduling info, set this
+# value to 1. If not, set this value to 0.
+
+use_retained_scheduling_info=1
+
+
+
+# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
+# The following variables are used to specify specific host and
+# service attributes that should *not* be retained by Icinga during
+# program restarts.
+#
+# The values of the masks are bitwise ANDs of values specified
+# by the "MODATTR_" definitions found in include/common.h.
+# For example, if you do not want the current enabled/disabled state
+# of flap detection and event handlers for hosts to be retained, you
+# would use a value of 24 for the host attribute mask...
+# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
+
+# This mask determines what host attributes are not retained
+retained_host_attribute_mask=0
+
+# This mask determines what service attributes are not retained
+retained_service_attribute_mask=0
+
+# These two masks determine what process attributes are not retained.
+# There are two masks, because some process attributes have host and service
+# options. For example, you can disable active host checks, but leave active
+# service checks enabled.
+retained_process_host_attribute_mask=0
+retained_process_service_attribute_mask=0
+
+# These two masks determine what contact attributes are not retained.
+# There are two masks, because some contact attributes have host and
+# service options. For example, you can disable host notifications for
+# a contact, but leave service notifications enabled for them.
+retained_contact_host_attribute_mask=0
+retained_contact_service_attribute_mask=0
+
+
+
+# INTERVAL LENGTH
+# This is the seconds per unit interval as used in the
+# host/contact/service configuration files. Setting this to 60 means
+# that each interval is one minute long (60 seconds). Other settings
+# have not been tested much, so your mileage is likely to vary...
+
+interval_length=60
+
+
+
+# AGGRESSIVE HOST CHECKING OPTION
+# If you don't want to turn on aggressive host checking features, set
+# this value to 0 (the default). Otherwise set this value to 1 to
+# enable the aggressive check option. Read the docs for more info
+# on what aggressive host check is or check out the source code in
+# base/checks.c
+
+use_aggressive_host_checking=0
+
+
+
+# SERVICE CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# service checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of service checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_service_checks=1
+
+
+
+# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# service checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_service_checks=1
+
+
+
+# HOST CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# host checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of host checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_host_checks=1
+
+
+
+# PASSIVE HOST CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# host checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_host_checks=1
+
+
+
+# NOTIFICATIONS OPTION
+# This determines whether or not Icinga will sent out any host or
+# service notifications when it is initially (re)started.
+# Values: 1 = enable notifications, 0 = disable notifications
+
+enable_notifications=1
+
+
+
+# EVENT HANDLER USE OPTION
+# This determines whether or not Icinga will run any host or
+# service event handlers when it is initially (re)started. Unless
+# you're implementing redundant hosts, leave this option enabled.
+# Values: 1 = enable event handlers, 0 = disable event handlers
+
+enable_event_handlers=1
+
+
+
+# STATE BASED ESCALATION RANGES !!!Experimental!!!
+# This option allows you to enable state based escalation ranges which
+# will allow a more detailed granularity on when an escalation notification
+# may happen, adding a filter based on the current host or service state
+# when checking the escalation for notification viability.
+# This is a behavioural change to the default, and therefore intentionally
+# disabled. Enable at your own risk, as this remains an experimental feature.
+# Values: 1 = enable state based escalation ranges,
+# 0 = disable state based escalation ranges
+
+#enable_state_based_escalation_ranges=0
+
+
+
+# PROCESS PERFORMANCE DATA OPTION
+# This determines whether or not Icinga will process performance
+# data returned from service and host checks. If this option is
+# enabled, host performance data will be processed using the
+# host_perfdata_command (defined below) and service performance
+# data will be processed using the service_perfdata_command (also
+# defined below). Read the HTML docs for more information on
+# performance data.
+# Values: 1 = process performance data, 0 = do not process performance data
+
+process_performance_data=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
+# These commands are run after every host and service check is
+# performed. These commands are executed only if the
+# process_performance_data option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on performance data.
+
+#host_perfdata_command=process-host-perfdata
+#service_perfdata_command=process-service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILES
+# These files are used to store host and service performance data.
+# Performance data is only written to these files if the
+# process_performance_data option (above) is set to 1.
+
+#host_perfdata_file=/tmp/host-perfdata
+#service_perfdata_file=/tmp/service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
+# These options determine what data is written (and how) to the
+# performance data files. The templates may contain macros, special
+# characters (\t for tab, \r for carriage return, \n for newline)
+# and plain text. A newline is automatically added after each write
+# to the performance data file. Some examples of what you can do are
+# shown below.
+
+#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
+#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE MODES
+# This option determines whether or not the host and service
+# performance data files are opened in write ("w") or append ("a")
+# mode. If you want to use named pipes, you should use the special
+# pipe ("p") mode which avoid blocking at startup, otherwise you will
+# likely want the defult append ("a") mode.
+
+#host_perfdata_file_mode=a
+#service_perfdata_file_mode=a
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
+# These options determine how often (in seconds) the host and service
+# performance data files are processed using the commands defined
+# below. A value of 0 indicates the files should not be periodically
+# processed.
+
+#host_perfdata_file_processing_interval=0
+#service_perfdata_file_processing_interval=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
+# These commands are used to periodically process the host and
+# service performance data files. The interval at which the
+# processing occurs is determined by the options above.
+
+#host_perfdata_file_processing_command=process-host-perfdata-file
+#service_perfdata_file_processing_command=process-service-perfdata-file
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
+# THese options determine wether the core will process empty perfdata
+# results or not. This is needed for distributed monitoring, and intentionally
+# turned on by default.
+# If you don't require empty perfdata - saving some cpu cycles
+# on unwanted macro calculation - you can turn that off. Be careful!
+# Values: 1 = enable, 0 = disable
+
+#host_perfdata_process_empty_results=1
+#service_perfdata_process_empty_results=1
+
+
+
+# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
+# This boolean option determines whether services assigned to empty
+# host groups (host groups with no host members) will cause Icinga to
+# exit with error on start up (or during a configuration check) or not.
+# It's useful to be able to assign services to empty hostgroups when
+# configuration files or pre-cached object files are distributed to
+# various pollers, or when the process of generating Icinga config is
+# automated, or when a set of services is slowly being phased out but
+# should be kept around.
+# The default behavior if the option is not present in the main
+# configuration file is for Icinga to exit with error if services are
+# associated with host groups that have no hosts associated with them.
+
+#allow_empty_hostgroup_assignment=0
+
+
+
+# OBSESS OVER SERVICE CHECKS OPTION
+# This determines whether or not Icinga will obsess over service
+# checks and run the ocsp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over services, 0 = do not obsess (default)
+
+obsess_over_services=0
+
+
+
+# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
+# This is the command that is run for every service check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_services option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ocsp_command=somecommand
+
+
+
+# OBSESS OVER HOST CHECKS OPTION
+# This determines whether or not Icinga will obsess over host
+# checks and run the ochp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over hosts, 0 = do not obsess (default)
+
+obsess_over_hosts=0
+
+
+
+# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
+# This is the command that is run for every host check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_hosts option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ochp_command=somecommand
+
+
+
+# TRANSLATE PASSIVE HOST CHECKS OPTION
+# This determines whether or not Icinga will translate
+# DOWN/UNREACHABLE passive host check results into their proper
+# state for this instance of Icinga. This option is useful
+# if you have distributed or failover monitoring setup. In
+# these cases your other Icinga servers probably have a different
+# "view" of the network, with regards to the parent/child relationship
+# of hosts. If a distributed monitoring server thinks a host
+# is DOWN, it may actually be UNREACHABLE from the point of
+# this Icinga instance. Enabling this option will tell Icinga
+# to translate any DOWN or UNREACHABLE host states it receives
+# passively into the correct state from the view of this server.
+# Values: 1 = perform translation, 0 = do not translate (default)
+
+translate_passive_host_checks=0
+
+
+
+# PASSIVE HOST CHECKS ARE SOFT OPTION
+# This determines whether or not Icinga will treat passive host
+# checks as being HARD or SOFT. By default, a passive host check
+# result will put a host into a HARD state type. This can be changed
+# by enabling this option.
+# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
+
+passive_host_checks_are_soft=0
+
+
+
+# ORPHANED HOST/SERVICE CHECK OPTIONS
+# These options determine whether or not Icinga will periodically
+# check for orphaned host service checks. Since service checks are
+# not rescheduled until the results of their previous execution
+# instance are processed, there exists a possibility that some
+# checks may never get rescheduled. A similar situation exists for
+# host checks, although the exact scheduling details differ a bit
+# from service checks. Orphaned checks seem to be a rare
+# problem and should not happen under normal circumstances.
+# If you have problems with service checks never getting
+# rescheduled, make sure you have orphaned service checks enabled.
+# Values: 1 = enable checks, 0 = disable checks
+
+check_for_orphaned_services=1
+check_for_orphaned_hosts=1
+
+
+
+# SERVICE CHECK TIMEOUT STATE
+# This setting determines the state Icinga will report when a
+# service check times out meaning it does not respond within
+# service_check_timeout seconds. The default is set to Unknown
+# and not Critical.
+# Valid settings are:
+# c - Critical
+# u - Unknown (default)
+# w - Warning
+# o - OK
+
+service_check_timeout_state=u
+
+
+
+# SERVICE FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of service results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_service_freshness=1
+
+
+
+# SERVICE FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of service check results. If you have
+# disabled service freshness checking, this option has no effect.
+
+service_freshness_check_interval=60
+
+
+
+# HOST FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of host results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_host_freshness=0
+
+
+
+# HOST FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of host check results. If you have
+# disabled host freshness checking, this option has no effect.
+
+host_freshness_check_interval=60
+
+
+
+
+# ADDITIONAL FRESHNESS THRESHOLD LATENCY
+# This setting determines the number of seconds that Icinga
+# will add to any host and service freshness thresholds that
+# it calculates (those not explicitly specified by the user).
+
+additional_freshness_latency=15
+
+
+
+
+# FLAP DETECTION OPTION
+# This option determines whether or not Icinga will try
+# and detect hosts and services that are "flapping".
+# Flapping occurs when a host or service changes between
+# states too frequently. When Icinga detects that a
+# host or service is flapping, it will temporarily suppress
+# notifications for that host/service until it stops
+# flapping. Flap detection is very experimental, so read
+# the HTML documentation before enabling this feature!
+# Values: 1 = enable flap detection
+# 0 = disable flap detection (default)
+
+enable_flap_detection=1
+
+
+
+# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
+# Read the HTML documentation on flap detection for
+# an explanation of what this option does. This option
+# has no effect if flap detection is disabled.
+
+low_service_flap_threshold=5.0
+high_service_flap_threshold=20.0
+low_host_flap_threshold=5.0
+high_host_flap_threshold=20.0
+
+
+
+# DATE FORMAT OPTION
+# This option determines how short dates are displayed. Valid options
+# include:
+# us (MM-DD-YYYY HH:MM:SS)
+# euro (DD-MM-YYYY HH:MM:SS)
+# iso8601 (YYYY-MM-DD HH:MM:SS)
+# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
+#
+
+date_format=iso8601
+
+
+
+
+# TIMEZONE OFFSET
+# This option is used to override the default timezone that this
+# instance of Icinga runs in. If not specified, Icinga will use
+# the system configured timezone.
+#
+# NOTE: In order to display the correct timezone in the CGIs, you
+# will also need to alter the Apache directives for the CGI path
+# to include your timezone. Example:
+#
+# <Directory "/usr/local/icinga/sbin/">
+# SetEnv TZ "Australia/Brisbane"
+# ...
+# </Directory>
+
+#use_timezone=US/Mountain
+#use_timezone=Australia/Brisbane
+
+
+
+
+# P1.PL FILE LOCATION
+# This value determines where the p1.pl perl script (used by the
+# embedded Perl interpreter) is located. If you didn't compile
+# Icinga with embedded Perl support, this option has no effect.
+
+p1_file=/usr/lib/icinga/p1.pl
+
+
+
+# EMBEDDED PERL INTERPRETER OPTION
+# This option determines whether or not the embedded Perl interpreter
+# will be enabled during runtime. This option has no effect if Icinga
+# has not been compiled with support for embedded Perl.
+# This option is intentionally disabled by default, because embedded
+# perl can cause memory leaks and make Icinga unstable if not properly
+# used.
+# Only enable this setting when you really know what you are doing!
+# Values: 0 = disable interpreter, 1 = enable interpreter
+
+enable_embedded_perl=1
+
+
+
+# EMBEDDED PERL USAGE OPTION
+# This option determines whether or not Icinga will process Perl plugins
+# and scripts with the embedded Perl interpreter if the plugins/scripts
+# do not explicitly indicate whether or not it is okay to do so. Read
+# the HTML documentation on the embedded Perl interpreter for more
+# information on how this option works.
+
+use_embedded_perl_implicitly=1
+
+
+
+# EVENT HANDLERS FOR STALKED HOSTS/SERVICES
+# Allow running event handlers for stalked hosts/services in order
+# to forward to external systems.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_event_handlers_for_hosts=0
+stalking_event_handlers_for_services=0
+
+
+
+# NOTIFICATIONS FOR STALKED HOSTS/SERVICES
+# Allow notifications for stalked hosts/services globally
+# for all contacts in order to notify about a stalking
+# alert.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_notifications_for_hosts=0
+stalking_notifications_for_services=0
+
+
+
+# ILLEGAL OBJECT NAME CHARACTERS
+# This option allows you to specify illegal characters that cannot
+# be used in host names, service descriptions, or names of other
+# object types.
+
+illegal_object_name_chars=`~!$%^&*|'"<>?,()=
+
+
+
+# ILLEGAL MACRO OUTPUT CHARACTERS
+# This option allows you to specify illegal characters that are
+# stripped from macros before being used in notifications, event
+# handlers, etc. This DOES NOT affect macros used in service or
+# host check commands.
+# The following macros are stripped of the characters you specify:
+# $HOSTOUTPUT$
+# $HOSTPERFDATA$
+# $HOSTACKAUTHOR$
+# $HOSTACKCOMMENT$
+# $SERVICEOUTPUT$
+# $SERVICEPERFDATA$
+# $SERVICEACKAUTHOR$
+# $SERVICEACKCOMMENT$
+
+illegal_macro_output_chars=`~$&|'"<>
+
+
+
+# KEEP UNKNOWN MACROS
+# This option can be used to keep unknown macros within the output.
+# e.g. check_proc -C $foo$ will remain.
+# This was the default in versions older than Icinga 1.8, but now
+# the default is to remove those macros from the output, causing
+# the shell to interpret $foo and leaving a single $ there. See
+# #2291 for further information.
+# Make sure to escape single dollar signs with another '$', as the
+# docs describe. Other than that, enable this setting to revert to
+# the old behaviour.
+
+keep_unknown_macros=1
+
+
+
+# REGULAR EXPRESSION MATCHING
+# This option controls whether or not regular expression matching
+# takes place in the object config files. Regular expression
+# matching is used to match host, hostgroup, service, and service
+# group names/descriptions in some fields of various object types.
+# Values: 1 = enable regexp matching, 0 = disable regexp matching
+
+use_regexp_matching=0
+
+
+
+# "TRUE" REGULAR EXPRESSION MATCHING
+# This option controls whether or not "true" regular expression
+# matching takes place in the object config files. This option
+# only has an effect if regular expression matching is enabled
+# (see above). If this option is DISABLED, regular expression
+# matching only occurs if a string contains wildcard characters
+# (* and ?). If the option is ENABLED, regexp matching occurs
+# all the time (which can be annoying).
+# Values: 1 = enable true matching, 0 = disable true matching
+
+use_true_regexp_matching=0
+
+
+
+# ADMINISTRATOR EMAIL/PAGER ADDRESSES
+# The email and pager address of a global administrator (likely you).
+# Icinga never uses these values itself, but you can access them by
+# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
+# commands.
+
+admin_email=root@localhost
+admin_pager=pageroot@localhost
+
+
+
+# DAEMON CORE DUMP OPTION
+# This option determines whether or not Icinga is allowed to create
+# a core dump when it runs as a daemon. Note that it is generally
+# considered bad form to allow this, but it may be useful for
+# debugging purposes. Enabling this option doesn't guarantee that
+# a core file will be produced, but that's just life...
+# Values: 1 - Allow core dumps
+# 0 - Do not allow core dumps (default)
+
+daemon_dumps_core=0
+
+
+
+# LARGE INSTALLATION TWEAKS OPTION
+# This option determines whether or not Icinga will take some shortcuts
+# which can save on memory and CPU usage in large Icinga installations.
+# Read the documentation for more information on the benefits/tradeoffs
+# of enabling this option.
+# Values: 1 - Enabled tweaks
+# 0 - Disable tweaks (default)
+
+use_large_installation_tweaks=0
+
+
+
+# ENABLE ENVIRONMENT MACROS
+# This option determines whether or not Icinga will make all standard
+# macros available as environment variables when host/service checks
+# and system commands (event handlers, notifications, etc.) are
+# executed. Enabling this option can cause performance issues in
+# large installations, as it will consume a bit more memory and (more
+# importantly) consume more CPU.
+# Keep in mind that various addons/plugins will require this setting
+# to be enabled (e.g. check_oracle_health) for special usage.
+# Values: 1 - Enable environment variable macros
+# 0 - Disable environment variable macros (default)
+
+enable_environment_macros=1
+
+
+
+# CHILD PROCESS MEMORY OPTION
+# This option determines whether or not Icinga will free memory in
+# child processes (processed used to execute system commands and host/
+# service checks). If you specify a value here, it will override
+# program defaults.
+# Value: 1 - Free memory in child processes
+# 0 - Do not free memory in child processes
+
+#free_child_process_memory=1
+
+
+
+# CHILD PROCESS FORKING BEHAVIOR
+# This option determines how Icinga will fork child processes
+# (used to execute system commands and host/service checks). Normally
+# child processes are fork()ed twice, which provides a very high level
+# of isolation from problems. Fork()ing once is probably enough and will
+# save a great deal on CPU usage (in large installs), so you might
+# want to consider using this. If you specify a value here, it will
+# program defaults.
+# Value: 1 - Child processes fork() twice
+# 0 - Child processes fork() just once
+
+#child_processes_fork_twice=1
+
+
+
+# DEBUG LEVEL
+# This option determines how much (if any) debugging information will
+# be written to the debug file. OR values together to log multiple
+# types of information.
+# Values:
+# -1 = Everything
+# 0 = Nothing
+# 1 = Functions
+# 2 = Configuration
+# 4 = Process information
+# 8 = Scheduled events
+# 16 = Host/service checks
+# 32 = Notifications
+# 64 = Event broker
+# 128 = External commands
+# 256 = Commands
+# 512 = Scheduled downtime
+# 1024 = Comments
+# 2048 = Macros
+
+debug_level=0
+
+
+
+# DEBUG VERBOSITY
+# This option determines how verbose the debug log out will be.
+# Values: 0 = Brief output
+# 1 = More detailed
+# 2 = Very detailed
+
+debug_verbosity=2
+
+
+
+# DEBUG FILE
+# This option determines where Icinga should write debugging information.
+
+debug_file=/var/log/icinga/icinga.debug
+
+
+
+# MAX DEBUG FILE SIZE
+# This option determines the maximum size (in bytes) of the debug file. If
+# the file grows larger than this size, it will be renamed with a .old
+# extension. If a file already exists with a .old extension it will
+# automatically be deleted. This helps ensure your disk space usage doesn't
+# get out of control when debugging Icinga.
+
+# 100M
+max_debug_file_size=100000000
diff --git a/roles/icinga-ed/files/nt.cfg b/roles/icinga-ed/files/nt.cfg
new file mode 100644
index 0000000..b461aca
--- /dev/null
+++ b/roles/icinga-ed/files/nt.cfg
@@ -0,0 +1,15 @@
+# If you are confused about this command definition, cause you was
+# reading other suggestions, please have a look into
+# /usr/share/doc/nagios-plugins/README.Debian
+
+# 'check_nt' command definition
+#define command {
+# command_name check_nt
+# command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -v '$ARG1$'
+#}
+
+# 'check_nscp' command definition
+define command {
+ command_name check_nscp
+ command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -p 12489 -v '$ARG1$'
+}
diff --git a/roles/icinga-ed/files/services_icinga.cfg b/roles/icinga-ed/files/services_icinga.cfg
new file mode 100644
index 0000000..4ea25d8
--- /dev/null
+++ b/roles/icinga-ed/files/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-ed/handlers/main.yml b/roles/icinga-ed/handlers/main.yml
new file mode 100644
index 0000000..721651e
--- /dev/null
+++ b/roles/icinga-ed/handlers/main.yml
@@ -0,0 +1,12 @@
+---
+ - name: restart icinga
+ service: name=icinga state=restarted
+
+ - name: stop icinga
+ service: name=icinga state=stopped
+
+ - name: start icinga
+ service: name=icinga state=started
+
+ - name: restart apache
+ service: name=apache2 state=restarted
diff --git a/roles/icinga-ed/tasks/main.yml b/roles/icinga-ed/tasks/main.yml
new file mode 100644
index 0000000..8815ca9
--- /dev/null
+++ b/roles/icinga-ed/tasks/main.yml
@@ -0,0 +1,153 @@
+---
+- name: Installation apache2
+ apt: name=apache2 state=present
+
+- name: Installation snmp
+ apt: name=snmp state=present
+
+- name: Installation de icinga
+ apt: name=icinga state=present
+
+- name: Installation de nagios-plugins
+ apt: name=nagios-plugins state=present
+
+- name: Installation de nagios-snmp-plugins
+ apt: name=nagios-snmp-plugins state=present
+
+- name: Installation des dépendances dns
+ apt: name=libnet-dns-perl state=present
+
+#- name: Copie de fichier apache.conf
+# copy: remote_src=true src=/etc/icinga/apache2.conf dest=/etc/apache2/sites-available/icinga.conf
+
+#- name: activation du site de icinga
+# shell: a2ensite icinga
+# notify:
+# - restart icinga
+
+- name: changement de mot de passe de icingaadmin
+ shell: htpasswd -dbc /etc/icinga/htpasswd.users icingaadmin root
+
+- name: Copie du fichier commands.cfg
+ copy: src=commands.cfg dest=/etc/icinga/commands.cfg
+
+- name: Copie du fichier icinga.cfg
+ copy: src=icinga.cfg dest=/etc/icinga
+
+- name: Copie du fichier contact
+ copy: src=contacts_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-infra.cfg
+ copy: src=cfg/s-infra.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier s-proxy.cfg
+ copy: src=cfg/s-proxy.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier s-adm.cfg
+ copy: src=cfg/s-adm.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier r-int.cfg
+ copy: src=cfg/r-int.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier r-ext.cfg
+ copy: src=cfg/r-ext.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier netgear
+ copy: src=cfg/netgear.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier serveur
+ copy: src=cfg/srv-2012.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier gwsio4
+ copy: src=cfg/gwsio4.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier hostgroup
+ copy: src=hostgroups_icinga.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier services
+ copy: src=services_icinga.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+#- name: attribution des droits dossier icinga rw
+# file:
+# path: /var/lib/icinga/rw
+# owner: nagios
+# mode: 2710
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- name: attribution des droits dossier icinga
+# file:
+# path: /var/lib/icinga
+# owner: nagios
+# mode: 751
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- file:
+# path: /var/lib/icinga/rw
+# state: directory
+# mode: 2770
+# notify:
+# - stop icinga
+
+#- name: attribution des droits dossier var lib icinga
+# shell: chmod 2770 /var/lib/icinga/rw
+# notify:
+# - stop icinga
+
+#- name: attribution des droits dossier var lib icinga
+# file:
+# path: /var/lib/icinga/rw
+# owner: www-data
+# mode: 2710
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- service:
+# name: apache2
+# state: restarted
+# notify:
+# - start icinga
+
+#- name: attribution des droits dossier var lib icinga
+# shell: apache2ctl restart
+# notify:
+# - start icinga
+
+- name: copie nt.cfg
+ copy: src=nt.cfg dest=/etc/nagios-plugins/config
+
+#- name: copie dns.cfg
+# copy: remote_src=true src=dns.cfg dest=/etc/nagios-plugins/config
+
+- name: copie check traffic
+ copy: src=check_iftraffic3.pl dest=/usr/lib/nagios/plugins
+
+- name: modif des droits plugin traffic
+ shell: chmod 755 /usr/lib/nagios/plugins/check_iftraffic3.pl
+
+- name: message d'information
+ debug: msg="Pour superviser le Windows, il faut installer NSClient++"
diff --git a/roles/icinga-fk/files/cfg/contacts_icinga.cfg b/roles/icinga-fk/files/cfg/contacts_icinga.cfg
new file mode 100644
index 0000000..8a66285
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email icinga.ppe31@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-fk/files/cfg/extinfo_icinga.cfg b/roles/icinga-fk/files/cfg/extinfo_icinga.cfg
new file mode 100644
index 0000000..07bd594
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/extinfo_icinga.cfg
@@ -0,0 +1,13 @@
+##
+## Extended Host and Service Information
+##
+
+define hostextinfo{
+ hostgroup_name debian-servers
+ notes Debian GNU/Linux servers
+# notes_url http://webserver.localhost.localdomain/hostinfo.pl?host=netware1
+ icon_image base/debian.png
+ icon_image_alt Debian GNU/Linux
+ vrml_image debian.png
+ statusmap_image base/debian.gd2
+ }
diff --git a/roles/icinga-fk/files/cfg/generic-host_icinga.cfg b/roles/icinga-fk/files/cfg/generic-host_icinga.cfg
new file mode 100644
index 0000000..e6d96ac
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/generic-host_icinga.cfg
@@ -0,0 +1,19 @@
+# Generic host definition template - This is NOT a real host, just a template!
+
+define host{
+ name generic-host ; The name of this host template
+ notifications_enabled 1 ; Host notifications are enabled
+ event_handler_enabled 1 ; Host event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ check_command check-host-alive
+ max_check_attempts 10
+ notification_interval 0
+ notification_period 24x7
+ notification_options d,u,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-fk/files/cfg/generic-service_icinga.cfg b/roles/icinga-fk/files/cfg/generic-service_icinga.cfg
new file mode 100644
index 0000000..4d60c79
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/generic-service_icinga.cfg
@@ -0,0 +1,26 @@
+# generic service template definition
+define service{
+ name generic-service ; The 'name' of this service template
+ active_checks_enabled 1 ; Active service checks are enabled
+ passive_checks_enabled 1 ; Passive service checks are enabled/accepted
+ parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems)
+ obsess_over_service 1 ; We should obsess over this service (if necessary)
+ check_freshness 0 ; Default is to NOT check service 'freshness'
+ notifications_enabled 1 ; Service notifications are enabled
+ event_handler_enabled 1 ; Service event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ notification_interval 0 ; Only send notifications on status change by default.
+ is_volatile 0
+ check_period 24x7
+ normal_check_interval 5
+ retry_check_interval 1
+ max_check_attempts 4
+ notification_period 24x7
+ notification_options w,u,c,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-fk/files/cfg/gwsio2.cfg b/roles/icinga-fk/files/cfg/gwsio2.cfg
new file mode 100644
index 0000000..c09b7d2
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/gwsio2.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name gwsio2
+ alias Passerelle
+ address 192.168.0.1
+ icon_image cook/linux_server.gif
+ statusmap_image cook/linux_server.gd2
+ }
diff --git a/roles/icinga-fk/files/cfg/hostgroups_icinga.cfg b/roles/icinga-fk/files/cfg/hostgroups_icinga.cfg
new file mode 100644
index 0000000..621646b
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/hostgroups_icinga.cfg
@@ -0,0 +1,74 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-infra, s-proxy, r-int, r-ext, s-adm, s-test
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-adm, s-infra, s-proxy, r-int, r-ext, localhost, s-test, gwsio2
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-infra, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members r-int, srv-2012
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+#define hostgroup {
+# hostgroup_name email-servers
+# alias serveurs-email
+# members s-mess
+# }
+
+define hostgroup {
+ hostgroup_name proxy-servers
+ alias serveurs-proxy
+ members s-proxy
+}
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members srv-2012
+}
+
+#define hostgroup{
+# hostgroup_name switch
+# alias switch
+# members netgear
+#}
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members s-infra, s-proxy, r-int, r-ext, s-adm, s-test
+}
+
diff --git a/roles/icinga-fk/files/cfg/localhost_icinga.cfg b/roles/icinga-fk/files/cfg/localhost_icinga.cfg
new file mode 100644
index 0000000..c15cda4
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/localhost_icinga.cfg
@@ -0,0 +1,60 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in icinga-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name localhost
+ alias localhost
+ address 127.0.0.1
+ parents gwsio2
+ }
+
+# Define a service to check the disk space of the root partition
+# on the local machine. Warning if < 20% free, critical if
+# < 10% free space on partition.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Disk Space
+ check_command check_all_disks!20%!10%
+ }
+
+
+
+# Define a service to check the number of currently logged in
+# users on the local machine. Warning if > 20 users, critical
+# if > 50 users.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Users
+ check_command check_users!20!50
+ }
+
+
+# Define a service to check the number of currently running procs
+# on the local machine. Warning if > 250 processes, critical if
+# > 400 processes.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Total Processes
+ check_command check_procs!250!400
+ }
+
+
+
+# Define a service to check the load on the local machine.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Load
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
diff --git a/roles/icinga-fk/files/cfg/netgear.cfg b/roles/icinga-fk/files/cfg/netgear.cfg
new file mode 100644
index 0000000..23562fe
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/netgear.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name netgear
+ alias switch
+ address 192.168.0.2
+ #parents gwsio4
+ icon_image cook/switch.gif
+ statusmap_image cook/switch.gd2
+}
+
diff --git a/roles/icinga-fk/files/cfg/r-ext.cfg b/roles/icinga-fk/files/cfg/r-ext.cfg
new file mode 100644
index 0000000..4c14bef
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/r-ext.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-ext
+ alias Routeur externe
+ address 192.168.200.253
+ parents localhost
+ }
diff --git a/roles/icinga-fk/files/cfg/r-int.cfg b/roles/icinga-fk/files/cfg/r-int.cfg
new file mode 100644
index 0000000..77ebe3d
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/r-int.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-int
+ alias Routeur interne
+ address 172.16.0.254
+ parents r-ext
+ }
diff --git a/roles/icinga-fk/files/cfg/s-adm.cfg b/roles/icinga-fk/files/cfg/s-adm.cfg
new file mode 100644
index 0000000..aeadbee
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/s-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-adm
+ alias debian-servers
+ address 192.168.99.99
+ parents r-int
+ }
+
diff --git a/roles/icinga-fk/files/cfg/s-infra.cfg b/roles/icinga-fk/files/cfg/s-infra.cfg
new file mode 100644
index 0000000..c369ff6
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/s-infra.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra
+ alias debian-servers
+ address 172.16.0.1
+ parents r-int
+ }
+
diff --git a/roles/icinga-fk/files/cfg/s-proxy.cfg b/roles/icinga-fk/files/cfg/s-proxy.cfg
new file mode 100644
index 0000000..de4f3c9
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/s-proxy.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-proxy
+ alias serveur proxy
+ address 172.16.0.2
+ parents r-int
+ }
diff --git a/roles/icinga-fk/files/cfg/s-test.cfg b/roles/icinga-fk/files/cfg/s-test.cfg
new file mode 100644
index 0000000..204262d
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/s-test.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-test
+ alias machine test
+ address 172.16.0.18
+ parents r-int
+ }
diff --git a/roles/icinga-fk/files/cfg/services_icinga.cfg b/roles/icinga-fk/files/cfg/services_icinga.cfg
new file mode 100644
index 0000000..4ea25d8
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-fk/files/cfg/srv-2012.cfg b/roles/icinga-fk/files/cfg/srv-2012.cfg
new file mode 100644
index 0000000..8ff28a9
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/srv-2012.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name srv-2012
+ alias windows-servers
+ address 172.16.0.6
+ parents r-int
+ icon_image base/win40.gif
+ statusmap_image base/win40.gd2
+ }
+
diff --git a/roles/icinga-fk/files/cfg/timeperiods_icinga.cfg b/roles/icinga-fk/files/cfg/timeperiods_icinga.cfg
new file mode 100644
index 0000000..55ecf9d
--- /dev/null
+++ b/roles/icinga-fk/files/cfg/timeperiods_icinga.cfg
@@ -0,0 +1,50 @@
+###############################################################################
+# timeperiods.cfg
+###############################################################################
+
+# This defines a timeperiod where all times are valid for checks,
+# notifications, etc. The classic "24x7" support nightmare. :-)
+
+define timeperiod{
+ timeperiod_name 24x7
+ alias 24 Hours A Day, 7 Days A Week
+ sunday 00:00-24:00
+ monday 00:00-24:00
+ tuesday 00:00-24:00
+ wednesday 00:00-24:00
+ thursday 00:00-24:00
+ friday 00:00-24:00
+ saturday 00:00-24:00
+ }
+
+# Here is a slightly friendlier period during work hours
+define timeperiod{
+ timeperiod_name workhours
+ alias Standard Work Hours
+ monday 09:00-17:00
+ tuesday 09:00-17:00
+ wednesday 09:00-17:00
+ thursday 09:00-17:00
+ friday 09:00-17:00
+ }
+
+# The complement of workhours
+define timeperiod{
+ timeperiod_name nonworkhours
+ alias Non-Work Hours
+ sunday 00:00-24:00
+ monday 00:00-09:00,17:00-24:00
+ tuesday 00:00-09:00,17:00-24:00
+ wednesday 00:00-09:00,17:00-24:00
+ thursday 00:00-09:00,17:00-24:00
+ friday 00:00-09:00,17:00-24:00
+ saturday 00:00-24:00
+ }
+
+# This one is a favorite: never :)
+define timeperiod{
+ timeperiod_name never
+ alias Never
+ }
+
+# end of file
diff --git a/roles/icinga-fk/files/check_iftraffic3.pl b/roles/icinga-fk/files/check_iftraffic3.pl
new file mode 100755
index 0000000..62ddbd1
--- /dev/null
+++ b/roles/icinga-fk/files/check_iftraffic3.pl
@@ -0,0 +1,643 @@
+#!/usr/bin/perl -w
+#
+# check_iftraffic.pl - Nagios(r) network traffic monitor plugin
+# Copyright (C) 2004 Gerd Mueller / Netways GmbH
+# $Id: check_iftraffic.pl 1119 2006-02-09 10:30:09Z gmueller $
+#
+# mw = Markus Werner mw+nagios@wobcom.de
+# Remarks (mw):
+#
+# I adopted as much as possible the programming style of the origin code.
+#
+# There should be a function to exit this programm,
+# instead of calling print and exit statements all over the place.
+#
+#
+# minor changes by mw
+# The snmp if_counters on net devices can have overflows.
+# I wrote this code to address this situation.
+# It has no automatic detection and which point the overflow
+# occurs but it will generate a warning state and you
+# can set the max value by calling this script with an additional
+# arg.
+#
+# minor cosmetic changes by mw
+# Sorry but I couldn't sustain to clean up some things.
+#
+# gj = Greg Frater gregATfraterfactory.com
+# Remarks (gj):
+# minor (gj):
+#
+# * fixed the performance data, formating was not to spec
+# * Added a check of the interfaces status (up/down).
+# If down the check returns a critical status.
+# * Allow either textual or the numeric index value.
+# * If the interface speed is not specified on the command line
+# it gets it automatically from IfSpeed
+# * Added option for second ifSpeed to allow for asymetrcal links
+# such as a DSL line or cable modem where the download and upload
+# speeds are different
+# * Added -B option to display results in bits/sec instead of Bytes/sec
+# * Added the current usage in Bytes/s (or bit/s) to the perfdata output
+# * Added ability for plugin to determine interface to query by matching IP
+# address of host with entry in ipAdEntIfIndex (.1.3.6.1.2.1.4.20.1.2)
+# * Added -L flag to list entries found in the ipAdEntIfIndex table
+# Otherwise, it works as before.
+#
+#
+#
+#
+# based on check_traffic from Adrian Wieczorek, <ads (at) irc.pila.pl>
+#
+# Send us bug reports, questions and comments about this plugin.
+# Latest version of this software: http://www.nagiosexchange.org
+#
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307
+
+use strict;
+
+use Net::SNMP;
+use Getopt::Long;
+&Getopt::Long::config('bundling');
+
+use Data::Dumper;
+
+my $host_ip;
+my $host_address;
+my $iface_number;
+my $iface_descr;
+my $iface_speed;
+my $iface_speedOut;
+my $index_list;
+my $opt_h;
+my $units;
+
+my $session;
+my $error;
+my $port = 161;
+my $snmp_version = 1;
+
+my @snmpoids;
+
+# SNMP OIDs for Traffic
+my $snmpIfOperStatus = '1.3.6.1.2.1.2.2.1.8';
+my $snmpIfInOctets = '1.3.6.1.2.1.2.2.1.10';
+my $snmpIfOutOctets = '1.3.6.1.2.1.2.2.1.16';
+my $snmpIfDescr = '1.3.6.1.2.1.2.2.1.2';
+my $snmpIfSpeed = '1.3.6.1.2.1.2.2.1.5';
+my $snmpIPAdEntIfIndex = '1.3.6.1.2.1.4.20.1.2';
+
+my $response;
+
+# Path to tmp files
+my $TRAFFIC_FILE = "/tmp/traffic";
+
+# changes sos 20090717 UNKNOWN must bes 3
+my %STATUS_CODE =
+ ( 'UNKNOWN' => '3', 'OK' => '0', 'WARNING' => '1', 'CRITICAL' => '2' );
+
+#default values;
+my $state = "UNKNOWN";
+my $if_status = '4';
+my ( $in_bytes, $out_bytes ) = 0;
+my $warn_usage = 85;
+my $crit_usage = 98;
+my $COMMUNITY = "public";
+my $use_reg = undef; # Use Regexp for name
+my $output = "";
+my $bits = undef;
+my $suffix = "Bs";
+my $label = "MBytes";
+
+#added 20050614 by mw
+my $max_value;
+my $max_bytes;
+
+#cosmetic changes 20050614 by mw, see old versions for detail
+# Added options for bits and second max ifspeed 20100202 by gj
+# Added options for specificy IP addr to match 20100405 by gj
+my $status = GetOptions(
+ "h|help" => \$opt_h,
+ 'B' => \$bits,
+ 'bits' => \$bits,
+ "C|community=s" => \$COMMUNITY,
+ "w|warning=s" => \$warn_usage,
+ "c|critical=s" => \$crit_usage,
+ "b|bandwidth|I|inBandwidth=i" => \$iface_speed,
+ "O|outBandwidth=i" => \$iface_speedOut,
+ 'r' => \$use_reg,
+ 'noregexp' => \$use_reg,
+ "p|port=i" => \$port,
+ "u|units=s" => \$units,
+ "i|interface=s" => \$iface_number,
+ "A|address=s" => \$host_ip,
+ "H|hostname=s" => \$host_address,
+ 'L' => \$index_list,
+ 'list' => \$index_list,
+
+ #added 20050614 by mw
+ "M|max=i" => \$max_value
+);
+
+if ( $status == 0 ) {
+ print_help();
+ exit $STATUS_CODE{'OK'};
+}
+
+# Changed 20091214 gj
+# Check for missing options
+#if ( ( !$host_address ) or ( !$iface_descr ) ) {
+if ( !$host_address ) {
+ print "\nMissing host address!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speed ) and ( !$units ) ){
+ print "\nMissing units!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $units ) and ( ( !$iface_speed ) and ( !$iface_speedOut ) ) ) {
+ print "\nMissing interface maximum speed!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speedOut ) and ( !$units ) ) {
+ print "\nMissing units for Out maximum speed!\n\n";
+ stop(print_usage(),"OK");
+}
+
+
+if ($bits) {
+ $suffix = "bs"
+}
+
+if ( !$iface_speed ) {
+ # Do nothing
+}else{
+
+ #change 20050414 by mw
+ # Added iface_speedOut 20100202 by gj
+ # Convert interface speed to kiloBytes
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+ if ( $iface_speedOut ) {
+ $iface_speedOut = bits2bytes( $iface_speedOut, $units ) / 1024;
+ }
+ if ( !$max_value ) {
+
+ # If no -M Parameter was set, set it to 32Bit Overflow
+ $max_bytes = 4194304 ; # the value is (2^32/1024)
+ }
+ else {
+ $max_bytes = unit2bytes( $max_value, $units );
+ }
+}
+
+if ( $snmp_version =~ /[12]/ ) {
+ ( $session, $error ) = Net::SNMP->session(
+ -hostname => $host_address,
+ -community => $COMMUNITY,
+ -port => $port,
+ -version => $snmp_version
+ );
+
+ if ( !defined($session) ) {
+ stop("UNKNOWN: $error","UNKNOWN");
+ }
+}
+elsif ( $snmp_version =~ /3/ ) {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v3 yet\n",$state);
+}
+else {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v$snmp_version yet\n",$state);
+}
+
+# Neither Interface Index nor Host IP address were specified
+if ( !$iface_descr ) {
+ if ( !$host_ip ){
+ # try to resolve host name and find index from ip addr
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_address );
+ } else {
+ # Use ip addr to find index
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_ip );
+ }
+}
+
+#push( @snmpoids, $snmpIPAdEntIfIndex . "." . $host_address );
+
+# Added 20091209 gj
+# Detect if a string description was given or a numberic interface index number
+if ( $iface_descr =~ /[^0123456789]+/ ) {
+ $iface_number = fetch_ifdescr( $session, $iface_descr );
+}else{
+ $iface_number = $iface_descr;
+}
+
+push( @snmpoids, $snmpIfSpeed . "." . $iface_number );
+push( @snmpoids, $snmpIfOperStatus . "." . $iface_number );
+push( @snmpoids, $snmpIfInOctets . "." . $iface_number );
+push( @snmpoids, $snmpIfOutOctets . "." . $iface_number );
+
+if ( !defined( $response = $session->get_request(@snmpoids) ) ) {
+ my $answer = $session->error;
+ $session->close;
+
+ stop("WARNING: SNMP error: $answer\n", "WARNING");
+}
+
+# Added 20091209 gj
+# Get interface speed from device if not provided on command line
+# Convert to kiloBytes
+if ( !$iface_speed ) {
+ $iface_speed = $response->{ $snmpIfSpeed . "." . $iface_number };
+ $units = "b";
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+}
+
+# Added 20100201 gj
+# Check if Out max speed was provided, use same if speed for both if not
+if (!$iface_speedOut) {
+ $iface_speedOut = $iface_speed;
+}
+
+$if_status = $response->{ $snmpIfOperStatus . "." . $iface_number };
+$in_bytes = $response->{ $snmpIfInOctets . "." . $iface_number } / 1024; # in kiloBytes
+$out_bytes = $response->{ $snmpIfOutOctets . "." . $iface_number } / 1024; # in kiloBytes
+
+$session->close;
+
+my $row;
+my $last_check_time = time - 1;
+my $last_in_bytes = $in_bytes;
+my $last_out_bytes = $out_bytes;
+
+if (
+ open( FILE,
+ "<" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address
+ )
+ )
+{
+ while ( $row = <FILE> ) {
+
+ #cosmetic change 20050416 by mw
+ #Couldn't sustain;-)
+## chomp();
+ ( $last_check_time, $last_in_bytes, $last_out_bytes ) =
+ split( ":", $row );
+
+ ### by sos 17.07.2009 check for last_bytes
+ if ( ! $last_in_bytes ) { $last_in_bytes=$in_bytes; }
+ if ( ! $last_out_bytes ) { $last_out_bytes=$out_bytes; }
+
+ if ($last_in_bytes !~ m/\d/) { $last_in_bytes=$in_bytes; }
+ if ($last_out_bytes !~ m/\d/) { $last_out_bytes=$out_bytes; }
+ }
+ close(FILE);
+}
+
+my $update_time = time;
+
+open( FILE, ">" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address )
+ or die "Can't open $TRAFFIC_FILE for writing: $!";
+
+printf FILE ( "%s:%.0ld:%.0ld\n", $update_time, $in_bytes, $out_bytes );
+close(FILE);
+
+my $db_file;
+
+#added 20050614 by mw
+#Check for and correct counter overflow (if possible).
+#See function counter_overflow.
+$in_bytes = counter_overflow( $in_bytes, $last_in_bytes, $max_bytes );
+$out_bytes = counter_overflow( $out_bytes, $last_out_bytes, $max_bytes );
+
+# Calculate traffic since last check (RX\TX) in kiloBytes
+my $in_traffic = sprintf( "%.2lf",
+ ( $in_bytes - $last_in_bytes ) / ( time - $last_check_time ) );
+my $out_traffic = sprintf( "%.2lf",
+ ( $out_bytes - $last_out_bytes ) / ( time - $last_check_time ) );
+
+# sos 20090717 changed due to rrdtool needs bytes
+my $in_traffic_absolut = $in_bytes * 1024 ;
+my $out_traffic_absolut = $out_bytes * 1024;
+
+# Calculate usage percentages
+my $in_usage = sprintf( "%.2f", ( 1.0 * $in_traffic * 100 ) / $iface_speed );
+my $out_usage = sprintf( "%.2f", ( 1.0 * $out_traffic * 100 ) / $iface_speedOut );
+
+
+if ($bits) {
+ # Convert output from Bytes to bits
+ $in_bytes = $in_bytes * 8;
+ $out_bytes = $out_bytes * 8;
+ $in_traffic = $in_traffic * 8;
+ $out_traffic = $out_traffic * 8;
+ $label = "Mbits";
+}
+
+my $in_prefix = "K";
+my $out_prefix = "K";
+
+if ( $in_traffic > 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 );
+ $in_prefix = "M";
+}
+if ( $out_traffic > 1024 ) {
+ $out_traffic = sprintf( "%.2f", $out_traffic / 1024 );
+ $out_prefix = "M";
+}
+if ( $in_traffic > 1024 * 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 * 1024 );
+ $in_prefix = "G";
+}
+if ( $out_traffic > 1024 * 1024 ) {
+ $out_traffic = sprintf( "%.2f",$out_traffic / 1024 * 1024 );
+ $out_prefix = "G";
+}
+
+# Convert from kiloBytes to megaBytes
+$in_bytes = sprintf( "%.2f", $in_bytes / 1024 );
+$out_bytes = sprintf( "%.2f", $out_bytes / 1024 );
+
+$state = "OK";
+
+# Added 20091209 by gj
+if ( $if_status != 1 ) {
+ $output = "Interface $iface_descr is down!";
+
+}else{
+ $output =
+ "Average IN: "
+ . $in_traffic . $in_prefix . $suffix . " (" . $in_usage . "%), "
+ . "Average OUT: " . $out_traffic . $out_prefix . $suffix . " (" . $out_usage . "%)<br>";
+ $output .= "Total RX: $in_bytes $label, Total TX: $out_bytes $label";
+}
+
+# Changed 20091209 gj
+if ( ( $in_usage > $crit_usage ) or ( $out_usage > $crit_usage ) or ( $if_status != 1 ) ) {
+ $state = "CRITICAL";
+}
+
+if ( ( $in_usage > $warn_usage )
+ or ( $out_usage > $warn_usage ) && $state eq "OK" )
+{
+ $state = "WARNING";
+}
+
+# Changed 20091209 gj
+$output = "$state - $output"
+ if ( $state ne "OK" );
+
+# Changed 20091214 gj - commas should have been semi colons
+$output .=
+"|inUsage=$in_usage%;$warn_usage;$crit_usage outUsage=$out_usage%;$warn_usage;$crit_usage"
+ . " inBandwidth=" . $in_traffic . $in_prefix . $suffix . " outBandwidth=" . $out_traffic . $out_prefix . $suffix
+ . " inAbsolut=$in_traffic_absolut outAbsolut=$out_traffic_absolut";
+
+stop($output, $state);
+
+
+sub fetch_Ip2IfIndex {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $host ) = @_;
+
+
+ # Determine if we have a host name or IP addr
+ if ( $host =~ /\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/ ){
+ #print "\nI found an IP address\n\n";
+ } else {
+ $host = get_ip ( $host );
+ #print "\nWe have a host name $host\n\n";
+ }
+
+ # Quit if results not found
+ if ( !defined( $response = $session->get_table($snmpIPAdEntIfIndex) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+
+ my %resp = %{$response};
+# foreach $key ( keys %{$response} ) {
+
+ if ( $index_list ){
+ print ("\nInterfaces found:\n");
+ print (" IP Addr\tIndex\n");
+ print ("------------------------\n");
+ }
+ # Check each returned value
+ foreach $key ( keys %resp ) {
+
+ if ( $index_list ){
+ my $index_addr = substr $key, 21;
+ print ($index_addr,"\t ",$resp{$key},"\n");
+ }
+
+ # Check for ip address mathcin in returned index results
+ if ( $key =~ /$host$/ ) {
+ $snmpkey = $resp{$key};
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $host \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+sub fetch_ifdescr {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $ifdescr ) = @_;
+
+ if ( !defined( $response = $session->get_table($snmpIfDescr) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+ foreach $key ( keys %{$response} ) {
+
+ # added 20070816 by oer: remove trailing 0 Byte for Windows :-(
+ my $resp=$response->{$key};
+ $resp =~ s/\x00//;
+
+
+ my $test = defined($use_reg)
+ ? $resp =~ /$ifdescr/
+ : $resp eq $ifdescr;
+
+ if ($test) {
+
+ ###if ( $resp =~ /^$ifdescr$/ ) {
+ ###if ( $resp =~ /$ifdescr/ ) {
+ ### print "$resp \n";
+ ###if ( $response->{$key} =~ /^$ifdescr$/ ) {
+
+ $key =~ /.*\.(\d+)$/;
+ $snmpkey = $1;
+
+ # print "$ifdescr = $key / $snmpkey \n"; #debug
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $ifdescr \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bits
+sub bits2bytes {
+ return unit2bytes(@_) / 8;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bytes
+sub unit2bytes {
+ my ( $value, $unit ) = @_;
+
+ if ( $unit eq "g" ) {
+ return $value * 1024 * 1024 * 1024;
+ }
+ elsif ( $unit eq "m" ) {
+ return $value * 1024 * 1024;
+ }
+ elsif ( $unit eq "k" ) {
+ return $value * 1024;
+ }
+ elsif ( $unit eq "b" ) {
+ return $value * 1;
+ }
+ else {
+ print "You have to supply a supported unit\n";
+ exit $STATUS_CODE{'UNKNOWN'};
+ }
+}
+
+#added 20050414 by mw
+#This function detects if an overflow occurs. If so, it returns
+#a computed value for $bytes.
+#If there is no counter overflow it simply returns the origin value of $bytes.
+#IF there is a Counter reboot wrap, just use previous output.
+sub counter_overflow {
+ my ( $bytes, $last_bytes, $max_bytes ) = @_;
+
+ $bytes += $max_bytes if ( $bytes < $last_bytes );
+ $bytes = $last_bytes if ( $bytes < $last_bytes );
+ return $bytes;
+}
+
+# Added 20100202 by gj
+# Print results and exit script
+sub stop {
+ my $result = shift;
+ my $exit_code = shift;
+ print $result . "\n";
+ exit ( $STATUS_CODE{$exit_code} );
+}
+
+# Added 20100405 by gj
+# Lookup hosts ip address
+sub get_ip {
+ use Net::DNS;
+
+ my ( $host_name ) = @_;
+
+ my $res = Net::DNS::Resolver->new;
+ my $query = $res->search($host_name);
+
+ if ($query) {
+ foreach my $rr ($query->answer) {
+ next unless $rr->type eq "A";
+ #print $rr->address, "\n";
+ return $rr->address;
+ }
+ } else {
+
+ stop("Error: IP address not resolved\n","UNKNOWN");
+ }
+}
+
+#cosmetic changes 20050614 by mw
+#Couldn't sustain "HERE";-), either.
+sub print_usage {
+ print <<EOU;
+ Usage: check_iftraffic3.pl -H host [ -C community_string ] [ -i if_index|if_descr ] [ -r ] [ -b if_max_speed_in | -I if_max_speed_in ] [ -O if_max_speed_out ] [ -u ] [ -B ] [ -A IP Address ] [ -L ] [ -M ] [ -w warn ] [ -c crit ]
+
+ Example 1: check_iftraffic3.pl -H host1 -C sneaky
+ Example 2: check_iftraffic3.pl -H host1 -C sneaky -i "Intel Pro" -r -B
+ Example 3: check_iftraffic3.pl -H host1 -C sneaky -i 5
+ Example 4: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 100 -u m
+ Example 5: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 20 -O 5 -u m
+ Example 6: check_iftraffic3.pl -H host1 -C sneaky -A 192.168.1.1 -B -b 100 -u m
+
+ Options:
+
+ -H, --host STRING or IPADDRESS
+ Check interface on the indicated host.
+ -B, --bits
+ Display results in bits per second b/s (default: Bytes/s)
+ -C, --community STRING
+ SNMP Community.
+ -r, --regexp
+ Use regexp to match NAME in description OID
+ -i, --interface STRING
+ Interface Name
+ -b, --bandwidth INTEGER
+ -I, --inBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ both IN and OUT if no second (-O) max speed is provided.
+ -O, --outBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ OUT traffic. Uses the same units value given for -b.
+ -u, --units STRING
+ g=gigabits/s,m=megabits/s,k=kilobits/s,b=bits/s. Required if -b, -I, or
+ -O are used.
+ -w, --warning INTEGER
+ % of bandwidth usage necessary to result in warning status (default: 85%)
+ -c, --critical INTEGER
+ % of bandwidth usage necessary to result in critical status (default: 98%)
+ -M, --max INTEGER
+ Max Counter Value of net devices in kilo/mega/giga/bytes.
+ -A, --address STRING (IP Address)
+ IP Address to use when determining the interface index to use. Can be
+ used when the index changes frequently or as in the case of Windows
+ servers the index is different depending on the NIC installed.
+ -L, --list FLAG (on/off)
+ Tell plugin to list available interfaces. This is not supported inside
+ of Nagios, but may be useful from the command line.
+EOU
+
+}
+
diff --git a/roles/icinga-fk/files/commands.cfg b/roles/icinga-fk/files/commands.cfg
new file mode 100644
index 0000000..1ceea2c
--- /dev/null
+++ b/roles/icinga-fk/files/commands.cfg
@@ -0,0 +1,90 @@
+###############################################################################
+# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
+###############################################################################
+
+
+################################################################################
+# NOTIFICATION COMMANDS
+################################################################################
+
+
+# 'notify-host-by-email' command definition
+define command{
+ command_name notify-host-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$
+ }
+
+# 'notify-service-by-email' command definition
+define command{
+ command_name notify-service-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$
+ }
+
+
+
+
+
+################################################################################
+# HOST CHECK COMMANDS
+################################################################################
+
+# On Debian, check-host-alive is being defined from within the
+# nagios-plugins-basic package
+define command{
+ command_name check_snmp_storage
+ command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -m $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_load
+ command_line $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -T $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_mem
+ command_line $USER1$/check_snmp_mem.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_int
+ command_line $USER1$/check_snmp_netint.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -a -m -k -M -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_iftraffic3
+ #command_name check_win_int
+ #command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$
+ #command_line $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -k -M -g -w $ARG4$ -c $ARG5$
+ command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$ -i $ARG2$ -w $ARG3$ -c $ARG4$
+}
+
+define command{
+ command_name check_snmp
+ command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
+}
+###############################
+##WINDOWS
+###############################
+
+define command{
+ command_name check_nt
+ command_line $USER1$/check_nt -H $HOSTADDRESS$ -s root -p 12489 -v $ARG1$ $ARG2$
+}
+
+################################################################################
+# PERFORMANCE DATA COMMANDS
+################################################################################
+
+
+# 'process-host-perfdata' command definition
+define command{
+ command_name process-host-perfdata
+ command_line /usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /var/lib/nagios3/host-perfdata.out
+ }
+
+
+# 'process-service-perfdata' command definition
+define command{
+ command_name process-service-perfdata
+ command_line /usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /var/lib/nagios3/service-perfdata.out
+ }
diff --git a/roles/icinga-fk/files/contacts_icinga.cfg b/roles/icinga-fk/files/contacts_icinga.cfg
new file mode 100644
index 0000000..8a66285
--- /dev/null
+++ b/roles/icinga-fk/files/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email icinga.ppe31@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-fk/files/dns.cfg b/roles/icinga-fk/files/dns.cfg
new file mode 100644
index 0000000..5b69aca
--- /dev/null
+++ b/roles/icinga-fk/files/dns.cfg
@@ -0,0 +1,11 @@
+# 'check_dns' command definition
+define command{
+ command_name check_dns
+ command_line /usr/lib/nagios/plugins/check_dns -H www.dfco.fr -s '$HOSTADDRESS$'
+}
+
+# 'check_dig' command definition
+define command{
+ command_name check_dig
+ command_line /usr/lib/nagios/plugins/check_dig -H '$HOSTADDRESS$' -l '$ARG1$'
+}
diff --git a/roles/icinga-fk/files/icinga.cfg b/roles/icinga-fk/files/icinga.cfg
new file mode 100644
index 0000000..fde1780
--- /dev/null
+++ b/roles/icinga-fk/files/icinga.cfg
@@ -0,0 +1,1494 @@
+##############################################################################
+#
+# ICINGA.CFG - Sample Main Config File for Icinga
+#
+# Read the documentation for more information on this configuration
+# file. I've provided some comments here, but things may not be so
+# clear without further explanation.
+#
+##############################################################################
+
+
+# LOG FILE
+# This is the main log file where service and host events are logged
+# for historical purposes. This should be the first option specified
+# in the config file!!!
+
+log_file=/var/log/icinga/icinga.log
+
+# Commands definitions
+cfg_file=/etc/icinga/commands.cfg
+
+# Debian also defaults to using the check commands defined by the debian
+# nagios-plugins package
+cfg_dir=/etc/nagios-plugins/config
+
+# OBJECT CONFIGURATION FILE(S)
+# These are the object configuration files in which you define hosts,
+# host groups, contacts, contact groups, services, etc.
+# Hint: Check the docs/wiki on how to monitor remote hosts with different
+# transport methods and plugins
+
+# Debian uses by default a configuration directory where icinga-common,
+# other packages and the local admin can dump or link configuration
+# files into.
+cfg_dir=/etc/icinga/objects/
+
+# Definitions for ido2db process checks
+#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg
+
+# Definitions for broker modules like idoutils.cfg
+cfg_dir=/etc/icinga/modules
+
+
+
+# OBJECT CACHE FILE
+# This option determines where object definitions are cached when
+# Icinga starts/restarts. The CGIs read object definitions from
+# this cache file (rather than looking at the object config files
+# directly) in order to prevent inconsistencies that can occur
+# when the config files are modified after Icinga starts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the objects cache file entirely.
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+# Tip: Use that file to debug your configuration with fully resolved
+# objects like the core sees them.
+
+object_cache_file=/var/cache/icinga/objects.cache
+
+
+
+# PRE-CACHED OBJECT FILE
+# This options determines the location of the precached object file.
+# If you run Icinga with the -p command line option, it will preprocess
+# your object configuration file(s) and write the cached config to this
+# file. You can then start Icinga with the -u option to have it read
+# object definitions from this precached file, rather than the standard
+# object configuration files (see the cfg_file and cfg_dir options above).
+# Using a precached object file can speed up the time needed to (re)start
+# the Icinga process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Icinga to find our more
+# about how this feature works.
+
+precached_object_file=/var/cache/icinga/objects.precache
+
+
+
+# RESOURCE FILE
+# This is an optional resource file that contains $USERx$ macro
+# definitions. Multiple resource files can be specified by using
+# multiple resource_file definitions. The CGIs will not attempt to
+# read the contents of resource files, so information that is
+# considered to be sensitive (usernames, passwords, etc) can be
+# defined as macros in this file and restrictive permissions (600)
+# can be placed on this file.
+
+resource_file=/etc/icinga/resource.cfg
+
+
+
+# STATUS FILE
+# This is where the current status of all monitored services and
+# hosts is stored. Its contents are read and processed by the CGIs.
+# The contents of the status file are deleted every time Icinga
+# restarts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the status file entirely. This becomes handy when using other methods
+# for data retrieval (e.g. IDOUtils DB)
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+
+status_file=/var/lib/icinga/status.dat
+
+
+
+# STATUS FILE UPDATE INTERVAL
+# This option determines the frequency (in seconds) that
+# Icinga will periodically dump program, host, and
+# service status data.
+# Increase the value, if you don't require it that often.
+
+#status_update_interval=30
+status_update_interval=10
+
+
+
+# ICINGA USER
+# This determines the effective user that Icinga should run as.
+# You can either supply a username or a UID.
+
+icinga_user=nagios
+
+
+
+# ICINGA GROUP
+# This determines the effective group that Icinga should run as.
+# You can either supply a group name or a GID.
+
+icinga_group=nagios
+
+
+
+# EXTERNAL COMMAND OPTION
+# This option allows you to specify whether or not Icinga should check
+# for external commands (in the command file defined below). By default
+# Icinga will *not* check for external commands, just to be on the
+# cautious side. If you want to be able to use the CGI command interface
+# you will have to enable this.
+# Values: 0 = disable commands, 1 = enable commands
+
+check_external_commands=1
+
+
+
+# EXTERNAL COMMAND CHECK INTERVAL
+# This is the interval at which Icinga should check for external commands.
+# This value works of the interval_length you specify later. If you leave
+# that at its default value of 60 (seconds), a value of 1 here will cause
+# Icinga to check for external commands every minute. If you specify a
+# number followed by an "s" (i.e. 15s), this will be interpreted to mean
+# actual seconds rather than a multiple of the interval_length variable.
+# Note: In addition to reading the external command file at regularly
+# scheduled intervals, Icinga will also check for external commands after
+# event handlers are executed.
+# NOTE: Setting this value to -1 causes Icinga to check the external
+# command file as often as possible.
+
+#command_check_interval=15s
+command_check_interval=-1
+
+
+
+# EXTERNAL COMMAND FILE
+# This is the file that Icinga checks for external command requests.
+# It is also where the command CGI will write commands that are submitted
+# by users, so it must be writeable by the user that the web server
+# is running as (usually 'nobody'). Permissions should be set at the
+# directory level instead of on the file, as the file is deleted every
+# time its contents are processed.
+# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
+# time to do it.
+
+command_file=/var/lib/icinga/rw/icinga.cmd
+
+
+
+# EXTERNAL COMMAND BUFFER SLOTS
+# This settings is used to tweak the number of items or "slots" that
+# the Icinga daemon should allocate to the buffer that holds incoming
+# external commands before they are processed. As external commands
+# are processed by the daemon, they are removed from the buffer.
+# Increase the value, if you are using addons like check_mk supplying
+# more external commands (passive check results) than usual.
+
+#external_command_buffer_slots=32768
+external_command_buffer_slots=4096
+
+
+
+# LOCK FILE
+# This is the lockfile that Icinga will use to store its PID number
+# in when it is running in daemon mode.
+
+lock_file=/var/run/icinga/icinga.pid
+
+
+
+# TEMP FILE
+# This is a temporary file that is used as scratch space when Icinga
+# updates the status log, cleans the comment file, etc. This file
+# is created, used, and deleted throughout the time that Icinga is
+# running.
+
+temp_file=/var/cache/icinga/icinga.tmp
+
+
+
+# TEMP PATH
+# This is path where Icinga can create temp files for service and
+# host check results, etc.
+
+temp_path=/tmp
+
+
+
+# EVENT BROKER OPTIONS
+# Controls what (if any) data gets sent to the event broker.
+# Values: 0 = Broker nothing
+# -1 = Broker everything
+# <other> = See documentation
+
+event_broker_options=-1
+
+
+
+# EVENT BROKER MODULE(S)
+# ----> use the new *module definition* instead:
+# ----> http://docs.icinga.org/latest/en/objectdefinitions.html
+#
+# Example definitions can be found in the '/etc/icinga/modules/' directory.
+# If you want to enable idoutils in Debian install icinga-idoutils and copy
+# /usr/share/doc/icinga-idoutils/examples/idoutils.cfg-sample to
+# /etc/icinga/modules/idoutils.cfg.
+# Don't forget to also enable the daemon in /etc/default/icinga
+
+# LOG ROTATION METHOD
+# This is the log rotation method that Icinga should use to rotate
+# the main log file. Values are as follows..
+# n = None - don't rotate the log
+# h = Hourly rotation (top of the hour)
+# d = Daily rotation (midnight every day)
+# w = Weekly rotation (midnight on Saturday evening)
+# m = Monthly rotation (midnight last day of month)
+
+log_rotation_method=d
+
+
+
+# LOG ARCHIVE PATH
+# This is the directory where archived (rotated) log files should be
+# placed (assuming you've chosen to do log rotation).
+
+log_archive_path=/var/log/icinga/archives
+
+
+
+# LOGGING OPTIONS FOR DAEMON
+# If you want messages logged to the daemon log file (usually icinga.log).
+# Default option is 1 (yes), the other valid option is 0 (no)
+
+use_daemon_log=1
+
+
+
+# LOGGING OPTIONS FOR SYSLOG
+# If you want messages logged to the syslog facility, as well as the
+# Icinga log file set this option to 1. If not, set it to 0.
+
+use_syslog=1
+
+
+
+# SYSLOG FACILITY
+# If you enabled use_syslog you can set icinga to use a local facility
+# instead of the default.To enable set this option to 1, if not, set it to 0.
+
+use_syslog_local_facility=0
+
+
+
+# SYSLOG LOCAL FACILITY
+# If you specified the use_syslog_local_facility you can chose which
+# local facility to use. Valid values are from 0 to 7
+
+syslog_local_facility=5
+
+
+
+# NOTIFICATION LOGGING OPTION
+# If you don't want notifications to be logged, set this value to 0.
+# If notifications should be logged, set the value to 1.
+
+log_notifications=1
+
+
+
+# SERVICE RETRY LOGGING OPTION
+# If you don't want service check retries to be logged, set this value
+# to 0. If retries should be logged, set the value to 1.
+
+log_service_retries=1
+
+
+
+# HOST RETRY LOGGING OPTION
+# If you don't want host check retries to be logged, set this value to
+# 0. If retries should be logged, set the value to 1.
+
+log_host_retries=1
+
+
+
+# EVENT HANDLER LOGGING OPTION
+# If you don't want host and service event handlers to be logged, set
+# this value to 0. If event handlers should be logged, set the value
+# to 1.
+
+log_event_handlers=1
+
+
+
+# INITIAL STATES LOGGING OPTION
+# If you want Icinga to log all initial host and service states to
+# the main log file (the first time the service or host is checked)
+# you can enable this option by setting this value to 1. If you
+# are not using an external application that does long term state
+# statistics reporting, you do not need to enable this option. In
+# this case, set the value to 0.
+
+log_initial_states=0
+
+
+
+# CURRENT STATES LOGGING OPTION
+# If you don't want Icinga to log all current host and service states
+# after log has been rotated to the main log file, you can disable this
+# option by setting this value to 0. Default value is 1.
+
+log_current_states=1
+
+
+
+# EXTERNAL COMMANDS LOGGING OPTION
+# If you don't want Icinga to log external commands, set this value
+# to 0. If external commands should be logged, set this value to 1.
+# Note: This option does not include logging of passive service
+# checks - see the option below for controlling whether or not
+# passive checks are logged.
+
+log_external_commands=1
+
+
+
+# LOG ANONYMIZED EXTERNAL COMMAND AUTHOR !!EXPERIMENTAL!!
+# This option substitutes the user name on external commands with
+# the string "<anon>" if the command gets logged. It is
+# anonymized in log files only. This option was added to make
+# icinga compliant with data retention laws on various countries.
+# This option is disabled by default.
+
+log_anonymized_external_command_author=0
+
+
+
+# PASSIVE CHECKS LOGGING OPTION
+# If you don't want Icinga to log passive host and service checks, set
+# this value to 0. If passive checks should be logged, set
+# this value to 1.
+
+log_passive_checks=1
+
+
+
+# LONG PLUGIN OUTPUT LOGGING OPTION
+# If you want Icinga to log the complete text of the plugin output
+# to the log instead of only the first line then set this value to 1.
+# Default value is 0.
+
+log_long_plugin_output=0
+
+
+
+# GLOBAL HOST AND SERVICE EVENT HANDLERS
+# These options allow you to specify a host and service event handler
+# command that is to be run for every host or service state change.
+# The global event handler is executed immediately prior to the event
+# handler that you have optionally specified in each host or
+# service definition. The command argument is the short name of a
+# command definition that you define in your host configuration file.
+# Read the HTML docs for more information.
+
+#global_host_event_handler=somecommand
+#global_service_event_handler=somecommand
+
+
+
+# SERVICE INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" service checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all service checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)! This is not a
+# good thing for production, but is useful when testing the
+# parallelization functionality.
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+service_inter_check_delay_method=s
+
+
+
+# MAXIMUM SERVICE CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all services should
+# be completed. Default is 30 minutes.
+
+max_service_check_spread=30
+
+
+
+# SERVICE CHECK INTERLEAVE FACTOR
+# This variable determines how service checks are interleaved.
+# Interleaving the service checks allows for a more even
+# distribution of service checks and reduced load on remote
+# hosts. Setting this value to 1 is equivalent to how versions
+# of Icinga previous to 0.0.5 did service checks. Set this
+# value to s (smart) for automatic calculation of the interleave
+# factor unless you have a specific reason to change it.
+# s = Use "smart" interleave factor calculation
+# x = Use an interleave factor of x, where x is a
+# number greater than or equal to 1.
+
+service_interleave_factor=s
+
+
+
+# HOST INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" host checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all host checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)!
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+host_inter_check_delay_method=s
+
+
+
+# MAXIMUM HOST CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all hosts should
+# be completed. Default is 30 minutes.
+
+max_host_check_spread=30
+
+
+
+# MAXIMUM CONCURRENT SERVICE CHECKS
+# This option allows you to specify the maximum number of
+# service checks that can be run in parallel at any given time.
+# Specifying a value of 1 for this variable essentially prevents
+# any service checks from being parallelized. A value of 0
+# will not restrict the number of concurrent checks that are
+# being executed.
+
+max_concurrent_checks=0
+
+
+
+# HOST AND SERVICE CHECK REAPER FREQUENCY
+# This is the frequency (in seconds!) that Icinga will process
+# the results of host and service checks.
+# Lower this value in larger environments to allow faster
+# check result processing (requires more cpu power).
+
+#check_result_reaper_frequency=1
+check_result_reaper_frequency=10
+
+
+
+
+# MAX CHECK RESULT REAPER TIME
+# This is the max amount of time (in seconds) that a single
+# check result reaper event will be allowed to run before
+# returning control back to Icinga so it can perform other
+# duties.
+
+max_check_result_reaper_time=30
+
+
+
+
+# CHECK RESULT PATH
+# This is directory where Icinga stores the results of host and
+# service checks that have not yet been processed.
+#
+# Note: Make sure that only one instance of Icinga has access
+# to this directory!
+
+check_result_path=/var/lib/icinga/spool/checkresults
+
+
+
+
+# MAX CHECK RESULT FILE AGE
+# This option determines the maximum age (in seconds) which check
+# result files are considered to be valid. Files older than this
+# threshold will be mercilessly deleted without further processing.
+
+max_check_result_file_age=3600
+
+
+
+
+# MAX CHECK RESULT LIST ITEMS !!EXPERIMENTAL!!
+# This experimental option allows you to set the max number of items
+# the checkresult reaper will put onto the checkresult list for further
+# processing by the core. If there are too many, the reaping will be
+# terminated early, allowing the core to process the results sooner.
+# On larger setups, that list might grow too much, and decrease
+# performance on processing. You might experiment with that value, the
+# inner core default is set to 0, disabling that feature.
+# Values:
+# 0 = Disable max check result list items
+# number = set max check result list items
+
+#max_check_result_list_items=1024
+
+
+
+
+# CACHED HOST CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous host check is considered current.
+# Cached host states (from host checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to the host check logic.
+# Too high of a value for this option may result in inaccurate host
+# states being used by Icinga, while a lower value may result in a
+# performance hit for host checks. Use a value of 0 to disable host
+# check caching.
+
+cached_host_check_horizon=15
+
+
+
+# CACHED SERVICE CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous service check is considered current.
+# Cached service states (from service checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to predictive dependency checks.
+# Use a value of 0 to disable service check caching.
+
+cached_service_check_horizon=15
+
+
+
+# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of hosts when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# host dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_host_dependency_checks=1
+
+
+
+# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of service when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# service dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_service_dependency_checks=1
+
+
+
+# SOFT STATE DEPENDENCIES
+# This option determines whether or not Icinga will use soft state
+# information when checking host and service dependencies. Normally
+# Icinga will only use the latest hard host or service state when
+# checking dependencies. If you want it to use the latest state (regardless
+# of whether its a soft or hard state type), enable this option.
+# Values:
+# 0 = Don't use soft state dependencies (default)
+# 1 = Use soft state dependencies
+
+soft_state_dependencies=0
+
+
+
+# TIME CHANGE ADJUSTMENT THRESHOLDS
+# These options determine when Icinga will react to detected changes
+# in system time (forward into the future).
+
+#time_change_threshold=900
+
+
+
+# AUTO-RESCHEDULING OPTION
+# This option determines whether or not Icinga will attempt to
+# automatically reschedule active host and service checks to
+# "smooth" them out over time. This can help balance the load on
+# the monitoring server.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_reschedule_checks=0
+
+
+
+# AUTO-RESCHEDULING INTERVAL
+# This option determines how often (in seconds) Icinga will
+# attempt to automatically reschedule checks. This option only
+# has an effect if the auto_reschedule_checks option is enabled.
+# Default is 30 seconds.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_interval=30
+
+
+
+# AUTO-RESCHEDULING WINDOW
+# This option determines the "window" of time (in seconds) that
+# Icinga will look at when automatically rescheduling checks.
+# Only host and service checks that occur in the next X seconds
+# (determined by this variable) will be rescheduled. This option
+# only has an effect if the auto_reschedule_checks option is
+# enabled. Default is 180 seconds (3 minutes).
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_window=180
+
+
+
+# SLEEP TIME
+# This is the number of seconds to sleep between checking for system
+# events and service checks that need to be run.
+
+sleep_time=0.25
+
+
+
+# TIMEOUT VALUES
+# These options control how much time Icinga will allow various
+# types of commands to execute before killing them off. Options
+# are available for controlling maximum time allotted for
+# service checks, host checks, event handlers, notifications, the
+# ocsp command, and performance data commands. All values are in
+# seconds.
+# Increase the timeout values in case you are experiencing a lot
+# of check timeouts. Addons like e.g. check_mk will perform
+# one combined active servicecheck which could take longer than
+# the default of 60sec.
+
+#service_check_timeout=120
+service_check_timeout=60
+host_check_timeout=30
+event_handler_timeout=30
+notification_timeout=30
+ocsp_timeout=5
+perfdata_timeout=5
+
+
+
+# RETAIN STATE INFORMATION
+# This setting determines whether or not Icinga will save state
+# information for services and hosts before it shuts down. Upon
+# startup Icinga will reload all saved service and host state
+# information before starting to monitor. This is useful for
+# maintaining long-term data on state statistics, etc, but will
+# slow Icinga down a bit when it (re)starts. Since its only
+# a one-time penalty, I think its well worth the additional
+# startup delay.
+
+retain_state_information=1
+
+
+
+# STATE RETENTION FILE
+# This is the file that Icinga should use to store host and
+# service state information before it shuts down. The state
+# information in this file is also read immediately prior to
+# starting to monitor the network when Icinga is restarted.
+# This file is used only if the retain_state_information
+# variable is set to 1.
+
+state_retention_file=/var/cache/icinga/retention.dat
+
+
+
+# SYNC FILE
+# This is an advanced facility to pass a subset of retention
+# information into Icinga on a running system. This is similar
+# to the state retention file with the following difference:
+#
+# - if the last_check value is less than the current last_check,
+# then the state information is ignored (this must be specified
+# immediately after the object identifiers)
+#
+# - downtimes and comments are not identified by an id number, but
+# by other "similar characteristics". This is required to work in
+# a distributed Nagios environment
+# * downtimes: hostname, servicename (if appropriate), author,
+# comment, start_time, end_time, fixed, duration
+# * comments: hostname, servicename, author, comment
+#
+# If this variable is set, then on Icinga startup, the sync file
+# will be read after the retention file has been processed. If the
+# file is read successfully, it will be removed.
+# If the file does not exist, no error will appear.
+# There is also an API that will force a read of the sync file.
+
+#sync_retention_file=/var/cache/icinga/sync.dat
+
+
+
+# RETENTION DATA UPDATE INTERVAL
+# This setting determines how often (in minutes) that Icinga
+# will automatically save retention data during normal operation.
+# If you set this value to 0, Icinga will not save retention
+# data at regular interval, but it will still save retention
+# data before shutting down or restarting. If you have disabled
+# state retention, this option has no effect.
+
+retention_update_interval=60
+
+
+
+# USE RETAINED PROGRAM STATE
+# This setting determines whether or not Icinga will set
+# program status variables based on the values saved in the
+# retention file. If you want to use retained program status
+# information, set this value to 1. If not, set this value
+# to 0.
+
+use_retained_program_state=1
+
+
+# DUMP RETAINED HOST SERVICE STATES TO NEB
+# This setting determines wether or not Icinga will dump host
+# and service states based on the values saved in the retention
+# file to the neb modules. It will already do that on event loop
+# initialization.
+# Changed in Icinga 1.10 to disabled - re-enable if you require it.
+
+dump_retained_host_service_states_to_neb=0
+
+
+
+# USE RETAINED SCHEDULING INFO
+# This setting determines whether or not Icinga will retain
+# the scheduling info (next check time) for hosts and services
+# based on the values saved in the retention file. If you
+# If you want to use retained scheduling info, set this
+# value to 1. If not, set this value to 0.
+
+use_retained_scheduling_info=1
+
+
+
+# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
+# The following variables are used to specify specific host and
+# service attributes that should *not* be retained by Icinga during
+# program restarts.
+#
+# The values of the masks are bitwise ANDs of values specified
+# by the "MODATTR_" definitions found in include/common.h.
+# For example, if you do not want the current enabled/disabled state
+# of flap detection and event handlers for hosts to be retained, you
+# would use a value of 24 for the host attribute mask...
+# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
+
+# This mask determines what host attributes are not retained
+retained_host_attribute_mask=0
+
+# This mask determines what service attributes are not retained
+retained_service_attribute_mask=0
+
+# These two masks determine what process attributes are not retained.
+# There are two masks, because some process attributes have host and service
+# options. For example, you can disable active host checks, but leave active
+# service checks enabled.
+retained_process_host_attribute_mask=0
+retained_process_service_attribute_mask=0
+
+# These two masks determine what contact attributes are not retained.
+# There are two masks, because some contact attributes have host and
+# service options. For example, you can disable host notifications for
+# a contact, but leave service notifications enabled for them.
+retained_contact_host_attribute_mask=0
+retained_contact_service_attribute_mask=0
+
+
+
+# INTERVAL LENGTH
+# This is the seconds per unit interval as used in the
+# host/contact/service configuration files. Setting this to 60 means
+# that each interval is one minute long (60 seconds). Other settings
+# have not been tested much, so your mileage is likely to vary...
+
+interval_length=60
+
+
+
+# AGGRESSIVE HOST CHECKING OPTION
+# If you don't want to turn on aggressive host checking features, set
+# this value to 0 (the default). Otherwise set this value to 1 to
+# enable the aggressive check option. Read the docs for more info
+# on what aggressive host check is or check out the source code in
+# base/checks.c
+
+use_aggressive_host_checking=0
+
+
+
+# SERVICE CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# service checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of service checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_service_checks=1
+
+
+
+# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# service checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_service_checks=1
+
+
+
+# HOST CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# host checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of host checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_host_checks=1
+
+
+
+# PASSIVE HOST CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# host checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_host_checks=1
+
+
+
+# NOTIFICATIONS OPTION
+# This determines whether or not Icinga will sent out any host or
+# service notifications when it is initially (re)started.
+# Values: 1 = enable notifications, 0 = disable notifications
+
+enable_notifications=1
+
+
+
+# EVENT HANDLER USE OPTION
+# This determines whether or not Icinga will run any host or
+# service event handlers when it is initially (re)started. Unless
+# you're implementing redundant hosts, leave this option enabled.
+# Values: 1 = enable event handlers, 0 = disable event handlers
+
+enable_event_handlers=1
+
+
+
+# STATE BASED ESCALATION RANGES !!!Experimental!!!
+# This option allows you to enable state based escalation ranges which
+# will allow a more detailed granularity on when an escalation notification
+# may happen, adding a filter based on the current host or service state
+# when checking the escalation for notification viability.
+# This is a behavioural change to the default, and therefore intentionally
+# disabled. Enable at your own risk, as this remains an experimental feature.
+# Values: 1 = enable state based escalation ranges,
+# 0 = disable state based escalation ranges
+
+#enable_state_based_escalation_ranges=0
+
+
+
+# PROCESS PERFORMANCE DATA OPTION
+# This determines whether or not Icinga will process performance
+# data returned from service and host checks. If this option is
+# enabled, host performance data will be processed using the
+# host_perfdata_command (defined below) and service performance
+# data will be processed using the service_perfdata_command (also
+# defined below). Read the HTML docs for more information on
+# performance data.
+# Values: 1 = process performance data, 0 = do not process performance data
+
+process_performance_data=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
+# These commands are run after every host and service check is
+# performed. These commands are executed only if the
+# process_performance_data option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on performance data.
+
+#host_perfdata_command=process-host-perfdata
+#service_perfdata_command=process-service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILES
+# These files are used to store host and service performance data.
+# Performance data is only written to these files if the
+# process_performance_data option (above) is set to 1.
+
+#host_perfdata_file=/tmp/host-perfdata
+#service_perfdata_file=/tmp/service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
+# These options determine what data is written (and how) to the
+# performance data files. The templates may contain macros, special
+# characters (\t for tab, \r for carriage return, \n for newline)
+# and plain text. A newline is automatically added after each write
+# to the performance data file. Some examples of what you can do are
+# shown below.
+
+#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
+#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE MODES
+# This option determines whether or not the host and service
+# performance data files are opened in write ("w") or append ("a")
+# mode. If you want to use named pipes, you should use the special
+# pipe ("p") mode which avoid blocking at startup, otherwise you will
+# likely want the defult append ("a") mode.
+
+#host_perfdata_file_mode=a
+#service_perfdata_file_mode=a
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
+# These options determine how often (in seconds) the host and service
+# performance data files are processed using the commands defined
+# below. A value of 0 indicates the files should not be periodically
+# processed.
+
+#host_perfdata_file_processing_interval=0
+#service_perfdata_file_processing_interval=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
+# These commands are used to periodically process the host and
+# service performance data files. The interval at which the
+# processing occurs is determined by the options above.
+
+#host_perfdata_file_processing_command=process-host-perfdata-file
+#service_perfdata_file_processing_command=process-service-perfdata-file
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
+# THese options determine wether the core will process empty perfdata
+# results or not. This is needed for distributed monitoring, and intentionally
+# turned on by default.
+# If you don't require empty perfdata - saving some cpu cycles
+# on unwanted macro calculation - you can turn that off. Be careful!
+# Values: 1 = enable, 0 = disable
+
+#host_perfdata_process_empty_results=1
+#service_perfdata_process_empty_results=1
+
+
+
+# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
+# This boolean option determines whether services assigned to empty
+# host groups (host groups with no host members) will cause Icinga to
+# exit with error on start up (or during a configuration check) or not.
+# It's useful to be able to assign services to empty hostgroups when
+# configuration files or pre-cached object files are distributed to
+# various pollers, or when the process of generating Icinga config is
+# automated, or when a set of services is slowly being phased out but
+# should be kept around.
+# The default behavior if the option is not present in the main
+# configuration file is for Icinga to exit with error if services are
+# associated with host groups that have no hosts associated with them.
+
+#allow_empty_hostgroup_assignment=0
+
+
+
+# OBSESS OVER SERVICE CHECKS OPTION
+# This determines whether or not Icinga will obsess over service
+# checks and run the ocsp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over services, 0 = do not obsess (default)
+
+obsess_over_services=0
+
+
+
+# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
+# This is the command that is run for every service check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_services option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ocsp_command=somecommand
+
+
+
+# OBSESS OVER HOST CHECKS OPTION
+# This determines whether or not Icinga will obsess over host
+# checks and run the ochp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over hosts, 0 = do not obsess (default)
+
+obsess_over_hosts=0
+
+
+
+# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
+# This is the command that is run for every host check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_hosts option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ochp_command=somecommand
+
+
+
+# TRANSLATE PASSIVE HOST CHECKS OPTION
+# This determines whether or not Icinga will translate
+# DOWN/UNREACHABLE passive host check results into their proper
+# state for this instance of Icinga. This option is useful
+# if you have distributed or failover monitoring setup. In
+# these cases your other Icinga servers probably have a different
+# "view" of the network, with regards to the parent/child relationship
+# of hosts. If a distributed monitoring server thinks a host
+# is DOWN, it may actually be UNREACHABLE from the point of
+# this Icinga instance. Enabling this option will tell Icinga
+# to translate any DOWN or UNREACHABLE host states it receives
+# passively into the correct state from the view of this server.
+# Values: 1 = perform translation, 0 = do not translate (default)
+
+translate_passive_host_checks=0
+
+
+
+# PASSIVE HOST CHECKS ARE SOFT OPTION
+# This determines whether or not Icinga will treat passive host
+# checks as being HARD or SOFT. By default, a passive host check
+# result will put a host into a HARD state type. This can be changed
+# by enabling this option.
+# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
+
+passive_host_checks_are_soft=0
+
+
+
+# ORPHANED HOST/SERVICE CHECK OPTIONS
+# These options determine whether or not Icinga will periodically
+# check for orphaned host service checks. Since service checks are
+# not rescheduled until the results of their previous execution
+# instance are processed, there exists a possibility that some
+# checks may never get rescheduled. A similar situation exists for
+# host checks, although the exact scheduling details differ a bit
+# from service checks. Orphaned checks seem to be a rare
+# problem and should not happen under normal circumstances.
+# If you have problems with service checks never getting
+# rescheduled, make sure you have orphaned service checks enabled.
+# Values: 1 = enable checks, 0 = disable checks
+
+check_for_orphaned_services=1
+check_for_orphaned_hosts=1
+
+
+
+# SERVICE CHECK TIMEOUT STATE
+# This setting determines the state Icinga will report when a
+# service check times out meaning it does not respond within
+# service_check_timeout seconds. The default is set to Unknown
+# and not Critical.
+# Valid settings are:
+# c - Critical
+# u - Unknown (default)
+# w - Warning
+# o - OK
+
+service_check_timeout_state=u
+
+
+
+# SERVICE FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of service results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_service_freshness=1
+
+
+
+# SERVICE FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of service check results. If you have
+# disabled service freshness checking, this option has no effect.
+
+service_freshness_check_interval=60
+
+
+
+# HOST FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of host results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_host_freshness=0
+
+
+
+# HOST FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of host check results. If you have
+# disabled host freshness checking, this option has no effect.
+
+host_freshness_check_interval=60
+
+
+
+
+# ADDITIONAL FRESHNESS THRESHOLD LATENCY
+# This setting determines the number of seconds that Icinga
+# will add to any host and service freshness thresholds that
+# it calculates (those not explicitly specified by the user).
+
+additional_freshness_latency=15
+
+
+
+
+# FLAP DETECTION OPTION
+# This option determines whether or not Icinga will try
+# and detect hosts and services that are "flapping".
+# Flapping occurs when a host or service changes between
+# states too frequently. When Icinga detects that a
+# host or service is flapping, it will temporarily suppress
+# notifications for that host/service until it stops
+# flapping. Flap detection is very experimental, so read
+# the HTML documentation before enabling this feature!
+# Values: 1 = enable flap detection
+# 0 = disable flap detection (default)
+
+enable_flap_detection=1
+
+
+
+# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
+# Read the HTML documentation on flap detection for
+# an explanation of what this option does. This option
+# has no effect if flap detection is disabled.
+
+low_service_flap_threshold=5.0
+high_service_flap_threshold=20.0
+low_host_flap_threshold=5.0
+high_host_flap_threshold=20.0
+
+
+
+# DATE FORMAT OPTION
+# This option determines how short dates are displayed. Valid options
+# include:
+# us (MM-DD-YYYY HH:MM:SS)
+# euro (DD-MM-YYYY HH:MM:SS)
+# iso8601 (YYYY-MM-DD HH:MM:SS)
+# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
+#
+
+date_format=iso8601
+
+
+
+
+# TIMEZONE OFFSET
+# This option is used to override the default timezone that this
+# instance of Icinga runs in. If not specified, Icinga will use
+# the system configured timezone.
+#
+# NOTE: In order to display the correct timezone in the CGIs, you
+# will also need to alter the Apache directives for the CGI path
+# to include your timezone. Example:
+#
+# <Directory "/usr/local/icinga/sbin/">
+# SetEnv TZ "Australia/Brisbane"
+# ...
+# </Directory>
+
+#use_timezone=US/Mountain
+#use_timezone=Australia/Brisbane
+
+
+
+
+# P1.PL FILE LOCATION
+# This value determines where the p1.pl perl script (used by the
+# embedded Perl interpreter) is located. If you didn't compile
+# Icinga with embedded Perl support, this option has no effect.
+
+p1_file=/usr/lib/icinga/p1.pl
+
+
+
+# EMBEDDED PERL INTERPRETER OPTION
+# This option determines whether or not the embedded Perl interpreter
+# will be enabled during runtime. This option has no effect if Icinga
+# has not been compiled with support for embedded Perl.
+# This option is intentionally disabled by default, because embedded
+# perl can cause memory leaks and make Icinga unstable if not properly
+# used.
+# Only enable this setting when you really know what you are doing!
+# Values: 0 = disable interpreter, 1 = enable interpreter
+
+enable_embedded_perl=1
+
+
+
+# EMBEDDED PERL USAGE OPTION
+# This option determines whether or not Icinga will process Perl plugins
+# and scripts with the embedded Perl interpreter if the plugins/scripts
+# do not explicitly indicate whether or not it is okay to do so. Read
+# the HTML documentation on the embedded Perl interpreter for more
+# information on how this option works.
+
+use_embedded_perl_implicitly=1
+
+
+
+# EVENT HANDLERS FOR STALKED HOSTS/SERVICES
+# Allow running event handlers for stalked hosts/services in order
+# to forward to external systems.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_event_handlers_for_hosts=0
+stalking_event_handlers_for_services=0
+
+
+
+# NOTIFICATIONS FOR STALKED HOSTS/SERVICES
+# Allow notifications for stalked hosts/services globally
+# for all contacts in order to notify about a stalking
+# alert.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_notifications_for_hosts=0
+stalking_notifications_for_services=0
+
+
+
+# ILLEGAL OBJECT NAME CHARACTERS
+# This option allows you to specify illegal characters that cannot
+# be used in host names, service descriptions, or names of other
+# object types.
+
+illegal_object_name_chars=`~!$%^&*|'"<>?,()=
+
+
+
+# ILLEGAL MACRO OUTPUT CHARACTERS
+# This option allows you to specify illegal characters that are
+# stripped from macros before being used in notifications, event
+# handlers, etc. This DOES NOT affect macros used in service or
+# host check commands.
+# The following macros are stripped of the characters you specify:
+# $HOSTOUTPUT$
+# $HOSTPERFDATA$
+# $HOSTACKAUTHOR$
+# $HOSTACKCOMMENT$
+# $SERVICEOUTPUT$
+# $SERVICEPERFDATA$
+# $SERVICEACKAUTHOR$
+# $SERVICEACKCOMMENT$
+
+illegal_macro_output_chars=`~$&|'"<>
+
+
+
+# KEEP UNKNOWN MACROS
+# This option can be used to keep unknown macros within the output.
+# e.g. check_proc -C $foo$ will remain.
+# This was the default in versions older than Icinga 1.8, but now
+# the default is to remove those macros from the output, causing
+# the shell to interpret $foo and leaving a single $ there. See
+# #2291 for further information.
+# Make sure to escape single dollar signs with another '$', as the
+# docs describe. Other than that, enable this setting to revert to
+# the old behaviour.
+
+keep_unknown_macros=1
+
+
+
+# REGULAR EXPRESSION MATCHING
+# This option controls whether or not regular expression matching
+# takes place in the object config files. Regular expression
+# matching is used to match host, hostgroup, service, and service
+# group names/descriptions in some fields of various object types.
+# Values: 1 = enable regexp matching, 0 = disable regexp matching
+
+use_regexp_matching=0
+
+
+
+# "TRUE" REGULAR EXPRESSION MATCHING
+# This option controls whether or not "true" regular expression
+# matching takes place in the object config files. This option
+# only has an effect if regular expression matching is enabled
+# (see above). If this option is DISABLED, regular expression
+# matching only occurs if a string contains wildcard characters
+# (* and ?). If the option is ENABLED, regexp matching occurs
+# all the time (which can be annoying).
+# Values: 1 = enable true matching, 0 = disable true matching
+
+use_true_regexp_matching=0
+
+
+
+# ADMINISTRATOR EMAIL/PAGER ADDRESSES
+# The email and pager address of a global administrator (likely you).
+# Icinga never uses these values itself, but you can access them by
+# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
+# commands.
+
+admin_email=root@localhost
+admin_pager=pageroot@localhost
+
+
+
+# DAEMON CORE DUMP OPTION
+# This option determines whether or not Icinga is allowed to create
+# a core dump when it runs as a daemon. Note that it is generally
+# considered bad form to allow this, but it may be useful for
+# debugging purposes. Enabling this option doesn't guarantee that
+# a core file will be produced, but that's just life...
+# Values: 1 - Allow core dumps
+# 0 - Do not allow core dumps (default)
+
+daemon_dumps_core=0
+
+
+
+# LARGE INSTALLATION TWEAKS OPTION
+# This option determines whether or not Icinga will take some shortcuts
+# which can save on memory and CPU usage in large Icinga installations.
+# Read the documentation for more information on the benefits/tradeoffs
+# of enabling this option.
+# Values: 1 - Enabled tweaks
+# 0 - Disable tweaks (default)
+
+use_large_installation_tweaks=0
+
+
+
+# ENABLE ENVIRONMENT MACROS
+# This option determines whether or not Icinga will make all standard
+# macros available as environment variables when host/service checks
+# and system commands (event handlers, notifications, etc.) are
+# executed. Enabling this option can cause performance issues in
+# large installations, as it will consume a bit more memory and (more
+# importantly) consume more CPU.
+# Keep in mind that various addons/plugins will require this setting
+# to be enabled (e.g. check_oracle_health) for special usage.
+# Values: 1 - Enable environment variable macros
+# 0 - Disable environment variable macros (default)
+
+enable_environment_macros=1
+
+
+
+# CHILD PROCESS MEMORY OPTION
+# This option determines whether or not Icinga will free memory in
+# child processes (processed used to execute system commands and host/
+# service checks). If you specify a value here, it will override
+# program defaults.
+# Value: 1 - Free memory in child processes
+# 0 - Do not free memory in child processes
+
+#free_child_process_memory=1
+
+
+
+# CHILD PROCESS FORKING BEHAVIOR
+# This option determines how Icinga will fork child processes
+# (used to execute system commands and host/service checks). Normally
+# child processes are fork()ed twice, which provides a very high level
+# of isolation from problems. Fork()ing once is probably enough and will
+# save a great deal on CPU usage (in large installs), so you might
+# want to consider using this. If you specify a value here, it will
+# program defaults.
+# Value: 1 - Child processes fork() twice
+# 0 - Child processes fork() just once
+
+#child_processes_fork_twice=1
+
+
+
+# DEBUG LEVEL
+# This option determines how much (if any) debugging information will
+# be written to the debug file. OR values together to log multiple
+# types of information.
+# Values:
+# -1 = Everything
+# 0 = Nothing
+# 1 = Functions
+# 2 = Configuration
+# 4 = Process information
+# 8 = Scheduled events
+# 16 = Host/service checks
+# 32 = Notifications
+# 64 = Event broker
+# 128 = External commands
+# 256 = Commands
+# 512 = Scheduled downtime
+# 1024 = Comments
+# 2048 = Macros
+
+debug_level=0
+
+
+
+# DEBUG VERBOSITY
+# This option determines how verbose the debug log out will be.
+# Values: 0 = Brief output
+# 1 = More detailed
+# 2 = Very detailed
+
+debug_verbosity=2
+
+
+
+# DEBUG FILE
+# This option determines where Icinga should write debugging information.
+
+debug_file=/var/log/icinga/icinga.debug
+
+
+
+# MAX DEBUG FILE SIZE
+# This option determines the maximum size (in bytes) of the debug file. If
+# the file grows larger than this size, it will be renamed with a .old
+# extension. If a file already exists with a .old extension it will
+# automatically be deleted. This helps ensure your disk space usage doesn't
+# get out of control when debugging Icinga.
+
+# 100M
+max_debug_file_size=100000000
diff --git a/roles/icinga-fk/files/icinga.conf b/roles/icinga-fk/files/icinga.conf
new file mode 100644
index 0000000..e19a486
--- /dev/null
+++ b/roles/icinga-fk/files/icinga.conf
@@ -0,0 +1,27 @@
+# apache configuration for icinga
+
+ScriptAlias /cgi-bin/icinga /usr/lib/cgi-bin/icinga
+
+# Where the stylesheets (config files) reside
+Alias /icinga/stylesheets /etc/icinga/stylesheets
+
+# Where the HTML pages live
+Alias /icinga /usr/share/icinga/htdocs
+
+<DirectoryMatch "^(?:/usr/share/icinga/htdocs|/usr/lib/cgi-bin/icinga|/etc/icinga/stylesheets)/">
+ Options FollowSymLinks
+
+ DirectoryIndex index.html
+
+ AllowOverride AuthConfig
+# Require all granted
+
+ AuthName "Icinga Access"
+ AuthType Basic
+ AuthUserFile /etc/icinga/htpasswd.users
+ Require valid-user
+</DirectoryMatch>
+
+<Directory "/usr/share/javascript/">
+ Options FollowSymLinks MultiViews
+</Directory>
diff --git a/roles/icinga-fk/files/nt.cfg b/roles/icinga-fk/files/nt.cfg
new file mode 100644
index 0000000..fcae576
--- /dev/null
+++ b/roles/icinga-fk/files/nt.cfg
@@ -0,0 +1,15 @@
+# If you are confused about this command definition, cause you was
+# reading other suggestions, please have a look into
+# /usr/share/doc/monitoring-plugins/README.Debian
+
+# 'check_nt' command definition
+#define command {
+# command_name check_nt
+# command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -v '$ARG1$'
+#}
+
+# 'check_nscp' command definition
+define command {
+ command_name check_nscp
+ command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -p 12489 -v '$ARG1$'
+}
diff --git a/roles/icinga-fk/files/services_icinga.cfg b/roles/icinga-fk/files/services_icinga.cfg
new file mode 100644
index 0000000..4ea25d8
--- /dev/null
+++ b/roles/icinga-fk/files/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-fk/handlers/main.yml b/roles/icinga-fk/handlers/main.yml
new file mode 100644
index 0000000..721651e
--- /dev/null
+++ b/roles/icinga-fk/handlers/main.yml
@@ -0,0 +1,12 @@
+---
+ - name: restart icinga
+ service: name=icinga state=restarted
+
+ - name: stop icinga
+ service: name=icinga state=stopped
+
+ - name: start icinga
+ service: name=icinga state=started
+
+ - name: restart apache
+ service: name=apache2 state=restarted
diff --git a/roles/icinga-fk/tasks/main.yml b/roles/icinga-fk/tasks/main.yml
new file mode 100644
index 0000000..813719b
--- /dev/null
+++ b/roles/icinga-fk/tasks/main.yml
@@ -0,0 +1,104 @@
+---
+- name: Installation apache2
+ apt:
+ name:
+ - apache2
+ - snmp
+ - icinga
+ - nagios-snmp-plugins
+ - python-passlib
+ state: present
+
+- name: Copie de fichier icinga.conf pour apache
+ copy: src=icinga.conf dest=/etc/apache2/sites-enabled/
+ notify:
+ - restart icinga
+
+- name: Copier le fichier commands.cfg pour icinga
+ copy: src=commands.cfg dest=/etc/icinga/
+ notify:
+ - restart icinga
+
+- name: Commente la ligne qui pose problème dans nt.cfg
+ copy: src=nt.cfg dest=/etc/nagios-plugins/config/
+ notify:
+ - restart icinga
+
+- name: macro pour test hdd
+ replace:
+ dest: /etc/icinga/icinga.cfg
+ regexp: 'keep_unknown_macros=0'
+ replace: 'keep_unknown_macros=1'
+ backup : yes
+ notify:
+ - restart icinga
+
+- name: Changement de mot de passe de icingaadmin
+ htpasswd:
+ path: /etc/icinga/htpasswd.users
+ name: icingaadmin
+ password: root
+
+
+- name: Copie du fichier contact
+ copy: src=contacts_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-infra s-proxy s-adm r-int r-ext srv-2012 gwsio2 s-test hostgroup
+ synchronize:
+ src: cfg/
+ dest: /etc/icinga/objects
+ notify:
+ - restart icinga
+
+
+- name: attribution des droits dossier icinga rw
+ file:
+ path: /var/lib/icinga/rw
+ owner: nagios
+ mode: 2710
+ recurse: yes
+ notify:
+ - restart icinga
+
+- name: attribution des droits dossier icinga
+ file:
+ path: /var/lib/icinga
+ owner: nagios
+ mode: 751
+ recurse: yes
+ notify:
+ - restart icinga
+
+
+- name: attribution des droits dossier var lib icinga
+ shell: chmod 2770 /var/lib/icinga/rw
+ notify:
+ - stop icinga
+
+- name: attribution des droits dossier var lib icinga
+ file:
+ path: /var/lib/icinga/rw
+ owner: www-data
+ mode: 2710
+ recurse: yes
+ notify:
+ - restart icinga
+
+ #- name: Changement droit notif
+ # shell: chmod 644 /var/log/icinga/icinga.log
+
+
+#- name: copie dns.cfg
+# copy: remote_src=true src=dns.cfg dest=/etc/nagios-plugins/config
+
+ #- name: copie check traffic
+ # copy: src=check_iftraffic3.pl dest=/usr/lib/nagios/plugins
+
+ #- name: modif des droits plugin traffic
+ # shell: chmod 755 /usr/lib/nagios/plugins/check_iftraffic3.pl
+
+- name: message d'information
+ debug: msg="Pour superviser le Windows, il faut installer NSClient++"
+
+- name: redemarrage apache
+ shell: service apache2 restart
diff --git a/roles/icinga-gm/files/cfg/contacts_icinga.cfg b/roles/icinga-gm/files/cfg/contacts_icinga.cfg
new file mode 100644
index 0000000..d4a1870
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email icingae4.gm@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-gm/files/cfg/extinfo_icinga.cfg b/roles/icinga-gm/files/cfg/extinfo_icinga.cfg
new file mode 100644
index 0000000..07bd594
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/extinfo_icinga.cfg
@@ -0,0 +1,13 @@
+##
+## Extended Host and Service Information
+##
+
+define hostextinfo{
+ hostgroup_name debian-servers
+ notes Debian GNU/Linux servers
+# notes_url http://webserver.localhost.localdomain/hostinfo.pl?host=netware1
+ icon_image base/debian.png
+ icon_image_alt Debian GNU/Linux
+ vrml_image debian.png
+ statusmap_image base/debian.gd2
+ }
diff --git a/roles/icinga-gm/files/cfg/generic-host_icinga.cfg b/roles/icinga-gm/files/cfg/generic-host_icinga.cfg
new file mode 100644
index 0000000..ed48590
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/generic-host_icinga.cfg
@@ -0,0 +1,19 @@
+ Generic host definition template - This is NOT a real host, just a template!
+
+define host{
+ name generic-host ; The name of this host template
+ notifications_enabled 1 ; Host notifications are enabled
+ event_handler_enabled 1 ; Host event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ check_command check-host-alive
+ max_check_attempts 10
+ notification_interval 0
+ notification_period 24x7
+ notification_options d,u,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-gm/files/cfg/generic-service_icinga.cfg b/roles/icinga-gm/files/cfg/generic-service_icinga.cfg
new file mode 100644
index 0000000..4d60c79
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/generic-service_icinga.cfg
@@ -0,0 +1,26 @@
+# generic service template definition
+define service{
+ name generic-service ; The 'name' of this service template
+ active_checks_enabled 1 ; Active service checks are enabled
+ passive_checks_enabled 1 ; Passive service checks are enabled/accepted
+ parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems)
+ obsess_over_service 1 ; We should obsess over this service (if necessary)
+ check_freshness 0 ; Default is to NOT check service 'freshness'
+ notifications_enabled 1 ; Service notifications are enabled
+ event_handler_enabled 1 ; Service event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ notification_interval 0 ; Only send notifications on status change by default.
+ is_volatile 0
+ check_period 24x7
+ normal_check_interval 5
+ retry_check_interval 1
+ max_check_attempts 4
+ notification_period 24x7
+ notification_options w,u,c,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-gm/files/cfg/gwsio2.cfg b/roles/icinga-gm/files/cfg/gwsio2.cfg
new file mode 100644
index 0000000..c09b7d2
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/gwsio2.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name gwsio2
+ alias Passerelle
+ address 192.168.0.1
+ icon_image cook/linux_server.gif
+ statusmap_image cook/linux_server.gd2
+ }
diff --git a/roles/icinga-gm/files/cfg/localhost.cfg b/roles/icinga-gm/files/cfg/localhost.cfg
new file mode 100644
index 0000000..4e4e190
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/localhost.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host
+ host_name localhost
+ alias Serveur monitoring
+ address localhost
+ }
+
diff --git a/roles/icinga-gm/files/cfg/localhost_icinga.cfg b/roles/icinga-gm/files/cfg/localhost_icinga.cfg
new file mode 100644
index 0000000..c15cda4
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/localhost_icinga.cfg
@@ -0,0 +1,60 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in icinga-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name localhost
+ alias localhost
+ address 127.0.0.1
+ parents gwsio2
+ }
+
+# Define a service to check the disk space of the root partition
+# on the local machine. Warning if < 20% free, critical if
+# < 10% free space on partition.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Disk Space
+ check_command check_all_disks!20%!10%
+ }
+
+
+
+# Define a service to check the number of currently logged in
+# users on the local machine. Warning if > 20 users, critical
+# if > 50 users.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Users
+ check_command check_users!20!50
+ }
+
+
+# Define a service to check the number of currently running procs
+# on the local machine. Warning if > 250 processes, critical if
+# > 400 processes.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Total Processes
+ check_command check_procs!250!400
+ }
+
+
+
+# Define a service to check the load on the local machine.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Load
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
diff --git a/roles/icinga-gm/files/cfg/netgear.cfg b/roles/icinga-gm/files/cfg/netgear.cfg
new file mode 100644
index 0000000..c35984a
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/netgear.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name netgear
+ alias switch
+ address 192.168.0.2
+ parents gwsio4
+ icon_image cook/switch.gif
+ statusmap_image cook/switch.gd2
+}
+
diff --git a/roles/icinga-gm/files/cfg/r-ext.cfg b/roles/icinga-gm/files/cfg/r-ext.cfg
new file mode 100644
index 0000000..4c14bef
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/r-ext.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-ext
+ alias Routeur externe
+ address 192.168.200.253
+ parents localhost
+ }
diff --git a/roles/icinga-gm/files/cfg/r-int.cfg b/roles/icinga-gm/files/cfg/r-int.cfg
new file mode 100644
index 0000000..77ebe3d
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/r-int.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-int
+ alias Routeur interne
+ address 172.16.0.254
+ parents r-ext
+ }
diff --git a/roles/icinga-gm/files/cfg/s-adm.cfg b/roles/icinga-gm/files/cfg/s-adm.cfg
new file mode 100644
index 0000000..aeadbee
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/s-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-adm
+ alias debian-servers
+ address 192.168.99.99
+ parents r-int
+ }
+
diff --git a/roles/icinga-gm/files/cfg/s-fog.cfg b/roles/icinga-gm/files/cfg/s-fog.cfg
new file mode 100644
index 0000000..6c24169
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/s-fog.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-fog
+ alias debian-servers
+ address 192.168.99.16
+ }
+
diff --git a/roles/icinga-gm/files/cfg/s-infra.cfg b/roles/icinga-gm/files/cfg/s-infra.cfg
new file mode 100644
index 0000000..c369ff6
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/s-infra.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra
+ alias debian-servers
+ address 172.16.0.1
+ parents r-int
+ }
+
diff --git a/roles/icinga-gm/files/cfg/s-proxy.cfg b/roles/icinga-gm/files/cfg/s-proxy.cfg
new file mode 100644
index 0000000..de4f3c9
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/s-proxy.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-proxy
+ alias serveur proxy
+ address 172.16.0.2
+ parents r-int
+ }
diff --git a/roles/icinga-gm/files/cfg/s-test.cfg b/roles/icinga-gm/files/cfg/s-test.cfg
new file mode 100644
index 0000000..2c562e6
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/s-test.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-test
+ alias debian-servers
+ address 192.168.100.150
+ parents r-ext
+ }
+
diff --git a/roles/icinga-gm/files/cfg/s-win.cfg b/roles/icinga-gm/files/cfg/s-win.cfg
new file mode 100644
index 0000000..4a5bc58
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/s-win.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-win
+ alias windows-servers
+ address 172.16.0.6
+ parents r-int
+ icon_image base/win40.gif
+ statusmap_image base/win40.gd2
+ }
+
diff --git a/roles/icinga-gm/files/cfg/services_icinga.cfg b/roles/icinga-gm/files/cfg/services_icinga.cfg
new file mode 100644
index 0000000..4ea25d8
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-gm/files/cfg/timeperiods_icinga.cfg b/roles/icinga-gm/files/cfg/timeperiods_icinga.cfg
new file mode 100644
index 0000000..55ecf9d
--- /dev/null
+++ b/roles/icinga-gm/files/cfg/timeperiods_icinga.cfg
@@ -0,0 +1,50 @@
+###############################################################################
+# timeperiods.cfg
+###############################################################################
+
+# This defines a timeperiod where all times are valid for checks,
+# notifications, etc. The classic "24x7" support nightmare. :-)
+
+define timeperiod{
+ timeperiod_name 24x7
+ alias 24 Hours A Day, 7 Days A Week
+ sunday 00:00-24:00
+ monday 00:00-24:00
+ tuesday 00:00-24:00
+ wednesday 00:00-24:00
+ thursday 00:00-24:00
+ friday 00:00-24:00
+ saturday 00:00-24:00
+ }
+
+# Here is a slightly friendlier period during work hours
+define timeperiod{
+ timeperiod_name workhours
+ alias Standard Work Hours
+ monday 09:00-17:00
+ tuesday 09:00-17:00
+ wednesday 09:00-17:00
+ thursday 09:00-17:00
+ friday 09:00-17:00
+ }
+
+# The complement of workhours
+define timeperiod{
+ timeperiod_name nonworkhours
+ alias Non-Work Hours
+ sunday 00:00-24:00
+ monday 00:00-09:00,17:00-24:00
+ tuesday 00:00-09:00,17:00-24:00
+ wednesday 00:00-09:00,17:00-24:00
+ thursday 00:00-09:00,17:00-24:00
+ friday 00:00-09:00,17:00-24:00
+ saturday 00:00-24:00
+ }
+
+# This one is a favorite: never :)
+define timeperiod{
+ timeperiod_name never
+ alias Never
+ }
+
+# end of file
diff --git a/roles/icinga-gm/files/check_iftraffic3.pl b/roles/icinga-gm/files/check_iftraffic3.pl
new file mode 100755
index 0000000..62ddbd1
--- /dev/null
+++ b/roles/icinga-gm/files/check_iftraffic3.pl
@@ -0,0 +1,643 @@
+#!/usr/bin/perl -w
+#
+# check_iftraffic.pl - Nagios(r) network traffic monitor plugin
+# Copyright (C) 2004 Gerd Mueller / Netways GmbH
+# $Id: check_iftraffic.pl 1119 2006-02-09 10:30:09Z gmueller $
+#
+# mw = Markus Werner mw+nagios@wobcom.de
+# Remarks (mw):
+#
+# I adopted as much as possible the programming style of the origin code.
+#
+# There should be a function to exit this programm,
+# instead of calling print and exit statements all over the place.
+#
+#
+# minor changes by mw
+# The snmp if_counters on net devices can have overflows.
+# I wrote this code to address this situation.
+# It has no automatic detection and which point the overflow
+# occurs but it will generate a warning state and you
+# can set the max value by calling this script with an additional
+# arg.
+#
+# minor cosmetic changes by mw
+# Sorry but I couldn't sustain to clean up some things.
+#
+# gj = Greg Frater gregATfraterfactory.com
+# Remarks (gj):
+# minor (gj):
+#
+# * fixed the performance data, formating was not to spec
+# * Added a check of the interfaces status (up/down).
+# If down the check returns a critical status.
+# * Allow either textual or the numeric index value.
+# * If the interface speed is not specified on the command line
+# it gets it automatically from IfSpeed
+# * Added option for second ifSpeed to allow for asymetrcal links
+# such as a DSL line or cable modem where the download and upload
+# speeds are different
+# * Added -B option to display results in bits/sec instead of Bytes/sec
+# * Added the current usage in Bytes/s (or bit/s) to the perfdata output
+# * Added ability for plugin to determine interface to query by matching IP
+# address of host with entry in ipAdEntIfIndex (.1.3.6.1.2.1.4.20.1.2)
+# * Added -L flag to list entries found in the ipAdEntIfIndex table
+# Otherwise, it works as before.
+#
+#
+#
+#
+# based on check_traffic from Adrian Wieczorek, <ads (at) irc.pila.pl>
+#
+# Send us bug reports, questions and comments about this plugin.
+# Latest version of this software: http://www.nagiosexchange.org
+#
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307
+
+use strict;
+
+use Net::SNMP;
+use Getopt::Long;
+&Getopt::Long::config('bundling');
+
+use Data::Dumper;
+
+my $host_ip;
+my $host_address;
+my $iface_number;
+my $iface_descr;
+my $iface_speed;
+my $iface_speedOut;
+my $index_list;
+my $opt_h;
+my $units;
+
+my $session;
+my $error;
+my $port = 161;
+my $snmp_version = 1;
+
+my @snmpoids;
+
+# SNMP OIDs for Traffic
+my $snmpIfOperStatus = '1.3.6.1.2.1.2.2.1.8';
+my $snmpIfInOctets = '1.3.6.1.2.1.2.2.1.10';
+my $snmpIfOutOctets = '1.3.6.1.2.1.2.2.1.16';
+my $snmpIfDescr = '1.3.6.1.2.1.2.2.1.2';
+my $snmpIfSpeed = '1.3.6.1.2.1.2.2.1.5';
+my $snmpIPAdEntIfIndex = '1.3.6.1.2.1.4.20.1.2';
+
+my $response;
+
+# Path to tmp files
+my $TRAFFIC_FILE = "/tmp/traffic";
+
+# changes sos 20090717 UNKNOWN must bes 3
+my %STATUS_CODE =
+ ( 'UNKNOWN' => '3', 'OK' => '0', 'WARNING' => '1', 'CRITICAL' => '2' );
+
+#default values;
+my $state = "UNKNOWN";
+my $if_status = '4';
+my ( $in_bytes, $out_bytes ) = 0;
+my $warn_usage = 85;
+my $crit_usage = 98;
+my $COMMUNITY = "public";
+my $use_reg = undef; # Use Regexp for name
+my $output = "";
+my $bits = undef;
+my $suffix = "Bs";
+my $label = "MBytes";
+
+#added 20050614 by mw
+my $max_value;
+my $max_bytes;
+
+#cosmetic changes 20050614 by mw, see old versions for detail
+# Added options for bits and second max ifspeed 20100202 by gj
+# Added options for specificy IP addr to match 20100405 by gj
+my $status = GetOptions(
+ "h|help" => \$opt_h,
+ 'B' => \$bits,
+ 'bits' => \$bits,
+ "C|community=s" => \$COMMUNITY,
+ "w|warning=s" => \$warn_usage,
+ "c|critical=s" => \$crit_usage,
+ "b|bandwidth|I|inBandwidth=i" => \$iface_speed,
+ "O|outBandwidth=i" => \$iface_speedOut,
+ 'r' => \$use_reg,
+ 'noregexp' => \$use_reg,
+ "p|port=i" => \$port,
+ "u|units=s" => \$units,
+ "i|interface=s" => \$iface_number,
+ "A|address=s" => \$host_ip,
+ "H|hostname=s" => \$host_address,
+ 'L' => \$index_list,
+ 'list' => \$index_list,
+
+ #added 20050614 by mw
+ "M|max=i" => \$max_value
+);
+
+if ( $status == 0 ) {
+ print_help();
+ exit $STATUS_CODE{'OK'};
+}
+
+# Changed 20091214 gj
+# Check for missing options
+#if ( ( !$host_address ) or ( !$iface_descr ) ) {
+if ( !$host_address ) {
+ print "\nMissing host address!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speed ) and ( !$units ) ){
+ print "\nMissing units!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $units ) and ( ( !$iface_speed ) and ( !$iface_speedOut ) ) ) {
+ print "\nMissing interface maximum speed!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speedOut ) and ( !$units ) ) {
+ print "\nMissing units for Out maximum speed!\n\n";
+ stop(print_usage(),"OK");
+}
+
+
+if ($bits) {
+ $suffix = "bs"
+}
+
+if ( !$iface_speed ) {
+ # Do nothing
+}else{
+
+ #change 20050414 by mw
+ # Added iface_speedOut 20100202 by gj
+ # Convert interface speed to kiloBytes
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+ if ( $iface_speedOut ) {
+ $iface_speedOut = bits2bytes( $iface_speedOut, $units ) / 1024;
+ }
+ if ( !$max_value ) {
+
+ # If no -M Parameter was set, set it to 32Bit Overflow
+ $max_bytes = 4194304 ; # the value is (2^32/1024)
+ }
+ else {
+ $max_bytes = unit2bytes( $max_value, $units );
+ }
+}
+
+if ( $snmp_version =~ /[12]/ ) {
+ ( $session, $error ) = Net::SNMP->session(
+ -hostname => $host_address,
+ -community => $COMMUNITY,
+ -port => $port,
+ -version => $snmp_version
+ );
+
+ if ( !defined($session) ) {
+ stop("UNKNOWN: $error","UNKNOWN");
+ }
+}
+elsif ( $snmp_version =~ /3/ ) {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v3 yet\n",$state);
+}
+else {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v$snmp_version yet\n",$state);
+}
+
+# Neither Interface Index nor Host IP address were specified
+if ( !$iface_descr ) {
+ if ( !$host_ip ){
+ # try to resolve host name and find index from ip addr
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_address );
+ } else {
+ # Use ip addr to find index
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_ip );
+ }
+}
+
+#push( @snmpoids, $snmpIPAdEntIfIndex . "." . $host_address );
+
+# Added 20091209 gj
+# Detect if a string description was given or a numberic interface index number
+if ( $iface_descr =~ /[^0123456789]+/ ) {
+ $iface_number = fetch_ifdescr( $session, $iface_descr );
+}else{
+ $iface_number = $iface_descr;
+}
+
+push( @snmpoids, $snmpIfSpeed . "." . $iface_number );
+push( @snmpoids, $snmpIfOperStatus . "." . $iface_number );
+push( @snmpoids, $snmpIfInOctets . "." . $iface_number );
+push( @snmpoids, $snmpIfOutOctets . "." . $iface_number );
+
+if ( !defined( $response = $session->get_request(@snmpoids) ) ) {
+ my $answer = $session->error;
+ $session->close;
+
+ stop("WARNING: SNMP error: $answer\n", "WARNING");
+}
+
+# Added 20091209 gj
+# Get interface speed from device if not provided on command line
+# Convert to kiloBytes
+if ( !$iface_speed ) {
+ $iface_speed = $response->{ $snmpIfSpeed . "." . $iface_number };
+ $units = "b";
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+}
+
+# Added 20100201 gj
+# Check if Out max speed was provided, use same if speed for both if not
+if (!$iface_speedOut) {
+ $iface_speedOut = $iface_speed;
+}
+
+$if_status = $response->{ $snmpIfOperStatus . "." . $iface_number };
+$in_bytes = $response->{ $snmpIfInOctets . "." . $iface_number } / 1024; # in kiloBytes
+$out_bytes = $response->{ $snmpIfOutOctets . "." . $iface_number } / 1024; # in kiloBytes
+
+$session->close;
+
+my $row;
+my $last_check_time = time - 1;
+my $last_in_bytes = $in_bytes;
+my $last_out_bytes = $out_bytes;
+
+if (
+ open( FILE,
+ "<" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address
+ )
+ )
+{
+ while ( $row = <FILE> ) {
+
+ #cosmetic change 20050416 by mw
+ #Couldn't sustain;-)
+## chomp();
+ ( $last_check_time, $last_in_bytes, $last_out_bytes ) =
+ split( ":", $row );
+
+ ### by sos 17.07.2009 check for last_bytes
+ if ( ! $last_in_bytes ) { $last_in_bytes=$in_bytes; }
+ if ( ! $last_out_bytes ) { $last_out_bytes=$out_bytes; }
+
+ if ($last_in_bytes !~ m/\d/) { $last_in_bytes=$in_bytes; }
+ if ($last_out_bytes !~ m/\d/) { $last_out_bytes=$out_bytes; }
+ }
+ close(FILE);
+}
+
+my $update_time = time;
+
+open( FILE, ">" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address )
+ or die "Can't open $TRAFFIC_FILE for writing: $!";
+
+printf FILE ( "%s:%.0ld:%.0ld\n", $update_time, $in_bytes, $out_bytes );
+close(FILE);
+
+my $db_file;
+
+#added 20050614 by mw
+#Check for and correct counter overflow (if possible).
+#See function counter_overflow.
+$in_bytes = counter_overflow( $in_bytes, $last_in_bytes, $max_bytes );
+$out_bytes = counter_overflow( $out_bytes, $last_out_bytes, $max_bytes );
+
+# Calculate traffic since last check (RX\TX) in kiloBytes
+my $in_traffic = sprintf( "%.2lf",
+ ( $in_bytes - $last_in_bytes ) / ( time - $last_check_time ) );
+my $out_traffic = sprintf( "%.2lf",
+ ( $out_bytes - $last_out_bytes ) / ( time - $last_check_time ) );
+
+# sos 20090717 changed due to rrdtool needs bytes
+my $in_traffic_absolut = $in_bytes * 1024 ;
+my $out_traffic_absolut = $out_bytes * 1024;
+
+# Calculate usage percentages
+my $in_usage = sprintf( "%.2f", ( 1.0 * $in_traffic * 100 ) / $iface_speed );
+my $out_usage = sprintf( "%.2f", ( 1.0 * $out_traffic * 100 ) / $iface_speedOut );
+
+
+if ($bits) {
+ # Convert output from Bytes to bits
+ $in_bytes = $in_bytes * 8;
+ $out_bytes = $out_bytes * 8;
+ $in_traffic = $in_traffic * 8;
+ $out_traffic = $out_traffic * 8;
+ $label = "Mbits";
+}
+
+my $in_prefix = "K";
+my $out_prefix = "K";
+
+if ( $in_traffic > 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 );
+ $in_prefix = "M";
+}
+if ( $out_traffic > 1024 ) {
+ $out_traffic = sprintf( "%.2f", $out_traffic / 1024 );
+ $out_prefix = "M";
+}
+if ( $in_traffic > 1024 * 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 * 1024 );
+ $in_prefix = "G";
+}
+if ( $out_traffic > 1024 * 1024 ) {
+ $out_traffic = sprintf( "%.2f",$out_traffic / 1024 * 1024 );
+ $out_prefix = "G";
+}
+
+# Convert from kiloBytes to megaBytes
+$in_bytes = sprintf( "%.2f", $in_bytes / 1024 );
+$out_bytes = sprintf( "%.2f", $out_bytes / 1024 );
+
+$state = "OK";
+
+# Added 20091209 by gj
+if ( $if_status != 1 ) {
+ $output = "Interface $iface_descr is down!";
+
+}else{
+ $output =
+ "Average IN: "
+ . $in_traffic . $in_prefix . $suffix . " (" . $in_usage . "%), "
+ . "Average OUT: " . $out_traffic . $out_prefix . $suffix . " (" . $out_usage . "%)<br>";
+ $output .= "Total RX: $in_bytes $label, Total TX: $out_bytes $label";
+}
+
+# Changed 20091209 gj
+if ( ( $in_usage > $crit_usage ) or ( $out_usage > $crit_usage ) or ( $if_status != 1 ) ) {
+ $state = "CRITICAL";
+}
+
+if ( ( $in_usage > $warn_usage )
+ or ( $out_usage > $warn_usage ) && $state eq "OK" )
+{
+ $state = "WARNING";
+}
+
+# Changed 20091209 gj
+$output = "$state - $output"
+ if ( $state ne "OK" );
+
+# Changed 20091214 gj - commas should have been semi colons
+$output .=
+"|inUsage=$in_usage%;$warn_usage;$crit_usage outUsage=$out_usage%;$warn_usage;$crit_usage"
+ . " inBandwidth=" . $in_traffic . $in_prefix . $suffix . " outBandwidth=" . $out_traffic . $out_prefix . $suffix
+ . " inAbsolut=$in_traffic_absolut outAbsolut=$out_traffic_absolut";
+
+stop($output, $state);
+
+
+sub fetch_Ip2IfIndex {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $host ) = @_;
+
+
+ # Determine if we have a host name or IP addr
+ if ( $host =~ /\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/ ){
+ #print "\nI found an IP address\n\n";
+ } else {
+ $host = get_ip ( $host );
+ #print "\nWe have a host name $host\n\n";
+ }
+
+ # Quit if results not found
+ if ( !defined( $response = $session->get_table($snmpIPAdEntIfIndex) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+
+ my %resp = %{$response};
+# foreach $key ( keys %{$response} ) {
+
+ if ( $index_list ){
+ print ("\nInterfaces found:\n");
+ print (" IP Addr\tIndex\n");
+ print ("------------------------\n");
+ }
+ # Check each returned value
+ foreach $key ( keys %resp ) {
+
+ if ( $index_list ){
+ my $index_addr = substr $key, 21;
+ print ($index_addr,"\t ",$resp{$key},"\n");
+ }
+
+ # Check for ip address mathcin in returned index results
+ if ( $key =~ /$host$/ ) {
+ $snmpkey = $resp{$key};
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $host \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+sub fetch_ifdescr {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $ifdescr ) = @_;
+
+ if ( !defined( $response = $session->get_table($snmpIfDescr) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+ foreach $key ( keys %{$response} ) {
+
+ # added 20070816 by oer: remove trailing 0 Byte for Windows :-(
+ my $resp=$response->{$key};
+ $resp =~ s/\x00//;
+
+
+ my $test = defined($use_reg)
+ ? $resp =~ /$ifdescr/
+ : $resp eq $ifdescr;
+
+ if ($test) {
+
+ ###if ( $resp =~ /^$ifdescr$/ ) {
+ ###if ( $resp =~ /$ifdescr/ ) {
+ ### print "$resp \n";
+ ###if ( $response->{$key} =~ /^$ifdescr$/ ) {
+
+ $key =~ /.*\.(\d+)$/;
+ $snmpkey = $1;
+
+ # print "$ifdescr = $key / $snmpkey \n"; #debug
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $ifdescr \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bits
+sub bits2bytes {
+ return unit2bytes(@_) / 8;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bytes
+sub unit2bytes {
+ my ( $value, $unit ) = @_;
+
+ if ( $unit eq "g" ) {
+ return $value * 1024 * 1024 * 1024;
+ }
+ elsif ( $unit eq "m" ) {
+ return $value * 1024 * 1024;
+ }
+ elsif ( $unit eq "k" ) {
+ return $value * 1024;
+ }
+ elsif ( $unit eq "b" ) {
+ return $value * 1;
+ }
+ else {
+ print "You have to supply a supported unit\n";
+ exit $STATUS_CODE{'UNKNOWN'};
+ }
+}
+
+#added 20050414 by mw
+#This function detects if an overflow occurs. If so, it returns
+#a computed value for $bytes.
+#If there is no counter overflow it simply returns the origin value of $bytes.
+#IF there is a Counter reboot wrap, just use previous output.
+sub counter_overflow {
+ my ( $bytes, $last_bytes, $max_bytes ) = @_;
+
+ $bytes += $max_bytes if ( $bytes < $last_bytes );
+ $bytes = $last_bytes if ( $bytes < $last_bytes );
+ return $bytes;
+}
+
+# Added 20100202 by gj
+# Print results and exit script
+sub stop {
+ my $result = shift;
+ my $exit_code = shift;
+ print $result . "\n";
+ exit ( $STATUS_CODE{$exit_code} );
+}
+
+# Added 20100405 by gj
+# Lookup hosts ip address
+sub get_ip {
+ use Net::DNS;
+
+ my ( $host_name ) = @_;
+
+ my $res = Net::DNS::Resolver->new;
+ my $query = $res->search($host_name);
+
+ if ($query) {
+ foreach my $rr ($query->answer) {
+ next unless $rr->type eq "A";
+ #print $rr->address, "\n";
+ return $rr->address;
+ }
+ } else {
+
+ stop("Error: IP address not resolved\n","UNKNOWN");
+ }
+}
+
+#cosmetic changes 20050614 by mw
+#Couldn't sustain "HERE";-), either.
+sub print_usage {
+ print <<EOU;
+ Usage: check_iftraffic3.pl -H host [ -C community_string ] [ -i if_index|if_descr ] [ -r ] [ -b if_max_speed_in | -I if_max_speed_in ] [ -O if_max_speed_out ] [ -u ] [ -B ] [ -A IP Address ] [ -L ] [ -M ] [ -w warn ] [ -c crit ]
+
+ Example 1: check_iftraffic3.pl -H host1 -C sneaky
+ Example 2: check_iftraffic3.pl -H host1 -C sneaky -i "Intel Pro" -r -B
+ Example 3: check_iftraffic3.pl -H host1 -C sneaky -i 5
+ Example 4: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 100 -u m
+ Example 5: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 20 -O 5 -u m
+ Example 6: check_iftraffic3.pl -H host1 -C sneaky -A 192.168.1.1 -B -b 100 -u m
+
+ Options:
+
+ -H, --host STRING or IPADDRESS
+ Check interface on the indicated host.
+ -B, --bits
+ Display results in bits per second b/s (default: Bytes/s)
+ -C, --community STRING
+ SNMP Community.
+ -r, --regexp
+ Use regexp to match NAME in description OID
+ -i, --interface STRING
+ Interface Name
+ -b, --bandwidth INTEGER
+ -I, --inBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ both IN and OUT if no second (-O) max speed is provided.
+ -O, --outBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ OUT traffic. Uses the same units value given for -b.
+ -u, --units STRING
+ g=gigabits/s,m=megabits/s,k=kilobits/s,b=bits/s. Required if -b, -I, or
+ -O are used.
+ -w, --warning INTEGER
+ % of bandwidth usage necessary to result in warning status (default: 85%)
+ -c, --critical INTEGER
+ % of bandwidth usage necessary to result in critical status (default: 98%)
+ -M, --max INTEGER
+ Max Counter Value of net devices in kilo/mega/giga/bytes.
+ -A, --address STRING (IP Address)
+ IP Address to use when determining the interface index to use. Can be
+ used when the index changes frequently or as in the case of Windows
+ servers the index is different depending on the NIC installed.
+ -L, --list FLAG (on/off)
+ Tell plugin to list available interfaces. This is not supported inside
+ of Nagios, but may be useful from the command line.
+EOU
+
+}
+
diff --git a/roles/icinga-gm/files/commands.cfg b/roles/icinga-gm/files/commands.cfg
new file mode 100644
index 0000000..1ceea2c
--- /dev/null
+++ b/roles/icinga-gm/files/commands.cfg
@@ -0,0 +1,90 @@
+###############################################################################
+# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
+###############################################################################
+
+
+################################################################################
+# NOTIFICATION COMMANDS
+################################################################################
+
+
+# 'notify-host-by-email' command definition
+define command{
+ command_name notify-host-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$
+ }
+
+# 'notify-service-by-email' command definition
+define command{
+ command_name notify-service-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$
+ }
+
+
+
+
+
+################################################################################
+# HOST CHECK COMMANDS
+################################################################################
+
+# On Debian, check-host-alive is being defined from within the
+# nagios-plugins-basic package
+define command{
+ command_name check_snmp_storage
+ command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -m $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_load
+ command_line $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -T $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_mem
+ command_line $USER1$/check_snmp_mem.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_int
+ command_line $USER1$/check_snmp_netint.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -a -m -k -M -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_iftraffic3
+ #command_name check_win_int
+ #command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$
+ #command_line $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -k -M -g -w $ARG4$ -c $ARG5$
+ command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$ -i $ARG2$ -w $ARG3$ -c $ARG4$
+}
+
+define command{
+ command_name check_snmp
+ command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
+}
+###############################
+##WINDOWS
+###############################
+
+define command{
+ command_name check_nt
+ command_line $USER1$/check_nt -H $HOSTADDRESS$ -s root -p 12489 -v $ARG1$ $ARG2$
+}
+
+################################################################################
+# PERFORMANCE DATA COMMANDS
+################################################################################
+
+
+# 'process-host-perfdata' command definition
+define command{
+ command_name process-host-perfdata
+ command_line /usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /var/lib/nagios3/host-perfdata.out
+ }
+
+
+# 'process-service-perfdata' command definition
+define command{
+ command_name process-service-perfdata
+ command_line /usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /var/lib/nagios3/service-perfdata.out
+ }
diff --git a/roles/icinga-gm/files/contacts_icinga.cfg b/roles/icinga-gm/files/contacts_icinga.cfg
new file mode 100644
index 0000000..d4a1870
--- /dev/null
+++ b/roles/icinga-gm/files/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email icingae4.gm@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-gm/files/dns.cfg b/roles/icinga-gm/files/dns.cfg
new file mode 100644
index 0000000..5b69aca
--- /dev/null
+++ b/roles/icinga-gm/files/dns.cfg
@@ -0,0 +1,11 @@
+# 'check_dns' command definition
+define command{
+ command_name check_dns
+ command_line /usr/lib/nagios/plugins/check_dns -H www.dfco.fr -s '$HOSTADDRESS$'
+}
+
+# 'check_dig' command definition
+define command{
+ command_name check_dig
+ command_line /usr/lib/nagios/plugins/check_dig -H '$HOSTADDRESS$' -l '$ARG1$'
+}
diff --git a/roles/icinga-gm/files/hostgroups_icinga-save.cfg b/roles/icinga-gm/files/hostgroups_icinga-save.cfg
new file mode 100644
index 0000000..68e48a4
--- /dev/null
+++ b/roles/icinga-gm/files/hostgroups_icinga-save.cfg
@@ -0,0 +1,74 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-infra, s-proxy, r-int, r-ext, s-adm, s-fog
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-adm, s-infra, s-proxy, r-int, r-ext, localhost, s-fog, gwsio2
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-infra, s-win
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members r-int, s-win
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+#define hostgroup {
+# hostgroup_name email-servers
+# alias serveurs-email
+# members s-mess
+# }
+
+define hostgroup {
+ hostgroup_name proxy-servers
+ alias serveurs-proxy
+ members s-proxy
+}
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members s-win
+}
+
+#define hostgroup{
+# hostgroup_name switch
+# alias switch
+# members netgear
+#}
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members s-infra, s-proxy, r-int, r-ext, s-adm, s-fog
+}
+
diff --git a/roles/icinga-gm/files/hostgroups_icinga.cfg b/roles/icinga-gm/files/hostgroups_icinga.cfg
new file mode 100644
index 0000000..773c702
--- /dev/null
+++ b/roles/icinga-gm/files/hostgroups_icinga.cfg
@@ -0,0 +1,74 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-adm, s-test
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-adm, s-test, localhost
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-win
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members s-win
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+#define hostgroup {
+# hostgroup_name email-servers
+# alias serveurs-email
+# members s-mess
+# }
+
+#define hostgroup {
+# hostgroup_name proxy-servers
+# alias serveurs-proxy
+# members s-proxy
+#}
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members s-win
+}
+
+#define hostgroup{
+# hostgroup_name switch
+# alias switch
+# members netgear
+#}
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members s-test, s-adm,
+}
+
diff --git a/roles/icinga-gm/files/icinga.cfg b/roles/icinga-gm/files/icinga.cfg
new file mode 100644
index 0000000..fde1780
--- /dev/null
+++ b/roles/icinga-gm/files/icinga.cfg
@@ -0,0 +1,1494 @@
+##############################################################################
+#
+# ICINGA.CFG - Sample Main Config File for Icinga
+#
+# Read the documentation for more information on this configuration
+# file. I've provided some comments here, but things may not be so
+# clear without further explanation.
+#
+##############################################################################
+
+
+# LOG FILE
+# This is the main log file where service and host events are logged
+# for historical purposes. This should be the first option specified
+# in the config file!!!
+
+log_file=/var/log/icinga/icinga.log
+
+# Commands definitions
+cfg_file=/etc/icinga/commands.cfg
+
+# Debian also defaults to using the check commands defined by the debian
+# nagios-plugins package
+cfg_dir=/etc/nagios-plugins/config
+
+# OBJECT CONFIGURATION FILE(S)
+# These are the object configuration files in which you define hosts,
+# host groups, contacts, contact groups, services, etc.
+# Hint: Check the docs/wiki on how to monitor remote hosts with different
+# transport methods and plugins
+
+# Debian uses by default a configuration directory where icinga-common,
+# other packages and the local admin can dump or link configuration
+# files into.
+cfg_dir=/etc/icinga/objects/
+
+# Definitions for ido2db process checks
+#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg
+
+# Definitions for broker modules like idoutils.cfg
+cfg_dir=/etc/icinga/modules
+
+
+
+# OBJECT CACHE FILE
+# This option determines where object definitions are cached when
+# Icinga starts/restarts. The CGIs read object definitions from
+# this cache file (rather than looking at the object config files
+# directly) in order to prevent inconsistencies that can occur
+# when the config files are modified after Icinga starts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the objects cache file entirely.
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+# Tip: Use that file to debug your configuration with fully resolved
+# objects like the core sees them.
+
+object_cache_file=/var/cache/icinga/objects.cache
+
+
+
+# PRE-CACHED OBJECT FILE
+# This options determines the location of the precached object file.
+# If you run Icinga with the -p command line option, it will preprocess
+# your object configuration file(s) and write the cached config to this
+# file. You can then start Icinga with the -u option to have it read
+# object definitions from this precached file, rather than the standard
+# object configuration files (see the cfg_file and cfg_dir options above).
+# Using a precached object file can speed up the time needed to (re)start
+# the Icinga process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Icinga to find our more
+# about how this feature works.
+
+precached_object_file=/var/cache/icinga/objects.precache
+
+
+
+# RESOURCE FILE
+# This is an optional resource file that contains $USERx$ macro
+# definitions. Multiple resource files can be specified by using
+# multiple resource_file definitions. The CGIs will not attempt to
+# read the contents of resource files, so information that is
+# considered to be sensitive (usernames, passwords, etc) can be
+# defined as macros in this file and restrictive permissions (600)
+# can be placed on this file.
+
+resource_file=/etc/icinga/resource.cfg
+
+
+
+# STATUS FILE
+# This is where the current status of all monitored services and
+# hosts is stored. Its contents are read and processed by the CGIs.
+# The contents of the status file are deleted every time Icinga
+# restarts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the status file entirely. This becomes handy when using other methods
+# for data retrieval (e.g. IDOUtils DB)
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+
+status_file=/var/lib/icinga/status.dat
+
+
+
+# STATUS FILE UPDATE INTERVAL
+# This option determines the frequency (in seconds) that
+# Icinga will periodically dump program, host, and
+# service status data.
+# Increase the value, if you don't require it that often.
+
+#status_update_interval=30
+status_update_interval=10
+
+
+
+# ICINGA USER
+# This determines the effective user that Icinga should run as.
+# You can either supply a username or a UID.
+
+icinga_user=nagios
+
+
+
+# ICINGA GROUP
+# This determines the effective group that Icinga should run as.
+# You can either supply a group name or a GID.
+
+icinga_group=nagios
+
+
+
+# EXTERNAL COMMAND OPTION
+# This option allows you to specify whether or not Icinga should check
+# for external commands (in the command file defined below). By default
+# Icinga will *not* check for external commands, just to be on the
+# cautious side. If you want to be able to use the CGI command interface
+# you will have to enable this.
+# Values: 0 = disable commands, 1 = enable commands
+
+check_external_commands=1
+
+
+
+# EXTERNAL COMMAND CHECK INTERVAL
+# This is the interval at which Icinga should check for external commands.
+# This value works of the interval_length you specify later. If you leave
+# that at its default value of 60 (seconds), a value of 1 here will cause
+# Icinga to check for external commands every minute. If you specify a
+# number followed by an "s" (i.e. 15s), this will be interpreted to mean
+# actual seconds rather than a multiple of the interval_length variable.
+# Note: In addition to reading the external command file at regularly
+# scheduled intervals, Icinga will also check for external commands after
+# event handlers are executed.
+# NOTE: Setting this value to -1 causes Icinga to check the external
+# command file as often as possible.
+
+#command_check_interval=15s
+command_check_interval=-1
+
+
+
+# EXTERNAL COMMAND FILE
+# This is the file that Icinga checks for external command requests.
+# It is also where the command CGI will write commands that are submitted
+# by users, so it must be writeable by the user that the web server
+# is running as (usually 'nobody'). Permissions should be set at the
+# directory level instead of on the file, as the file is deleted every
+# time its contents are processed.
+# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
+# time to do it.
+
+command_file=/var/lib/icinga/rw/icinga.cmd
+
+
+
+# EXTERNAL COMMAND BUFFER SLOTS
+# This settings is used to tweak the number of items or "slots" that
+# the Icinga daemon should allocate to the buffer that holds incoming
+# external commands before they are processed. As external commands
+# are processed by the daemon, they are removed from the buffer.
+# Increase the value, if you are using addons like check_mk supplying
+# more external commands (passive check results) than usual.
+
+#external_command_buffer_slots=32768
+external_command_buffer_slots=4096
+
+
+
+# LOCK FILE
+# This is the lockfile that Icinga will use to store its PID number
+# in when it is running in daemon mode.
+
+lock_file=/var/run/icinga/icinga.pid
+
+
+
+# TEMP FILE
+# This is a temporary file that is used as scratch space when Icinga
+# updates the status log, cleans the comment file, etc. This file
+# is created, used, and deleted throughout the time that Icinga is
+# running.
+
+temp_file=/var/cache/icinga/icinga.tmp
+
+
+
+# TEMP PATH
+# This is path where Icinga can create temp files for service and
+# host check results, etc.
+
+temp_path=/tmp
+
+
+
+# EVENT BROKER OPTIONS
+# Controls what (if any) data gets sent to the event broker.
+# Values: 0 = Broker nothing
+# -1 = Broker everything
+# <other> = See documentation
+
+event_broker_options=-1
+
+
+
+# EVENT BROKER MODULE(S)
+# ----> use the new *module definition* instead:
+# ----> http://docs.icinga.org/latest/en/objectdefinitions.html
+#
+# Example definitions can be found in the '/etc/icinga/modules/' directory.
+# If you want to enable idoutils in Debian install icinga-idoutils and copy
+# /usr/share/doc/icinga-idoutils/examples/idoutils.cfg-sample to
+# /etc/icinga/modules/idoutils.cfg.
+# Don't forget to also enable the daemon in /etc/default/icinga
+
+# LOG ROTATION METHOD
+# This is the log rotation method that Icinga should use to rotate
+# the main log file. Values are as follows..
+# n = None - don't rotate the log
+# h = Hourly rotation (top of the hour)
+# d = Daily rotation (midnight every day)
+# w = Weekly rotation (midnight on Saturday evening)
+# m = Monthly rotation (midnight last day of month)
+
+log_rotation_method=d
+
+
+
+# LOG ARCHIVE PATH
+# This is the directory where archived (rotated) log files should be
+# placed (assuming you've chosen to do log rotation).
+
+log_archive_path=/var/log/icinga/archives
+
+
+
+# LOGGING OPTIONS FOR DAEMON
+# If you want messages logged to the daemon log file (usually icinga.log).
+# Default option is 1 (yes), the other valid option is 0 (no)
+
+use_daemon_log=1
+
+
+
+# LOGGING OPTIONS FOR SYSLOG
+# If you want messages logged to the syslog facility, as well as the
+# Icinga log file set this option to 1. If not, set it to 0.
+
+use_syslog=1
+
+
+
+# SYSLOG FACILITY
+# If you enabled use_syslog you can set icinga to use a local facility
+# instead of the default.To enable set this option to 1, if not, set it to 0.
+
+use_syslog_local_facility=0
+
+
+
+# SYSLOG LOCAL FACILITY
+# If you specified the use_syslog_local_facility you can chose which
+# local facility to use. Valid values are from 0 to 7
+
+syslog_local_facility=5
+
+
+
+# NOTIFICATION LOGGING OPTION
+# If you don't want notifications to be logged, set this value to 0.
+# If notifications should be logged, set the value to 1.
+
+log_notifications=1
+
+
+
+# SERVICE RETRY LOGGING OPTION
+# If you don't want service check retries to be logged, set this value
+# to 0. If retries should be logged, set the value to 1.
+
+log_service_retries=1
+
+
+
+# HOST RETRY LOGGING OPTION
+# If you don't want host check retries to be logged, set this value to
+# 0. If retries should be logged, set the value to 1.
+
+log_host_retries=1
+
+
+
+# EVENT HANDLER LOGGING OPTION
+# If you don't want host and service event handlers to be logged, set
+# this value to 0. If event handlers should be logged, set the value
+# to 1.
+
+log_event_handlers=1
+
+
+
+# INITIAL STATES LOGGING OPTION
+# If you want Icinga to log all initial host and service states to
+# the main log file (the first time the service or host is checked)
+# you can enable this option by setting this value to 1. If you
+# are not using an external application that does long term state
+# statistics reporting, you do not need to enable this option. In
+# this case, set the value to 0.
+
+log_initial_states=0
+
+
+
+# CURRENT STATES LOGGING OPTION
+# If you don't want Icinga to log all current host and service states
+# after log has been rotated to the main log file, you can disable this
+# option by setting this value to 0. Default value is 1.
+
+log_current_states=1
+
+
+
+# EXTERNAL COMMANDS LOGGING OPTION
+# If you don't want Icinga to log external commands, set this value
+# to 0. If external commands should be logged, set this value to 1.
+# Note: This option does not include logging of passive service
+# checks - see the option below for controlling whether or not
+# passive checks are logged.
+
+log_external_commands=1
+
+
+
+# LOG ANONYMIZED EXTERNAL COMMAND AUTHOR !!EXPERIMENTAL!!
+# This option substitutes the user name on external commands with
+# the string "<anon>" if the command gets logged. It is
+# anonymized in log files only. This option was added to make
+# icinga compliant with data retention laws on various countries.
+# This option is disabled by default.
+
+log_anonymized_external_command_author=0
+
+
+
+# PASSIVE CHECKS LOGGING OPTION
+# If you don't want Icinga to log passive host and service checks, set
+# this value to 0. If passive checks should be logged, set
+# this value to 1.
+
+log_passive_checks=1
+
+
+
+# LONG PLUGIN OUTPUT LOGGING OPTION
+# If you want Icinga to log the complete text of the plugin output
+# to the log instead of only the first line then set this value to 1.
+# Default value is 0.
+
+log_long_plugin_output=0
+
+
+
+# GLOBAL HOST AND SERVICE EVENT HANDLERS
+# These options allow you to specify a host and service event handler
+# command that is to be run for every host or service state change.
+# The global event handler is executed immediately prior to the event
+# handler that you have optionally specified in each host or
+# service definition. The command argument is the short name of a
+# command definition that you define in your host configuration file.
+# Read the HTML docs for more information.
+
+#global_host_event_handler=somecommand
+#global_service_event_handler=somecommand
+
+
+
+# SERVICE INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" service checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all service checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)! This is not a
+# good thing for production, but is useful when testing the
+# parallelization functionality.
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+service_inter_check_delay_method=s
+
+
+
+# MAXIMUM SERVICE CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all services should
+# be completed. Default is 30 minutes.
+
+max_service_check_spread=30
+
+
+
+# SERVICE CHECK INTERLEAVE FACTOR
+# This variable determines how service checks are interleaved.
+# Interleaving the service checks allows for a more even
+# distribution of service checks and reduced load on remote
+# hosts. Setting this value to 1 is equivalent to how versions
+# of Icinga previous to 0.0.5 did service checks. Set this
+# value to s (smart) for automatic calculation of the interleave
+# factor unless you have a specific reason to change it.
+# s = Use "smart" interleave factor calculation
+# x = Use an interleave factor of x, where x is a
+# number greater than or equal to 1.
+
+service_interleave_factor=s
+
+
+
+# HOST INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" host checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all host checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)!
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+host_inter_check_delay_method=s
+
+
+
+# MAXIMUM HOST CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all hosts should
+# be completed. Default is 30 minutes.
+
+max_host_check_spread=30
+
+
+
+# MAXIMUM CONCURRENT SERVICE CHECKS
+# This option allows you to specify the maximum number of
+# service checks that can be run in parallel at any given time.
+# Specifying a value of 1 for this variable essentially prevents
+# any service checks from being parallelized. A value of 0
+# will not restrict the number of concurrent checks that are
+# being executed.
+
+max_concurrent_checks=0
+
+
+
+# HOST AND SERVICE CHECK REAPER FREQUENCY
+# This is the frequency (in seconds!) that Icinga will process
+# the results of host and service checks.
+# Lower this value in larger environments to allow faster
+# check result processing (requires more cpu power).
+
+#check_result_reaper_frequency=1
+check_result_reaper_frequency=10
+
+
+
+
+# MAX CHECK RESULT REAPER TIME
+# This is the max amount of time (in seconds) that a single
+# check result reaper event will be allowed to run before
+# returning control back to Icinga so it can perform other
+# duties.
+
+max_check_result_reaper_time=30
+
+
+
+
+# CHECK RESULT PATH
+# This is directory where Icinga stores the results of host and
+# service checks that have not yet been processed.
+#
+# Note: Make sure that only one instance of Icinga has access
+# to this directory!
+
+check_result_path=/var/lib/icinga/spool/checkresults
+
+
+
+
+# MAX CHECK RESULT FILE AGE
+# This option determines the maximum age (in seconds) which check
+# result files are considered to be valid. Files older than this
+# threshold will be mercilessly deleted without further processing.
+
+max_check_result_file_age=3600
+
+
+
+
+# MAX CHECK RESULT LIST ITEMS !!EXPERIMENTAL!!
+# This experimental option allows you to set the max number of items
+# the checkresult reaper will put onto the checkresult list for further
+# processing by the core. If there are too many, the reaping will be
+# terminated early, allowing the core to process the results sooner.
+# On larger setups, that list might grow too much, and decrease
+# performance on processing. You might experiment with that value, the
+# inner core default is set to 0, disabling that feature.
+# Values:
+# 0 = Disable max check result list items
+# number = set max check result list items
+
+#max_check_result_list_items=1024
+
+
+
+
+# CACHED HOST CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous host check is considered current.
+# Cached host states (from host checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to the host check logic.
+# Too high of a value for this option may result in inaccurate host
+# states being used by Icinga, while a lower value may result in a
+# performance hit for host checks. Use a value of 0 to disable host
+# check caching.
+
+cached_host_check_horizon=15
+
+
+
+# CACHED SERVICE CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous service check is considered current.
+# Cached service states (from service checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to predictive dependency checks.
+# Use a value of 0 to disable service check caching.
+
+cached_service_check_horizon=15
+
+
+
+# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of hosts when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# host dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_host_dependency_checks=1
+
+
+
+# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of service when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# service dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_service_dependency_checks=1
+
+
+
+# SOFT STATE DEPENDENCIES
+# This option determines whether or not Icinga will use soft state
+# information when checking host and service dependencies. Normally
+# Icinga will only use the latest hard host or service state when
+# checking dependencies. If you want it to use the latest state (regardless
+# of whether its a soft or hard state type), enable this option.
+# Values:
+# 0 = Don't use soft state dependencies (default)
+# 1 = Use soft state dependencies
+
+soft_state_dependencies=0
+
+
+
+# TIME CHANGE ADJUSTMENT THRESHOLDS
+# These options determine when Icinga will react to detected changes
+# in system time (forward into the future).
+
+#time_change_threshold=900
+
+
+
+# AUTO-RESCHEDULING OPTION
+# This option determines whether or not Icinga will attempt to
+# automatically reschedule active host and service checks to
+# "smooth" them out over time. This can help balance the load on
+# the monitoring server.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_reschedule_checks=0
+
+
+
+# AUTO-RESCHEDULING INTERVAL
+# This option determines how often (in seconds) Icinga will
+# attempt to automatically reschedule checks. This option only
+# has an effect if the auto_reschedule_checks option is enabled.
+# Default is 30 seconds.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_interval=30
+
+
+
+# AUTO-RESCHEDULING WINDOW
+# This option determines the "window" of time (in seconds) that
+# Icinga will look at when automatically rescheduling checks.
+# Only host and service checks that occur in the next X seconds
+# (determined by this variable) will be rescheduled. This option
+# only has an effect if the auto_reschedule_checks option is
+# enabled. Default is 180 seconds (3 minutes).
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_window=180
+
+
+
+# SLEEP TIME
+# This is the number of seconds to sleep between checking for system
+# events and service checks that need to be run.
+
+sleep_time=0.25
+
+
+
+# TIMEOUT VALUES
+# These options control how much time Icinga will allow various
+# types of commands to execute before killing them off. Options
+# are available for controlling maximum time allotted for
+# service checks, host checks, event handlers, notifications, the
+# ocsp command, and performance data commands. All values are in
+# seconds.
+# Increase the timeout values in case you are experiencing a lot
+# of check timeouts. Addons like e.g. check_mk will perform
+# one combined active servicecheck which could take longer than
+# the default of 60sec.
+
+#service_check_timeout=120
+service_check_timeout=60
+host_check_timeout=30
+event_handler_timeout=30
+notification_timeout=30
+ocsp_timeout=5
+perfdata_timeout=5
+
+
+
+# RETAIN STATE INFORMATION
+# This setting determines whether or not Icinga will save state
+# information for services and hosts before it shuts down. Upon
+# startup Icinga will reload all saved service and host state
+# information before starting to monitor. This is useful for
+# maintaining long-term data on state statistics, etc, but will
+# slow Icinga down a bit when it (re)starts. Since its only
+# a one-time penalty, I think its well worth the additional
+# startup delay.
+
+retain_state_information=1
+
+
+
+# STATE RETENTION FILE
+# This is the file that Icinga should use to store host and
+# service state information before it shuts down. The state
+# information in this file is also read immediately prior to
+# starting to monitor the network when Icinga is restarted.
+# This file is used only if the retain_state_information
+# variable is set to 1.
+
+state_retention_file=/var/cache/icinga/retention.dat
+
+
+
+# SYNC FILE
+# This is an advanced facility to pass a subset of retention
+# information into Icinga on a running system. This is similar
+# to the state retention file with the following difference:
+#
+# - if the last_check value is less than the current last_check,
+# then the state information is ignored (this must be specified
+# immediately after the object identifiers)
+#
+# - downtimes and comments are not identified by an id number, but
+# by other "similar characteristics". This is required to work in
+# a distributed Nagios environment
+# * downtimes: hostname, servicename (if appropriate), author,
+# comment, start_time, end_time, fixed, duration
+# * comments: hostname, servicename, author, comment
+#
+# If this variable is set, then on Icinga startup, the sync file
+# will be read after the retention file has been processed. If the
+# file is read successfully, it will be removed.
+# If the file does not exist, no error will appear.
+# There is also an API that will force a read of the sync file.
+
+#sync_retention_file=/var/cache/icinga/sync.dat
+
+
+
+# RETENTION DATA UPDATE INTERVAL
+# This setting determines how often (in minutes) that Icinga
+# will automatically save retention data during normal operation.
+# If you set this value to 0, Icinga will not save retention
+# data at regular interval, but it will still save retention
+# data before shutting down or restarting. If you have disabled
+# state retention, this option has no effect.
+
+retention_update_interval=60
+
+
+
+# USE RETAINED PROGRAM STATE
+# This setting determines whether or not Icinga will set
+# program status variables based on the values saved in the
+# retention file. If you want to use retained program status
+# information, set this value to 1. If not, set this value
+# to 0.
+
+use_retained_program_state=1
+
+
+# DUMP RETAINED HOST SERVICE STATES TO NEB
+# This setting determines wether or not Icinga will dump host
+# and service states based on the values saved in the retention
+# file to the neb modules. It will already do that on event loop
+# initialization.
+# Changed in Icinga 1.10 to disabled - re-enable if you require it.
+
+dump_retained_host_service_states_to_neb=0
+
+
+
+# USE RETAINED SCHEDULING INFO
+# This setting determines whether or not Icinga will retain
+# the scheduling info (next check time) for hosts and services
+# based on the values saved in the retention file. If you
+# If you want to use retained scheduling info, set this
+# value to 1. If not, set this value to 0.
+
+use_retained_scheduling_info=1
+
+
+
+# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
+# The following variables are used to specify specific host and
+# service attributes that should *not* be retained by Icinga during
+# program restarts.
+#
+# The values of the masks are bitwise ANDs of values specified
+# by the "MODATTR_" definitions found in include/common.h.
+# For example, if you do not want the current enabled/disabled state
+# of flap detection and event handlers for hosts to be retained, you
+# would use a value of 24 for the host attribute mask...
+# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
+
+# This mask determines what host attributes are not retained
+retained_host_attribute_mask=0
+
+# This mask determines what service attributes are not retained
+retained_service_attribute_mask=0
+
+# These two masks determine what process attributes are not retained.
+# There are two masks, because some process attributes have host and service
+# options. For example, you can disable active host checks, but leave active
+# service checks enabled.
+retained_process_host_attribute_mask=0
+retained_process_service_attribute_mask=0
+
+# These two masks determine what contact attributes are not retained.
+# There are two masks, because some contact attributes have host and
+# service options. For example, you can disable host notifications for
+# a contact, but leave service notifications enabled for them.
+retained_contact_host_attribute_mask=0
+retained_contact_service_attribute_mask=0
+
+
+
+# INTERVAL LENGTH
+# This is the seconds per unit interval as used in the
+# host/contact/service configuration files. Setting this to 60 means
+# that each interval is one minute long (60 seconds). Other settings
+# have not been tested much, so your mileage is likely to vary...
+
+interval_length=60
+
+
+
+# AGGRESSIVE HOST CHECKING OPTION
+# If you don't want to turn on aggressive host checking features, set
+# this value to 0 (the default). Otherwise set this value to 1 to
+# enable the aggressive check option. Read the docs for more info
+# on what aggressive host check is or check out the source code in
+# base/checks.c
+
+use_aggressive_host_checking=0
+
+
+
+# SERVICE CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# service checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of service checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_service_checks=1
+
+
+
+# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# service checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_service_checks=1
+
+
+
+# HOST CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# host checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of host checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_host_checks=1
+
+
+
+# PASSIVE HOST CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# host checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_host_checks=1
+
+
+
+# NOTIFICATIONS OPTION
+# This determines whether or not Icinga will sent out any host or
+# service notifications when it is initially (re)started.
+# Values: 1 = enable notifications, 0 = disable notifications
+
+enable_notifications=1
+
+
+
+# EVENT HANDLER USE OPTION
+# This determines whether or not Icinga will run any host or
+# service event handlers when it is initially (re)started. Unless
+# you're implementing redundant hosts, leave this option enabled.
+# Values: 1 = enable event handlers, 0 = disable event handlers
+
+enable_event_handlers=1
+
+
+
+# STATE BASED ESCALATION RANGES !!!Experimental!!!
+# This option allows you to enable state based escalation ranges which
+# will allow a more detailed granularity on when an escalation notification
+# may happen, adding a filter based on the current host or service state
+# when checking the escalation for notification viability.
+# This is a behavioural change to the default, and therefore intentionally
+# disabled. Enable at your own risk, as this remains an experimental feature.
+# Values: 1 = enable state based escalation ranges,
+# 0 = disable state based escalation ranges
+
+#enable_state_based_escalation_ranges=0
+
+
+
+# PROCESS PERFORMANCE DATA OPTION
+# This determines whether or not Icinga will process performance
+# data returned from service and host checks. If this option is
+# enabled, host performance data will be processed using the
+# host_perfdata_command (defined below) and service performance
+# data will be processed using the service_perfdata_command (also
+# defined below). Read the HTML docs for more information on
+# performance data.
+# Values: 1 = process performance data, 0 = do not process performance data
+
+process_performance_data=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
+# These commands are run after every host and service check is
+# performed. These commands are executed only if the
+# process_performance_data option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on performance data.
+
+#host_perfdata_command=process-host-perfdata
+#service_perfdata_command=process-service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILES
+# These files are used to store host and service performance data.
+# Performance data is only written to these files if the
+# process_performance_data option (above) is set to 1.
+
+#host_perfdata_file=/tmp/host-perfdata
+#service_perfdata_file=/tmp/service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
+# These options determine what data is written (and how) to the
+# performance data files. The templates may contain macros, special
+# characters (\t for tab, \r for carriage return, \n for newline)
+# and plain text. A newline is automatically added after each write
+# to the performance data file. Some examples of what you can do are
+# shown below.
+
+#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
+#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE MODES
+# This option determines whether or not the host and service
+# performance data files are opened in write ("w") or append ("a")
+# mode. If you want to use named pipes, you should use the special
+# pipe ("p") mode which avoid blocking at startup, otherwise you will
+# likely want the defult append ("a") mode.
+
+#host_perfdata_file_mode=a
+#service_perfdata_file_mode=a
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
+# These options determine how often (in seconds) the host and service
+# performance data files are processed using the commands defined
+# below. A value of 0 indicates the files should not be periodically
+# processed.
+
+#host_perfdata_file_processing_interval=0
+#service_perfdata_file_processing_interval=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
+# These commands are used to periodically process the host and
+# service performance data files. The interval at which the
+# processing occurs is determined by the options above.
+
+#host_perfdata_file_processing_command=process-host-perfdata-file
+#service_perfdata_file_processing_command=process-service-perfdata-file
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
+# THese options determine wether the core will process empty perfdata
+# results or not. This is needed for distributed monitoring, and intentionally
+# turned on by default.
+# If you don't require empty perfdata - saving some cpu cycles
+# on unwanted macro calculation - you can turn that off. Be careful!
+# Values: 1 = enable, 0 = disable
+
+#host_perfdata_process_empty_results=1
+#service_perfdata_process_empty_results=1
+
+
+
+# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
+# This boolean option determines whether services assigned to empty
+# host groups (host groups with no host members) will cause Icinga to
+# exit with error on start up (or during a configuration check) or not.
+# It's useful to be able to assign services to empty hostgroups when
+# configuration files or pre-cached object files are distributed to
+# various pollers, or when the process of generating Icinga config is
+# automated, or when a set of services is slowly being phased out but
+# should be kept around.
+# The default behavior if the option is not present in the main
+# configuration file is for Icinga to exit with error if services are
+# associated with host groups that have no hosts associated with them.
+
+#allow_empty_hostgroup_assignment=0
+
+
+
+# OBSESS OVER SERVICE CHECKS OPTION
+# This determines whether or not Icinga will obsess over service
+# checks and run the ocsp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over services, 0 = do not obsess (default)
+
+obsess_over_services=0
+
+
+
+# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
+# This is the command that is run for every service check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_services option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ocsp_command=somecommand
+
+
+
+# OBSESS OVER HOST CHECKS OPTION
+# This determines whether or not Icinga will obsess over host
+# checks and run the ochp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over hosts, 0 = do not obsess (default)
+
+obsess_over_hosts=0
+
+
+
+# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
+# This is the command that is run for every host check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_hosts option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ochp_command=somecommand
+
+
+
+# TRANSLATE PASSIVE HOST CHECKS OPTION
+# This determines whether or not Icinga will translate
+# DOWN/UNREACHABLE passive host check results into their proper
+# state for this instance of Icinga. This option is useful
+# if you have distributed or failover monitoring setup. In
+# these cases your other Icinga servers probably have a different
+# "view" of the network, with regards to the parent/child relationship
+# of hosts. If a distributed monitoring server thinks a host
+# is DOWN, it may actually be UNREACHABLE from the point of
+# this Icinga instance. Enabling this option will tell Icinga
+# to translate any DOWN or UNREACHABLE host states it receives
+# passively into the correct state from the view of this server.
+# Values: 1 = perform translation, 0 = do not translate (default)
+
+translate_passive_host_checks=0
+
+
+
+# PASSIVE HOST CHECKS ARE SOFT OPTION
+# This determines whether or not Icinga will treat passive host
+# checks as being HARD or SOFT. By default, a passive host check
+# result will put a host into a HARD state type. This can be changed
+# by enabling this option.
+# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
+
+passive_host_checks_are_soft=0
+
+
+
+# ORPHANED HOST/SERVICE CHECK OPTIONS
+# These options determine whether or not Icinga will periodically
+# check for orphaned host service checks. Since service checks are
+# not rescheduled until the results of their previous execution
+# instance are processed, there exists a possibility that some
+# checks may never get rescheduled. A similar situation exists for
+# host checks, although the exact scheduling details differ a bit
+# from service checks. Orphaned checks seem to be a rare
+# problem and should not happen under normal circumstances.
+# If you have problems with service checks never getting
+# rescheduled, make sure you have orphaned service checks enabled.
+# Values: 1 = enable checks, 0 = disable checks
+
+check_for_orphaned_services=1
+check_for_orphaned_hosts=1
+
+
+
+# SERVICE CHECK TIMEOUT STATE
+# This setting determines the state Icinga will report when a
+# service check times out meaning it does not respond within
+# service_check_timeout seconds. The default is set to Unknown
+# and not Critical.
+# Valid settings are:
+# c - Critical
+# u - Unknown (default)
+# w - Warning
+# o - OK
+
+service_check_timeout_state=u
+
+
+
+# SERVICE FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of service results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_service_freshness=1
+
+
+
+# SERVICE FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of service check results. If you have
+# disabled service freshness checking, this option has no effect.
+
+service_freshness_check_interval=60
+
+
+
+# HOST FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of host results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_host_freshness=0
+
+
+
+# HOST FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of host check results. If you have
+# disabled host freshness checking, this option has no effect.
+
+host_freshness_check_interval=60
+
+
+
+
+# ADDITIONAL FRESHNESS THRESHOLD LATENCY
+# This setting determines the number of seconds that Icinga
+# will add to any host and service freshness thresholds that
+# it calculates (those not explicitly specified by the user).
+
+additional_freshness_latency=15
+
+
+
+
+# FLAP DETECTION OPTION
+# This option determines whether or not Icinga will try
+# and detect hosts and services that are "flapping".
+# Flapping occurs when a host or service changes between
+# states too frequently. When Icinga detects that a
+# host or service is flapping, it will temporarily suppress
+# notifications for that host/service until it stops
+# flapping. Flap detection is very experimental, so read
+# the HTML documentation before enabling this feature!
+# Values: 1 = enable flap detection
+# 0 = disable flap detection (default)
+
+enable_flap_detection=1
+
+
+
+# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
+# Read the HTML documentation on flap detection for
+# an explanation of what this option does. This option
+# has no effect if flap detection is disabled.
+
+low_service_flap_threshold=5.0
+high_service_flap_threshold=20.0
+low_host_flap_threshold=5.0
+high_host_flap_threshold=20.0
+
+
+
+# DATE FORMAT OPTION
+# This option determines how short dates are displayed. Valid options
+# include:
+# us (MM-DD-YYYY HH:MM:SS)
+# euro (DD-MM-YYYY HH:MM:SS)
+# iso8601 (YYYY-MM-DD HH:MM:SS)
+# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
+#
+
+date_format=iso8601
+
+
+
+
+# TIMEZONE OFFSET
+# This option is used to override the default timezone that this
+# instance of Icinga runs in. If not specified, Icinga will use
+# the system configured timezone.
+#
+# NOTE: In order to display the correct timezone in the CGIs, you
+# will also need to alter the Apache directives for the CGI path
+# to include your timezone. Example:
+#
+# <Directory "/usr/local/icinga/sbin/">
+# SetEnv TZ "Australia/Brisbane"
+# ...
+# </Directory>
+
+#use_timezone=US/Mountain
+#use_timezone=Australia/Brisbane
+
+
+
+
+# P1.PL FILE LOCATION
+# This value determines where the p1.pl perl script (used by the
+# embedded Perl interpreter) is located. If you didn't compile
+# Icinga with embedded Perl support, this option has no effect.
+
+p1_file=/usr/lib/icinga/p1.pl
+
+
+
+# EMBEDDED PERL INTERPRETER OPTION
+# This option determines whether or not the embedded Perl interpreter
+# will be enabled during runtime. This option has no effect if Icinga
+# has not been compiled with support for embedded Perl.
+# This option is intentionally disabled by default, because embedded
+# perl can cause memory leaks and make Icinga unstable if not properly
+# used.
+# Only enable this setting when you really know what you are doing!
+# Values: 0 = disable interpreter, 1 = enable interpreter
+
+enable_embedded_perl=1
+
+
+
+# EMBEDDED PERL USAGE OPTION
+# This option determines whether or not Icinga will process Perl plugins
+# and scripts with the embedded Perl interpreter if the plugins/scripts
+# do not explicitly indicate whether or not it is okay to do so. Read
+# the HTML documentation on the embedded Perl interpreter for more
+# information on how this option works.
+
+use_embedded_perl_implicitly=1
+
+
+
+# EVENT HANDLERS FOR STALKED HOSTS/SERVICES
+# Allow running event handlers for stalked hosts/services in order
+# to forward to external systems.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_event_handlers_for_hosts=0
+stalking_event_handlers_for_services=0
+
+
+
+# NOTIFICATIONS FOR STALKED HOSTS/SERVICES
+# Allow notifications for stalked hosts/services globally
+# for all contacts in order to notify about a stalking
+# alert.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_notifications_for_hosts=0
+stalking_notifications_for_services=0
+
+
+
+# ILLEGAL OBJECT NAME CHARACTERS
+# This option allows you to specify illegal characters that cannot
+# be used in host names, service descriptions, or names of other
+# object types.
+
+illegal_object_name_chars=`~!$%^&*|'"<>?,()=
+
+
+
+# ILLEGAL MACRO OUTPUT CHARACTERS
+# This option allows you to specify illegal characters that are
+# stripped from macros before being used in notifications, event
+# handlers, etc. This DOES NOT affect macros used in service or
+# host check commands.
+# The following macros are stripped of the characters you specify:
+# $HOSTOUTPUT$
+# $HOSTPERFDATA$
+# $HOSTACKAUTHOR$
+# $HOSTACKCOMMENT$
+# $SERVICEOUTPUT$
+# $SERVICEPERFDATA$
+# $SERVICEACKAUTHOR$
+# $SERVICEACKCOMMENT$
+
+illegal_macro_output_chars=`~$&|'"<>
+
+
+
+# KEEP UNKNOWN MACROS
+# This option can be used to keep unknown macros within the output.
+# e.g. check_proc -C $foo$ will remain.
+# This was the default in versions older than Icinga 1.8, but now
+# the default is to remove those macros from the output, causing
+# the shell to interpret $foo and leaving a single $ there. See
+# #2291 for further information.
+# Make sure to escape single dollar signs with another '$', as the
+# docs describe. Other than that, enable this setting to revert to
+# the old behaviour.
+
+keep_unknown_macros=1
+
+
+
+# REGULAR EXPRESSION MATCHING
+# This option controls whether or not regular expression matching
+# takes place in the object config files. Regular expression
+# matching is used to match host, hostgroup, service, and service
+# group names/descriptions in some fields of various object types.
+# Values: 1 = enable regexp matching, 0 = disable regexp matching
+
+use_regexp_matching=0
+
+
+
+# "TRUE" REGULAR EXPRESSION MATCHING
+# This option controls whether or not "true" regular expression
+# matching takes place in the object config files. This option
+# only has an effect if regular expression matching is enabled
+# (see above). If this option is DISABLED, regular expression
+# matching only occurs if a string contains wildcard characters
+# (* and ?). If the option is ENABLED, regexp matching occurs
+# all the time (which can be annoying).
+# Values: 1 = enable true matching, 0 = disable true matching
+
+use_true_regexp_matching=0
+
+
+
+# ADMINISTRATOR EMAIL/PAGER ADDRESSES
+# The email and pager address of a global administrator (likely you).
+# Icinga never uses these values itself, but you can access them by
+# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
+# commands.
+
+admin_email=root@localhost
+admin_pager=pageroot@localhost
+
+
+
+# DAEMON CORE DUMP OPTION
+# This option determines whether or not Icinga is allowed to create
+# a core dump when it runs as a daemon. Note that it is generally
+# considered bad form to allow this, but it may be useful for
+# debugging purposes. Enabling this option doesn't guarantee that
+# a core file will be produced, but that's just life...
+# Values: 1 - Allow core dumps
+# 0 - Do not allow core dumps (default)
+
+daemon_dumps_core=0
+
+
+
+# LARGE INSTALLATION TWEAKS OPTION
+# This option determines whether or not Icinga will take some shortcuts
+# which can save on memory and CPU usage in large Icinga installations.
+# Read the documentation for more information on the benefits/tradeoffs
+# of enabling this option.
+# Values: 1 - Enabled tweaks
+# 0 - Disable tweaks (default)
+
+use_large_installation_tweaks=0
+
+
+
+# ENABLE ENVIRONMENT MACROS
+# This option determines whether or not Icinga will make all standard
+# macros available as environment variables when host/service checks
+# and system commands (event handlers, notifications, etc.) are
+# executed. Enabling this option can cause performance issues in
+# large installations, as it will consume a bit more memory and (more
+# importantly) consume more CPU.
+# Keep in mind that various addons/plugins will require this setting
+# to be enabled (e.g. check_oracle_health) for special usage.
+# Values: 1 - Enable environment variable macros
+# 0 - Disable environment variable macros (default)
+
+enable_environment_macros=1
+
+
+
+# CHILD PROCESS MEMORY OPTION
+# This option determines whether or not Icinga will free memory in
+# child processes (processed used to execute system commands and host/
+# service checks). If you specify a value here, it will override
+# program defaults.
+# Value: 1 - Free memory in child processes
+# 0 - Do not free memory in child processes
+
+#free_child_process_memory=1
+
+
+
+# CHILD PROCESS FORKING BEHAVIOR
+# This option determines how Icinga will fork child processes
+# (used to execute system commands and host/service checks). Normally
+# child processes are fork()ed twice, which provides a very high level
+# of isolation from problems. Fork()ing once is probably enough and will
+# save a great deal on CPU usage (in large installs), so you might
+# want to consider using this. If you specify a value here, it will
+# program defaults.
+# Value: 1 - Child processes fork() twice
+# 0 - Child processes fork() just once
+
+#child_processes_fork_twice=1
+
+
+
+# DEBUG LEVEL
+# This option determines how much (if any) debugging information will
+# be written to the debug file. OR values together to log multiple
+# types of information.
+# Values:
+# -1 = Everything
+# 0 = Nothing
+# 1 = Functions
+# 2 = Configuration
+# 4 = Process information
+# 8 = Scheduled events
+# 16 = Host/service checks
+# 32 = Notifications
+# 64 = Event broker
+# 128 = External commands
+# 256 = Commands
+# 512 = Scheduled downtime
+# 1024 = Comments
+# 2048 = Macros
+
+debug_level=0
+
+
+
+# DEBUG VERBOSITY
+# This option determines how verbose the debug log out will be.
+# Values: 0 = Brief output
+# 1 = More detailed
+# 2 = Very detailed
+
+debug_verbosity=2
+
+
+
+# DEBUG FILE
+# This option determines where Icinga should write debugging information.
+
+debug_file=/var/log/icinga/icinga.debug
+
+
+
+# MAX DEBUG FILE SIZE
+# This option determines the maximum size (in bytes) of the debug file. If
+# the file grows larger than this size, it will be renamed with a .old
+# extension. If a file already exists with a .old extension it will
+# automatically be deleted. This helps ensure your disk space usage doesn't
+# get out of control when debugging Icinga.
+
+# 100M
+max_debug_file_size=100000000
diff --git a/roles/icinga-gm/files/nt.cfg b/roles/icinga-gm/files/nt.cfg
new file mode 100644
index 0000000..b461aca
--- /dev/null
+++ b/roles/icinga-gm/files/nt.cfg
@@ -0,0 +1,15 @@
+# If you are confused about this command definition, cause you was
+# reading other suggestions, please have a look into
+# /usr/share/doc/nagios-plugins/README.Debian
+
+# 'check_nt' command definition
+#define command {
+# command_name check_nt
+# command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -v '$ARG1$'
+#}
+
+# 'check_nscp' command definition
+define command {
+ command_name check_nscp
+ command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -p 12489 -v '$ARG1$'
+}
diff --git a/roles/icinga-gm/files/services_icinga.cfg b/roles/icinga-gm/files/services_icinga.cfg
new file mode 100644
index 0000000..4ea25d8
--- /dev/null
+++ b/roles/icinga-gm/files/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-gm/handlers/main.yml b/roles/icinga-gm/handlers/main.yml
new file mode 100644
index 0000000..721651e
--- /dev/null
+++ b/roles/icinga-gm/handlers/main.yml
@@ -0,0 +1,12 @@
+---
+ - name: restart icinga
+ service: name=icinga state=restarted
+
+ - name: stop icinga
+ service: name=icinga state=stopped
+
+ - name: start icinga
+ service: name=icinga state=started
+
+ - name: restart apache
+ service: name=apache2 state=restarted
diff --git a/roles/icinga-gm/tasks/main.yml b/roles/icinga-gm/tasks/main.yml
new file mode 100644
index 0000000..ebc9c58
--- /dev/null
+++ b/roles/icinga-gm/tasks/main.yml
@@ -0,0 +1,161 @@
+---
+- name: Installation apache2
+ apt: name=apache2 state=present
+
+- name: Installation snmp
+ apt: name=snmp state=present
+
+- name: Installation de icinga
+ apt: name=icinga state=present
+
+- name: Installation de nagios-plugins
+ apt: name=nagios-plugins state=present
+
+- name: Installation de nagios-snmp-plugins
+ apt: name=nagios-snmp-plugins state=present
+
+- name: Installation des dépendances dns
+ apt: name=libnet-dns-perl state=present
+
+#- name: Copie de fichier apache.conf
+# copy: remote_src=true src=/etc/icinga/apache2.conf dest=/etc/apache2/sites-available/icinga.conf
+
+#- name: activation du site de icinga
+# shell: a2ensite icinga
+# notify:
+# - restart icinga
+
+- name: changement de mot de passe de icingaadmin
+ shell: htpasswd -dbc /etc/icinga/htpasswd.users icingaadmin root
+
+- name: Copie du fichier commands.cfg
+ copy: src=commands.cfg dest=/etc/icinga/commands.cfg
+
+- name: Copie du fichier icinga.cfg
+ copy: src=icinga.cfg dest=/etc/icinga
+
+- name: Copie du fichier contact
+ copy: src=contacts_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-test.cfg
+ copy: src=cfg/s-test.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+#- name: Copie du fichier s-proxy.cfg
+# copy: src=cfg/s-proxy.cfg dest=/etc/icinga/objects
+# notify:
+# - restart icinga
+
+- name: Copie du fichier s-adm.cfg
+ copy: src=cfg/s-adm.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+#- name: Copie du fichier r-int.cfg
+# copy: src=cfg/r-int.cfg dest=/etc/icinga/objects
+# notify:
+# - restart icinga
+
+#- name: Copie du fichier r-ext.cfg
+# copy: src=cfg/r-ext.cfg dest=/etc/icinga/objects
+# notify:
+# - restart icinga
+
+#- name: Copie du fichier netgear
+# copy: src=cfg/netgear.cfg dest=/etc/icinga/objects
+# notify:
+# - restart icinga
+
+- name: Copie du fichier serveur
+ copy: src=cfg/s-win.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+#- name: Copie du fichier gwsio2
+# copy: src=cfg/gwsio2.cfg dest=/etc/icinga/objects
+# notify:
+# - restart icinga
+
+#- name: Copie du fichier s-fog
+# copy: src=cfg/s-fog.cfg dest=/etc/icinga/objects
+# notify:
+# - restart icinga
+
+- name: Copie du fichier hostgroup
+ copy: src=hostgroups_icinga.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+- name: Copie du fichier services
+ copy: src=services_icinga.cfg dest=/etc/icinga/objects
+ notify:
+ - restart icinga
+
+#- name: attribution des droits dossier icinga rw
+# file:
+# path: /var/lib/icinga/rw
+# owner: nagios
+# mode: 2710
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- name: attribution des droits dossier icinga
+# file:
+# path: /var/lib/icinga
+# owner: nagios
+# mode: 751
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- file:
+# path: /var/lib/icinga/rw
+# state: directory
+# mode: 2770
+# notify:
+# - stop icinga
+
+#- name: attribution des droits dossier var lib icinga
+# shell: chmod 2770 /var/lib/icinga/rw
+# notify:
+# - stop icinga
+
+#- name: attribution des droits dossier var lib icinga
+# file:
+# path: /var/lib/icinga/rw
+# owner: www-data
+# mode: 2710
+# recurse: yes
+# notify:
+# - restart icinga
+
+#- service:
+# name: apache2
+# state: restarted
+# notify:
+# - start icinga
+
+#- name: attribution des droits dossier var lib icinga
+# shell: apache2ctl restart
+# notify:
+# - start icinga
+
+- name: Changement droit notif
+ shell: chmod 644 /var/log/icinga/icinga.log
+
+- name: copie nt.cfg
+ copy: src=nt.cfg dest=/etc/nagios-plugins/config
+
+#- name: copie dns.cfg
+# copy: remote_src=true src=dns.cfg dest=/etc/nagios-plugins/config
+
+- name: copie check traffic
+ copy: src=check_iftraffic3.pl dest=/usr/lib/nagios/plugins
+
+- name: modif des droits plugin traffic
+ shell: chmod 755 /usr/lib/nagios/plugins/check_iftraffic3.pl
+
+- name: message d'information
+ debug: msg="Pour superviser le Windows, il faut installer NSClient++"
diff --git a/roles/icinga-kb/files/cfg/contacts_icinga.cfg b/roles/icinga-kb/files/cfg/contacts_icinga.cfg
new file mode 100644
index 0000000..da706dc
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email kylian.barassin@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-kb/files/cfg/extinfo_icinga.cfg b/roles/icinga-kb/files/cfg/extinfo_icinga.cfg
new file mode 100644
index 0000000..07bd594
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/extinfo_icinga.cfg
@@ -0,0 +1,13 @@
+##
+## Extended Host and Service Information
+##
+
+define hostextinfo{
+ hostgroup_name debian-servers
+ notes Debian GNU/Linux servers
+# notes_url http://webserver.localhost.localdomain/hostinfo.pl?host=netware1
+ icon_image base/debian.png
+ icon_image_alt Debian GNU/Linux
+ vrml_image debian.png
+ statusmap_image base/debian.gd2
+ }
diff --git a/roles/icinga-kb/files/cfg/generic-host_icinga.cfg b/roles/icinga-kb/files/cfg/generic-host_icinga.cfg
new file mode 100644
index 0000000..e6d96ac
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/generic-host_icinga.cfg
@@ -0,0 +1,19 @@
+# Generic host definition template - This is NOT a real host, just a template!
+
+define host{
+ name generic-host ; The name of this host template
+ notifications_enabled 1 ; Host notifications are enabled
+ event_handler_enabled 1 ; Host event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ check_command check-host-alive
+ max_check_attempts 10
+ notification_interval 0
+ notification_period 24x7
+ notification_options d,u,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-kb/files/cfg/generic-service_icinga.cfg b/roles/icinga-kb/files/cfg/generic-service_icinga.cfg
new file mode 100644
index 0000000..4d60c79
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/generic-service_icinga.cfg
@@ -0,0 +1,26 @@
+# generic service template definition
+define service{
+ name generic-service ; The 'name' of this service template
+ active_checks_enabled 1 ; Active service checks are enabled
+ passive_checks_enabled 1 ; Passive service checks are enabled/accepted
+ parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems)
+ obsess_over_service 1 ; We should obsess over this service (if necessary)
+ check_freshness 0 ; Default is to NOT check service 'freshness'
+ notifications_enabled 1 ; Service notifications are enabled
+ event_handler_enabled 1 ; Service event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ notification_interval 0 ; Only send notifications on status change by default.
+ is_volatile 0
+ check_period 24x7
+ normal_check_interval 5
+ retry_check_interval 1
+ max_check_attempts 4
+ notification_period 24x7
+ notification_options w,u,c,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-kb/files/cfg/hostgroups_icinga.cfg b/roles/icinga-kb/files/cfg/hostgroups_icinga.cfg
new file mode 100644
index 0000000..6b50eca
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/hostgroups_icinga.cfg
@@ -0,0 +1,59 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-infra, r-int, r-ext, s-adm, s-lb
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-adm, r-int, r-ext, localhost, s-lb-adm, s-infra-adm
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-infra
+
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members r-int, s-win
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members s-win
+}
+
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members r-int, r-ext, s-adm, s-win, s-lb
+}
+
diff --git a/roles/icinga-kb/files/cfg/localhost.cfg b/roles/icinga-kb/files/cfg/localhost.cfg
new file mode 100644
index 0000000..4e4e190
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/localhost.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host
+ host_name localhost
+ alias Serveur monitoring
+ address localhost
+ }
+
diff --git a/roles/icinga-kb/files/cfg/localhost_icinga.cfg b/roles/icinga-kb/files/cfg/localhost_icinga.cfg
new file mode 100644
index 0000000..0764b3a
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/localhost_icinga.cfg
@@ -0,0 +1,59 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in icinga-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name localhost
+ alias localhost
+ address 127.0.0.1
+ }
+
+# Define a service to check the disk space of the root partition
+# on the local machine. Warning if < 20% free, critical if
+# < 10% free space on partition.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Disk Space
+ check_command check_all_disks!20%!10%
+ }
+
+
+
+# Define a service to check the number of currently logged in
+# users on the local machine. Warning if > 20 users, critical
+# if > 50 users.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Users
+ check_command check_users!20!50
+ }
+
+
+# Define a service to check the number of currently running procs
+# on the local machine. Warning if > 250 processes, critical if
+# > 400 processes.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Total Processes
+ check_command check_procs!250!400
+ }
+
+
+
+# Define a service to check the load on the local machine.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Load
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
diff --git a/roles/icinga-kb/files/cfg/r-ext.cfg b/roles/icinga-kb/files/cfg/r-ext.cfg
new file mode 100644
index 0000000..0844c5e
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/r-ext.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-ext
+ alias Routeur externe
+ address 192.168.200.253
+ parents r-int
+ }
diff --git a/roles/icinga-kb/files/cfg/r-int.cfg b/roles/icinga-kb/files/cfg/r-int.cfg
new file mode 100644
index 0000000..249e69f
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/r-int.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-int
+ alias Routeur interne
+ address 172.16.0.254
+ parents localhost
+ }
diff --git a/roles/icinga-kb/files/cfg/s-adm.cfg b/roles/icinga-kb/files/cfg/s-adm.cfg
new file mode 100644
index 0000000..aeadbee
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/s-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-adm
+ alias debian-servers
+ address 192.168.99.99
+ parents r-int
+ }
+
diff --git a/roles/icinga-kb/files/cfg/s-infra-adm.cfg b/roles/icinga-kb/files/cfg/s-infra-adm.cfg
new file mode 100644
index 0000000..c08df47
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/s-infra-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra-adm
+ alias debian-servers
+ address 192.168.99.1
+ parents s-adm
+ }
+
diff --git a/roles/icinga-kb/files/cfg/s-infra.cfg b/roles/icinga-kb/files/cfg/s-infra.cfg
new file mode 100644
index 0000000..c369ff6
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/s-infra.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra
+ alias debian-servers
+ address 172.16.0.1
+ parents r-int
+ }
+
diff --git a/roles/icinga-kb/files/cfg/s-lb-adm.cfg b/roles/icinga-kb/files/cfg/s-lb-adm.cfg
new file mode 100644
index 0000000..9b24f52
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/s-lb-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-lb-adm
+ alias debian-servers
+ address 192.168.99.100
+ parents s-adm
+ }
+
diff --git a/roles/icinga-kb/files/cfg/s-lb.cfg b/roles/icinga-kb/files/cfg/s-lb.cfg
new file mode 100644
index 0000000..dde599e
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/s-lb.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-lb
+ alias debian-servers
+ address 192.168.100.10
+ parents r-ext
+ }
+
diff --git a/roles/icinga-kb/files/cfg/s-win.cfg b/roles/icinga-kb/files/cfg/s-win.cfg
new file mode 100644
index 0000000..4a5bc58
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/s-win.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-win
+ alias windows-servers
+ address 172.16.0.6
+ parents r-int
+ icon_image base/win40.gif
+ statusmap_image base/win40.gd2
+ }
+
diff --git a/roles/icinga-kb/files/cfg/services_icinga.cfg b/roles/icinga-kb/files/cfg/services_icinga.cfg
new file mode 100644
index 0000000..226237f
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0 -c 6000:0 -w 60000:0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-kb/files/cfg/timeperiods_icinga.cfg b/roles/icinga-kb/files/cfg/timeperiods_icinga.cfg
new file mode 100644
index 0000000..55ecf9d
--- /dev/null
+++ b/roles/icinga-kb/files/cfg/timeperiods_icinga.cfg
@@ -0,0 +1,50 @@
+###############################################################################
+# timeperiods.cfg
+###############################################################################
+
+# This defines a timeperiod where all times are valid for checks,
+# notifications, etc. The classic "24x7" support nightmare. :-)
+
+define timeperiod{
+ timeperiod_name 24x7
+ alias 24 Hours A Day, 7 Days A Week
+ sunday 00:00-24:00
+ monday 00:00-24:00
+ tuesday 00:00-24:00
+ wednesday 00:00-24:00
+ thursday 00:00-24:00
+ friday 00:00-24:00
+ saturday 00:00-24:00
+ }
+
+# Here is a slightly friendlier period during work hours
+define timeperiod{
+ timeperiod_name workhours
+ alias Standard Work Hours
+ monday 09:00-17:00
+ tuesday 09:00-17:00
+ wednesday 09:00-17:00
+ thursday 09:00-17:00
+ friday 09:00-17:00
+ }
+
+# The complement of workhours
+define timeperiod{
+ timeperiod_name nonworkhours
+ alias Non-Work Hours
+ sunday 00:00-24:00
+ monday 00:00-09:00,17:00-24:00
+ tuesday 00:00-09:00,17:00-24:00
+ wednesday 00:00-09:00,17:00-24:00
+ thursday 00:00-09:00,17:00-24:00
+ friday 00:00-09:00,17:00-24:00
+ saturday 00:00-24:00
+ }
+
+# This one is a favorite: never :)
+define timeperiod{
+ timeperiod_name never
+ alias Never
+ }
+
+# end of file
diff --git a/roles/icinga-kb/files/check_iftraffic3.pl b/roles/icinga-kb/files/check_iftraffic3.pl
new file mode 100755
index 0000000..62ddbd1
--- /dev/null
+++ b/roles/icinga-kb/files/check_iftraffic3.pl
@@ -0,0 +1,643 @@
+#!/usr/bin/perl -w
+#
+# check_iftraffic.pl - Nagios(r) network traffic monitor plugin
+# Copyright (C) 2004 Gerd Mueller / Netways GmbH
+# $Id: check_iftraffic.pl 1119 2006-02-09 10:30:09Z gmueller $
+#
+# mw = Markus Werner mw+nagios@wobcom.de
+# Remarks (mw):
+#
+# I adopted as much as possible the programming style of the origin code.
+#
+# There should be a function to exit this programm,
+# instead of calling print and exit statements all over the place.
+#
+#
+# minor changes by mw
+# The snmp if_counters on net devices can have overflows.
+# I wrote this code to address this situation.
+# It has no automatic detection and which point the overflow
+# occurs but it will generate a warning state and you
+# can set the max value by calling this script with an additional
+# arg.
+#
+# minor cosmetic changes by mw
+# Sorry but I couldn't sustain to clean up some things.
+#
+# gj = Greg Frater gregATfraterfactory.com
+# Remarks (gj):
+# minor (gj):
+#
+# * fixed the performance data, formating was not to spec
+# * Added a check of the interfaces status (up/down).
+# If down the check returns a critical status.
+# * Allow either textual or the numeric index value.
+# * If the interface speed is not specified on the command line
+# it gets it automatically from IfSpeed
+# * Added option for second ifSpeed to allow for asymetrcal links
+# such as a DSL line or cable modem where the download and upload
+# speeds are different
+# * Added -B option to display results in bits/sec instead of Bytes/sec
+# * Added the current usage in Bytes/s (or bit/s) to the perfdata output
+# * Added ability for plugin to determine interface to query by matching IP
+# address of host with entry in ipAdEntIfIndex (.1.3.6.1.2.1.4.20.1.2)
+# * Added -L flag to list entries found in the ipAdEntIfIndex table
+# Otherwise, it works as before.
+#
+#
+#
+#
+# based on check_traffic from Adrian Wieczorek, <ads (at) irc.pila.pl>
+#
+# Send us bug reports, questions and comments about this plugin.
+# Latest version of this software: http://www.nagiosexchange.org
+#
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307
+
+use strict;
+
+use Net::SNMP;
+use Getopt::Long;
+&Getopt::Long::config('bundling');
+
+use Data::Dumper;
+
+my $host_ip;
+my $host_address;
+my $iface_number;
+my $iface_descr;
+my $iface_speed;
+my $iface_speedOut;
+my $index_list;
+my $opt_h;
+my $units;
+
+my $session;
+my $error;
+my $port = 161;
+my $snmp_version = 1;
+
+my @snmpoids;
+
+# SNMP OIDs for Traffic
+my $snmpIfOperStatus = '1.3.6.1.2.1.2.2.1.8';
+my $snmpIfInOctets = '1.3.6.1.2.1.2.2.1.10';
+my $snmpIfOutOctets = '1.3.6.1.2.1.2.2.1.16';
+my $snmpIfDescr = '1.3.6.1.2.1.2.2.1.2';
+my $snmpIfSpeed = '1.3.6.1.2.1.2.2.1.5';
+my $snmpIPAdEntIfIndex = '1.3.6.1.2.1.4.20.1.2';
+
+my $response;
+
+# Path to tmp files
+my $TRAFFIC_FILE = "/tmp/traffic";
+
+# changes sos 20090717 UNKNOWN must bes 3
+my %STATUS_CODE =
+ ( 'UNKNOWN' => '3', 'OK' => '0', 'WARNING' => '1', 'CRITICAL' => '2' );
+
+#default values;
+my $state = "UNKNOWN";
+my $if_status = '4';
+my ( $in_bytes, $out_bytes ) = 0;
+my $warn_usage = 85;
+my $crit_usage = 98;
+my $COMMUNITY = "public";
+my $use_reg = undef; # Use Regexp for name
+my $output = "";
+my $bits = undef;
+my $suffix = "Bs";
+my $label = "MBytes";
+
+#added 20050614 by mw
+my $max_value;
+my $max_bytes;
+
+#cosmetic changes 20050614 by mw, see old versions for detail
+# Added options for bits and second max ifspeed 20100202 by gj
+# Added options for specificy IP addr to match 20100405 by gj
+my $status = GetOptions(
+ "h|help" => \$opt_h,
+ 'B' => \$bits,
+ 'bits' => \$bits,
+ "C|community=s" => \$COMMUNITY,
+ "w|warning=s" => \$warn_usage,
+ "c|critical=s" => \$crit_usage,
+ "b|bandwidth|I|inBandwidth=i" => \$iface_speed,
+ "O|outBandwidth=i" => \$iface_speedOut,
+ 'r' => \$use_reg,
+ 'noregexp' => \$use_reg,
+ "p|port=i" => \$port,
+ "u|units=s" => \$units,
+ "i|interface=s" => \$iface_number,
+ "A|address=s" => \$host_ip,
+ "H|hostname=s" => \$host_address,
+ 'L' => \$index_list,
+ 'list' => \$index_list,
+
+ #added 20050614 by mw
+ "M|max=i" => \$max_value
+);
+
+if ( $status == 0 ) {
+ print_help();
+ exit $STATUS_CODE{'OK'};
+}
+
+# Changed 20091214 gj
+# Check for missing options
+#if ( ( !$host_address ) or ( !$iface_descr ) ) {
+if ( !$host_address ) {
+ print "\nMissing host address!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speed ) and ( !$units ) ){
+ print "\nMissing units!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $units ) and ( ( !$iface_speed ) and ( !$iface_speedOut ) ) ) {
+ print "\nMissing interface maximum speed!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speedOut ) and ( !$units ) ) {
+ print "\nMissing units for Out maximum speed!\n\n";
+ stop(print_usage(),"OK");
+}
+
+
+if ($bits) {
+ $suffix = "bs"
+}
+
+if ( !$iface_speed ) {
+ # Do nothing
+}else{
+
+ #change 20050414 by mw
+ # Added iface_speedOut 20100202 by gj
+ # Convert interface speed to kiloBytes
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+ if ( $iface_speedOut ) {
+ $iface_speedOut = bits2bytes( $iface_speedOut, $units ) / 1024;
+ }
+ if ( !$max_value ) {
+
+ # If no -M Parameter was set, set it to 32Bit Overflow
+ $max_bytes = 4194304 ; # the value is (2^32/1024)
+ }
+ else {
+ $max_bytes = unit2bytes( $max_value, $units );
+ }
+}
+
+if ( $snmp_version =~ /[12]/ ) {
+ ( $session, $error ) = Net::SNMP->session(
+ -hostname => $host_address,
+ -community => $COMMUNITY,
+ -port => $port,
+ -version => $snmp_version
+ );
+
+ if ( !defined($session) ) {
+ stop("UNKNOWN: $error","UNKNOWN");
+ }
+}
+elsif ( $snmp_version =~ /3/ ) {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v3 yet\n",$state);
+}
+else {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v$snmp_version yet\n",$state);
+}
+
+# Neither Interface Index nor Host IP address were specified
+if ( !$iface_descr ) {
+ if ( !$host_ip ){
+ # try to resolve host name and find index from ip addr
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_address );
+ } else {
+ # Use ip addr to find index
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_ip );
+ }
+}
+
+#push( @snmpoids, $snmpIPAdEntIfIndex . "." . $host_address );
+
+# Added 20091209 gj
+# Detect if a string description was given or a numberic interface index number
+if ( $iface_descr =~ /[^0123456789]+/ ) {
+ $iface_number = fetch_ifdescr( $session, $iface_descr );
+}else{
+ $iface_number = $iface_descr;
+}
+
+push( @snmpoids, $snmpIfSpeed . "." . $iface_number );
+push( @snmpoids, $snmpIfOperStatus . "." . $iface_number );
+push( @snmpoids, $snmpIfInOctets . "." . $iface_number );
+push( @snmpoids, $snmpIfOutOctets . "." . $iface_number );
+
+if ( !defined( $response = $session->get_request(@snmpoids) ) ) {
+ my $answer = $session->error;
+ $session->close;
+
+ stop("WARNING: SNMP error: $answer\n", "WARNING");
+}
+
+# Added 20091209 gj
+# Get interface speed from device if not provided on command line
+# Convert to kiloBytes
+if ( !$iface_speed ) {
+ $iface_speed = $response->{ $snmpIfSpeed . "." . $iface_number };
+ $units = "b";
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+}
+
+# Added 20100201 gj
+# Check if Out max speed was provided, use same if speed for both if not
+if (!$iface_speedOut) {
+ $iface_speedOut = $iface_speed;
+}
+
+$if_status = $response->{ $snmpIfOperStatus . "." . $iface_number };
+$in_bytes = $response->{ $snmpIfInOctets . "." . $iface_number } / 1024; # in kiloBytes
+$out_bytes = $response->{ $snmpIfOutOctets . "." . $iface_number } / 1024; # in kiloBytes
+
+$session->close;
+
+my $row;
+my $last_check_time = time - 1;
+my $last_in_bytes = $in_bytes;
+my $last_out_bytes = $out_bytes;
+
+if (
+ open( FILE,
+ "<" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address
+ )
+ )
+{
+ while ( $row = <FILE> ) {
+
+ #cosmetic change 20050416 by mw
+ #Couldn't sustain;-)
+## chomp();
+ ( $last_check_time, $last_in_bytes, $last_out_bytes ) =
+ split( ":", $row );
+
+ ### by sos 17.07.2009 check for last_bytes
+ if ( ! $last_in_bytes ) { $last_in_bytes=$in_bytes; }
+ if ( ! $last_out_bytes ) { $last_out_bytes=$out_bytes; }
+
+ if ($last_in_bytes !~ m/\d/) { $last_in_bytes=$in_bytes; }
+ if ($last_out_bytes !~ m/\d/) { $last_out_bytes=$out_bytes; }
+ }
+ close(FILE);
+}
+
+my $update_time = time;
+
+open( FILE, ">" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address )
+ or die "Can't open $TRAFFIC_FILE for writing: $!";
+
+printf FILE ( "%s:%.0ld:%.0ld\n", $update_time, $in_bytes, $out_bytes );
+close(FILE);
+
+my $db_file;
+
+#added 20050614 by mw
+#Check for and correct counter overflow (if possible).
+#See function counter_overflow.
+$in_bytes = counter_overflow( $in_bytes, $last_in_bytes, $max_bytes );
+$out_bytes = counter_overflow( $out_bytes, $last_out_bytes, $max_bytes );
+
+# Calculate traffic since last check (RX\TX) in kiloBytes
+my $in_traffic = sprintf( "%.2lf",
+ ( $in_bytes - $last_in_bytes ) / ( time - $last_check_time ) );
+my $out_traffic = sprintf( "%.2lf",
+ ( $out_bytes - $last_out_bytes ) / ( time - $last_check_time ) );
+
+# sos 20090717 changed due to rrdtool needs bytes
+my $in_traffic_absolut = $in_bytes * 1024 ;
+my $out_traffic_absolut = $out_bytes * 1024;
+
+# Calculate usage percentages
+my $in_usage = sprintf( "%.2f", ( 1.0 * $in_traffic * 100 ) / $iface_speed );
+my $out_usage = sprintf( "%.2f", ( 1.0 * $out_traffic * 100 ) / $iface_speedOut );
+
+
+if ($bits) {
+ # Convert output from Bytes to bits
+ $in_bytes = $in_bytes * 8;
+ $out_bytes = $out_bytes * 8;
+ $in_traffic = $in_traffic * 8;
+ $out_traffic = $out_traffic * 8;
+ $label = "Mbits";
+}
+
+my $in_prefix = "K";
+my $out_prefix = "K";
+
+if ( $in_traffic > 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 );
+ $in_prefix = "M";
+}
+if ( $out_traffic > 1024 ) {
+ $out_traffic = sprintf( "%.2f", $out_traffic / 1024 );
+ $out_prefix = "M";
+}
+if ( $in_traffic > 1024 * 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 * 1024 );
+ $in_prefix = "G";
+}
+if ( $out_traffic > 1024 * 1024 ) {
+ $out_traffic = sprintf( "%.2f",$out_traffic / 1024 * 1024 );
+ $out_prefix = "G";
+}
+
+# Convert from kiloBytes to megaBytes
+$in_bytes = sprintf( "%.2f", $in_bytes / 1024 );
+$out_bytes = sprintf( "%.2f", $out_bytes / 1024 );
+
+$state = "OK";
+
+# Added 20091209 by gj
+if ( $if_status != 1 ) {
+ $output = "Interface $iface_descr is down!";
+
+}else{
+ $output =
+ "Average IN: "
+ . $in_traffic . $in_prefix . $suffix . " (" . $in_usage . "%), "
+ . "Average OUT: " . $out_traffic . $out_prefix . $suffix . " (" . $out_usage . "%)<br>";
+ $output .= "Total RX: $in_bytes $label, Total TX: $out_bytes $label";
+}
+
+# Changed 20091209 gj
+if ( ( $in_usage > $crit_usage ) or ( $out_usage > $crit_usage ) or ( $if_status != 1 ) ) {
+ $state = "CRITICAL";
+}
+
+if ( ( $in_usage > $warn_usage )
+ or ( $out_usage > $warn_usage ) && $state eq "OK" )
+{
+ $state = "WARNING";
+}
+
+# Changed 20091209 gj
+$output = "$state - $output"
+ if ( $state ne "OK" );
+
+# Changed 20091214 gj - commas should have been semi colons
+$output .=
+"|inUsage=$in_usage%;$warn_usage;$crit_usage outUsage=$out_usage%;$warn_usage;$crit_usage"
+ . " inBandwidth=" . $in_traffic . $in_prefix . $suffix . " outBandwidth=" . $out_traffic . $out_prefix . $suffix
+ . " inAbsolut=$in_traffic_absolut outAbsolut=$out_traffic_absolut";
+
+stop($output, $state);
+
+
+sub fetch_Ip2IfIndex {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $host ) = @_;
+
+
+ # Determine if we have a host name or IP addr
+ if ( $host =~ /\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/ ){
+ #print "\nI found an IP address\n\n";
+ } else {
+ $host = get_ip ( $host );
+ #print "\nWe have a host name $host\n\n";
+ }
+
+ # Quit if results not found
+ if ( !defined( $response = $session->get_table($snmpIPAdEntIfIndex) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+
+ my %resp = %{$response};
+# foreach $key ( keys %{$response} ) {
+
+ if ( $index_list ){
+ print ("\nInterfaces found:\n");
+ print (" IP Addr\tIndex\n");
+ print ("------------------------\n");
+ }
+ # Check each returned value
+ foreach $key ( keys %resp ) {
+
+ if ( $index_list ){
+ my $index_addr = substr $key, 21;
+ print ($index_addr,"\t ",$resp{$key},"\n");
+ }
+
+ # Check for ip address mathcin in returned index results
+ if ( $key =~ /$host$/ ) {
+ $snmpkey = $resp{$key};
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $host \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+sub fetch_ifdescr {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $ifdescr ) = @_;
+
+ if ( !defined( $response = $session->get_table($snmpIfDescr) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+ foreach $key ( keys %{$response} ) {
+
+ # added 20070816 by oer: remove trailing 0 Byte for Windows :-(
+ my $resp=$response->{$key};
+ $resp =~ s/\x00//;
+
+
+ my $test = defined($use_reg)
+ ? $resp =~ /$ifdescr/
+ : $resp eq $ifdescr;
+
+ if ($test) {
+
+ ###if ( $resp =~ /^$ifdescr$/ ) {
+ ###if ( $resp =~ /$ifdescr/ ) {
+ ### print "$resp \n";
+ ###if ( $response->{$key} =~ /^$ifdescr$/ ) {
+
+ $key =~ /.*\.(\d+)$/;
+ $snmpkey = $1;
+
+ # print "$ifdescr = $key / $snmpkey \n"; #debug
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $ifdescr \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bits
+sub bits2bytes {
+ return unit2bytes(@_) / 8;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bytes
+sub unit2bytes {
+ my ( $value, $unit ) = @_;
+
+ if ( $unit eq "g" ) {
+ return $value * 1024 * 1024 * 1024;
+ }
+ elsif ( $unit eq "m" ) {
+ return $value * 1024 * 1024;
+ }
+ elsif ( $unit eq "k" ) {
+ return $value * 1024;
+ }
+ elsif ( $unit eq "b" ) {
+ return $value * 1;
+ }
+ else {
+ print "You have to supply a supported unit\n";
+ exit $STATUS_CODE{'UNKNOWN'};
+ }
+}
+
+#added 20050414 by mw
+#This function detects if an overflow occurs. If so, it returns
+#a computed value for $bytes.
+#If there is no counter overflow it simply returns the origin value of $bytes.
+#IF there is a Counter reboot wrap, just use previous output.
+sub counter_overflow {
+ my ( $bytes, $last_bytes, $max_bytes ) = @_;
+
+ $bytes += $max_bytes if ( $bytes < $last_bytes );
+ $bytes = $last_bytes if ( $bytes < $last_bytes );
+ return $bytes;
+}
+
+# Added 20100202 by gj
+# Print results and exit script
+sub stop {
+ my $result = shift;
+ my $exit_code = shift;
+ print $result . "\n";
+ exit ( $STATUS_CODE{$exit_code} );
+}
+
+# Added 20100405 by gj
+# Lookup hosts ip address
+sub get_ip {
+ use Net::DNS;
+
+ my ( $host_name ) = @_;
+
+ my $res = Net::DNS::Resolver->new;
+ my $query = $res->search($host_name);
+
+ if ($query) {
+ foreach my $rr ($query->answer) {
+ next unless $rr->type eq "A";
+ #print $rr->address, "\n";
+ return $rr->address;
+ }
+ } else {
+
+ stop("Error: IP address not resolved\n","UNKNOWN");
+ }
+}
+
+#cosmetic changes 20050614 by mw
+#Couldn't sustain "HERE";-), either.
+sub print_usage {
+ print <<EOU;
+ Usage: check_iftraffic3.pl -H host [ -C community_string ] [ -i if_index|if_descr ] [ -r ] [ -b if_max_speed_in | -I if_max_speed_in ] [ -O if_max_speed_out ] [ -u ] [ -B ] [ -A IP Address ] [ -L ] [ -M ] [ -w warn ] [ -c crit ]
+
+ Example 1: check_iftraffic3.pl -H host1 -C sneaky
+ Example 2: check_iftraffic3.pl -H host1 -C sneaky -i "Intel Pro" -r -B
+ Example 3: check_iftraffic3.pl -H host1 -C sneaky -i 5
+ Example 4: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 100 -u m
+ Example 5: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 20 -O 5 -u m
+ Example 6: check_iftraffic3.pl -H host1 -C sneaky -A 192.168.1.1 -B -b 100 -u m
+
+ Options:
+
+ -H, --host STRING or IPADDRESS
+ Check interface on the indicated host.
+ -B, --bits
+ Display results in bits per second b/s (default: Bytes/s)
+ -C, --community STRING
+ SNMP Community.
+ -r, --regexp
+ Use regexp to match NAME in description OID
+ -i, --interface STRING
+ Interface Name
+ -b, --bandwidth INTEGER
+ -I, --inBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ both IN and OUT if no second (-O) max speed is provided.
+ -O, --outBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ OUT traffic. Uses the same units value given for -b.
+ -u, --units STRING
+ g=gigabits/s,m=megabits/s,k=kilobits/s,b=bits/s. Required if -b, -I, or
+ -O are used.
+ -w, --warning INTEGER
+ % of bandwidth usage necessary to result in warning status (default: 85%)
+ -c, --critical INTEGER
+ % of bandwidth usage necessary to result in critical status (default: 98%)
+ -M, --max INTEGER
+ Max Counter Value of net devices in kilo/mega/giga/bytes.
+ -A, --address STRING (IP Address)
+ IP Address to use when determining the interface index to use. Can be
+ used when the index changes frequently or as in the case of Windows
+ servers the index is different depending on the NIC installed.
+ -L, --list FLAG (on/off)
+ Tell plugin to list available interfaces. This is not supported inside
+ of Nagios, but may be useful from the command line.
+EOU
+
+}
+
diff --git a/roles/icinga-kb/files/commands.cfg b/roles/icinga-kb/files/commands.cfg
new file mode 100644
index 0000000..1ceea2c
--- /dev/null
+++ b/roles/icinga-kb/files/commands.cfg
@@ -0,0 +1,90 @@
+###############################################################################
+# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
+###############################################################################
+
+
+################################################################################
+# NOTIFICATION COMMANDS
+################################################################################
+
+
+# 'notify-host-by-email' command definition
+define command{
+ command_name notify-host-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$
+ }
+
+# 'notify-service-by-email' command definition
+define command{
+ command_name notify-service-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$
+ }
+
+
+
+
+
+################################################################################
+# HOST CHECK COMMANDS
+################################################################################
+
+# On Debian, check-host-alive is being defined from within the
+# nagios-plugins-basic package
+define command{
+ command_name check_snmp_storage
+ command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -m $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_load
+ command_line $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -T $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_mem
+ command_line $USER1$/check_snmp_mem.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_int
+ command_line $USER1$/check_snmp_netint.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -a -m -k -M -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_iftraffic3
+ #command_name check_win_int
+ #command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$
+ #command_line $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -k -M -g -w $ARG4$ -c $ARG5$
+ command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$ -i $ARG2$ -w $ARG3$ -c $ARG4$
+}
+
+define command{
+ command_name check_snmp
+ command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
+}
+###############################
+##WINDOWS
+###############################
+
+define command{
+ command_name check_nt
+ command_line $USER1$/check_nt -H $HOSTADDRESS$ -s root -p 12489 -v $ARG1$ $ARG2$
+}
+
+################################################################################
+# PERFORMANCE DATA COMMANDS
+################################################################################
+
+
+# 'process-host-perfdata' command definition
+define command{
+ command_name process-host-perfdata
+ command_line /usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /var/lib/nagios3/host-perfdata.out
+ }
+
+
+# 'process-service-perfdata' command definition
+define command{
+ command_name process-service-perfdata
+ command_line /usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /var/lib/nagios3/service-perfdata.out
+ }
diff --git a/roles/icinga-kb/files/dns.cfg b/roles/icinga-kb/files/dns.cfg
new file mode 100644
index 0000000..5b69aca
--- /dev/null
+++ b/roles/icinga-kb/files/dns.cfg
@@ -0,0 +1,11 @@
+# 'check_dns' command definition
+define command{
+ command_name check_dns
+ command_line /usr/lib/nagios/plugins/check_dns -H www.dfco.fr -s '$HOSTADDRESS$'
+}
+
+# 'check_dig' command definition
+define command{
+ command_name check_dig
+ command_line /usr/lib/nagios/plugins/check_dig -H '$HOSTADDRESS$' -l '$ARG1$'
+}
diff --git a/roles/icinga-kb/files/icinga.cfg b/roles/icinga-kb/files/icinga.cfg
new file mode 100644
index 0000000..fde1780
--- /dev/null
+++ b/roles/icinga-kb/files/icinga.cfg
@@ -0,0 +1,1494 @@
+##############################################################################
+#
+# ICINGA.CFG - Sample Main Config File for Icinga
+#
+# Read the documentation for more information on this configuration
+# file. I've provided some comments here, but things may not be so
+# clear without further explanation.
+#
+##############################################################################
+
+
+# LOG FILE
+# This is the main log file where service and host events are logged
+# for historical purposes. This should be the first option specified
+# in the config file!!!
+
+log_file=/var/log/icinga/icinga.log
+
+# Commands definitions
+cfg_file=/etc/icinga/commands.cfg
+
+# Debian also defaults to using the check commands defined by the debian
+# nagios-plugins package
+cfg_dir=/etc/nagios-plugins/config
+
+# OBJECT CONFIGURATION FILE(S)
+# These are the object configuration files in which you define hosts,
+# host groups, contacts, contact groups, services, etc.
+# Hint: Check the docs/wiki on how to monitor remote hosts with different
+# transport methods and plugins
+
+# Debian uses by default a configuration directory where icinga-common,
+# other packages and the local admin can dump or link configuration
+# files into.
+cfg_dir=/etc/icinga/objects/
+
+# Definitions for ido2db process checks
+#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg
+
+# Definitions for broker modules like idoutils.cfg
+cfg_dir=/etc/icinga/modules
+
+
+
+# OBJECT CACHE FILE
+# This option determines where object definitions are cached when
+# Icinga starts/restarts. The CGIs read object definitions from
+# this cache file (rather than looking at the object config files
+# directly) in order to prevent inconsistencies that can occur
+# when the config files are modified after Icinga starts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the objects cache file entirely.
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+# Tip: Use that file to debug your configuration with fully resolved
+# objects like the core sees them.
+
+object_cache_file=/var/cache/icinga/objects.cache
+
+
+
+# PRE-CACHED OBJECT FILE
+# This options determines the location of the precached object file.
+# If you run Icinga with the -p command line option, it will preprocess
+# your object configuration file(s) and write the cached config to this
+# file. You can then start Icinga with the -u option to have it read
+# object definitions from this precached file, rather than the standard
+# object configuration files (see the cfg_file and cfg_dir options above).
+# Using a precached object file can speed up the time needed to (re)start
+# the Icinga process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Icinga to find our more
+# about how this feature works.
+
+precached_object_file=/var/cache/icinga/objects.precache
+
+
+
+# RESOURCE FILE
+# This is an optional resource file that contains $USERx$ macro
+# definitions. Multiple resource files can be specified by using
+# multiple resource_file definitions. The CGIs will not attempt to
+# read the contents of resource files, so information that is
+# considered to be sensitive (usernames, passwords, etc) can be
+# defined as macros in this file and restrictive permissions (600)
+# can be placed on this file.
+
+resource_file=/etc/icinga/resource.cfg
+
+
+
+# STATUS FILE
+# This is where the current status of all monitored services and
+# hosts is stored. Its contents are read and processed by the CGIs.
+# The contents of the status file are deleted every time Icinga
+# restarts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the status file entirely. This becomes handy when using other methods
+# for data retrieval (e.g. IDOUtils DB)
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+
+status_file=/var/lib/icinga/status.dat
+
+
+
+# STATUS FILE UPDATE INTERVAL
+# This option determines the frequency (in seconds) that
+# Icinga will periodically dump program, host, and
+# service status data.
+# Increase the value, if you don't require it that often.
+
+#status_update_interval=30
+status_update_interval=10
+
+
+
+# ICINGA USER
+# This determines the effective user that Icinga should run as.
+# You can either supply a username or a UID.
+
+icinga_user=nagios
+
+
+
+# ICINGA GROUP
+# This determines the effective group that Icinga should run as.
+# You can either supply a group name or a GID.
+
+icinga_group=nagios
+
+
+
+# EXTERNAL COMMAND OPTION
+# This option allows you to specify whether or not Icinga should check
+# for external commands (in the command file defined below). By default
+# Icinga will *not* check for external commands, just to be on the
+# cautious side. If you want to be able to use the CGI command interface
+# you will have to enable this.
+# Values: 0 = disable commands, 1 = enable commands
+
+check_external_commands=1
+
+
+
+# EXTERNAL COMMAND CHECK INTERVAL
+# This is the interval at which Icinga should check for external commands.
+# This value works of the interval_length you specify later. If you leave
+# that at its default value of 60 (seconds), a value of 1 here will cause
+# Icinga to check for external commands every minute. If you specify a
+# number followed by an "s" (i.e. 15s), this will be interpreted to mean
+# actual seconds rather than a multiple of the interval_length variable.
+# Note: In addition to reading the external command file at regularly
+# scheduled intervals, Icinga will also check for external commands after
+# event handlers are executed.
+# NOTE: Setting this value to -1 causes Icinga to check the external
+# command file as often as possible.
+
+#command_check_interval=15s
+command_check_interval=-1
+
+
+
+# EXTERNAL COMMAND FILE
+# This is the file that Icinga checks for external command requests.
+# It is also where the command CGI will write commands that are submitted
+# by users, so it must be writeable by the user that the web server
+# is running as (usually 'nobody'). Permissions should be set at the
+# directory level instead of on the file, as the file is deleted every
+# time its contents are processed.
+# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
+# time to do it.
+
+command_file=/var/lib/icinga/rw/icinga.cmd
+
+
+
+# EXTERNAL COMMAND BUFFER SLOTS
+# This settings is used to tweak the number of items or "slots" that
+# the Icinga daemon should allocate to the buffer that holds incoming
+# external commands before they are processed. As external commands
+# are processed by the daemon, they are removed from the buffer.
+# Increase the value, if you are using addons like check_mk supplying
+# more external commands (passive check results) than usual.
+
+#external_command_buffer_slots=32768
+external_command_buffer_slots=4096
+
+
+
+# LOCK FILE
+# This is the lockfile that Icinga will use to store its PID number
+# in when it is running in daemon mode.
+
+lock_file=/var/run/icinga/icinga.pid
+
+
+
+# TEMP FILE
+# This is a temporary file that is used as scratch space when Icinga
+# updates the status log, cleans the comment file, etc. This file
+# is created, used, and deleted throughout the time that Icinga is
+# running.
+
+temp_file=/var/cache/icinga/icinga.tmp
+
+
+
+# TEMP PATH
+# This is path where Icinga can create temp files for service and
+# host check results, etc.
+
+temp_path=/tmp
+
+
+
+# EVENT BROKER OPTIONS
+# Controls what (if any) data gets sent to the event broker.
+# Values: 0 = Broker nothing
+# -1 = Broker everything
+# <other> = See documentation
+
+event_broker_options=-1
+
+
+
+# EVENT BROKER MODULE(S)
+# ----> use the new *module definition* instead:
+# ----> http://docs.icinga.org/latest/en/objectdefinitions.html
+#
+# Example definitions can be found in the '/etc/icinga/modules/' directory.
+# If you want to enable idoutils in Debian install icinga-idoutils and copy
+# /usr/share/doc/icinga-idoutils/examples/idoutils.cfg-sample to
+# /etc/icinga/modules/idoutils.cfg.
+# Don't forget to also enable the daemon in /etc/default/icinga
+
+# LOG ROTATION METHOD
+# This is the log rotation method that Icinga should use to rotate
+# the main log file. Values are as follows..
+# n = None - don't rotate the log
+# h = Hourly rotation (top of the hour)
+# d = Daily rotation (midnight every day)
+# w = Weekly rotation (midnight on Saturday evening)
+# m = Monthly rotation (midnight last day of month)
+
+log_rotation_method=d
+
+
+
+# LOG ARCHIVE PATH
+# This is the directory where archived (rotated) log files should be
+# placed (assuming you've chosen to do log rotation).
+
+log_archive_path=/var/log/icinga/archives
+
+
+
+# LOGGING OPTIONS FOR DAEMON
+# If you want messages logged to the daemon log file (usually icinga.log).
+# Default option is 1 (yes), the other valid option is 0 (no)
+
+use_daemon_log=1
+
+
+
+# LOGGING OPTIONS FOR SYSLOG
+# If you want messages logged to the syslog facility, as well as the
+# Icinga log file set this option to 1. If not, set it to 0.
+
+use_syslog=1
+
+
+
+# SYSLOG FACILITY
+# If you enabled use_syslog you can set icinga to use a local facility
+# instead of the default.To enable set this option to 1, if not, set it to 0.
+
+use_syslog_local_facility=0
+
+
+
+# SYSLOG LOCAL FACILITY
+# If you specified the use_syslog_local_facility you can chose which
+# local facility to use. Valid values are from 0 to 7
+
+syslog_local_facility=5
+
+
+
+# NOTIFICATION LOGGING OPTION
+# If you don't want notifications to be logged, set this value to 0.
+# If notifications should be logged, set the value to 1.
+
+log_notifications=1
+
+
+
+# SERVICE RETRY LOGGING OPTION
+# If you don't want service check retries to be logged, set this value
+# to 0. If retries should be logged, set the value to 1.
+
+log_service_retries=1
+
+
+
+# HOST RETRY LOGGING OPTION
+# If you don't want host check retries to be logged, set this value to
+# 0. If retries should be logged, set the value to 1.
+
+log_host_retries=1
+
+
+
+# EVENT HANDLER LOGGING OPTION
+# If you don't want host and service event handlers to be logged, set
+# this value to 0. If event handlers should be logged, set the value
+# to 1.
+
+log_event_handlers=1
+
+
+
+# INITIAL STATES LOGGING OPTION
+# If you want Icinga to log all initial host and service states to
+# the main log file (the first time the service or host is checked)
+# you can enable this option by setting this value to 1. If you
+# are not using an external application that does long term state
+# statistics reporting, you do not need to enable this option. In
+# this case, set the value to 0.
+
+log_initial_states=0
+
+
+
+# CURRENT STATES LOGGING OPTION
+# If you don't want Icinga to log all current host and service states
+# after log has been rotated to the main log file, you can disable this
+# option by setting this value to 0. Default value is 1.
+
+log_current_states=1
+
+
+
+# EXTERNAL COMMANDS LOGGING OPTION
+# If you don't want Icinga to log external commands, set this value
+# to 0. If external commands should be logged, set this value to 1.
+# Note: This option does not include logging of passive service
+# checks - see the option below for controlling whether or not
+# passive checks are logged.
+
+log_external_commands=1
+
+
+
+# LOG ANONYMIZED EXTERNAL COMMAND AUTHOR !!EXPERIMENTAL!!
+# This option substitutes the user name on external commands with
+# the string "<anon>" if the command gets logged. It is
+# anonymized in log files only. This option was added to make
+# icinga compliant with data retention laws on various countries.
+# This option is disabled by default.
+
+log_anonymized_external_command_author=0
+
+
+
+# PASSIVE CHECKS LOGGING OPTION
+# If you don't want Icinga to log passive host and service checks, set
+# this value to 0. If passive checks should be logged, set
+# this value to 1.
+
+log_passive_checks=1
+
+
+
+# LONG PLUGIN OUTPUT LOGGING OPTION
+# If you want Icinga to log the complete text of the plugin output
+# to the log instead of only the first line then set this value to 1.
+# Default value is 0.
+
+log_long_plugin_output=0
+
+
+
+# GLOBAL HOST AND SERVICE EVENT HANDLERS
+# These options allow you to specify a host and service event handler
+# command that is to be run for every host or service state change.
+# The global event handler is executed immediately prior to the event
+# handler that you have optionally specified in each host or
+# service definition. The command argument is the short name of a
+# command definition that you define in your host configuration file.
+# Read the HTML docs for more information.
+
+#global_host_event_handler=somecommand
+#global_service_event_handler=somecommand
+
+
+
+# SERVICE INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" service checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all service checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)! This is not a
+# good thing for production, but is useful when testing the
+# parallelization functionality.
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+service_inter_check_delay_method=s
+
+
+
+# MAXIMUM SERVICE CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all services should
+# be completed. Default is 30 minutes.
+
+max_service_check_spread=30
+
+
+
+# SERVICE CHECK INTERLEAVE FACTOR
+# This variable determines how service checks are interleaved.
+# Interleaving the service checks allows for a more even
+# distribution of service checks and reduced load on remote
+# hosts. Setting this value to 1 is equivalent to how versions
+# of Icinga previous to 0.0.5 did service checks. Set this
+# value to s (smart) for automatic calculation of the interleave
+# factor unless you have a specific reason to change it.
+# s = Use "smart" interleave factor calculation
+# x = Use an interleave factor of x, where x is a
+# number greater than or equal to 1.
+
+service_interleave_factor=s
+
+
+
+# HOST INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" host checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all host checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)!
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+host_inter_check_delay_method=s
+
+
+
+# MAXIMUM HOST CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all hosts should
+# be completed. Default is 30 minutes.
+
+max_host_check_spread=30
+
+
+
+# MAXIMUM CONCURRENT SERVICE CHECKS
+# This option allows you to specify the maximum number of
+# service checks that can be run in parallel at any given time.
+# Specifying a value of 1 for this variable essentially prevents
+# any service checks from being parallelized. A value of 0
+# will not restrict the number of concurrent checks that are
+# being executed.
+
+max_concurrent_checks=0
+
+
+
+# HOST AND SERVICE CHECK REAPER FREQUENCY
+# This is the frequency (in seconds!) that Icinga will process
+# the results of host and service checks.
+# Lower this value in larger environments to allow faster
+# check result processing (requires more cpu power).
+
+#check_result_reaper_frequency=1
+check_result_reaper_frequency=10
+
+
+
+
+# MAX CHECK RESULT REAPER TIME
+# This is the max amount of time (in seconds) that a single
+# check result reaper event will be allowed to run before
+# returning control back to Icinga so it can perform other
+# duties.
+
+max_check_result_reaper_time=30
+
+
+
+
+# CHECK RESULT PATH
+# This is directory where Icinga stores the results of host and
+# service checks that have not yet been processed.
+#
+# Note: Make sure that only one instance of Icinga has access
+# to this directory!
+
+check_result_path=/var/lib/icinga/spool/checkresults
+
+
+
+
+# MAX CHECK RESULT FILE AGE
+# This option determines the maximum age (in seconds) which check
+# result files are considered to be valid. Files older than this
+# threshold will be mercilessly deleted without further processing.
+
+max_check_result_file_age=3600
+
+
+
+
+# MAX CHECK RESULT LIST ITEMS !!EXPERIMENTAL!!
+# This experimental option allows you to set the max number of items
+# the checkresult reaper will put onto the checkresult list for further
+# processing by the core. If there are too many, the reaping will be
+# terminated early, allowing the core to process the results sooner.
+# On larger setups, that list might grow too much, and decrease
+# performance on processing. You might experiment with that value, the
+# inner core default is set to 0, disabling that feature.
+# Values:
+# 0 = Disable max check result list items
+# number = set max check result list items
+
+#max_check_result_list_items=1024
+
+
+
+
+# CACHED HOST CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous host check is considered current.
+# Cached host states (from host checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to the host check logic.
+# Too high of a value for this option may result in inaccurate host
+# states being used by Icinga, while a lower value may result in a
+# performance hit for host checks. Use a value of 0 to disable host
+# check caching.
+
+cached_host_check_horizon=15
+
+
+
+# CACHED SERVICE CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous service check is considered current.
+# Cached service states (from service checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to predictive dependency checks.
+# Use a value of 0 to disable service check caching.
+
+cached_service_check_horizon=15
+
+
+
+# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of hosts when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# host dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_host_dependency_checks=1
+
+
+
+# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of service when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# service dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_service_dependency_checks=1
+
+
+
+# SOFT STATE DEPENDENCIES
+# This option determines whether or not Icinga will use soft state
+# information when checking host and service dependencies. Normally
+# Icinga will only use the latest hard host or service state when
+# checking dependencies. If you want it to use the latest state (regardless
+# of whether its a soft or hard state type), enable this option.
+# Values:
+# 0 = Don't use soft state dependencies (default)
+# 1 = Use soft state dependencies
+
+soft_state_dependencies=0
+
+
+
+# TIME CHANGE ADJUSTMENT THRESHOLDS
+# These options determine when Icinga will react to detected changes
+# in system time (forward into the future).
+
+#time_change_threshold=900
+
+
+
+# AUTO-RESCHEDULING OPTION
+# This option determines whether or not Icinga will attempt to
+# automatically reschedule active host and service checks to
+# "smooth" them out over time. This can help balance the load on
+# the monitoring server.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_reschedule_checks=0
+
+
+
+# AUTO-RESCHEDULING INTERVAL
+# This option determines how often (in seconds) Icinga will
+# attempt to automatically reschedule checks. This option only
+# has an effect if the auto_reschedule_checks option is enabled.
+# Default is 30 seconds.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_interval=30
+
+
+
+# AUTO-RESCHEDULING WINDOW
+# This option determines the "window" of time (in seconds) that
+# Icinga will look at when automatically rescheduling checks.
+# Only host and service checks that occur in the next X seconds
+# (determined by this variable) will be rescheduled. This option
+# only has an effect if the auto_reschedule_checks option is
+# enabled. Default is 180 seconds (3 minutes).
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_window=180
+
+
+
+# SLEEP TIME
+# This is the number of seconds to sleep between checking for system
+# events and service checks that need to be run.
+
+sleep_time=0.25
+
+
+
+# TIMEOUT VALUES
+# These options control how much time Icinga will allow various
+# types of commands to execute before killing them off. Options
+# are available for controlling maximum time allotted for
+# service checks, host checks, event handlers, notifications, the
+# ocsp command, and performance data commands. All values are in
+# seconds.
+# Increase the timeout values in case you are experiencing a lot
+# of check timeouts. Addons like e.g. check_mk will perform
+# one combined active servicecheck which could take longer than
+# the default of 60sec.
+
+#service_check_timeout=120
+service_check_timeout=60
+host_check_timeout=30
+event_handler_timeout=30
+notification_timeout=30
+ocsp_timeout=5
+perfdata_timeout=5
+
+
+
+# RETAIN STATE INFORMATION
+# This setting determines whether or not Icinga will save state
+# information for services and hosts before it shuts down. Upon
+# startup Icinga will reload all saved service and host state
+# information before starting to monitor. This is useful for
+# maintaining long-term data on state statistics, etc, but will
+# slow Icinga down a bit when it (re)starts. Since its only
+# a one-time penalty, I think its well worth the additional
+# startup delay.
+
+retain_state_information=1
+
+
+
+# STATE RETENTION FILE
+# This is the file that Icinga should use to store host and
+# service state information before it shuts down. The state
+# information in this file is also read immediately prior to
+# starting to monitor the network when Icinga is restarted.
+# This file is used only if the retain_state_information
+# variable is set to 1.
+
+state_retention_file=/var/cache/icinga/retention.dat
+
+
+
+# SYNC FILE
+# This is an advanced facility to pass a subset of retention
+# information into Icinga on a running system. This is similar
+# to the state retention file with the following difference:
+#
+# - if the last_check value is less than the current last_check,
+# then the state information is ignored (this must be specified
+# immediately after the object identifiers)
+#
+# - downtimes and comments are not identified by an id number, but
+# by other "similar characteristics". This is required to work in
+# a distributed Nagios environment
+# * downtimes: hostname, servicename (if appropriate), author,
+# comment, start_time, end_time, fixed, duration
+# * comments: hostname, servicename, author, comment
+#
+# If this variable is set, then on Icinga startup, the sync file
+# will be read after the retention file has been processed. If the
+# file is read successfully, it will be removed.
+# If the file does not exist, no error will appear.
+# There is also an API that will force a read of the sync file.
+
+#sync_retention_file=/var/cache/icinga/sync.dat
+
+
+
+# RETENTION DATA UPDATE INTERVAL
+# This setting determines how often (in minutes) that Icinga
+# will automatically save retention data during normal operation.
+# If you set this value to 0, Icinga will not save retention
+# data at regular interval, but it will still save retention
+# data before shutting down or restarting. If you have disabled
+# state retention, this option has no effect.
+
+retention_update_interval=60
+
+
+
+# USE RETAINED PROGRAM STATE
+# This setting determines whether or not Icinga will set
+# program status variables based on the values saved in the
+# retention file. If you want to use retained program status
+# information, set this value to 1. If not, set this value
+# to 0.
+
+use_retained_program_state=1
+
+
+# DUMP RETAINED HOST SERVICE STATES TO NEB
+# This setting determines wether or not Icinga will dump host
+# and service states based on the values saved in the retention
+# file to the neb modules. It will already do that on event loop
+# initialization.
+# Changed in Icinga 1.10 to disabled - re-enable if you require it.
+
+dump_retained_host_service_states_to_neb=0
+
+
+
+# USE RETAINED SCHEDULING INFO
+# This setting determines whether or not Icinga will retain
+# the scheduling info (next check time) for hosts and services
+# based on the values saved in the retention file. If you
+# If you want to use retained scheduling info, set this
+# value to 1. If not, set this value to 0.
+
+use_retained_scheduling_info=1
+
+
+
+# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
+# The following variables are used to specify specific host and
+# service attributes that should *not* be retained by Icinga during
+# program restarts.
+#
+# The values of the masks are bitwise ANDs of values specified
+# by the "MODATTR_" definitions found in include/common.h.
+# For example, if you do not want the current enabled/disabled state
+# of flap detection and event handlers for hosts to be retained, you
+# would use a value of 24 for the host attribute mask...
+# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
+
+# This mask determines what host attributes are not retained
+retained_host_attribute_mask=0
+
+# This mask determines what service attributes are not retained
+retained_service_attribute_mask=0
+
+# These two masks determine what process attributes are not retained.
+# There are two masks, because some process attributes have host and service
+# options. For example, you can disable active host checks, but leave active
+# service checks enabled.
+retained_process_host_attribute_mask=0
+retained_process_service_attribute_mask=0
+
+# These two masks determine what contact attributes are not retained.
+# There are two masks, because some contact attributes have host and
+# service options. For example, you can disable host notifications for
+# a contact, but leave service notifications enabled for them.
+retained_contact_host_attribute_mask=0
+retained_contact_service_attribute_mask=0
+
+
+
+# INTERVAL LENGTH
+# This is the seconds per unit interval as used in the
+# host/contact/service configuration files. Setting this to 60 means
+# that each interval is one minute long (60 seconds). Other settings
+# have not been tested much, so your mileage is likely to vary...
+
+interval_length=60
+
+
+
+# AGGRESSIVE HOST CHECKING OPTION
+# If you don't want to turn on aggressive host checking features, set
+# this value to 0 (the default). Otherwise set this value to 1 to
+# enable the aggressive check option. Read the docs for more info
+# on what aggressive host check is or check out the source code in
+# base/checks.c
+
+use_aggressive_host_checking=0
+
+
+
+# SERVICE CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# service checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of service checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_service_checks=1
+
+
+
+# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# service checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_service_checks=1
+
+
+
+# HOST CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# host checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of host checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_host_checks=1
+
+
+
+# PASSIVE HOST CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# host checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_host_checks=1
+
+
+
+# NOTIFICATIONS OPTION
+# This determines whether or not Icinga will sent out any host or
+# service notifications when it is initially (re)started.
+# Values: 1 = enable notifications, 0 = disable notifications
+
+enable_notifications=1
+
+
+
+# EVENT HANDLER USE OPTION
+# This determines whether or not Icinga will run any host or
+# service event handlers when it is initially (re)started. Unless
+# you're implementing redundant hosts, leave this option enabled.
+# Values: 1 = enable event handlers, 0 = disable event handlers
+
+enable_event_handlers=1
+
+
+
+# STATE BASED ESCALATION RANGES !!!Experimental!!!
+# This option allows you to enable state based escalation ranges which
+# will allow a more detailed granularity on when an escalation notification
+# may happen, adding a filter based on the current host or service state
+# when checking the escalation for notification viability.
+# This is a behavioural change to the default, and therefore intentionally
+# disabled. Enable at your own risk, as this remains an experimental feature.
+# Values: 1 = enable state based escalation ranges,
+# 0 = disable state based escalation ranges
+
+#enable_state_based_escalation_ranges=0
+
+
+
+# PROCESS PERFORMANCE DATA OPTION
+# This determines whether or not Icinga will process performance
+# data returned from service and host checks. If this option is
+# enabled, host performance data will be processed using the
+# host_perfdata_command (defined below) and service performance
+# data will be processed using the service_perfdata_command (also
+# defined below). Read the HTML docs for more information on
+# performance data.
+# Values: 1 = process performance data, 0 = do not process performance data
+
+process_performance_data=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
+# These commands are run after every host and service check is
+# performed. These commands are executed only if the
+# process_performance_data option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on performance data.
+
+#host_perfdata_command=process-host-perfdata
+#service_perfdata_command=process-service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILES
+# These files are used to store host and service performance data.
+# Performance data is only written to these files if the
+# process_performance_data option (above) is set to 1.
+
+#host_perfdata_file=/tmp/host-perfdata
+#service_perfdata_file=/tmp/service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
+# These options determine what data is written (and how) to the
+# performance data files. The templates may contain macros, special
+# characters (\t for tab, \r for carriage return, \n for newline)
+# and plain text. A newline is automatically added after each write
+# to the performance data file. Some examples of what you can do are
+# shown below.
+
+#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
+#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE MODES
+# This option determines whether or not the host and service
+# performance data files are opened in write ("w") or append ("a")
+# mode. If you want to use named pipes, you should use the special
+# pipe ("p") mode which avoid blocking at startup, otherwise you will
+# likely want the defult append ("a") mode.
+
+#host_perfdata_file_mode=a
+#service_perfdata_file_mode=a
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
+# These options determine how often (in seconds) the host and service
+# performance data files are processed using the commands defined
+# below. A value of 0 indicates the files should not be periodically
+# processed.
+
+#host_perfdata_file_processing_interval=0
+#service_perfdata_file_processing_interval=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
+# These commands are used to periodically process the host and
+# service performance data files. The interval at which the
+# processing occurs is determined by the options above.
+
+#host_perfdata_file_processing_command=process-host-perfdata-file
+#service_perfdata_file_processing_command=process-service-perfdata-file
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
+# THese options determine wether the core will process empty perfdata
+# results or not. This is needed for distributed monitoring, and intentionally
+# turned on by default.
+# If you don't require empty perfdata - saving some cpu cycles
+# on unwanted macro calculation - you can turn that off. Be careful!
+# Values: 1 = enable, 0 = disable
+
+#host_perfdata_process_empty_results=1
+#service_perfdata_process_empty_results=1
+
+
+
+# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
+# This boolean option determines whether services assigned to empty
+# host groups (host groups with no host members) will cause Icinga to
+# exit with error on start up (or during a configuration check) or not.
+# It's useful to be able to assign services to empty hostgroups when
+# configuration files or pre-cached object files are distributed to
+# various pollers, or when the process of generating Icinga config is
+# automated, or when a set of services is slowly being phased out but
+# should be kept around.
+# The default behavior if the option is not present in the main
+# configuration file is for Icinga to exit with error if services are
+# associated with host groups that have no hosts associated with them.
+
+#allow_empty_hostgroup_assignment=0
+
+
+
+# OBSESS OVER SERVICE CHECKS OPTION
+# This determines whether or not Icinga will obsess over service
+# checks and run the ocsp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over services, 0 = do not obsess (default)
+
+obsess_over_services=0
+
+
+
+# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
+# This is the command that is run for every service check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_services option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ocsp_command=somecommand
+
+
+
+# OBSESS OVER HOST CHECKS OPTION
+# This determines whether or not Icinga will obsess over host
+# checks and run the ochp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over hosts, 0 = do not obsess (default)
+
+obsess_over_hosts=0
+
+
+
+# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
+# This is the command that is run for every host check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_hosts option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ochp_command=somecommand
+
+
+
+# TRANSLATE PASSIVE HOST CHECKS OPTION
+# This determines whether or not Icinga will translate
+# DOWN/UNREACHABLE passive host check results into their proper
+# state for this instance of Icinga. This option is useful
+# if you have distributed or failover monitoring setup. In
+# these cases your other Icinga servers probably have a different
+# "view" of the network, with regards to the parent/child relationship
+# of hosts. If a distributed monitoring server thinks a host
+# is DOWN, it may actually be UNREACHABLE from the point of
+# this Icinga instance. Enabling this option will tell Icinga
+# to translate any DOWN or UNREACHABLE host states it receives
+# passively into the correct state from the view of this server.
+# Values: 1 = perform translation, 0 = do not translate (default)
+
+translate_passive_host_checks=0
+
+
+
+# PASSIVE HOST CHECKS ARE SOFT OPTION
+# This determines whether or not Icinga will treat passive host
+# checks as being HARD or SOFT. By default, a passive host check
+# result will put a host into a HARD state type. This can be changed
+# by enabling this option.
+# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
+
+passive_host_checks_are_soft=0
+
+
+
+# ORPHANED HOST/SERVICE CHECK OPTIONS
+# These options determine whether or not Icinga will periodically
+# check for orphaned host service checks. Since service checks are
+# not rescheduled until the results of their previous execution
+# instance are processed, there exists a possibility that some
+# checks may never get rescheduled. A similar situation exists for
+# host checks, although the exact scheduling details differ a bit
+# from service checks. Orphaned checks seem to be a rare
+# problem and should not happen under normal circumstances.
+# If you have problems with service checks never getting
+# rescheduled, make sure you have orphaned service checks enabled.
+# Values: 1 = enable checks, 0 = disable checks
+
+check_for_orphaned_services=1
+check_for_orphaned_hosts=1
+
+
+
+# SERVICE CHECK TIMEOUT STATE
+# This setting determines the state Icinga will report when a
+# service check times out meaning it does not respond within
+# service_check_timeout seconds. The default is set to Unknown
+# and not Critical.
+# Valid settings are:
+# c - Critical
+# u - Unknown (default)
+# w - Warning
+# o - OK
+
+service_check_timeout_state=u
+
+
+
+# SERVICE FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of service results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_service_freshness=1
+
+
+
+# SERVICE FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of service check results. If you have
+# disabled service freshness checking, this option has no effect.
+
+service_freshness_check_interval=60
+
+
+
+# HOST FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of host results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_host_freshness=0
+
+
+
+# HOST FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of host check results. If you have
+# disabled host freshness checking, this option has no effect.
+
+host_freshness_check_interval=60
+
+
+
+
+# ADDITIONAL FRESHNESS THRESHOLD LATENCY
+# This setting determines the number of seconds that Icinga
+# will add to any host and service freshness thresholds that
+# it calculates (those not explicitly specified by the user).
+
+additional_freshness_latency=15
+
+
+
+
+# FLAP DETECTION OPTION
+# This option determines whether or not Icinga will try
+# and detect hosts and services that are "flapping".
+# Flapping occurs when a host or service changes between
+# states too frequently. When Icinga detects that a
+# host or service is flapping, it will temporarily suppress
+# notifications for that host/service until it stops
+# flapping. Flap detection is very experimental, so read
+# the HTML documentation before enabling this feature!
+# Values: 1 = enable flap detection
+# 0 = disable flap detection (default)
+
+enable_flap_detection=1
+
+
+
+# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
+# Read the HTML documentation on flap detection for
+# an explanation of what this option does. This option
+# has no effect if flap detection is disabled.
+
+low_service_flap_threshold=5.0
+high_service_flap_threshold=20.0
+low_host_flap_threshold=5.0
+high_host_flap_threshold=20.0
+
+
+
+# DATE FORMAT OPTION
+# This option determines how short dates are displayed. Valid options
+# include:
+# us (MM-DD-YYYY HH:MM:SS)
+# euro (DD-MM-YYYY HH:MM:SS)
+# iso8601 (YYYY-MM-DD HH:MM:SS)
+# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
+#
+
+date_format=iso8601
+
+
+
+
+# TIMEZONE OFFSET
+# This option is used to override the default timezone that this
+# instance of Icinga runs in. If not specified, Icinga will use
+# the system configured timezone.
+#
+# NOTE: In order to display the correct timezone in the CGIs, you
+# will also need to alter the Apache directives for the CGI path
+# to include your timezone. Example:
+#
+# <Directory "/usr/local/icinga/sbin/">
+# SetEnv TZ "Australia/Brisbane"
+# ...
+# </Directory>
+
+#use_timezone=US/Mountain
+#use_timezone=Australia/Brisbane
+
+
+
+
+# P1.PL FILE LOCATION
+# This value determines where the p1.pl perl script (used by the
+# embedded Perl interpreter) is located. If you didn't compile
+# Icinga with embedded Perl support, this option has no effect.
+
+p1_file=/usr/lib/icinga/p1.pl
+
+
+
+# EMBEDDED PERL INTERPRETER OPTION
+# This option determines whether or not the embedded Perl interpreter
+# will be enabled during runtime. This option has no effect if Icinga
+# has not been compiled with support for embedded Perl.
+# This option is intentionally disabled by default, because embedded
+# perl can cause memory leaks and make Icinga unstable if not properly
+# used.
+# Only enable this setting when you really know what you are doing!
+# Values: 0 = disable interpreter, 1 = enable interpreter
+
+enable_embedded_perl=1
+
+
+
+# EMBEDDED PERL USAGE OPTION
+# This option determines whether or not Icinga will process Perl plugins
+# and scripts with the embedded Perl interpreter if the plugins/scripts
+# do not explicitly indicate whether or not it is okay to do so. Read
+# the HTML documentation on the embedded Perl interpreter for more
+# information on how this option works.
+
+use_embedded_perl_implicitly=1
+
+
+
+# EVENT HANDLERS FOR STALKED HOSTS/SERVICES
+# Allow running event handlers for stalked hosts/services in order
+# to forward to external systems.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_event_handlers_for_hosts=0
+stalking_event_handlers_for_services=0
+
+
+
+# NOTIFICATIONS FOR STALKED HOSTS/SERVICES
+# Allow notifications for stalked hosts/services globally
+# for all contacts in order to notify about a stalking
+# alert.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_notifications_for_hosts=0
+stalking_notifications_for_services=0
+
+
+
+# ILLEGAL OBJECT NAME CHARACTERS
+# This option allows you to specify illegal characters that cannot
+# be used in host names, service descriptions, or names of other
+# object types.
+
+illegal_object_name_chars=`~!$%^&*|'"<>?,()=
+
+
+
+# ILLEGAL MACRO OUTPUT CHARACTERS
+# This option allows you to specify illegal characters that are
+# stripped from macros before being used in notifications, event
+# handlers, etc. This DOES NOT affect macros used in service or
+# host check commands.
+# The following macros are stripped of the characters you specify:
+# $HOSTOUTPUT$
+# $HOSTPERFDATA$
+# $HOSTACKAUTHOR$
+# $HOSTACKCOMMENT$
+# $SERVICEOUTPUT$
+# $SERVICEPERFDATA$
+# $SERVICEACKAUTHOR$
+# $SERVICEACKCOMMENT$
+
+illegal_macro_output_chars=`~$&|'"<>
+
+
+
+# KEEP UNKNOWN MACROS
+# This option can be used to keep unknown macros within the output.
+# e.g. check_proc -C $foo$ will remain.
+# This was the default in versions older than Icinga 1.8, but now
+# the default is to remove those macros from the output, causing
+# the shell to interpret $foo and leaving a single $ there. See
+# #2291 for further information.
+# Make sure to escape single dollar signs with another '$', as the
+# docs describe. Other than that, enable this setting to revert to
+# the old behaviour.
+
+keep_unknown_macros=1
+
+
+
+# REGULAR EXPRESSION MATCHING
+# This option controls whether or not regular expression matching
+# takes place in the object config files. Regular expression
+# matching is used to match host, hostgroup, service, and service
+# group names/descriptions in some fields of various object types.
+# Values: 1 = enable regexp matching, 0 = disable regexp matching
+
+use_regexp_matching=0
+
+
+
+# "TRUE" REGULAR EXPRESSION MATCHING
+# This option controls whether or not "true" regular expression
+# matching takes place in the object config files. This option
+# only has an effect if regular expression matching is enabled
+# (see above). If this option is DISABLED, regular expression
+# matching only occurs if a string contains wildcard characters
+# (* and ?). If the option is ENABLED, regexp matching occurs
+# all the time (which can be annoying).
+# Values: 1 = enable true matching, 0 = disable true matching
+
+use_true_regexp_matching=0
+
+
+
+# ADMINISTRATOR EMAIL/PAGER ADDRESSES
+# The email and pager address of a global administrator (likely you).
+# Icinga never uses these values itself, but you can access them by
+# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
+# commands.
+
+admin_email=root@localhost
+admin_pager=pageroot@localhost
+
+
+
+# DAEMON CORE DUMP OPTION
+# This option determines whether or not Icinga is allowed to create
+# a core dump when it runs as a daemon. Note that it is generally
+# considered bad form to allow this, but it may be useful for
+# debugging purposes. Enabling this option doesn't guarantee that
+# a core file will be produced, but that's just life...
+# Values: 1 - Allow core dumps
+# 0 - Do not allow core dumps (default)
+
+daemon_dumps_core=0
+
+
+
+# LARGE INSTALLATION TWEAKS OPTION
+# This option determines whether or not Icinga will take some shortcuts
+# which can save on memory and CPU usage in large Icinga installations.
+# Read the documentation for more information on the benefits/tradeoffs
+# of enabling this option.
+# Values: 1 - Enabled tweaks
+# 0 - Disable tweaks (default)
+
+use_large_installation_tweaks=0
+
+
+
+# ENABLE ENVIRONMENT MACROS
+# This option determines whether or not Icinga will make all standard
+# macros available as environment variables when host/service checks
+# and system commands (event handlers, notifications, etc.) are
+# executed. Enabling this option can cause performance issues in
+# large installations, as it will consume a bit more memory and (more
+# importantly) consume more CPU.
+# Keep in mind that various addons/plugins will require this setting
+# to be enabled (e.g. check_oracle_health) for special usage.
+# Values: 1 - Enable environment variable macros
+# 0 - Disable environment variable macros (default)
+
+enable_environment_macros=1
+
+
+
+# CHILD PROCESS MEMORY OPTION
+# This option determines whether or not Icinga will free memory in
+# child processes (processed used to execute system commands and host/
+# service checks). If you specify a value here, it will override
+# program defaults.
+# Value: 1 - Free memory in child processes
+# 0 - Do not free memory in child processes
+
+#free_child_process_memory=1
+
+
+
+# CHILD PROCESS FORKING BEHAVIOR
+# This option determines how Icinga will fork child processes
+# (used to execute system commands and host/service checks). Normally
+# child processes are fork()ed twice, which provides a very high level
+# of isolation from problems. Fork()ing once is probably enough and will
+# save a great deal on CPU usage (in large installs), so you might
+# want to consider using this. If you specify a value here, it will
+# program defaults.
+# Value: 1 - Child processes fork() twice
+# 0 - Child processes fork() just once
+
+#child_processes_fork_twice=1
+
+
+
+# DEBUG LEVEL
+# This option determines how much (if any) debugging information will
+# be written to the debug file. OR values together to log multiple
+# types of information.
+# Values:
+# -1 = Everything
+# 0 = Nothing
+# 1 = Functions
+# 2 = Configuration
+# 4 = Process information
+# 8 = Scheduled events
+# 16 = Host/service checks
+# 32 = Notifications
+# 64 = Event broker
+# 128 = External commands
+# 256 = Commands
+# 512 = Scheduled downtime
+# 1024 = Comments
+# 2048 = Macros
+
+debug_level=0
+
+
+
+# DEBUG VERBOSITY
+# This option determines how verbose the debug log out will be.
+# Values: 0 = Brief output
+# 1 = More detailed
+# 2 = Very detailed
+
+debug_verbosity=2
+
+
+
+# DEBUG FILE
+# This option determines where Icinga should write debugging information.
+
+debug_file=/var/log/icinga/icinga.debug
+
+
+
+# MAX DEBUG FILE SIZE
+# This option determines the maximum size (in bytes) of the debug file. If
+# the file grows larger than this size, it will be renamed with a .old
+# extension. If a file already exists with a .old extension it will
+# automatically be deleted. This helps ensure your disk space usage doesn't
+# get out of control when debugging Icinga.
+
+# 100M
+max_debug_file_size=100000000
diff --git a/roles/icinga-kb/files/nt.cfg b/roles/icinga-kb/files/nt.cfg
new file mode 100644
index 0000000..b461aca
--- /dev/null
+++ b/roles/icinga-kb/files/nt.cfg
@@ -0,0 +1,15 @@
+# If you are confused about this command definition, cause you was
+# reading other suggestions, please have a look into
+# /usr/share/doc/nagios-plugins/README.Debian
+
+# 'check_nt' command definition
+#define command {
+# command_name check_nt
+# command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -v '$ARG1$'
+#}
+
+# 'check_nscp' command definition
+define command {
+ command_name check_nscp
+ command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -p 12489 -v '$ARG1$'
+}
diff --git a/roles/icinga-kb/handlers/main.yml b/roles/icinga-kb/handlers/main.yml
new file mode 100644
index 0000000..721651e
--- /dev/null
+++ b/roles/icinga-kb/handlers/main.yml
@@ -0,0 +1,12 @@
+---
+ - name: restart icinga
+ service: name=icinga state=restarted
+
+ - name: stop icinga
+ service: name=icinga state=stopped
+
+ - name: start icinga
+ service: name=icinga state=started
+
+ - name: restart apache
+ service: name=apache2 state=restarted
diff --git a/roles/icinga-kb/tasks/main.yml b/roles/icinga-kb/tasks/main.yml
new file mode 100644
index 0000000..5b598da
--- /dev/null
+++ b/roles/icinga-kb/tasks/main.yml
@@ -0,0 +1,102 @@
+---
+- name: Installation apache2
+ apt: name=apache2 state=present
+
+- name: Installation snmp
+ apt: name=snmp state=present
+
+- name: Installation de icinga
+ apt: name=icinga state=present
+
+- name: Installation de nagios-plugins
+ apt: name=nagios-plugins state=present
+
+- name: Installation de nagios-snmp-plugins
+ apt: name=nagios-snmp-plugins state=present
+
+- name: Installation des dépendances dns
+ apt: name=libnet-dns-perl state=present
+
+#- name: Copie de fichier apache.conf
+# copy: remote_src=true src=/etc/icinga/apache2.conf dest=/etc/apache2/sites-available/icinga.conf
+
+#- name: activation du site de icinga
+# shell: a2ensite icinga
+# notify:
+# - restart icinga
+
+- name: changement de mot de passe de icingaadmin
+ shell: htpasswd -dbc /etc/icinga/htpasswd.users icingaadmin root
+
+- name: Copie du fichier commands.cfg
+ copy: src=commands.cfg dest=/etc/icinga/commands.cfg
+
+- name: Copie du fichier icinga.cfg
+ copy: src=icinga.cfg dest=/etc/icinga
+
+- name: Copie du fichier contacts_icinga.cfg
+ copy: src=cfg/contacts_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier hostgroups_icinga.cfg
+ copy: src=cfg/hostgroups_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier r-ext.cfg
+ copy: src=cfg/r-ext.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier r-int.cfg
+ copy: src=cfg/r-int.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-adm.cfg
+ copy: src=cfg/s-adm.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier services_icinga.cfg
+ copy: src=cfg/services_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-infra.cfg
+ copy: src=cfg/s-infra.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-infra-adm.cfg
+ copy: src=cfg/s-infra-adm.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-lb.cfg
+ copy: src=cfg/s-lb.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-lb-adm.cfg
+ copy: src=cfg/s-lb-adm.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-win
+ copy: src=cfg/s-win.cfg dest=/etc/icinga/objects
+
+- name: Changement droit notif
+ shell: chmod 644 /var/log/icinga/icinga.log
+
+- name: copie nt.cfg
+ copy: src=nt.cfg dest=/etc/nagios-plugins/config
+
+#- name: copie dns.cfg
+# copy: remote_src=true src=dns.cfg dest=/etc/nagios-plugins/config
+
+- name: stop icinga
+ service:
+ name: icinga
+ state: stopped
+
+- name: modif des droits /var/lib/icinga/rw/
+ shell: dpkg-statoverride --update --add nagios www-data 2710 /var/lib/icinga/rw/
+
+- name: modif des droits /var/lib/icinga/
+ shell: dpkg-statoverride --update --add nagios nagios 751 /var/lib/icinga/
+
+- name: start icinga
+ service:
+ name: icinga
+ state: started
+
+- name: copie check traffic
+ copy: src=check_iftraffic3.pl dest=/usr/lib/nagios/plugins
+
+- name: modif des droits plugin traffic
+ shell: chmod 755 /usr/lib/nagios/plugins/check_iftraffic3.pl
+
+- name: message d'information
+ debug: msg="Pour superviser le Windows, il faut installer NSClient++"
diff --git a/roles/icinga-yb/files/cfg/contacts_icinga.cfg b/roles/icinga-yb/files/cfg/contacts_icinga.cfg
new file mode 100644
index 0000000..955fc27
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/contacts_icinga.cfg
@@ -0,0 +1,59 @@
+###############################################################################
+# contacts.cfg
+###############################################################################
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACTS
+#
+###############################################################################
+###############################################################################
+
+# In this simple config file, a single contact will receive all alerts.
+
+#define contact{
+# contact_name root
+# alias Root
+# service_notification_period 24x7
+# host_notification_period 24x7
+# service_notification_options w,u,c,r
+# host_notification_options d,r
+# service_notification_commands notify-service-by-email
+# host_notification_commands notify-host-by-email
+# email root@localhost
+# }
+
+
+define contact{
+ contact_name admin
+ alias Administrateur
+ service_notification_period 24x7
+ host_notification_period 24x7
+ service_notification_options w,u,c,r
+ host_notification_options d,r
+ service_notification_commands notify-service-by-email
+ host_notification_commands notify-host-by-email
+ email yousriwalid@gmail.com
+ }
+
+
+
+###############################################################################
+###############################################################################
+#
+# CONTACT GROUPS
+#
+###############################################################################
+###############################################################################
+
+# We only have one contact in this simple configuration file, so there is
+# no need to create more than one contact group.
+
+define contactgroup{
+ contactgroup_name admins
+ alias Nagios Administrators
+ members admin
+ }
diff --git a/roles/icinga-yb/files/cfg/extinfo_icinga.cfg b/roles/icinga-yb/files/cfg/extinfo_icinga.cfg
new file mode 100644
index 0000000..07bd594
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/extinfo_icinga.cfg
@@ -0,0 +1,13 @@
+##
+## Extended Host and Service Information
+##
+
+define hostextinfo{
+ hostgroup_name debian-servers
+ notes Debian GNU/Linux servers
+# notes_url http://webserver.localhost.localdomain/hostinfo.pl?host=netware1
+ icon_image base/debian.png
+ icon_image_alt Debian GNU/Linux
+ vrml_image debian.png
+ statusmap_image base/debian.gd2
+ }
diff --git a/roles/icinga-yb/files/cfg/generic-host_icinga.cfg b/roles/icinga-yb/files/cfg/generic-host_icinga.cfg
new file mode 100644
index 0000000..e6d96ac
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/generic-host_icinga.cfg
@@ -0,0 +1,19 @@
+# Generic host definition template - This is NOT a real host, just a template!
+
+define host{
+ name generic-host ; The name of this host template
+ notifications_enabled 1 ; Host notifications are enabled
+ event_handler_enabled 1 ; Host event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ check_command check-host-alive
+ max_check_attempts 10
+ notification_interval 0
+ notification_period 24x7
+ notification_options d,u,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-yb/files/cfg/generic-service_icinga.cfg b/roles/icinga-yb/files/cfg/generic-service_icinga.cfg
new file mode 100644
index 0000000..4d60c79
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/generic-service_icinga.cfg
@@ -0,0 +1,26 @@
+# generic service template definition
+define service{
+ name generic-service ; The 'name' of this service template
+ active_checks_enabled 1 ; Active service checks are enabled
+ passive_checks_enabled 1 ; Passive service checks are enabled/accepted
+ parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems)
+ obsess_over_service 1 ; We should obsess over this service (if necessary)
+ check_freshness 0 ; Default is to NOT check service 'freshness'
+ notifications_enabled 1 ; Service notifications are enabled
+ event_handler_enabled 1 ; Service event handler is enabled
+ flap_detection_enabled 1 ; Flap detection is enabled
+ failure_prediction_enabled 1 ; Failure prediction is enabled
+ process_perf_data 1 ; Process performance data
+ retain_status_information 1 ; Retain status information across program restarts
+ retain_nonstatus_information 1 ; Retain non-status information across program restarts
+ notification_interval 0 ; Only send notifications on status change by default.
+ is_volatile 0
+ check_period 24x7
+ normal_check_interval 5
+ retry_check_interval 1
+ max_check_attempts 4
+ notification_period 24x7
+ notification_options w,u,c,r
+ contact_groups admins
+ register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
+ }
diff --git a/roles/icinga-yb/files/cfg/hostgroups_icinga.cfg b/roles/icinga-yb/files/cfg/hostgroups_icinga.cfg
new file mode 100644
index 0000000..49b2a76
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/hostgroups_icinga.cfg
@@ -0,0 +1,59 @@
+# Some generic hostgroup definitions
+
+define hostgroup {
+ hostgroup_name all
+ alias All Servers
+ members *
+ }
+
+define hostgroup {
+ hostgroup_name localhost
+ alias Debian GNU/Linux Servers
+ members localhost
+ }
+
+define hostgroup {
+ hostgroup_name debian-servers
+ alias Serveurs distant
+ members s-infra, r-int, r-ext, s-adm, s-itil
+}
+
+define hostgroup {
+ hostgroup_name ssh-servers
+ alias acces SSH
+ members s-adm, r-int, r-ext, localhost, s-infra, s-itil
+}
+
+define hostgroup {
+ hostgroup_name dns-servers
+ alias serveurs-dns
+ members s-infra
+
+}
+
+define hostgroup {
+ hostgroup_name dhcp-servers
+ alias serveurs-dhcp
+ members r-int, s-win
+}
+
+define hostgroup {
+ hostgroup_name http-servers
+ alias serveurs-web
+ members localhost
+ }
+
+
+define hostgroup{
+ hostgroup_name windows-servers
+ alias windows-servers
+ members s-win
+}
+
+
+define hostgroup{
+ hostgroup_name uptimegrp
+ alias uptimegrp
+ members r-int, r-ext, s-adm, s-win, s-itil
+}
+
diff --git a/roles/icinga-yb/files/cfg/localhost.cfg b/roles/icinga-yb/files/cfg/localhost.cfg
new file mode 100644
index 0000000..4e4e190
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/localhost.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host
+ host_name localhost
+ alias Serveur monitoring
+ address localhost
+ }
+
diff --git a/roles/icinga-yb/files/cfg/localhost_icinga.cfg b/roles/icinga-yb/files/cfg/localhost_icinga.cfg
new file mode 100644
index 0000000..0764b3a
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/localhost_icinga.cfg
@@ -0,0 +1,59 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in icinga-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name localhost
+ alias localhost
+ address 127.0.0.1
+ }
+
+# Define a service to check the disk space of the root partition
+# on the local machine. Warning if < 20% free, critical if
+# < 10% free space on partition.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Disk Space
+ check_command check_all_disks!20%!10%
+ }
+
+
+
+# Define a service to check the number of currently logged in
+# users on the local machine. Warning if > 20 users, critical
+# if > 50 users.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Users
+ check_command check_users!20!50
+ }
+
+
+# Define a service to check the number of currently running procs
+# on the local machine. Warning if > 250 processes, critical if
+# > 400 processes.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Total Processes
+ check_command check_procs!250!400
+ }
+
+
+
+# Define a service to check the load on the local machine.
+
+define service{
+ use generic-service ; Name of service template to use
+ host_name localhost
+ service_description Current Load
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
diff --git a/roles/icinga-yb/files/cfg/r-ext.cfg b/roles/icinga-yb/files/cfg/r-ext.cfg
new file mode 100644
index 0000000..0844c5e
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/r-ext.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-ext
+ alias Routeur externe
+ address 192.168.200.253
+ parents r-int
+ }
diff --git a/roles/icinga-yb/files/cfg/r-int.cfg b/roles/icinga-yb/files/cfg/r-int.cfg
new file mode 100644
index 0000000..249e69f
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/r-int.cfg
@@ -0,0 +1,13 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name r-int
+ alias Routeur interne
+ address 172.16.0.254
+ parents localhost
+ }
diff --git a/roles/icinga-yb/files/cfg/s-adm.cfg b/roles/icinga-yb/files/cfg/s-adm.cfg
new file mode 100644
index 0000000..aeadbee
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/s-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-adm
+ alias debian-servers
+ address 192.168.99.99
+ parents r-int
+ }
+
diff --git a/roles/icinga-yb/files/cfg/s-infra-adm.cfg b/roles/icinga-yb/files/cfg/s-infra-adm.cfg
new file mode 100644
index 0000000..c08df47
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/s-infra-adm.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra-adm
+ alias debian-servers
+ address 192.168.99.1
+ parents s-adm
+ }
+
diff --git a/roles/icinga-yb/files/cfg/s-infra.cfg b/roles/icinga-yb/files/cfg/s-infra.cfg
new file mode 100644
index 0000000..c369ff6
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/s-infra.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-infra
+ alias debian-servers
+ address 172.16.0.1
+ parents r-int
+ }
+
diff --git a/roles/icinga-yb/files/cfg/s-itil.cfg b/roles/icinga-yb/files/cfg/s-itil.cfg
new file mode 100644
index 0000000..812f64f
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/s-itil.cfg
@@ -0,0 +1,14 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-adm
+ alias debian-servers
+ address 172.16.0.9
+ parents r-int
+ }
+
diff --git a/roles/icinga-yb/files/cfg/s-win.cfg b/roles/icinga-yb/files/cfg/s-win.cfg
new file mode 100644
index 0000000..4a5bc58
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/s-win.cfg
@@ -0,0 +1,16 @@
+# A simple configuration file for monitoring the local host
+# This can serve as an example for configuring other servers;
+# Custom services specific to this host are added here, but services
+# defined in nagios2-common_services.cfg may also apply.
+#
+
+define host{
+ use generic-host ; Name of host template to use
+ host_name s-win
+ alias windows-servers
+ address 172.16.0.6
+ parents r-int
+ icon_image base/win40.gif
+ statusmap_image base/win40.gd2
+ }
+
diff --git a/roles/icinga-yb/files/cfg/services_icinga.cfg b/roles/icinga-yb/files/cfg/services_icinga.cfg
new file mode 100644
index 0000000..226237f
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/services_icinga.cfg
@@ -0,0 +1,106 @@
+define service {
+ hostgroup_name http-servers
+ service_description HTTP
+ check_command check_http
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service {
+ hostgroup_name ssh-servers
+ service_description SSH
+ check_command check_ssh
+ use generic-service
+ notification_interval 0 ; set > 0 if you want to be renotified
+}
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Espace disque
+ check_command check_snmp_storage!public!--v2c!"^/$|tmp|usr|var"!90!95
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description Charge machine
+ check_command check_snmp_load!public!--v2c!netsl!2,1,1!3,2,2
+ }
+
+define service{
+ use generic-service
+ hostgroup_name localhost
+ service_description Charge machine
+ check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0
+ }
+
+define service{
+ use generic-service
+ hostgroup_name debian-servers
+ service_description RAM
+ check_command check_snmp_mem!public!--v2c!-N!95,60!99,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Version NSClient++
+ check_command check_nt!CLIENTVERSION
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Charge CPU
+ check_command check_nt!CPULOAD!-l 5,80,90,15,80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Uptime
+ check_command check_nt!UPTIME
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Mem Use
+ check_command check_nt!MEMUSE!80,90
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Disk Space
+ check_command check_nt!USEDDISKSPACE!-l C!10,5
+}
+
+define service{
+ use generic-service
+ hostgroup_name windows-servers
+ service_description Service DNS
+ check_command check_nt!SERVICESTATE!-l W32Time,"Client DNS"
+}
+
+define service{
+ use generic-service
+ hostgroup_name uptimegrp
+ service_description Uptime
+ check_command check_snmp!-C public -o 1.3.6.1.2.1.1.3.0 -c 6000:0 -w 60000:0
+}
+
+define service{
+ use generic-service
+ hostgroup_name dns-servers
+ service_description DNS Ext
+ check_command check_dns
+}
+
+#define service{
+# use generic-service
+# hostgroup_name dhcp-servers
+# service_description Service DHCP
+# check_command check_dhcp
+#}
diff --git a/roles/icinga-yb/files/cfg/timeperiods_icinga.cfg b/roles/icinga-yb/files/cfg/timeperiods_icinga.cfg
new file mode 100644
index 0000000..55ecf9d
--- /dev/null
+++ b/roles/icinga-yb/files/cfg/timeperiods_icinga.cfg
@@ -0,0 +1,50 @@
+###############################################################################
+# timeperiods.cfg
+###############################################################################
+
+# This defines a timeperiod where all times are valid for checks,
+# notifications, etc. The classic "24x7" support nightmare. :-)
+
+define timeperiod{
+ timeperiod_name 24x7
+ alias 24 Hours A Day, 7 Days A Week
+ sunday 00:00-24:00
+ monday 00:00-24:00
+ tuesday 00:00-24:00
+ wednesday 00:00-24:00
+ thursday 00:00-24:00
+ friday 00:00-24:00
+ saturday 00:00-24:00
+ }
+
+# Here is a slightly friendlier period during work hours
+define timeperiod{
+ timeperiod_name workhours
+ alias Standard Work Hours
+ monday 09:00-17:00
+ tuesday 09:00-17:00
+ wednesday 09:00-17:00
+ thursday 09:00-17:00
+ friday 09:00-17:00
+ }
+
+# The complement of workhours
+define timeperiod{
+ timeperiod_name nonworkhours
+ alias Non-Work Hours
+ sunday 00:00-24:00
+ monday 00:00-09:00,17:00-24:00
+ tuesday 00:00-09:00,17:00-24:00
+ wednesday 00:00-09:00,17:00-24:00
+ thursday 00:00-09:00,17:00-24:00
+ friday 00:00-09:00,17:00-24:00
+ saturday 00:00-24:00
+ }
+
+# This one is a favorite: never :)
+define timeperiod{
+ timeperiod_name never
+ alias Never
+ }
+
+# end of file
diff --git a/roles/icinga-yb/files/check_iftraffic3.pl b/roles/icinga-yb/files/check_iftraffic3.pl
new file mode 100755
index 0000000..62ddbd1
--- /dev/null
+++ b/roles/icinga-yb/files/check_iftraffic3.pl
@@ -0,0 +1,643 @@
+#!/usr/bin/perl -w
+#
+# check_iftraffic.pl - Nagios(r) network traffic monitor plugin
+# Copyright (C) 2004 Gerd Mueller / Netways GmbH
+# $Id: check_iftraffic.pl 1119 2006-02-09 10:30:09Z gmueller $
+#
+# mw = Markus Werner mw+nagios@wobcom.de
+# Remarks (mw):
+#
+# I adopted as much as possible the programming style of the origin code.
+#
+# There should be a function to exit this programm,
+# instead of calling print and exit statements all over the place.
+#
+#
+# minor changes by mw
+# The snmp if_counters on net devices can have overflows.
+# I wrote this code to address this situation.
+# It has no automatic detection and which point the overflow
+# occurs but it will generate a warning state and you
+# can set the max value by calling this script with an additional
+# arg.
+#
+# minor cosmetic changes by mw
+# Sorry but I couldn't sustain to clean up some things.
+#
+# gj = Greg Frater gregATfraterfactory.com
+# Remarks (gj):
+# minor (gj):
+#
+# * fixed the performance data, formating was not to spec
+# * Added a check of the interfaces status (up/down).
+# If down the check returns a critical status.
+# * Allow either textual or the numeric index value.
+# * If the interface speed is not specified on the command line
+# it gets it automatically from IfSpeed
+# * Added option for second ifSpeed to allow for asymetrcal links
+# such as a DSL line or cable modem where the download and upload
+# speeds are different
+# * Added -B option to display results in bits/sec instead of Bytes/sec
+# * Added the current usage in Bytes/s (or bit/s) to the perfdata output
+# * Added ability for plugin to determine interface to query by matching IP
+# address of host with entry in ipAdEntIfIndex (.1.3.6.1.2.1.4.20.1.2)
+# * Added -L flag to list entries found in the ipAdEntIfIndex table
+# Otherwise, it works as before.
+#
+#
+#
+#
+# based on check_traffic from Adrian Wieczorek, <ads (at) irc.pila.pl>
+#
+# Send us bug reports, questions and comments about this plugin.
+# Latest version of this software: http://www.nagiosexchange.org
+#
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License
+# as published by the Free Software Foundation; either version 2
+# of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307
+
+use strict;
+
+use Net::SNMP;
+use Getopt::Long;
+&Getopt::Long::config('bundling');
+
+use Data::Dumper;
+
+my $host_ip;
+my $host_address;
+my $iface_number;
+my $iface_descr;
+my $iface_speed;
+my $iface_speedOut;
+my $index_list;
+my $opt_h;
+my $units;
+
+my $session;
+my $error;
+my $port = 161;
+my $snmp_version = 1;
+
+my @snmpoids;
+
+# SNMP OIDs for Traffic
+my $snmpIfOperStatus = '1.3.6.1.2.1.2.2.1.8';
+my $snmpIfInOctets = '1.3.6.1.2.1.2.2.1.10';
+my $snmpIfOutOctets = '1.3.6.1.2.1.2.2.1.16';
+my $snmpIfDescr = '1.3.6.1.2.1.2.2.1.2';
+my $snmpIfSpeed = '1.3.6.1.2.1.2.2.1.5';
+my $snmpIPAdEntIfIndex = '1.3.6.1.2.1.4.20.1.2';
+
+my $response;
+
+# Path to tmp files
+my $TRAFFIC_FILE = "/tmp/traffic";
+
+# changes sos 20090717 UNKNOWN must bes 3
+my %STATUS_CODE =
+ ( 'UNKNOWN' => '3', 'OK' => '0', 'WARNING' => '1', 'CRITICAL' => '2' );
+
+#default values;
+my $state = "UNKNOWN";
+my $if_status = '4';
+my ( $in_bytes, $out_bytes ) = 0;
+my $warn_usage = 85;
+my $crit_usage = 98;
+my $COMMUNITY = "public";
+my $use_reg = undef; # Use Regexp for name
+my $output = "";
+my $bits = undef;
+my $suffix = "Bs";
+my $label = "MBytes";
+
+#added 20050614 by mw
+my $max_value;
+my $max_bytes;
+
+#cosmetic changes 20050614 by mw, see old versions for detail
+# Added options for bits and second max ifspeed 20100202 by gj
+# Added options for specificy IP addr to match 20100405 by gj
+my $status = GetOptions(
+ "h|help" => \$opt_h,
+ 'B' => \$bits,
+ 'bits' => \$bits,
+ "C|community=s" => \$COMMUNITY,
+ "w|warning=s" => \$warn_usage,
+ "c|critical=s" => \$crit_usage,
+ "b|bandwidth|I|inBandwidth=i" => \$iface_speed,
+ "O|outBandwidth=i" => \$iface_speedOut,
+ 'r' => \$use_reg,
+ 'noregexp' => \$use_reg,
+ "p|port=i" => \$port,
+ "u|units=s" => \$units,
+ "i|interface=s" => \$iface_number,
+ "A|address=s" => \$host_ip,
+ "H|hostname=s" => \$host_address,
+ 'L' => \$index_list,
+ 'list' => \$index_list,
+
+ #added 20050614 by mw
+ "M|max=i" => \$max_value
+);
+
+if ( $status == 0 ) {
+ print_help();
+ exit $STATUS_CODE{'OK'};
+}
+
+# Changed 20091214 gj
+# Check for missing options
+#if ( ( !$host_address ) or ( !$iface_descr ) ) {
+if ( !$host_address ) {
+ print "\nMissing host address!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speed ) and ( !$units ) ){
+ print "\nMissing units!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $units ) and ( ( !$iface_speed ) and ( !$iface_speedOut ) ) ) {
+ print "\nMissing interface maximum speed!\n\n";
+ stop(print_usage(),"OK");
+} elsif ( ( $iface_speedOut ) and ( !$units ) ) {
+ print "\nMissing units for Out maximum speed!\n\n";
+ stop(print_usage(),"OK");
+}
+
+
+if ($bits) {
+ $suffix = "bs"
+}
+
+if ( !$iface_speed ) {
+ # Do nothing
+}else{
+
+ #change 20050414 by mw
+ # Added iface_speedOut 20100202 by gj
+ # Convert interface speed to kiloBytes
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+ if ( $iface_speedOut ) {
+ $iface_speedOut = bits2bytes( $iface_speedOut, $units ) / 1024;
+ }
+ if ( !$max_value ) {
+
+ # If no -M Parameter was set, set it to 32Bit Overflow
+ $max_bytes = 4194304 ; # the value is (2^32/1024)
+ }
+ else {
+ $max_bytes = unit2bytes( $max_value, $units );
+ }
+}
+
+if ( $snmp_version =~ /[12]/ ) {
+ ( $session, $error ) = Net::SNMP->session(
+ -hostname => $host_address,
+ -community => $COMMUNITY,
+ -port => $port,
+ -version => $snmp_version
+ );
+
+ if ( !defined($session) ) {
+ stop("UNKNOWN: $error","UNKNOWN");
+ }
+}
+elsif ( $snmp_version =~ /3/ ) {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v3 yet\n",$state);
+}
+else {
+ $state = 'UNKNOWN';
+ stop("$state: No support for SNMP v$snmp_version yet\n",$state);
+}
+
+# Neither Interface Index nor Host IP address were specified
+if ( !$iface_descr ) {
+ if ( !$host_ip ){
+ # try to resolve host name and find index from ip addr
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_address );
+ } else {
+ # Use ip addr to find index
+ $iface_descr = fetch_Ip2IfIndex( $session, $host_ip );
+ }
+}
+
+#push( @snmpoids, $snmpIPAdEntIfIndex . "." . $host_address );
+
+# Added 20091209 gj
+# Detect if a string description was given or a numberic interface index number
+if ( $iface_descr =~ /[^0123456789]+/ ) {
+ $iface_number = fetch_ifdescr( $session, $iface_descr );
+}else{
+ $iface_number = $iface_descr;
+}
+
+push( @snmpoids, $snmpIfSpeed . "." . $iface_number );
+push( @snmpoids, $snmpIfOperStatus . "." . $iface_number );
+push( @snmpoids, $snmpIfInOctets . "." . $iface_number );
+push( @snmpoids, $snmpIfOutOctets . "." . $iface_number );
+
+if ( !defined( $response = $session->get_request(@snmpoids) ) ) {
+ my $answer = $session->error;
+ $session->close;
+
+ stop("WARNING: SNMP error: $answer\n", "WARNING");
+}
+
+# Added 20091209 gj
+# Get interface speed from device if not provided on command line
+# Convert to kiloBytes
+if ( !$iface_speed ) {
+ $iface_speed = $response->{ $snmpIfSpeed . "." . $iface_number };
+ $units = "b";
+ $iface_speed = bits2bytes( $iface_speed, $units ) / 1024;
+}
+
+# Added 20100201 gj
+# Check if Out max speed was provided, use same if speed for both if not
+if (!$iface_speedOut) {
+ $iface_speedOut = $iface_speed;
+}
+
+$if_status = $response->{ $snmpIfOperStatus . "." . $iface_number };
+$in_bytes = $response->{ $snmpIfInOctets . "." . $iface_number } / 1024; # in kiloBytes
+$out_bytes = $response->{ $snmpIfOutOctets . "." . $iface_number } / 1024; # in kiloBytes
+
+$session->close;
+
+my $row;
+my $last_check_time = time - 1;
+my $last_in_bytes = $in_bytes;
+my $last_out_bytes = $out_bytes;
+
+if (
+ open( FILE,
+ "<" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address
+ )
+ )
+{
+ while ( $row = <FILE> ) {
+
+ #cosmetic change 20050416 by mw
+ #Couldn't sustain;-)
+## chomp();
+ ( $last_check_time, $last_in_bytes, $last_out_bytes ) =
+ split( ":", $row );
+
+ ### by sos 17.07.2009 check for last_bytes
+ if ( ! $last_in_bytes ) { $last_in_bytes=$in_bytes; }
+ if ( ! $last_out_bytes ) { $last_out_bytes=$out_bytes; }
+
+ if ($last_in_bytes !~ m/\d/) { $last_in_bytes=$in_bytes; }
+ if ($last_out_bytes !~ m/\d/) { $last_out_bytes=$out_bytes; }
+ }
+ close(FILE);
+}
+
+my $update_time = time;
+
+open( FILE, ">" . $TRAFFIC_FILE . "_if" . $iface_number . "_" . $host_address )
+ or die "Can't open $TRAFFIC_FILE for writing: $!";
+
+printf FILE ( "%s:%.0ld:%.0ld\n", $update_time, $in_bytes, $out_bytes );
+close(FILE);
+
+my $db_file;
+
+#added 20050614 by mw
+#Check for and correct counter overflow (if possible).
+#See function counter_overflow.
+$in_bytes = counter_overflow( $in_bytes, $last_in_bytes, $max_bytes );
+$out_bytes = counter_overflow( $out_bytes, $last_out_bytes, $max_bytes );
+
+# Calculate traffic since last check (RX\TX) in kiloBytes
+my $in_traffic = sprintf( "%.2lf",
+ ( $in_bytes - $last_in_bytes ) / ( time - $last_check_time ) );
+my $out_traffic = sprintf( "%.2lf",
+ ( $out_bytes - $last_out_bytes ) / ( time - $last_check_time ) );
+
+# sos 20090717 changed due to rrdtool needs bytes
+my $in_traffic_absolut = $in_bytes * 1024 ;
+my $out_traffic_absolut = $out_bytes * 1024;
+
+# Calculate usage percentages
+my $in_usage = sprintf( "%.2f", ( 1.0 * $in_traffic * 100 ) / $iface_speed );
+my $out_usage = sprintf( "%.2f", ( 1.0 * $out_traffic * 100 ) / $iface_speedOut );
+
+
+if ($bits) {
+ # Convert output from Bytes to bits
+ $in_bytes = $in_bytes * 8;
+ $out_bytes = $out_bytes * 8;
+ $in_traffic = $in_traffic * 8;
+ $out_traffic = $out_traffic * 8;
+ $label = "Mbits";
+}
+
+my $in_prefix = "K";
+my $out_prefix = "K";
+
+if ( $in_traffic > 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 );
+ $in_prefix = "M";
+}
+if ( $out_traffic > 1024 ) {
+ $out_traffic = sprintf( "%.2f", $out_traffic / 1024 );
+ $out_prefix = "M";
+}
+if ( $in_traffic > 1024 * 1024 ) {
+ $in_traffic = sprintf( "%.2f", $in_traffic / 1024 * 1024 );
+ $in_prefix = "G";
+}
+if ( $out_traffic > 1024 * 1024 ) {
+ $out_traffic = sprintf( "%.2f",$out_traffic / 1024 * 1024 );
+ $out_prefix = "G";
+}
+
+# Convert from kiloBytes to megaBytes
+$in_bytes = sprintf( "%.2f", $in_bytes / 1024 );
+$out_bytes = sprintf( "%.2f", $out_bytes / 1024 );
+
+$state = "OK";
+
+# Added 20091209 by gj
+if ( $if_status != 1 ) {
+ $output = "Interface $iface_descr is down!";
+
+}else{
+ $output =
+ "Average IN: "
+ . $in_traffic . $in_prefix . $suffix . " (" . $in_usage . "%), "
+ . "Average OUT: " . $out_traffic . $out_prefix . $suffix . " (" . $out_usage . "%)<br>";
+ $output .= "Total RX: $in_bytes $label, Total TX: $out_bytes $label";
+}
+
+# Changed 20091209 gj
+if ( ( $in_usage > $crit_usage ) or ( $out_usage > $crit_usage ) or ( $if_status != 1 ) ) {
+ $state = "CRITICAL";
+}
+
+if ( ( $in_usage > $warn_usage )
+ or ( $out_usage > $warn_usage ) && $state eq "OK" )
+{
+ $state = "WARNING";
+}
+
+# Changed 20091209 gj
+$output = "$state - $output"
+ if ( $state ne "OK" );
+
+# Changed 20091214 gj - commas should have been semi colons
+$output .=
+"|inUsage=$in_usage%;$warn_usage;$crit_usage outUsage=$out_usage%;$warn_usage;$crit_usage"
+ . " inBandwidth=" . $in_traffic . $in_prefix . $suffix . " outBandwidth=" . $out_traffic . $out_prefix . $suffix
+ . " inAbsolut=$in_traffic_absolut outAbsolut=$out_traffic_absolut";
+
+stop($output, $state);
+
+
+sub fetch_Ip2IfIndex {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $host ) = @_;
+
+
+ # Determine if we have a host name or IP addr
+ if ( $host =~ /\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/ ){
+ #print "\nI found an IP address\n\n";
+ } else {
+ $host = get_ip ( $host );
+ #print "\nWe have a host name $host\n\n";
+ }
+
+ # Quit if results not found
+ if ( !defined( $response = $session->get_table($snmpIPAdEntIfIndex) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+
+ my %resp = %{$response};
+# foreach $key ( keys %{$response} ) {
+
+ if ( $index_list ){
+ print ("\nInterfaces found:\n");
+ print (" IP Addr\tIndex\n");
+ print ("------------------------\n");
+ }
+ # Check each returned value
+ foreach $key ( keys %resp ) {
+
+ if ( $index_list ){
+ my $index_addr = substr $key, 21;
+ print ($index_addr,"\t ",$resp{$key},"\n");
+ }
+
+ # Check for ip address mathcin in returned index results
+ if ( $key =~ /$host$/ ) {
+ $snmpkey = $resp{$key};
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $host \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+sub fetch_ifdescr {
+ my $state;
+ my $response;
+
+ my $snmpkey;
+ my $answer;
+ my $key;
+
+ my ( $session, $ifdescr ) = @_;
+
+ if ( !defined( $response = $session->get_table($snmpIfDescr) ) ) {
+ $answer = $session->error;
+ $session->close;
+ $state = 'CRITICAL';
+ $session->close;
+ exit $STATUS_CODE{$state};
+ }
+
+ foreach $key ( keys %{$response} ) {
+
+ # added 20070816 by oer: remove trailing 0 Byte for Windows :-(
+ my $resp=$response->{$key};
+ $resp =~ s/\x00//;
+
+
+ my $test = defined($use_reg)
+ ? $resp =~ /$ifdescr/
+ : $resp eq $ifdescr;
+
+ if ($test) {
+
+ ###if ( $resp =~ /^$ifdescr$/ ) {
+ ###if ( $resp =~ /$ifdescr/ ) {
+ ### print "$resp \n";
+ ###if ( $response->{$key} =~ /^$ifdescr$/ ) {
+
+ $key =~ /.*\.(\d+)$/;
+ $snmpkey = $1;
+
+ # print "$ifdescr = $key / $snmpkey \n"; #debug
+ }
+ }
+ unless ( defined $snmpkey ) {
+ $session->close;
+ $state = 'CRITICAL';
+ printf "$state: Could not match $ifdescr \n";
+ exit $STATUS_CODE{$state};
+ }
+ return $snmpkey;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bits
+sub bits2bytes {
+ return unit2bytes(@_) / 8;
+}
+
+#added 20050416 by mw
+#Converts an input value to value in bytes
+sub unit2bytes {
+ my ( $value, $unit ) = @_;
+
+ if ( $unit eq "g" ) {
+ return $value * 1024 * 1024 * 1024;
+ }
+ elsif ( $unit eq "m" ) {
+ return $value * 1024 * 1024;
+ }
+ elsif ( $unit eq "k" ) {
+ return $value * 1024;
+ }
+ elsif ( $unit eq "b" ) {
+ return $value * 1;
+ }
+ else {
+ print "You have to supply a supported unit\n";
+ exit $STATUS_CODE{'UNKNOWN'};
+ }
+}
+
+#added 20050414 by mw
+#This function detects if an overflow occurs. If so, it returns
+#a computed value for $bytes.
+#If there is no counter overflow it simply returns the origin value of $bytes.
+#IF there is a Counter reboot wrap, just use previous output.
+sub counter_overflow {
+ my ( $bytes, $last_bytes, $max_bytes ) = @_;
+
+ $bytes += $max_bytes if ( $bytes < $last_bytes );
+ $bytes = $last_bytes if ( $bytes < $last_bytes );
+ return $bytes;
+}
+
+# Added 20100202 by gj
+# Print results and exit script
+sub stop {
+ my $result = shift;
+ my $exit_code = shift;
+ print $result . "\n";
+ exit ( $STATUS_CODE{$exit_code} );
+}
+
+# Added 20100405 by gj
+# Lookup hosts ip address
+sub get_ip {
+ use Net::DNS;
+
+ my ( $host_name ) = @_;
+
+ my $res = Net::DNS::Resolver->new;
+ my $query = $res->search($host_name);
+
+ if ($query) {
+ foreach my $rr ($query->answer) {
+ next unless $rr->type eq "A";
+ #print $rr->address, "\n";
+ return $rr->address;
+ }
+ } else {
+
+ stop("Error: IP address not resolved\n","UNKNOWN");
+ }
+}
+
+#cosmetic changes 20050614 by mw
+#Couldn't sustain "HERE";-), either.
+sub print_usage {
+ print <<EOU;
+ Usage: check_iftraffic3.pl -H host [ -C community_string ] [ -i if_index|if_descr ] [ -r ] [ -b if_max_speed_in | -I if_max_speed_in ] [ -O if_max_speed_out ] [ -u ] [ -B ] [ -A IP Address ] [ -L ] [ -M ] [ -w warn ] [ -c crit ]
+
+ Example 1: check_iftraffic3.pl -H host1 -C sneaky
+ Example 2: check_iftraffic3.pl -H host1 -C sneaky -i "Intel Pro" -r -B
+ Example 3: check_iftraffic3.pl -H host1 -C sneaky -i 5
+ Example 4: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 100 -u m
+ Example 5: check_iftraffic3.pl -H host1 -C sneaky -i 5 -B -b 20 -O 5 -u m
+ Example 6: check_iftraffic3.pl -H host1 -C sneaky -A 192.168.1.1 -B -b 100 -u m
+
+ Options:
+
+ -H, --host STRING or IPADDRESS
+ Check interface on the indicated host.
+ -B, --bits
+ Display results in bits per second b/s (default: Bytes/s)
+ -C, --community STRING
+ SNMP Community.
+ -r, --regexp
+ Use regexp to match NAME in description OID
+ -i, --interface STRING
+ Interface Name
+ -b, --bandwidth INTEGER
+ -I, --inBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ both IN and OUT if no second (-O) max speed is provided.
+ -O, --outBandwidth INTEGER
+ Interface maximum speed in kilo/mega/giga/bits per second. Applied to
+ OUT traffic. Uses the same units value given for -b.
+ -u, --units STRING
+ g=gigabits/s,m=megabits/s,k=kilobits/s,b=bits/s. Required if -b, -I, or
+ -O are used.
+ -w, --warning INTEGER
+ % of bandwidth usage necessary to result in warning status (default: 85%)
+ -c, --critical INTEGER
+ % of bandwidth usage necessary to result in critical status (default: 98%)
+ -M, --max INTEGER
+ Max Counter Value of net devices in kilo/mega/giga/bytes.
+ -A, --address STRING (IP Address)
+ IP Address to use when determining the interface index to use. Can be
+ used when the index changes frequently or as in the case of Windows
+ servers the index is different depending on the NIC installed.
+ -L, --list FLAG (on/off)
+ Tell plugin to list available interfaces. This is not supported inside
+ of Nagios, but may be useful from the command line.
+EOU
+
+}
+
diff --git a/roles/icinga-yb/files/commands.cfg b/roles/icinga-yb/files/commands.cfg
new file mode 100644
index 0000000..1ceea2c
--- /dev/null
+++ b/roles/icinga-yb/files/commands.cfg
@@ -0,0 +1,90 @@
+###############################################################################
+# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS
+###############################################################################
+
+
+################################################################################
+# NOTIFICATION COMMANDS
+################################################################################
+
+
+# 'notify-host-by-email' command definition
+define command{
+ command_name notify-host-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$
+ }
+
+# 'notify-service-by-email' command definition
+define command{
+ command_name notify-service-by-email
+ command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$
+ }
+
+
+
+
+
+################################################################################
+# HOST CHECK COMMANDS
+################################################################################
+
+# On Debian, check-host-alive is being defined from within the
+# nagios-plugins-basic package
+define command{
+ command_name check_snmp_storage
+ command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -m $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_load
+ command_line $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -T $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_mem
+ command_line $USER1$/check_snmp_mem.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ $ARG3$ -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_snmp_int
+ command_line $USER1$/check_snmp_netint.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -a -m -k -M -w $ARG4$ -c $ARG5$
+}
+
+define command{
+ command_name check_iftraffic3
+ #command_name check_win_int
+ #command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$
+ #command_line $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ -C $ARG1$ $ARG2$ -n $ARG3$ -k -M -g -w $ARG4$ -c $ARG5$
+ command_line $USER1$/check_iftraffic3.pl -H $HOSTADDRESS$ -C $ARG1$ -i $ARG2$ -w $ARG3$ -c $ARG4$
+}
+
+define command{
+ command_name check_snmp
+ command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
+}
+###############################
+##WINDOWS
+###############################
+
+define command{
+ command_name check_nt
+ command_line $USER1$/check_nt -H $HOSTADDRESS$ -s root -p 12489 -v $ARG1$ $ARG2$
+}
+
+################################################################################
+# PERFORMANCE DATA COMMANDS
+################################################################################
+
+
+# 'process-host-perfdata' command definition
+define command{
+ command_name process-host-perfdata
+ command_line /usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /var/lib/nagios3/host-perfdata.out
+ }
+
+
+# 'process-service-perfdata' command definition
+define command{
+ command_name process-service-perfdata
+ command_line /usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /var/lib/nagios3/service-perfdata.out
+ }
diff --git a/roles/icinga-yb/files/dns.cfg b/roles/icinga-yb/files/dns.cfg
new file mode 100644
index 0000000..5b69aca
--- /dev/null
+++ b/roles/icinga-yb/files/dns.cfg
@@ -0,0 +1,11 @@
+# 'check_dns' command definition
+define command{
+ command_name check_dns
+ command_line /usr/lib/nagios/plugins/check_dns -H www.dfco.fr -s '$HOSTADDRESS$'
+}
+
+# 'check_dig' command definition
+define command{
+ command_name check_dig
+ command_line /usr/lib/nagios/plugins/check_dig -H '$HOSTADDRESS$' -l '$ARG1$'
+}
diff --git a/roles/icinga-yb/files/icinga.cfg b/roles/icinga-yb/files/icinga.cfg
new file mode 100644
index 0000000..fde1780
--- /dev/null
+++ b/roles/icinga-yb/files/icinga.cfg
@@ -0,0 +1,1494 @@
+##############################################################################
+#
+# ICINGA.CFG - Sample Main Config File for Icinga
+#
+# Read the documentation for more information on this configuration
+# file. I've provided some comments here, but things may not be so
+# clear without further explanation.
+#
+##############################################################################
+
+
+# LOG FILE
+# This is the main log file where service and host events are logged
+# for historical purposes. This should be the first option specified
+# in the config file!!!
+
+log_file=/var/log/icinga/icinga.log
+
+# Commands definitions
+cfg_file=/etc/icinga/commands.cfg
+
+# Debian also defaults to using the check commands defined by the debian
+# nagios-plugins package
+cfg_dir=/etc/nagios-plugins/config
+
+# OBJECT CONFIGURATION FILE(S)
+# These are the object configuration files in which you define hosts,
+# host groups, contacts, contact groups, services, etc.
+# Hint: Check the docs/wiki on how to monitor remote hosts with different
+# transport methods and plugins
+
+# Debian uses by default a configuration directory where icinga-common,
+# other packages and the local admin can dump or link configuration
+# files into.
+cfg_dir=/etc/icinga/objects/
+
+# Definitions for ido2db process checks
+#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg
+
+# Definitions for broker modules like idoutils.cfg
+cfg_dir=/etc/icinga/modules
+
+
+
+# OBJECT CACHE FILE
+# This option determines where object definitions are cached when
+# Icinga starts/restarts. The CGIs read object definitions from
+# this cache file (rather than looking at the object config files
+# directly) in order to prevent inconsistencies that can occur
+# when the config files are modified after Icinga starts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the objects cache file entirely.
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+# Tip: Use that file to debug your configuration with fully resolved
+# objects like the core sees them.
+
+object_cache_file=/var/cache/icinga/objects.cache
+
+
+
+# PRE-CACHED OBJECT FILE
+# This options determines the location of the precached object file.
+# If you run Icinga with the -p command line option, it will preprocess
+# your object configuration file(s) and write the cached config to this
+# file. You can then start Icinga with the -u option to have it read
+# object definitions from this precached file, rather than the standard
+# object configuration files (see the cfg_file and cfg_dir options above).
+# Using a precached object file can speed up the time needed to (re)start
+# the Icinga process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Icinga to find our more
+# about how this feature works.
+
+precached_object_file=/var/cache/icinga/objects.precache
+
+
+
+# RESOURCE FILE
+# This is an optional resource file that contains $USERx$ macro
+# definitions. Multiple resource files can be specified by using
+# multiple resource_file definitions. The CGIs will not attempt to
+# read the contents of resource files, so information that is
+# considered to be sensitive (usernames, passwords, etc) can be
+# defined as macros in this file and restrictive permissions (600)
+# can be placed on this file.
+
+resource_file=/etc/icinga/resource.cfg
+
+
+
+# STATUS FILE
+# This is where the current status of all monitored services and
+# hosts is stored. Its contents are read and processed by the CGIs.
+# The contents of the status file are deleted every time Icinga
+# restarts.
+# If you explicitely set it to /dev/null the core will skip writing
+# the status file entirely. This becomes handy when using other methods
+# for data retrieval (e.g. IDOUtils DB)
+# Note: This is a mandatory output for Icinga Classic UI to work properly.
+
+status_file=/var/lib/icinga/status.dat
+
+
+
+# STATUS FILE UPDATE INTERVAL
+# This option determines the frequency (in seconds) that
+# Icinga will periodically dump program, host, and
+# service status data.
+# Increase the value, if you don't require it that often.
+
+#status_update_interval=30
+status_update_interval=10
+
+
+
+# ICINGA USER
+# This determines the effective user that Icinga should run as.
+# You can either supply a username or a UID.
+
+icinga_user=nagios
+
+
+
+# ICINGA GROUP
+# This determines the effective group that Icinga should run as.
+# You can either supply a group name or a GID.
+
+icinga_group=nagios
+
+
+
+# EXTERNAL COMMAND OPTION
+# This option allows you to specify whether or not Icinga should check
+# for external commands (in the command file defined below). By default
+# Icinga will *not* check for external commands, just to be on the
+# cautious side. If you want to be able to use the CGI command interface
+# you will have to enable this.
+# Values: 0 = disable commands, 1 = enable commands
+
+check_external_commands=1
+
+
+
+# EXTERNAL COMMAND CHECK INTERVAL
+# This is the interval at which Icinga should check for external commands.
+# This value works of the interval_length you specify later. If you leave
+# that at its default value of 60 (seconds), a value of 1 here will cause
+# Icinga to check for external commands every minute. If you specify a
+# number followed by an "s" (i.e. 15s), this will be interpreted to mean
+# actual seconds rather than a multiple of the interval_length variable.
+# Note: In addition to reading the external command file at regularly
+# scheduled intervals, Icinga will also check for external commands after
+# event handlers are executed.
+# NOTE: Setting this value to -1 causes Icinga to check the external
+# command file as often as possible.
+
+#command_check_interval=15s
+command_check_interval=-1
+
+
+
+# EXTERNAL COMMAND FILE
+# This is the file that Icinga checks for external command requests.
+# It is also where the command CGI will write commands that are submitted
+# by users, so it must be writeable by the user that the web server
+# is running as (usually 'nobody'). Permissions should be set at the
+# directory level instead of on the file, as the file is deleted every
+# time its contents are processed.
+# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
+# time to do it.
+
+command_file=/var/lib/icinga/rw/icinga.cmd
+
+
+
+# EXTERNAL COMMAND BUFFER SLOTS
+# This settings is used to tweak the number of items or "slots" that
+# the Icinga daemon should allocate to the buffer that holds incoming
+# external commands before they are processed. As external commands
+# are processed by the daemon, they are removed from the buffer.
+# Increase the value, if you are using addons like check_mk supplying
+# more external commands (passive check results) than usual.
+
+#external_command_buffer_slots=32768
+external_command_buffer_slots=4096
+
+
+
+# LOCK FILE
+# This is the lockfile that Icinga will use to store its PID number
+# in when it is running in daemon mode.
+
+lock_file=/var/run/icinga/icinga.pid
+
+
+
+# TEMP FILE
+# This is a temporary file that is used as scratch space when Icinga
+# updates the status log, cleans the comment file, etc. This file
+# is created, used, and deleted throughout the time that Icinga is
+# running.
+
+temp_file=/var/cache/icinga/icinga.tmp
+
+
+
+# TEMP PATH
+# This is path where Icinga can create temp files for service and
+# host check results, etc.
+
+temp_path=/tmp
+
+
+
+# EVENT BROKER OPTIONS
+# Controls what (if any) data gets sent to the event broker.
+# Values: 0 = Broker nothing
+# -1 = Broker everything
+# <other> = See documentation
+
+event_broker_options=-1
+
+
+
+# EVENT BROKER MODULE(S)
+# ----> use the new *module definition* instead:
+# ----> http://docs.icinga.org/latest/en/objectdefinitions.html
+#
+# Example definitions can be found in the '/etc/icinga/modules/' directory.
+# If you want to enable idoutils in Debian install icinga-idoutils and copy
+# /usr/share/doc/icinga-idoutils/examples/idoutils.cfg-sample to
+# /etc/icinga/modules/idoutils.cfg.
+# Don't forget to also enable the daemon in /etc/default/icinga
+
+# LOG ROTATION METHOD
+# This is the log rotation method that Icinga should use to rotate
+# the main log file. Values are as follows..
+# n = None - don't rotate the log
+# h = Hourly rotation (top of the hour)
+# d = Daily rotation (midnight every day)
+# w = Weekly rotation (midnight on Saturday evening)
+# m = Monthly rotation (midnight last day of month)
+
+log_rotation_method=d
+
+
+
+# LOG ARCHIVE PATH
+# This is the directory where archived (rotated) log files should be
+# placed (assuming you've chosen to do log rotation).
+
+log_archive_path=/var/log/icinga/archives
+
+
+
+# LOGGING OPTIONS FOR DAEMON
+# If you want messages logged to the daemon log file (usually icinga.log).
+# Default option is 1 (yes), the other valid option is 0 (no)
+
+use_daemon_log=1
+
+
+
+# LOGGING OPTIONS FOR SYSLOG
+# If you want messages logged to the syslog facility, as well as the
+# Icinga log file set this option to 1. If not, set it to 0.
+
+use_syslog=1
+
+
+
+# SYSLOG FACILITY
+# If you enabled use_syslog you can set icinga to use a local facility
+# instead of the default.To enable set this option to 1, if not, set it to 0.
+
+use_syslog_local_facility=0
+
+
+
+# SYSLOG LOCAL FACILITY
+# If you specified the use_syslog_local_facility you can chose which
+# local facility to use. Valid values are from 0 to 7
+
+syslog_local_facility=5
+
+
+
+# NOTIFICATION LOGGING OPTION
+# If you don't want notifications to be logged, set this value to 0.
+# If notifications should be logged, set the value to 1.
+
+log_notifications=1
+
+
+
+# SERVICE RETRY LOGGING OPTION
+# If you don't want service check retries to be logged, set this value
+# to 0. If retries should be logged, set the value to 1.
+
+log_service_retries=1
+
+
+
+# HOST RETRY LOGGING OPTION
+# If you don't want host check retries to be logged, set this value to
+# 0. If retries should be logged, set the value to 1.
+
+log_host_retries=1
+
+
+
+# EVENT HANDLER LOGGING OPTION
+# If you don't want host and service event handlers to be logged, set
+# this value to 0. If event handlers should be logged, set the value
+# to 1.
+
+log_event_handlers=1
+
+
+
+# INITIAL STATES LOGGING OPTION
+# If you want Icinga to log all initial host and service states to
+# the main log file (the first time the service or host is checked)
+# you can enable this option by setting this value to 1. If you
+# are not using an external application that does long term state
+# statistics reporting, you do not need to enable this option. In
+# this case, set the value to 0.
+
+log_initial_states=0
+
+
+
+# CURRENT STATES LOGGING OPTION
+# If you don't want Icinga to log all current host and service states
+# after log has been rotated to the main log file, you can disable this
+# option by setting this value to 0. Default value is 1.
+
+log_current_states=1
+
+
+
+# EXTERNAL COMMANDS LOGGING OPTION
+# If you don't want Icinga to log external commands, set this value
+# to 0. If external commands should be logged, set this value to 1.
+# Note: This option does not include logging of passive service
+# checks - see the option below for controlling whether or not
+# passive checks are logged.
+
+log_external_commands=1
+
+
+
+# LOG ANONYMIZED EXTERNAL COMMAND AUTHOR !!EXPERIMENTAL!!
+# This option substitutes the user name on external commands with
+# the string "<anon>" if the command gets logged. It is
+# anonymized in log files only. This option was added to make
+# icinga compliant with data retention laws on various countries.
+# This option is disabled by default.
+
+log_anonymized_external_command_author=0
+
+
+
+# PASSIVE CHECKS LOGGING OPTION
+# If you don't want Icinga to log passive host and service checks, set
+# this value to 0. If passive checks should be logged, set
+# this value to 1.
+
+log_passive_checks=1
+
+
+
+# LONG PLUGIN OUTPUT LOGGING OPTION
+# If you want Icinga to log the complete text of the plugin output
+# to the log instead of only the first line then set this value to 1.
+# Default value is 0.
+
+log_long_plugin_output=0
+
+
+
+# GLOBAL HOST AND SERVICE EVENT HANDLERS
+# These options allow you to specify a host and service event handler
+# command that is to be run for every host or service state change.
+# The global event handler is executed immediately prior to the event
+# handler that you have optionally specified in each host or
+# service definition. The command argument is the short name of a
+# command definition that you define in your host configuration file.
+# Read the HTML docs for more information.
+
+#global_host_event_handler=somecommand
+#global_service_event_handler=somecommand
+
+
+
+# SERVICE INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" service checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all service checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)! This is not a
+# good thing for production, but is useful when testing the
+# parallelization functionality.
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+service_inter_check_delay_method=s
+
+
+
+# MAXIMUM SERVICE CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all services should
+# be completed. Default is 30 minutes.
+
+max_service_check_spread=30
+
+
+
+# SERVICE CHECK INTERLEAVE FACTOR
+# This variable determines how service checks are interleaved.
+# Interleaving the service checks allows for a more even
+# distribution of service checks and reduced load on remote
+# hosts. Setting this value to 1 is equivalent to how versions
+# of Icinga previous to 0.0.5 did service checks. Set this
+# value to s (smart) for automatic calculation of the interleave
+# factor unless you have a specific reason to change it.
+# s = Use "smart" interleave factor calculation
+# x = Use an interleave factor of x, where x is a
+# number greater than or equal to 1.
+
+service_interleave_factor=s
+
+
+
+# HOST INTER-CHECK DELAY METHOD
+# This is the method that Icinga should use when initially
+# "spreading out" host checks when it starts monitoring. The
+# default is to use smart delay calculation, which will try to
+# space all host checks out evenly to minimize CPU load.
+# Using the dumb setting will cause all checks to be scheduled
+# at the same time (with no delay between them)!
+# n = None - don't use any delay between checks
+# d = Use a "dumb" delay of 1 second between checks
+# s = Use "smart" inter-check delay calculation
+# x.xx = Use an inter-check delay of x.xx seconds
+
+host_inter_check_delay_method=s
+
+
+
+# MAXIMUM HOST CHECK SPREAD
+# This variable determines the timeframe (in minutes) from the
+# program start time that an initial check of all hosts should
+# be completed. Default is 30 minutes.
+
+max_host_check_spread=30
+
+
+
+# MAXIMUM CONCURRENT SERVICE CHECKS
+# This option allows you to specify the maximum number of
+# service checks that can be run in parallel at any given time.
+# Specifying a value of 1 for this variable essentially prevents
+# any service checks from being parallelized. A value of 0
+# will not restrict the number of concurrent checks that are
+# being executed.
+
+max_concurrent_checks=0
+
+
+
+# HOST AND SERVICE CHECK REAPER FREQUENCY
+# This is the frequency (in seconds!) that Icinga will process
+# the results of host and service checks.
+# Lower this value in larger environments to allow faster
+# check result processing (requires more cpu power).
+
+#check_result_reaper_frequency=1
+check_result_reaper_frequency=10
+
+
+
+
+# MAX CHECK RESULT REAPER TIME
+# This is the max amount of time (in seconds) that a single
+# check result reaper event will be allowed to run before
+# returning control back to Icinga so it can perform other
+# duties.
+
+max_check_result_reaper_time=30
+
+
+
+
+# CHECK RESULT PATH
+# This is directory where Icinga stores the results of host and
+# service checks that have not yet been processed.
+#
+# Note: Make sure that only one instance of Icinga has access
+# to this directory!
+
+check_result_path=/var/lib/icinga/spool/checkresults
+
+
+
+
+# MAX CHECK RESULT FILE AGE
+# This option determines the maximum age (in seconds) which check
+# result files are considered to be valid. Files older than this
+# threshold will be mercilessly deleted without further processing.
+
+max_check_result_file_age=3600
+
+
+
+
+# MAX CHECK RESULT LIST ITEMS !!EXPERIMENTAL!!
+# This experimental option allows you to set the max number of items
+# the checkresult reaper will put onto the checkresult list for further
+# processing by the core. If there are too many, the reaping will be
+# terminated early, allowing the core to process the results sooner.
+# On larger setups, that list might grow too much, and decrease
+# performance on processing. You might experiment with that value, the
+# inner core default is set to 0, disabling that feature.
+# Values:
+# 0 = Disable max check result list items
+# number = set max check result list items
+
+#max_check_result_list_items=1024
+
+
+
+
+# CACHED HOST CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous host check is considered current.
+# Cached host states (from host checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to the host check logic.
+# Too high of a value for this option may result in inaccurate host
+# states being used by Icinga, while a lower value may result in a
+# performance hit for host checks. Use a value of 0 to disable host
+# check caching.
+
+cached_host_check_horizon=15
+
+
+
+# CACHED SERVICE CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous service check is considered current.
+# Cached service states (from service checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to predictive dependency checks.
+# Use a value of 0 to disable service check caching.
+
+cached_service_check_horizon=15
+
+
+
+# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of hosts when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# host dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_host_dependency_checks=1
+
+
+
+# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
+# This option determines whether or not Icinga will attempt to execute
+# checks of service when it predicts that future dependency logic test
+# may be needed. These predictive checks can help ensure that your
+# service dependency logic works well.
+# Values:
+# 0 = Disable predictive checks
+# 1 = Enable predictive checks (default)
+
+enable_predictive_service_dependency_checks=1
+
+
+
+# SOFT STATE DEPENDENCIES
+# This option determines whether or not Icinga will use soft state
+# information when checking host and service dependencies. Normally
+# Icinga will only use the latest hard host or service state when
+# checking dependencies. If you want it to use the latest state (regardless
+# of whether its a soft or hard state type), enable this option.
+# Values:
+# 0 = Don't use soft state dependencies (default)
+# 1 = Use soft state dependencies
+
+soft_state_dependencies=0
+
+
+
+# TIME CHANGE ADJUSTMENT THRESHOLDS
+# These options determine when Icinga will react to detected changes
+# in system time (forward into the future).
+
+#time_change_threshold=900
+
+
+
+# AUTO-RESCHEDULING OPTION
+# This option determines whether or not Icinga will attempt to
+# automatically reschedule active host and service checks to
+# "smooth" them out over time. This can help balance the load on
+# the monitoring server.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_reschedule_checks=0
+
+
+
+# AUTO-RESCHEDULING INTERVAL
+# This option determines how often (in seconds) Icinga will
+# attempt to automatically reschedule checks. This option only
+# has an effect if the auto_reschedule_checks option is enabled.
+# Default is 30 seconds.
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_interval=30
+
+
+
+# AUTO-RESCHEDULING WINDOW
+# This option determines the "window" of time (in seconds) that
+# Icinga will look at when automatically rescheduling checks.
+# Only host and service checks that occur in the next X seconds
+# (determined by this variable) will be rescheduled. This option
+# only has an effect if the auto_reschedule_checks option is
+# enabled. Default is 180 seconds (3 minutes).
+# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
+# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
+
+auto_rescheduling_window=180
+
+
+
+# SLEEP TIME
+# This is the number of seconds to sleep between checking for system
+# events and service checks that need to be run.
+
+sleep_time=0.25
+
+
+
+# TIMEOUT VALUES
+# These options control how much time Icinga will allow various
+# types of commands to execute before killing them off. Options
+# are available for controlling maximum time allotted for
+# service checks, host checks, event handlers, notifications, the
+# ocsp command, and performance data commands. All values are in
+# seconds.
+# Increase the timeout values in case you are experiencing a lot
+# of check timeouts. Addons like e.g. check_mk will perform
+# one combined active servicecheck which could take longer than
+# the default of 60sec.
+
+#service_check_timeout=120
+service_check_timeout=60
+host_check_timeout=30
+event_handler_timeout=30
+notification_timeout=30
+ocsp_timeout=5
+perfdata_timeout=5
+
+
+
+# RETAIN STATE INFORMATION
+# This setting determines whether or not Icinga will save state
+# information for services and hosts before it shuts down. Upon
+# startup Icinga will reload all saved service and host state
+# information before starting to monitor. This is useful for
+# maintaining long-term data on state statistics, etc, but will
+# slow Icinga down a bit when it (re)starts. Since its only
+# a one-time penalty, I think its well worth the additional
+# startup delay.
+
+retain_state_information=1
+
+
+
+# STATE RETENTION FILE
+# This is the file that Icinga should use to store host and
+# service state information before it shuts down. The state
+# information in this file is also read immediately prior to
+# starting to monitor the network when Icinga is restarted.
+# This file is used only if the retain_state_information
+# variable is set to 1.
+
+state_retention_file=/var/cache/icinga/retention.dat
+
+
+
+# SYNC FILE
+# This is an advanced facility to pass a subset of retention
+# information into Icinga on a running system. This is similar
+# to the state retention file with the following difference:
+#
+# - if the last_check value is less than the current last_check,
+# then the state information is ignored (this must be specified
+# immediately after the object identifiers)
+#
+# - downtimes and comments are not identified by an id number, but
+# by other "similar characteristics". This is required to work in
+# a distributed Nagios environment
+# * downtimes: hostname, servicename (if appropriate), author,
+# comment, start_time, end_time, fixed, duration
+# * comments: hostname, servicename, author, comment
+#
+# If this variable is set, then on Icinga startup, the sync file
+# will be read after the retention file has been processed. If the
+# file is read successfully, it will be removed.
+# If the file does not exist, no error will appear.
+# There is also an API that will force a read of the sync file.
+
+#sync_retention_file=/var/cache/icinga/sync.dat
+
+
+
+# RETENTION DATA UPDATE INTERVAL
+# This setting determines how often (in minutes) that Icinga
+# will automatically save retention data during normal operation.
+# If you set this value to 0, Icinga will not save retention
+# data at regular interval, but it will still save retention
+# data before shutting down or restarting. If you have disabled
+# state retention, this option has no effect.
+
+retention_update_interval=60
+
+
+
+# USE RETAINED PROGRAM STATE
+# This setting determines whether or not Icinga will set
+# program status variables based on the values saved in the
+# retention file. If you want to use retained program status
+# information, set this value to 1. If not, set this value
+# to 0.
+
+use_retained_program_state=1
+
+
+# DUMP RETAINED HOST SERVICE STATES TO NEB
+# This setting determines wether or not Icinga will dump host
+# and service states based on the values saved in the retention
+# file to the neb modules. It will already do that on event loop
+# initialization.
+# Changed in Icinga 1.10 to disabled - re-enable if you require it.
+
+dump_retained_host_service_states_to_neb=0
+
+
+
+# USE RETAINED SCHEDULING INFO
+# This setting determines whether or not Icinga will retain
+# the scheduling info (next check time) for hosts and services
+# based on the values saved in the retention file. If you
+# If you want to use retained scheduling info, set this
+# value to 1. If not, set this value to 0.
+
+use_retained_scheduling_info=1
+
+
+
+# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
+# The following variables are used to specify specific host and
+# service attributes that should *not* be retained by Icinga during
+# program restarts.
+#
+# The values of the masks are bitwise ANDs of values specified
+# by the "MODATTR_" definitions found in include/common.h.
+# For example, if you do not want the current enabled/disabled state
+# of flap detection and event handlers for hosts to be retained, you
+# would use a value of 24 for the host attribute mask...
+# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
+
+# This mask determines what host attributes are not retained
+retained_host_attribute_mask=0
+
+# This mask determines what service attributes are not retained
+retained_service_attribute_mask=0
+
+# These two masks determine what process attributes are not retained.
+# There are two masks, because some process attributes have host and service
+# options. For example, you can disable active host checks, but leave active
+# service checks enabled.
+retained_process_host_attribute_mask=0
+retained_process_service_attribute_mask=0
+
+# These two masks determine what contact attributes are not retained.
+# There are two masks, because some contact attributes have host and
+# service options. For example, you can disable host notifications for
+# a contact, but leave service notifications enabled for them.
+retained_contact_host_attribute_mask=0
+retained_contact_service_attribute_mask=0
+
+
+
+# INTERVAL LENGTH
+# This is the seconds per unit interval as used in the
+# host/contact/service configuration files. Setting this to 60 means
+# that each interval is one minute long (60 seconds). Other settings
+# have not been tested much, so your mileage is likely to vary...
+
+interval_length=60
+
+
+
+# AGGRESSIVE HOST CHECKING OPTION
+# If you don't want to turn on aggressive host checking features, set
+# this value to 0 (the default). Otherwise set this value to 1 to
+# enable the aggressive check option. Read the docs for more info
+# on what aggressive host check is or check out the source code in
+# base/checks.c
+
+use_aggressive_host_checking=0
+
+
+
+# SERVICE CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# service checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of service checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_service_checks=1
+
+
+
+# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# service checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_service_checks=1
+
+
+
+# HOST CHECK EXECUTION OPTION
+# This determines whether or not Icinga will actively execute
+# host checks when it initially starts. If this option is
+# disabled, checks are not actively made, but Icinga can still
+# receive and process passive check results that come in. Unless
+# you're implementing redundant hosts or have a special need for
+# disabling the execution of host checks, leave this enabled!
+# Values: 1 = enable checks, 0 = disable checks
+
+execute_host_checks=1
+
+
+
+# PASSIVE HOST CHECK ACCEPTANCE OPTION
+# This determines whether or not Icinga will accept passive
+# host checks results when it initially (re)starts.
+# Values: 1 = accept passive checks, 0 = reject passive checks
+
+accept_passive_host_checks=1
+
+
+
+# NOTIFICATIONS OPTION
+# This determines whether or not Icinga will sent out any host or
+# service notifications when it is initially (re)started.
+# Values: 1 = enable notifications, 0 = disable notifications
+
+enable_notifications=1
+
+
+
+# EVENT HANDLER USE OPTION
+# This determines whether or not Icinga will run any host or
+# service event handlers when it is initially (re)started. Unless
+# you're implementing redundant hosts, leave this option enabled.
+# Values: 1 = enable event handlers, 0 = disable event handlers
+
+enable_event_handlers=1
+
+
+
+# STATE BASED ESCALATION RANGES !!!Experimental!!!
+# This option allows you to enable state based escalation ranges which
+# will allow a more detailed granularity on when an escalation notification
+# may happen, adding a filter based on the current host or service state
+# when checking the escalation for notification viability.
+# This is a behavioural change to the default, and therefore intentionally
+# disabled. Enable at your own risk, as this remains an experimental feature.
+# Values: 1 = enable state based escalation ranges,
+# 0 = disable state based escalation ranges
+
+#enable_state_based_escalation_ranges=0
+
+
+
+# PROCESS PERFORMANCE DATA OPTION
+# This determines whether or not Icinga will process performance
+# data returned from service and host checks. If this option is
+# enabled, host performance data will be processed using the
+# host_perfdata_command (defined below) and service performance
+# data will be processed using the service_perfdata_command (also
+# defined below). Read the HTML docs for more information on
+# performance data.
+# Values: 1 = process performance data, 0 = do not process performance data
+
+process_performance_data=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
+# These commands are run after every host and service check is
+# performed. These commands are executed only if the
+# process_performance_data option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on performance data.
+
+#host_perfdata_command=process-host-perfdata
+#service_perfdata_command=process-service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILES
+# These files are used to store host and service performance data.
+# Performance data is only written to these files if the
+# process_performance_data option (above) is set to 1.
+
+#host_perfdata_file=/tmp/host-perfdata
+#service_perfdata_file=/tmp/service-perfdata
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
+# These options determine what data is written (and how) to the
+# performance data files. The templates may contain macros, special
+# characters (\t for tab, \r for carriage return, \n for newline)
+# and plain text. A newline is automatically added after each write
+# to the performance data file. Some examples of what you can do are
+# shown below.
+
+#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
+#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE MODES
+# This option determines whether or not the host and service
+# performance data files are opened in write ("w") or append ("a")
+# mode. If you want to use named pipes, you should use the special
+# pipe ("p") mode which avoid blocking at startup, otherwise you will
+# likely want the defult append ("a") mode.
+
+#host_perfdata_file_mode=a
+#service_perfdata_file_mode=a
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
+# These options determine how often (in seconds) the host and service
+# performance data files are processed using the commands defined
+# below. A value of 0 indicates the files should not be periodically
+# processed.
+
+#host_perfdata_file_processing_interval=0
+#service_perfdata_file_processing_interval=0
+
+
+
+# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
+# These commands are used to periodically process the host and
+# service performance data files. The interval at which the
+# processing occurs is determined by the options above.
+
+#host_perfdata_file_processing_command=process-host-perfdata-file
+#service_perfdata_file_processing_command=process-service-perfdata-file
+
+
+# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
+# THese options determine wether the core will process empty perfdata
+# results or not. This is needed for distributed monitoring, and intentionally
+# turned on by default.
+# If you don't require empty perfdata - saving some cpu cycles
+# on unwanted macro calculation - you can turn that off. Be careful!
+# Values: 1 = enable, 0 = disable
+
+#host_perfdata_process_empty_results=1
+#service_perfdata_process_empty_results=1
+
+
+
+# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
+# This boolean option determines whether services assigned to empty
+# host groups (host groups with no host members) will cause Icinga to
+# exit with error on start up (or during a configuration check) or not.
+# It's useful to be able to assign services to empty hostgroups when
+# configuration files or pre-cached object files are distributed to
+# various pollers, or when the process of generating Icinga config is
+# automated, or when a set of services is slowly being phased out but
+# should be kept around.
+# The default behavior if the option is not present in the main
+# configuration file is for Icinga to exit with error if services are
+# associated with host groups that have no hosts associated with them.
+
+#allow_empty_hostgroup_assignment=0
+
+
+
+# OBSESS OVER SERVICE CHECKS OPTION
+# This determines whether or not Icinga will obsess over service
+# checks and run the ocsp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over services, 0 = do not obsess (default)
+
+obsess_over_services=0
+
+
+
+# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
+# This is the command that is run for every service check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_services option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ocsp_command=somecommand
+
+
+
+# OBSESS OVER HOST CHECKS OPTION
+# This determines whether or not Icinga will obsess over host
+# checks and run the ochp_command defined below. Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option. Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over hosts, 0 = do not obsess (default)
+
+obsess_over_hosts=0
+
+
+
+# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
+# This is the command that is run for every host check that is
+# processed by Icinga. This command is executed only if the
+# obsess_over_hosts option (above) is set to 1. The command
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ochp_command=somecommand
+
+
+
+# TRANSLATE PASSIVE HOST CHECKS OPTION
+# This determines whether or not Icinga will translate
+# DOWN/UNREACHABLE passive host check results into their proper
+# state for this instance of Icinga. This option is useful
+# if you have distributed or failover monitoring setup. In
+# these cases your other Icinga servers probably have a different
+# "view" of the network, with regards to the parent/child relationship
+# of hosts. If a distributed monitoring server thinks a host
+# is DOWN, it may actually be UNREACHABLE from the point of
+# this Icinga instance. Enabling this option will tell Icinga
+# to translate any DOWN or UNREACHABLE host states it receives
+# passively into the correct state from the view of this server.
+# Values: 1 = perform translation, 0 = do not translate (default)
+
+translate_passive_host_checks=0
+
+
+
+# PASSIVE HOST CHECKS ARE SOFT OPTION
+# This determines whether or not Icinga will treat passive host
+# checks as being HARD or SOFT. By default, a passive host check
+# result will put a host into a HARD state type. This can be changed
+# by enabling this option.
+# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
+
+passive_host_checks_are_soft=0
+
+
+
+# ORPHANED HOST/SERVICE CHECK OPTIONS
+# These options determine whether or not Icinga will periodically
+# check for orphaned host service checks. Since service checks are
+# not rescheduled until the results of their previous execution
+# instance are processed, there exists a possibility that some
+# checks may never get rescheduled. A similar situation exists for
+# host checks, although the exact scheduling details differ a bit
+# from service checks. Orphaned checks seem to be a rare
+# problem and should not happen under normal circumstances.
+# If you have problems with service checks never getting
+# rescheduled, make sure you have orphaned service checks enabled.
+# Values: 1 = enable checks, 0 = disable checks
+
+check_for_orphaned_services=1
+check_for_orphaned_hosts=1
+
+
+
+# SERVICE CHECK TIMEOUT STATE
+# This setting determines the state Icinga will report when a
+# service check times out meaning it does not respond within
+# service_check_timeout seconds. The default is set to Unknown
+# and not Critical.
+# Valid settings are:
+# c - Critical
+# u - Unknown (default)
+# w - Warning
+# o - OK
+
+service_check_timeout_state=u
+
+
+
+# SERVICE FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of service results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_service_freshness=1
+
+
+
+# SERVICE FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of service check results. If you have
+# disabled service freshness checking, this option has no effect.
+
+service_freshness_check_interval=60
+
+
+
+# HOST FRESHNESS CHECK OPTION
+# This option determines whether or not Icinga will periodically
+# check the "freshness" of host results. Enabling this option
+# is useful for ensuring passive checks are received in a timely
+# manner.
+# Values: 1 = enabled freshness checking, 0 = disable freshness checking
+
+check_host_freshness=0
+
+
+
+# HOST FRESHNESS CHECK INTERVAL
+# This setting determines how often (in seconds) Icinga will
+# check the "freshness" of host check results. If you have
+# disabled host freshness checking, this option has no effect.
+
+host_freshness_check_interval=60
+
+
+
+
+# ADDITIONAL FRESHNESS THRESHOLD LATENCY
+# This setting determines the number of seconds that Icinga
+# will add to any host and service freshness thresholds that
+# it calculates (those not explicitly specified by the user).
+
+additional_freshness_latency=15
+
+
+
+
+# FLAP DETECTION OPTION
+# This option determines whether or not Icinga will try
+# and detect hosts and services that are "flapping".
+# Flapping occurs when a host or service changes between
+# states too frequently. When Icinga detects that a
+# host or service is flapping, it will temporarily suppress
+# notifications for that host/service until it stops
+# flapping. Flap detection is very experimental, so read
+# the HTML documentation before enabling this feature!
+# Values: 1 = enable flap detection
+# 0 = disable flap detection (default)
+
+enable_flap_detection=1
+
+
+
+# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
+# Read the HTML documentation on flap detection for
+# an explanation of what this option does. This option
+# has no effect if flap detection is disabled.
+
+low_service_flap_threshold=5.0
+high_service_flap_threshold=20.0
+low_host_flap_threshold=5.0
+high_host_flap_threshold=20.0
+
+
+
+# DATE FORMAT OPTION
+# This option determines how short dates are displayed. Valid options
+# include:
+# us (MM-DD-YYYY HH:MM:SS)
+# euro (DD-MM-YYYY HH:MM:SS)
+# iso8601 (YYYY-MM-DD HH:MM:SS)
+# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
+#
+
+date_format=iso8601
+
+
+
+
+# TIMEZONE OFFSET
+# This option is used to override the default timezone that this
+# instance of Icinga runs in. If not specified, Icinga will use
+# the system configured timezone.
+#
+# NOTE: In order to display the correct timezone in the CGIs, you
+# will also need to alter the Apache directives for the CGI path
+# to include your timezone. Example:
+#
+# <Directory "/usr/local/icinga/sbin/">
+# SetEnv TZ "Australia/Brisbane"
+# ...
+# </Directory>
+
+#use_timezone=US/Mountain
+#use_timezone=Australia/Brisbane
+
+
+
+
+# P1.PL FILE LOCATION
+# This value determines where the p1.pl perl script (used by the
+# embedded Perl interpreter) is located. If you didn't compile
+# Icinga with embedded Perl support, this option has no effect.
+
+p1_file=/usr/lib/icinga/p1.pl
+
+
+
+# EMBEDDED PERL INTERPRETER OPTION
+# This option determines whether or not the embedded Perl interpreter
+# will be enabled during runtime. This option has no effect if Icinga
+# has not been compiled with support for embedded Perl.
+# This option is intentionally disabled by default, because embedded
+# perl can cause memory leaks and make Icinga unstable if not properly
+# used.
+# Only enable this setting when you really know what you are doing!
+# Values: 0 = disable interpreter, 1 = enable interpreter
+
+enable_embedded_perl=1
+
+
+
+# EMBEDDED PERL USAGE OPTION
+# This option determines whether or not Icinga will process Perl plugins
+# and scripts with the embedded Perl interpreter if the plugins/scripts
+# do not explicitly indicate whether or not it is okay to do so. Read
+# the HTML documentation on the embedded Perl interpreter for more
+# information on how this option works.
+
+use_embedded_perl_implicitly=1
+
+
+
+# EVENT HANDLERS FOR STALKED HOSTS/SERVICES
+# Allow running event handlers for stalked hosts/services in order
+# to forward to external systems.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_event_handlers_for_hosts=0
+stalking_event_handlers_for_services=0
+
+
+
+# NOTIFICATIONS FOR STALKED HOSTS/SERVICES
+# Allow notifications for stalked hosts/services globally
+# for all contacts in order to notify about a stalking
+# alert.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_notifications_for_hosts=0
+stalking_notifications_for_services=0
+
+
+
+# ILLEGAL OBJECT NAME CHARACTERS
+# This option allows you to specify illegal characters that cannot
+# be used in host names, service descriptions, or names of other
+# object types.
+
+illegal_object_name_chars=`~!$%^&*|'"<>?,()=
+
+
+
+# ILLEGAL MACRO OUTPUT CHARACTERS
+# This option allows you to specify illegal characters that are
+# stripped from macros before being used in notifications, event
+# handlers, etc. This DOES NOT affect macros used in service or
+# host check commands.
+# The following macros are stripped of the characters you specify:
+# $HOSTOUTPUT$
+# $HOSTPERFDATA$
+# $HOSTACKAUTHOR$
+# $HOSTACKCOMMENT$
+# $SERVICEOUTPUT$
+# $SERVICEPERFDATA$
+# $SERVICEACKAUTHOR$
+# $SERVICEACKCOMMENT$
+
+illegal_macro_output_chars=`~$&|'"<>
+
+
+
+# KEEP UNKNOWN MACROS
+# This option can be used to keep unknown macros within the output.
+# e.g. check_proc -C $foo$ will remain.
+# This was the default in versions older than Icinga 1.8, but now
+# the default is to remove those macros from the output, causing
+# the shell to interpret $foo and leaving a single $ there. See
+# #2291 for further information.
+# Make sure to escape single dollar signs with another '$', as the
+# docs describe. Other than that, enable this setting to revert to
+# the old behaviour.
+
+keep_unknown_macros=1
+
+
+
+# REGULAR EXPRESSION MATCHING
+# This option controls whether or not regular expression matching
+# takes place in the object config files. Regular expression
+# matching is used to match host, hostgroup, service, and service
+# group names/descriptions in some fields of various object types.
+# Values: 1 = enable regexp matching, 0 = disable regexp matching
+
+use_regexp_matching=0
+
+
+
+# "TRUE" REGULAR EXPRESSION MATCHING
+# This option controls whether or not "true" regular expression
+# matching takes place in the object config files. This option
+# only has an effect if regular expression matching is enabled
+# (see above). If this option is DISABLED, regular expression
+# matching only occurs if a string contains wildcard characters
+# (* and ?). If the option is ENABLED, regexp matching occurs
+# all the time (which can be annoying).
+# Values: 1 = enable true matching, 0 = disable true matching
+
+use_true_regexp_matching=0
+
+
+
+# ADMINISTRATOR EMAIL/PAGER ADDRESSES
+# The email and pager address of a global administrator (likely you).
+# Icinga never uses these values itself, but you can access them by
+# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
+# commands.
+
+admin_email=root@localhost
+admin_pager=pageroot@localhost
+
+
+
+# DAEMON CORE DUMP OPTION
+# This option determines whether or not Icinga is allowed to create
+# a core dump when it runs as a daemon. Note that it is generally
+# considered bad form to allow this, but it may be useful for
+# debugging purposes. Enabling this option doesn't guarantee that
+# a core file will be produced, but that's just life...
+# Values: 1 - Allow core dumps
+# 0 - Do not allow core dumps (default)
+
+daemon_dumps_core=0
+
+
+
+# LARGE INSTALLATION TWEAKS OPTION
+# This option determines whether or not Icinga will take some shortcuts
+# which can save on memory and CPU usage in large Icinga installations.
+# Read the documentation for more information on the benefits/tradeoffs
+# of enabling this option.
+# Values: 1 - Enabled tweaks
+# 0 - Disable tweaks (default)
+
+use_large_installation_tweaks=0
+
+
+
+# ENABLE ENVIRONMENT MACROS
+# This option determines whether or not Icinga will make all standard
+# macros available as environment variables when host/service checks
+# and system commands (event handlers, notifications, etc.) are
+# executed. Enabling this option can cause performance issues in
+# large installations, as it will consume a bit more memory and (more
+# importantly) consume more CPU.
+# Keep in mind that various addons/plugins will require this setting
+# to be enabled (e.g. check_oracle_health) for special usage.
+# Values: 1 - Enable environment variable macros
+# 0 - Disable environment variable macros (default)
+
+enable_environment_macros=1
+
+
+
+# CHILD PROCESS MEMORY OPTION
+# This option determines whether or not Icinga will free memory in
+# child processes (processed used to execute system commands and host/
+# service checks). If you specify a value here, it will override
+# program defaults.
+# Value: 1 - Free memory in child processes
+# 0 - Do not free memory in child processes
+
+#free_child_process_memory=1
+
+
+
+# CHILD PROCESS FORKING BEHAVIOR
+# This option determines how Icinga will fork child processes
+# (used to execute system commands and host/service checks). Normally
+# child processes are fork()ed twice, which provides a very high level
+# of isolation from problems. Fork()ing once is probably enough and will
+# save a great deal on CPU usage (in large installs), so you might
+# want to consider using this. If you specify a value here, it will
+# program defaults.
+# Value: 1 - Child processes fork() twice
+# 0 - Child processes fork() just once
+
+#child_processes_fork_twice=1
+
+
+
+# DEBUG LEVEL
+# This option determines how much (if any) debugging information will
+# be written to the debug file. OR values together to log multiple
+# types of information.
+# Values:
+# -1 = Everything
+# 0 = Nothing
+# 1 = Functions
+# 2 = Configuration
+# 4 = Process information
+# 8 = Scheduled events
+# 16 = Host/service checks
+# 32 = Notifications
+# 64 = Event broker
+# 128 = External commands
+# 256 = Commands
+# 512 = Scheduled downtime
+# 1024 = Comments
+# 2048 = Macros
+
+debug_level=0
+
+
+
+# DEBUG VERBOSITY
+# This option determines how verbose the debug log out will be.
+# Values: 0 = Brief output
+# 1 = More detailed
+# 2 = Very detailed
+
+debug_verbosity=2
+
+
+
+# DEBUG FILE
+# This option determines where Icinga should write debugging information.
+
+debug_file=/var/log/icinga/icinga.debug
+
+
+
+# MAX DEBUG FILE SIZE
+# This option determines the maximum size (in bytes) of the debug file. If
+# the file grows larger than this size, it will be renamed with a .old
+# extension. If a file already exists with a .old extension it will
+# automatically be deleted. This helps ensure your disk space usage doesn't
+# get out of control when debugging Icinga.
+
+# 100M
+max_debug_file_size=100000000
diff --git a/roles/icinga-yb/files/nt.cfg b/roles/icinga-yb/files/nt.cfg
new file mode 100644
index 0000000..b461aca
--- /dev/null
+++ b/roles/icinga-yb/files/nt.cfg
@@ -0,0 +1,15 @@
+# If you are confused about this command definition, cause you was
+# reading other suggestions, please have a look into
+# /usr/share/doc/nagios-plugins/README.Debian
+
+# 'check_nt' command definition
+#define command {
+# command_name check_nt
+# command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -v '$ARG1$'
+#}
+
+# 'check_nscp' command definition
+define command {
+ command_name check_nscp
+ command_line /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$' -p 12489 -v '$ARG1$'
+}
diff --git a/roles/icinga-yb/handlers/main.yml b/roles/icinga-yb/handlers/main.yml
new file mode 100644
index 0000000..721651e
--- /dev/null
+++ b/roles/icinga-yb/handlers/main.yml
@@ -0,0 +1,12 @@
+---
+ - name: restart icinga
+ service: name=icinga state=restarted
+
+ - name: stop icinga
+ service: name=icinga state=stopped
+
+ - name: start icinga
+ service: name=icinga state=started
+
+ - name: restart apache
+ service: name=apache2 state=restarted
diff --git a/roles/icinga-yb/tasks/main.yml b/roles/icinga-yb/tasks/main.yml
new file mode 100644
index 0000000..7e7c3e5
--- /dev/null
+++ b/roles/icinga-yb/tasks/main.yml
@@ -0,0 +1,102 @@
+---
+- name: Installation apache2
+ apt: name=apache2 state=present
+
+- name: Installation snmp
+ apt: name=snmp state=present
+
+- name: Installation de icinga
+ apt: name=icinga state=present
+
+- name: Installation de nagios-plugins
+ apt: name=nagios-plugins state=present
+
+- name: Installation de nagios-snmp-plugins
+ apt: name=nagios-snmp-plugins state=present
+
+- name: Installation des dépendances dns
+ apt: name=libnet-dns-perl state=present
+
+#- name: Copie de fichier apache.conf
+# copy: remote_src=true src=/etc/icinga/apache2.conf dest=/etc/apache2/sites-available/icinga.conf
+
+#- name: activation du site de icinga
+# shell: a2ensite icinga
+# notify:
+# - restart icinga
+
+- name: changement de mot de passe de icingaadmin
+ shell: htpasswd -dbc /etc/icinga/htpasswd.users icingaadmin root
+
+- name: Copie du fichier commands.cfg
+ copy: src=commands.cfg dest=/etc/icinga/commands.cfg
+
+- name: Copie du fichier icinga.cfg
+ copy: src=icinga.cfg dest=/etc/icinga
+
+- name: Copie du fichier contacts_icinga.cfg
+ copy: src=cfg/contacts_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier hostgroups_icinga.cfg
+ copy: src=cfg/hostgroups_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier r-ext.cfg
+ copy: src=cfg/r-ext.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier r-int.cfg
+ copy: src=cfg/r-int.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-adm.cfg
+ copy: src=cfg/s-adm.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier services_icinga.cfg
+ copy: src=cfg/services_icinga.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-infra.cfg
+ copy: src=cfg/s-infra.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-infra-adm.cfg
+ copy: src=cfg/s-infra-adm.cfg dest=/etc/icinga/objects
+
+#- name: Copie du fichier s-lb.cfg
+# copy: src=cfg/s-lb.cfg dest=/etc/icinga/objects
+
+#- name: Copie du fichier s-lb-adm.cfg
+# copy: src=cfg/s-lb-adm.cfg dest=/etc/icinga/objects
+
+- name: Copie du fichier s-win
+ copy: src=cfg/s-win.cfg dest=/etc/icinga/objects
+
+- name: Changement droit notif
+ shell: chmod 644 /var/log/icinga/icinga.log
+
+- name: copie nt.cfg
+ copy: src=nt.cfg dest=/etc/nagios-plugins/config
+
+#- name: copie dns.cfg
+# copy: remote_src=true src=dns.cfg dest=/etc/nagios-plugins/config
+
+- name: stop icinga
+ service:
+ name: icinga
+ state: stopped
+
+- name: modif des droits /var/lib/icinga/rw/
+ shell: dpkg-statoverride --update --add nagios www-data 2710 /var/lib/icinga/rw/
+
+- name: modif des droits /var/lib/icinga/
+ shell: dpkg-statoverride --update --add nagios nagios 751 /var/lib/icinga/
+
+- name: start icinga
+ service:
+ name: icinga
+ state: started
+
+- name: copie check traffic
+ copy: src=check_iftraffic3.pl dest=/usr/lib/nagios/plugins
+
+- name: modif des droits plugin traffic
+ shell: chmod 755 /usr/lib/nagios/plugins/check_iftraffic3.pl
+
+- name: message d'information
+ debug: msg="Pour superviser le Windows, il faut installer NSClient++"
diff --git a/roles/itil-cs/files/.my.cnf b/roles/itil-cs/files/.my.cnf
new file mode 100644
index 0000000..34d0e25
--- /dev/null
+++ b/roles/itil-cs/files/.my.cnf
@@ -0,0 +1,3 @@
+[client]
+user=root
+password=root
diff --git a/roles/itil-cs/files/glpi.conf b/roles/itil-cs/files/glpi.conf
new file mode 100644
index 0000000..4c37222
--- /dev/null
+++ b/roles/itil-cs/files/glpi.conf
@@ -0,0 +1,12 @@
+DocumentRoot /var/www/glpi
+ <Directory /var/www/glpi>
+ Options Indexes FollowSymLinks MultiViews
+ AllowOverride All
+ Order allow,deny
+ allow from all
+ AuthType Basic
+ </Directory>
+
+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined
+ CustomLog ${APACHE_LOG_DIR}/glpi_access.log combined
+ ErrorLog ${APACHE_LOG_DIR}/glpi_error.log
diff --git a/roles/itil-cs/files/script b/roles/itil-cs/files/script
new file mode 100644
index 0000000..f400139
--- /dev/null
+++ b/roles/itil-cs/files/script
@@ -0,0 +1,4 @@
+#!/bin/sh
+chm= »/var/www/html/glpi/files/_dumps »
+# Dump base GLPI
+mysqldump -uroot -proot glpi |gzip > $chm/$(date +%Y-%m-%d).sql.gz
\ No newline at end of file
diff --git a/roles/itil-cs/handlers/main.yml b/roles/itil-cs/handlers/main.yml
new file mode 100644
index 0000000..9744cf7
--- /dev/null
+++ b/roles/itil-cs/handlers/main.yml
@@ -0,0 +1,6 @@
+---
+ - name: restart apache2
+ service: name=apache2 state=restarted
+
+ - name: restart mysql-server
+ service: name=mysql-server state=restarted
diff --git a/roles/itil-cs/tasks/main.yml b/roles/itil-cs/tasks/main.yml
new file mode 100644
index 0000000..ced06f0
--- /dev/null
+++ b/roles/itil-cs/tasks/main.yml
@@ -0,0 +1,65 @@
+---
+ - name: Install apache2
+ apt: name=apache2 state=present update_cache=yes
+ notify:
+ - restart apache2
+
+ - name: Install php5
+ apt: name=php5 state=present update_cache=yes
+
+ - name: Install php5-mysql
+ apt: name=php5-mysql state=present update_cache=yes
+
+ - name: Install php5-gd
+ apt: name=php5-gd state=present update_cache=yes
+
+ - name: Install php5-curl
+ apt: name=php5-curl state=present update_cache=yes
+
+ - name: Install php5-imap
+ apt: name=php5-imap state=present update_cache=yes
+
+ - name: Install php5-ldap
+ apt: name=php5-ldap state=present update_cache=yes
+
+ - name: Download GLPI from Internet
+ copy: src=glpi-9.1.3.tgz dest=/var/www/
+
+ - name: Instructions
+ debug: msg="En cas de problemes, relancez le playbook une seconde fois."
+
+ - name: unpack tarball
+ unarchive: src=/var/www/glpi-9.1.3.tgz dest=/var/www/
+
+ - name: Fix permissions
+ shell: chown -R www-data:www-data /var/www/glpi/
+
+ - name: copy .my.cnf file with root password credentials
+ copy: src=.my.cnf dest=/root/tools/ansible/.my.cnf owner=root mode=0600
+
+
+ - name: Print web instructions
+ debug: msg="/!\ Se rendre sur http://adresse_ip_de_votre_serveur/glpi et suivre l'installation"
+
+ - name: Download Fusioninventory from Internet
+ copy: src=fusioninventory-for-glpi_0.85+1.3.tar.gz dest=/var/www/glpi/plugins
+
+ - name: unpack tarball
+ unarchive: src=/var/www/glpi/plugins/fusioninventory-for-glpi_0.85+1.3.tar.gz dest=/var/www/glpi/plugins
+
+ - name: Print web instructions
+ debug: msg="(i) Fusioninventory plugin installed in /var/www/glpi/plugins"
+
+ - name: copy glpi.conf
+ copy: src=glpi.conf dest=/etc/apache2/sites-available/
+
+ - name: activation du site glpi
+ shell: a2ensite glpi.conf
+ notify:
+ - restart apache2
+
+ - name: copie script
+ copy: src=script dest=/root/
+
+ - name: chmod
+ shell: chmod +x /root/script
\ No newline at end of file
diff --git a/roles/itil/files/.my.cnf b/roles/itil/files/.my.cnf
new file mode 100644
index 0000000..34d0e25
--- /dev/null
+++ b/roles/itil/files/.my.cnf
@@ -0,0 +1,3 @@
+[client]
+user=root
+password=root
diff --git a/roles/itil/files/dbdump b/roles/itil/files/dbdump
new file mode 100644
index 0000000..f892580
--- /dev/null
+++ b/roles/itil/files/dbdump
@@ -0,0 +1,4 @@
+#!/bin/sh
+chm="/var/www/html/glpi/files/_dumps"
+# Dump base GLPI
+mysqldump -uroot -proot glpi |gzip > $chm/$(date +%Y-%m-%d).sql.gz
diff --git a/roles/itil/files/glpi.conf b/roles/itil/files/glpi.conf
new file mode 100644
index 0000000..4c37222
--- /dev/null
+++ b/roles/itil/files/glpi.conf
@@ -0,0 +1,12 @@
+DocumentRoot /var/www/glpi
+ <Directory /var/www/glpi>
+ Options Indexes FollowSymLinks MultiViews
+ AllowOverride All
+ Order allow,deny
+ allow from all
+ AuthType Basic
+ </Directory>
+
+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined
+ CustomLog ${APACHE_LOG_DIR}/glpi_access.log combined
+ ErrorLog ${APACHE_LOG_DIR}/glpi_error.log
diff --git a/roles/itil/handlers/main.yml b/roles/itil/handlers/main.yml
new file mode 100644
index 0000000..2d5614c
--- /dev/null
+++ b/roles/itil/handlers/main.yml
@@ -0,0 +1,9 @@
+---
+ - name: restart php-fpm
+ service: name=php7.0-fpm state=restarted
+
+ - name: restart nginx
+ service: name=nginx state=restarted
+
+ - name: restart mariadb-server
+ service: name=mariadb-server state=restarted
diff --git a/roles/itil/tasks/main.yml b/roles/itil/tasks/main.yml
new file mode 100644
index 0000000..0b565cc
--- /dev/null
+++ b/roles/itil/tasks/main.yml
@@ -0,0 +1,120 @@
+---
+ - name: Installation des paquets
+ apt:
+ state: latest
+ name:
+ - nginx
+ - php-fpm
+ - php-mbstring
+ - php-mysql
+ - php-gd
+ - php-curl
+ - php-xml
+ - php-apcu
+ - php-ldap
+ - php-imap
+ - php-xmlrpc
+ - php-cas
+ - python-mysqldb
+ - mariadb-server
+
+ - name: Changement listen dans le fichier conf de php7.3
+ replace:
+ dest: /etc/php/7.3/fpm/pool.d/www.conf
+ regexp: 'listen = /run/php/php7.3-fpm.sock'
+ replace: 'listen = 127.0.0.1:9000'
+ backup: yes
+
+ - name: Effacement block nginx default
+ file: path=/etc/nginx/sites-enabled/default state=absent
+
+ - name: Creation fichier block nginx
+ template: src=block.j2 dest=/etc/nginx/sites-enabled/glpi
+
+ - name: Remplacement dans le fichier de conf php du timeout
+ replace:
+ dest: /etc/php/7.3/fpm/php.ini
+ regexp: 'max_execution_time = 30'
+ replace: 'max_execution_time = 600'
+ backup: yes
+
+ notify:
+ - restart nginx
+
+ - name: Creation de la base de donnee mysql
+ mysql_db: name={{ glpi_dbname }} state=present
+
+ - name: Creation de l'utilisateur mysql avec tous les privileges
+ mysql_user:
+ name={{ glpi_dbuser }}
+ password={{ glpi_dbpasswd }}
+ priv=*.*:ALL
+
+ - name: Creation du repertoire {{ glpi_dir }}
+ file: path={{ glpi_dir }} state=directory owner=www-data group=www-data
+
+ - name: Installation de GLPI
+ unarchive:
+ src: http://depl/gsbstore/glpi-{{ glpi_version }}.tgz
+ dest: /var/www/html
+ remote_src: yes
+ owner: www-data
+ group: www-data
+
+ - name: Changement des attributs {{ glpi_dir }}
+ file: path={{ glpi_dir }} owner=www-data group=www-data mode=0755 recurse=yes
+
+ - name: Changement des attributs {{ glpi_dir }}/plugins
+ file:
+ path: "{{ glpi_dir }}/plugins"
+ mode: 0777
+ recurse: yes
+
+ - name: Attribution des permissions
+ shell: chown -R www-data:www-data /var/www/html/glpi/
+
+# - name: copy .my.cnf file with root password credentials
+# copy: src=.my.cnf dest=/root/tools/ansible/.my.cnf owner=root mode=0600
+
+ - name: Installation de Fusioninventory pour Linux
+ unarchive:
+ src: http://depl/gsbstore/fusioninventory-{{ fd_version }}.tar.bz2
+ dest: /var/www/html/glpi/plugins
+ remote_src: yes
+
+ - name: Creation de ficlient
+ file:
+ path: /var/www/html/ficlients
+ state: directory
+ owner: www-data
+ group: www-data
+ mode: 0775
+
+ - name: Attribution des droits nginx.index
+ file:
+ path: /var/www/html/index.nginx-debian.html
+ owner: www-data
+ group: www-data
+ mode: 0775
+
+ - name: Installation de FusionInventory windows x64
+ get_url:
+ url: http://depl/gsbstore/fusioninventory-agent_windows-{{ fd_version64 }}.exe
+ dest: "/var/www/html/ficlients"
+
+ - name: Installation de FusionInventory windows x86
+ get_url:
+ url: http://depl/gsbstore/fusioninventory-agent_windows-{{ fd_version86 }}.exe
+ dest: "/var/www/html/ficlients"
+
+ - name: Copie du script dbdump
+ copy: src=dbdump dest=/root/
+
+ - name: chmod de dbdump
+ shell: chmod +x /root/dbdump
+
+ - debug:
+ msg: "Redemarrez le serveur GLPI"
+
+ - debug:
+ msg: "L'utilisateur mysql:ID:glpi et MDP:glpi"
diff --git a/roles/itil/templates/block.j2 b/roles/itil/templates/block.j2
new file mode 100644
index 0000000..0cec4f7
--- /dev/null
+++ b/roles/itil/templates/block.j2
@@ -0,0 +1,23 @@
+server {
+ listen 80 default_server;
+ root {{ glpi_dir }};
+ index index.php;
+ server_name localhost;
+
+ location / {try_files $uri $uri/ index.php;}
+
+ #prise en charge PHP
+ location ~ \.php$ {
+ fastcgi_pass 127.0.0.1:9000;
+ fastcgi_index index.php;
+ include /etc/nginx/fastcgi_params;
+ fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
+ include fastcgi_params;
+ fastcgi_param SERVER_NAME $host;
+ }
+
+ location /ficlients {
+ root /var/www/html;
+ autoindex on;
+ }
+}
diff --git a/roles/mariadb-ab/README.md b/roles/mariadb-ab/README.md
new file mode 100644
index 0000000..225dd44
--- /dev/null
+++ b/roles/mariadb-ab/README.md
@@ -0,0 +1,38 @@
+Role Name
+=========
+
+A brief description of the role goes here.
+
+Requirements
+------------
+
+Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
+
+Role Variables
+--------------
+
+A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.
+
+Dependencies
+------------
+
+A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
+
+Example Playbook
+----------------
+
+Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
+
+ - hosts: servers
+ roles:
+ - { role: username.rolename, x: 42 }
+
+License
+-------
+
+BSD
+
+Author Information
+------------------
+
+An optional section for the role authors to include contact information, or a website (HTML is not allowed).
diff --git a/roles/mariadb-ab/_travis.yml b/roles/mariadb-ab/_travis.yml
new file mode 100644
index 0000000..36bbf62
--- /dev/null
+++ b/roles/mariadb-ab/_travis.yml
@@ -0,0 +1,29 @@
+---
+language: python
+python: "2.7"
+
+# Use the new container infrastructure
+sudo: false
+
+# Install ansible
+addons:
+ apt:
+ packages:
+ - python-pip
+
+install:
+ # Install ansible
+ - pip install ansible
+
+ # Check ansible version
+ - ansible --version
+
+ # Create ansible.cfg with correct roles_path
+ - printf '[defaults]\nroles_path=../' >ansible.cfg
+
+script:
+ # Basic role syntax check
+ - ansible-playbook tests/test.yml -i tests/inventory --syntax-check
+
+notifications:
+ webhooks: https://galaxy.ansible.com/api/v1/notifications/
\ No newline at end of file
diff --git a/roles/mariadb-ab/defaults/main.yml b/roles/mariadb-ab/defaults/main.yml
new file mode 100644
index 0000000..bf0e537
--- /dev/null
+++ b/roles/mariadb-ab/defaults/main.yml
@@ -0,0 +1,2 @@
+---
+# defaults file for mariadb
diff --git a/roles/mariadb-ab/files/my.cnf b/roles/mariadb-ab/files/my.cnf
new file mode 100644
index 0000000..1308652
--- /dev/null
+++ b/roles/mariadb-ab/files/my.cnf
@@ -0,0 +1,128 @@
+#
+# The MySQL database server configuration file.
+#
+# You can copy this to one of:
+# - "/etc/mysql/my.cnf" to set global options,
+# - "~/.my.cnf" to set user-specific options.
+#
+# One can use all long options that the program supports.
+# Run program with --help to get a list of available options and with
+# --print-defaults to see which it would actually understand and use.
+#
+# For explanations see
+# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
+
+# This will be passed to all mysql clients
+# It has been reported that passwords should be enclosed with ticks/quotes
+# escpecially if they contain "#" chars...
+# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
+[client]
+port = 3306
+socket = /var/run/mysqld/mysqld.sock
+
+# Here is entries for some specific programs
+# The following values assume you have at least 32M ram
+
+# This was formally known as [safe_mysqld]. Both versions are currently parsed.
+[mysqld_safe]
+socket = /var/run/mysqld/mysqld.sock
+nice = 0
+
+[mysqld]
+#
+# * Basic Settings
+#
+user = mysql
+pid-file = /var/run/mysqld/mysqld.pid
+socket = /var/run/mysqld/mysqld.sock
+port = 3306
+basedir = /usr
+datadir = /var/lib/mysql
+tmpdir = /tmp
+lc-messages-dir = /usr/share/mysql
+skip-external-locking
+#
+# Instead of skip-networking the default is now to listen only on
+# localhost which is more compatible and is not less secure.
+#bind-address = 127.0.0.1
+#
+# * Fine Tuning
+#
+key_buffer = 16M
+max_allowed_packet = 16M
+thread_stack = 192K
+thread_cache_size = 8
+# This replaces the startup script and checks MyISAM tables if needed
+# the first time they are touched
+myisam-recover = BACKUP
+#max_connections = 100
+#table_cache = 64
+#thread_concurrency = 10
+#
+# * Query Cache Configuration
+#
+query_cache_limit = 1M
+query_cache_size = 16M
+#
+# * Logging and Replication
+#
+# Both location gets rotated by the cronjob.
+# Be aware that this log type is a performance killer.
+# As of 5.1 you can enable the log at runtime!
+#general_log_file = /var/log/mysql/mysql.log
+#general_log = 1
+#
+# Error log - should be very few entries.
+#
+log_error = /var/log/mysql/error.log
+#
+# Here you can see queries with especially long duration
+#slow_query_log_file = /var/log/mysql/mysql-slow.log
+#slow_query_log = 1
+#long_query_time = 2
+#log_queries_not_using_indexes
+#
+# The following can be used as easy to replay backup logs or for replication.
+# note: if you are setting up a replication slave, see README.Debian about
+# other settings you may need to change.
+#server-id = 1
+#log_bin = /var/log/mysql/mysql-bin.log
+expire_logs_days = 10
+max_binlog_size = 100M
+#binlog_do_db = include_database_name
+#binlog_ignore_db = include_database_name
+#
+# * InnoDB
+#
+# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
+# Read the manual for more InnoDB related options. There are many!
+#
+# * Security Features
+#
+# Read the manual, too, if you want chroot!
+# chroot = /var/lib/mysql/
+#
+# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
+#
+# ssl-ca=/etc/mysql/cacert.pem
+# ssl-cert=/etc/mysql/server-cert.pem
+# ssl-key=/etc/mysql/server-key.pem
+
+
+
+[mysqldump]
+quick
+quote-names
+max_allowed_packet = 16M
+
+[mysql]
+#no-auto-rehash # faster start of mysql but no tab completition
+
+[isamchk]
+key_buffer = 16M
+
+#
+# * IMPORTANT: Additional settings that can override those from this file!
+# The files must end with '.cnf', otherwise they'll be ignored.
+#
+!includedir /etc/mysql/conf.d/
diff --git a/roles/mariadb-ab/handlers/main.yml b/roles/mariadb-ab/handlers/main.yml
new file mode 100644
index 0000000..49ba9f4
--- /dev/null
+++ b/roles/mariadb-ab/handlers/main.yml
@@ -0,0 +1,2 @@
+---
+# handlers file for mariadb
diff --git a/roles/mariadb-ab/meta/main.yml b/roles/mariadb-ab/meta/main.yml
new file mode 100644
index 0000000..6f81d2b
--- /dev/null
+++ b/roles/mariadb-ab/meta/main.yml
@@ -0,0 +1,232 @@
+galaxy_info:
+ author: your name
+ description: your description
+ company: your company (optional)
+
+ # If the issue tracker for your role is not on github, uncomment the
+ # next line and provide a value
+ # issue_tracker_url: http://example.com/issue/tracker
+
+ # Some suggested licenses:
+ # - BSD (default)
+ # - MIT
+ # - GPLv2
+ # - GPLv3
+ # - Apache
+ # - CC-BY
+ license: license (GPLv2, CC-BY, etc)
+
+ min_ansible_version: 1.2
+
+ # Optionally specify the branch Galaxy will use when accessing the GitHub
+ # repo for this role. During role install, if no tags are available,
+ # Galaxy will use this branch. During import Galaxy will access files on
+ # this branch. If travis integration is cofigured, only notification for this
+ # branch will be accepted. Otherwise, in all cases, the repo's default branch
+ # (usually master) will be used.
+ #github_branch:
+
+ #
+ # Below are all platforms currently available. Just uncomment
+ # the ones that apply to your role. If you don't see your
+ # platform on this list, let us know and we'll get it added!
+ #
+ #platforms:
+ #- name: OpenBSD
+ # versions:
+ # - all
+ # - 5.6
+ # - 5.7
+ # - 5.8
+ # - 5.9
+ # - 6.0
+ # - 6.1
+ # - 6.2
+ #- name: Fedora
+ # versions:
+ # - all
+ # - 16
+ # - 17
+ # - 18
+ # - 19
+ # - 20
+ # - 21
+ # - 22
+ # - 23
+ # - 24
+ # - 25
+ # - 26
+ #- name: DellOS
+ # versions:
+ # - all
+ # - 10
+ # - 6
+ # - 9
+ #- name: MacOSX
+ # versions:
+ # - all
+ # - 10.10
+ # - 10.11
+ # - 10.12
+ # - 10.7
+ # - 10.8
+ # - 10.9
+ #- name: Synology
+ # versions:
+ # - all
+ # - any
+ #- name: Junos
+ # versions:
+ # - all
+ # - any
+ #- name: GenericBSD
+ # versions:
+ # - all
+ # - any
+ #- name: Void Linux
+ # versions:
+ # - all
+ # - any
+ #- name: GenericLinux
+ # versions:
+ # - all
+ # - any
+ #- name: NXOS
+ # versions:
+ # - all
+ # - any
+ #- name: macOS
+ # versions:
+ # - all
+ # - Sierra
+ #- name: IOS
+ # versions:
+ # - all
+ # - any
+ #- name: Amazon
+ # versions:
+ # - all
+ # - 2013.03
+ # - 2013.09
+ # - 2016.03
+ # - 2016.09
+ #- name: ArchLinux
+ # versions:
+ # - all
+ # - any
+ #- name: FreeBSD
+ # versions:
+ # - all
+ # - 10.0
+ # - 10.1
+ # - 10.2
+ # - 10.3
+ # - 11.0
+ # - 11.1
+ # - 8.0
+ # - 8.1
+ # - 8.2
+ # - 8.3
+ # - 8.4
+ # - 9.0
+ # - 9.1
+ # - 9.1
+ # - 9.2
+ # - 9.3
+ #- name: Ubuntu
+ # versions:
+ # - all
+ # - artful
+ # - lucid
+ # - maverick
+ # - natty
+ # - oneiric
+ # - precise
+ # - quantal
+ # - raring
+ # - saucy
+ # - trusty
+ # - utopic
+ # - vivid
+ # - wily
+ # - xenial
+ # - yakkety
+ # - zesty
+ #- name: Debian
+ # versions:
+ # - all
+ # - etch
+ # - jessie
+ # - lenny
+ # - sid
+ # - squeeze
+ # - stretch
+ # - wheezy
+ #- name: Alpine
+ # versions:
+ # - all
+ # - any
+ #- name: EL
+ # versions:
+ # - all
+ # - 5
+ # - 6
+ # - 7
+ #- name: Windows
+ # versions:
+ # - all
+ # - 2012R2
+ #- name: SmartOS
+ # versions:
+ # - all
+ # - any
+ #- name: opensuse
+ # versions:
+ # - all
+ # - 12.1
+ # - 12.2
+ # - 12.3
+ # - 13.1
+ # - 13.2
+ #- name: SLES
+ # versions:
+ # - all
+ # - 10SP3
+ # - 10SP4
+ # - 11
+ # - 11SP1
+ # - 11SP2
+ # - 11SP3
+ # - 11SP4
+ # - 12
+ # - 12SP1
+ #- name: GenericUNIX
+ # versions:
+ # - all
+ # - any
+ #- name: Solaris
+ # versions:
+ # - all
+ # - 10
+ # - 11.0
+ # - 11.1
+ # - 11.2
+ # - 11.3
+ #- name: eos
+ # versions:
+ # - all
+ # - Any
+
+ galaxy_tags: []
+ # List tags for your role here, one per line. A tag is
+ # a keyword that describes and categorizes the role.
+ # Users find roles by searching for tags. Be sure to
+ # remove the '[]' above if you add tags to this list.
+ #
+ # NOTE: A tag is limited to a single word comprised of
+ # alphanumeric characters. Maximum 20 tags per role.
+
+dependencies: []
+ # List your role dependencies here, one per line.
+ # Be sure to remove the '[]' above if you add dependencies
+ # to this list.
\ No newline at end of file
diff --git a/roles/mariadb-ab/tasks/main.yml b/roles/mariadb-ab/tasks/main.yml
new file mode 100644
index 0000000..fee4d01
--- /dev/null
+++ b/roles/mariadb-ab/tasks/main.yml
@@ -0,0 +1,16 @@
+---
+- name: Installation des paquets python-mysqldb mariadb-server
+ apt:
+ name:
+ - python-mysqldb
+ - mariadb-server
+ state: present
+
+- name: Create mysql database
+ mysql_db: name={{ maria_dbname }} state=present
+
+- name: Copie du fichier my.cnf pour autorises toutes les adresses sur le port 3306
+ copy : src=my.cnf dest=/etc/mysql/
+
+- name: Redemarrage du service mariadb
+ shell: service mariadb restart
diff --git a/roles/mariadb-ab/tests/inventory b/roles/mariadb-ab/tests/inventory
new file mode 100644
index 0000000..d18580b
--- /dev/null
+++ b/roles/mariadb-ab/tests/inventory
@@ -0,0 +1 @@
+localhost
\ No newline at end of file
diff --git a/roles/mariadb-ab/tests/test.yml b/roles/mariadb-ab/tests/test.yml
new file mode 100644
index 0000000..ec4a223
--- /dev/null
+++ b/roles/mariadb-ab/tests/test.yml
@@ -0,0 +1,5 @@
+---
+- hosts: localhost
+ remote_user: root
+ roles:
+ - mariadb
\ No newline at end of file
diff --git a/roles/mariadb-ab/vars/main.yml b/roles/mariadb-ab/vars/main.yml
new file mode 100644
index 0000000..618771d
--- /dev/null
+++ b/roles/mariadb-ab/vars/main.yml
@@ -0,0 +1,2 @@
+---
+# vars file for mariadb
diff --git a/roles/mariadb/README.md b/roles/mariadb/README.md
new file mode 100644
index 0000000..225dd44
--- /dev/null
+++ b/roles/mariadb/README.md
@@ -0,0 +1,38 @@
+Role Name
+=========
+
+A brief description of the role goes here.
+
+Requirements
+------------
+
+Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
+
+Role Variables
+--------------
+
+A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.
+
+Dependencies
+------------
+
+A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
+
+Example Playbook
+----------------
+
+Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
+
+ - hosts: servers
+ roles:
+ - { role: username.rolename, x: 42 }
+
+License
+-------
+
+BSD
+
+Author Information
+------------------
+
+An optional section for the role authors to include contact information, or a website (HTML is not allowed).
diff --git a/roles/mariadb/_travis.yml b/roles/mariadb/_travis.yml
new file mode 100644
index 0000000..36bbf62
--- /dev/null
+++ b/roles/mariadb/_travis.yml
@@ -0,0 +1,29 @@
+---
+language: python
+python: "2.7"
+
+# Use the new container infrastructure
+sudo: false
+
+# Install ansible
+addons:
+ apt:
+ packages:
+ - python-pip
+
+install:
+ # Install ansible
+ - pip install ansible
+
+ # Check ansible version
+ - ansible --version
+
+ # Create ansible.cfg with correct roles_path
+ - printf '[defaults]\nroles_path=../' >ansible.cfg
+
+script:
+ # Basic role syntax check
+ - ansible-playbook tests/test.yml -i tests/inventory --syntax-check
+
+notifications:
+ webhooks: https://galaxy.ansible.com/api/v1/notifications/
\ No newline at end of file
diff --git a/roles/mariadb/defaults/main.yml b/roles/mariadb/defaults/main.yml
new file mode 100644
index 0000000..bf0e537
--- /dev/null
+++ b/roles/mariadb/defaults/main.yml
@@ -0,0 +1,2 @@
+---
+# defaults file for mariadb
diff --git a/roles/mariadb/handlers/main.yml b/roles/mariadb/handlers/main.yml
new file mode 100644
index 0000000..49ba9f4
--- /dev/null
+++ b/roles/mariadb/handlers/main.yml
@@ -0,0 +1,2 @@
+---
+# handlers file for mariadb
diff --git a/roles/mariadb/meta/main.yml b/roles/mariadb/meta/main.yml
new file mode 100644
index 0000000..6f81d2b
--- /dev/null
+++ b/roles/mariadb/meta/main.yml
@@ -0,0 +1,232 @@
+galaxy_info:
+ author: your name
+ description: your description
+ company: your company (optional)
+
+ # If the issue tracker for your role is not on github, uncomment the
+ # next line and provide a value
+ # issue_tracker_url: http://example.com/issue/tracker
+
+ # Some suggested licenses:
+ # - BSD (default)
+ # - MIT
+ # - GPLv2
+ # - GPLv3
+ # - Apache
+ # - CC-BY
+ license: license (GPLv2, CC-BY, etc)
+
+ min_ansible_version: 1.2
+
+ # Optionally specify the branch Galaxy will use when accessing the GitHub
+ # repo for this role. During role install, if no tags are available,
+ # Galaxy will use this branch. During import Galaxy will access files on
+ # this branch. If travis integration is cofigured, only notification for this
+ # branch will be accepted. Otherwise, in all cases, the repo's default branch
+ # (usually master) will be used.
+ #github_branch:
+
+ #
+ # Below are all platforms currently available. Just uncomment
+ # the ones that apply to your role. If you don't see your
+ # platform on this list, let us know and we'll get it added!
+ #
+ #platforms:
+ #- name: OpenBSD
+ # versions:
+ # - all
+ # - 5.6
+ # - 5.7
+ # - 5.8
+ # - 5.9
+ # - 6.0
+ # - 6.1
+ # - 6.2
+ #- name: Fedora
+ # versions:
+ # - all
+ # - 16
+ # - 17
+ # - 18
+ # - 19
+ # - 20
+ # - 21
+ # - 22
+ # - 23
+ # - 24
+ # - 25
+ # - 26
+ #- name: DellOS
+ # versions:
+ # - all
+ # - 10
+ # - 6
+ # - 9
+ #- name: MacOSX
+ # versions:
+ # - all
+ # - 10.10
+ # - 10.11
+ # - 10.12
+ # - 10.7
+ # - 10.8
+ # - 10.9
+ #- name: Synology
+ # versions:
+ # - all
+ # - any
+ #- name: Junos
+ # versions:
+ # - all
+ # - any
+ #- name: GenericBSD
+ # versions:
+ # - all
+ # - any
+ #- name: Void Linux
+ # versions:
+ # - all
+ # - any
+ #- name: GenericLinux
+ # versions:
+ # - all
+ # - any
+ #- name: NXOS
+ # versions:
+ # - all
+ # - any
+ #- name: macOS
+ # versions:
+ # - all
+ # - Sierra
+ #- name: IOS
+ # versions:
+ # - all
+ # - any
+ #- name: Amazon
+ # versions:
+ # - all
+ # - 2013.03
+ # - 2013.09
+ # - 2016.03
+ # - 2016.09
+ #- name: ArchLinux
+ # versions:
+ # - all
+ # - any
+ #- name: FreeBSD
+ # versions:
+ # - all
+ # - 10.0
+ # - 10.1
+ # - 10.2
+ # - 10.3
+ # - 11.0
+ # - 11.1
+ # - 8.0
+ # - 8.1
+ # - 8.2
+ # - 8.3
+ # - 8.4
+ # - 9.0
+ # - 9.1
+ # - 9.1
+ # - 9.2
+ # - 9.3
+ #- name: Ubuntu
+ # versions:
+ # - all
+ # - artful
+ # - lucid
+ # - maverick
+ # - natty
+ # - oneiric
+ # - precise
+ # - quantal
+ # - raring
+ # - saucy
+ # - trusty
+ # - utopic
+ # - vivid
+ # - wily
+ # - xenial
+ # - yakkety
+ # - zesty
+ #- name: Debian
+ # versions:
+ # - all
+ # - etch
+ # - jessie
+ # - lenny
+ # - sid
+ # - squeeze
+ # - stretch
+ # - wheezy
+ #- name: Alpine
+ # versions:
+ # - all
+ # - any
+ #- name: EL
+ # versions:
+ # - all
+ # - 5
+ # - 6
+ # - 7
+ #- name: Windows
+ # versions:
+ # - all
+ # - 2012R2
+ #- name: SmartOS
+ # versions:
+ # - all
+ # - any
+ #- name: opensuse
+ # versions:
+ # - all
+ # - 12.1
+ # - 12.2
+ # - 12.3
+ # - 13.1
+ # - 13.2
+ #- name: SLES
+ # versions:
+ # - all
+ # - 10SP3
+ # - 10SP4
+ # - 11
+ # - 11SP1
+ # - 11SP2
+ # - 11SP3
+ # - 11SP4
+ # - 12
+ # - 12SP1
+ #- name: GenericUNIX
+ # versions:
+ # - all
+ # - any
+ #- name: Solaris
+ # versions:
+ # - all
+ # - 10
+ # - 11.0
+ # - 11.1
+ # - 11.2
+ # - 11.3
+ #- name: eos
+ # versions:
+ # - all
+ # - Any
+
+ galaxy_tags: []
+ # List tags for your role here, one per line. A tag is
+ # a keyword that describes and categorizes the role.
+ # Users find roles by searching for tags. Be sure to
+ # remove the '[]' above if you add tags to this list.
+ #
+ # NOTE: A tag is limited to a single word comprised of
+ # alphanumeric characters. Maximum 20 tags per role.
+
+dependencies: []
+ # List your role dependencies here, one per line.
+ # Be sure to remove the '[]' above if you add dependencies
+ # to this list.
\ No newline at end of file
diff --git a/roles/mariadb/tasks/main.yml b/roles/mariadb/tasks/main.yml
new file mode 100644
index 0000000..b857b5c
--- /dev/null
+++ b/roles/mariadb/tasks/main.yml
@@ -0,0 +1,15 @@
+---
+# tasks file for mariadb
+- name: Installation de python-mysqldb
+ apt: name=python-mysqldb state=present
+
+- name: Installation de mariadb-server
+ apt: name=mariadb-server state=present
+
+- name: Create mysql database
+ mysql_db: name={{ maria_dbname }} state=present
+
+- name: Commenter la ligne
+ replace: dest=/etc/mysql/mariadb.conf.d/50-server.cnf
+ regexp='bind-address = 127.0.0.1'
+ replace='#bind-address = 127.0.0.1'
\ No newline at end of file
diff --git a/roles/mariadb/tests/inventory b/roles/mariadb/tests/inventory
new file mode 100644
index 0000000..d18580b
--- /dev/null
+++ b/roles/mariadb/tests/inventory
@@ -0,0 +1 @@
+localhost
\ No newline at end of file
diff --git a/roles/mariadb/tests/test.yml b/roles/mariadb/tests/test.yml
new file mode 100644
index 0000000..ec4a223
--- /dev/null
+++ b/roles/mariadb/tests/test.yml
@@ -0,0 +1,5 @@
+---
+- hosts: localhost
+ remote_user: root
+ roles:
+ - mariadb
\ No newline at end of file
diff --git a/roles/mariadb/vars/main.yml b/roles/mariadb/vars/main.yml
new file mode 100644
index 0000000..618771d
--- /dev/null
+++ b/roles/mariadb/vars/main.yml
@@ -0,0 +1,2 @@
+---
+# vars file for mariadb
diff --git a/roles/mess/files/nslcd.conf b/roles/mess/files/nslcd.conf
new file mode 100644
index 0000000..29ea826
--- /dev/null
+++ b/roles/mess/files/nslcd.conf
@@ -0,0 +1,31 @@
+# /etc/nslcd.conf
+# nslcd configuration file. See nslcd.conf(5)
+# for details.
+
+# The user and group nslcd should run as.
+uid nslcd
+gid nslcd
+
+# The location at which the LDAP server(s) should be reachable.
+uri ldap://172.16.0.6:389
+
+# The search base that will be used for all queries.
+base cn=Users,dc=gsb,dc=lan
+
+# The LDAP protocol version to use.
+#ldap_version 3
+
+# The DN to bind with for normal lookups.
+binddn cn=ncsld-connect,cn=Users,dc=gsb,dc=lan
+bindpw secret
+
+# The DN used for password modifications by root.
+#rootpwmoddn cn=admin,dc=example,dc=com
+
+# SSL options
+#ssl off
+#tls_reqcert never
+
+# The search scope.
+#scope sub
+
diff --git a/roles/mess/files/pam_ldap.conf b/roles/mess/files/pam_ldap.conf
new file mode 100644
index 0000000..f23a43a
--- /dev/null
+++ b/roles/mess/files/pam_ldap.conf
@@ -0,0 +1,6 @@
+base dc=gsb,dc=lan
+binddn cn=nslcd-connect,cn=Users,dc=gsb,dc=lan
+bindpw secret
+bind_policy soft
+uri ldap://172.16.0.6:389/
+ssl no
diff --git a/roles/mess/files/slapd.conf b/roles/mess/files/slapd.conf
new file mode 100644
index 0000000..4aed8b9
--- /dev/null
+++ b/roles/mess/files/slapd.conf
@@ -0,0 +1,144 @@
+# This is the main slapd configuration file. See slapd.conf(5) for more
+# info on the configuration options.
+
+#######################################################################
+# Global Directives:
+
+# Features to permit
+#allow bind_v2
+
+# Schema and objectClass definitions
+include /etc/ldap/schema/core.schema
+include /etc/ldap/schema/cosine.schema
+include /etc/ldap/schema/nis.schema
+include /etc/ldap/schema/inetorgperson.schema
+include /etc/ldap/schema/mailserver.schema
+include /etc/ldap/schema/sudo.schema
+include /etc/ldap/schema/samba.schema
+
+# Where the pid file is put. The init.d script
+# will not stop the server if you change this.
+pidfile /var/run/slapd/slapd.pid
+
+# List of arguments that were passed to the server
+argsfile /var/run/slapd/slapd.args
+
+password-hash {SSHA}
+
+# Read slapd.conf(5) for possible values
+loglevel 256
+
+# Where the dynamically loaded modules are stored
+modulepath /usr/lib/ldap
+moduleload back_ldap
+moduleload rwm
+
+# The maximum number of entries that is returned for a search operation
+sizelimit 500
+
+# The tool-threads parameter sets the actual amount of cpu's that is used
+# for indexing.
+tool-threads 1
+
+#######################################################################
+# Specific Backend Directives for hdb:
+# Backend specific directives apply to this backend until another
+# 'backend' directive occurs
+backend ldap
+
+
+#######################################################################
+# Specific Backend Directives for 'other':
+# Backend specific directives apply to this backend until another
+# 'backend' directive occurs
+#backend <other>
+
+#######################################################################
+# Specific Directives for database #1, of type hdb:
+# Database specific directives apply to this databasse until another
+# 'database' directive occurs
+database ldap
+
+# The base of your directory in database #1
+suffix "dc=gsb,dc=lan"
+uri "ldap://172.16.0.6:389"
+#directory "/var/lib/ldap"
+
+# The dbconfig settings are used to generate a DB_CONFIG file the first
+# time slapd starts. They do NOT override existing an existing DB_CONFIG
+# file. You should therefore change these settings in DB_CONFIG directly
+# or remove DB_CONFIG and restart slapd for changes to take effect.
+
+# For the Debian package we use 2MB as default but be sure to update this
+# value if you have plenty of RAM
+#dbconfig set_cachesize 0 2097152 0
+
+# Sven Hartge reported that he had to set this value incredibly high
+# to get slapd running at all. See http://bugs.debian.org/303057 for more
+# information.
+
+# Number of objects that can be locked at the same time.
+#dbconfig set_lk_max_objects 1500
+# Number of locks (both requested and granted)
+#dbconfig set_lk_max_locks 1500
+# Number of lockers
+#dbconfig set_lk_max_lockers 1500
+
+# Indexing options for database #1
+#index objectClass eq
+#index uid eq,sub
+#index entryCSN,entryUUID eq
+
+# Save the time that the entry gets modified, for database #1
+lastmod on
+
+# Checkpoint the BerkeleyDB database periodically in case of system
+# failure and to speed slapd shutdown.
+#checkpoint 512 30
+
+# Where to store the replica logs for database #1
+# replogfile /var/lib/ldap/replog
+
+# The userPassword by default can be changed
+# by the entry owning it if they are authenticated.
+# Others should not be able to see it, except the
+# admin entry below
+# These access lines apply to database #1 only
+access to attrs=userPassword
+ by dn="cn=admin,dc=yunohost,dc=org" write
+ by anonymous auth
+ by self write
+ by * none
+
+access to attrs=cn,gecos,givenName,mail,maildrop,displayName,sn
+ by dn="cn=admin,dc=yunohost,dc=org" write
+ by self write
+ by * read
+
+
+# Ensure read access to the base for things like
+# supportedSASLMechanisms. Without this you may
+# have problems with SASL not knowing what
+# mechanisms are available and the like.
+# Note that this is covered by the 'access to *'
+# ACL below too but if you change that as people
+# are wont to do you'll still need this if you
+# want SASL (and possible other things) to work
+# happily.
+access to dn.base="" by * read
+
+# The admin dn has full write access, everyone else
+# can read everything.
+access to *
+ by dn="cn=admin,dc=yunohost,dc=org" write
+ by group/groupOfNames/Member="cn=admin,ou=groups,dc=yunohost,dc=org" write
+ by * read
+
+#######################################################################
+# Specific Directives for database #2, of type 'other' (can be hdb too):
+# Database specific directives apply to this databasse until another
+# 'database' directive occurs
+#database <other>
+
+# The base of your directory for database #2
+#suffix "dc=debian,dc=org"
diff --git a/roles/mess/handlers/main.yml b/roles/mess/handlers/main.yml
new file mode 100644
index 0000000..6ad92ff
--- /dev/null
+++ b/roles/mess/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart slapd
+ service: name=slapd state=restarted
diff --git a/roles/mess/tasks/main.yml b/roles/mess/tasks/main.yml
new file mode 100644
index 0000000..82a7113
--- /dev/null
+++ b/roles/mess/tasks/main.yml
@@ -0,0 +1,15 @@
+---
+#- name: Installation openLDAP
+# apt: name=slapd state=present update_cache=yes
+
+#- name: Copie du slapd.conf
+# copy: src=slapd.conf dest=/etc/openldap
+
+- name: Copie du nslcd.conf
+ copy: src=nslcd.conf dest=/etc/
+
+- name: Copie du pam_ldap.conf
+ copy: src=pam_ldap.conf dest=/etc/
+
+- name: Recup du depot git
+ git: repo=https://github.com/YunoHost/install_script dest=/tmp/install_script
diff --git a/roles/mysql/defaults/main.yml b/roles/mysql/defaults/main.yml
new file mode 100644
index 0000000..c6d435b
--- /dev/null
+++ b/roles/mysql/defaults/main.yml
@@ -0,0 +1,4 @@
+---
+wp_mysql_db: wordpress
+wp_mysql_user: wp
+wp_mysql_password: wp
diff --git a/roles/mysql/files/.my.cnf b/roles/mysql/files/.my.cnf
new file mode 100644
index 0000000..34d0e25
--- /dev/null
+++ b/roles/mysql/files/.my.cnf
@@ -0,0 +1,3 @@
+[client]
+user=root
+password=root
diff --git a/roles/mysql/handlers/main.yml b/roles/mysql/handlers/main.yml
new file mode 100644
index 0000000..caa5308
--- /dev/null
+++ b/roles/mysql/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart mysql-server
+ service: name=mysql-server state=restarted
diff --git a/roles/mysql/tasks/main.yml b/roles/mysql/tasks/main.yml
new file mode 100644
index 0000000..eb11703
--- /dev/null
+++ b/roles/mysql/tasks/main.yml
@@ -0,0 +1,13 @@
+---
+# - name: Create mysql database
+# mysql_db: name={{ wp_mysql_db }} state=present
+
+# - name: Create mysql user
+# mysql_user:
+# name={{ wp_mysql_user }}
+# password={{ wp_mysql_password }}
+# priv=*.*:ALL
+# host=localhost
+
+ - name: copy .my.cnf file with root password credentials
+ copy: src=.my.cnf dest=/root/.my.cnf owner=root mode=0600
diff --git a/roles/php-fpm/handlers/main.yml b/roles/php-fpm/handlers/main.yml
new file mode 100644
index 0000000..b45a971
--- /dev/null
+++ b/roles/php-fpm/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart php7.0-fpm
+ service: name=php7.0-fpm state=restarted
diff --git a/roles/php-fpm/tasks/main.yml b/roles/php-fpm/tasks/main.yml
new file mode 100644
index 0000000..eb78510
--- /dev/null
+++ b/roles/php-fpm/tasks/main.yml
@@ -0,0 +1,9 @@
+---
+ - name: Install php-fpm and deps
+ apt: name={{ item }} state=present
+ with_items:
+ - php
+ - php-fpm
+ - php-mysql
+ notify:
+ - restart php7.0-fpm
diff --git a/roles/php-fpm/templates/main.yml b/roles/php-fpm/templates/main.yml
new file mode 100644
index 0000000..23080b5
--- /dev/null
+++ b/roles/php-fpm/templates/main.yml
@@ -0,0 +1,15 @@
+[wordpress]
+listen = /var/run/php-fpm/wordpress.sock
+listen.owner = apache2
+listen.group = apache2
+listen.mode = 0660
+user = wordpress
+group = wordpress
+pm = dynamic
+pm.max_children = 10
+pm.start_servers = 1
+pm.min_spare_servers = 1
+pm.max_spare_servers = 3
+pm.max_requests = 500
+chdir = /srv/wordpress/
+php_admin_value[open_basedir] = /srv/wordpress/:/tmp
diff --git a/roles/post/files/interface.user-yb b/roles/post/files/interface.user-yb
new file mode 100644
index 0000000..8e58317
--- /dev/null
+++ b/roles/post/files/interface.user-yb
@@ -0,0 +1,25 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.20
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.20
+ netmask 255.255.255.0
+
+# cote N-user
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 172.16.64.1
+ netmask 255.255.255.0
\ No newline at end of file
diff --git a/roles/post/files/interfaces.graylog-pont b/roles/post/files/interfaces.graylog-pont
new file mode 100644
index 0000000..db5ebd9
--- /dev/null
+++ b/roles/post/files/interfaces.graylog-pont
@@ -0,0 +1,12 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# Accès par pont
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.0.50
+ netmask 255.255.255.0
diff --git a/roles/post/files/interfaces.r-ext b/roles/post/files/interfaces.r-ext
new file mode 100644
index 0000000..669dfab
--- /dev/null
+++ b/roles/post/files/interfaces.r-ext
@@ -0,0 +1,41 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# carte reseau admin
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.13
+ netmask 255.255.255.0
+
+# Réseau DMZ
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.100.254
+ netmask 255.255.255.0
+
+# carte en bridge
+allow-hotplug enp0s9
+iface enp0s9 inet dhcp
+# address 192.168.0.50
+# netmask 255.255.255.0
+# gateway 192.168.0.1
+ up /root/nat.sh
+
+# Réseau VPN
+allow-hotplug enp0s10
+iface enp0s10 inet static
+ address 192.168.1.1
+ netmask 255.255.255.0
+ up route add -net 172.16.128.0/24 gw 192.168.1.2
+
+
+# Réseau liaison entre routeur
+allow-hotplug enp0s16
+iface enp0s16 inet static
+ address 192.168.200.253
+ netmask 255.255.255.0
+ up route add -net 172.16.0.0/24 gw 192.168.200.254
+ up route add -net 172.16.64.0/24 gw 192.168.200.254
diff --git a/roles/post/files/interfaces.r-int b/roles/post/files/interfaces.r-int
new file mode 100644
index 0000000..d67057b
--- /dev/null
+++ b/roles/post/files/interfaces.r-int
@@ -0,0 +1,44 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# Reseau N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.12
+ netmask 255.255.255.0
+
+
+# Reseau liaison avec r-ext
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.200.254
+ netmask 255.255.255.0
+ gateway 192.168.200.253
+ up route add default gw 192.168.200.253
+
+
+# Reseau wifi
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 172.16.65.254
+ netmask 255.255.255.0
+
+
+# Reseau user
+allow-hotplug enp0s10
+iface enp0s10 inet static
+ address 172.16.64.254
+ netmask 255.255.255.0
+
+
+# Reseau infra
+allow-hotplug enp0s16
+iface enp0s16 inet static
+ address 172.16.0.254
+ netmask 255.255.255.0
+ up /root/routagenat
+
diff --git a/roles/post/files/interfaces.r-vp1 b/roles/post/files/interfaces.r-vp1
new file mode 100644
index 0000000..ac0a8fa
--- /dev/null
+++ b/roles/post/files/interfaces.r-vp1
@@ -0,0 +1,29 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+#auto lo
+#iface lo inet loopback
+
+#cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.112
+ netmask 255.255.255.0
+
+# reseau entre vpn
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.0.51
+ netmask 255.255.255.0
+
+# reseau interne n-linkv
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.1.2
+ netmask 255.255.255.0
+ up route add -net 172.16.128.0/24 gw 192.168.1.2
+# up route add -net 172.16.128.0/24 gw 192.168.0.52
+# up route add default gw 192.168.1.1
+# post-up /bin/bash /root/iptables-vpn
+ post-up /etc/init.d/ipsec restart
\ No newline at end of file
diff --git a/roles/post/files/interfaces.r-vp1-cs b/roles/post/files/interfaces.r-vp1-cs
new file mode 100644
index 0000000..4a3abe3
--- /dev/null
+++ b/roles/post/files/interfaces.r-vp1-cs
@@ -0,0 +1,26 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+#auto lo
+#iface lo inet loopback
+
+#cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+
+# reseau entre vpn
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.0.51
+ netmask 255.255.255.0
+
+# reseau interne n-linkv
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.1.2
+ netmask 255.255.255.0
+ up route add -net 172.16.128.0/24 gw 192.168.1.2
+ up route add default gw 192.168.1.1
+# post-up /bin/bash /root/iptables-vpn
+ post-up /etc/init.d/ipsec restart
\ No newline at end of file
diff --git a/roles/post/files/interfaces.r-vp2 b/roles/post/files/interfaces.r-vp2
new file mode 100644
index 0000000..6398c63
--- /dev/null
+++ b/roles/post/files/interfaces.r-vp2
@@ -0,0 +1,28 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+#auto lo
+#iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.102
+ netmask 255.255.255.0
+
+# cote Agence
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.128.254
+ netmask 255.255.255.0
+
+# cote VPN
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.0.52
+ netmask 255.255.255.0
+# up route add -net 192.168.1.0/24 gw 172.16.128.254
+ up route add -net 192.168.1.0/24 gw 192.168.0.52
+# post-up /bin/bash /root/iptables-vpn
+ post-up /etc/init.d/ipsec restart
\ No newline at end of file
diff --git a/roles/post/files/interfaces.r-vp2-cs b/roles/post/files/interfaces.r-vp2-cs
new file mode 100644
index 0000000..d5f8539
--- /dev/null
+++ b/roles/post/files/interfaces.r-vp2-cs
@@ -0,0 +1,25 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+#auto lo
+#iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+
+# cote Agence
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.128.254
+ netmask 255.255.255.0
+
+# cote VPN
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.0.52
+ netmask 255.255.255.0
+ up route add -net 192.168.1.0/24 gw 172.16.128.254
+# post-up /bin/bash /root/iptables-vpn
+ post-up /etc/init.d/ipsec restart
\ No newline at end of file
diff --git a/roles/post/files/interfaces.s-adm b/roles/post/files/interfaces.s-adm
new file mode 100644
index 0000000..90ab935
--- /dev/null
+++ b/roles/post/files/interfaces.s-adm
@@ -0,0 +1,20 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote public
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+ post-up iptables -t nat -A POSTROUTING -o enp0s3 -j MASQUERADE
+ post-up echo "1" > /proc/sys/net/ipv4/ip_forward
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.99.99
+ netmask 255.255.255.0
+
+
diff --git a/roles/post/files/interfaces.s-agence b/roles/post/files/interfaces.s-agence
new file mode 100644
index 0000000..98a4301
--- /dev/null
+++ b/roles/post/files/interfaces.s-agence
@@ -0,0 +1,11 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote n-ag
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+
diff --git a/roles/post/files/interfaces.s-appli b/roles/post/files/interfaces.s-appli
new file mode 100644
index 0000000..c52d5b0
--- /dev/null
+++ b/roles/post/files/interfaces.s-appli
@@ -0,0 +1,27 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.3
+ netmask 255.255.255.0
+ gateway 192.168.99.99
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.3
+ netmask 255.255.255.0
+ post-up route add -net 172.16.64.0/24 gw 172.16.0.254
+ post-up route add -net 172.16.65.0/24 gw 172.16.0.254
+
+#cote N-san
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.20.103
+ netmask 255.255.255.0
diff --git a/roles/post/files/interfaces.s-backup b/roles/post/files/interfaces.s-backup
new file mode 100644
index 0000000..120ad6b
--- /dev/null
+++ b/roles/post/files/interfaces.s-backup
@@ -0,0 +1,25 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.4
+ netmask 255.255.255.0
+ gateway 192.168.99.99
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.4
+ netmask 255.255.255.0
+
+# cote N-San
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.20.4
+ netmask 255.255.255.0
diff --git a/roles/post/files/interfaces.s-bdd b/roles/post/files/interfaces.s-bdd
new file mode 100644
index 0000000..a8cb4f6
--- /dev/null
+++ b/roles/post/files/interfaces.s-bdd
@@ -0,0 +1,21 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+ address 192.168.99.154
+ netmask 255.255.255.0
+
+
+# cote N-dmz-db
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.102.254
+ netmask 255.255.255.0
+
+
diff --git a/roles/post/files/interfaces.s-docker b/roles/post/files/interfaces.s-docker
new file mode 100644
index 0000000..150189a
--- /dev/null
+++ b/roles/post/files/interfaces.s-docker
@@ -0,0 +1,20 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.19
+ netmask 255.255.255.0
+ gateway 192.168.99.99
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.19
+ netmask 255.255.255.0
\ No newline at end of file
diff --git a/roles/post/files/interfaces.s-fog b/roles/post/files/interfaces.s-fog
new file mode 100644
index 0000000..63421bf
--- /dev/null
+++ b/roles/post/files/interfaces.s-fog
@@ -0,0 +1,25 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.16
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.16
+ netmask 255.255.255.0
+
+#cote N-user
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 172.16.64.16
+ netmask 255.255.255.0
diff --git a/roles/post/files/interfaces.s-graylog b/roles/post/files/interfaces.s-graylog
new file mode 100644
index 0000000..8ff1151
--- /dev/null
+++ b/roles/post/files/interfaces.s-graylog
@@ -0,0 +1,21 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.20
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.20
+ netmask 255.255.255.0
+ up route add -net 192.168.200.0/24 gw 172.16.0.254
+ up route add default gw 192.168.99.99
diff --git a/roles/post/files/interfaces.s-infra b/roles/post/files/interfaces.s-infra
new file mode 100644
index 0000000..8aea160
--- /dev/null
+++ b/roles/post/files/interfaces.s-infra
@@ -0,0 +1,24 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.1
+ netmask 255.255.255.0
+ gateway 192.168.99.99
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.1
+ netmask 255.255.255.0
+ up route add -net 172.16.64.0/24 gw 172.16.0.254
+ up route add -net 172.16.128.0/24 gw 172.16.0.254
+ up route add -net 192.168.0.0/16 gw 172.16.0.254
+
diff --git a/roles/post/files/interfaces.s-itil b/roles/post/files/interfaces.s-itil
new file mode 100644
index 0000000..e2b1200
--- /dev/null
+++ b/roles/post/files/interfaces.s-itil
@@ -0,0 +1,24 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.9
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.9
+ netmask 255.255.255.0
+# routage statique
+ post-up route add -net 172.16.64.0/24 gw 172.16.0.254
+
+allow-hotplug enp0s9
+iface enp0s9 inet dhcp
\ No newline at end of file
diff --git a/roles/post/files/interfaces.s-itil-cs b/roles/post/files/interfaces.s-itil-cs
new file mode 100644
index 0000000..e2b1200
--- /dev/null
+++ b/roles/post/files/interfaces.s-itil-cs
@@ -0,0 +1,24 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.9
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.9
+ netmask 255.255.255.0
+# routage statique
+ post-up route add -net 172.16.64.0/24 gw 172.16.0.254
+
+allow-hotplug enp0s9
+iface enp0s9 inet dhcp
\ No newline at end of file
diff --git a/roles/post/files/interfaces.s-lb b/roles/post/files/interfaces.s-lb
new file mode 100644
index 0000000..3e4b2fe
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb
@@ -0,0 +1,27 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.100
+ netmask 255.255.255.0
+
+# cote N-dmz
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.100.10
+ netmask 255.255.255.0
+ gateway 192.168.101.100
+ up route add -net 192.168.200.0/24 gw 192.168.100.254
+ up route add -net 172.16.0.0/24 gw 192.168.100.254
+
+# cote N-lb-f
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.101.100
+ netmask 255.255.255.0
diff --git a/roles/post/files/interfaces.s-lb-bd b/roles/post/files/interfaces.s-lb-bd
new file mode 100644
index 0000000..a8cb4f6
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb-bd
@@ -0,0 +1,21 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+ address 192.168.99.154
+ netmask 255.255.255.0
+
+
+# cote N-dmz-db
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.102.254
+ netmask 255.255.255.0
+
+
diff --git a/roles/post/files/interfaces.s-lb-web1 b/roles/post/files/interfaces.s-lb-web1
new file mode 100644
index 0000000..fc76724
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb-web1
@@ -0,0 +1,27 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# carte n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.101
+ netmask 255.255.255.0
+
+# Réseau n-dmz-lb
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.1
+ netmask 255.255.255.0
+
+# réseau n-dmz-db
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.1
+ netmask 255.255.255.0
+
+
+
+
diff --git a/roles/post/files/interfaces.s-lb-web2 b/roles/post/files/interfaces.s-lb-web2
new file mode 100644
index 0000000..53defed
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb-web2
@@ -0,0 +1,25 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.102
+ netmask 255.255.255.0
+
+# n-dmz-lb
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.2
+ netmask 255.255.255.0
+
+# n-dmz-db
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.2
+ netmask 255.255.255.0
+
+
diff --git a/roles/post/files/interfaces.s-lb-web3 b/roles/post/files/interfaces.s-lb-web3
new file mode 100644
index 0000000..656d503
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb-web3
@@ -0,0 +1,25 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.103
+ netmask 255.255.255.0
+
+# n-dmz-lb
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.3
+ netmask 255.255.255.0
+
+# n-dmz-db
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.3
+ netmask 255.255.255.0
+
+
diff --git a/roles/post/files/interfaces.s-lb-wordpress b/roles/post/files/interfaces.s-lb-wordpress
new file mode 100644
index 0000000..6c41c2a
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb-wordpress
@@ -0,0 +1,39 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# carte reseau admin
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+ address 192.168.99.11
+ netmask 255.255.255.0
+
+# Réseau N-lb-f
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.1
+ netmask 255.255.255.0
+
+# réseau N-lb-b
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.1
+ netmask 255.255.255.0
+# up /root/nat.sh
+
+# Réseau VPN
+#allow-hotplug enp0s10
+#iface enp0s10 inet static
+# address 192.168.1.1
+# netmask 255.255.255.0
+
+
+
+# Réseau liaison entre routeur
+#allow-hotplug enp0s16
+#iface enp0s16 inet static
+# address 192.168.200.253
+# netmask 255.255.255.0
+
diff --git a/roles/post/files/interfaces.s-lb-wordpress2 b/roles/post/files/interfaces.s-lb-wordpress2
new file mode 100644
index 0000000..8667576
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb-wordpress2
@@ -0,0 +1,39 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# carte reseau admin
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+ address 192.168.99.12
+ netmask 255.255.255.0
+
+# Réseau N-lb-f
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.2
+ netmask 255.255.255.0
+
+# réseau N-lb-b
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.2
+ netmask 255.255.255.0
+# up /root/nat.sh
+
+# Réseau VPN
+#allow-hotplug enp0s10
+#iface enp0s10 inet static
+# address 192.168.1.1
+# netmask 255.255.255.0
+
+
+
+# Réseau liaison entre routeur
+#allow-hotplug enp0s16
+#iface enp0s16 inet static
+# address 192.168.200.253
+# netmask 255.255.255.0
+
diff --git a/roles/post/files/interfaces.s-lb-wordpress3 b/roles/post/files/interfaces.s-lb-wordpress3
new file mode 100644
index 0000000..1947d94
--- /dev/null
+++ b/roles/post/files/interfaces.s-lb-wordpress3
@@ -0,0 +1,39 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# carte reseau admin
+allow-hotplug enp0s3
+iface enp0s3 inet dhcp
+ address 192.168.99.13
+ netmask 255.255.255.0
+
+# Réseau N-lb-f
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.3
+ netmask 255.255.255.0
+
+# réseau N-lb-b
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.3
+ netmask 255.255.255.0
+# up /root/nat.sh
+
+# Réseau VPN
+#allow-hotplug enp0s10
+#iface enp0s10 inet static
+# address 192.168.1.1
+# netmask 255.255.255.0
+
+
+
+# Réseau liaison entre routeur
+#allow-hotplug enp0s16
+#iface enp0s16 inet static
+# address 192.168.200.253
+# netmask 255.255.255.0
+
diff --git a/roles/post/files/interfaces.s-mess b/roles/post/files/interfaces.s-mess
new file mode 100644
index 0000000..9eff04c
--- /dev/null
+++ b/roles/post/files/interfaces.s-mess
@@ -0,0 +1,24 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.7
+ netmask 255.255.255.0
+ gateway 192.168.99.99
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.7
+ netmask 255.255.255.0
+ post-up route add -net 172.16.64.0/24 gw 172.16.0.254
+ post-up route add -net 172.16.65.0/24 gw 172.16.0.254
+
+
diff --git a/roles/post/files/interfaces.s-mon b/roles/post/files/interfaces.s-mon
new file mode 100644
index 0000000..d3af2fc
--- /dev/null
+++ b/roles/post/files/interfaces.s-mon
@@ -0,0 +1,21 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.8
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.8
+ netmask 255.255.255.0
+ up route add -net 192.168.200.0/24 gw 172.16.0.254
+ up route add default gw 192.168.99.99
diff --git a/roles/post/files/interfaces.s-mon-gm b/roles/post/files/interfaces.s-mon-gm
new file mode 100644
index 0000000..a0a172b
--- /dev/null
+++ b/roles/post/files/interfaces.s-mon-gm
@@ -0,0 +1,22 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.8
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.8
+ netmask 255.255.255.0
+ up route add -net 192.168.200.0/24 gw 172.16.0.254
+ up route add -net 192.168.100.0/24 gw 172.16.0.254
+ up route add default gw 192.168.99.99
diff --git a/roles/post/files/interfaces.s-mon-kb b/roles/post/files/interfaces.s-mon-kb
new file mode 100644
index 0000000..a0a172b
--- /dev/null
+++ b/roles/post/files/interfaces.s-mon-kb
@@ -0,0 +1,22 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.8
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.8
+ netmask 255.255.255.0
+ up route add -net 192.168.200.0/24 gw 172.16.0.254
+ up route add -net 192.168.100.0/24 gw 172.16.0.254
+ up route add default gw 192.168.99.99
diff --git a/roles/post/files/interfaces.s-mon-yb b/roles/post/files/interfaces.s-mon-yb
new file mode 100644
index 0000000..8e67e37
--- /dev/null
+++ b/roles/post/files/interfaces.s-mon-yb
@@ -0,0 +1,22 @@
+#This file describes the network interfaces available on your system
+#and how to activate them. For more information, see interfaces(5).
+
+#The loopback network interface
+auto lo
+iface lo inet loopback
+
+#cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.8
+ netmask 255.255.255.0
+
+
+#cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.8
+ netmask 255.255.255.0
+ up route add -net 192.168.200.0/24 gw 172.16.0.254
+ up route add -net 192.168.100.0/24 gw 172.16.0.254
+ up route add default gw 192.168.99.99
diff --git a/roles/post/files/interfaces.s-mon2 b/roles/post/files/interfaces.s-mon2
new file mode 100644
index 0000000..ef79346
--- /dev/null
+++ b/roles/post/files/interfaces.s-mon2
@@ -0,0 +1,21 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.8
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.8
+ netmask 255.255.255.0
+ gateway 172.16.0.254
+
diff --git a/roles/post/files/interfaces.s-mon3 b/roles/post/files/interfaces.s-mon3
new file mode 100644
index 0000000..4ab3b9b
--- /dev/null
+++ b/roles/post/files/interfaces.s-mon3
@@ -0,0 +1,24 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.8
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.8
+ netmask 255.255.255.0
+ up route add default gw 172.16.0.254
+ up route add default gw 192.168.99.99
+
+# bridge
+iface enp0s9 inet dhcp
\ No newline at end of file
diff --git a/roles/post/files/interfaces.s-nas b/roles/post/files/interfaces.s-nas
new file mode 100644
index 0000000..94c3eaf
--- /dev/null
+++ b/roles/post/files/interfaces.s-nas
@@ -0,0 +1,17 @@
+source /etc/network/interfaces.d/*
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.153
+ netmask 255.255.255.0
+
+# n-dmz-db
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.102.253
+ netmask 255.255.255.0
\ No newline at end of file
diff --git a/roles/post/files/interfaces.s-proxy b/roles/post/files/interfaces.s-proxy
new file mode 100644
index 0000000..850da12
--- /dev/null
+++ b/roles/post/files/interfaces.s-proxy
@@ -0,0 +1,22 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.2
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.2
+ netmask 255.255.255.0
+ gateway 172.16.0.254
+
+
diff --git a/roles/post/files/interfaces.s-san b/roles/post/files/interfaces.s-san
new file mode 100644
index 0000000..ff01320
--- /dev/null
+++ b/roles/post/files/interfaces.s-san
@@ -0,0 +1,25 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.15
+ netmask 255.255.255.0
+ gateway 192.168.99.99
+
+# cote S-appli
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.20.103
+ netmask 255.255.255.0
+
+# cote s-Backup
+#allow-hotplug enp0s9
+#iface enp0s9 inet static
+# address 192.168.20.104
+# netmask 255.255.255.0
diff --git a/roles/post/files/interfaces.s-sspec b/roles/post/files/interfaces.s-sspec
new file mode 100644
index 0000000..03d8686
--- /dev/null
+++ b/roles/post/files/interfaces.s-sspec
@@ -0,0 +1,22 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote N-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.10
+ netmask 255.255.255.0
+
+
+# cote N-infra
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 172.16.0.10
+ netmask 255.255.255.0
+ gateway 172.16.0.254
+
+
diff --git a/roles/post/files/interfaces.s-test b/roles/post/files/interfaces.s-test
new file mode 100644
index 0000000..d1005fd
--- /dev/null
+++ b/roles/post/files/interfaces.s-test
@@ -0,0 +1,21 @@
+#This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# cote n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.18
+ netmask 255.255.255.0
+ gateway 192.168.99.99
+
+
+# cote n-dmz
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.100.150
+ netmask 255.255.255.0
+ gateway 192.168.100.254
diff --git a/roles/post/files/interfaces.s-web b/roles/post/files/interfaces.s-web
new file mode 100644
index 0000000..9c82c9a
--- /dev/null
+++ b/roles/post/files/interfaces.s-web
@@ -0,0 +1,20 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+
+
+# cote N-dmz
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.100.11
+ netmask 255.255.255.0
+
+# cote N-adm
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.99.14
+ netmask 255.255.255.0
diff --git a/roles/post/files/interfaces.s-web1 b/roles/post/files/interfaces.s-web1
new file mode 100644
index 0000000..fc76724
--- /dev/null
+++ b/roles/post/files/interfaces.s-web1
@@ -0,0 +1,27 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# carte n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.101
+ netmask 255.255.255.0
+
+# Réseau n-dmz-lb
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.1
+ netmask 255.255.255.0
+
+# réseau n-dmz-db
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.1
+ netmask 255.255.255.0
+
+
+
+
diff --git a/roles/post/files/interfaces.s-web2 b/roles/post/files/interfaces.s-web2
new file mode 100644
index 0000000..53defed
--- /dev/null
+++ b/roles/post/files/interfaces.s-web2
@@ -0,0 +1,25 @@
+### 0.2 - putconf - jeudi 7 janvier 2016, 16:18:49 (UTC+0100)
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# n-adm
+allow-hotplug enp0s3
+iface enp0s3 inet static
+ address 192.168.99.102
+ netmask 255.255.255.0
+
+# n-dmz-lb
+allow-hotplug enp0s8
+iface enp0s8 inet static
+ address 192.168.101.2
+ netmask 255.255.255.0
+
+# n-dmz-db
+allow-hotplug enp0s9
+iface enp0s9 inet static
+ address 192.168.102.2
+ netmask 255.255.255.0
+
+
diff --git a/roles/post/files/resolv.conf b/roles/post/files/resolv.conf
new file mode 100644
index 0000000..ae3fdec
--- /dev/null
+++ b/roles/post/files/resolv.conf
@@ -0,0 +1,4 @@
+search gsb.lan
+domain gsb.lan
+nameserver 172.16.0.1
+
diff --git a/roles/post/files/resolv.conf.s-proxy b/roles/post/files/resolv.conf.s-proxy
new file mode 100644
index 0000000..ae3fdec
--- /dev/null
+++ b/roles/post/files/resolv.conf.s-proxy
@@ -0,0 +1,4 @@
+search gsb.lan
+domain gsb.lan
+nameserver 172.16.0.1
+
diff --git a/roles/post/tasks/main.yml b/roles/post/tasks/main.yml
new file mode 100644
index 0000000..d750d2d
--- /dev/null
+++ b/roles/post/tasks/main.yml
@@ -0,0 +1,24 @@
+---
+
+
+- name: Copie interfaces
+ copy: src=interfaces.{{ ansible_hostname }} dest=/etc/network/interfaces
+
+- name: Copie resolv.conf
+ copy: src=resolv.conf dest=/etc/
+ when: ansible_hostname != "s-adm"
+
+- name: Copie resolv.conf
+ copy: src=resolv.conf dest=/etc/
+ when: ansible_hostname != "s-proxy"
+
+- name: Copie resolv.conf pour s-proxy
+ copy: src=resolv.conf.s-proxy dest=/etc/resolv.conf
+ when: ansible_hostname == "s-proxy"
+
+#- name: Confirm
+# prompt: "<Entree> pour redemarrer ..."
+
+#- name: Reboot
+# shell: reboot
+
diff --git a/roles/postfix-nd/files/main.cf b/roles/postfix-nd/files/main.cf
new file mode 100644
index 0000000..22d044b
--- /dev/null
+++ b/roles/postfix-nd/files/main.cf
@@ -0,0 +1,49 @@
+# See /usr/share/postfix/main.cf.dist for a commented, more complete version
+
+
+# Debian specific: Specifying a file name will cause the first
+# line of that file to be used as the name. The Debian default
+# is /etc/mailname.
+#myorigin = /etc/mailname
+
+smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
+biff = no
+
+# appending .domain is the MUA's job.
+append_dot_mydomain = no
+
+# Uncomment the next line to generate "delayed mail" warnings
+#delay_warning_time = 4h
+
+readme_directory = no
+
+# TLS parameters
+smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
+smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
+smtpd_use_tls=yes
+smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
+smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
+
+# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
+# information on enabling SSL in the smtp client.
+
+mydomain = gsb.lan
+myhostname = s-mon.gsb.lan
+alias_maps = hash:/etc/aliases
+alias_database = hash:/etc/aliases
+mydestination = wheezy, localhost.localdomain, localhost
+relayhost = [smtp.gmail.com]:587
+mynetworks = 172.16.0.0/24
+mailbox_command = procmail -a "$EXTENSION"
+mailbox_size_limit = 0
+recipient_delimiter = +
+inet_interfaces = loopback-only
+default_transport = smtp
+relay_transport = smtp
+
+smtp_sasl_auth_enable = yes
+smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
+smtp_sasl_security_options = noanonymous
+smtp_tls_CAfile = /etc/postfix/cacert.pem
+smtp_use_tls = yes
+
diff --git a/roles/postfix-nd/files/sasl_passwd b/roles/postfix-nd/files/sasl_passwd
new file mode 100644
index 0000000..97c93d0
--- /dev/null
+++ b/roles/postfix-nd/files/sasl_passwd
@@ -0,0 +1 @@
+[smtp.gmail.com]:587 dahmouninabil21@gmail.com:POISSON21
\ No newline at end of file
diff --git a/roles/postfix-nd/files/thawte_Premium_Server_CA.pem b/roles/postfix-nd/files/thawte_Premium_Server_CA.pem
new file mode 100644
index 0000000..29cf7e1
--- /dev/null
+++ b/roles/postfix-nd/files/thawte_Premium_Server_CA.pem
@@ -0,0 +1,20 @@
+-----BEGIN CERTIFICATE-----
+MIIDNjCCAp+gAwIBAgIQNhIilsXjOKUgodJfTNcJVDANBgkqhkiG9w0BAQUFADCB
+zjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJ
+Q2FwZSBUb3duMR0wGwYDVQQKExRUaGF3dGUgQ29uc3VsdGluZyBjYzEoMCYGA1UE
+CxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEhMB8GA1UEAxMYVGhh
+d3RlIFByZW1pdW0gU2VydmVyIENBMSgwJgYJKoZIhvcNAQkBFhlwcmVtaXVtLXNl
+cnZlckB0aGF3dGUuY29tMB4XDTk2MDgwMTAwMDAwMFoXDTIxMDEwMTIzNTk1OVow
+gc4xCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT
+CUNhcGUgVG93bjEdMBsGA1UEChMUVGhhd3RlIENvbnN1bHRpbmcgY2MxKDAmBgNV
+BAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xITAfBgNVBAMTGFRo
+YXd0ZSBQcmVtaXVtIFNlcnZlciBDQTEoMCYGCSqGSIb3DQEJARYZcHJlbWl1bS1z
+ZXJ2ZXJAdGhhd3RlLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0jY2
+aovXwlue2oFBYo847kkEVdbQ7xwblRZH7xhINTpS9CtqBo87L+pW46+GjZ4X9560
+ZXUCTe/LCaIhUdib0GfQug2SBhRz1JPLlyoAnFxODLz6FVL88kRu2hFKbgifLy3j
++ao6hnO2RlNYyIkFvYMRuHM/qgeN9EJN50CdHDcCAwEAAaMTMBEwDwYDVR0TAQH/
+BAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQBlkKyID1bZ5jA01CbH0FDxkt5r1DmI
+CSLGpmODA/eZd9iy5Ri4XWPz1HP7bJyZePFLeH0ZJMMrAoT4vCLZiiLXoPxx7JGH
+IPG47LHlVYCsPVLIOQ7C8MAFT9aCdYy9X9LcdpoFEsmvcsPcJX6kTY4XpeCHf+Ga
+WuFg3GQjPEIuTQ==
+-----END CERTIFICATE-----
\ No newline at end of file
diff --git a/roles/postfix-nd/handlers/main.yml b/roles/postfix-nd/handlers/main.yml
new file mode 100644
index 0000000..6f511d5
--- /dev/null
+++ b/roles/postfix-nd/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart postfix
+ service: name=postfix state=restarted
diff --git a/roles/postfix-nd/tasks/main.yml b/roles/postfix-nd/tasks/main.yml
new file mode 100644
index 0000000..c79ca11
--- /dev/null
+++ b/roles/postfix-nd/tasks/main.yml
@@ -0,0 +1,36 @@
+---
+- name: Installation Postfix
+ apt: name=postfix state=present
+
+- name: Installation mailutils
+ apt: name=mailutils state=present
+
+- name: Installation libsasl2-2
+ apt: name=libsasl2-2 state=present
+
+- name: Installation ca-certificates
+ apt: name=ca-certificates state=present
+
+- name: Installation libsasl2-modules
+ apt: name=libsasl2-modules state=present
+
+- name: Copie main.cf
+ copy: remote_src=true src=main.cf dest=/etc/postfix/
+
+- name: Copie sasl_passwd
+ copy: remote_src=true src=sasl_passwd dest=/etc/postfix
+
+- name: attribution des droits sasl_passwd
+ shell: chmod 400 /etc/postfix/sasl_passwd
+
+- name: postmap
+ shell: postmap /etc/postfix/sasl_passwd
+
+- name: Copie thawte_Premium_Server_CA.pem
+ copy: remote_src=true src=thawte_Premium_Server_CA.pem dest=/etc/ssl/certs/
+
+- name: Certificats
+ shell: cat /etc/ssl/certs/thawte_Premium_Server_CA.pem |tee -a /etc/postfix/cacert.pem
+ notify:
+ - restart postfix
+
diff --git a/roles/postfix/files/main.cf b/roles/postfix/files/main.cf
new file mode 100644
index 0000000..8b2bf4f
--- /dev/null
+++ b/roles/postfix/files/main.cf
@@ -0,0 +1,50 @@
+# See /usr/share/postfix/main.cf.dist for a commented, more complete version
+
+
+# Debian specific: Specifying a file name will cause the first
+# line of that file to be used as the name. The Debian default
+# is /etc/mailname.
+#myorigin = /etc/mailname
+
+smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
+biff = no
+
+# appending .domain is the MUA's job.
+append_dot_mydomain = no
+
+# Uncomment the next line to generate "delayed mail" warnings
+#delay_warning_time = 4h
+
+readme_directory = no
+
+# TLS parameters
+#smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
+#smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
+#smtpd_use_tls=yes
+#smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
+#smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
+
+# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
+# information on enabling SSL in the smtp client.
+
+mydomain = gsb.lan
+myhostname = s-mon.gsb.lan
+alias_maps = hash:/etc/aliases
+alias_database = hash:/etc/aliases
+mydestination = $myhostname, s-mon, s-mon.gsb.lan
+relayhost = [smtp.gmail.com]:587
+mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 172.16.0.0/24
+#mailbox_command = procmail -a "$EXTENSION"
+mailbox_size_limit = 0
+recipient_delimiter = +
+inet_interfaces = all
+inet_protocols = ipv4
+default_transport = smtp
+relay_transport = smtp
+
+smtp_sasl_auth_enable = yes
+smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
+smtp_sasl_security_options =
+smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
+smtp_use_tls = yes
+
diff --git a/roles/postfix/files/sasl_passwd b/roles/postfix/files/sasl_passwd
new file mode 100644
index 0000000..db077bd
--- /dev/null
+++ b/roles/postfix/files/sasl_passwd
@@ -0,0 +1 @@
+[smtp.gmail.com]:587 supervisiongsb@gmail.com:sio2018cst
diff --git a/roles/postfix/files/thawte_Premium_Server_CA.pem b/roles/postfix/files/thawte_Premium_Server_CA.pem
new file mode 100644
index 0000000..29cf7e1
--- /dev/null
+++ b/roles/postfix/files/thawte_Premium_Server_CA.pem
@@ -0,0 +1,20 @@
+-----BEGIN CERTIFICATE-----
+MIIDNjCCAp+gAwIBAgIQNhIilsXjOKUgodJfTNcJVDANBgkqhkiG9w0BAQUFADCB
+zjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJ
+Q2FwZSBUb3duMR0wGwYDVQQKExRUaGF3dGUgQ29uc3VsdGluZyBjYzEoMCYGA1UE
+CxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEhMB8GA1UEAxMYVGhh
+d3RlIFByZW1pdW0gU2VydmVyIENBMSgwJgYJKoZIhvcNAQkBFhlwcmVtaXVtLXNl
+cnZlckB0aGF3dGUuY29tMB4XDTk2MDgwMTAwMDAwMFoXDTIxMDEwMTIzNTk1OVow
+gc4xCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT
+CUNhcGUgVG93bjEdMBsGA1UEChMUVGhhd3RlIENvbnN1bHRpbmcgY2MxKDAmBgNV
+BAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xITAfBgNVBAMTGFRo
+YXd0ZSBQcmVtaXVtIFNlcnZlciBDQTEoMCYGCSqGSIb3DQEJARYZcHJlbWl1bS1z
+ZXJ2ZXJAdGhhd3RlLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0jY2
+aovXwlue2oFBYo847kkEVdbQ7xwblRZH7xhINTpS9CtqBo87L+pW46+GjZ4X9560
+ZXUCTe/LCaIhUdib0GfQug2SBhRz1JPLlyoAnFxODLz6FVL88kRu2hFKbgifLy3j
++ao6hnO2RlNYyIkFvYMRuHM/qgeN9EJN50CdHDcCAwEAAaMTMBEwDwYDVR0TAQH/
+BAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQBlkKyID1bZ5jA01CbH0FDxkt5r1DmI
+CSLGpmODA/eZd9iy5Ri4XWPz1HP7bJyZePFLeH0ZJMMrAoT4vCLZiiLXoPxx7JGH
+IPG47LHlVYCsPVLIOQ7C8MAFT9aCdYy9X9LcdpoFEsmvcsPcJX6kTY4XpeCHf+Ga
+WuFg3GQjPEIuTQ==
+-----END CERTIFICATE-----
\ No newline at end of file
diff --git a/roles/postfix/handlers/main.yml b/roles/postfix/handlers/main.yml
new file mode 100644
index 0000000..6f511d5
--- /dev/null
+++ b/roles/postfix/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart postfix
+ service: name=postfix state=restarted
diff --git a/roles/postfix/tasks/main.yml b/roles/postfix/tasks/main.yml
new file mode 100644
index 0000000..d7ffa65
--- /dev/null
+++ b/roles/postfix/tasks/main.yml
@@ -0,0 +1,36 @@
+---
+- name: Installation Postfix
+ apt: name=postfix state=present
+
+- name: Installation mailutils
+ apt: name=mailutils state=present
+
+- name: Installation libsasl2-2
+ apt: name=libsasl2-2 state=present
+
+- name: Installation ca-certificates
+ apt: name=ca-certificates state=present
+
+- name: Installation libsasl2-modules
+ apt: name=libsasl2-modules state=present
+
+- name: Copie main.cf
+ copy: src=main.cf dest=/etc/postfix/
+
+- name: Copie sasl_passwd
+ copy: src=sasl_passwd dest=/etc/postfix
+
+- name: attribution des droits sasl_passwd
+ shell: chmod 400 /etc/postfix/sasl_passwd
+
+- name: postmap
+ shell: postmap /etc/postfix/sasl_passwd
+
+- name: Copie thawte_Premium_Server_CA.pem
+ copy: src=thawte_Premium_Server_CA.pem dest=/etc/ssl/certs/
+
+- name: Certificats
+ shell: cat /etc/ssl/certs/thawte_Premium_Server_CA.pem |tee -a /etc/postfix/cacert.pem
+ notify:
+ - restart postfix
+
diff --git a/roles/r-ext/files/ferm.conf b/roles/r-ext/files/ferm.conf
new file mode 100644
index 0000000..68cd163
--- /dev/null
+++ b/roles/r-ext/files/ferm.conf
@@ -0,0 +1,113 @@
+# -*- shell-script -*-
+#
+# Configuration file for ferm(1).
+#
+
+@def $DEV_ADM = enp0s3;
+@def $DEV_DMZ = enp0s8;
+@def $DEV_WORLD = enp0s9;
+@def $DEV_VPN = enp0s10;
+@def $DEV_LINK = enp0s16;
+
+@def $NET_ADM = 192.168.99.0/24;
+@def $NET_DMZ = 192.168.100.0/24;
+@def $NET_WORLD = 192.168.0.0/24;
+@def $NET_LINKV = 192.168.1.0/30;
+@def $NET_LINK = 192.168.200.0/24;
+
+# mon ip static
+#@def $HOST_STATIC =
+@include '/root/tools/ansible/gsb/roles/r-ext/files/mkferm |';
+#@def $HOST_PASSERELLEDMZ = 172.16.0.1;
+
+@def &FORWARD_TCP($proto, $port, $dest) = {
+ table filter chain FORWARD interface $DEV_WORLD outerface $DEV_DMZ daddr $dest proto $proto dport $port ACCEPT;
+ table nat chain PREROUTING interface $DEV_WORLD daddr $HOST_STATIC proto $proto dport $port DNAT to $dest;
+}
+#@def &FORWARD($proto, $port, $dest) = {
+# table filter chain FORWARD interface $DEV_DMZ outerface $DEV_PRIVATE daddr $dest proto $proto dport $port ACCEPT;
+# table nat chain PREROUTING interface $DEV_DMZ daddr $HOST_PASSERELLEDMZ proto $proto dport $port DNAT to $dest;
+#}
+
+#&FORWARD(tcp, 3306, 10.0.0.2);
+#&FORWARD_TCP(tcp, http, 192.168.100.254);
+#&FORWARD_TCP(tcp, smtp, 192.168.1.3);
+
+table filter {
+ chain INPUT {
+ policy DROP;
+
+ # connection tracking
+ mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+
+ # allow local packet
+ interface lo ACCEPT;
+
+ # respond to ping
+ proto icmp ACCEPT;
+
+ # allow IPsec
+ interface ($DEV_LINK) {
+ proto udp dport 500 ACCEPT;
+ proto (esp ah) ACCEPT;
+ }
+ # allow SSH connections
+ interface ($DEV_ADM) {
+ proto tcp dport ssh ACCEPT;
+ }
+ # we provide DNS for the internal net
+ interface ($DEV_WORLD $DEV_DMZ) {
+ proto (udp tcp) dport domain ACCEPT;
+ proto (tcp) dport http ACCEPT;
+ }
+
+ }
+ chain OUTPUT {
+ policy ACCEPT;
+
+ # connection tracking
+ #mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+ }
+ chain FORWARD {
+ policy DROP;
+
+ # connection tracking
+ mod state state INVALID DROP;
+ mod state state (ESTABLISHED RELATED) ACCEPT;
+
+ # the DMZ may only access the internet
+ interface ($DEV_DMZ $DEV_LINK) {
+ outerface $DEV_WORLD ACCEPT;
+ # report failure gracefully
+ REJECT reject-with icmp-net-prohibited;
+ }
+
+ interface ($DEV_WORLD) {
+ proto tcp dport http outerface $DEV_DMZ ACCEPT;
+ # report failure gracefully
+ REJECT reject-with icmp-net-prohibited;
+ }
+ }
+}
+
+table nat {
+ chain POSTROUTING {
+ # masquerade private IP addresses
+ saddr ($NET_LINK) outerface $DEV_WORLD SNAT to $HOST_STATIC;
+ }
+}
+
+
+
+# IPv6:
+#domain ip6 {
+# table filter {
+# chain INPUT {
+# policy ACCEPT;
+# # ...
+# }
+# # ...
+# }
+#}
diff --git a/roles/r-ext/files/ipFerm.sh b/roles/r-ext/files/ipFerm.sh
new file mode 100755
index 0000000..ce4ce5d
--- /dev/null
+++ b/roles/r-ext/files/ipFerm.sh
@@ -0,0 +1,3 @@
+#!/bin/bash
+
+ip a show dev enp0s9|grep "inet "|cut -d/ -f1 | cut -dt -f2
diff --git a/roles/r-ext/files/mkferm b/roles/r-ext/files/mkferm
new file mode 100755
index 0000000..f668986
--- /dev/null
+++ b/roles/r-ext/files/mkferm
@@ -0,0 +1,7 @@
+#!/bin/bash
+#IPADD=$(root/ipFerm.sh| tr -d '\n')
+#MSG="@def $HOST_STATIC = $
+echo -n -E "@def \$HOST_STATIC ="
+/root/tools/ansible/gsb/roles/r-ext/files/ipFerm.sh |tr -d '\n'
+echo ";"
+
diff --git a/roles/r-ext/files/nat.sh b/roles/r-ext/files/nat.sh
new file mode 100755
index 0000000..5a065ca
--- /dev/null
+++ b/roles/r-ext/files/nat.sh
@@ -0,0 +1,4 @@
+#!/bin/bash
+echo "1" > /proc/sys/net/ipv4/ip_forward
+iptables -t nat -A POSTROUTING -o enp0s3 -j MASQUERADE
+iptables -t nat -A POSTROUTING -o enp0s9 -j MASQUERADE
\ No newline at end of file
diff --git a/roles/r-ext/files/routagenat b/roles/r-ext/files/routagenat
new file mode 100755
index 0000000..c58086c
--- /dev/null
+++ b/roles/r-ext/files/routagenat
@@ -0,0 +1,3 @@
+#!/usr/bin/perl
+
+qx(route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.200.253);
diff --git a/roles/r-ext/files/sysctl.conf b/roles/r-ext/files/sysctl.conf
new file mode 100644
index 0000000..b138754
--- /dev/null
+++ b/roles/r-ext/files/sysctl.conf
@@ -0,0 +1,60 @@
+#
+# /etc/sysctl.conf - Configuration file for setting system variables
+# See /etc/sysctl.d/ for additonal system variables
+# See sysctl.conf (5) for information.
+#
+
+#kernel.domainname = example.com
+
+# Uncomment the following to stop low-level messages on console
+#kernel.printk = 3 4 1 3
+
+##############################################################3
+# Functions previously found in netbase
+#
+
+# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
+# Turn on Source Address Verification in all interfaces to
+# prevent some spoofing attacks
+#net.ipv4.conf.default.rp_filter=1
+#net.ipv4.conf.all.rp_filter=1
+
+# Uncomment the next line to enable TCP/IP SYN cookies
+# See http://lwn.net/Articles/277146/
+# Note: This may impact IPv6 TCP sessions too
+#net.ipv4.tcp_syncookies=1
+
+# Uncomment the next line to enable packet forwarding for IPv4
+net.ipv4.ip_forward=1
+
+# Uncomment the next line to enable packet forwarding for IPv6
+# Enabling this option disables Stateless Address Autoconfiguration
+# based on Router Advertisements for this host
+#net.ipv6.conf.all.forwarding=1
+
+
+###################################################################
+# Additional settings - these settings can improve the network
+# security of the host and prevent against some network attacks
+# including spoofing attacks and man in the middle attacks through
+# redirection. Some network environments, however, require that these
+# settings are disabled so review and enable them as needed.
+#
+# Do not accept ICMP redirects (prevent MITM attacks)
+#net.ipv4.conf.all.accept_redirects = 0
+#net.ipv6.conf.all.accept_redirects = 0
+# _or_
+# Accept ICMP redirects only for gateways listed in our default
+# gateway list (enabled by default)
+# net.ipv4.conf.all.secure_redirects = 1
+#
+# Do not send ICMP redirects (we are not a router)
+#net.ipv4.conf.all.send_redirects = 0
+#
+# Do not accept IP source route packets (we are not a router)
+#net.ipv4.conf.all.accept_source_route = 0
+#net.ipv6.conf.all.accept_source_route = 0
+#
+# Log Martian Packets
+#net.ipv4.conf.all.log_martians = 1
+#
diff --git a/roles/r-ext/tasks/main.yml b/roles/r-ext/tasks/main.yml
new file mode 100644
index 0000000..6988cd7
--- /dev/null
+++ b/roles/r-ext/tasks/main.yml
@@ -0,0 +1,24 @@
+---
+
+- name: Copie du fichier sysctl.conf
+ copy:
+ src: sysctl.conf
+ dest: /etc/
+
+- name: copier le script de routage
+ copy:
+ src: nat.sh
+ dest: /root/
+ mode: '0755'
+
+- name: installer ferm
+ apt:
+ name: ferm
+ state: present
+ update_cache: yes
+
+- name: copier le fichier ferm.conf
+ copy:
+ src: ferm.conf
+ dest: /etc/ferm/
+
diff --git a/roles/r-int/files/routagenat b/roles/r-int/files/routagenat
new file mode 100755
index 0000000..133152b
--- /dev/null
+++ b/roles/r-int/files/routagenat
@@ -0,0 +1,3 @@
+#!/bin/bash
+
+route add default gw 192.168.200.253
diff --git a/roles/r-int/files/sysctl.conf b/roles/r-int/files/sysctl.conf
new file mode 100644
index 0000000..b138754
--- /dev/null
+++ b/roles/r-int/files/sysctl.conf
@@ -0,0 +1,60 @@
+#
+# /etc/sysctl.conf - Configuration file for setting system variables
+# See /etc/sysctl.d/ for additonal system variables
+# See sysctl.conf (5) for information.
+#
+
+#kernel.domainname = example.com
+
+# Uncomment the following to stop low-level messages on console
+#kernel.printk = 3 4 1 3
+
+##############################################################3
+# Functions previously found in netbase
+#
+
+# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
+# Turn on Source Address Verification in all interfaces to
+# prevent some spoofing attacks
+#net.ipv4.conf.default.rp_filter=1
+#net.ipv4.conf.all.rp_filter=1
+
+# Uncomment the next line to enable TCP/IP SYN cookies
+# See http://lwn.net/Articles/277146/
+# Note: This may impact IPv6 TCP sessions too
+#net.ipv4.tcp_syncookies=1
+
+# Uncomment the next line to enable packet forwarding for IPv4
+net.ipv4.ip_forward=1
+
+# Uncomment the next line to enable packet forwarding for IPv6
+# Enabling this option disables Stateless Address Autoconfiguration
+# based on Router Advertisements for this host
+#net.ipv6.conf.all.forwarding=1
+
+
+###################################################################
+# Additional settings - these settings can improve the network
+# security of the host and prevent against some network attacks
+# including spoofing attacks and man in the middle attacks through
+# redirection. Some network environments, however, require that these
+# settings are disabled so review and enable them as needed.
+#
+# Do not accept ICMP redirects (prevent MITM attacks)
+#net.ipv4.conf.all.accept_redirects = 0
+#net.ipv6.conf.all.accept_redirects = 0
+# _or_
+# Accept ICMP redirects only for gateways listed in our default
+# gateway list (enabled by default)
+# net.ipv4.conf.all.secure_redirects = 1
+#
+# Do not send ICMP redirects (we are not a router)
+#net.ipv4.conf.all.send_redirects = 0
+#
+# Do not accept IP source route packets (we are not a router)
+#net.ipv4.conf.all.accept_source_route = 0
+#net.ipv6.conf.all.accept_source_route = 0
+#
+# Log Martian Packets
+#net.ipv4.conf.all.log_martians = 1
+#
diff --git a/roles/r-int/tasks/main.yml b/roles/r-int/tasks/main.yml
new file mode 100644
index 0000000..01356a7
--- /dev/null
+++ b/roles/r-int/tasks/main.yml
@@ -0,0 +1,19 @@
+---
+
+- name: Copie du fichier sysctl.conf
+ copy: src=sysctl.conf dest=/etc/
+
+- name: copier le script de routage
+ copy: src=routagenat dest=/root/
+
+- name: rendre executabe le script
+ shell: chmod +x /root/routagenat
+
+ #- name: exectuer le script
+ # script: /root/routagenat
+
+ #- name: copier fog server
+ #get_url: url="http://depl/gsbstore/fog_1.4.4.tar.gz" dest=/tmp/fog.tar.gz
+
+ #- name: extraction fog.tar.gz
+ #unarchive: src=/tmp/fog.tar.gz dest=/var/www/ copy=no
diff --git a/roles/s-lb-ab/files/haproxy.cfg b/roles/s-lb-ab/files/haproxy.cfg
new file mode 100644
index 0000000..37933e3
--- /dev/null
+++ b/roles/s-lb-ab/files/haproxy.cfg
@@ -0,0 +1,55 @@
+global
+ log /dev/log local0
+ log /dev/log local1 notice
+ chroot /var/lib/haproxy
+ stats socket /run/haproxy/admin.sock mode 660 level admin
+ stats timeout 30s
+ user haproxy
+ group haproxy
+ daemon
+
+ # Default SSL material locations
+ ca-base /etc/ssl/certs
+ crt-base /etc/ssl/private
+
+ # Default ciphers to use on SSL-enabled listening sockets.
+ # For more information, see ciphers(1SSL). This list is from:
+ # https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/
+ ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS
+ ssl-default-bind-options no-sslv3
+
+defaults
+ log global
+ mode http
+ option httplog
+ option dontlognull
+ timeout connect 5000
+ timeout client 50000
+ timeout server 50000
+ errorfile 400 /etc/haproxy/errors/400.http
+ errorfile 403 /etc/haproxy/errors/403.http
+ errorfile 408 /etc/haproxy/errors/408.http
+ errorfile 500 /etc/haproxy/errors/500.http
+ errorfile 502 /etc/haproxy/errors/502.http
+ errorfile 503 /etc/haproxy/errors/503.http
+ errorfile 504 /etc/haproxy/errors/504.http
+
+frontend proxypublic
+ bind 192.168.100.10:80
+ default_backend fermeweb
+
+backend fermeweb
+ balance roundrobin
+ option httpclose
+ #option httpchk HEAD / HTTP/1.0
+ server s-lb-web1 192.168.101.1:80 check
+ server s-lb-web2 192.168.101.2:80 check
+
+
+listen stats
+ bind *:8080
+ stats enable
+ stats uri /haproxy
+ stats auth admin:admin
+
+
diff --git a/roles/s-lb-ab/handlers/main.yml b/roles/s-lb-ab/handlers/main.yml
new file mode 100644
index 0000000..27f130b
--- /dev/null
+++ b/roles/s-lb-ab/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart haproxy
+ service: name=haproxy state=restarted
diff --git a/roles/s-lb-ab/tasks/main.yml b/roles/s-lb-ab/tasks/main.yml
new file mode 100644
index 0000000..ba1500d
--- /dev/null
+++ b/roles/s-lb-ab/tasks/main.yml
@@ -0,0 +1,11 @@
+---
+- name: Installation d'HAproxy
+ apt:
+ name:
+ - haproxy
+ state: present
+
+- name: Copie du fichier de configuration
+ copy: src=haproxy.cfg dest=/etc/haproxy/haproxy.cfg
+ notify:
+ - restart haproxy
diff --git a/roles/s-lb-bd-ab/README.txt b/roles/s-lb-bd-ab/README.txt
new file mode 100644
index 0000000..1159174
--- /dev/null
+++ b/roles/s-lb-bd-ab/README.txt
@@ -0,0 +1,11 @@
+Apres avoir lancer le bash pull config:
+
+Creer un utilisateur autre que root dans la base de donnee
+CREATE USER 'admin'@'localhost'IDENTIFIED BY 'Azerty1+';
+GRANT ALL PRIVILEGES ON *.* TO 'admin'@'localhost';
+
+Puis executer le script dans files/installmysql.sh qui bloquera les connexions root en localhost et distantes
+
+Enfin se connecter en tant que admin et creer un autre compte pour les utilisateurs
+CREATE USER 'user'@'192.168.102.%'IDENTIFIED BY 'password';
+Le % permet d'autoriser la connexion de tous les postes du reseau 192.168.102.0/24
diff --git a/roles/s-lb-bd-ab/files/.my.cnf b/roles/s-lb-bd-ab/files/.my.cnf
new file mode 100644
index 0000000..34d0e25
--- /dev/null
+++ b/roles/s-lb-bd-ab/files/.my.cnf
@@ -0,0 +1,3 @@
+[client]
+user=root
+password=root
diff --git a/roles/s-lb-bd-ab/files/installmysql.sh b/roles/s-lb-bd-ab/files/installmysql.sh
new file mode 100755
index 0000000..9ee2508
--- /dev/null
+++ b/roles/s-lb-bd-ab/files/installmysql.sh
@@ -0,0 +1,16 @@
+# Download and Install the Latest Updates for the OS
+apt-get update && apt-get upgrade -y
+
+# Install MySQL Server in a Non-Interactive mode. Default root password will be "root"
+echo "mysql-server mysql-server/root_password password root" | debconf-set-selections
+echo "mysql-server mysql-server/root_password_again password root" | debconf-set-selections
+apt-get -y install mysql-server
+
+
+# Run the MySQL Secure Installation wizard
+mysql_secure_installation
+
+sed -i 's/127\.0\.0\.1/0\.0\.0\.0/g' /etc/mysql/my.cnf
+mysql -uroot -p -e 'USE mysql; UPDATE `user` SET `Host`="%" WHERE `User`="root" AND `Host`="localhost"; DELETE FROM `user` WHERE `Host` != "%" AND `User`="root"; FLUSH PRIVILEGES;'
+
+service mysql restart
\ No newline at end of file
diff --git a/roles/s-lb-bd-ab/files/my.cnf b/roles/s-lb-bd-ab/files/my.cnf
new file mode 100644
index 0000000..1308652
--- /dev/null
+++ b/roles/s-lb-bd-ab/files/my.cnf
@@ -0,0 +1,128 @@
+#
+# The MySQL database server configuration file.
+#
+# You can copy this to one of:
+# - "/etc/mysql/my.cnf" to set global options,
+# - "~/.my.cnf" to set user-specific options.
+#
+# One can use all long options that the program supports.
+# Run program with --help to get a list of available options and with
+# --print-defaults to see which it would actually understand and use.
+#
+# For explanations see
+# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
+
+# This will be passed to all mysql clients
+# It has been reported that passwords should be enclosed with ticks/quotes
+# escpecially if they contain "#" chars...
+# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
+[client]
+port = 3306
+socket = /var/run/mysqld/mysqld.sock
+
+# Here is entries for some specific programs
+# The following values assume you have at least 32M ram
+
+# This was formally known as [safe_mysqld]. Both versions are currently parsed.
+[mysqld_safe]
+socket = /var/run/mysqld/mysqld.sock
+nice = 0
+
+[mysqld]
+#
+# * Basic Settings
+#
+user = mysql
+pid-file = /var/run/mysqld/mysqld.pid
+socket = /var/run/mysqld/mysqld.sock
+port = 3306
+basedir = /usr
+datadir = /var/lib/mysql
+tmpdir = /tmp
+lc-messages-dir = /usr/share/mysql
+skip-external-locking
+#
+# Instead of skip-networking the default is now to listen only on
+# localhost which is more compatible and is not less secure.
+#bind-address = 127.0.0.1
+#
+# * Fine Tuning
+#
+key_buffer = 16M
+max_allowed_packet = 16M
+thread_stack = 192K
+thread_cache_size = 8
+# This replaces the startup script and checks MyISAM tables if needed
+# the first time they are touched
+myisam-recover = BACKUP
+#max_connections = 100
+#table_cache = 64
+#thread_concurrency = 10
+#
+# * Query Cache Configuration
+#
+query_cache_limit = 1M
+query_cache_size = 16M
+#
+# * Logging and Replication
+#
+# Both location gets rotated by the cronjob.
+# Be aware that this log type is a performance killer.
+# As of 5.1 you can enable the log at runtime!
+#general_log_file = /var/log/mysql/mysql.log
+#general_log = 1
+#
+# Error log - should be very few entries.
+#
+log_error = /var/log/mysql/error.log
+#
+# Here you can see queries with especially long duration
+#slow_query_log_file = /var/log/mysql/mysql-slow.log
+#slow_query_log = 1
+#long_query_time = 2
+#log_queries_not_using_indexes
+#
+# The following can be used as easy to replay backup logs or for replication.
+# note: if you are setting up a replication slave, see README.Debian about
+# other settings you may need to change.
+#server-id = 1
+#log_bin = /var/log/mysql/mysql-bin.log
+expire_logs_days = 10
+max_binlog_size = 100M
+#binlog_do_db = include_database_name
+#binlog_ignore_db = include_database_name
+#
+# * InnoDB
+#
+# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
+# Read the manual for more InnoDB related options. There are many!
+#
+# * Security Features
+#
+# Read the manual, too, if you want chroot!
+# chroot = /var/lib/mysql/
+#
+# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
+#
+# ssl-ca=/etc/mysql/cacert.pem
+# ssl-cert=/etc/mysql/server-cert.pem
+# ssl-key=/etc/mysql/server-key.pem
+
+
+
+[mysqldump]
+quick
+quote-names
+max_allowed_packet = 16M
+
+[mysql]
+#no-auto-rehash # faster start of mysql but no tab completition
+
+[isamchk]
+key_buffer = 16M
+
+#
+# * IMPORTANT: Additional settings that can override those from this file!
+# The files must end with '.cnf', otherwise they'll be ignored.
+#
+!includedir /etc/mysql/conf.d/
diff --git a/roles/s-lb-bd-ab/handlers/main.yml b/roles/s-lb-bd-ab/handlers/main.yml
new file mode 100644
index 0000000..caa5308
--- /dev/null
+++ b/roles/s-lb-bd-ab/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart mysql-server
+ service: name=mysql-server state=restarted
diff --git a/roles/s-lb-bd/files/.my.cnf b/roles/s-lb-bd/files/.my.cnf
new file mode 100644
index 0000000..34d0e25
--- /dev/null
+++ b/roles/s-lb-bd/files/.my.cnf
@@ -0,0 +1,3 @@
+[client]
+user=root
+password=root
diff --git a/roles/s-lb-bd/files/installmysql.sh b/roles/s-lb-bd/files/installmysql.sh
new file mode 100755
index 0000000..9ee2508
--- /dev/null
+++ b/roles/s-lb-bd/files/installmysql.sh
@@ -0,0 +1,16 @@
+# Download and Install the Latest Updates for the OS
+apt-get update && apt-get upgrade -y
+
+# Install MySQL Server in a Non-Interactive mode. Default root password will be "root"
+echo "mysql-server mysql-server/root_password password root" | debconf-set-selections
+echo "mysql-server mysql-server/root_password_again password root" | debconf-set-selections
+apt-get -y install mysql-server
+
+
+# Run the MySQL Secure Installation wizard
+mysql_secure_installation
+
+sed -i 's/127\.0\.0\.1/0\.0\.0\.0/g' /etc/mysql/my.cnf
+mysql -uroot -p -e 'USE mysql; UPDATE `user` SET `Host`="%" WHERE `User`="root" AND `Host`="localhost"; DELETE FROM `user` WHERE `Host` != "%" AND `User`="root"; FLUSH PRIVILEGES;'
+
+service mysql restart
\ No newline at end of file
diff --git a/roles/s-lb-bd/files/my.cnf b/roles/s-lb-bd/files/my.cnf
new file mode 100644
index 0000000..1308652
--- /dev/null
+++ b/roles/s-lb-bd/files/my.cnf
@@ -0,0 +1,128 @@
+#
+# The MySQL database server configuration file.
+#
+# You can copy this to one of:
+# - "/etc/mysql/my.cnf" to set global options,
+# - "~/.my.cnf" to set user-specific options.
+#
+# One can use all long options that the program supports.
+# Run program with --help to get a list of available options and with
+# --print-defaults to see which it would actually understand and use.
+#
+# For explanations see
+# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
+
+# This will be passed to all mysql clients
+# It has been reported that passwords should be enclosed with ticks/quotes
+# escpecially if they contain "#" chars...
+# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
+[client]
+port = 3306
+socket = /var/run/mysqld/mysqld.sock
+
+# Here is entries for some specific programs
+# The following values assume you have at least 32M ram
+
+# This was formally known as [safe_mysqld]. Both versions are currently parsed.
+[mysqld_safe]
+socket = /var/run/mysqld/mysqld.sock
+nice = 0
+
+[mysqld]
+#
+# * Basic Settings
+#
+user = mysql
+pid-file = /var/run/mysqld/mysqld.pid
+socket = /var/run/mysqld/mysqld.sock
+port = 3306
+basedir = /usr
+datadir = /var/lib/mysql
+tmpdir = /tmp
+lc-messages-dir = /usr/share/mysql
+skip-external-locking
+#
+# Instead of skip-networking the default is now to listen only on
+# localhost which is more compatible and is not less secure.
+#bind-address = 127.0.0.1
+#
+# * Fine Tuning
+#
+key_buffer = 16M
+max_allowed_packet = 16M
+thread_stack = 192K
+thread_cache_size = 8
+# This replaces the startup script and checks MyISAM tables if needed
+# the first time they are touched
+myisam-recover = BACKUP
+#max_connections = 100
+#table_cache = 64
+#thread_concurrency = 10
+#
+# * Query Cache Configuration
+#
+query_cache_limit = 1M
+query_cache_size = 16M
+#
+# * Logging and Replication
+#
+# Both location gets rotated by the cronjob.
+# Be aware that this log type is a performance killer.
+# As of 5.1 you can enable the log at runtime!
+#general_log_file = /var/log/mysql/mysql.log
+#general_log = 1
+#
+# Error log - should be very few entries.
+#
+log_error = /var/log/mysql/error.log
+#
+# Here you can see queries with especially long duration
+#slow_query_log_file = /var/log/mysql/mysql-slow.log
+#slow_query_log = 1
+#long_query_time = 2
+#log_queries_not_using_indexes
+#
+# The following can be used as easy to replay backup logs or for replication.
+# note: if you are setting up a replication slave, see README.Debian about
+# other settings you may need to change.
+#server-id = 1
+#log_bin = /var/log/mysql/mysql-bin.log
+expire_logs_days = 10
+max_binlog_size = 100M
+#binlog_do_db = include_database_name
+#binlog_ignore_db = include_database_name
+#
+# * InnoDB
+#
+# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
+# Read the manual for more InnoDB related options. There are many!
+#
+# * Security Features
+#
+# Read the manual, too, if you want chroot!
+# chroot = /var/lib/mysql/
+#
+# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
+#
+# ssl-ca=/etc/mysql/cacert.pem
+# ssl-cert=/etc/mysql/server-cert.pem
+# ssl-key=/etc/mysql/server-key.pem
+
+
+
+[mysqldump]
+quick
+quote-names
+max_allowed_packet = 16M
+
+[mysql]
+#no-auto-rehash # faster start of mysql but no tab completition
+
+[isamchk]
+key_buffer = 16M
+
+#
+# * IMPORTANT: Additional settings that can override those from this file!
+# The files must end with '.cnf', otherwise they'll be ignored.
+#
+!includedir /etc/mysql/conf.d/
diff --git a/roles/s-lb-bd/handlers/main.yml b/roles/s-lb-bd/handlers/main.yml
new file mode 100644
index 0000000..caa5308
--- /dev/null
+++ b/roles/s-lb-bd/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart mysql-server
+ service: name=mysql-server state=restarted
diff --git a/roles/s-lb-bd/tasks/main.yml b/roles/s-lb-bd/tasks/main.yml
new file mode 100644
index 0000000..9f65e0e
--- /dev/null
+++ b/roles/s-lb-bd/tasks/main.yml
@@ -0,0 +1,4 @@
+---
+- name: Install paquets
+ apt: name=mysql-server state=present force=yes
+
diff --git a/roles/s-lb-web-ab/files/.my.cnf b/roles/s-lb-web-ab/files/.my.cnf
new file mode 100644
index 0000000..34d0e25
--- /dev/null
+++ b/roles/s-lb-web-ab/files/.my.cnf
@@ -0,0 +1,3 @@
+[client]
+user=root
+password=root
diff --git a/roles/s-lb-web-ab/files/compter.bash b/roles/s-lb-web-ab/files/compter.bash
new file mode 100644
index 0000000..9d257fa
--- /dev/null
+++ b/roles/s-lb-web-ab/files/compter.bash
@@ -0,0 +1,4 @@
+#!/bin/bash
+
+echo "" > /var/log/apache2/access.log
+watch -n 0 wc -l /var/log/apache2/access.log
diff --git a/roles/s-lb-web-ab/handlers/main.yml b/roles/s-lb-web-ab/handlers/main.yml
new file mode 100644
index 0000000..e5c9101
--- /dev/null
+++ b/roles/s-lb-web-ab/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart apache2
+ service: name=apache2 state=restarted
\ No newline at end of file
diff --git a/roles/s-lb-web-ab/tasks/main.yml b/roles/s-lb-web-ab/tasks/main.yml
new file mode 100644
index 0000000..251a74c
--- /dev/null
+++ b/roles/s-lb-web-ab/tasks/main.yml
@@ -0,0 +1,20 @@
+---
+- name: Install apache2 php php5-mysql
+ apt:
+ name:
+ - apache2
+ - php
+ - php-mysql
+ state: present
+
+- name: copie exports pour partage nfs wordpress
+ copy: src=compter.bash dest=/root
+
+- name: Changement de permission pour compter.bash
+ shell: chmod a+x /root/compter.bash
+
+#- name: Envoi d'index dans /var/www/
+# copy: src=index.html dest=/var/www/
+
+#- name: Install glusterfs client
+# apt: pkg=glusterfs-client state=present update_cache=yes
diff --git a/roles/s-lb-web/files/.my.cnf b/roles/s-lb-web/files/.my.cnf
new file mode 100644
index 0000000..34d0e25
--- /dev/null
+++ b/roles/s-lb-web/files/.my.cnf
@@ -0,0 +1,3 @@
+[client]
+user=root
+password=root
diff --git a/roles/s-lb-web/files/compter.bash b/roles/s-lb-web/files/compter.bash
new file mode 100644
index 0000000..9d257fa
--- /dev/null
+++ b/roles/s-lb-web/files/compter.bash
@@ -0,0 +1,4 @@
+#!/bin/bash
+
+echo "" > /var/log/apache2/access.log
+watch -n 0 wc -l /var/log/apache2/access.log
diff --git a/roles/s-lb-web/handlers/main.yml b/roles/s-lb-web/handlers/main.yml
new file mode 100644
index 0000000..e5c9101
--- /dev/null
+++ b/roles/s-lb-web/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart apache2
+ service: name=apache2 state=restarted
\ No newline at end of file
diff --git a/roles/s-lb-web/tasks/main.yml b/roles/s-lb-web/tasks/main.yml
new file mode 100644
index 0000000..62c7264
--- /dev/null
+++ b/roles/s-lb-web/tasks/main.yml
@@ -0,0 +1,21 @@
+---
+- name: Install apache2
+ apt: pkg=apache2 state=present update_cache=yes
+
+- name: Install php
+ apt: pkg=php state=present update_cache=yes
+
+- name: Install php5-mysql (pour pdo)
+ apt: pkg=php-mysql state=present update_cache=yes
+
+- name: copie exports pour partage nfs wordpress
+ copy: src=compter.bash dest=/root
+
+- name: Changement de permission pour compter.bash
+ shell: chmod a+x /root/compter.bash
+
+#- name: Envoi d'index dans /var/www/
+# copy: src=index.html dest=/var/www/
+
+#- name: Install glusterfs client
+# apt: pkg=glusterfs-client state=present update_cache=yes
diff --git a/roles/s-lb-wordpress/handlers/main.yml b/roles/s-lb-wordpress/handlers/main.yml
new file mode 100644
index 0000000..b8b354d
--- /dev/null
+++ b/roles/s-lb-wordpress/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart apache2
+ service: name=apache2 state=restarted
diff --git a/roles/s-lb-wordpress/tasks/main.yml b/roles/s-lb-wordpress/tasks/main.yml
new file mode 100644
index 0000000..16e86e8
--- /dev/null
+++ b/roles/s-lb-wordpress/tasks/main.yml
@@ -0,0 +1,35 @@
+---
+ - name: creation repertoir
+ file:
+ path: /home/
+ state: directory
+ - name: download and extract wordpress
+ unarchive:
+ src: http://depl/gsbstore/wordpress-5.3.2-fr_FR.tar.gz
+ dest: /home/
+ remote_src: yes
+
+ - name: Copy sample config file
+ command: mv /home/wordpress/wp-config-sample.php /home/wordpress/wp-config.php creates=/home/wordpress/wp-config.php
+
+ - name: Update WordPress config file
+ lineinfile:
+ dest=/home/wordpress/wp-config.php
+ regexp="{{ item.regexp }}"
+ line="{{ item.line }}"
+ with_items:
+ - {'regexp': "define\\('DB_NAME', '(.)+'\\);", 'line': "define('DB_NAME', '{{wp_mysql_db}}');"}
+ - {'regexp': "define\\('DB_HOST', '(.)+'\\);", 'line': "define('DB_HOST', '{{wp_mysql_host}}');"}
+ - {'regexp': "define\\('DB_USER', '(.)+'\\);", 'line': "define('DB_USER', '{{wp_mysql_user}}');"}
+ - {'regexp': "define\\('DB_PASSWORD', '(.)+'\\);", 'line': "define('DB_PASSWORD', '{{wp_mysql_password}}');"}
+
+# - name: Fix permissions
+# shell: chown -R www-data /var/www/wordpress/*
+#
+# - name: Update default Apache site
+# lineinfile:
+# dest=/etc/apache2/sites-enabled/000-default.conf
+# regexp="(.)+DocumentRoot /var/www/html"
+# line="DocumentRoot /var/www/wordpress"
+# notify:
+# - restart apache2
diff --git a/roles/s-lb/files/goss.yaml b/roles/s-lb/files/goss.yaml
new file mode 100644
index 0000000..4c24938
--- /dev/null
+++ b/roles/s-lb/files/goss.yaml
@@ -0,0 +1,23 @@
+port:
+ tcp:80:
+ listening: true
+ ip:
+ - 192.168.100.11
+service:
+ haproxy:
+ enabled: true
+ running: true
+ sshd:
+ enabled: true
+ running: true
+interface:
+ enp0s8:
+ exists: true
+ addrs:
+ - 192.168.100.11/24
+ mtu: 1500
+ enp0s9:
+ exists: true
+ addrs:
+ - 192.168.101.254/24
+ mtu: 1500
diff --git a/roles/s-lb/files/haproxy.cfg b/roles/s-lb/files/haproxy.cfg
new file mode 100644
index 0000000..0f09078
--- /dev/null
+++ b/roles/s-lb/files/haproxy.cfg
@@ -0,0 +1,56 @@
+global
+ log /dev/log local0
+ log /dev/log local1 notice
+ chroot /var/lib/haproxy
+ stats socket /run/haproxy/admin.sock mode 660 level admin
+ stats timeout 30s
+ user haproxy
+ group haproxy
+ daemon
+
+ # Default SSL material locations
+ ca-base /etc/ssl/certs
+ crt-base /etc/ssl/private
+
+ # Default ciphers to use on SSL-enabled listening sockets.
+ # For more information, see ciphers(1SSL). This list is from:
+ # https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/
+ ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS
+ ssl-default-bind-options no-sslv3
+
+defaults
+ log global
+ mode http
+ option httplog
+ option dontlognull
+ timeout connect 5000
+ timeout client 50000
+ timeout server 50000
+ errorfile 400 /etc/haproxy/errors/400.http
+ errorfile 403 /etc/haproxy/errors/403.http
+ errorfile 408 /etc/haproxy/errors/408.http
+ errorfile 500 /etc/haproxy/errors/500.http
+ errorfile 502 /etc/haproxy/errors/502.http
+ errorfile 503 /etc/haproxy/errors/503.http
+ errorfile 504 /etc/haproxy/errors/504.http
+
+frontend proxypublic
+ bind 192.168.100.10:80
+ default_backend fermeweb
+
+backend fermeweb
+ balance roundrobin
+ option httpclose
+ #option httpchk HEAD / HTTP/1.0
+ server s-lb-web1 192.168.101.1:80 check
+ server s-lb-web2 192.168.101.2:80 check
+ #server s-lb-web3 192.168.101.3:80 check
+
+
+listen stats
+ bind *:8080
+ stats enable
+ stats uri /haproxy
+ stats auth admin:admin
+
+
diff --git a/roles/s-lb/handlers/main.yml b/roles/s-lb/handlers/main.yml
new file mode 100644
index 0000000..27f130b
--- /dev/null
+++ b/roles/s-lb/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart haproxy
+ service: name=haproxy state=restarted
diff --git a/roles/s-lb/tasks/main.yml b/roles/s-lb/tasks/main.yml
new file mode 100644
index 0000000..ba3692d
--- /dev/null
+++ b/roles/s-lb/tasks/main.yml
@@ -0,0 +1,11 @@
+---
+ - name: Installation d'HAproxy
+ apt: pkg=haproxy state=present update_cache=yes
+
+ - name: Fichier de configuration
+ copy: src=haproxy.cfg dest=/etc/haproxy/haproxy.cfg
+ notify:
+ - restart haproxy
+
+ - name: Copie de goss
+ copy: src=goss.yaml dest=/root
diff --git a/roles/s-nas-client/handlers/main.yml b/roles/s-nas-client/handlers/main.yml
new file mode 100644
index 0000000..3aa7dca
--- /dev/null
+++ b/roles/s-nas-client/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart nfs-common
+ service: name=nfs-common state=restarted
diff --git a/roles/s-nas-client/tasks/main.yml b/roles/s-nas-client/tasks/main.yml
new file mode 100644
index 0000000..0189683
--- /dev/null
+++ b/roles/s-nas-client/tasks/main.yml
@@ -0,0 +1,13 @@
+---
+ - name: installation des paquets
+ apt:
+ name:
+ - nfs-common
+ state: latest
+
+ - name: ajout du montage automatique dans fstab
+ lineinfile:
+ dest: /etc/fstab
+ regexp: ''
+ insertafter: EOF
+ line: '192.168.102.253:/home/wordpress /var/www/html/wordpress nfs _netdev,soft,timeo=5,intr,rsize=8192,wsize=8192,wsize=8192 0 0'
diff --git a/roles/s-nas-server/files/exports b/roles/s-nas-server/files/exports
new file mode 100644
index 0000000..74c649d
--- /dev/null
+++ b/roles/s-nas-server/files/exports
@@ -0,0 +1,10 @@
+# /etc/exports: the access control list for filesystems which may be exported
+# to NFS clients. See exports(5).
+#
+# Example for NFSv2 and NFSv3:
+# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
+#
+# Example for NFSv4:
+# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
+# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
+/home/wordpress 192.168.102.0/255.255.255.0 (rw,no_root_squash,subtree_check)
diff --git a/roles/s-nas-server/handlers/main.yml b/roles/s-nas-server/handlers/main.yml
new file mode 100644
index 0000000..eb9f450
--- /dev/null
+++ b/roles/s-nas-server/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart nfs-kernel-server
+ service: name=nfs-kernel-server state=restarted
diff --git a/roles/s-nas-server/tasks/main.yml b/roles/s-nas-server/tasks/main.yml
new file mode 100644
index 0000000..3f9b4a4
--- /dev/null
+++ b/roles/s-nas-server/tasks/main.yml
@@ -0,0 +1,18 @@
+---
+ - name: installation des paquets
+ apt:
+ name:
+ - nfs-kernel-server
+ state: latest
+
+ - name: copie exports pour partage nfs wordpress
+ copy:
+ src: exports
+ dest: /etc
+
+ - name: redemarrage du service rpcbind requis pour le service nfs
+ shell: service rpcbind restart
+
+ - name: redemarrage du service nfs-kernel-server
+ shell: service nfs-kernel-server restart
+
diff --git a/roles/s-ssh/files/config b/roles/s-ssh/files/config
new file mode 100644
index 0000000..d460bbf
--- /dev/null
+++ b/roles/s-ssh/files/config
@@ -0,0 +1,51 @@
+HashKnownHosts yes
+
+Host s-proxy
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-proxy
+ hostname s-proxy.gsb.adm
+
+Host s-infra
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-infra
+ hostname s-infra.gsb.adm
+
+Host s-appli
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-appli
+ hostname s-appli.gsb.adm
+
+Host s-mess
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-mess
+ hostname s-mess.gsb.adm
+
+Host s-itil
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-itil
+ hostname s-itil.gsb.adm
+
+Host s-mon
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-mon
+ hostname s-mon.gsb.adm
+
+Host s-backup
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-backup
+ hostname s-backup.gsb.adm
+
+Host r-int
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/r-int
+ hostname r-int.gsb.adm
+
+Host r-ext
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/r-ext
+ hostname r-ext.gsb.adm
+
+Host s-mon
+ user root
+# UserKnownHostsFile=~/.ssh/known_hosts/s-spec
+ hostname s-mon.gsb.adm
diff --git a/roles/s-ssh/handlers/main.yml b/roles/s-ssh/handlers/main.yml
new file mode 100644
index 0000000..59608ec
--- /dev/null
+++ b/roles/s-ssh/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart lighttpd
+ service: name=lighttpd state=restarted
diff --git a/roles/s-ssh/tasks/main.yml b/roles/s-ssh/tasks/main.yml
new file mode 100644
index 0000000..d717eb0
--- /dev/null
+++ b/roles/s-ssh/tasks/main.yml
@@ -0,0 +1,22 @@
+---
+
+- name: Installation lighttpd
+ apt: name=lighttpd state=present
+
+- user: name=adm shell=/bin/bash password=no
+
+- user: name=adm generate_ssh_key=yes ssh_key_bits=2048 ssh_key_file=.ssh/id_rsa
+
+- name: Copie du fichier .ssh/config
+ copy: src=config dest=/home/adm/.ssh/
+
+- name: Copie de la clé publique dans le repertoire web
+ copy: remote_src=true src=/home/adm/.ssh/id_rsa.pub dest=/var/www/html
+ notify:
+ - restart lighttpd
+
+ #- name: Copie de la signature des machines
+ # copy: src=known_hosts dest=/home/adm/.ssh/
+ # notify:
+ # - restart apache2
+
diff --git a/roles/snmp-agent/files/snmpd.conf b/roles/snmp-agent/files/snmpd.conf
new file mode 100644
index 0000000..6b81b54
--- /dev/null
+++ b/roles/snmp-agent/files/snmpd.conf
@@ -0,0 +1,193 @@
+###############################################################################
+#
+# EXAMPLE.conf:
+# An example configuration file for configuring the Net-SNMP agent ('snmpd')
+# See the 'snmpd.conf(5)' man page for details
+#
+# Some entries are deliberately commented out, and will need to be explicitly activated
+#
+###############################################################################
+#
+# AGENT BEHAVIOUR
+#
+
+# Listen for connections from the local system only
+#agentAddress udp:127.0.0.1:161
+# Listen for connections on all interfaces (both IPv4 *and* IPv6)
+agentAddress udp:161,udp6:[::1]:161
+
+
+
+###############################################################################
+#
+# SNMPv3 AUTHENTICATION
+#
+# Note that these particular settings don't actually belong here.
+# They should be copied to the file /var/lib/snmp/snmpd.conf
+# and the passwords changed, before being uncommented in that file *only*.
+# Then restart the agent
+
+# createUser authOnlyUser MD5 "remember to change this password"
+# createUser authPrivUser SHA "remember to change this one too" DES
+# createUser internalUser MD5 "this is only ever used internally, but still change the password"
+
+# If you also change the usernames (which might be sensible),
+# then remember to update the other occurances in this example config file to match.
+
+
+
+###############################################################################
+#
+# ACCESS CONTROL
+#
+
+ # system + hrSystem groups only
+view systemonly included .1.3.6.1.2.1.1
+view systemonly included .1.3.6.1.2.1.25.1
+
+ # Full access from the local host
+rocommunity public s-mon.gsb.adm
+ # Default access to basic system info
+rocommunity public
+
+ # Full access from an example network
+ # Adjust this network address to match your local
+ # settings, change the community string,
+ # and check the 'agentAddress' setting above
+#rocommunity secret 10.0.0.0/16
+
+ # Full read-only access for SNMPv3
+ rouser authOnlyUser
+ # Full write access for encrypted requests
+ # Remember to activate the 'createUser' lines above
+#rwuser authPrivUser priv
+
+# It's no longer typically necessary to use the full 'com2sec/group/access' configuration
+# r[ou]user and r[ow]community, together with suitable views, should cover most requirements
+
+
+
+###############################################################################
+#
+# SYSTEM INFORMATION
+#
+
+# Note that setting these values here, results in the corresponding MIB objects being 'read-only'
+# See snmpd.conf(5) for more details
+sysLocation Sitting on the Dock of the Bay
+sysContact Me <me@example.org>
+ # Application + End-to-End layers
+sysServices 72
+
+
+#
+# Process Monitoring
+#
+ # At least one 'mountd' process
+proc mountd
+ # No more than 4 'ntalkd' processes - 0 is OK
+proc ntalkd 4
+ # At least one 'sendmail' process, but no more than 10
+proc sendmail 10 1
+
+# Walk the UCD-SNMP-MIB::prTable to see the resulting output
+# Note that this table will be empty if there are no "proc" entries in the snmpd.conf file
+
+
+#
+# Disk Monitoring
+#
+ # 10MBs required on root disk, 5% free on /var, 10% free on all other disks
+disk / 10000
+disk /var 5%
+includeAllDisks 10%
+
+# Walk the UCD-SNMP-MIB::dskTable to see the resulting output
+# Note that this table will be empty if there are no "disk" entries in the snmpd.conf file
+
+
+#
+# System Load
+#
+ # Unacceptable 1-, 5-, and 15-minute load averages
+load 12 10 5
+
+# Walk the UCD-SNMP-MIB::laTable to see the resulting output
+# Note that this table *will* be populated, even without a "load" entry in the snmpd.conf file
+
+
+
+###############################################################################
+#
+# ACTIVE MONITORING
+#
+
+ # send SNMPv1 traps
+ trapsink localhost public
+ # send SNMPv2c traps
+#trap2sink localhost public
+ # send SNMPv2c INFORMs
+#informsink localhost public
+
+# Note that you typically only want *one* of these three lines
+# Uncommenting two (or all three) will result in multiple copies of each notification.
+
+
+#
+# Event MIB - automatically generate alerts
+#
+ # Remember to activate the 'createUser' lines above
+iquerySecName internalUser
+rouser internalUser
+ # generate traps on UCD error conditions
+defaultMonitors yes
+ # generate traps on linkUp/Down
+linkUpDownNotifications yes
+
+
+
+###############################################################################
+#
+# EXTENDING THE AGENT
+#
+
+#
+# Arbitrary extension commands
+#
+ extend test1 /bin/echo Hello, world!
+ extend-sh test2 echo Hello, world! ; echo Hi there ; exit 35
+#extend-sh test3 /bin/sh /tmp/shtest
+
+# Note that this last entry requires the script '/tmp/shtest' to be created first,
+# containing the same three shell commands, before the line is uncommented
+
+# Walk the NET-SNMP-EXTEND-MIB tables (nsExtendConfigTable, nsExtendOutput1Table
+# and nsExtendOutput2Table) to see the resulting output
+
+# Note that the "extend" directive supercedes the previous "exec" and "sh" directives
+# However, walking the UCD-SNMP-MIB::extTable should still returns the same output,
+# as well as the fuller results in the above tables.
+
+
+#
+# "Pass-through" MIB extension command
+#
+#pass .1.3.6.1.4.1.8072.2.255 /bin/sh PREFIX/local/passtest
+#pass .1.3.6.1.4.1.8072.2.255 /usr/bin/perl PREFIX/local/passtest.pl
+
+# Note that this requires one of the two 'passtest' scripts to be installed first,
+# before the appropriate line is uncommented.
+# These scripts can be found in the 'local' directory of the source distribution,
+# and are not installed automatically.
+
+# Walk the NET-SNMP-PASS-MIB::netSnmpPassExamples subtree to see the resulting output
+
+
+#
+# AgentX Sub-agents
+#
+ # Run as an AgentX master agent
+ master agentx
+ # Listen for network connections (from localhost)
+ # rather than the default named socket /var/agentx/master
+#agentXSocket tcp:localhost:705
diff --git a/roles/snmp-agent/handlers/main.yml b/roles/snmp-agent/handlers/main.yml
new file mode 100644
index 0000000..9d9b583
--- /dev/null
+++ b/roles/snmp-agent/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart snmpd
+ service: name=snmpd state=restarted
diff --git a/roles/snmp-agent/tasks/main.yml b/roles/snmp-agent/tasks/main.yml
new file mode 100644
index 0000000..4b4a192
--- /dev/null
+++ b/roles/snmp-agent/tasks/main.yml
@@ -0,0 +1,12 @@
+---
+
+- name: Installation snmpd
+ apt: name=snmpd state=present
+
+- name: Installation snmp
+ apt: name=snmp state=present
+
+- name: Copie du fichier snmpd.conf
+ copy: src=snmpd.conf dest=/etc/snmp/
+ notify:
+ - restart snmpd
diff --git a/roles/snmp-cs/files/snmpd.conf b/roles/snmp-cs/files/snmpd.conf
new file mode 100644
index 0000000..6b81b54
--- /dev/null
+++ b/roles/snmp-cs/files/snmpd.conf
@@ -0,0 +1,193 @@
+###############################################################################
+#
+# EXAMPLE.conf:
+# An example configuration file for configuring the Net-SNMP agent ('snmpd')
+# See the 'snmpd.conf(5)' man page for details
+#
+# Some entries are deliberately commented out, and will need to be explicitly activated
+#
+###############################################################################
+#
+# AGENT BEHAVIOUR
+#
+
+# Listen for connections from the local system only
+#agentAddress udp:127.0.0.1:161
+# Listen for connections on all interfaces (both IPv4 *and* IPv6)
+agentAddress udp:161,udp6:[::1]:161
+
+
+
+###############################################################################
+#
+# SNMPv3 AUTHENTICATION
+#
+# Note that these particular settings don't actually belong here.
+# They should be copied to the file /var/lib/snmp/snmpd.conf
+# and the passwords changed, before being uncommented in that file *only*.
+# Then restart the agent
+
+# createUser authOnlyUser MD5 "remember to change this password"
+# createUser authPrivUser SHA "remember to change this one too" DES
+# createUser internalUser MD5 "this is only ever used internally, but still change the password"
+
+# If you also change the usernames (which might be sensible),
+# then remember to update the other occurances in this example config file to match.
+
+
+
+###############################################################################
+#
+# ACCESS CONTROL
+#
+
+ # system + hrSystem groups only
+view systemonly included .1.3.6.1.2.1.1
+view systemonly included .1.3.6.1.2.1.25.1
+
+ # Full access from the local host
+rocommunity public s-mon.gsb.adm
+ # Default access to basic system info
+rocommunity public
+
+ # Full access from an example network
+ # Adjust this network address to match your local
+ # settings, change the community string,
+ # and check the 'agentAddress' setting above
+#rocommunity secret 10.0.0.0/16
+
+ # Full read-only access for SNMPv3
+ rouser authOnlyUser
+ # Full write access for encrypted requests
+ # Remember to activate the 'createUser' lines above
+#rwuser authPrivUser priv
+
+# It's no longer typically necessary to use the full 'com2sec/group/access' configuration
+# r[ou]user and r[ow]community, together with suitable views, should cover most requirements
+
+
+
+###############################################################################
+#
+# SYSTEM INFORMATION
+#
+
+# Note that setting these values here, results in the corresponding MIB objects being 'read-only'
+# See snmpd.conf(5) for more details
+sysLocation Sitting on the Dock of the Bay
+sysContact Me <me@example.org>
+ # Application + End-to-End layers
+sysServices 72
+
+
+#
+# Process Monitoring
+#
+ # At least one 'mountd' process
+proc mountd
+ # No more than 4 'ntalkd' processes - 0 is OK
+proc ntalkd 4
+ # At least one 'sendmail' process, but no more than 10
+proc sendmail 10 1
+
+# Walk the UCD-SNMP-MIB::prTable to see the resulting output
+# Note that this table will be empty if there are no "proc" entries in the snmpd.conf file
+
+
+#
+# Disk Monitoring
+#
+ # 10MBs required on root disk, 5% free on /var, 10% free on all other disks
+disk / 10000
+disk /var 5%
+includeAllDisks 10%
+
+# Walk the UCD-SNMP-MIB::dskTable to see the resulting output
+# Note that this table will be empty if there are no "disk" entries in the snmpd.conf file
+
+
+#
+# System Load
+#
+ # Unacceptable 1-, 5-, and 15-minute load averages
+load 12 10 5
+
+# Walk the UCD-SNMP-MIB::laTable to see the resulting output
+# Note that this table *will* be populated, even without a "load" entry in the snmpd.conf file
+
+
+
+###############################################################################
+#
+# ACTIVE MONITORING
+#
+
+ # send SNMPv1 traps
+ trapsink localhost public
+ # send SNMPv2c traps
+#trap2sink localhost public
+ # send SNMPv2c INFORMs
+#informsink localhost public
+
+# Note that you typically only want *one* of these three lines
+# Uncommenting two (or all three) will result in multiple copies of each notification.
+
+
+#
+# Event MIB - automatically generate alerts
+#
+ # Remember to activate the 'createUser' lines above
+iquerySecName internalUser
+rouser internalUser
+ # generate traps on UCD error conditions
+defaultMonitors yes
+ # generate traps on linkUp/Down
+linkUpDownNotifications yes
+
+
+
+###############################################################################
+#
+# EXTENDING THE AGENT
+#
+
+#
+# Arbitrary extension commands
+#
+ extend test1 /bin/echo Hello, world!
+ extend-sh test2 echo Hello, world! ; echo Hi there ; exit 35
+#extend-sh test3 /bin/sh /tmp/shtest
+
+# Note that this last entry requires the script '/tmp/shtest' to be created first,
+# containing the same three shell commands, before the line is uncommented
+
+# Walk the NET-SNMP-EXTEND-MIB tables (nsExtendConfigTable, nsExtendOutput1Table
+# and nsExtendOutput2Table) to see the resulting output
+
+# Note that the "extend" directive supercedes the previous "exec" and "sh" directives
+# However, walking the UCD-SNMP-MIB::extTable should still returns the same output,
+# as well as the fuller results in the above tables.
+
+
+#
+# "Pass-through" MIB extension command
+#
+#pass .1.3.6.1.4.1.8072.2.255 /bin/sh PREFIX/local/passtest
+#pass .1.3.6.1.4.1.8072.2.255 /usr/bin/perl PREFIX/local/passtest.pl
+
+# Note that this requires one of the two 'passtest' scripts to be installed first,
+# before the appropriate line is uncommented.
+# These scripts can be found in the 'local' directory of the source distribution,
+# and are not installed automatically.
+
+# Walk the NET-SNMP-PASS-MIB::netSnmpPassExamples subtree to see the resulting output
+
+
+#
+# AgentX Sub-agents
+#
+ # Run as an AgentX master agent
+ master agentx
+ # Listen for network connections (from localhost)
+ # rather than the default named socket /var/agentx/master
+#agentXSocket tcp:localhost:705
diff --git a/roles/snmp-cs/handlers/main.yml b/roles/snmp-cs/handlers/main.yml
new file mode 100644
index 0000000..9d9b583
--- /dev/null
+++ b/roles/snmp-cs/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart snmpd
+ service: name=snmpd state=restarted
diff --git a/roles/snmp-cs/tasks/main.yml b/roles/snmp-cs/tasks/main.yml
new file mode 100644
index 0000000..63a1fbf
--- /dev/null
+++ b/roles/snmp-cs/tasks/main.yml
@@ -0,0 +1,14 @@
+---
+
+- name: Installation snmpd
+ apt: name=snmpd state=present
+
+- name: Installation snmp
+ apt: name=snmp state=present
+
+- name: Copie du fichier snmpd.conf
+ copy: src=snmpd.conf dest=/etc/snmp/
+ notify:
+ - restart snmpd
+
+
diff --git a/roles/squid/files/squid.s-adm.conf b/roles/squid/files/squid.s-adm.conf
new file mode 100644
index 0000000..af62dd5
--- /dev/null
+++ b/roles/squid/files/squid.s-adm.conf
@@ -0,0 +1,7961 @@
+# WELCOME TO SQUID 3.5.23
+# ----------------------------
+#
+# This is the documentation for the Squid configuration file.
+# This documentation can also be found online at:
+# http://www.squid-cache.org/Doc/config/
+#
+# You may wish to look at the Squid home page and wiki for the
+# FAQ and other documentation:
+# http://www.squid-cache.org/
+# http://wiki.squid-cache.org/SquidFaq
+# http://wiki.squid-cache.org/ConfigExamples
+#
+# This documentation shows what the defaults for various directives
+# happen to be. If you don't need to change the default, you should
+# leave the line out of your squid.conf in most cases.
+#
+# In some cases "none" refers to no default setting at all,
+# while in other cases it refers to the value of the option
+# - the comments for that keyword indicate if this is the case.
+#
+
+# Configuration options can be included using the "include" directive.
+# Include takes a list of files to include. Quoting and wildcards are
+# supported.
+#
+# For example,
+#
+# include /path/to/included/file/squid.acl.config
+#
+# Includes can be nested up to a hard-coded depth of 16 levels.
+# This arbitrary restriction is to prevent recursive include references
+# from causing Squid entering an infinite loop whilst trying to load
+# configuration files.
+#
+# Values with byte units
+#
+# Squid accepts size units on some size related directives. All
+# such directives are documented with a default value displaying
+# a unit.
+#
+# Units accepted by Squid are:
+# bytes - byte
+# KB - Kilobyte (1024 bytes)
+# MB - Megabyte
+# GB - Gigabyte
+#
+# Values with spaces, quotes, and other special characters
+#
+# Squid supports directive parameters with spaces, quotes, and other
+# special characters. Surround such parameters with "double quotes". Use
+# the configuration_includes_quoted_values directive to enable or
+# disable that support.
+#
+# Squid supports reading configuration option parameters from external
+# files using the syntax:
+# parameters("/path/filename")
+# For example:
+# acl whitelist dstdomain parameters("/etc/squid/whitelist.txt")
+#
+# Conditional configuration
+#
+# If-statements can be used to make configuration directives
+# depend on conditions:
+#
+# if <CONDITION>
+# ... regular configuration directives ...
+# [else
+# ... regular configuration directives ...]
+# endif
+#
+# The else part is optional. The keywords "if", "else", and "endif"
+# must be typed on their own lines, as if they were regular
+# configuration directives.
+#
+# NOTE: An else-if condition is not supported.
+#
+# These individual conditions types are supported:
+#
+# true
+# Always evaluates to true.
+# false
+# Always evaluates to false.
+# <integer> = <integer>
+# Equality comparison of two integer numbers.
+#
+#
+# SMP-Related Macros
+#
+# The following SMP-related preprocessor macros can be used.
+#
+# ${process_name} expands to the current Squid process "name"
+# (e.g., squid1, squid2, or cache1).
+#
+# ${process_number} expands to the current Squid process
+# identifier, which is an integer number (e.g., 1, 2, 3) unique
+# across all Squid processes of the current service instance.
+#
+# ${service_name} expands into the current Squid service instance
+# name identifier which is provided by -n on the command line.
+#
+
+# TAG: broken_vary_encoding
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: cache_vary
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: error_map
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: external_refresh_check
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: location_rewrite_program
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: refresh_stale_hit
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: hierarchy_stoplist
+# Remove this line. Use always_direct or cache_peer_access ACLs instead if you need to prevent cache_peer use.
+#Default:
+# none
+
+# TAG: log_access
+# Remove this line. Use acls with access_log directives to control access logging
+#Default:
+# none
+
+# TAG: log_icap
+# Remove this line. Use acls with icap_log directives to control icap logging
+#Default:
+# none
+
+# TAG: ignore_ims_on_miss
+# Remove this line. The HTTP/1.1 feature is now configured by 'cache_miss_revalidate'.
+#Default:
+# none
+
+# TAG: chunked_request_body_max_size
+# Remove this line. Squid is now HTTP/1.1 compliant.
+#Default:
+# none
+
+# TAG: dns_v4_fallback
+# Remove this line. Squid performs a 'Happy Eyeballs' algorithm, the 'fallback' algorithm is no longer relevant.
+#Default:
+# none
+
+# TAG: emulate_httpd_log
+# Replace this with an access_log directive using the format 'common' or 'combined'.
+#Default:
+# none
+
+# TAG: forward_log
+# Use a regular access.log with ACL limiting it to MISS events.
+#Default:
+# none
+
+# TAG: ftp_list_width
+# Remove this line. Configure FTP page display using the CSS controls in errorpages.css instead.
+#Default:
+# none
+
+# TAG: ignore_expect_100
+# Remove this line. The HTTP/1.1 feature is now fully supported by default.
+#Default:
+# none
+
+# TAG: log_fqdn
+# Remove this option from your config. To log FQDN use %>A in the log format.
+#Default:
+# none
+
+# TAG: log_ip_on_direct
+# Remove this option from your config. To log server or peer names use %<A in the log format.
+#Default:
+# none
+
+# TAG: maximum_single_addr_tries
+# Replaced by connect_retries. The behaviour has changed, please read the documentation before altering.
+#Default:
+# none
+
+# TAG: referer_log
+# Replace this with an access_log directive using the format 'referrer'.
+#Default:
+# none
+
+# TAG: update_headers
+# Remove this line. The feature is supported by default in storage types where update is implemented.
+#Default:
+# none
+
+# TAG: url_rewrite_concurrency
+# Remove this line. Set the 'concurrency=' option of url_rewrite_children instead.
+#Default:
+# none
+
+# TAG: useragent_log
+# Replace this with an access_log directive using the format 'useragent'.
+#Default:
+# none
+
+# TAG: dns_testnames
+# Remove this line. DNS is no longer tested on startup.
+#Default:
+# none
+
+# TAG: extension_methods
+# Remove this line. All valid methods for HTTP are accepted by default.
+#Default:
+# none
+
+# TAG: zero_buffers
+#Default:
+# none
+
+# TAG: incoming_rate
+#Default:
+# none
+
+# TAG: server_http11
+# Remove this line. HTTP/1.1 is supported by default.
+#Default:
+# none
+
+# TAG: upgrade_http0.9
+# Remove this line. ICY/1.0 streaming protocol is supported by default.
+#Default:
+# none
+
+# TAG: zph_local
+# Alter these entries. Use the qos_flows directive instead.
+#Default:
+# none
+
+# TAG: header_access
+# Since squid-3.0 replace with request_header_access or reply_header_access
+# depending on whether you wish to match client requests or server replies.
+#Default:
+# none
+
+# TAG: httpd_accel_no_pmtu_disc
+# Since squid-3.0 use the 'disable-pmtu-discovery' flag on http_port instead.
+#Default:
+# none
+
+# TAG: wais_relay_host
+# Replace this line with 'cache_peer' configuration.
+#Default:
+# none
+
+# TAG: wais_relay_port
+# Replace this line with 'cache_peer' configuration.
+#Default:
+# none
+
+# OPTIONS FOR SMP
+# -----------------------------------------------------------------------------
+
+# TAG: workers
+# Number of main Squid processes or "workers" to fork and maintain.
+# 0: "no daemon" mode, like running "squid -N ..."
+# 1: "no SMP" mode, start one main Squid process daemon (default)
+# N: start N main Squid process daemons (i.e., SMP mode)
+#
+# In SMP mode, each worker does nearly all what a single Squid daemon
+# does (e.g., listen on http_port and forward HTTP requests).
+#Default:
+# SMP support disabled.
+
+# TAG: cpu_affinity_map
+# Usage: cpu_affinity_map process_numbers=P1,P2,... cores=C1,C2,...
+#
+# Sets 1:1 mapping between Squid processes and CPU cores. For example,
+#
+# cpu_affinity_map process_numbers=1,2,3,4 cores=1,3,5,7
+#
+# affects processes 1 through 4 only and places them on the first
+# four even cores, starting with core #1.
+#
+# CPU cores are numbered starting from 1. Requires support for
+# sched_getaffinity(2) and sched_setaffinity(2) system calls.
+#
+# Multiple cpu_affinity_map options are merged.
+#
+# See also: workers
+#Default:
+# Let operating system decide.
+
+# OPTIONS FOR AUTHENTICATION
+# -----------------------------------------------------------------------------
+
+# TAG: auth_param
+# This is used to define parameters for the various authentication
+# schemes supported by Squid.
+#
+# format: auth_param scheme parameter [setting]
+#
+# The order in which authentication schemes are presented to the client is
+# dependent on the order the scheme first appears in config file. IE
+# has a bug (it's not RFC 2617 compliant) in that it will use the basic
+# scheme if basic is the first entry presented, even if more secure
+# schemes are presented. For now use the order in the recommended
+# settings section below. If other browsers have difficulties (don't
+# recognize the schemes offered even if you are using basic) either
+# put basic first, or disable the other schemes (by commenting out their
+# program entry).
+#
+# Once an authentication scheme is fully configured, it can only be
+# shutdown by shutting squid down and restarting. Changes can be made on
+# the fly and activated with a reconfigure. I.E. You can change to a
+# different helper, but not unconfigure the helper completely.
+#
+# Please note that while this directive defines how Squid processes
+# authentication it does not automatically activate authentication.
+# To use authentication you must in addition make use of ACLs based
+# on login name in http_access (proxy_auth, proxy_auth_regex or
+# external with %LOGIN used in the format tag). The browser will be
+# challenged for authentication on the first such acl encountered
+# in http_access processing and will also be re-challenged for new
+# login credentials if the request is being denied by a proxy_auth
+# type acl.
+#
+# WARNING: authentication can't be used in a transparently intercepting
+# proxy as the client then thinks it is talking to an origin server and
+# not the proxy. This is a limitation of bending the TCP/IP protocol to
+# transparently intercepting port 80, not a limitation in Squid.
+# Ports flagged 'transparent', 'intercept', or 'tproxy' have
+# authentication disabled.
+#
+# === Parameters common to all schemes. ===
+#
+# "program" cmdline
+# Specifies the command for the external authenticator.
+#
+# By default, each authentication scheme is not used unless a
+# program is specified.
+#
+# See http://wiki.squid-cache.org/Features/AddonHelpers for
+# more details on helper operations and creating your own.
+#
+# "key_extras" format
+# Specifies a string to be append to request line format for
+# the authentication helper. "Quoted" format values may contain
+# spaces and logformat %macros. In theory, any logformat %macro
+# can be used. In practice, a %macro expands as a dash (-) if
+# the helper request is sent before the required macro
+# information is available to Squid.
+#
+# By default, Squid uses request formats provided in
+# scheme-specific examples below (search for %credentials).
+#
+# The expanded key_extras value is added to the Squid credentials
+# cache and, hence, will affect authentication. It can be used to
+# autenticate different users with identical user names (e.g.,
+# when user authentication depends on http_port).
+#
+# Avoid adding frequently changing information to key_extras. For
+# example, if you add user source IP, and it changes frequently
+# in your environment, then max_user_ip ACL is going to treat
+# every user+IP combination as a unique "user", breaking the ACL
+# and wasting a lot of memory on those user records. It will also
+# force users to authenticate from scratch whenever their IP
+# changes.
+#
+# "realm" string
+# Specifies the protection scope (aka realm name) which is to be
+# reported to the client for the authentication scheme. It is
+# commonly part of the text the user will see when prompted for
+# their username and password.
+#
+# For Basic the default is "Squid proxy-caching web server".
+# For Digest there is no default, this parameter is mandatory.
+# For NTLM and Negotiate this parameter is ignored.
+#
+# "children" numberofchildren [startup=N] [idle=N] [concurrency=N]
+#
+# The maximum number of authenticator processes to spawn. If
+# you start too few Squid will have to wait for them to process
+# a backlog of credential verifications, slowing it down. When
+# password verifications are done via a (slow) network you are
+# likely to need lots of authenticator processes.
+#
+# The startup= and idle= options permit some skew in the exact
+# amount run. A minimum of startup=N will begin during startup
+# and reconfigure. Squid will start more in groups of up to
+# idle=N in an attempt to meet traffic needs and to keep idle=N
+# free above those traffic needs up to the maximum.
+#
+# The concurrency= option sets the number of concurrent requests
+# the helper can process. The default of 0 is used for helpers
+# who only supports one request at a time. Setting this to a
+# number greater than 0 changes the protocol used to include a
+# channel ID field first on the request/response line, allowing
+# multiple requests to be sent to the same helper in parallel
+# without waiting for the response.
+#
+# Concurrency must not be set unless it's known the helper
+# supports the input format with channel-ID fields.
+#
+# NOTE: NTLM and Negotiate schemes do not support concurrency
+# in the Squid code module even though some helpers can.
+#
+#
+#
+# === Example Configuration ===
+#
+# This configuration displays the recommended authentication scheme
+# order from most to least secure with recommended minimum configuration
+# settings for each scheme:
+#
+##auth_param negotiate program <uncomment and complete this line to activate>
+##auth_param negotiate children 20 startup=0 idle=1
+##auth_param negotiate keep_alive on
+##
+##auth_param digest program <uncomment and complete this line to activate>
+##auth_param digest children 20 startup=0 idle=1
+##auth_param digest realm Squid proxy-caching web server
+##auth_param digest nonce_garbage_interval 5 minutes
+##auth_param digest nonce_max_duration 30 minutes
+##auth_param digest nonce_max_count 50
+##
+##auth_param ntlm program <uncomment and complete this line to activate>
+##auth_param ntlm children 20 startup=0 idle=1
+##auth_param ntlm keep_alive on
+##
+##auth_param basic program <uncomment and complete this line>
+##auth_param basic children 5 startup=5 idle=1
+##auth_param basic realm Squid proxy-caching web server
+##auth_param basic credentialsttl 2 hours
+#Default:
+# none
+
+# TAG: authenticate_cache_garbage_interval
+# The time period between garbage collection across the username cache.
+# This is a trade-off between memory utilization (long intervals - say
+# 2 days) and CPU (short intervals - say 1 minute). Only change if you
+# have good reason to.
+#Default:
+# authenticate_cache_garbage_interval 1 hour
+
+# TAG: authenticate_ttl
+# The time a user & their credentials stay in the logged in
+# user cache since their last request. When the garbage
+# interval passes, all user credentials that have passed their
+# TTL are removed from memory.
+#Default:
+# authenticate_ttl 1 hour
+
+# TAG: authenticate_ip_ttl
+# If you use proxy authentication and the 'max_user_ip' ACL,
+# this directive controls how long Squid remembers the IP
+# addresses associated with each user. Use a small value
+# (e.g., 60 seconds) if your users might change addresses
+# quickly, as is the case with dialup. You might be safe
+# using a larger value (e.g., 2 hours) in a corporate LAN
+# environment with relatively static address assignments.
+#Default:
+# authenticate_ip_ttl 1 second
+
+# ACCESS CONTROLS
+# -----------------------------------------------------------------------------
+
+# TAG: external_acl_type
+# This option defines external acl classes using a helper program
+# to look up the status
+#
+# external_acl_type name [options] FORMAT.. /path/to/helper [helper arguments..]
+#
+# Options:
+#
+# ttl=n TTL in seconds for cached results (defaults to 3600
+# for 1 hour)
+#
+# negative_ttl=n
+# TTL for cached negative lookups (default same
+# as ttl)
+#
+# grace=n Percentage remaining of TTL where a refresh of a
+# cached entry should be initiated without needing to
+# wait for a new reply. (default is for no grace period)
+#
+# cache=n The maximum number of entries in the result cache. The
+# default limit is 262144 entries. Each cache entry usually
+# consumes at least 256 bytes. Squid currently does not remove
+# expired cache entries until the limit is reached, so a proxy
+# will sooner or later reach the limit. The expanded FORMAT
+# value is used as the cache key, so if the details in FORMAT
+# are highly variable, a larger cache may be needed to produce
+# reduction in helper load.
+#
+# children-max=n
+# Maximum number of acl helper processes spawned to service
+# external acl lookups of this type. (default 5)
+#
+# children-startup=n
+# Minimum number of acl helper processes to spawn during
+# startup and reconfigure to service external acl lookups
+# of this type. (default 0)
+#
+# children-idle=n
+# Number of acl helper processes to keep ahead of traffic
+# loads. Squid will spawn this many at once whenever load
+# rises above the capabilities of existing processes.
+# Up to the value of children-max. (default 1)
+#
+# concurrency=n concurrency level per process. Only used with helpers
+# capable of processing more than one query at a time.
+#
+# protocol=2.5 Compatibility mode for Squid-2.5 external acl helpers.
+#
+# ipv4 / ipv6 IP protocol used to communicate with this helper.
+# The default is to auto-detect IPv6 and use it when available.
+#
+#
+# FORMAT specifications
+#
+# %LOGIN Authenticated user login name
+# %un A user name. Expands to the first available name
+# from the following list of information sources:
+# - authenticated user name, like %ul or %LOGIN
+# - user name sent by an external ACL, like %EXT_USER
+# - SSL client name, like %us in logformat
+# - ident user name, like %ui in logformat
+# %EXT_USER Username from previous external acl
+# %EXT_LOG Log details from previous external acl
+# %EXT_TAG Tag from previous external acl
+# %IDENT Ident user name
+# %SRC Client IP
+# %SRCPORT Client source port
+# %URI Requested URI
+# %DST Requested host
+# %PROTO Requested URL scheme
+# %PORT Requested port
+# %PATH Requested URL path
+# %METHOD Request method
+# %MYADDR Squid interface address
+# %MYPORT Squid http_port number
+# %PATH Requested URL-path (including query-string if any)
+# %USER_CERT SSL User certificate in PEM format
+# %USER_CERTCHAIN SSL User certificate chain in PEM format
+# %USER_CERT_xx SSL User certificate subject attribute xx
+# %USER_CA_CERT_xx SSL User certificate issuer attribute xx
+# %ssl::>sni SSL client SNI sent to Squid
+# %ssl::<cert_subject SSL server certificate DN
+# %ssl::<cert_issuer SSL server certificate issuer DN
+#
+# %>{Header} HTTP request header "Header"
+# %>{Hdr:member}
+# HTTP request header "Hdr" list member "member"
+# %>{Hdr:;member}
+# HTTP request header list member using ; as
+# list separator. ; can be any non-alphanumeric
+# character.
+#
+# %<{Header} HTTP reply header "Header"
+# %<{Hdr:member}
+# HTTP reply header "Hdr" list member "member"
+# %<{Hdr:;member}
+# HTTP reply header list member using ; as
+# list separator. ; can be any non-alphanumeric
+# character.
+#
+# %ACL The name of the ACL being tested.
+# %DATA The ACL arguments. If not used then any arguments
+# is automatically added at the end of the line
+# sent to the helper.
+# NOTE: this will encode the arguments as one token,
+# whereas the default will pass each separately.
+#
+# %% The percent sign. Useful for helpers which need
+# an unchanging input format.
+#
+#
+# General request syntax:
+#
+# [channel-ID] FORMAT-values [acl-values ...]
+#
+#
+# FORMAT-values consists of transaction details expanded with
+# whitespace separation per the config file FORMAT specification
+# using the FORMAT macros listed above.
+#
+# acl-values consists of any string specified in the referencing
+# config 'acl ... external' line. see the "acl external" directive.
+#
+# Request values sent to the helper are URL escaped to protect
+# each value in requests against whitespaces.
+#
+# If using protocol=2.5 then the request sent to the helper is not
+# URL escaped to protect against whitespace.
+#
+# NOTE: protocol=3.0 is deprecated as no longer necessary.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+#
+# The helper receives lines expanded per the above format specification
+# and for each input line returns 1 line starting with OK/ERR/BH result
+# code and optionally followed by additional keywords with more details.
+#
+#
+# General result syntax:
+#
+# [channel-ID] result keyword=value ...
+#
+# Result consists of one of the codes:
+#
+# OK
+# the ACL test produced a match.
+#
+# ERR
+# the ACL test does not produce a match.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified.
+#
+# The meaning of 'a match' is determined by your squid.conf
+# access control configuration. See the Squid wiki for details.
+#
+# Defined keywords:
+#
+# user= The users name (login)
+#
+# password= The users password (for login= cache_peer option)
+#
+# message= Message describing the reason for this response.
+# Available as %o in error pages.
+# Useful on (ERR and BH results).
+#
+# tag= Apply a tag to a request. Only sets a tag once,
+# does not alter existing tags.
+#
+# log= String to be logged in access.log. Available as
+# %ea in logformat specifications.
+#
+# clt_conn_tag= Associates a TAG with the client TCP connection.
+# Please see url_rewrite_program related documentation
+# for this kv-pair.
+#
+# Any keywords may be sent on any response whether OK, ERR or BH.
+#
+# All response keyword values need to be a single token with URL
+# escaping, or enclosed in double quotes (") and escaped using \ on
+# any double quotes or \ characters within the value. The wrapping
+# double quotes are removed before the value is interpreted by Squid.
+# \r and \n are also replace by CR and LF.
+#
+# Some example key values:
+#
+# user=John%20Smith
+# user="John Smith"
+# user="J. \"Bob\" Smith"
+#Default:
+# none
+
+# TAG: acl
+# Defining an Access List
+#
+# Every access list definition must begin with an aclname and acltype,
+# followed by either type-specific arguments or a quoted filename that
+# they are read from.
+#
+# acl aclname acltype argument ...
+# acl aclname acltype "file" ...
+#
+# When using "file", the file should contain one item per line.
+#
+# Some acl types supports options which changes their default behaviour.
+# The available options are:
+#
+# -i,+i By default, regular expressions are CASE-SENSITIVE. To make them
+# case-insensitive, use the -i option. To return case-sensitive
+# use the +i option between patterns, or make a new ACL line
+# without -i.
+#
+# -n Disable lookups and address type conversions. If lookup or
+# conversion is required because the parameter type (IP or
+# domain name) does not match the message address type (domain
+# name or IP), then the ACL would immediately declare a mismatch
+# without any warnings or lookups.
+#
+# -- Used to stop processing all options, in the case the first acl
+# value has '-' character as first character (for example the '-'
+# is a valid domain name)
+#
+# Some acl types require suspending the current request in order
+# to access some external data source.
+# Those which do are marked with the tag [slow], those which
+# don't are marked as [fast].
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl
+# for further information
+#
+# ***** ACL TYPES AVAILABLE *****
+#
+# acl aclname src ip-address/mask ... # clients IP address [fast]
+# acl aclname src addr1-addr2/mask ... # range of addresses [fast]
+# acl aclname dst [-n] ip-address/mask ... # URL host's IP address [slow]
+# acl aclname localip ip-address/mask ... # IP address the client connected to [fast]
+#
+# acl aclname arp mac-address ... (xx:xx:xx:xx:xx:xx notation)
+# # [fast]
+# # The 'arp' ACL code is not portable to all operating systems.
+# # It works on Linux, Solaris, Windows, FreeBSD, and some other
+# # BSD variants.
+# #
+# # NOTE: Squid can only determine the MAC/EUI address for IPv4
+# # clients that are on the same subnet. If the client is on a
+# # different subnet, then Squid cannot find out its address.
+# #
+# # NOTE 2: IPv6 protocol does not contain ARP. MAC/EUI is either
+# # encoded directly in the IPv6 address or not available.
+#
+# acl aclname srcdomain .foo.com ...
+# # reverse lookup, from client IP [slow]
+# acl aclname dstdomain [-n] .foo.com ...
+# # Destination server from URL [fast]
+# acl aclname srcdom_regex [-i] \.foo\.com ...
+# # regex matching client name [slow]
+# acl aclname dstdom_regex [-n] [-i] \.foo\.com ...
+# # regex matching server [fast]
+# #
+# # For dstdomain and dstdom_regex a reverse lookup is tried if a IP
+# # based URL is used and no match is found. The name "none" is used
+# # if the reverse lookup fails.
+#
+# acl aclname src_as number ...
+# acl aclname dst_as number ...
+# # [fast]
+# # Except for access control, AS numbers can be used for
+# # routing of requests to specific caches. Here's an
+# # example for routing all requests for AS#1241 and only
+# # those to mycache.mydomain.net:
+# # acl asexample dst_as 1241
+# # cache_peer_access mycache.mydomain.net allow asexample
+# # cache_peer_access mycache_mydomain.net deny all
+#
+# acl aclname peername myPeer ...
+# # [fast]
+# # match against a named cache_peer entry
+# # set unique name= on cache_peer lines for reliable use.
+#
+# acl aclname time [day-abbrevs] [h1:m1-h2:m2]
+# # [fast]
+# # day-abbrevs:
+# # S - Sunday
+# # M - Monday
+# # T - Tuesday
+# # W - Wednesday
+# # H - Thursday
+# # F - Friday
+# # A - Saturday
+# # h1:m1 must be less than h2:m2
+#
+# acl aclname url_regex [-i] ^http:// ...
+# # regex matching on whole URL [fast]
+# acl aclname urllogin [-i] [^a-zA-Z0-9] ...
+# # regex matching on URL login field
+# acl aclname urlpath_regex [-i] \.gif$ ...
+# # regex matching on URL path [fast]
+#
+# acl aclname port 80 70 21 0-1024... # destination TCP port [fast]
+# # ranges are alloed
+# acl aclname localport 3128 ... # TCP port the client connected to [fast]
+# # NP: for interception mode this is usually '80'
+#
+# acl aclname myportname 3128 ... # *_port name [fast]
+#
+# acl aclname proto HTTP FTP ... # request protocol [fast]
+#
+# acl aclname method GET POST ... # HTTP request method [fast]
+#
+# acl aclname http_status 200 301 500- 400-403 ...
+# # status code in reply [fast]
+#
+# acl aclname browser [-i] regexp ...
+# # pattern match on User-Agent header (see also req_header below) [fast]
+#
+# acl aclname referer_regex [-i] regexp ...
+# # pattern match on Referer header [fast]
+# # Referer is highly unreliable, so use with care
+#
+# acl aclname ident username ...
+# acl aclname ident_regex [-i] pattern ...
+# # string match on ident output [slow]
+# # use REQUIRED to accept any non-null ident.
+#
+# acl aclname proxy_auth [-i] username ...
+# acl aclname proxy_auth_regex [-i] pattern ...
+# # perform http authentication challenge to the client and match against
+# # supplied credentials [slow]
+# #
+# # takes a list of allowed usernames.
+# # use REQUIRED to accept any valid username.
+# #
+# # Will use proxy authentication in forward-proxy scenarios, and plain
+# # http authenticaiton in reverse-proxy scenarios
+# #
+# # NOTE: when a Proxy-Authentication header is sent but it is not
+# # needed during ACL checking the username is NOT logged
+# # in access.log.
+# #
+# # NOTE: proxy_auth requires a EXTERNAL authentication program
+# # to check username/password combinations (see
+# # auth_param directive).
+# #
+# # NOTE: proxy_auth can't be used in a transparent/intercepting proxy
+# # as the browser needs to be configured for using a proxy in order
+# # to respond to proxy authentication.
+#
+# acl aclname snmp_community string ...
+# # A community string to limit access to your SNMP Agent [fast]
+# # Example:
+# #
+# # acl snmppublic snmp_community public
+#
+# acl aclname maxconn number
+# # This will be matched when the client's IP address has
+# # more than <number> TCP connections established. [fast]
+# # NOTE: This only measures direct TCP links so X-Forwarded-For
+# # indirect clients are not counted.
+#
+# acl aclname max_user_ip [-s] number
+# # This will be matched when the user attempts to log in from more
+# # than <number> different ip addresses. The authenticate_ip_ttl
+# # parameter controls the timeout on the ip entries. [fast]
+# # If -s is specified the limit is strict, denying browsing
+# # from any further IP addresses until the ttl has expired. Without
+# # -s Squid will just annoy the user by "randomly" denying requests.
+# # (the counter is reset each time the limit is reached and a
+# # request is denied)
+# # NOTE: in acceleration mode or where there is mesh of child proxies,
+# # clients may appear to come from multiple addresses if they are
+# # going through proxy farms, so a limit of 1 may cause user problems.
+#
+# acl aclname random probability
+# # Pseudo-randomly match requests. Based on the probability given.
+# # Probability may be written as a decimal (0.333), fraction (1/3)
+# # or ratio of matches:non-matches (3:5).
+#
+# acl aclname req_mime_type [-i] mime-type ...
+# # regex match against the mime type of the request generated
+# # by the client. Can be used to detect file upload or some
+# # types HTTP tunneling requests [fast]
+# # NOTE: This does NOT match the reply. You cannot use this
+# # to match the returned file type.
+#
+# acl aclname req_header header-name [-i] any\.regex\.here
+# # regex match against any of the known request headers. May be
+# # thought of as a superset of "browser", "referer" and "mime-type"
+# # ACL [fast]
+#
+# acl aclname rep_mime_type [-i] mime-type ...
+# # regex match against the mime type of the reply received by
+# # squid. Can be used to detect file download or some
+# # types HTTP tunneling requests. [fast]
+# # NOTE: This has no effect in http_access rules. It only has
+# # effect in rules that affect the reply data stream such as
+# # http_reply_access.
+#
+# acl aclname rep_header header-name [-i] any\.regex\.here
+# # regex match against any of the known reply headers. May be
+# # thought of as a superset of "browser", "referer" and "mime-type"
+# # ACLs [fast]
+#
+# acl aclname external class_name [arguments...]
+# # external ACL lookup via a helper class defined by the
+# # external_acl_type directive [slow]
+#
+# acl aclname user_cert attribute values...
+# # match against attributes in a user SSL certificate
+# # attribute is one of DN/C/O/CN/L/ST or a numerical OID [fast]
+#
+# acl aclname ca_cert attribute values...
+# # match against attributes a users issuing CA SSL certificate
+# # attribute is one of DN/C/O/CN/L/ST or a numerical OID [fast]
+#
+# acl aclname ext_user username ...
+# acl aclname ext_user_regex [-i] pattern ...
+# # string match on username returned by external acl helper [slow]
+# # use REQUIRED to accept any non-null user name.
+#
+# acl aclname tag tagvalue ...
+# # string match on tag returned by external acl helper [fast]
+# # DEPRECATED. Only the first tag will match with this ACL.
+# # Use the 'note' ACL instead for handling multiple tag values.
+#
+# acl aclname hier_code codename ...
+# # string match against squid hierarchy code(s); [fast]
+# # e.g., DIRECT, PARENT_HIT, NONE, etc.
+# #
+# # NOTE: This has no effect in http_access rules. It only has
+# # effect in rules that affect the reply data stream such as
+# # http_reply_access.
+#
+# acl aclname note name [value ...]
+# # match transaction annotation [fast]
+# # Without values, matches any annotation with a given name.
+# # With value(s), matches any annotation with a given name that
+# # also has one of the given values.
+# # Names and values are compared using a string equality test.
+# # Annotation sources include note and adaptation_meta directives
+# # as well as helper and eCAP responses.
+#
+# acl aclname adaptation_service service ...
+# # Matches the name of any icap_service, ecap_service,
+# # adaptation_service_set, or adaptation_service_chain that Squid
+# # has used (or attempted to use) for the master transaction.
+# # This ACL must be defined after the corresponding adaptation
+# # service is named in squid.conf. This ACL is usable with
+# # adaptation_meta because it starts matching immediately after
+# # the service has been selected for adaptation.
+#
+# acl aclname any-of acl1 acl2 ...
+# # match any one of the acls [fast or slow]
+# # The first matching ACL stops further ACL evaluation.
+# #
+# # ACLs from multiple any-of lines with the same name are ORed.
+# # For example, A = (a1 or a2) or (a3 or a4) can be written as
+# # acl A any-of a1 a2
+# # acl A any-of a3 a4
+# #
+# # This group ACL is fast if all evaluated ACLs in the group are fast
+# # and slow otherwise.
+#
+# acl aclname all-of acl1 acl2 ...
+# # match all of the acls [fast or slow]
+# # The first mismatching ACL stops further ACL evaluation.
+# #
+# # ACLs from multiple all-of lines with the same name are ORed.
+# # For example, B = (b1 and b2) or (b3 and b4) can be written as
+# # acl B all-of b1 b2
+# # acl B all-of b3 b4
+# #
+# # This group ACL is fast if all evaluated ACLs in the group are fast
+# # and slow otherwise.
+#
+# Examples:
+# acl macaddress arp 09:00:2b:23:45:67
+# acl myexample dst_as 1241
+# acl password proxy_auth REQUIRED
+# acl fileupload req_mime_type -i ^multipart/form-data$
+# acl javascript rep_mime_type -i ^application/x-javascript$
+#
+#Default:
+# ACLs all, manager, localhost, and to_localhost are predefined.
+#
+#
+# Recommended minimum configuration:
+#
+
+# Example rule allowing access from your local networks.
+# Adapt to list your (internal) IP networks from where browsing
+# should be allowed
+#acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
+#acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
+acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
+#acl localnet src fc00::/7 # RFC 4193 local private network range
+#acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
+
+acl SSL_ports port 443
+acl Safe_ports port 80 # http
+acl Safe_ports port 21 # ftp
+acl Safe_ports port 443 # https
+acl Safe_ports port 70 # gopher
+acl Safe_ports port 210 # wais
+acl Safe_ports port 1025-65535 # unregistered ports
+acl Safe_ports port 280 # http-mgmt
+acl Safe_ports port 488 # gss-http
+acl Safe_ports port 591 # filemaker
+acl Safe_ports port 777 # multiling http
+acl CONNECT method CONNECT
+
+# TAG: proxy_protocol_access
+# Determine which client proxies can be trusted to provide correct
+# information regarding real client IP address using PROXY protocol.
+#
+# Requests may pass through a chain of several other proxies
+# before reaching us. The original source details may by sent in:
+# * HTTP message Forwarded header, or
+# * HTTP message X-Forwarded-For header, or
+# * PROXY protocol connection header.
+#
+# This directive is solely for validating new PROXY protocol
+# connections received from a port flagged with require-proxy-header.
+# It is checked only once after TCP connection setup.
+#
+# A deny match results in TCP connection closure.
+#
+# An allow match is required for Squid to permit the corresponding
+# TCP connection, before Squid even looks for HTTP request headers.
+# If there is an allow match, Squid starts using PROXY header information
+# to determine the source address of the connection for all future ACL
+# checks, logging, etc.
+#
+# SECURITY CONSIDERATIONS:
+#
+# Any host from which we accept client IP details can place
+# incorrect information in the relevant header, and Squid
+# will use the incorrect information as if it were the
+# source address of the request. This may enable remote
+# hosts to bypass any access control restrictions that are
+# based on the client's source addresses.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# all TCP connections to ports with require-proxy-header will be denied
+
+# TAG: follow_x_forwarded_for
+# Determine which client proxies can be trusted to provide correct
+# information regarding real client IP address.
+#
+# Requests may pass through a chain of several other proxies
+# before reaching us. The original source details may by sent in:
+# * HTTP message Forwarded header, or
+# * HTTP message X-Forwarded-For header, or
+# * PROXY protocol connection header.
+#
+# PROXY protocol connections are controlled by the proxy_protocol_access
+# directive which is checked before this.
+#
+# If a request reaches us from a source that is allowed by this
+# directive, then we trust the information it provides regarding
+# the IP of the client it received from (if any).
+#
+# For the purpose of ACLs used in this directive the src ACL type always
+# matches the address we are testing and srcdomain matches its rDNS.
+#
+# On each HTTP request Squid checks for X-Forwarded-For header fields.
+# If found the header values are iterated in reverse order and an allow
+# match is required for Squid to continue on to the next value.
+# The verification ends when a value receives a deny match, cannot be
+# tested, or there are no more values to test.
+# NOTE: Squid does not yet follow the Forwarded HTTP header.
+#
+# The end result of this process is an IP address that we will
+# refer to as the indirect client address. This address may
+# be treated as the client address for access control, ICAP, delay
+# pools and logging, depending on the acl_uses_indirect_client,
+# icap_uses_indirect_client, delay_pool_uses_indirect_client,
+# log_uses_indirect_client and tproxy_uses_indirect_client options.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# SECURITY CONSIDERATIONS:
+#
+# Any host from which we accept client IP details can place
+# incorrect information in the relevant header, and Squid
+# will use the incorrect information as if it were the
+# source address of the request. This may enable remote
+# hosts to bypass any access control restrictions that are
+# based on the client's source addresses.
+#
+# For example:
+#
+# acl localhost src 127.0.0.1
+# acl my_other_proxy srcdomain .proxy.example.com
+# follow_x_forwarded_for allow localhost
+# follow_x_forwarded_for allow my_other_proxy
+#Default:
+# X-Forwarded-For header will be ignored.
+
+# TAG: acl_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in acl matching.
+#
+# NOTE: maxconn ACL considers direct TCP links and indirect
+# clients will always have zero. So no match.
+#Default:
+# acl_uses_indirect_client on
+
+# TAG: delay_pool_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in delay pools.
+#Default:
+# delay_pool_uses_indirect_client on
+
+# TAG: log_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in the access log.
+#Default:
+# log_uses_indirect_client on
+
+# TAG: tproxy_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address when spoofing the outgoing client.
+#
+# This has no effect on requests arriving in non-tproxy
+# mode ports.
+#
+# SECURITY WARNING: Usage of this option is dangerous
+# and should not be used trivially. Correct configuration
+# of follow_x_forwarded_for with a limited set of trusted
+# sources is required to prevent abuse of your proxy.
+#Default:
+# tproxy_uses_indirect_client off
+
+# TAG: spoof_client_ip
+# Control client IP address spoofing of TPROXY traffic based on
+# defined access lists.
+#
+# spoof_client_ip allow|deny [!]aclname ...
+#
+# If there are no "spoof_client_ip" lines present, the default
+# is to "allow" spoofing of any suitable request.
+#
+# Note that the cache_peer "no-tproxy" option overrides this ACL.
+#
+# This clause supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow spoofing on all TPROXY traffic.
+
+# TAG: http_access
+# Allowing or Denying access based on defined access lists
+#
+# To allow or deny a message received on an HTTP, HTTPS, or FTP port:
+# http_access allow|deny [!]aclname ...
+#
+# NOTE on default values:
+#
+# If there are no "access" lines present, the default is to deny
+# the request.
+#
+# If none of the "access" lines cause a match, the default is the
+# opposite of the last line in the list. If the last line was
+# deny, the default is allow. Conversely, if the last line
+# is allow, the default will be deny. For these reasons, it is a
+# good idea to have an "deny all" entry at the end of your access
+# lists to avoid potential confusion.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Default:
+# Deny, unless rules exist in squid.conf.
+#
+
+#
+# Recommended minimum Access Permission configuration:
+#
+# Deny requests to certain unsafe ports
+http_access deny !Safe_ports
+
+# Deny CONNECT to other than secure SSL ports
+http_access deny CONNECT !SSL_ports
+
+# Only allow cachemgr access from localhost
+http_access allow localhost manager
+http_access deny manager
+
+# We strongly recommend the following be uncommented to protect innocent
+# web applications running on the proxy server who think the only
+# one who can access services on "localhost" is a local user
+#http_access deny to_localhost
+
+#
+# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
+#
+
+# Example rule allowing access from your local networks.
+# Adapt localnet in the ACL section to list your (internal) IP networks
+# from where browsing should be allowed
+#http_access allow localnet
+http_access allow localhost
+http_access allow localnet
+
+# And finally deny all other access to this proxy
+http_access deny all
+
+# TAG: adapted_http_access
+# Allowing or Denying access based on defined access lists
+#
+# Essentially identical to http_access, but runs after redirectors
+# and ICAP/eCAP adaptation. Allowing access control based on their
+# output.
+#
+# If not set then only http_access is used.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: http_reply_access
+# Allow replies to client requests. This is complementary to http_access.
+#
+# http_reply_access allow|deny [!] aclname ...
+#
+# NOTE: if there are no access lines present, the default is to allow
+# all replies.
+#
+# If none of the access lines cause a match the opposite of the
+# last line will apply. Thus it is good practice to end the rules
+# with an "allow all" or "deny all" entry.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: icp_access
+# Allowing or Denying access to the ICP port based on defined
+# access lists
+#
+# icp_access allow|deny [!]aclname ...
+#
+# NOTE: The default if no icp_access lines are present is to
+# deny all traffic. This default may cause problems with peers
+# using ICP.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow ICP queries from local networks only
+##icp_access allow localnet
+##icp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: htcp_access
+# Allowing or Denying access to the HTCP port based on defined
+# access lists
+#
+# htcp_access allow|deny [!]aclname ...
+#
+# See also htcp_clr_access for details on access control for
+# cache purge (CLR) HTCP messages.
+#
+# NOTE: The default if no htcp_access lines are present is to
+# deny all traffic. This default may cause problems with peers
+# using the htcp option.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow HTCP queries from local networks only
+##htcp_access allow localnet
+##htcp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: htcp_clr_access
+# Allowing or Denying access to purge content using HTCP based
+# on defined access lists.
+# See htcp_access for details on general HTCP access control.
+#
+# htcp_clr_access allow|deny [!]aclname ...
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow HTCP CLR requests from trusted peers
+#acl htcp_clr_peer src 192.0.2.2 2001:DB8::2
+#htcp_clr_access allow htcp_clr_peer
+#htcp_clr_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: miss_access
+# Determines whether network access is permitted when satisfying a request.
+#
+# For example;
+# to force your neighbors to use you as a sibling instead of
+# a parent.
+#
+# acl localclients src 192.0.2.0/24 2001:DB8::a:0/64
+# miss_access deny !localclients
+# miss_access allow all
+#
+# This means only your local clients are allowed to fetch relayed/MISS
+# replies from the network and all other clients can only fetch cached
+# objects (HITs).
+#
+# The default for this setting allows all clients who passed the
+# http_access rules to relay via this proxy.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: ident_lookup_access
+# A list of ACL elements which, if matched, cause an ident
+# (RFC 931) lookup to be performed for this request. For
+# example, you might choose to always perform ident lookups
+# for your main multi-user Unix boxes, but not for your Macs
+# and PCs. By default, ident lookups are not performed for
+# any requests.
+#
+# To enable ident lookups for specific client addresses, you
+# can follow this example:
+#
+# acl ident_aware_hosts src 198.168.1.0/24
+# ident_lookup_access allow ident_aware_hosts
+# ident_lookup_access deny all
+#
+# Only src type ACL checks are fully supported. A srcdomain
+# ACL might work at times, but it will not always provide
+# the correct result.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Unless rules exist in squid.conf, IDENT is not fetched.
+
+# TAG: reply_body_max_size size [acl acl...]
+# This option specifies the maximum size of a reply body. It can be
+# used to prevent users from downloading very large files, such as
+# MP3's and movies. When the reply headers are received, the
+# reply_body_max_size lines are processed, and the first line where
+# all (if any) listed ACLs are true is used as the maximum body size
+# for this reply.
+#
+# This size is checked twice. First when we get the reply headers,
+# we check the content-length value. If the content length value exists
+# and is larger than the allowed size, the request is denied and the
+# user receives an error message that says "the request or reply
+# is too large." If there is no content-length, and the reply
+# size exceeds this limit, the client's connection is just closed
+# and they will receive a partial reply.
+#
+# WARNING: downstream caches probably can not detect a partial reply
+# if there is no content-length header, so they will cache
+# partial responses and give them out as hits. You should NOT
+# use this option if you have downstream caches.
+#
+# WARNING: A maximum size smaller than the size of squid's error messages
+# will cause an infinite loop and crash squid. Ensure that the smallest
+# non-zero value you use is greater that the maximum header size plus
+# the size of your largest error page.
+#
+# If you set this parameter none (the default), there will be
+# no limit imposed.
+#
+# Configuration Format is:
+# reply_body_max_size SIZE UNITS [acl ...]
+# ie.
+# reply_body_max_size 10 MB
+#
+#Default:
+# No limit is applied.
+
+# NETWORK OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: http_port
+# Usage: port [mode] [options]
+# hostname:port [mode] [options]
+# 1.2.3.4:port [mode] [options]
+#
+# The socket addresses where Squid will listen for HTTP client
+# requests. You may specify multiple socket addresses.
+# There are three forms: port alone, hostname with port, and
+# IP address with port. If you specify a hostname or IP
+# address, Squid binds the socket to that specific
+# address. Most likely, you do not need to bind to a specific
+# address, so you can use the port number alone.
+#
+# If you are running Squid in accelerator mode, you
+# probably want to listen on port 80 also, or instead.
+#
+# The -a command line option may be used to specify additional
+# port(s) where Squid listens for proxy request. Such ports will
+# be plain proxy ports with no options.
+#
+# You may specify multiple socket addresses on multiple lines.
+#
+# Modes:
+#
+# intercept Support for IP-Layer NAT interception delivering
+# traffic to this Squid port.
+# NP: disables authentication on the port.
+#
+# tproxy Support Linux TPROXY (or BSD divert-to) with spoofing
+# of outgoing connections using the client IP address.
+# NP: disables authentication on the port.
+#
+# accel Accelerator / reverse proxy mode
+#
+# ssl-bump For each CONNECT request allowed by ssl_bump ACLs,
+# establish secure connection with the client and with
+# the server, decrypt HTTPS messages as they pass through
+# Squid, and treat them as unencrypted HTTP messages,
+# becoming the man-in-the-middle.
+#
+# The ssl_bump option is required to fully enable
+# bumping of CONNECT requests.
+#
+# Omitting the mode flag causes default forward proxy mode to be used.
+#
+#
+# Accelerator Mode Options:
+#
+# defaultsite=domainname
+# What to use for the Host: header if it is not present
+# in a request. Determines what site (not origin server)
+# accelerators should consider the default.
+#
+# no-vhost Disable using HTTP/1.1 Host header for virtual domain support.
+#
+# protocol= Protocol to reconstruct accelerated and intercepted
+# requests with. Defaults to HTTP/1.1 for http_port and
+# HTTPS/1.1 for https_port.
+# When an unsupported value is configured Squid will
+# produce a FATAL error.
+# Values: HTTP or HTTP/1.1, HTTPS or HTTPS/1.1
+#
+# vport Virtual host port support. Using the http_port number
+# instead of the port passed on Host: headers.
+#
+# vport=NN Virtual host port support. Using the specified port
+# number instead of the port passed on Host: headers.
+#
+# act-as-origin
+# Act as if this Squid is the origin server.
+# This currently means generate new Date: and Expires:
+# headers on HIT instead of adding Age:.
+#
+# ignore-cc Ignore request Cache-Control headers.
+#
+# WARNING: This option violates HTTP specifications if
+# used in non-accelerator setups.
+#
+# allow-direct Allow direct forwarding in accelerator mode. Normally
+# accelerated requests are denied direct forwarding as if
+# never_direct was used.
+#
+# WARNING: this option opens accelerator mode to security
+# vulnerabilities usually only affecting in interception
+# mode. Make sure to protect forwarding with suitable
+# http_access rules when using this.
+#
+#
+# SSL Bump Mode Options:
+# In addition to these options ssl-bump requires TLS/SSL options.
+#
+# generate-host-certificates[=<on|off>]
+# Dynamically create SSL server certificates for the
+# destination hosts of bumped CONNECT requests.When
+# enabled, the cert and key options are used to sign
+# generated certificates. Otherwise generated
+# certificate will be selfsigned.
+# If there is a CA certificate lifetime of the generated
+# certificate equals lifetime of the CA certificate. If
+# generated certificate is selfsigned lifetime is three
+# years.
+# This option is disabled by default. See the ssl-bump
+# option above for more information.
+#
+# dynamic_cert_mem_cache_size=SIZE
+# Approximate total RAM size spent on cached generated
+# certificates. If set to zero, caching is disabled.
+#
+# TLS / SSL Options:
+#
+# cert= Path to SSL certificate (PEM format).
+#
+# key= Path to SSL private key file (PEM format)
+# if not specified, the certificate file is
+# assumed to be a combined certificate and
+# key file.
+#
+# version= The version of SSL/TLS supported
+# 1 automatic (default)
+# 2 SSLv2 only
+# 3 SSLv3 only
+# 4 TLSv1.0 only
+# 5 TLSv1.1 only
+# 6 TLSv1.2 only
+#
+# cipher= Colon separated list of supported ciphers.
+# NOTE: some ciphers such as EDH ciphers depend on
+# additional settings. If those settings are
+# omitted the ciphers may be silently ignored
+# by the OpenSSL library.
+#
+# options= Various SSL implementation options. The most important
+# being:
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1.0
+# NO_TLSv1_1 Disallow the use of TLSv1.1
+# NO_TLSv1_2 Disallow the use of TLSv1.2
+# SINGLE_DH_USE Always create a new key when using
+# temporary/ephemeral DH key exchanges
+# NO_TICKET Disables TLS tickets extension
+#
+# SINGLE_ECDH_USE
+# Enable ephemeral ECDH key exchange.
+# The adopted curve should be specified
+# using the tls-dh option.
+#
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+# See OpenSSL SSL_CTX_set_options documentation for a
+# complete list of options.
+#
+# clientca= File containing the list of CAs to use when
+# requesting a client certificate.
+#
+# cafile= File containing additional CA certificates to
+# use when verifying client certificates. If unset
+# clientca will be used.
+#
+# capath= Directory containing additional CA certificates
+# and CRL lists to use when verifying client certificates.
+#
+# crlfile= File of additional CRL lists to use when verifying
+# the client certificate, in addition to CRLs stored in
+# the capath. Implies VERIFY_CRL flag below.
+#
+# tls-dh=[curve:]file
+# File containing DH parameters for temporary/ephemeral DH key
+# exchanges, optionally prefixed by a curve for ephemeral ECDH
+# key exchanges.
+# See OpenSSL documentation for details on how to create the
+# DH parameter file. Supported curves for ECDH can be listed
+# using the "openssl ecparam -list_curves" command.
+# WARNING: EDH and EECDH ciphers will be silently disabled if
+# this option is not set.
+#
+# sslflags= Various flags modifying the use of SSL:
+# DELAYED_AUTH
+# Don't request client certificates
+# immediately, but wait until acl processing
+# requires a certificate (not yet implemented).
+# NO_DEFAULT_CA
+# Don't use the default CA lists built in
+# to OpenSSL.
+# NO_SESSION_REUSE
+# Don't allow for session reuse. Each connection
+# will result in a new SSL session.
+# VERIFY_CRL
+# Verify CRL lists when accepting client
+# certificates.
+# VERIFY_CRL_ALL
+# Verify CRL lists for all certificates in the
+# client certificate chain.
+#
+# sslcontext= SSL session ID context identifier.
+#
+# Other Options:
+#
+# connection-auth[=on|off]
+# use connection-auth=off to tell Squid to prevent
+# forwarding Microsoft connection oriented authentication
+# (NTLM, Negotiate and Kerberos)
+#
+# disable-pmtu-discovery=
+# Control Path-MTU discovery usage:
+# off lets OS decide on what to do (default).
+# transparent disable PMTU discovery when transparent
+# support is enabled.
+# always disable always PMTU discovery.
+#
+# In many setups of transparently intercepting proxies
+# Path-MTU discovery can not work on traffic towards the
+# clients. This is the case when the intercepting device
+# does not fully track connections and fails to forward
+# ICMP must fragment messages to the cache server. If you
+# have such setup and experience that certain clients
+# sporadically hang or never complete requests set
+# disable-pmtu-discovery option to 'transparent'.
+#
+# name= Specifies a internal name for the port. Defaults to
+# the port specification (port or addr:port)
+#
+# tcpkeepalive[=idle,interval,timeout]
+# Enable TCP keepalive probes of idle connections.
+# In seconds; idle is the initial time before TCP starts
+# probing the connection, interval how often to probe, and
+# timeout the time before giving up.
+#
+# require-proxy-header
+# Require PROXY protocol version 1 or 2 connections.
+# The proxy_protocol_access is required to whitelist
+# downstream proxies which can be trusted.
+#
+# If you run Squid on a dual-homed machine with an internal
+# and an external interface we recommend you to specify the
+# internal address:port in http_port. This way Squid will only be
+# visible on the internal address.
+#
+#
+
+# Squid normally listens to port 3128
+#http_port 3128
+http_port 8080
+
+# TAG: https_port
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Usage: [ip:]port cert=certificate.pem [key=key.pem] [mode] [options...]
+#
+# The socket address where Squid will listen for client requests made
+# over TLS or SSL connections. Commonly referred to as HTTPS.
+#
+# This is most useful for situations where you are running squid in
+# accelerator mode and you want to do the SSL work at the accelerator level.
+#
+# You may specify multiple socket addresses on multiple lines,
+# each with their own SSL certificate and/or options.
+#
+# Modes:
+#
+# accel Accelerator / reverse proxy mode
+#
+# intercept Support for IP-Layer interception of
+# outgoing requests without browser settings.
+# NP: disables authentication and IPv6 on the port.
+#
+# tproxy Support Linux TPROXY for spoofing outgoing
+# connections using the client IP address.
+# NP: disables authentication and maybe IPv6 on the port.
+#
+# ssl-bump For each intercepted connection allowed by ssl_bump
+# ACLs, establish a secure connection with the client and with
+# the server, decrypt HTTPS messages as they pass through
+# Squid, and treat them as unencrypted HTTP messages,
+# becoming the man-in-the-middle.
+#
+# An "ssl_bump server-first" match is required to
+# fully enable bumping of intercepted SSL connections.
+#
+# Requires tproxy or intercept.
+#
+# Omitting the mode flag causes default forward proxy mode to be used.
+#
+#
+# See http_port for a list of generic options
+#
+#
+# SSL Options:
+#
+# cert= Path to SSL certificate (PEM format).
+#
+# key= Path to SSL private key file (PEM format)
+# if not specified, the certificate file is
+# assumed to be a combined certificate and
+# key file.
+#
+# version= The version of SSL/TLS supported
+# 1 automatic (default)
+# 2 SSLv2 only
+# 3 SSLv3 only
+# 4 TLSv1 only
+#
+# cipher= Colon separated list of supported ciphers.
+#
+# options= Various SSL engine options. The most important
+# being:
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1
+#
+# SINGLE_DH_USE Always create a new key when using
+# temporary/ephemeral DH key exchanges
+#
+# SINGLE_ECDH_USE
+# Enable ephemeral ECDH key exchange.
+# The adopted curve should be specified
+# using the tls-dh option.
+#
+# See src/ssl_support.c or OpenSSL SSL_CTX_set_options
+# documentation for a complete list of options.
+#
+# clientca= File containing the list of CAs to use when
+# requesting a client certificate.
+#
+# cafile= File containing additional CA certificates to
+# use when verifying client certificates. If unset
+# clientca will be used.
+#
+# capath= Directory containing additional CA certificates
+# and CRL lists to use when verifying client certificates.
+#
+# crlfile= File of additional CRL lists to use when verifying
+# the client certificate, in addition to CRLs stored in
+# the capath. Implies VERIFY_CRL flag below.
+#
+# tls-dh=[curve:]file
+# File containing DH parameters for temporary/ephemeral DH key
+# exchanges, optionally prefixed by a curve for ephemeral ECDH
+# key exchanges.
+#
+# sslflags= Various flags modifying the use of SSL:
+# DELAYED_AUTH
+# Don't request client certificates
+# immediately, but wait until acl processing
+# requires a certificate (not yet implemented).
+# NO_DEFAULT_CA
+# Don't use the default CA lists built in
+# to OpenSSL.
+# NO_SESSION_REUSE
+# Don't allow for session reuse. Each connection
+# will result in a new SSL session.
+# VERIFY_CRL
+# Verify CRL lists when accepting client
+# certificates.
+# VERIFY_CRL_ALL
+# Verify CRL lists for all certificates in the
+# client certificate chain.
+#
+# sslcontext= SSL session ID context identifier.
+#
+# generate-host-certificates[=<on|off>]
+# Dynamically create SSL server certificates for the
+# destination hosts of bumped SSL requests.When
+# enabled, the cert and key options are used to sign
+# generated certificates. Otherwise generated
+# certificate will be selfsigned.
+# If there is CA certificate life time of generated
+# certificate equals lifetime of CA certificate. If
+# generated certificate is selfsigned lifetime is three
+# years.
+# This option is disabled by default. See the ssl-bump
+# option above for more information.
+#
+# dynamic_cert_mem_cache_size=SIZE
+# Approximate total RAM size spent on cached generated
+# certificates. If set to zero, caching is disabled.
+#
+# See http_port for a list of available options.
+#Default:
+# none
+
+# TAG: ftp_port
+# Enables Native FTP proxy by specifying the socket address where Squid
+# listens for FTP client requests. See http_port directive for various
+# ways to specify the listening address and mode.
+#
+# Usage: ftp_port address [mode] [options]
+#
+# WARNING: This is a new, experimental, complex feature that has seen
+# limited production exposure. Some Squid modules (e.g., caching) do not
+# currently work with native FTP proxying, and many features have not
+# even been tested for compatibility. Test well before deploying!
+#
+# Native FTP proxying differs substantially from proxying HTTP requests
+# with ftp:// URIs because Squid works as an FTP server and receives
+# actual FTP commands (rather than HTTP requests with FTP URLs).
+#
+# Native FTP commands accepted at ftp_port are internally converted or
+# wrapped into HTTP-like messages. The same happens to Native FTP
+# responses received from FTP origin servers. Those HTTP-like messages
+# are shoveled through regular access control and adaptation layers
+# between the FTP client and the FTP origin server. This allows Squid to
+# examine, adapt, block, and log FTP exchanges. Squid reuses most HTTP
+# mechanisms when shoveling wrapped FTP messages. For example,
+# http_access and adaptation_access directives are used.
+#
+# Modes:
+#
+# intercept Same as http_port intercept. The FTP origin address is
+# determined based on the intended destination of the
+# intercepted connection.
+#
+# tproxy Support Linux TPROXY for spoofing outgoing
+# connections using the client IP address.
+# NP: disables authentication and maybe IPv6 on the port.
+#
+# By default (i.e., without an explicit mode option), Squid extracts the
+# FTP origin address from the login@origin parameter of the FTP USER
+# command. Many popular FTP clients support such native FTP proxying.
+#
+# Options:
+#
+# name=token Specifies an internal name for the port. Defaults to
+# the port address. Usable with myportname ACL.
+#
+# ftp-track-dirs
+# Enables tracking of FTP directories by injecting extra
+# PWD commands and adjusting Request-URI (in wrapping
+# HTTP requests) to reflect the current FTP server
+# directory. Tracking is disabled by default.
+#
+# protocol=FTP Protocol to reconstruct accelerated and intercepted
+# requests with. Defaults to FTP. No other accepted
+# values have been tested with. An unsupported value
+# results in a FATAL error. Accepted values are FTP,
+# HTTP (or HTTP/1.1), and HTTPS (or HTTPS/1.1).
+#
+# Other http_port modes and options that are not specific to HTTP and
+# HTTPS may also work.
+#Default:
+# none
+
+# TAG: tcp_outgoing_tos
+# Allows you to select a TOS/Diffserv value for packets outgoing
+# on the server side, based on an ACL.
+#
+# tcp_outgoing_tos ds-field [!]aclname ...
+#
+# Example where normal_service_net uses the TOS value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# tcp_outgoing_tos 0x00 normal_service_net
+# tcp_outgoing_tos 0x20 good_service_net
+#
+# TOS/DSCP values really only have local significance - so you should
+# know what you're specifying. For more information, see RFC2474,
+# RFC2475, and RFC3260.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or
+# "default" to use whatever default your host has.
+# Note that only multiples of 4 are usable as the two rightmost bits have
+# been redefined for use by ECN (RFC 3168 section 23.1).
+# The squid parser will enforce this by masking away the ECN bits.
+#
+# Processing proceeds in the order specified, and stops at first fully
+# matching line.
+#
+# Only fast ACLs are supported.
+#Default:
+# none
+
+# TAG: clientside_tos
+# Allows you to select a TOS/DSCP value for packets being transmitted
+# on the client-side, based on an ACL.
+#
+# clientside_tos ds-field [!]aclname ...
+#
+# Example where normal_service_net uses the TOS value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# clientside_tos 0x00 normal_service_net
+# clientside_tos 0x20 good_service_net
+#
+# Note: This feature is incompatible with qos_flows. Any TOS values set here
+# will be overwritten by TOS values in qos_flows.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or
+# "default" to use whatever default your host has.
+# Note that only multiples of 4 are usable as the two rightmost bits have
+# been redefined for use by ECN (RFC 3168 section 23.1).
+# The squid parser will enforce this by masking away the ECN bits.
+#
+#Default:
+# none
+
+# TAG: tcp_outgoing_mark
+# Note: This option is only available if Squid is rebuilt with the
+# Packet MARK (Linux)
+#
+# Allows you to apply a Netfilter mark value to outgoing packets
+# on the server side, based on an ACL.
+#
+# tcp_outgoing_mark mark-value [!]aclname ...
+#
+# Example where normal_service_net uses the mark value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# tcp_outgoing_mark 0x00 normal_service_net
+# tcp_outgoing_mark 0x20 good_service_net
+#
+# Only fast ACLs are supported.
+#Default:
+# none
+
+# TAG: clientside_mark
+# Note: This option is only available if Squid is rebuilt with the
+# Packet MARK (Linux)
+#
+# Allows you to apply a Netfilter mark value to packets being transmitted
+# on the client-side, based on an ACL.
+#
+# clientside_mark mark-value [!]aclname ...
+#
+# Example where normal_service_net uses the mark value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# clientside_mark 0x00 normal_service_net
+# clientside_mark 0x20 good_service_net
+#
+# Note: This feature is incompatible with qos_flows. Any mark values set here
+# will be overwritten by mark values in qos_flows.
+#Default:
+# none
+
+# TAG: qos_flows
+# Allows you to select a TOS/DSCP value to mark outgoing
+# connections to the client, based on where the reply was sourced.
+# For platforms using netfilter, allows you to set a netfilter mark
+# value instead of, or in addition to, a TOS value.
+#
+# By default this functionality is disabled. To enable it with the default
+# settings simply use "qos_flows mark" or "qos_flows tos". Default
+# settings will result in the netfilter mark or TOS value being copied
+# from the upstream connection to the client. Note that it is the connection
+# CONNMARK value not the packet MARK value that is copied.
+#
+# It is not currently possible to copy the mark or TOS value from the
+# client to the upstream connection request.
+#
+# TOS values really only have local significance - so you should
+# know what you're specifying. For more information, see RFC2474,
+# RFC2475, and RFC3260.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255.
+# Note that only multiples of 4 are usable as the two rightmost bits have
+# been redefined for use by ECN (RFC 3168 section 23.1).
+# The squid parser will enforce this by masking away the ECN bits.
+#
+# Mark values can be any unsigned 32-bit integer value.
+#
+# This setting is configured by setting the following values:
+#
+# tos|mark Whether to set TOS or netfilter mark values
+#
+# local-hit=0xFF Value to mark local cache hits.
+#
+# sibling-hit=0xFF Value to mark hits from sibling peers.
+#
+# parent-hit=0xFF Value to mark hits from parent peers.
+#
+# miss=0xFF[/mask] Value to mark cache misses. Takes precedence
+# over the preserve-miss feature (see below), unless
+# mask is specified, in which case only the bits
+# specified in the mask are written.
+#
+# The TOS variant of the following features are only possible on Linux
+# and require your kernel to be patched with the TOS preserving ZPH
+# patch, available from http://zph.bratcheda.org
+# No patch is needed to preserve the netfilter mark, which will work
+# with all variants of netfilter.
+#
+# disable-preserve-miss
+# This option disables the preservation of the TOS or netfilter
+# mark. By default, the existing TOS or netfilter mark value of
+# the response coming from the remote server will be retained
+# and masked with miss-mark.
+# NOTE: in the case of a netfilter mark, the mark must be set on
+# the connection (using the CONNMARK target) not on the packet
+# (MARK target).
+#
+# miss-mask=0xFF
+# Allows you to mask certain bits in the TOS or mark value
+# received from the remote server, before copying the value to
+# the TOS sent towards clients.
+# Default for tos: 0xFF (TOS from server is not changed).
+# Default for mark: 0xFFFFFFFF (mark from server is not changed).
+#
+# All of these features require the --enable-zph-qos compilation flag
+# (enabled by default). Netfilter marking also requires the
+# libnetfilter_conntrack libraries (--with-netfilter-conntrack) and
+# libcap 2.09+ (--with-libcap).
+#
+#Default:
+# none
+
+# TAG: tcp_outgoing_address
+# Allows you to map requests to different outgoing IP addresses
+# based on the username or source address of the user making
+# the request.
+#
+# tcp_outgoing_address ipaddr [[!]aclname] ...
+#
+# For example;
+# Forwarding clients with dedicated IPs for certain subnets.
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.2.0/24
+#
+# tcp_outgoing_address 2001:db8::c001 good_service_net
+# tcp_outgoing_address 10.1.0.2 good_service_net
+#
+# tcp_outgoing_address 2001:db8::beef normal_service_net
+# tcp_outgoing_address 10.1.0.1 normal_service_net
+#
+# tcp_outgoing_address 2001:db8::1
+# tcp_outgoing_address 10.1.0.3
+#
+# Processing proceeds in the order specified, and stops at first fully
+# matching line.
+#
+# Squid will add an implicit IP version test to each line.
+# Requests going to IPv4 websites will use the outgoing 10.1.0.* addresses.
+# Requests going to IPv6 websites will use the outgoing 2001:db8:* addresses.
+#
+#
+# NOTE: The use of this directive using client dependent ACLs is
+# incompatible with the use of server side persistent connections. To
+# ensure correct results it is best to set server_persistent_connections
+# to off when using this directive in such configurations.
+#
+# NOTE: The use of this directive to set a local IP on outgoing TCP links
+# is incompatible with using TPROXY to set client IP out outbound TCP links.
+# When needing to contact peers use the no-tproxy cache_peer option and the
+# client_dst_passthru directive re-enable normal forwarding such as this.
+#
+#Default:
+# Address selection is performed by the operating system.
+
+# TAG: host_verify_strict
+# Regardless of this option setting, when dealing with intercepted
+# traffic, Squid always verifies that the destination IP address matches
+# the Host header domain or IP (called 'authority form URL').
+#
+# This enforcement is performed to satisfy a MUST-level requirement in
+# RFC 2616 section 14.23: "The Host field value MUST represent the naming
+# authority of the origin server or gateway given by the original URL".
+#
+# When set to ON:
+# Squid always responds with an HTTP 409 (Conflict) error
+# page and logs a security warning if there is no match.
+#
+# Squid verifies that the destination IP address matches
+# the Host header for forward-proxy and reverse-proxy traffic
+# as well. For those traffic types, Squid also enables the
+# following checks, comparing the corresponding Host header
+# and Request-URI components:
+#
+# * The host names (domain or IP) must be identical,
+# but valueless or missing Host header disables all checks.
+# For the two host names to match, both must be either IP
+# or FQDN.
+#
+# * Port numbers must be identical, but if a port is missing
+# the scheme-default port is assumed.
+#
+#
+# When set to OFF (the default):
+# Squid allows suspicious requests to continue but logs a
+# security warning and blocks caching of the response.
+#
+# * Forward-proxy traffic is not checked at all.
+#
+# * Reverse-proxy traffic is not checked at all.
+#
+# * Intercepted traffic which passes verification is handled
+# according to client_dst_passthru.
+#
+# * Intercepted requests which fail verification are sent
+# to the client original destination instead of DIRECT.
+# This overrides 'client_dst_passthru off'.
+#
+# For now suspicious intercepted CONNECT requests are always
+# responded to with an HTTP 409 (Conflict) error page.
+#
+#
+# SECURITY NOTE:
+#
+# As described in CVE-2009-0801 when the Host: header alone is used
+# to determine the destination of a request it becomes trivial for
+# malicious scripts on remote websites to bypass browser same-origin
+# security policy and sandboxing protections.
+#
+# The cause of this is that such applets are allowed to perform their
+# own HTTP stack, in which case the same-origin policy of the browser
+# sandbox only verifies that the applet tries to contact the same IP
+# as from where it was loaded at the IP level. The Host: header may
+# be different from the connected IP and approved origin.
+#
+#Default:
+# host_verify_strict off
+
+# TAG: client_dst_passthru
+# With NAT or TPROXY intercepted traffic Squid may pass the request
+# directly to the original client destination IP or seek a faster
+# source using the HTTP Host header.
+#
+# Using Host to locate alternative servers can provide faster
+# connectivity with a range of failure recovery options.
+# But can also lead to connectivity trouble when the client and
+# server are attempting stateful interactions unaware of the proxy.
+#
+# This option (on by default) prevents alternative DNS entries being
+# located to send intercepted traffic DIRECT to an origin server.
+# The clients original destination IP and port will be used instead.
+#
+# Regardless of this option setting, when dealing with intercepted
+# traffic Squid will verify the Host: header and any traffic which
+# fails Host verification will be treated as if this option were ON.
+#
+# see host_verify_strict for details on the verification process.
+#Default:
+# client_dst_passthru on
+
+# SSL OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: ssl_unclean_shutdown
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Some browsers (especially MSIE) bugs out on SSL shutdown
+# messages.
+#Default:
+# ssl_unclean_shutdown off
+
+# TAG: ssl_engine
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# The OpenSSL engine to use. You will need to set this if you
+# would like to use hardware SSL acceleration for example.
+#Default:
+# none
+
+# TAG: sslproxy_client_certificate
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Client SSL Certificate to use when proxying https:// URLs
+#Default:
+# none
+
+# TAG: sslproxy_client_key
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Client SSL Key to use when proxying https:// URLs
+#Default:
+# none
+
+# TAG: sslproxy_version
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# SSL version level to use when proxying https:// URLs
+#
+# The versions of SSL/TLS supported:
+#
+# 1 automatic (default)
+# 2 SSLv2 only
+# 3 SSLv3 only
+# 4 TLSv1.0 only
+# 5 TLSv1.1 only
+# 6 TLSv1.2 only
+#Default:
+# automatic SSL/TLS version negotiation
+
+# TAG: sslproxy_options
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Colon (:) or comma (,) separated list of SSL implementation options
+# to use when proxying https:// URLs
+#
+# The most important being:
+#
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1.0
+# NO_TLSv1_1 Disallow the use of TLSv1.1
+# NO_TLSv1_2 Disallow the use of TLSv1.2
+#
+# SINGLE_DH_USE
+# Always create a new key when using temporary/ephemeral
+# DH key exchanges
+#
+# NO_TICKET
+# Disable use of RFC5077 session tickets. Some servers
+# may have problems understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+#
+# ALL Enable various bug workarounds suggested as "harmless"
+# by OpenSSL. Be warned that this may reduce SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation for a
+# complete list of possible options.
+#
+# WARNING: This directive takes a single token. If a space is used
+# the value(s) after that space are SILENTLY IGNORED.
+#Default:
+# none
+
+# TAG: sslproxy_cipher
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# SSL cipher list to use when proxying https:// URLs
+#
+# Colon separated list of supported ciphers.
+#Default:
+# none
+
+# TAG: sslproxy_cafile
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# file containing CA certificates to use when verifying server
+# certificates while proxying https:// URLs
+#Default:
+# none
+
+# TAG: sslproxy_capath
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# directory containing CA certificates to use when verifying
+# server certificates while proxying https:// URLs
+#Default:
+# none
+
+# TAG: sslproxy_session_ttl
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Sets the timeout value for SSL sessions
+#Default:
+# sslproxy_session_ttl 300
+
+# TAG: sslproxy_session_cache_size
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Sets the cache size to use for ssl session
+#Default:
+# sslproxy_session_cache_size 2 MB
+
+# TAG: sslproxy_foreign_intermediate_certs
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Many origin servers fail to send their full server certificate
+# chain for verification, assuming the client already has or can
+# easily locate any missing intermediate certificates.
+#
+# Squid uses the certificates from the specified file to fill in
+# these missing chains when trying to validate origin server
+# certificate chains.
+#
+# The file is expected to contain zero or more PEM-encoded
+# intermediate certificates. These certificates are not treated
+# as trusted root certificates, and any self-signed certificate in
+# this file will be ignored.
+#Default:
+# none
+
+# TAG: sslproxy_cert_sign_hash
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Sets the hashing algorithm to use when signing generated certificates.
+# Valid algorithm names depend on the OpenSSL library used. The following
+# names are usually available: sha1, sha256, sha512, and md5. Please see
+# your OpenSSL library manual for the available hashes. By default, Squids
+# that support this option use sha256 hashes.
+#
+# Squid does not forcefully purge cached certificates that were generated
+# with an algorithm other than the currently configured one. They remain
+# in the cache, subject to the regular cache eviction policy, and become
+# useful if the algorithm changes again.
+#Default:
+# none
+
+# TAG: ssl_bump
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# This option is consulted when a CONNECT request is received on
+# an http_port (or a new connection is intercepted at an
+# https_port), provided that port was configured with an ssl-bump
+# flag. The subsequent data on the connection is either treated as
+# HTTPS and decrypted OR tunneled at TCP level without decryption,
+# depending on the first matching bumping "action".
+#
+# ssl_bump <action> [!]acl ...
+#
+# The following bumping actions are currently supported:
+#
+# splice
+# Become a TCP tunnel without decrypting proxied traffic.
+# This is the default action.
+#
+# bump
+# Establish a secure connection with the server and, using a
+# mimicked server certificate, with the client.
+#
+# peek
+# Receive client (step SslBump1) or server (step SslBump2)
+# certificate while preserving the possibility of splicing the
+# connection. Peeking at the server certificate (during step 2)
+# usually precludes bumping of the connection at step 3.
+#
+# stare
+# Receive client (step SslBump1) or server (step SslBump2)
+# certificate while preserving the possibility of bumping the
+# connection. Staring at the server certificate (during step 2)
+# usually precludes splicing of the connection at step 3.
+#
+# terminate
+# Close client and server connections.
+#
+# Backward compatibility actions available at step SslBump1:
+#
+# client-first
+# Bump the connection. Establish a secure connection with the
+# client first, then connect to the server. This old mode does
+# not allow Squid to mimic server SSL certificate and does not
+# work with intercepted SSL connections.
+#
+# server-first
+# Bump the connection. Establish a secure connection with the
+# server first, then establish a secure connection with the
+# client, using a mimicked server certificate. Works with both
+# CONNECT requests and intercepted SSL connections, but does
+# not allow to make decisions based on SSL handshake info.
+#
+# peek-and-splice
+# Decide whether to bump or splice the connection based on
+# client-to-squid and server-to-squid SSL hello messages.
+# XXX: Remove.
+#
+# none
+# Same as the "splice" action.
+#
+# All ssl_bump rules are evaluated at each of the supported bumping
+# steps. Rules with actions that are impossible at the current step are
+# ignored. The first matching ssl_bump action wins and is applied at the
+# end of the current step. If no rules match, the splice action is used.
+# See the at_step ACL for a list of the supported SslBump steps.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# See also: http_port ssl-bump, https_port ssl-bump, and acl at_step.
+#
+#
+# # Example: Bump all TLS connections except those originating from
+# # localhost or those going to example.com.
+#
+# acl broken_sites ssl::server_name .example.com
+# ssl_bump splice localhost
+# ssl_bump splice broken_sites
+# ssl_bump bump all
+#Default:
+# Become a TCP tunnel without decrypting proxied traffic.
+
+# TAG: sslproxy_flags
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Various flags modifying the use of SSL while proxying https:// URLs:
+# DONT_VERIFY_PEER Accept certificates that fail verification.
+# For refined control, see sslproxy_cert_error.
+# NO_DEFAULT_CA Don't use the default CA list built in
+# to OpenSSL.
+#Default:
+# none
+
+# TAG: sslproxy_cert_error
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Use this ACL to bypass server certificate validation errors.
+#
+# For example, the following lines will bypass all validation errors
+# when talking to servers for example.com. All other
+# validation errors will result in ERR_SECURE_CONNECT_FAIL error.
+#
+# acl BrokenButTrustedServers dstdomain example.com
+# sslproxy_cert_error allow BrokenButTrustedServers
+# sslproxy_cert_error deny all
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+# Using slow acl types may result in server crashes
+#
+# Without this option, all server certificate validation errors
+# terminate the transaction to protect Squid and the client.
+#
+# SQUID_X509_V_ERR_INFINITE_VALIDATION error cannot be bypassed
+# but should not happen unless your OpenSSL library is buggy.
+#
+# SECURITY WARNING:
+# Bypassing validation errors is dangerous because an
+# error usually implies that the server cannot be trusted
+# and the connection may be insecure.
+#
+# See also: sslproxy_flags and DONT_VERIFY_PEER.
+#Default:
+# Server certificate errors terminate the transaction.
+
+# TAG: sslproxy_cert_sign
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+#
+# sslproxy_cert_sign <signing algorithm> acl ...
+#
+# The following certificate signing algorithms are supported:
+#
+# signTrusted
+# Sign using the configured CA certificate which is usually
+# placed in and trusted by end-user browsers. This is the
+# default for trusted origin server certificates.
+#
+# signUntrusted
+# Sign to guarantee an X509_V_ERR_CERT_UNTRUSTED browser error.
+# This is the default for untrusted origin server certificates
+# that are not self-signed (see ssl::certUntrusted).
+#
+# signSelf
+# Sign using a self-signed certificate with the right CN to
+# generate a X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT error in the
+# browser. This is the default for self-signed origin server
+# certificates (see ssl::certSelfSigned).
+#
+# This clause only supports fast acl types.
+#
+# When sslproxy_cert_sign acl(s) match, Squid uses the corresponding
+# signing algorithm to generate the certificate and ignores all
+# subsequent sslproxy_cert_sign options (the first match wins). If no
+# acl(s) match, the default signing algorithm is determined by errors
+# detected when obtaining and validating the origin server certificate.
+#
+# WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can
+# be used with sslproxy_cert_adapt, but if and only if Squid is bumping a
+# CONNECT request that carries a domain name. In all other cases (CONNECT
+# to an IP address or an intercepted SSL connection), Squid cannot detect
+# the domain mismatch at certificate generation time when
+# bump-server-first is used.
+#Default:
+# none
+
+# TAG: sslproxy_cert_adapt
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+#
+# sslproxy_cert_adapt <adaptation algorithm> acl ...
+#
+# The following certificate adaptation algorithms are supported:
+#
+# setValidAfter
+# Sets the "Not After" property to the "Not After" property of
+# the CA certificate used to sign generated certificates.
+#
+# setValidBefore
+# Sets the "Not Before" property to the "Not Before" property of
+# the CA certificate used to sign generated certificates.
+#
+# setCommonName or setCommonName{CN}
+# Sets Subject.CN property to the host name specified as a
+# CN parameter or, if no explicit CN parameter was specified,
+# extracted from the CONNECT request. It is a misconfiguration
+# to use setCommonName without an explicit parameter for
+# intercepted or tproxied SSL connections.
+#
+# This clause only supports fast acl types.
+#
+# Squid first groups sslproxy_cert_adapt options by adaptation algorithm.
+# Within a group, when sslproxy_cert_adapt acl(s) match, Squid uses the
+# corresponding adaptation algorithm to generate the certificate and
+# ignores all subsequent sslproxy_cert_adapt options in that algorithm's
+# group (i.e., the first match wins within each algorithm group). If no
+# acl(s) match, the default mimicking action takes place.
+#
+# WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can
+# be used with sslproxy_cert_adapt, but if and only if Squid is bumping a
+# CONNECT request that carries a domain name. In all other cases (CONNECT
+# to an IP address or an intercepted SSL connection), Squid cannot detect
+# the domain mismatch at certificate generation time when
+# bump-server-first is used.
+#Default:
+# none
+
+# TAG: sslpassword_program
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Specify a program used for entering SSL key passphrases
+# when using encrypted SSL certificate keys. If not specified
+# keys must either be unencrypted, or Squid started with the -N
+# option to allow it to query interactively for the passphrase.
+#
+# The key file name is given as argument to the program allowing
+# selection of the right password if you have multiple encrypted
+# keys.
+#Default:
+# none
+
+# OPTIONS RELATING TO EXTERNAL SSL_CRTD
+# -----------------------------------------------------------------------------
+
+# TAG: sslcrtd_program
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl-crtd
+#
+# Specify the location and options of the executable for ssl_crtd process.
+# /usr/lib/squid/ssl_crtd program requires -s and -M parameters
+# For more information use:
+# /usr/lib/squid/ssl_crtd -h
+#Default:
+# sslcrtd_program /usr/lib/squid/ssl_crtd -s /var/lib/ssl_db -M 4MB
+
+# TAG: sslcrtd_children
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl-crtd
+#
+# The maximum number of processes spawn to service ssl server.
+# The maximum this may be safely set to is 32.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=N
+#
+# Sets the minimum number of processes to spawn when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few children temporary slows Squid under load while it
+# tries to spawn enough additional processes to cope with traffic.
+#
+# idle=N
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# You must have at least one ssl_crtd process.
+#Default:
+# sslcrtd_children 32 startup=5 idle=1
+
+# TAG: sslcrtvalidator_program
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Specify the location and options of the executable for ssl_crt_validator
+# process.
+#
+# Usage: sslcrtvalidator_program [ttl=n] [cache=n] path ...
+#
+# Options:
+# ttl=n TTL in seconds for cached results. The default is 60 secs
+# cache=n limit the result cache size. The default value is 2048
+#Default:
+# none
+
+# TAG: sslcrtvalidator_children
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# The maximum number of processes spawn to service SSL server.
+# The maximum this may be safely set to is 32.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=N
+#
+# Sets the minimum number of processes to spawn when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few children temporary slows Squid under load while it
+# tries to spawn enough additional processes to cope with traffic.
+#
+# idle=N
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each certificate validator helper can handle in
+# parallel. A value of 0 indicates the certficate validator does not
+# support concurrency. Defaults to 1.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# a request ID in front of the request/response. The request
+# ID from the request must be echoed back with the response
+# to that request.
+#
+# You must have at least one ssl_crt_validator process.
+#Default:
+# sslcrtvalidator_children 32 startup=5 idle=1 concurrency=1
+
+# OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM
+# -----------------------------------------------------------------------------
+
+# TAG: cache_peer
+# To specify other caches in a hierarchy, use the format:
+#
+# cache_peer hostname type http-port icp-port [options]
+#
+# For example,
+#
+# # proxy icp
+# # hostname type port port options
+# # -------------------- -------- ----- ----- -----------
+# cache_peer parent.foo.net parent 3128 3130 default
+# cache_peer sib1.foo.net sibling 3128 3130 proxy-only
+# cache_peer sib2.foo.net sibling 3128 3130 proxy-only
+# cache_peer example.com parent 80 0 default
+# cache_peer cdn.example.com sibling 3128 0
+#
+# type: either 'parent', 'sibling', or 'multicast'.
+#
+# proxy-port: The port number where the peer accept HTTP requests.
+# For other Squid proxies this is usually 3128
+# For web servers this is usually 80
+#
+# icp-port: Used for querying neighbor caches about objects.
+# Set to 0 if the peer does not support ICP or HTCP.
+# See ICP and HTCP options below for additional details.
+#
+#
+# ==== ICP OPTIONS ====
+#
+# You MUST also set icp_port and icp_access explicitly when using these options.
+# The defaults will prevent peer traffic using ICP.
+#
+#
+# no-query Disable ICP queries to this neighbor.
+#
+# multicast-responder
+# Indicates the named peer is a member of a multicast group.
+# ICP queries will not be sent directly to the peer, but ICP
+# replies will be accepted from it.
+#
+# closest-only Indicates that, for ICP_OP_MISS replies, we'll only forward
+# CLOSEST_PARENT_MISSes and never FIRST_PARENT_MISSes.
+#
+# background-ping
+# To only send ICP queries to this neighbor infrequently.
+# This is used to keep the neighbor round trip time updated
+# and is usually used in conjunction with weighted-round-robin.
+#
+#
+# ==== HTCP OPTIONS ====
+#
+# You MUST also set htcp_port and htcp_access explicitly when using these options.
+# The defaults will prevent peer traffic using HTCP.
+#
+#
+# htcp Send HTCP, instead of ICP, queries to the neighbor.
+# You probably also want to set the "icp-port" to 4827
+# instead of 3130. This directive accepts a comma separated
+# list of options described below.
+#
+# htcp=oldsquid Send HTCP to old Squid versions (2.5 or earlier).
+#
+# htcp=no-clr Send HTCP to the neighbor but without
+# sending any CLR requests. This cannot be used with
+# only-clr.
+#
+# htcp=only-clr Send HTCP to the neighbor but ONLY CLR requests.
+# This cannot be used with no-clr.
+#
+# htcp=no-purge-clr
+# Send HTCP to the neighbor including CLRs but only when
+# they do not result from PURGE requests.
+#
+# htcp=forward-clr
+# Forward any HTCP CLR requests this proxy receives to the peer.
+#
+#
+# ==== PEER SELECTION METHODS ====
+#
+# The default peer selection method is ICP, with the first responding peer
+# being used as source. These options can be used for better load balancing.
+#
+#
+# default This is a parent cache which can be used as a "last-resort"
+# if a peer cannot be located by any of the peer-selection methods.
+# If specified more than once, only the first is used.
+#
+# round-robin Load-Balance parents which should be used in a round-robin
+# fashion in the absence of any ICP queries.
+# weight=N can be used to add bias.
+#
+# weighted-round-robin
+# Load-Balance parents which should be used in a round-robin
+# fashion with the frequency of each parent being based on the
+# round trip time. Closer parents are used more often.
+# Usually used for background-ping parents.
+# weight=N can be used to add bias.
+#
+# carp Load-Balance parents which should be used as a CARP array.
+# The requests will be distributed among the parents based on the
+# CARP load balancing hash function based on their weight.
+#
+# userhash Load-balance parents based on the client proxy_auth or ident username.
+#
+# sourcehash Load-balance parents based on the client source IP.
+#
+# multicast-siblings
+# To be used only for cache peers of type "multicast".
+# ALL members of this multicast group have "sibling"
+# relationship with it, not "parent". This is to a multicast
+# group when the requested object would be fetched only from
+# a "parent" cache, anyway. It's useful, e.g., when
+# configuring a pool of redundant Squid proxies, being
+# members of the same multicast group.
+#
+#
+# ==== PEER SELECTION OPTIONS ====
+#
+# weight=N use to affect the selection of a peer during any weighted
+# peer-selection mechanisms.
+# The weight must be an integer; default is 1,
+# larger weights are favored more.
+# This option does not affect parent selection if a peering
+# protocol is not in use.
+#
+# basetime=N Specify a base amount to be subtracted from round trip
+# times of parents.
+# It is subtracted before division by weight in calculating
+# which parent to fectch from. If the rtt is less than the
+# base time the rtt is set to a minimal value.
+#
+# ttl=N Specify a TTL to use when sending multicast ICP queries
+# to this address.
+# Only useful when sending to a multicast group.
+# Because we don't accept ICP replies from random
+# hosts, you must configure other group members as
+# peers with the 'multicast-responder' option.
+#
+# no-delay To prevent access to this neighbor from influencing the
+# delay pools.
+#
+# digest-url=URL Tell Squid to fetch the cache digest (if digests are
+# enabled) for this host from the specified URL rather
+# than the Squid default location.
+#
+#
+# ==== CARP OPTIONS ====
+#
+# carp-key=key-specification
+# use a different key than the full URL to hash against the peer.
+# the key-specification is a comma-separated list of the keywords
+# scheme, host, port, path, params
+# Order is not important.
+#
+# ==== ACCELERATOR / REVERSE-PROXY OPTIONS ====
+#
+# originserver Causes this parent to be contacted as an origin server.
+# Meant to be used in accelerator setups when the peer
+# is a web server.
+#
+# forceddomain=name
+# Set the Host header of requests forwarded to this peer.
+# Useful in accelerator setups where the server (peer)
+# expects a certain domain name but clients may request
+# others. ie example.com or www.example.com
+#
+# no-digest Disable request of cache digests.
+#
+# no-netdb-exchange
+# Disables requesting ICMP RTT database (NetDB).
+#
+#
+# ==== AUTHENTICATION OPTIONS ====
+#
+# login=user:password
+# If this is a personal/workgroup proxy and your parent
+# requires proxy authentication.
+#
+# Note: The string can include URL escapes (i.e. %20 for
+# spaces). This also means % must be written as %%.
+#
+# login=PASSTHRU
+# Send login details received from client to this peer.
+# Both Proxy- and WWW-Authorization headers are passed
+# without alteration to the peer.
+# Authentication is not required by Squid for this to work.
+#
+# Note: This will pass any form of authentication but
+# only Basic auth will work through a proxy unless the
+# connection-auth options are also used.
+#
+# login=PASS Send login details received from client to this peer.
+# Authentication is not required by this option.
+#
+# If there are no client-provided authentication headers
+# to pass on, but username and password are available
+# from an external ACL user= and password= result tags
+# they may be sent instead.
+#
+# Note: To combine this with proxy_auth both proxies must
+# share the same user database as HTTP only allows for
+# a single login (one for proxy, one for origin server).
+# Also be warned this will expose your users proxy
+# password to the peer. USE WITH CAUTION
+#
+# login=*:password
+# Send the username to the upstream cache, but with a
+# fixed password. This is meant to be used when the peer
+# is in another administrative domain, but it is still
+# needed to identify each user.
+# The star can optionally be followed by some extra
+# information which is added to the username. This can
+# be used to identify this proxy to the peer, similar to
+# the login=username:password option above.
+#
+# login=NEGOTIATE
+# If this is a personal/workgroup proxy and your parent
+# requires a secure proxy authentication.
+# The first principal from the default keytab or defined by
+# the environment variable KRB5_KTNAME will be used.
+#
+# WARNING: The connection may transmit requests from multiple
+# clients. Negotiate often assumes end-to-end authentication
+# and a single-client. Which is not strictly true here.
+#
+# login=NEGOTIATE:principal_name
+# If this is a personal/workgroup proxy and your parent
+# requires a secure proxy authentication.
+# The principal principal_name from the default keytab or
+# defined by the environment variable KRB5_KTNAME will be
+# used.
+#
+# WARNING: The connection may transmit requests from multiple
+# clients. Negotiate often assumes end-to-end authentication
+# and a single-client. Which is not strictly true here.
+#
+# connection-auth=on|off
+# Tell Squid that this peer does or not support Microsoft
+# connection oriented authentication, and any such
+# challenges received from there should be ignored.
+# Default is auto to automatically determine the status
+# of the peer.
+#
+#
+# ==== SSL / HTTPS / TLS OPTIONS ====
+#
+# ssl Encrypt connections to this peer with SSL/TLS.
+#
+# sslcert=/path/to/ssl/certificate
+# A client SSL certificate to use when connecting to
+# this peer.
+#
+# sslkey=/path/to/ssl/key
+# The private SSL key corresponding to sslcert above.
+# If 'sslkey' is not specified 'sslcert' is assumed to
+# reference a combined file containing both the
+# certificate and the key.
+#
+# sslversion=1|2|3|4|5|6
+# The SSL version to use when connecting to this peer
+# 1 = automatic (default)
+# 2 = SSL v2 only
+# 3 = SSL v3 only
+# 4 = TLS v1.0 only
+# 5 = TLS v1.1 only
+# 6 = TLS v1.2 only
+#
+# sslcipher=... The list of valid SSL ciphers to use when connecting
+# to this peer.
+#
+# ssloptions=... Specify various SSL implementation options:
+#
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1.0
+# NO_TLSv1_1 Disallow the use of TLSv1.1
+# NO_TLSv1_2 Disallow the use of TLSv1.2
+#
+# SINGLE_DH_USE
+# Always create a new key when using
+# temporary/ephemeral DH key exchanges
+#
+# NO_TICKET
+# Disable use of RFC5077 session tickets. Some servers
+# may have problems understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+#
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation for a
+# more complete list.
+#
+# sslcafile=... A file containing additional CA certificates to use
+# when verifying the peer certificate.
+#
+# sslcapath=... A directory containing additional CA certificates to
+# use when verifying the peer certificate.
+#
+# sslcrlfile=... A certificate revocation list file to use when
+# verifying the peer certificate.
+#
+# sslflags=... Specify various flags modifying the SSL implementation:
+#
+# DONT_VERIFY_PEER
+# Accept certificates even if they fail to
+# verify.
+# NO_DEFAULT_CA
+# Don't use the default CA list built in
+# to OpenSSL.
+# DONT_VERIFY_DOMAIN
+# Don't verify the peer certificate
+# matches the server name
+#
+# ssldomain= The peer name as advertised in it's certificate.
+# Used for verifying the correctness of the received peer
+# certificate. If not specified the peer hostname will be
+# used.
+#
+# front-end-https
+# Enable the "Front-End-Https: On" header needed when
+# using Squid as a SSL frontend in front of Microsoft OWA.
+# See MS KB document Q307347 for details on this header.
+# If set to auto the header will only be added if the
+# request is forwarded as a https:// URL.
+#
+#
+# ==== GENERAL OPTIONS ====
+#
+# connect-timeout=N
+# A peer-specific connect timeout.
+# Also see the peer_connect_timeout directive.
+#
+# connect-fail-limit=N
+# How many times connecting to a peer must fail before
+# it is marked as down. Standby connection failures
+# count towards this limit. Default is 10.
+#
+# allow-miss Disable Squid's use of only-if-cached when forwarding
+# requests to siblings. This is primarily useful when
+# icp_hit_stale is used by the sibling. Excessive use
+# of this option may result in forwarding loops. One way
+# to prevent peering loops when using this option, is to
+# deny cache peer usage on requests from a peer:
+# acl fromPeer ...
+# cache_peer_access peerName deny fromPeer
+#
+# max-conn=N Limit the number of concurrent connections the Squid
+# may open to this peer, including already opened idle
+# and standby connections. There is no peer-specific
+# connection limit by default.
+#
+# A peer exceeding the limit is not used for new
+# requests unless a standby connection is available.
+#
+# max-conn currently works poorly with idle persistent
+# connections: When a peer reaches its max-conn limit,
+# and there are idle persistent connections to the peer,
+# the peer may not be selected because the limiting code
+# does not know whether Squid can reuse those idle
+# connections.
+#
+# standby=N Maintain a pool of N "hot standby" connections to an
+# UP peer, available for requests when no idle
+# persistent connection is available (or safe) to use.
+# By default and with zero N, no such pool is maintained.
+# N must not exceed the max-conn limit (if any).
+#
+# At start or after reconfiguration, Squid opens new TCP
+# standby connections until there are N connections
+# available and then replenishes the standby pool as
+# opened connections are used up for requests. A used
+# connection never goes back to the standby pool, but
+# may go to the regular idle persistent connection pool
+# shared by all peers and origin servers.
+#
+# Squid never opens multiple new standby connections
+# concurrently. This one-at-a-time approach minimizes
+# flooding-like effect on peers. Furthermore, just a few
+# standby connections should be sufficient in most cases
+# to supply most new requests with a ready-to-use
+# connection.
+#
+# Standby connections obey server_idle_pconn_timeout.
+# For the feature to work as intended, the peer must be
+# configured to accept and keep them open longer than
+# the idle timeout at the connecting Squid, to minimize
+# race conditions typical to idle used persistent
+# connections. Default request_timeout and
+# server_idle_pconn_timeout values ensure such a
+# configuration.
+#
+# name=xxx Unique name for the peer.
+# Required if you have multiple peers on the same host
+# but different ports.
+# This name can be used in cache_peer_access and similar
+# directives to identify the peer.
+# Can be used by outgoing access controls through the
+# peername ACL type.
+#
+# no-tproxy Do not use the client-spoof TPROXY support when forwarding
+# requests to this peer. Use normal address selection instead.
+# This overrides the spoof_client_ip ACL.
+#
+# proxy-only objects fetched from the peer will not be stored locally.
+#
+#Default:
+# none
+
+# TAG: cache_peer_domain
+# Use to limit the domains for which a neighbor cache will be
+# queried.
+#
+# Usage:
+# cache_peer_domain cache-host domain [domain ...]
+# cache_peer_domain cache-host !domain
+#
+# For example, specifying
+#
+# cache_peer_domain parent.foo.net .edu
+#
+# has the effect such that UDP query packets are sent to
+# 'bigserver' only when the requested object exists on a
+# server in the .edu domain. Prefixing the domainname
+# with '!' means the cache will be queried for objects
+# NOT in that domain.
+#
+# NOTE: * Any number of domains may be given for a cache-host,
+# either on the same or separate lines.
+# * When multiple domains are given for a particular
+# cache-host, the first matched domain is applied.
+# * Cache hosts with no domain restrictions are queried
+# for all requests.
+# * There are no defaults.
+# * There is also a 'cache_peer_access' tag in the ACL
+# section.
+#Default:
+# none
+
+# TAG: cache_peer_access
+# Restricts usage of cache_peer proxies.
+#
+# Usage:
+# cache_peer_access peer-name allow|deny [!]aclname ...
+#
+# For the required peer-name parameter, use either the value of the
+# cache_peer name=value parameter or, if name=value is missing, the
+# cache_peer hostname parameter.
+#
+# This directive narrows down the selection of peering candidates, but
+# does not determine the order in which the selected candidates are
+# contacted. That order is determined by the peer selection algorithms
+# (see PEER SELECTION sections in the cache_peer documentation).
+#
+# If a deny rule matches, the corresponding peer will not be contacted
+# for the current transaction -- Squid will not send ICP queries and
+# will not forward HTTP requests to that peer. An allow match leaves
+# the corresponding peer in the selection. The first match for a given
+# peer wins for that peer.
+#
+# The relative order of cache_peer_access directives for the same peer
+# matters. The relative order of any two cache_peer_access directives
+# for different peers does not matter. To ease interpretation, it is a
+# good idea to group cache_peer_access directives for the same peer
+# together.
+#
+# A single cache_peer_access directive may be evaluated multiple times
+# for a given transaction because individual peer selection algorithms
+# may check it independently from each other. These redundant checks
+# may be optimized away in future Squid versions.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# No peer usage restrictions.
+
+# TAG: neighbor_type_domain
+# Modify the cache_peer neighbor type when passing requests
+# about specific domains to the peer.
+#
+# Usage:
+# neighbor_type_domain neighbor parent|sibling domain domain ...
+#
+# For example:
+# cache_peer foo.example.com parent 3128 3130
+# neighbor_type_domain foo.example.com sibling .au .de
+#
+# The above configuration treats all requests to foo.example.com as a
+# parent proxy unless the request is for a .au or .de ccTLD domain name.
+#Default:
+# The peer type from cache_peer directive is used for all requests to that peer.
+
+# TAG: dead_peer_timeout (seconds)
+# This controls how long Squid waits to declare a peer cache
+# as "dead." If there are no ICP replies received in this
+# amount of time, Squid will declare the peer dead and not
+# expect to receive any further ICP replies. However, it
+# continues to send ICP queries, and will mark the peer as
+# alive upon receipt of the first subsequent ICP reply.
+#
+# This timeout also affects when Squid expects to receive ICP
+# replies from peers. If more than 'dead_peer' seconds have
+# passed since the last ICP reply was received, Squid will not
+# expect to receive an ICP reply on the next query. Thus, if
+# your time between requests is greater than this timeout, you
+# will see a lot of requests sent DIRECT to origin servers
+# instead of to your parents.
+#Default:
+# dead_peer_timeout 10 seconds
+
+# TAG: forward_max_tries
+# Controls how many different forward paths Squid will try
+# before giving up. See also forward_timeout.
+#
+# NOTE: connect_retries (default: none) can make each of these
+# possible forwarding paths be tried multiple times.
+#Default:
+# forward_max_tries 25
+
+# MEMORY CACHE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_mem (bytes)
+# NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE.
+# IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL
+# USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER
+# THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS.
+#
+# 'cache_mem' specifies the ideal amount of memory to be used
+# for:
+# * In-Transit objects
+# * Hot Objects
+# * Negative-Cached objects
+#
+# Data for these objects are stored in 4 KB blocks. This
+# parameter specifies the ideal upper limit on the total size of
+# 4 KB blocks allocated. In-Transit objects take the highest
+# priority.
+#
+# In-transit objects have priority over the others. When
+# additional space is needed for incoming data, negative-cached
+# and hot objects will be released. In other words, the
+# negative-cached and hot objects will fill up any unused space
+# not needed for in-transit objects.
+#
+# If circumstances require, this limit will be exceeded.
+# Specifically, if your incoming request rate requires more than
+# 'cache_mem' of memory to hold in-transit objects, Squid will
+# exceed this limit to satisfy the new requests. When the load
+# decreases, blocks will be freed until the high-water mark is
+# reached. Thereafter, blocks will be used to store hot
+# objects.
+#
+# If shared memory caching is enabled, Squid does not use the shared
+# cache space for in-transit objects, but they still consume as much
+# local memory as they need. For more details about the shared memory
+# cache, see memory_cache_shared.
+#Default:
+# cache_mem 256 MB
+
+# TAG: maximum_object_size_in_memory (bytes)
+# Objects greater than this size will not be attempted to kept in
+# the memory cache. This should be set high enough to keep objects
+# accessed frequently in memory to improve performance whilst low
+# enough to keep larger objects from hoarding cache_mem.
+#Default:
+# maximum_object_size_in_memory 512 KB
+
+# TAG: memory_cache_shared on|off
+# Controls whether the memory cache is shared among SMP workers.
+#
+# The shared memory cache is meant to occupy cache_mem bytes and replace
+# the non-shared memory cache, although some entities may still be
+# cached locally by workers for now (e.g., internal and in-transit
+# objects may be served from a local memory cache even if shared memory
+# caching is enabled).
+#
+# By default, the memory cache is shared if and only if all of the
+# following conditions are satisfied: Squid runs in SMP mode with
+# multiple workers, cache_mem is positive, and Squid environment
+# supports required IPC primitives (e.g., POSIX shared memory segments
+# and GCC-style atomic operations).
+#
+# To avoid blocking locks, shared memory uses opportunistic algorithms
+# that do not guarantee that every cachable entity that could have been
+# shared among SMP workers will actually be shared.
+#Default:
+# "on" where supported if doing memory caching with multiple SMP workers.
+
+# TAG: memory_cache_mode
+# Controls which objects to keep in the memory cache (cache_mem)
+#
+# always Keep most recently fetched objects in memory (default)
+#
+# disk Only disk cache hits are kept in memory, which means
+# an object must first be cached on disk and then hit
+# a second time before cached in memory.
+#
+# network Only objects fetched from network is kept in memory
+#Default:
+# Keep the most recently fetched objects in memory
+
+# TAG: memory_replacement_policy
+# The memory replacement policy parameter determines which
+# objects are purged from memory when memory space is needed.
+#
+# See cache_replacement_policy for details on algorithms.
+#Default:
+# memory_replacement_policy lru
+
+# DISK CACHE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_replacement_policy
+# The cache replacement policy parameter determines which
+# objects are evicted (replaced) when disk space is needed.
+#
+# lru : Squid's original list based LRU policy
+# heap GDSF : Greedy-Dual Size Frequency
+# heap LFUDA: Least Frequently Used with Dynamic Aging
+# heap LRU : LRU policy implemented using a heap
+#
+# Applies to any cache_dir lines listed below this directive.
+#
+# The LRU policies keeps recently referenced objects.
+#
+# The heap GDSF policy optimizes object hit rate by keeping smaller
+# popular objects in cache so it has a better chance of getting a
+# hit. It achieves a lower byte hit rate than LFUDA though since
+# it evicts larger (possibly popular) objects.
+#
+# The heap LFUDA policy keeps popular objects in cache regardless of
+# their size and thus optimizes byte hit rate at the expense of
+# hit rate since one large, popular object will prevent many
+# smaller, slightly less popular objects from being cached.
+#
+# Both policies utilize a dynamic aging mechanism that prevents
+# cache pollution that can otherwise occur with frequency-based
+# replacement policies.
+#
+# NOTE: if using the LFUDA replacement policy you should increase
+# the value of maximum_object_size above its default of 4 MB to
+# to maximize the potential byte hit rate improvement of LFUDA.
+#
+# For more information about the GDSF and LFUDA cache replacement
+# policies see http://www.hpl.hp.com/techreports/1999/HPL-1999-69.html
+# and http://fog.hpl.external.hp.com/techreports/98/HPL-98-173.html.
+#Default:
+# cache_replacement_policy lru
+
+# TAG: minimum_object_size (bytes)
+# Objects smaller than this size will NOT be saved on disk. The
+# value is specified in bytes, and the default is 0 KB, which
+# means all responses can be stored.
+#Default:
+# no limit
+
+# TAG: maximum_object_size (bytes)
+# Set the default value for max-size parameter on any cache_dir.
+# The value is specified in bytes, and the default is 4 MB.
+#
+# If you wish to get a high BYTES hit ratio, you should probably
+# increase this (one 32 MB object hit counts for 3200 10KB
+# hits).
+#
+# If you wish to increase hit ratio more than you want to
+# save bandwidth you should leave this low.
+#
+# NOTE: if using the LFUDA replacement policy you should increase
+# this value to maximize the byte hit rate improvement of LFUDA!
+# See cache_replacement_policy for a discussion of this policy.
+#Default:
+# maximum_object_size 4 MB
+
+# TAG: cache_dir
+# Format:
+# cache_dir Type Directory-Name Fs-specific-data [options]
+#
+# You can specify multiple cache_dir lines to spread the
+# cache among different disk partitions.
+#
+# Type specifies the kind of storage system to use. Only "ufs"
+# is built by default. To enable any of the other storage systems
+# see the --enable-storeio configure option.
+#
+# 'Directory' is a top-level directory where cache swap
+# files will be stored. If you want to use an entire disk
+# for caching, this can be the mount-point directory.
+# The directory must exist and be writable by the Squid
+# process. Squid will NOT create this directory for you.
+#
+# In SMP configurations, cache_dir must not precede the workers option
+# and should use configuration macros or conditionals to give each
+# worker interested in disk caching a dedicated cache directory.
+#
+#
+# ==== The ufs store type ====
+#
+# "ufs" is the old well-known Squid storage format that has always
+# been there.
+#
+# Usage:
+# cache_dir ufs Directory-Name Mbytes L1 L2 [options]
+#
+# 'Mbytes' is the amount of disk space (MB) to use under this
+# directory. The default is 100 MB. Change this to suit your
+# configuration. Do NOT put the size of your disk drive here.
+# Instead, if you want Squid to use the entire disk drive,
+# subtract 20% and use that value.
+#
+# 'L1' is the number of first-level subdirectories which
+# will be created under the 'Directory'. The default is 16.
+#
+# 'L2' is the number of second-level subdirectories which
+# will be created under each first-level directory. The default
+# is 256.
+#
+#
+# ==== The aufs store type ====
+#
+# "aufs" uses the same storage format as "ufs", utilizing
+# POSIX-threads to avoid blocking the main Squid process on
+# disk-I/O. This was formerly known in Squid as async-io.
+#
+# Usage:
+# cache_dir aufs Directory-Name Mbytes L1 L2 [options]
+#
+# see argument descriptions under ufs above
+#
+#
+# ==== The diskd store type ====
+#
+# "diskd" uses the same storage format as "ufs", utilizing a
+# separate process to avoid blocking the main Squid process on
+# disk-I/O.
+#
+# Usage:
+# cache_dir diskd Directory-Name Mbytes L1 L2 [options] [Q1=n] [Q2=n]
+#
+# see argument descriptions under ufs above
+#
+# Q1 specifies the number of unacknowledged I/O requests when Squid
+# stops opening new files. If this many messages are in the queues,
+# Squid won't open new files. Default is 64
+#
+# Q2 specifies the number of unacknowledged messages when Squid
+# starts blocking. If this many messages are in the queues,
+# Squid blocks until it receives some replies. Default is 72
+#
+# When Q1 < Q2 (the default), the cache directory is optimized
+# for lower response time at the expense of a decrease in hit
+# ratio. If Q1 > Q2, the cache directory is optimized for
+# higher hit ratio at the expense of an increase in response
+# time.
+#
+#
+# ==== The rock store type ====
+#
+# Usage:
+# cache_dir rock Directory-Name Mbytes [options]
+#
+# The Rock Store type is a database-style storage. All cached
+# entries are stored in a "database" file, using fixed-size slots.
+# A single entry occupies one or more slots.
+#
+# If possible, Squid using Rock Store creates a dedicated kid
+# process called "disker" to avoid blocking Squid worker(s) on disk
+# I/O. One disker kid is created for each rock cache_dir. Diskers
+# are created only when Squid, running in daemon mode, has support
+# for the IpcIo disk I/O module.
+#
+# swap-timeout=msec: Squid will not start writing a miss to or
+# reading a hit from disk if it estimates that the swap operation
+# will take more than the specified number of milliseconds. By
+# default and when set to zero, disables the disk I/O time limit
+# enforcement. Ignored when using blocking I/O module because
+# blocking synchronous I/O does not allow Squid to estimate the
+# expected swap wait time.
+#
+# max-swap-rate=swaps/sec: Artificially limits disk access using
+# the specified I/O rate limit. Swap out requests that
+# would cause the average I/O rate to exceed the limit are
+# delayed. Individual swap in requests (i.e., hits or reads) are
+# not delayed, but they do contribute to measured swap rate and
+# since they are placed in the same FIFO queue as swap out
+# requests, they may wait longer if max-swap-rate is smaller.
+# This is necessary on file systems that buffer "too
+# many" writes and then start blocking Squid and other processes
+# while committing those writes to disk. Usually used together
+# with swap-timeout to avoid excessive delays and queue overflows
+# when disk demand exceeds available disk "bandwidth". By default
+# and when set to zero, disables the disk I/O rate limit
+# enforcement. Currently supported by IpcIo module only.
+#
+# slot-size=bytes: The size of a database "record" used for
+# storing cached responses. A cached response occupies at least
+# one slot and all database I/O is done using individual slots so
+# increasing this parameter leads to more disk space waste while
+# decreasing it leads to more disk I/O overheads. Should be a
+# multiple of your operating system I/O page size. Defaults to
+# 16KBytes. A housekeeping header is stored with each slot and
+# smaller slot-sizes will be rejected. The header is smaller than
+# 100 bytes.
+#
+#
+# ==== COMMON OPTIONS ====
+#
+# no-store no new objects should be stored to this cache_dir.
+#
+# min-size=n the minimum object size in bytes this cache_dir
+# will accept. It's used to restrict a cache_dir
+# to only store large objects (e.g. AUFS) while
+# other stores are optimized for smaller objects
+# (e.g. Rock).
+# Defaults to 0.
+#
+# max-size=n the maximum object size in bytes this cache_dir
+# supports.
+# The value in maximum_object_size directive sets
+# the default unless more specific details are
+# available (ie a small store capacity).
+#
+# Note: To make optimal use of the max-size limits you should order
+# the cache_dir lines with the smallest max-size value first.
+#
+#Default:
+# No disk cache. Store cache ojects only in memory.
+#
+
+# Uncomment and adjust the following to add a disk cache directory.
+#cache_dir ufs /var/spool/squid 100 16 256
+
+# TAG: store_dir_select_algorithm
+# How Squid selects which cache_dir to use when the response
+# object will fit into more than one.
+#
+# Regardless of which algorithm is used the cache_dir min-size
+# and max-size parameters are obeyed. As such they can affect
+# the selection algorithm by limiting the set of considered
+# cache_dir.
+#
+# Algorithms:
+#
+# least-load
+#
+# This algorithm is suited to caches with similar cache_dir
+# sizes and disk speeds.
+#
+# The disk with the least I/O pending is selected.
+# When there are multiple disks with the same I/O load ranking
+# the cache_dir with most available capacity is selected.
+#
+# When a mix of cache_dir sizes are configured the faster disks
+# have a naturally lower I/O loading and larger disks have more
+# capacity. So space used to store objects and data throughput
+# may be very unbalanced towards larger disks.
+#
+#
+# round-robin
+#
+# This algorithm is suited to caches with unequal cache_dir
+# disk sizes.
+#
+# Each cache_dir is selected in a rotation. The next suitable
+# cache_dir is used.
+#
+# Available cache_dir capacity is only considered in relation
+# to whether the object will fit and meets the min-size and
+# max-size parameters.
+#
+# Disk I/O loading is only considered to prevent overload on slow
+# disks. This algorithm does not spread objects by size, so any
+# I/O loading per-disk may appear very unbalanced and volatile.
+#
+# If several cache_dirs use similar min-size, max-size, or other
+# limits to to reject certain responses, then do not group such
+# cache_dir lines together, to avoid round-robin selection bias
+# towards the first cache_dir after the group. Instead, interleave
+# cache_dir lines from different groups. For example:
+#
+# store_dir_select_algorithm round-robin
+# cache_dir rock /hdd1 ... min-size=100000
+# cache_dir rock /ssd1 ... max-size=99999
+# cache_dir rock /hdd2 ... min-size=100000
+# cache_dir rock /ssd2 ... max-size=99999
+# cache_dir rock /hdd3 ... min-size=100000
+# cache_dir rock /ssd3 ... max-size=99999
+#Default:
+# store_dir_select_algorithm least-load
+
+# TAG: max_open_disk_fds
+# To avoid having disk as the I/O bottleneck Squid can optionally
+# bypass the on-disk cache if more than this amount of disk file
+# descriptors are open.
+#
+# A value of 0 indicates no limit.
+#Default:
+# no limit
+
+# TAG: cache_swap_low (percent, 0-100)
+# The low-water mark for AUFS/UFS/diskd cache object eviction by
+# the cache_replacement_policy algorithm.
+#
+# Removal begins when the swap (disk) usage of a cache_dir is
+# above this low-water mark and attempts to maintain utilization
+# near the low-water mark.
+#
+# As swap utilization increases towards the high-water mark set
+# by cache_swap_high object eviction becomes more agressive.
+#
+# The value difference in percentages between low- and high-water
+# marks represent an eviction rate of 300 objects per second and
+# the rate continues to scale in agressiveness by multiples of
+# this above the high-water mark.
+#
+# Defaults are 90% and 95%. If you have a large cache, 5% could be
+# hundreds of MB. If this is the case you may wish to set these
+# numbers closer together.
+#
+# See also cache_swap_high and cache_replacement_policy
+#Default:
+# cache_swap_low 90
+
+# TAG: cache_swap_high (percent, 0-100)
+# The high-water mark for AUFS/UFS/diskd cache object eviction by
+# the cache_replacement_policy algorithm.
+#
+# Removal begins when the swap (disk) usage of a cache_dir is
+# above the low-water mark set by cache_swap_low and attempts to
+# maintain utilization near the low-water mark.
+#
+# As swap utilization increases towards this high-water mark object
+# eviction becomes more agressive.
+#
+# The value difference in percentages between low- and high-water
+# marks represent an eviction rate of 300 objects per second and
+# the rate continues to scale in agressiveness by multiples of
+# this above the high-water mark.
+#
+# Defaults are 90% and 95%. If you have a large cache, 5% could be
+# hundreds of MB. If this is the case you may wish to set these
+# numbers closer together.
+#
+# See also cache_swap_low and cache_replacement_policy
+#Default:
+# cache_swap_high 95
+
+# LOGFILE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: logformat
+# Usage:
+#
+# logformat <name> <format specification>
+#
+# Defines an access log format.
+#
+# The <format specification> is a string with embedded % format codes
+#
+# % format codes all follow the same basic structure where all but
+# the formatcode is optional. Output strings are automatically escaped
+# as required according to their context and the output format
+# modifiers are usually not needed, but can be specified if an explicit
+# output format is desired.
+#
+# % ["|[|'|#] [-] [[0]width] [{argument}] formatcode
+#
+# " output in quoted string format
+# [ output in squid text log format as used by log_mime_hdrs
+# # output in URL quoted format
+# ' output as-is
+#
+# - left aligned
+#
+# width minimum and/or maximum field width:
+# [width_min][.width_max]
+# When minimum starts with 0, the field is zero-padded.
+# String values exceeding maximum width are truncated.
+#
+# {arg} argument such as header name etc
+#
+# Format codes:
+#
+# % a literal % character
+# sn Unique sequence number per log line entry
+# err_code The ID of an error response served by Squid or
+# a similar internal error identifier.
+# err_detail Additional err_code-dependent error information.
+# note The annotation specified by the argument. Also
+# logs the adaptation meta headers set by the
+# adaptation_meta configuration parameter.
+# If no argument given all annotations logged.
+# The argument may include a separator to use with
+# annotation values:
+# name[:separator]
+# By default, multiple note values are separated with ","
+# and multiple notes are separated with "\r\n".
+# When logging named notes with %{name}note, the
+# explicitly configured separator is used between note
+# values. When logging all notes with %note, the
+# explicitly configured separator is used between
+# individual notes. There is currently no way to
+# specify both value and notes separators when logging
+# all notes with %note.
+#
+# Connection related format codes:
+#
+# >a Client source IP address
+# >A Client FQDN
+# >p Client source port
+# >eui Client source EUI (MAC address, EUI-48 or EUI-64 identifier)
+# >la Local IP address the client connected to
+# >lp Local port number the client connected to
+# >qos Client connection TOS/DSCP value set by Squid
+# >nfmark Client connection netfilter mark set by Squid
+#
+# la Local listening IP address the client connection was connected to.
+# lp Local listening port number the client connection was connected to.
+#
+# <a Server IP address of the last server or peer connection
+# <A Server FQDN or peer name
+# <p Server port number of the last server or peer connection
+# <la Local IP address of the last server or peer connection
+# <lp Local port number of the last server or peer connection
+# <qos Server connection TOS/DSCP value set by Squid
+# <nfmark Server connection netfilter mark set by Squid
+#
+# Time related format codes:
+#
+# ts Seconds since epoch
+# tu subsecond time (milliseconds)
+# tl Local time. Optional strftime format argument
+# default %d/%b/%Y:%H:%M:%S %z
+# tg GMT time. Optional strftime format argument
+# default %d/%b/%Y:%H:%M:%S %z
+# tr Response time (milliseconds)
+# dt Total time spent making DNS lookups (milliseconds)
+# tS Approximate master transaction start time in
+# <full seconds since epoch>.<fractional seconds> format.
+# Currently, Squid considers the master transaction
+# started when a complete HTTP request header initiating
+# the transaction is received from the client. This is
+# the same value that Squid uses to calculate transaction
+# response time when logging %tr to access.log. Currently,
+# Squid uses millisecond resolution for %tS values,
+# similar to the default access.log "current time" field
+# (%ts.%03tu).
+#
+# Access Control related format codes:
+#
+# et Tag returned by external acl
+# ea Log string returned by external acl
+# un User name (any available)
+# ul User name from authentication
+# ue User name from external acl helper
+# ui User name from ident
+# un A user name. Expands to the first available name
+# from the following list of information sources:
+# - authenticated user name, like %ul
+# - user name supplied by an external ACL, like %ue
+# - SSL client name, like %us
+# - ident user name, like %ui
+# credentials Client credentials. The exact meaning depends on
+# the authentication scheme: For Basic authentication,
+# it is the password; for Digest, the realm sent by the
+# client; for NTLM and Negotiate, the client challenge
+# or client credentials prefixed with "YR " or "KK ".
+#
+# HTTP related format codes:
+#
+# REQUEST
+#
+# [http::]rm Request method (GET/POST etc)
+# [http::]>rm Request method from client
+# [http::]<rm Request method sent to server or peer
+# [http::]ru Request URL from client (historic, filtered for logging)
+# [http::]>ru Request URL from client
+# [http::]<ru Request URL sent to server or peer
+# [http::]>rs Request URL scheme from client
+# [http::]<rs Request URL scheme sent to server or peer
+# [http::]>rd Request URL domain from client
+# [http::]<rd Request URL domain sent to server or peer
+# [http::]>rP Request URL port from client
+# [http::]<rP Request URL port sent to server or peer
+# [http::]rp Request URL path excluding hostname
+# [http::]>rp Request URL path excluding hostname from client
+# [http::]<rp Request URL path excluding hostname sent to server or peer
+# [http::]rv Request protocol version
+# [http::]>rv Request protocol version from client
+# [http::]<rv Request protocol version sent to server or peer
+#
+# [http::]>h Original received request header.
+# Usually differs from the request header sent by
+# Squid, although most fields are often preserved.
+# Accepts optional header field name/value filter
+# argument using name[:[separator]element] format.
+# [http::]>ha Received request header after adaptation and
+# redirection (pre-cache REQMOD vectoring point).
+# Usually differs from the request header sent by
+# Squid, although most fields are often preserved.
+# Optional header name argument as for >h
+#
+#
+# RESPONSE
+#
+# [http::]<Hs HTTP status code received from the next hop
+# [http::]>Hs HTTP status code sent to the client
+#
+# [http::]<h Reply header. Optional header name argument
+# as for >h
+#
+# [http::]mt MIME content type
+#
+#
+# SIZE COUNTERS
+#
+# [http::]st Total size of request + reply traffic with client
+# [http::]>st Total size of request received from client.
+# Excluding chunked encoding bytes.
+# [http::]<st Total size of reply sent to client (after adaptation)
+#
+# [http::]>sh Size of request headers received from client
+# [http::]<sh Size of reply headers sent to client (after adaptation)
+#
+# [http::]<sH Reply high offset sent
+# [http::]<sS Upstream object size
+#
+# [http::]<bs Number of HTTP-equivalent message body bytes
+# received from the next hop, excluding chunked
+# transfer encoding and control messages.
+# Generated FTP/Gopher listings are treated as
+# received bodies.
+#
+#
+# TIMING
+#
+# [http::]<pt Peer response time in milliseconds. The timer starts
+# when the last request byte is sent to the next hop
+# and stops when the last response byte is received.
+# [http::]<tt Total time in milliseconds. The timer
+# starts with the first connect request (or write I/O)
+# sent to the first selected peer. The timer stops
+# with the last I/O with the last peer.
+#
+# Squid handling related format codes:
+#
+# Ss Squid request status (TCP_MISS etc)
+# Sh Squid hierarchy status (DEFAULT_PARENT etc)
+#
+# SSL-related format codes:
+#
+# ssl::bump_mode SslBump decision for the transaction:
+#
+# For CONNECT requests that initiated bumping of
+# a connection and for any request received on
+# an already bumped connection, Squid logs the
+# corresponding SslBump mode ("server-first" or
+# "client-first"). See the ssl_bump option for
+# more information about these modes.
+#
+# A "none" token is logged for requests that
+# triggered "ssl_bump" ACL evaluation matching
+# either a "none" rule or no rules at all.
+#
+# In all other cases, a single dash ("-") is
+# logged.
+#
+# ssl::>sni SSL client SNI sent to Squid. Available only
+# after the peek, stare, or splice SSL bumping
+# actions.
+#
+# If ICAP is enabled, the following code becomes available (as
+# well as ICAP log codes documented with the icap_log option):
+#
+# icap::tt Total ICAP processing time for the HTTP
+# transaction. The timer ticks when ICAP
+# ACLs are checked and when ICAP
+# transaction is in progress.
+#
+# If adaptation is enabled the following three codes become available:
+#
+# adapt::<last_h The header of the last ICAP response or
+# meta-information from the last eCAP
+# transaction related to the HTTP transaction.
+# Like <h, accepts an optional header name
+# argument.
+#
+# adapt::sum_trs Summed adaptation transaction response
+# times recorded as a comma-separated list in
+# the order of transaction start time. Each time
+# value is recorded as an integer number,
+# representing response time of one or more
+# adaptation (ICAP or eCAP) transaction in
+# milliseconds. When a failed transaction is
+# being retried or repeated, its time is not
+# logged individually but added to the
+# replacement (next) transaction. See also:
+# adapt::all_trs.
+#
+# adapt::all_trs All adaptation transaction response times.
+# Same as adaptation_strs but response times of
+# individual transactions are never added
+# together. Instead, all transaction response
+# times are recorded individually.
+#
+# You can prefix adapt::*_trs format codes with adaptation
+# service name in curly braces to record response time(s) specific
+# to that service. For example: %{my_service}adapt::sum_trs
+#
+# If SSL is enabled, the following formating codes become available:
+#
+# %ssl::>cert_subject The Subject field of the received client
+# SSL certificate or a dash ('-') if Squid has
+# received an invalid/malformed certificate or
+# no certificate at all. Consider encoding the
+# logged value because Subject often has spaces.
+#
+# %ssl::>cert_issuer The Issuer field of the received client
+# SSL certificate or a dash ('-') if Squid has
+# received an invalid/malformed certificate or
+# no certificate at all. Consider encoding the
+# logged value because Issuer often has spaces.
+#
+# The default formats available (which do not need re-defining) are:
+#
+#logformat squid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt
+#logformat common %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st %Ss:%Sh
+#logformat combined %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st "%{Referer}>h" "%{User-Agent}>h" %Ss:%Sh
+#logformat referrer %ts.%03tu %>a %{Referer}>h %ru
+#logformat useragent %>a [%tl] "%{User-Agent}>h"
+#
+# NOTE: When the log_mime_hdrs directive is set to ON.
+# The squid, common and combined formats have a safely encoded copy
+# of the mime headers appended to each line within a pair of brackets.
+#
+# NOTE: The common and combined formats are not quite true to the Apache definition.
+# The logs from Squid contain an extra status and hierarchy code appended.
+#
+#Default:
+# The format definitions squid, common, combined, referrer, useragent are built in.
+
+# TAG: access_log
+# Configures whether and how Squid logs HTTP and ICP transactions.
+# If access logging is enabled, a single line is logged for every
+# matching HTTP or ICP request. The recommended directive formats are:
+#
+# access_log <module>:<place> [option ...] [acl acl ...]
+# access_log none [acl acl ...]
+#
+# The following directive format is accepted but may be deprecated:
+# access_log <module>:<place> [<logformat name> [acl acl ...]]
+#
+# In most cases, the first ACL name must not contain the '=' character
+# and should not be equal to an existing logformat name. You can always
+# start with an 'all' ACL to work around those restrictions.
+#
+# Will log to the specified module:place using the specified format (which
+# must be defined in a logformat directive) those entries which match
+# ALL the acl's specified (which must be defined in acl clauses).
+# If no acl is specified, all requests will be logged to this destination.
+#
+# ===== Available options for the recommended directive format =====
+#
+# logformat=name Names log line format (either built-in or
+# defined by a logformat directive). Defaults
+# to 'squid'.
+#
+# buffer-size=64KB Defines approximate buffering limit for log
+# records (see buffered_logs). Squid should not
+# keep more than the specified size and, hence,
+# should flush records before the buffer becomes
+# full to avoid overflows under normal
+# conditions (the exact flushing algorithm is
+# module-dependent though). The on-error option
+# controls overflow handling.
+#
+# on-error=die|drop Defines action on unrecoverable errors. The
+# 'drop' action ignores (i.e., does not log)
+# affected log records. The default 'die' action
+# kills the affected worker. The drop action
+# support has not been tested for modules other
+# than tcp.
+#
+# ===== Modules Currently available =====
+#
+# none Do not log any requests matching these ACL.
+# Do not specify Place or logformat name.
+#
+# stdio Write each log line to disk immediately at the completion of
+# each request.
+# Place: the filename and path to be written.
+#
+# daemon Very similar to stdio. But instead of writing to disk the log
+# line is passed to a daemon helper for asychronous handling instead.
+# Place: varies depending on the daemon.
+#
+# log_file_daemon Place: the file name and path to be written.
+#
+# syslog To log each request via syslog facility.
+# Place: The syslog facility and priority level for these entries.
+# Place Format: facility.priority
+#
+# where facility could be any of:
+# authpriv, daemon, local0 ... local7 or user.
+#
+# And priority could be any of:
+# err, warning, notice, info, debug.
+#
+# udp To send each log line as text data to a UDP receiver.
+# Place: The destination host name or IP and port.
+# Place Format: //host:port
+#
+# tcp To send each log line as text data to a TCP receiver.
+# Lines may be accumulated before sending (see buffered_logs).
+# Place: The destination host name or IP and port.
+# Place Format: //host:port
+#
+# Default:
+# access_log daemon:/var/log/squid/access.log squid
+#Default:
+# access_log daemon:/var/log/squid/access.log squid
+
+# TAG: icap_log
+# ICAP log files record ICAP transaction summaries, one line per
+# transaction.
+#
+# The icap_log option format is:
+# icap_log <filepath> [<logformat name> [acl acl ...]]
+# icap_log none [acl acl ...]]
+#
+# Please see access_log option documentation for details. The two
+# kinds of logs share the overall configuration approach and many
+# features.
+#
+# ICAP processing of a single HTTP message or transaction may
+# require multiple ICAP transactions. In such cases, multiple
+# ICAP transaction log lines will correspond to a single access
+# log line.
+#
+# ICAP log supports many access.log logformat %codes. In ICAP context,
+# HTTP message-related %codes are applied to the HTTP message embedded
+# in an ICAP message. Logformat "%http::>..." codes are used for HTTP
+# messages embedded in ICAP requests while "%http::<..." codes are used
+# for HTTP messages embedded in ICAP responses. For example:
+#
+# http::>h To-be-adapted HTTP message headers sent by Squid to
+# the ICAP service. For REQMOD transactions, these are
+# HTTP request headers. For RESPMOD, these are HTTP
+# response headers, but Squid currently cannot log them
+# (i.e., %http::>h will expand to "-" for RESPMOD).
+#
+# http::<h Adapted HTTP message headers sent by the ICAP
+# service to Squid (i.e., HTTP request headers in regular
+# REQMOD; HTTP response headers in RESPMOD and during
+# request satisfaction in REQMOD).
+#
+# ICAP OPTIONS transactions do not embed HTTP messages.
+#
+# Several logformat codes below deal with ICAP message bodies. An ICAP
+# message body, if any, typically includes a complete HTTP message
+# (required HTTP headers plus optional HTTP message body). When
+# computing HTTP message body size for these logformat codes, Squid
+# either includes or excludes chunked encoding overheads; see
+# code-specific documentation for details.
+#
+# For Secure ICAP services, all size-related information is currently
+# computed before/after TLS encryption/decryption, as if TLS was not
+# in use at all.
+#
+# The following format codes are also available for ICAP logs:
+#
+# icap::<A ICAP server IP address. Similar to <A.
+#
+# icap::<service_name ICAP service name from the icap_service
+# option in Squid configuration file.
+#
+# icap::ru ICAP Request-URI. Similar to ru.
+#
+# icap::rm ICAP request method (REQMOD, RESPMOD, or
+# OPTIONS). Similar to existing rm.
+#
+# icap::>st The total size of the ICAP request sent to the ICAP
+# server (ICAP headers + ICAP body), including chunking
+# metadata (if any).
+#
+# icap::<st The total size of the ICAP response received from the
+# ICAP server (ICAP headers + ICAP body), including
+# chunking metadata (if any).
+#
+# icap::<bs The size of the ICAP response body received from the
+# ICAP server, excluding chunking metadata (if any).
+#
+# icap::tr Transaction response time (in
+# milliseconds). The timer starts when
+# the ICAP transaction is created and
+# stops when the transaction is completed.
+# Similar to tr.
+#
+# icap::tio Transaction I/O time (in milliseconds). The
+# timer starts when the first ICAP request
+# byte is scheduled for sending. The timers
+# stops when the last byte of the ICAP response
+# is received.
+#
+# icap::to Transaction outcome: ICAP_ERR* for all
+# transaction errors, ICAP_OPT for OPTION
+# transactions, ICAP_ECHO for 204
+# responses, ICAP_MOD for message
+# modification, and ICAP_SAT for request
+# satisfaction. Similar to Ss.
+#
+# icap::Hs ICAP response status code. Similar to Hs.
+#
+# icap::>h ICAP request header(s). Similar to >h.
+#
+# icap::<h ICAP response header(s). Similar to <h.
+#
+# The default ICAP log format, which can be used without an explicit
+# definition, is called icap_squid:
+#
+#logformat icap_squid %ts.%03tu %6icap::tr %>A %icap::to/%03icap::Hs %icap::<st %icap::rm %icap::ru %un -/%icap::<A -
+#
+# See also: logformat and %adapt::<last_h
+#Default:
+# none
+
+# TAG: logfile_daemon
+# Specify the path to the logfile-writing daemon. This daemon is
+# used to write the access and store logs, if configured.
+#
+# Squid sends a number of commands to the log daemon:
+# L<data>\n - logfile data
+# R\n - rotate file
+# T\n - truncate file
+# O\n - reopen file
+# F\n - flush file
+# r<n>\n - set rotate count to <n>
+# b<n>\n - 1 = buffer output, 0 = don't buffer output
+#
+# No responses is expected.
+#Default:
+# logfile_daemon /usr/lib/squid/log_file_daemon
+
+# TAG: stats_collection allow|deny acl acl...
+# This options allows you to control which requests gets accounted
+# in performance counters.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow logging for all transactions.
+
+# TAG: cache_store_log
+# Logs the activities of the storage manager. Shows which
+# objects are ejected from the cache, and which objects are
+# saved and for how long.
+# There are not really utilities to analyze this data, so you can safely
+# disable it (the default).
+#
+# Store log uses modular logging outputs. See access_log for the list
+# of modules supported.
+#
+# Example:
+# cache_store_log stdio:/var/log/squid/store.log
+# cache_store_log daemon:/var/log/squid/store.log
+#Default:
+# none
+
+# TAG: cache_swap_state
+# Location for the cache "swap.state" file. This index file holds
+# the metadata of objects saved on disk. It is used to rebuild
+# the cache during startup. Normally this file resides in each
+# 'cache_dir' directory, but you may specify an alternate
+# pathname here. Note you must give a full filename, not just
+# a directory. Since this is the index for the whole object
+# list you CANNOT periodically rotate it!
+#
+# If %s can be used in the file name it will be replaced with a
+# a representation of the cache_dir name where each / is replaced
+# with '.'. This is needed to allow adding/removing cache_dir
+# lines when cache_swap_log is being used.
+#
+# If have more than one 'cache_dir', and %s is not used in the name
+# these swap logs will have names such as:
+#
+# cache_swap_log.00
+# cache_swap_log.01
+# cache_swap_log.02
+#
+# The numbered extension (which is added automatically)
+# corresponds to the order of the 'cache_dir' lines in this
+# configuration file. If you change the order of the 'cache_dir'
+# lines in this file, these index files will NOT correspond to
+# the correct 'cache_dir' entry (unless you manually rename
+# them). We recommend you do NOT use this option. It is
+# better to keep these index files in each 'cache_dir' directory.
+#Default:
+# Store the journal inside its cache_dir
+
+# TAG: logfile_rotate
+# Specifies the number of logfile rotations to make when you
+# type 'squid -k rotate'. The default is 10, which will rotate
+# with extensions 0 through 9. Setting logfile_rotate to 0 will
+# disable the file name rotation, but the logfiles are still closed
+# and re-opened. This will enable you to rename the logfiles
+# yourself just before sending the rotate signal.
+#
+# Note, the 'squid -k rotate' command normally sends a USR1
+# signal to the running squid process. In certain situations
+# (e.g. on Linux with Async I/O), USR1 is used for other
+# purposes, so -k rotate uses another signal. It is best to get
+# in the habit of using 'squid -k rotate' instead of 'kill -USR1
+# <pid>'.
+#
+# Note, from Squid-3.1 this option is only a default for cache.log,
+# that log can be rotated separately by using debug_options.
+#
+# Note2, for Debian/Linux the default of logfile_rotate is
+# zero, since it includes external logfile-rotation methods.
+#Default:
+# logfile_rotate 0
+
+# TAG: mime_table
+# Path to Squid's icon configuration file.
+#
+# You shouldn't need to change this, but the default file contains
+# examples and formatting information if you do.
+#Default:
+# mime_table /usr/share/squid/mime.conf
+
+# TAG: log_mime_hdrs on|off
+# The Cache can record both the request and the response MIME
+# headers for each HTTP transaction. The headers are encoded
+# safely and will appear as two bracketed fields at the end of
+# the access log (for either the native or httpd-emulated log
+# formats). To enable this logging set log_mime_hdrs to 'on'.
+#Default:
+# log_mime_hdrs off
+
+# TAG: pid_filename
+# A filename to write the process-id to. To disable, enter "none".
+#Default:
+# pid_filename /var/run/squid.pid
+
+# TAG: client_netmask
+# A netmask for client addresses in logfiles and cachemgr output.
+# Change this to protect the privacy of your cache clients.
+# A netmask of 255.255.255.0 will log all IP's in that range with
+# the last digit set to '0'.
+#Default:
+# Log full client IP address
+
+# TAG: strip_query_terms
+# By default, Squid strips query terms from requested URLs before
+# logging. This protects your user's privacy and reduces log size.
+#
+# When investigating HIT/MISS or other caching behaviour you
+# will need to disable this to see the full URL used by Squid.
+#Default:
+# strip_query_terms on
+
+# TAG: buffered_logs on|off
+# Whether to write/send access_log records ASAP or accumulate them and
+# then write/send them in larger chunks. Buffering may improve
+# performance because it decreases the number of I/Os. However,
+# buffering increases the delay before log records become available to
+# the final recipient (e.g., a disk file or logging daemon) and,
+# hence, increases the risk of log records loss.
+#
+# Note that even when buffered_logs are off, Squid may have to buffer
+# records if it cannot write/send them immediately due to pending I/Os
+# (e.g., the I/O writing the previous log record) or connectivity loss.
+#
+# Currently honored by 'daemon' and 'tcp' access_log modules only.
+#Default:
+# buffered_logs off
+
+# TAG: netdb_filename
+# Where Squid stores it's netdb journal.
+# When enabled this journal preserves netdb state between restarts.
+#
+# To disable, enter "none".
+#Default:
+# netdb_filename stdio:/var/log/squid/netdb.state
+
+# OPTIONS FOR TROUBLESHOOTING
+# -----------------------------------------------------------------------------
+
+# TAG: cache_log
+# Squid administrative logging file.
+#
+# This is where general information about Squid behavior goes. You can
+# increase the amount of data logged to this file and how often it is
+# rotated with "debug_options"
+#Default:
+# cache_log /var/log/squid/cache.log
+
+# TAG: debug_options
+# Logging options are set as section,level where each source file
+# is assigned a unique section. Lower levels result in less
+# output, Full debugging (level 9) can result in a very large
+# log file, so be careful.
+#
+# The magic word "ALL" sets debugging levels for all sections.
+# The default is to run with "ALL,1" to record important warnings.
+#
+# The rotate=N option can be used to keep more or less of these logs
+# than would otherwise be kept by logfile_rotate.
+# For most uses a single log should be enough to monitor current
+# events affecting Squid.
+#Default:
+# Log all critical and important messages.
+
+# TAG: coredump_dir
+# By default Squid leaves core files in the directory from where
+# it was started. If you set 'coredump_dir' to a directory
+# that exists, Squid will chdir() to that directory at startup
+# and coredump files will be left there.
+#
+#Default:
+# Use the directory from where Squid was started.
+#
+
+# Leave coredumps in the first cache dir
+coredump_dir /var/spool/squid
+
+# OPTIONS FOR FTP GATEWAYING
+# -----------------------------------------------------------------------------
+
+# TAG: ftp_user
+# If you want the anonymous login password to be more informative
+# (and enable the use of picky FTP servers), set this to something
+# reasonable for your domain, like wwwuser@somewhere.net
+#
+# The reason why this is domainless by default is the
+# request can be made on the behalf of a user in any domain,
+# depending on how the cache is used.
+# Some FTP server also validate the email address is valid
+# (for example perl.com).
+#Default:
+# ftp_user Squid@
+
+# TAG: ftp_passive
+# If your firewall does not allow Squid to use passive
+# connections, turn off this option.
+#
+# Use of ftp_epsv_all option requires this to be ON.
+#Default:
+# ftp_passive on
+
+# TAG: ftp_epsv_all
+# FTP Protocol extensions permit the use of a special "EPSV ALL" command.
+#
+# NATs may be able to put the connection on a "fast path" through the
+# translator, as the EPRT command will never be used and therefore,
+# translation of the data portion of the segments will never be needed.
+#
+# When a client only expects to do two-way FTP transfers this may be
+# useful.
+# If squid finds that it must do a three-way FTP transfer after issuing
+# an EPSV ALL command, the FTP session will fail.
+#
+# If you have any doubts about this option do not use it.
+# Squid will nicely attempt all other connection methods.
+#
+# Requires ftp_passive to be ON (default) for any effect.
+#Default:
+# ftp_epsv_all off
+
+# TAG: ftp_epsv
+# FTP Protocol extensions permit the use of a special "EPSV" command.
+#
+# NATs may be able to put the connection on a "fast path" through the
+# translator using EPSV, as the EPRT command will never be used
+# and therefore, translation of the data portion of the segments
+# will never be needed.
+#
+# EPSV is often required to interoperate with FTP servers on IPv6
+# networks. On the other hand, it may break some IPv4 servers.
+#
+# By default, EPSV may try EPSV with any FTP server. To fine tune
+# that decision, you may restrict EPSV to certain clients or servers
+# using ACLs:
+#
+# ftp_epsv allow|deny al1 acl2 ...
+#
+# WARNING: Disabling EPSV may cause problems with external NAT and IPv6.
+#
+# Only fast ACLs are supported.
+# Requires ftp_passive to be ON (default) for any effect.
+#Default:
+# none
+
+# TAG: ftp_eprt
+# FTP Protocol extensions permit the use of a special "EPRT" command.
+#
+# This extension provides a protocol neutral alternative to the
+# IPv4-only PORT command. When supported it enables active FTP data
+# channels over IPv6 and efficient NAT handling.
+#
+# Turning this OFF will prevent EPRT being attempted and will skip
+# straight to using PORT for IPv4 servers.
+#
+# Some devices are known to not handle this extension correctly and
+# may result in crashes. Devices which suport EPRT enough to fail
+# cleanly will result in Squid attempting PORT anyway. This directive
+# should only be disabled when EPRT results in device failures.
+#
+# WARNING: Doing so will convert Squid back to the old behavior with all
+# the related problems with external NAT devices/layers and IPv4-only FTP.
+#Default:
+# ftp_eprt on
+
+# TAG: ftp_sanitycheck
+# For security and data integrity reasons Squid by default performs
+# sanity checks of the addresses of FTP data connections ensure the
+# data connection is to the requested server. If you need to allow
+# FTP connections to servers using another IP address for the data
+# connection turn this off.
+#Default:
+# ftp_sanitycheck on
+
+# TAG: ftp_telnet_protocol
+# The FTP protocol is officially defined to use the telnet protocol
+# as transport channel for the control connection. However, many
+# implementations are broken and does not respect this aspect of
+# the FTP protocol.
+#
+# If you have trouble accessing files with ASCII code 255 in the
+# path or similar problems involving this ASCII code you can
+# try setting this directive to off. If that helps, report to the
+# operator of the FTP server in question that their FTP server
+# is broken and does not follow the FTP standard.
+#Default:
+# ftp_telnet_protocol on
+
+# OPTIONS FOR EXTERNAL SUPPORT PROGRAMS
+# -----------------------------------------------------------------------------
+
+# TAG: diskd_program
+# Specify the location of the diskd executable.
+# Note this is only useful if you have compiled in
+# diskd as one of the store io modules.
+#Default:
+# diskd_program /usr/lib/squid/diskd
+
+# TAG: unlinkd_program
+# Specify the location of the executable for file deletion process.
+#Default:
+# unlinkd_program /usr/lib/squid/unlinkd
+
+# TAG: pinger_program
+# Specify the location of the executable for the pinger process.
+#Default:
+# pinger_program /usr/lib/squid/pinger
+
+# TAG: pinger_enable
+# Control whether the pinger is active at run-time.
+# Enables turning ICMP pinger on and off with a simple
+# squid -k reconfigure.
+#Default:
+# pinger_enable on
+
+# OPTIONS FOR URL REWRITING
+# -----------------------------------------------------------------------------
+
+# TAG: url_rewrite_program
+# Specify the location of the executable URL rewriter to use.
+# Since they can perform almost any function there isn't one included.
+#
+# For each requested URL, the rewriter will receive on line with the format
+#
+# [channel-ID <SP>] URL [<SP> extras]<NL>
+#
+# See url_rewrite_extras on how to send "extras" with optional values to
+# the helper.
+# After processing the request the helper must reply using the following format:
+#
+# [channel-ID <SP>] result [<SP> kv-pairs]
+#
+# The result code can be:
+#
+# OK status=30N url="..."
+# Redirect the URL to the one supplied in 'url='.
+# 'status=' is optional and contains the status code to send
+# the client in Squids HTTP response. It must be one of the
+# HTTP redirect status codes: 301, 302, 303, 307, 308.
+# When no status is given Squid will use 302.
+#
+# OK rewrite-url="..."
+# Rewrite the URL to the one supplied in 'rewrite-url='.
+# The new URL is fetched directly by Squid and returned to
+# the client as the response to its request.
+#
+# OK
+# When neither of url= and rewrite-url= are sent Squid does
+# not change the URL.
+#
+# ERR
+# Do not change the URL.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified. The 'message=' key name is
+# reserved for delivering a log message.
+#
+#
+# In addition to the above kv-pairs Squid also understands the following
+# optional kv-pairs received from URL rewriters:
+# clt_conn_tag=TAG
+# Associates a TAG with the client TCP connection.
+# The TAG is treated as a regular annotation but persists across
+# future requests on the client connection rather than just the
+# current request. A helper may update the TAG during subsequent
+# requests be returning a new kv-pair.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+# WARNING: URL re-writing ability should be avoided whenever possible.
+# Use the URL redirect form of response instead.
+#
+# Re-write creates a difference in the state held by the client
+# and server. Possibly causing confusion when the server response
+# contains snippets of its view state. Embeded URLs, response
+# and content Location headers, etc. are not re-written by this
+# interface.
+#
+# By default, a URL rewriter is not used.
+#Default:
+# none
+
+# TAG: url_rewrite_children
+# The maximum number of redirector processes to spawn. If you limit
+# it too few Squid will have to wait for them to process a backlog of
+# URLs, slowing it down. If you allow too many they will use RAM
+# and other system resources noticably.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=
+#
+# Sets a minimum of how many processes are to be spawned when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few will cause an initial slowdown in traffic as Squid
+# attempts to simultaneously spawn enough processes to cope.
+#
+# idle=
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each redirector helper can handle in
+# parallel. Defaults to 0 which indicates the redirector
+# is a old-style single threaded redirector.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# an ID in front of the request/response. The ID from the request
+# must be echoed back with the response to that request.
+#Default:
+# url_rewrite_children 20 startup=0 idle=1 concurrency=0
+
+# TAG: url_rewrite_host_header
+# To preserve same-origin security policies in browsers and
+# prevent Host: header forgery by redirectors Squid rewrites
+# any Host: header in redirected requests.
+#
+# If you are running an accelerator this may not be a wanted
+# effect of a redirector. This directive enables you disable
+# Host: alteration in reverse-proxy traffic.
+#
+# WARNING: Entries are cached on the result of the URL rewriting
+# process, so be careful if you have domain-virtual hosts.
+#
+# WARNING: Squid and other software verifies the URL and Host
+# are matching, so be careful not to relay through other proxies
+# or inspecting firewalls with this disabled.
+#Default:
+# url_rewrite_host_header on
+
+# TAG: url_rewrite_access
+# If defined, this access list specifies which requests are
+# sent to the redirector processes.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: url_rewrite_bypass
+# When this is 'on', a request will not go through the
+# redirector if all the helpers are busy. If this is 'off'
+# and the redirector queue grows too large, Squid will exit
+# with a FATAL error and ask you to increase the number of
+# redirectors. You should only enable this if the redirectors
+# are not critical to your caching system. If you use
+# redirectors for access control, and you enable this option,
+# users may have access to pages they should not
+# be allowed to request.
+#Default:
+# url_rewrite_bypass off
+
+# TAG: url_rewrite_extras
+# Specifies a string to be append to request line format for the
+# rewriter helper. "Quoted" format values may contain spaces and
+# logformat %macros. In theory, any logformat %macro can be used.
+# In practice, a %macro expands as a dash (-) if the helper request is
+# sent before the required macro information is available to Squid.
+#Default:
+# url_rewrite_extras "%>a/%>A %un %>rm myip=%la myport=%lp"
+
+# OPTIONS FOR STORE ID
+# -----------------------------------------------------------------------------
+
+# TAG: store_id_program
+# Specify the location of the executable StoreID helper to use.
+# Since they can perform almost any function there isn't one included.
+#
+# For each requested URL, the helper will receive one line with the format
+#
+# [channel-ID <SP>] URL [<SP> extras]<NL>
+#
+#
+# After processing the request the helper must reply using the following format:
+#
+# [channel-ID <SP>] result [<SP> kv-pairs]
+#
+# The result code can be:
+#
+# OK store-id="..."
+# Use the StoreID supplied in 'store-id='.
+#
+# ERR
+# The default is to use HTTP request URL as the store ID.
+#
+# BH
+# An internal error occured in the helper, preventing
+# a result being identified.
+#
+# In addition to the above kv-pairs Squid also understands the following
+# optional kv-pairs received from URL rewriters:
+# clt_conn_tag=TAG
+# Associates a TAG with the client TCP connection.
+# Please see url_rewrite_program related documentation for this
+# kv-pair
+#
+# Helper programs should be prepared to receive and possibly ignore
+# additional whitespace-separated tokens on each input line.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+# NOTE: when using StoreID refresh_pattern will apply to the StoreID
+# returned from the helper and not the URL.
+#
+# WARNING: Wrong StoreID value returned by a careless helper may result
+# in the wrong cached response returned to the user.
+#
+# By default, a StoreID helper is not used.
+#Default:
+# none
+
+# TAG: store_id_extras
+# Specifies a string to be append to request line format for the
+# StoreId helper. "Quoted" format values may contain spaces and
+# logformat %macros. In theory, any logformat %macro can be used.
+# In practice, a %macro expands as a dash (-) if the helper request is
+# sent before the required macro information is available to Squid.
+#Default:
+# store_id_extras "%>a/%>A %un %>rm myip=%la myport=%lp"
+
+# TAG: store_id_children
+# The maximum number of StoreID helper processes to spawn. If you limit
+# it too few Squid will have to wait for them to process a backlog of
+# requests, slowing it down. If you allow too many they will use RAM
+# and other system resources noticably.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=
+#
+# Sets a minimum of how many processes are to be spawned when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few will cause an initial slowdown in traffic as Squid
+# attempts to simultaneously spawn enough processes to cope.
+#
+# idle=
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each storeID helper can handle in
+# parallel. Defaults to 0 which indicates the helper
+# is a old-style single threaded program.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# an ID in front of the request/response. The ID from the request
+# must be echoed back with the response to that request.
+#Default:
+# store_id_children 20 startup=0 idle=1 concurrency=0
+
+# TAG: store_id_access
+# If defined, this access list specifies which requests are
+# sent to the StoreID processes. By default all requests
+# are sent.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: store_id_bypass
+# When this is 'on', a request will not go through the
+# helper if all helpers are busy. If this is 'off'
+# and the helper queue grows too large, Squid will exit
+# with a FATAL error and ask you to increase the number of
+# helpers. You should only enable this if the helperss
+# are not critical to your caching system. If you use
+# helpers for critical caching components, and you enable this
+# option, users may not get objects from cache.
+#Default:
+# store_id_bypass on
+
+# OPTIONS FOR TUNING THE CACHE
+# -----------------------------------------------------------------------------
+
+# TAG: cache
+# Requests denied by this directive will not be served from the cache
+# and their responses will not be stored in the cache. This directive
+# has no effect on other transactions and on already cached responses.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# This and the two other similar caching directives listed below are
+# checked at different transaction processing stages, have different
+# access to response information, affect different cache operations,
+# and differ in slow ACLs support:
+#
+# * cache: Checked before Squid makes a hit/miss determination.
+# No access to reply information!
+# Denies both serving a hit and storing a miss.
+# Supports both fast and slow ACLs.
+# * send_hit: Checked after a hit was detected.
+# Has access to reply (hit) information.
+# Denies serving a hit only.
+# Supports fast ACLs only.
+# * store_miss: Checked before storing a cachable miss.
+# Has access to reply (miss) information.
+# Denies storing a miss only.
+# Supports fast ACLs only.
+#
+# If you are not sure which of the three directives to use, apply the
+# following decision logic:
+#
+# * If your ACL(s) are of slow type _and_ need response info, redesign.
+# Squid does not support that particular combination at this time.
+# Otherwise:
+# * If your directive ACL(s) are of slow type, use "cache"; and/or
+# * if your directive ACL(s) need no response info, use "cache".
+# Otherwise:
+# * If you do not want the response cached, use store_miss; and/or
+# * if you do not want a hit on a cached response, use send_hit.
+#Default:
+# By default, this directive is unused and has no effect.
+
+# TAG: send_hit
+# Responses denied by this directive will not be served from the cache
+# (but may still be cached, see store_miss). This directive has no
+# effect on the responses it allows and on the cached objects.
+#
+# Please see the "cache" directive for a summary of differences among
+# store_miss, send_hit, and cache directives.
+#
+# Unlike the "cache" directive, send_hit only supports fast acl
+# types. See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# For example:
+#
+# # apply custom Store ID mapping to some URLs
+# acl MapMe dstdomain .c.example.com
+# store_id_program ...
+# store_id_access allow MapMe
+#
+# # but prevent caching of special responses
+# # such as 302 redirects that cause StoreID loops
+# acl Ordinary http_status 200-299
+# store_miss deny MapMe !Ordinary
+#
+# # and do not serve any previously stored special responses
+# # from the cache (in case they were already cached before
+# # the above store_miss rule was in effect).
+# send_hit deny MapMe !Ordinary
+#Default:
+# By default, this directive is unused and has no effect.
+
+# TAG: store_miss
+# Responses denied by this directive will not be cached (but may still
+# be served from the cache, see send_hit). This directive has no
+# effect on the responses it allows and on the already cached responses.
+#
+# Please see the "cache" directive for a summary of differences among
+# store_miss, send_hit, and cache directives. See the
+# send_hit directive for a usage example.
+#
+# Unlike the "cache" directive, store_miss only supports fast acl
+# types. See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# By default, this directive is unused and has no effect.
+
+# TAG: max_stale time-units
+# This option puts an upper limit on how stale content Squid
+# will serve from the cache if cache validation fails.
+# Can be overriden by the refresh_pattern max-stale option.
+#Default:
+# max_stale 1 week
+
+# TAG: refresh_pattern
+# usage: refresh_pattern [-i] regex min percent max [options]
+#
+# By default, regular expressions are CASE-SENSITIVE. To make
+# them case-insensitive, use the -i option.
+#
+# 'Min' is the time (in minutes) an object without an explicit
+# expiry time should be considered fresh. The recommended
+# value is 0, any higher values may cause dynamic applications
+# to be erroneously cached unless the application designer
+# has taken the appropriate actions.
+#
+# 'Percent' is a percentage of the objects age (time since last
+# modification age) an object without explicit expiry time
+# will be considered fresh.
+#
+# 'Max' is an upper limit on how long objects without an explicit
+# expiry time will be considered fresh.
+#
+# options: override-expire
+# override-lastmod
+# reload-into-ims
+# ignore-reload
+# ignore-no-store
+# ignore-must-revalidate
+# ignore-private
+# ignore-auth
+# max-stale=NN
+# refresh-ims
+# store-stale
+#
+# override-expire enforces min age even if the server
+# sent an explicit expiry time (e.g., with the
+# Expires: header or Cache-Control: max-age). Doing this
+# VIOLATES the HTTP standard. Enabling this feature
+# could make you liable for problems which it causes.
+#
+# Note: override-expire does not enforce staleness - it only extends
+# freshness / min. If the server returns a Expires time which
+# is longer than your max time, Squid will still consider
+# the object fresh for that period of time.
+#
+# override-lastmod enforces min age even on objects
+# that were modified recently.
+#
+# reload-into-ims changes a client no-cache or ``reload''
+# request for a cached entry into a conditional request using
+# If-Modified-Since and/or If-None-Match headers, provided the
+# cached entry has a Last-Modified and/or a strong ETag header.
+# Doing this VIOLATES the HTTP standard. Enabling this feature
+# could make you liable for problems which it causes.
+#
+# ignore-reload ignores a client no-cache or ``reload''
+# header. Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which
+# it causes.
+#
+# ignore-no-store ignores any ``Cache-control: no-store''
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# ignore-must-revalidate ignores any ``Cache-Control: must-revalidate``
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# ignore-private ignores any ``Cache-control: private''
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# ignore-auth caches responses to requests with authorization,
+# as if the originserver had sent ``Cache-control: public''
+# in the response header. Doing this VIOLATES the HTTP standard.
+# Enabling this feature could make you liable for problems which
+# it causes.
+#
+# refresh-ims causes squid to contact the origin server
+# when a client issues an If-Modified-Since request. This
+# ensures that the client will receive an updated version
+# if one is available.
+#
+# store-stale stores responses even if they don't have explicit
+# freshness or a validator (i.e., Last-Modified or an ETag)
+# present, or if they're already stale. By default, Squid will
+# not cache such responses because they usually can't be
+# reused. Note that such responses will be stale by default.
+#
+# max-stale=NN provide a maximum staleness factor. Squid won't
+# serve objects more stale than this even if it failed to
+# validate the object. Default: use the max_stale global limit.
+#
+# Basically a cached object is:
+#
+# FRESH if expire > now, else STALE
+# STALE if age > max
+# FRESH if lm-factor < percent, else STALE
+# FRESH if age < min
+# else STALE
+#
+# The refresh_pattern lines are checked in the order listed here.
+# The first entry which matches is used. If none of the entries
+# match the default will be used.
+#
+# Note, you must uncomment all the default lines if you want
+# to change one. The default setting is only active if none is
+# used.
+#
+#
+
+#
+# Add any of your own refresh_pattern entries above these.
+#
+refresh_pattern ^ftp: 1440 20% 10080
+refresh_pattern ^gopher: 1440 0% 1440
+refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
+refresh_pattern . 0 20% 4320
+
+# TAG: quick_abort_min (KB)
+#Default:
+# quick_abort_min 16 KB
+
+# TAG: quick_abort_max (KB)
+#Default:
+# quick_abort_max 16 KB
+
+# TAG: quick_abort_pct (percent)
+# The cache by default continues downloading aborted requests
+# which are almost completed (less than 16 KB remaining). This
+# may be undesirable on slow (e.g. SLIP) links and/or very busy
+# caches. Impatient users may tie up file descriptors and
+# bandwidth by repeatedly requesting and immediately aborting
+# downloads.
+#
+# When the user aborts a request, Squid will check the
+# quick_abort values to the amount of data transferred until
+# then.
+#
+# If the transfer has less than 'quick_abort_min' KB remaining,
+# it will finish the retrieval.
+#
+# If the transfer has more than 'quick_abort_max' KB remaining,
+# it will abort the retrieval.
+#
+# If more than 'quick_abort_pct' of the transfer has completed,
+# it will finish the retrieval.
+#
+# If you do not want any retrieval to continue after the client
+# has aborted, set both 'quick_abort_min' and 'quick_abort_max'
+# to '0 KB'.
+#
+# If you want retrievals to always continue if they are being
+# cached set 'quick_abort_min' to '-1 KB'.
+#Default:
+# quick_abort_pct 95
+
+# TAG: read_ahead_gap buffer-size
+# The amount of data the cache will buffer ahead of what has been
+# sent to the client when retrieving an object from another server.
+#Default:
+# read_ahead_gap 16 KB
+
+# TAG: negative_ttl time-units
+# Set the Default Time-to-Live (TTL) for failed requests.
+# Certain types of failures (such as "connection refused" and
+# "404 Not Found") are able to be negatively-cached for a short time.
+# Modern web servers should provide Expires: header, however if they
+# do not this can provide a minimum TTL.
+# The default is not to cache errors with unknown expiry details.
+#
+# Note that this is different from negative caching of DNS lookups.
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#Default:
+# negative_ttl 0 seconds
+
+# TAG: positive_dns_ttl time-units
+# Upper limit on how long Squid will cache positive DNS responses.
+# Default is 6 hours (360 minutes). This directive must be set
+# larger than negative_dns_ttl.
+#Default:
+# positive_dns_ttl 6 hours
+
+# TAG: negative_dns_ttl time-units
+# Time-to-Live (TTL) for negative caching of failed DNS lookups.
+# This also sets the lower cache limit on positive lookups.
+# Minimum value is 1 second, and it is not recommendable to go
+# much below 10 seconds.
+#Default:
+# negative_dns_ttl 1 minutes
+
+# TAG: range_offset_limit size [acl acl...]
+# usage: (size) [units] [[!]aclname]
+#
+# Sets an upper limit on how far (number of bytes) into the file
+# a Range request may be to cause Squid to prefetch the whole file.
+# If beyond this limit, Squid forwards the Range request as it is and
+# the result is NOT cached.
+#
+# This is to stop a far ahead range request (lets say start at 17MB)
+# from making Squid fetch the whole object up to that point before
+# sending anything to the client.
+#
+# Multiple range_offset_limit lines may be specified, and they will
+# be searched from top to bottom on each request until a match is found.
+# The first match found will be used. If no line matches a request, the
+# default limit of 0 bytes will be used.
+#
+# 'size' is the limit specified as a number of units.
+#
+# 'units' specifies whether to use bytes, KB, MB, etc.
+# If no units are specified bytes are assumed.
+#
+# A size of 0 causes Squid to never fetch more than the
+# client requested. (default)
+#
+# A size of 'none' causes Squid to always fetch the object from the
+# beginning so it may cache the result. (2.0 style)
+#
+# 'aclname' is the name of a defined ACL.
+#
+# NP: Using 'none' as the byte value here will override any quick_abort settings
+# that may otherwise apply to the range request. The range request will
+# be fully fetched from start to finish regardless of the client
+# actions. This affects bandwidth usage.
+#Default:
+# none
+
+# TAG: minimum_expiry_time (seconds)
+# The minimum caching time according to (Expires - Date)
+# headers Squid honors if the object can't be revalidated.
+# The default is 60 seconds.
+#
+# In reverse proxy environments it might be desirable to honor
+# shorter object lifetimes. It is most likely better to make
+# your server return a meaningful Last-Modified header however.
+#
+# In ESI environments where page fragments often have short
+# lifetimes, this will often be best set to 0.
+#Default:
+# minimum_expiry_time 60 seconds
+
+# TAG: store_avg_object_size (bytes)
+# Average object size, used to estimate number of objects your
+# cache can hold. The default is 13 KB.
+#
+# This is used to pre-seed the cache index memory allocation to
+# reduce expensive reallocate operations while handling clients
+# traffic. Too-large values may result in memory allocation during
+# peak traffic, too-small values will result in wasted memory.
+#
+# Check the cache manager 'info' report metrics for the real
+# object sizes seen by your Squid before tuning this.
+#Default:
+# store_avg_object_size 13 KB
+
+# TAG: store_objects_per_bucket
+# Target number of objects per bucket in the store hash table.
+# Lowering this value increases the total number of buckets and
+# also the storage maintenance rate. The default is 20.
+#Default:
+# store_objects_per_bucket 20
+
+# HTTP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: request_header_max_size (KB)
+# This specifies the maximum size for HTTP headers in a request.
+# Request headers are usually relatively small (about 512 bytes).
+# Placing a limit on the request header size will catch certain
+# bugs (for example with persistent connections) and possibly
+# buffer-overflow or denial-of-service attacks.
+#Default:
+# request_header_max_size 64 KB
+
+# TAG: reply_header_max_size (KB)
+# This specifies the maximum size for HTTP headers in a reply.
+# Reply headers are usually relatively small (about 512 bytes).
+# Placing a limit on the reply header size will catch certain
+# bugs (for example with persistent connections) and possibly
+# buffer-overflow or denial-of-service attacks.
+#Default:
+# reply_header_max_size 64 KB
+
+# TAG: request_body_max_size (bytes)
+# This specifies the maximum size for an HTTP request body.
+# In other words, the maximum size of a PUT/POST request.
+# A user who attempts to send a request with a body larger
+# than this limit receives an "Invalid Request" error message.
+# If you set this parameter to a zero (the default), there will
+# be no limit imposed.
+#
+# See also client_request_buffer_max_size for an alternative
+# limitation on client uploads which can be configured.
+#Default:
+# No limit.
+
+# TAG: client_request_buffer_max_size (bytes)
+# This specifies the maximum buffer size of a client request.
+# It prevents squid eating too much memory when somebody uploads
+# a large file.
+#Default:
+# client_request_buffer_max_size 512 KB
+
+# TAG: broken_posts
+# A list of ACL elements which, if matched, causes Squid to send
+# an extra CRLF pair after the body of a PUT/POST request.
+#
+# Some HTTP servers has broken implementations of PUT/POST,
+# and rely on an extra CRLF pair sent by some WWW clients.
+#
+# Quote from RFC2616 section 4.1 on this matter:
+#
+# Note: certain buggy HTTP/1.0 client implementations generate an
+# extra CRLF's after a POST request. To restate what is explicitly
+# forbidden by the BNF, an HTTP/1.1 client must not preface or follow
+# a request with an extra CRLF.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Example:
+# acl buggy_server url_regex ^http://....
+# broken_posts allow buggy_server
+#Default:
+# Obey RFC 2616.
+
+# TAG: adaptation_uses_indirect_client on|off
+# Controls whether the indirect client IP address (instead of the direct
+# client IP address) is passed to adaptation services.
+#
+# See also: follow_x_forwarded_for adaptation_send_client_ip
+#Default:
+# adaptation_uses_indirect_client on
+
+# TAG: via on|off
+# If set (default), Squid will include a Via header in requests and
+# replies as required by RFC2616.
+#Default:
+# via on
+
+# TAG: ie_refresh on|off
+# Microsoft Internet Explorer up until version 5.5 Service
+# Pack 1 has an issue with transparent proxies, wherein it
+# is impossible to force a refresh. Turning this on provides
+# a partial fix to the problem, by causing all IMS-REFRESH
+# requests from older IE versions to check the origin server
+# for fresh content. This reduces hit ratio by some amount
+# (~10% in my experience), but allows users to actually get
+# fresh content when they want it. Note because Squid
+# cannot tell if the user is using 5.5 or 5.5SP1, the behavior
+# of 5.5 is unchanged from old versions of Squid (i.e. a
+# forced refresh is impossible). Newer versions of IE will,
+# hopefully, continue to have the new behavior and will be
+# handled based on that assumption. This option defaults to
+# the old Squid behavior, which is better for hit ratios but
+# worse for clients using IE, if they need to be able to
+# force fresh content.
+#Default:
+# ie_refresh off
+
+# TAG: vary_ignore_expire on|off
+# Many HTTP servers supporting Vary gives such objects
+# immediate expiry time with no cache-control header
+# when requested by a HTTP/1.0 client. This option
+# enables Squid to ignore such expiry times until
+# HTTP/1.1 is fully implemented.
+#
+# WARNING: If turned on this may eventually cause some
+# varying objects not intended for caching to get cached.
+#Default:
+# vary_ignore_expire off
+
+# TAG: request_entities
+# Squid defaults to deny GET and HEAD requests with request entities,
+# as the meaning of such requests are undefined in the HTTP standard
+# even if not explicitly forbidden.
+#
+# Set this directive to on if you have clients which insists
+# on sending request entities in GET or HEAD requests. But be warned
+# that there is server software (both proxies and web servers) which
+# can fail to properly process this kind of request which may make you
+# vulnerable to cache pollution attacks if enabled.
+#Default:
+# request_entities off
+
+# TAG: request_header_access
+# Usage: request_header_access header_name allow|deny [!]aclname ...
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#
+# This option replaces the old 'anonymize_headers' and the
+# older 'http_anonymizer' option with something that is much
+# more configurable. A list of ACLs for each header name allows
+# removal of specific header fields under specific conditions.
+#
+# This option only applies to outgoing HTTP request headers (i.e.,
+# headers sent by Squid to the next HTTP hop such as a cache peer
+# or an origin server). The option has no effect during cache hit
+# detection. The equivalent adaptation vectoring point in ICAP
+# terminology is post-cache REQMOD.
+#
+# The option is applied to individual outgoing request header
+# fields. For each request header field F, Squid uses the first
+# qualifying sets of request_header_access rules:
+#
+# 1. Rules with header_name equal to F's name.
+# 2. Rules with header_name 'Other', provided F's name is not
+# on the hard-coded list of commonly used HTTP header names.
+# 3. Rules with header_name 'All'.
+#
+# Within that qualifying rule set, rule ACLs are checked as usual.
+# If ACLs of an "allow" rule match, the header field is allowed to
+# go through as is. If ACLs of a "deny" rule match, the header is
+# removed and request_header_replace is then checked to identify
+# if the removed header has a replacement. If no rules within the
+# set have matching ACLs, the header field is left as is.
+#
+# For example, to achieve the same behavior as the old
+# 'http_anonymizer standard' option, you should use:
+#
+# request_header_access From deny all
+# request_header_access Referer deny all
+# request_header_access User-Agent deny all
+#
+# Or, to reproduce the old 'http_anonymizer paranoid' feature
+# you should use:
+#
+# request_header_access Authorization allow all
+# request_header_access Proxy-Authorization allow all
+# request_header_access Cache-Control allow all
+# request_header_access Content-Length allow all
+# request_header_access Content-Type allow all
+# request_header_access Date allow all
+# request_header_access Host allow all
+# request_header_access If-Modified-Since allow all
+# request_header_access Pragma allow all
+# request_header_access Accept allow all
+# request_header_access Accept-Charset allow all
+# request_header_access Accept-Encoding allow all
+# request_header_access Accept-Language allow all
+# request_header_access Connection allow all
+# request_header_access All deny all
+#
+# HTTP reply headers are controlled with the reply_header_access directive.
+#
+# By default, all headers are allowed (no anonymizing is performed).
+#Default:
+# No limits.
+
+# TAG: reply_header_access
+# Usage: reply_header_access header_name allow|deny [!]aclname ...
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#
+# This option only applies to reply headers, i.e., from the
+# server to the client.
+#
+# This is the same as request_header_access, but in the other
+# direction. Please see request_header_access for detailed
+# documentation.
+#
+# For example, to achieve the same behavior as the old
+# 'http_anonymizer standard' option, you should use:
+#
+# reply_header_access Server deny all
+# reply_header_access WWW-Authenticate deny all
+# reply_header_access Link deny all
+#
+# Or, to reproduce the old 'http_anonymizer paranoid' feature
+# you should use:
+#
+# reply_header_access Allow allow all
+# reply_header_access WWW-Authenticate allow all
+# reply_header_access Proxy-Authenticate allow all
+# reply_header_access Cache-Control allow all
+# reply_header_access Content-Encoding allow all
+# reply_header_access Content-Length allow all
+# reply_header_access Content-Type allow all
+# reply_header_access Date allow all
+# reply_header_access Expires allow all
+# reply_header_access Last-Modified allow all
+# reply_header_access Location allow all
+# reply_header_access Pragma allow all
+# reply_header_access Content-Language allow all
+# reply_header_access Retry-After allow all
+# reply_header_access Title allow all
+# reply_header_access Content-Disposition allow all
+# reply_header_access Connection allow all
+# reply_header_access All deny all
+#
+# HTTP request headers are controlled with the request_header_access directive.
+#
+# By default, all headers are allowed (no anonymizing is
+# performed).
+#Default:
+# No limits.
+
+# TAG: request_header_replace
+# Usage: request_header_replace header_name message
+# Example: request_header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit)
+#
+# This option allows you to change the contents of headers
+# denied with request_header_access above, by replacing them
+# with some fixed string.
+#
+# This only applies to request headers, not reply headers.
+#
+# By default, headers are removed if denied.
+#Default:
+# none
+
+# TAG: reply_header_replace
+# Usage: reply_header_replace header_name message
+# Example: reply_header_replace Server Foo/1.0
+#
+# This option allows you to change the contents of headers
+# denied with reply_header_access above, by replacing them
+# with some fixed string.
+#
+# This only applies to reply headers, not request headers.
+#
+# By default, headers are removed if denied.
+#Default:
+# none
+
+# TAG: request_header_add
+# Usage: request_header_add field-name field-value acl1 [acl2] ...
+# Example: request_header_add X-Client-CA "CA=%ssl::>cert_issuer" all
+#
+# This option adds header fields to outgoing HTTP requests (i.e.,
+# request headers sent by Squid to the next HTTP hop such as a
+# cache peer or an origin server). The option has no effect during
+# cache hit detection. The equivalent adaptation vectoring point
+# in ICAP terminology is post-cache REQMOD.
+#
+# Field-name is a token specifying an HTTP header name. If a
+# standard HTTP header name is used, Squid does not check whether
+# the new header conflicts with any existing headers or violates
+# HTTP rules. If the request to be modified already contains a
+# field with the same name, the old field is preserved but the
+# header field values are not merged.
+#
+# Field-value is either a token or a quoted string. If quoted
+# string format is used, then the surrounding quotes are removed
+# while escape sequences and %macros are processed.
+#
+# In theory, all of the logformat codes can be used as %macros.
+# However, unlike logging (which happens at the very end of
+# transaction lifetime), the transaction may not yet have enough
+# information to expand a macro when the new header value is needed.
+# And some information may already be available to Squid but not yet
+# committed where the macro expansion code can access it (report
+# such instances!). The macro will be expanded into a single dash
+# ('-') in such cases. Not all macros have been tested.
+#
+# One or more Squid ACLs may be specified to restrict header
+# injection to matching requests. As always in squid.conf, all
+# ACLs in an option ACL list must be satisfied for the insertion
+# to happen. The request_header_add option supports fast ACLs
+# only.
+#Default:
+# none
+
+# TAG: note
+# This option used to log custom information about the master
+# transaction. For example, an admin may configure Squid to log
+# which "user group" the transaction belongs to, where "user group"
+# will be determined based on a set of ACLs and not [just]
+# authentication information.
+# Values of key/value pairs can be logged using %{key}note macros:
+#
+# note key value acl ...
+# logformat myFormat ... %{key}note ...
+#Default:
+# none
+
+# TAG: relaxed_header_parser on|off|warn
+# In the default "on" setting Squid accepts certain forms
+# of non-compliant HTTP messages where it is unambiguous
+# what the sending application intended even if the message
+# is not correctly formatted. The messages is then normalized
+# to the correct form when forwarded by Squid.
+#
+# If set to "warn" then a warning will be emitted in cache.log
+# each time such HTTP error is encountered.
+#
+# If set to "off" then such HTTP errors will cause the request
+# or response to be rejected.
+#Default:
+# relaxed_header_parser on
+
+# TAG: collapsed_forwarding (on|off)
+# When enabled, instead of forwarding each concurrent request for
+# the same URL, Squid just sends the first of them. The other, so
+# called "collapsed" requests, wait for the response to the first
+# request and, if it happens to be cachable, use that response.
+# Here, "concurrent requests" means "received after the first
+# request headers were parsed and before the corresponding response
+# headers were parsed".
+#
+# This feature is disabled by default: enabling collapsed
+# forwarding needlessly delays forwarding requests that look
+# cachable (when they are collapsed) but then need to be forwarded
+# individually anyway because they end up being for uncachable
+# content. However, in some cases, such as acceleration of highly
+# cachable content with periodic or grouped expiration times, the
+# gains from collapsing [large volumes of simultaneous refresh
+# requests] outweigh losses from such delays.
+#
+# Squid collapses two kinds of requests: regular client requests
+# received on one of the listening ports and internal "cache
+# revalidation" requests which are triggered by those regular
+# requests hitting a stale cached object. Revalidation collapsing
+# is currently disabled for Squid instances containing SMP-aware
+# disk or memory caches and for Vary-controlled cached objects.
+#Default:
+# collapsed_forwarding off
+
+# TIMEOUTS
+# -----------------------------------------------------------------------------
+
+# TAG: forward_timeout time-units
+# This parameter specifies how long Squid should at most attempt in
+# finding a forwarding path for the request before giving up.
+#Default:
+# forward_timeout 4 minutes
+
+# TAG: connect_timeout time-units
+# This parameter specifies how long to wait for the TCP connect to
+# the requested server or peer to complete before Squid should
+# attempt to find another path where to forward the request.
+#Default:
+# connect_timeout 1 minute
+
+# TAG: peer_connect_timeout time-units
+# This parameter specifies how long to wait for a pending TCP
+# connection to a peer cache. The default is 30 seconds. You
+# may also set different timeout values for individual neighbors
+# with the 'connect-timeout' option on a 'cache_peer' line.
+#Default:
+# peer_connect_timeout 30 seconds
+
+# TAG: read_timeout time-units
+# Applied on peer server connections.
+#
+# After each successful read(), the timeout will be extended by this
+# amount. If no data is read again after this amount of time,
+# the request is aborted and logged with ERR_READ_TIMEOUT.
+#
+# The default is 15 minutes.
+#Default:
+# read_timeout 15 minutes
+
+# TAG: write_timeout time-units
+# This timeout is tracked for all connections that have data
+# available for writing and are waiting for the socket to become
+# ready. After each successful write, the timeout is extended by
+# the configured amount. If Squid has data to write but the
+# connection is not ready for the configured duration, the
+# transaction associated with the connection is terminated. The
+# default is 15 minutes.
+#Default:
+# write_timeout 15 minutes
+
+# TAG: request_timeout
+# How long to wait for complete HTTP request headers after initial
+# connection establishment.
+#Default:
+# request_timeout 5 minutes
+
+# TAG: client_idle_pconn_timeout
+# How long to wait for the next HTTP request on a persistent
+# client connection after the previous request completes.
+#Default:
+# client_idle_pconn_timeout 2 minutes
+
+# TAG: ftp_client_idle_timeout
+# How long to wait for an FTP request on a connection to Squid ftp_port.
+# Many FTP clients do not deal with idle connection closures well,
+# necessitating a longer default timeout than client_idle_pconn_timeout
+# used for incoming HTTP requests.
+#Default:
+# ftp_client_idle_timeout 30 minutes
+
+# TAG: client_lifetime time-units
+# The maximum amount of time a client (browser) is allowed to
+# remain connected to the cache process. This protects the Cache
+# from having a lot of sockets (and hence file descriptors) tied up
+# in a CLOSE_WAIT state from remote clients that go away without
+# properly shutting down (either because of a network failure or
+# because of a poor client implementation). The default is one
+# day, 1440 minutes.
+#
+# NOTE: The default value is intended to be much larger than any
+# client would ever need to be connected to your cache. You
+# should probably change client_lifetime only as a last resort.
+# If you seem to have many client connections tying up
+# filedescriptors, we recommend first tuning the read_timeout,
+# request_timeout, persistent_request_timeout and quick_abort values.
+#Default:
+# client_lifetime 1 day
+
+# TAG: half_closed_clients
+# Some clients may shutdown the sending side of their TCP
+# connections, while leaving their receiving sides open. Sometimes,
+# Squid can not tell the difference between a half-closed and a
+# fully-closed TCP connection.
+#
+# By default, Squid will immediately close client connections when
+# read(2) returns "no more data to read."
+#
+# Change this option to 'on' and Squid will keep open connections
+# until a read(2) or write(2) on the socket returns an error.
+# This may show some benefits for reverse proxies. But if not
+# it is recommended to leave OFF.
+#Default:
+# half_closed_clients off
+
+# TAG: server_idle_pconn_timeout
+# Timeout for idle persistent connections to servers and other
+# proxies.
+#Default:
+# server_idle_pconn_timeout 1 minute
+
+# TAG: ident_timeout
+# Maximum time to wait for IDENT lookups to complete.
+#
+# If this is too high, and you enabled IDENT lookups from untrusted
+# users, you might be susceptible to denial-of-service by having
+# many ident requests going at once.
+#Default:
+# ident_timeout 10 seconds
+
+# TAG: shutdown_lifetime time-units
+# When SIGTERM or SIGHUP is received, the cache is put into
+# "shutdown pending" mode until all active sockets are closed.
+# This value is the lifetime to set for all open descriptors
+# during shutdown mode. Any active clients after this many
+# seconds will receive a 'timeout' message.
+#Default:
+# shutdown_lifetime 30 seconds
+
+# ADMINISTRATIVE PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_mgr
+# Email-address of local cache manager who will receive
+# mail if the cache dies. The default is "webmaster".
+#Default:
+# cache_mgr webmaster
+
+# TAG: mail_from
+# From: email-address for mail sent when the cache dies.
+# The default is to use 'squid@unique_hostname'.
+#
+# See also: unique_hostname directive.
+#Default:
+# none
+
+# TAG: mail_program
+# Email program used to send mail if the cache dies.
+# The default is "mail". The specified program must comply
+# with the standard Unix mail syntax:
+# mail-program recipient < mailfile
+#
+# Optional command line options can be specified.
+#Default:
+# mail_program mail
+
+# TAG: cache_effective_user
+# If you start Squid as root, it will change its effective/real
+# UID/GID to the user specified below. The default is to change
+# to UID of proxy.
+# see also; cache_effective_group
+#Default:
+# cache_effective_user proxy
+
+# TAG: cache_effective_group
+# Squid sets the GID to the effective user's default group ID
+# (taken from the password file) and supplementary group list
+# from the groups membership.
+#
+# If you want Squid to run with a specific GID regardless of
+# the group memberships of the effective user then set this
+# to the group (or GID) you want Squid to run as. When set
+# all other group privileges of the effective user are ignored
+# and only this GID is effective. If Squid is not started as
+# root the user starting Squid MUST be member of the specified
+# group.
+#
+# This option is not recommended by the Squid Team.
+# Our preference is for administrators to configure a secure
+# user account for squid with UID/GID matching system policies.
+#Default:
+# Use system group memberships of the cache_effective_user account
+
+# TAG: httpd_suppress_version_string on|off
+# Suppress Squid version string info in HTTP headers and HTML error pages.
+#Default:
+# httpd_suppress_version_string off
+
+# TAG: visible_hostname
+# If you want to present a special hostname in error messages, etc,
+# define this. Otherwise, the return value of gethostname()
+# will be used. If you have multiple caches in a cluster and
+# get errors about IP-forwarding you must set them to have individual
+# names with this setting.
+#Default:
+# Automatically detect the system host name
+
+# TAG: unique_hostname
+# If you want to have multiple machines with the same
+# 'visible_hostname' you must give each machine a different
+# 'unique_hostname' so forwarding loops can be detected.
+#Default:
+# Copy the value from visible_hostname
+
+# TAG: hostname_aliases
+# A list of other DNS names your cache has.
+#Default:
+# none
+
+# TAG: umask
+# Minimum umask which should be enforced while the proxy
+# is running, in addition to the umask set at startup.
+#
+# For a traditional octal representation of umasks, start
+# your value with 0.
+#Default:
+# umask 027
+
+# OPTIONS FOR THE CACHE REGISTRATION SERVICE
+# -----------------------------------------------------------------------------
+#
+# This section contains parameters for the (optional) cache
+# announcement service. This service is provided to help
+# cache administrators locate one another in order to join or
+# create cache hierarchies.
+#
+# An 'announcement' message is sent (via UDP) to the registration
+# service by Squid. By default, the announcement message is NOT
+# SENT unless you enable it with 'announce_period' below.
+#
+# The announcement message includes your hostname, plus the
+# following information from this configuration file:
+#
+# http_port
+# icp_port
+# cache_mgr
+#
+# All current information is processed regularly and made
+# available on the Web at http://www.ircache.net/Cache/Tracker/.
+
+# TAG: announce_period
+# This is how frequently to send cache announcements.
+#
+# To enable announcing your cache, just set an announce period.
+#
+# Example:
+# announce_period 1 day
+#Default:
+# Announcement messages disabled.
+
+# TAG: announce_host
+# Set the hostname where announce registration messages will be sent.
+#
+# See also announce_port and announce_file
+#Default:
+# announce_host tracker.ircache.net
+
+# TAG: announce_file
+# The contents of this file will be included in the announce
+# registration messages.
+#Default:
+# none
+
+# TAG: announce_port
+# Set the port where announce registration messages will be sent.
+#
+# See also announce_host and announce_file
+#Default:
+# announce_port 3131
+
+# HTTPD-ACCELERATOR OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: httpd_accel_surrogate_id
+# Surrogates (http://www.esi.org/architecture_spec_1.0.html)
+# need an identification token to allow control targeting. Because
+# a farm of surrogates may all perform the same tasks, they may share
+# an identification token.
+#Default:
+# visible_hostname is used if no specific ID is set.
+
+# TAG: http_accel_surrogate_remote on|off
+# Remote surrogates (such as those in a CDN) honour the header
+# "Surrogate-Control: no-store-remote".
+#
+# Set this to on to have squid behave as a remote surrogate.
+#Default:
+# http_accel_surrogate_remote off
+
+# TAG: esi_parser libxml2|expat|custom
+# ESI markup is not strictly XML compatible. The custom ESI parser
+# will give higher performance, but cannot handle non ASCII character
+# encodings.
+#Default:
+# esi_parser custom
+
+# DELAY POOL PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: delay_pools
+# This represents the number of delay pools to be used. For example,
+# if you have one class 2 delay pool and one class 3 delays pool, you
+# have a total of 2 delay pools.
+#
+# See also delay_parameters, delay_class, delay_access for pool
+# configuration details.
+#Default:
+# delay_pools 0
+
+# TAG: delay_class
+# This defines the class of each delay pool. There must be exactly one
+# delay_class line for each delay pool. For example, to define two
+# delay pools, one of class 2 and one of class 3, the settings above
+# and here would be:
+#
+# Example:
+# delay_pools 4 # 4 delay pools
+# delay_class 1 2 # pool 1 is a class 2 pool
+# delay_class 2 3 # pool 2 is a class 3 pool
+# delay_class 3 4 # pool 3 is a class 4 pool
+# delay_class 4 5 # pool 4 is a class 5 pool
+#
+# The delay pool classes are:
+#
+# class 1 Everything is limited by a single aggregate
+# bucket.
+#
+# class 2 Everything is limited by a single aggregate
+# bucket as well as an "individual" bucket chosen
+# from bits 25 through 32 of the IPv4 address.
+#
+# class 3 Everything is limited by a single aggregate
+# bucket as well as a "network" bucket chosen
+# from bits 17 through 24 of the IP address and a
+# "individual" bucket chosen from bits 17 through
+# 32 of the IPv4 address.
+#
+# class 4 Everything in a class 3 delay pool, with an
+# additional limit on a per user basis. This
+# only takes effect if the username is established
+# in advance - by forcing authentication in your
+# http_access rules.
+#
+# class 5 Requests are grouped according their tag (see
+# external_acl's tag= reply).
+#
+#
+# Each pool also requires a delay_parameters directive to configure the pool size
+# and speed limits used whenever the pool is applied to a request. Along with
+# a set of delay_access directives to determine when it is used.
+#
+# NOTE: If an IP address is a.b.c.d
+# -> bits 25 through 32 are "d"
+# -> bits 17 through 24 are "c"
+# -> bits 17 through 32 are "c * 256 + d"
+#
+# NOTE-2: Due to the use of bitmasks in class 2,3,4 pools they only apply to
+# IPv4 traffic. Class 1 and 5 pools may be used with IPv6 traffic.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# See also delay_parameters and delay_access.
+#Default:
+# none
+
+# TAG: delay_access
+# This is used to determine which delay pool a request falls into.
+#
+# delay_access is sorted per pool and the matching starts with pool 1,
+# then pool 2, ..., and finally pool N. The first delay pool where the
+# request is allowed is selected for the request. If it does not allow
+# the request to any pool then the request is not delayed (default).
+#
+# For example, if you want some_big_clients in delay
+# pool 1 and lotsa_little_clients in delay pool 2:
+#
+# delay_access 1 allow some_big_clients
+# delay_access 1 deny all
+# delay_access 2 allow lotsa_little_clients
+# delay_access 2 deny all
+# delay_access 3 allow authenticated_clients
+#
+# See also delay_parameters and delay_class.
+#
+#Default:
+# Deny using the pool, unless allow rules exist in squid.conf for the pool.
+
+# TAG: delay_parameters
+# This defines the parameters for a delay pool. Each delay pool has
+# a number of "buckets" associated with it, as explained in the
+# description of delay_class.
+#
+# For a class 1 delay pool, the syntax is:
+# delay_class pool 1
+# delay_parameters pool aggregate
+#
+# For a class 2 delay pool:
+# delay_class pool 2
+# delay_parameters pool aggregate individual
+#
+# For a class 3 delay pool:
+# delay_class pool 3
+# delay_parameters pool aggregate network individual
+#
+# For a class 4 delay pool:
+# delay_class pool 4
+# delay_parameters pool aggregate network individual user
+#
+# For a class 5 delay pool:
+# delay_class pool 5
+# delay_parameters pool tagrate
+#
+# The option variables are:
+#
+# pool a pool number - ie, a number between 1 and the
+# number specified in delay_pools as used in
+# delay_class lines.
+#
+# aggregate the speed limit parameters for the aggregate bucket
+# (class 1, 2, 3).
+#
+# individual the speed limit parameters for the individual
+# buckets (class 2, 3).
+#
+# network the speed limit parameters for the network buckets
+# (class 3).
+#
+# user the speed limit parameters for the user buckets
+# (class 4).
+#
+# tagrate the speed limit parameters for the tag buckets
+# (class 5).
+#
+# A pair of delay parameters is written restore/maximum, where restore is
+# the number of bytes (not bits - modem and network speeds are usually
+# quoted in bits) per second placed into the bucket, and maximum is the
+# maximum number of bytes which can be in the bucket at any time.
+#
+# There must be one delay_parameters line for each delay pool.
+#
+#
+# For example, if delay pool number 1 is a class 2 delay pool as in the
+# above example, and is being used to strictly limit each host to 64Kbit/sec
+# (plus overheads), with no overall limit, the line is:
+#
+# delay_parameters 1 none 8000/8000
+#
+# Note that 8 x 8K Byte/sec -> 64K bit/sec.
+#
+# Note that the word 'none' is used to represent no limit.
+#
+#
+# And, if delay pool number 2 is a class 3 delay pool as in the above
+# example, and you want to limit it to a total of 256Kbit/sec (strict limit)
+# with each 8-bit network permitted 64Kbit/sec (strict limit) and each
+# individual host permitted 4800bit/sec with a bucket maximum size of 64Kbits
+# to permit a decent web page to be downloaded at a decent speed
+# (if the network is not being limited due to overuse) but slow down
+# large downloads more significantly:
+#
+# delay_parameters 2 32000/32000 8000/8000 600/8000
+#
+# Note that 8 x 32K Byte/sec -> 256K bit/sec.
+# 8 x 8K Byte/sec -> 64K bit/sec.
+# 8 x 600 Byte/sec -> 4800 bit/sec.
+#
+#
+# Finally, for a class 4 delay pool as in the example - each user will
+# be limited to 128Kbits/sec no matter how many workstations they are logged into.:
+#
+# delay_parameters 4 32000/32000 8000/8000 600/64000 16000/16000
+#
+#
+# See also delay_class and delay_access.
+#
+#Default:
+# none
+
+# TAG: delay_initial_bucket_level (percent, 0-100)
+# The initial bucket percentage is used to determine how much is put
+# in each bucket when squid starts, is reconfigured, or first notices
+# a host accessing it (in class 2 and class 3, individual hosts and
+# networks only have buckets associated with them once they have been
+# "seen" by squid).
+#Default:
+# delay_initial_bucket_level 50
+
+# CLIENT DELAY POOL PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: client_delay_pools
+# This option specifies the number of client delay pools used. It must
+# preceed other client_delay_* options.
+#
+# Example:
+# client_delay_pools 2
+#
+# See also client_delay_parameters and client_delay_access.
+#Default:
+# client_delay_pools 0
+
+# TAG: client_delay_initial_bucket_level (percent, 0-no_limit)
+# This option determines the initial bucket size as a percentage of
+# max_bucket_size from client_delay_parameters. Buckets are created
+# at the time of the "first" connection from the matching IP. Idle
+# buckets are periodically deleted up.
+#
+# You can specify more than 100 percent but note that such "oversized"
+# buckets are not refilled until their size goes down to max_bucket_size
+# from client_delay_parameters.
+#
+# Example:
+# client_delay_initial_bucket_level 50
+#Default:
+# client_delay_initial_bucket_level 50
+
+# TAG: client_delay_parameters
+#
+# This option configures client-side bandwidth limits using the
+# following format:
+#
+# client_delay_parameters pool speed_limit max_bucket_size
+#
+# pool is an integer ID used for client_delay_access matching.
+#
+# speed_limit is bytes added to the bucket per second.
+#
+# max_bucket_size is the maximum size of a bucket, enforced after any
+# speed_limit additions.
+#
+# Please see the delay_parameters option for more information and
+# examples.
+#
+# Example:
+# client_delay_parameters 1 1024 2048
+# client_delay_parameters 2 51200 16384
+#
+# See also client_delay_access.
+#
+#Default:
+# none
+
+# TAG: client_delay_access
+# This option determines the client-side delay pool for the
+# request:
+#
+# client_delay_access pool_ID allow|deny acl_name
+#
+# All client_delay_access options are checked in their pool ID
+# order, starting with pool 1. The first checked pool with allowed
+# request is selected for the request. If no ACL matches or there
+# are no client_delay_access options, the request bandwidth is not
+# limited.
+#
+# The ACL-selected pool is then used to find the
+# client_delay_parameters for the request. Client-side pools are
+# not used to aggregate clients. Clients are always aggregated
+# based on their source IP addresses (one bucket per source IP).
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+# Additionally, only the client TCP connection details are available.
+# ACLs testing HTTP properties will not work.
+#
+# Please see delay_access for more examples.
+#
+# Example:
+# client_delay_access 1 allow low_rate_network
+# client_delay_access 2 allow vips_network
+#
+#
+# See also client_delay_parameters and client_delay_pools.
+#Default:
+# Deny use of the pool, unless allow rules exist in squid.conf for the pool.
+
+# WCCPv1 AND WCCPv2 CONFIGURATION OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: wccp_router
+# Use this option to define your WCCP ``home'' router for
+# Squid.
+#
+# wccp_router supports a single WCCP(v1) router
+#
+# wccp2_router supports multiple WCCPv2 routers
+#
+# only one of the two may be used at the same time and defines
+# which version of WCCP to use.
+#Default:
+# WCCP disabled.
+
+# TAG: wccp2_router
+# Use this option to define your WCCP ``home'' router for
+# Squid.
+#
+# wccp_router supports a single WCCP(v1) router
+#
+# wccp2_router supports multiple WCCPv2 routers
+#
+# only one of the two may be used at the same time and defines
+# which version of WCCP to use.
+#Default:
+# WCCPv2 disabled.
+
+# TAG: wccp_version
+# This directive is only relevant if you need to set up WCCP(v1)
+# to some very old and end-of-life Cisco routers. In all other
+# setups it must be left unset or at the default setting.
+# It defines an internal version in the WCCP(v1) protocol,
+# with version 4 being the officially documented protocol.
+#
+# According to some users, Cisco IOS 11.2 and earlier only
+# support WCCP version 3. If you're using that or an earlier
+# version of IOS, you may need to change this value to 3, otherwise
+# do not specify this parameter.
+#Default:
+# wccp_version 4
+
+# TAG: wccp2_rebuild_wait
+# If this is enabled Squid will wait for the cache dir rebuild to finish
+# before sending the first wccp2 HereIAm packet
+#Default:
+# wccp2_rebuild_wait on
+
+# TAG: wccp2_forwarding_method
+# WCCP2 allows the setting of forwarding methods between the
+# router/switch and the cache. Valid values are as follows:
+#
+# gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
+# l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
+#
+# Currently (as of IOS 12.4) cisco routers only support GRE.
+# Cisco switches only support the L2 redirect assignment method.
+#Default:
+# wccp2_forwarding_method gre
+
+# TAG: wccp2_return_method
+# WCCP2 allows the setting of return methods between the
+# router/switch and the cache for packets that the cache
+# decides not to handle. Valid values are as follows:
+#
+# gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
+# l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
+#
+# Currently (as of IOS 12.4) cisco routers only support GRE.
+# Cisco switches only support the L2 redirect assignment.
+#
+# If the "ip wccp redirect exclude in" command has been
+# enabled on the cache interface, then it is still safe for
+# the proxy server to use a l2 redirect method even if this
+# option is set to GRE.
+#Default:
+# wccp2_return_method gre
+
+# TAG: wccp2_assignment_method
+# WCCP2 allows the setting of methods to assign the WCCP hash
+# Valid values are as follows:
+#
+# hash - Hash assignment
+# mask - Mask assignment
+#
+# As a general rule, cisco routers support the hash assignment method
+# and cisco switches support the mask assignment method.
+#Default:
+# wccp2_assignment_method hash
+
+# TAG: wccp2_service
+# WCCP2 allows for multiple traffic services. There are two
+# types: "standard" and "dynamic". The standard type defines
+# one service id - http (id 0). The dynamic service ids can be from
+# 51 to 255 inclusive. In order to use a dynamic service id
+# one must define the type of traffic to be redirected; this is done
+# using the wccp2_service_info option.
+#
+# The "standard" type does not require a wccp2_service_info option,
+# just specifying the service id will suffice.
+#
+# MD5 service authentication can be enabled by adding
+# "password=<password>" to the end of this service declaration.
+#
+# Examples:
+#
+# wccp2_service standard 0 # for the 'web-cache' standard service
+# wccp2_service dynamic 80 # a dynamic service type which will be
+# # fleshed out with subsequent options.
+# wccp2_service standard 0 password=foo
+#Default:
+# Use the 'web-cache' standard service.
+
+# TAG: wccp2_service_info
+# Dynamic WCCPv2 services require further information to define the
+# traffic you wish to have diverted.
+#
+# The format is:
+#
+# wccp2_service_info <id> protocol=<protocol> flags=<flag>,<flag>..
+# priority=<priority> ports=<port>,<port>..
+#
+# The relevant WCCPv2 flags:
+# + src_ip_hash, dst_ip_hash
+# + source_port_hash, dst_port_hash
+# + src_ip_alt_hash, dst_ip_alt_hash
+# + src_port_alt_hash, dst_port_alt_hash
+# + ports_source
+#
+# The port list can be one to eight entries.
+#
+# Example:
+#
+# wccp2_service_info 80 protocol=tcp flags=src_ip_hash,ports_source
+# priority=240 ports=80
+#
+# Note: the service id must have been defined by a previous
+# 'wccp2_service dynamic <id>' entry.
+#Default:
+# none
+
+# TAG: wccp2_weight
+# Each cache server gets assigned a set of the destination
+# hash proportional to their weight.
+#Default:
+# wccp2_weight 10000
+
+# TAG: wccp_address
+# Use this option if you require WCCPv2 to use a specific
+# interface address.
+#
+# The default behavior is to not bind to any specific address.
+#Default:
+# Address selected by the operating system.
+
+# TAG: wccp2_address
+# Use this option if you require WCCP to use a specific
+# interface address.
+#
+# The default behavior is to not bind to any specific address.
+#Default:
+# Address selected by the operating system.
+
+# PERSISTENT CONNECTION HANDLING
+# -----------------------------------------------------------------------------
+#
+# Also see "pconn_timeout" in the TIMEOUTS section
+
+# TAG: client_persistent_connections
+# Persistent connection support for clients.
+# Squid uses persistent connections (when allowed). You can use
+# this option to disable persistent connections with clients.
+#Default:
+# client_persistent_connections on
+
+# TAG: server_persistent_connections
+# Persistent connection support for servers.
+# Squid uses persistent connections (when allowed). You can use
+# this option to disable persistent connections with servers.
+#Default:
+# server_persistent_connections on
+
+# TAG: persistent_connection_after_error
+# With this directive the use of persistent connections after
+# HTTP errors can be disabled. Useful if you have clients
+# who fail to handle errors on persistent connections proper.
+#Default:
+# persistent_connection_after_error on
+
+# TAG: detect_broken_pconn
+# Some servers have been found to incorrectly signal the use
+# of HTTP/1.0 persistent connections even on replies not
+# compatible, causing significant delays. This server problem
+# has mostly been seen on redirects.
+#
+# By enabling this directive Squid attempts to detect such
+# broken replies and automatically assume the reply is finished
+# after 10 seconds timeout.
+#Default:
+# detect_broken_pconn off
+
+# CACHE DIGEST OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: digest_generation
+# This controls whether the server will generate a Cache Digest
+# of its contents. By default, Cache Digest generation is
+# enabled if Squid is compiled with --enable-cache-digests defined.
+#Default:
+# digest_generation on
+
+# TAG: digest_bits_per_entry
+# This is the number of bits of the server's Cache Digest which
+# will be associated with the Digest entry for a given HTTP
+# Method and URL (public key) combination. The default is 5.
+#Default:
+# digest_bits_per_entry 5
+
+# TAG: digest_rebuild_period (seconds)
+# This is the wait time between Cache Digest rebuilds.
+#Default:
+# digest_rebuild_period 1 hour
+
+# TAG: digest_rewrite_period (seconds)
+# This is the wait time between Cache Digest writes to
+# disk.
+#Default:
+# digest_rewrite_period 1 hour
+
+# TAG: digest_swapout_chunk_size (bytes)
+# This is the number of bytes of the Cache Digest to write to
+# disk at a time. It defaults to 4096 bytes (4KB), the Squid
+# default swap page.
+#Default:
+# digest_swapout_chunk_size 4096 bytes
+
+# TAG: digest_rebuild_chunk_percentage (percent, 0-100)
+# This is the percentage of the Cache Digest to be scanned at a
+# time. By default it is set to 10% of the Cache Digest.
+#Default:
+# digest_rebuild_chunk_percentage 10
+
+# SNMP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: snmp_port
+# The port number where Squid listens for SNMP requests. To enable
+# SNMP support set this to a suitable port number. Port number
+# 3401 is often used for the Squid SNMP agent. By default it's
+# set to "0" (disabled)
+#
+# Example:
+# snmp_port 3401
+#Default:
+# SNMP disabled.
+
+# TAG: snmp_access
+# Allowing or denying access to the SNMP port.
+#
+# All access to the agent is denied by default.
+# usage:
+#
+# snmp_access allow|deny [!]aclname ...
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Example:
+# snmp_access allow snmppublic localhost
+# snmp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: snmp_incoming_address
+# Just like 'udp_incoming_address', but for the SNMP port.
+#
+# snmp_incoming_address is used for the SNMP socket receiving
+# messages from SNMP agents.
+#
+# The default snmp_incoming_address is to listen on all
+# available network interfaces.
+#Default:
+# Accept SNMP packets from all machine interfaces.
+
+# TAG: snmp_outgoing_address
+# Just like 'udp_outgoing_address', but for the SNMP port.
+#
+# snmp_outgoing_address is used for SNMP packets returned to SNMP
+# agents.
+#
+# If snmp_outgoing_address is not set it will use the same socket
+# as snmp_incoming_address. Only change this if you want to have
+# SNMP replies sent using another address than where this Squid
+# listens for SNMP queries.
+#
+# NOTE, snmp_incoming_address and snmp_outgoing_address can not have
+# the same value since they both use the same port.
+#Default:
+# Use snmp_incoming_address or an address selected by the operating system.
+
+# ICP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icp_port
+# The port number where Squid sends and receives ICP queries to
+# and from neighbor caches. The standard UDP port for ICP is 3130.
+#
+# Example:
+# icp_port 3130
+#Default:
+# ICP disabled.
+
+# TAG: htcp_port
+# The port number where Squid sends and receives HTCP queries to
+# and from neighbor caches. To turn it on you want to set it to
+# 4827.
+#
+# Example:
+# htcp_port 4827
+#Default:
+# HTCP disabled.
+
+# TAG: log_icp_queries on|off
+# If set, ICP queries are logged to access.log. You may wish
+# do disable this if your ICP load is VERY high to speed things
+# up or to simplify log analysis.
+#Default:
+# log_icp_queries on
+
+# TAG: udp_incoming_address
+# udp_incoming_address is used for UDP packets received from other
+# caches.
+#
+# The default behavior is to not bind to any specific address.
+#
+# Only change this if you want to have all UDP queries received on
+# a specific interface/address.
+#
+# NOTE: udp_incoming_address is used by the ICP, HTCP, and DNS
+# modules. Altering it will affect all of them in the same manner.
+#
+# see also; udp_outgoing_address
+#
+# NOTE, udp_incoming_address and udp_outgoing_address can not
+# have the same value since they both use the same port.
+#Default:
+# Accept packets from all machine interfaces.
+
+# TAG: udp_outgoing_address
+# udp_outgoing_address is used for UDP packets sent out to other
+# caches.
+#
+# The default behavior is to not bind to any specific address.
+#
+# Instead it will use the same socket as udp_incoming_address.
+# Only change this if you want to have UDP queries sent using another
+# address than where this Squid listens for UDP queries from other
+# caches.
+#
+# NOTE: udp_outgoing_address is used by the ICP, HTCP, and DNS
+# modules. Altering it will affect all of them in the same manner.
+#
+# see also; udp_incoming_address
+#
+# NOTE, udp_incoming_address and udp_outgoing_address can not
+# have the same value since they both use the same port.
+#Default:
+# Use udp_incoming_address or an address selected by the operating system.
+
+# TAG: icp_hit_stale on|off
+# If you want to return ICP_HIT for stale cache objects, set this
+# option to 'on'. If you have sibling relationships with caches
+# in other administrative domains, this should be 'off'. If you only
+# have sibling relationships with caches under your control,
+# it is probably okay to set this to 'on'.
+# If set to 'on', your siblings should use the option "allow-miss"
+# on their cache_peer lines for connecting to you.
+#Default:
+# icp_hit_stale off
+
+# TAG: minimum_direct_hops
+# If using the ICMP pinging stuff, do direct fetches for sites
+# which are no more than this many hops away.
+#Default:
+# minimum_direct_hops 4
+
+# TAG: minimum_direct_rtt (msec)
+# If using the ICMP pinging stuff, do direct fetches for sites
+# which are no more than this many rtt milliseconds away.
+#Default:
+# minimum_direct_rtt 400
+
+# TAG: netdb_low
+# The low water mark for the ICMP measurement database.
+#
+# Note: high watermark controlled by netdb_high directive.
+#
+# These watermarks are counts, not percents. The defaults are
+# (low) 900 and (high) 1000. When the high water mark is
+# reached, database entries will be deleted until the low
+# mark is reached.
+#Default:
+# netdb_low 900
+
+# TAG: netdb_high
+# The high water mark for the ICMP measurement database.
+#
+# Note: low watermark controlled by netdb_low directive.
+#
+# These watermarks are counts, not percents. The defaults are
+# (low) 900 and (high) 1000. When the high water mark is
+# reached, database entries will be deleted until the low
+# mark is reached.
+#Default:
+# netdb_high 1000
+
+# TAG: netdb_ping_period
+# The minimum period for measuring a site. There will be at
+# least this much delay between successive pings to the same
+# network. The default is five minutes.
+#Default:
+# netdb_ping_period 5 minutes
+
+# TAG: query_icmp on|off
+# If you want to ask your peers to include ICMP data in their ICP
+# replies, enable this option.
+#
+# If your peer has configured Squid (during compilation) with
+# '--enable-icmp' that peer will send ICMP pings to origin server
+# sites of the URLs it receives. If you enable this option the
+# ICP replies from that peer will include the ICMP data (if available).
+# Then, when choosing a parent cache, Squid will choose the parent with
+# the minimal RTT to the origin server. When this happens, the
+# hierarchy field of the access.log will be
+# "CLOSEST_PARENT_MISS". This option is off by default.
+#Default:
+# query_icmp off
+
+# TAG: test_reachability on|off
+# When this is 'on', ICP MISS replies will be ICP_MISS_NOFETCH
+# instead of ICP_MISS if the target host is NOT in the ICMP
+# database, or has a zero RTT.
+#Default:
+# test_reachability off
+
+# TAG: icp_query_timeout (msec)
+# Normally Squid will automatically determine an optimal ICP
+# query timeout value based on the round-trip-time of recent ICP
+# queries. If you want to override the value determined by
+# Squid, set this 'icp_query_timeout' to a non-zero value. This
+# value is specified in MILLISECONDS, so, to use a 2-second
+# timeout (the old default), you would write:
+#
+# icp_query_timeout 2000
+#Default:
+# Dynamic detection.
+
+# TAG: maximum_icp_query_timeout (msec)
+# Normally the ICP query timeout is determined dynamically. But
+# sometimes it can lead to very large values (say 5 seconds).
+# Use this option to put an upper limit on the dynamic timeout
+# value. Do NOT use this option to always use a fixed (instead
+# of a dynamic) timeout value. To set a fixed timeout see the
+# 'icp_query_timeout' directive.
+#Default:
+# maximum_icp_query_timeout 2000
+
+# TAG: minimum_icp_query_timeout (msec)
+# Normally the ICP query timeout is determined dynamically. But
+# sometimes it can lead to very small timeouts, even lower than
+# the normal latency variance on your link due to traffic.
+# Use this option to put an lower limit on the dynamic timeout
+# value. Do NOT use this option to always use a fixed (instead
+# of a dynamic) timeout value. To set a fixed timeout see the
+# 'icp_query_timeout' directive.
+#Default:
+# minimum_icp_query_timeout 5
+
+# TAG: background_ping_rate time-units
+# Controls how often the ICP pings are sent to siblings that
+# have background-ping set.
+#Default:
+# background_ping_rate 10 seconds
+
+# MULTICAST ICP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: mcast_groups
+# This tag specifies a list of multicast groups which your server
+# should join to receive multicasted ICP queries.
+#
+# NOTE! Be very careful what you put here! Be sure you
+# understand the difference between an ICP _query_ and an ICP
+# _reply_. This option is to be set only if you want to RECEIVE
+# multicast queries. Do NOT set this option to SEND multicast
+# ICP (use cache_peer for that). ICP replies are always sent via
+# unicast, so this option does not affect whether or not you will
+# receive replies from multicast group members.
+#
+# You must be very careful to NOT use a multicast address which
+# is already in use by another group of caches.
+#
+# If you are unsure about multicast, please read the Multicast
+# chapter in the Squid FAQ (http://www.squid-cache.org/FAQ/).
+#
+# Usage: mcast_groups 239.128.16.128 224.0.1.20
+#
+# By default, Squid doesn't listen on any multicast groups.
+#Default:
+# none
+
+# TAG: mcast_miss_addr
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# If you enable this option, every "cache miss" URL will
+# be sent out on the specified multicast address.
+#
+# Do not enable this option unless you are are absolutely
+# certain you understand what you are doing.
+#Default:
+# disabled.
+
+# TAG: mcast_miss_ttl
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# This is the time-to-live value for packets multicasted
+# when multicasting off cache miss URLs is enabled. By
+# default this is set to 'site scope', i.e. 16.
+#Default:
+# mcast_miss_ttl 16
+
+# TAG: mcast_miss_port
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# This is the port number to be used in conjunction with
+# 'mcast_miss_addr'.
+#Default:
+# mcast_miss_port 3135
+
+# TAG: mcast_miss_encode_key
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# The URLs that are sent in the multicast miss stream are
+# encrypted. This is the encryption key.
+#Default:
+# mcast_miss_encode_key XXXXXXXXXXXXXXXX
+
+# TAG: mcast_icp_query_timeout (msec)
+# For multicast peers, Squid regularly sends out ICP "probes" to
+# count how many other peers are listening on the given multicast
+# address. This value specifies how long Squid should wait to
+# count all the replies. The default is 2000 msec, or 2
+# seconds.
+#Default:
+# mcast_icp_query_timeout 2000
+
+# INTERNAL ICON OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icon_directory
+# Where the icons are stored. These are normally kept in
+# /usr/share/squid/icons
+#Default:
+# icon_directory /usr/share/squid/icons
+
+# TAG: global_internal_static
+# This directive controls is Squid should intercept all requests for
+# /squid-internal-static/ no matter which host the URL is requesting
+# (default on setting), or if nothing special should be done for
+# such URLs (off setting). The purpose of this directive is to make
+# icons etc work better in complex cache hierarchies where it may
+# not always be possible for all corners in the cache mesh to reach
+# the server generating a directory listing.
+#Default:
+# global_internal_static on
+
+# TAG: short_icon_urls
+# If this is enabled Squid will use short URLs for icons.
+# If disabled it will revert to the old behavior of including
+# it's own name and port in the URL.
+#
+# If you run a complex cache hierarchy with a mix of Squid and
+# other proxies you may need to disable this directive.
+#Default:
+# short_icon_urls on
+
+# ERROR PAGE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: error_directory
+# If you wish to create your own versions of the default
+# error files to customize them to suit your company copy
+# the error/template files to another directory and point
+# this tag at them.
+#
+# WARNING: This option will disable multi-language support
+# on error pages if used.
+#
+# The squid developers are interested in making squid available in
+# a wide variety of languages. If you are making translations for a
+# language that Squid does not currently provide please consider
+# contributing your translation back to the project.
+# http://wiki.squid-cache.org/Translations
+#
+# The squid developers working on translations are happy to supply drop-in
+# translated error files in exchange for any new language contributions.
+#Default:
+# Send error pages in the clients preferred language
+
+# TAG: error_default_language
+# Set the default language which squid will send error pages in
+# if no existing translation matches the clients language
+# preferences.
+#
+# If unset (default) generic English will be used.
+#
+# The squid developers are interested in making squid available in
+# a wide variety of languages. If you are interested in making
+# translations for any language see the squid wiki for details.
+# http://wiki.squid-cache.org/Translations
+#Default:
+# Generate English language pages.
+
+# TAG: error_log_languages
+# Log to cache.log what languages users are attempting to
+# auto-negotiate for translations.
+#
+# Successful negotiations are not logged. Only failures
+# have meaning to indicate that Squid may need an upgrade
+# of its error page translations.
+#Default:
+# error_log_languages on
+
+# TAG: err_page_stylesheet
+# CSS Stylesheet to pattern the display of Squid default error pages.
+#
+# For information on CSS see http://www.w3.org/Style/CSS/
+#Default:
+# err_page_stylesheet /etc/squid/errorpage.css
+
+# TAG: err_html_text
+# HTML text to include in error messages. Make this a "mailto"
+# URL to your admin address, or maybe just a link to your
+# organizations Web page.
+#
+# To include this in your error messages, you must rewrite
+# the error template files (found in the "errors" directory).
+# Wherever you want the 'err_html_text' line to appear,
+# insert a %L tag in the error template file.
+#Default:
+# none
+
+# TAG: email_err_data on|off
+# If enabled, information about the occurred error will be
+# included in the mailto links of the ERR pages (if %W is set)
+# so that the email body contains the data.
+# Syntax is <A HREF="mailto:%w%W">%w</A>
+#Default:
+# email_err_data on
+
+# TAG: deny_info
+# Usage: deny_info err_page_name acl
+# or deny_info http://... acl
+# or deny_info TCP_RESET acl
+#
+# This can be used to return a ERR_ page for requests which
+# do not pass the 'http_access' rules. Squid remembers the last
+# acl it evaluated in http_access, and if a 'deny_info' line exists
+# for that ACL Squid returns a corresponding error page.
+#
+# The acl is typically the last acl on the http_access deny line which
+# denied access. The exceptions to this rule are:
+# - When Squid needs to request authentication credentials. It's then
+# the first authentication related acl encountered
+# - When none of the http_access lines matches. It's then the last
+# acl processed on the last http_access line.
+# - When the decision to deny access was made by an adaptation service,
+# the acl name is the corresponding eCAP or ICAP service_name.
+#
+# NP: If providing your own custom error pages with error_directory
+# you may also specify them by your custom file name:
+# Example: deny_info ERR_CUSTOM_ACCESS_DENIED bad_guys
+#
+# By defaut Squid will send "403 Forbidden". A different 4xx or 5xx
+# may be specified by prefixing the file name with the code and a colon.
+# e.g. 404:ERR_CUSTOM_ACCESS_DENIED
+#
+# Alternatively you can tell Squid to reset the TCP connection
+# by specifying TCP_RESET.
+#
+# Or you can specify an error URL or URL pattern. The browsers will
+# get redirected to the specified URL after formatting tags have
+# been replaced. Redirect will be done with 302 or 307 according to
+# HTTP/1.1 specs. A different 3xx code may be specified by prefixing
+# the URL. e.g. 303:http://example.com/
+#
+# URL FORMAT TAGS:
+# %a - username (if available. Password NOT included)
+# %B - FTP path URL
+# %e - Error number
+# %E - Error description
+# %h - Squid hostname
+# %H - Request domain name
+# %i - Client IP Address
+# %M - Request Method
+# %o - Message result from external ACL helper
+# %p - Request Port number
+# %P - Request Protocol name
+# %R - Request URL path
+# %T - Timestamp in RFC 1123 format
+# %U - Full canonical URL from client
+# (HTTPS URLs terminate with *)
+# %u - Full canonical URL from client
+# %w - Admin email from squid.conf
+# %x - Error name
+# %% - Literal percent (%) code
+#
+#Default:
+# none
+
+# OPTIONS INFLUENCING REQUEST FORWARDING
+# -----------------------------------------------------------------------------
+
+# TAG: nonhierarchical_direct
+# By default, Squid will send any non-hierarchical requests
+# (not cacheable request type) direct to origin servers.
+#
+# When this is set to "off", Squid will prefer to send these
+# requests to parents.
+#
+# Note that in most configurations, by turning this off you will only
+# add latency to these request without any improvement in global hit
+# ratio.
+#
+# This option only sets a preference. If the parent is unavailable a
+# direct connection to the origin server may still be attempted. To
+# completely prevent direct connections use never_direct.
+#Default:
+# nonhierarchical_direct on
+
+# TAG: prefer_direct
+# Normally Squid tries to use parents for most requests. If you for some
+# reason like it to first try going direct and only use a parent if
+# going direct fails set this to on.
+#
+# By combining nonhierarchical_direct off and prefer_direct on you
+# can set up Squid to use a parent as a backup path if going direct
+# fails.
+#
+# Note: If you want Squid to use parents for all requests see
+# the never_direct directive. prefer_direct only modifies how Squid
+# acts on cacheable requests.
+#Default:
+# prefer_direct off
+
+# TAG: cache_miss_revalidate on|off
+# RFC 7232 defines a conditional request mechanism to prevent
+# response objects being unnecessarily transferred over the network.
+# If that mechanism is used by the client and a cache MISS occurs
+# it can prevent new cache entries being created.
+#
+# This option determines whether Squid on cache MISS will pass the
+# client revalidation request to the server or tries to fetch new
+# content for caching. It can be useful while the cache is mostly
+# empty to more quickly have the cache populated by generating
+# non-conditional GETs.
+#
+# When set to 'on' (default), Squid will pass all client If-* headers
+# to the server. This permits server responses without a cacheable
+# payload to be delivered and on MISS no new cache entry is created.
+#
+# When set to 'off' and if the request is cacheable, Squid will
+# remove the clients If-Modified-Since and If-None-Match headers from
+# the request sent to the server. This requests a 200 status response
+# from the server to create a new cache entry with.
+#Default:
+# cache_miss_revalidate on
+
+# TAG: always_direct
+# Usage: always_direct allow|deny [!]aclname ...
+#
+# Here you can use ACL elements to specify requests which should
+# ALWAYS be forwarded by Squid to the origin servers without using
+# any peers. For example, to always directly forward requests for
+# local servers ignoring any parents or siblings you may have use
+# something like:
+#
+# acl local-servers dstdomain my.domain.net
+# always_direct allow local-servers
+#
+# To always forward FTP requests directly, use
+#
+# acl FTP proto FTP
+# always_direct allow FTP
+#
+# NOTE: There is a similar, but opposite option named
+# 'never_direct'. You need to be aware that "always_direct deny
+# foo" is NOT the same thing as "never_direct allow foo". You
+# may need to use a deny rule to exclude a more-specific case of
+# some other rule. Example:
+#
+# acl local-external dstdomain external.foo.net
+# acl local-servers dstdomain .foo.net
+# always_direct deny local-external
+# always_direct allow local-servers
+#
+# NOTE: If your goal is to make the client forward the request
+# directly to the origin server bypassing Squid then this needs
+# to be done in the client configuration. Squid configuration
+# can only tell Squid how Squid should fetch the object.
+#
+# NOTE: This directive is not related to caching. The replies
+# is cached as usual even if you use always_direct. To not cache
+# the replies see the 'cache' directive.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Prevent any cache_peer being used for this request.
+
+# TAG: never_direct
+# Usage: never_direct allow|deny [!]aclname ...
+#
+# never_direct is the opposite of always_direct. Please read
+# the description for always_direct if you have not already.
+#
+# With 'never_direct' you can use ACL elements to specify
+# requests which should NEVER be forwarded directly to origin
+# servers. For example, to force the use of a proxy for all
+# requests, except those in your local domain use something like:
+#
+# acl local-servers dstdomain .foo.net
+# never_direct deny local-servers
+# never_direct allow all
+#
+# or if Squid is inside a firewall and there are local intranet
+# servers inside the firewall use something like:
+#
+# acl local-intranet dstdomain .foo.net
+# acl local-external dstdomain external.foo.net
+# always_direct deny local-external
+# always_direct allow local-intranet
+# never_direct allow all
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow DNS results to be used for this request.
+
+# ADVANCED NETWORKING OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: incoming_udp_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_udp_average 6
+
+# TAG: incoming_tcp_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_tcp_average 4
+
+# TAG: incoming_dns_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_dns_average 4
+
+# TAG: min_udp_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_udp_poll_cnt 8
+
+# TAG: min_dns_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_dns_poll_cnt 8
+
+# TAG: min_tcp_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_tcp_poll_cnt 8
+
+# TAG: accept_filter
+# FreeBSD:
+#
+# The name of an accept(2) filter to install on Squid's
+# listen socket(s). This feature is perhaps specific to
+# FreeBSD and requires support in the kernel.
+#
+# The 'httpready' filter delays delivering new connections
+# to Squid until a full HTTP request has been received.
+# See the accf_http(9) man page for details.
+#
+# The 'dataready' filter delays delivering new connections
+# to Squid until there is some data to process.
+# See the accf_dataready(9) man page for details.
+#
+# Linux:
+#
+# The 'data' filter delays delivering of new connections
+# to Squid until there is some data to process by TCP_ACCEPT_DEFER.
+# You may optionally specify a number of seconds to wait by
+# 'data=N' where N is the number of seconds. Defaults to 30
+# if not specified. See the tcp(7) man page for details.
+#EXAMPLE:
+## FreeBSD
+#accept_filter httpready
+## Linux
+#accept_filter data
+#Default:
+# none
+
+# TAG: client_ip_max_connections
+# Set an absolute limit on the number of connections a single
+# client IP can use. Any more than this and Squid will begin to drop
+# new connections from the client until it closes some links.
+#
+# Note that this is a global limit. It affects all HTTP, HTCP, Gopher and FTP
+# connections from the client. For finer control use the ACL access controls.
+#
+# Requires client_db to be enabled (the default).
+#
+# WARNING: This may noticably slow down traffic received via external proxies
+# or NAT devices and cause them to rebound error messages back to their clients.
+#Default:
+# No limit.
+
+# TAG: tcp_recv_bufsize (bytes)
+# Size of receive buffer to set for TCP sockets. Probably just
+# as easy to change your kernel's default.
+# Omit from squid.conf to use the default buffer size.
+#Default:
+# Use operating system TCP defaults.
+
+# ICAP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icap_enable on|off
+# If you want to enable the ICAP module support, set this to on.
+#Default:
+# icap_enable off
+
+# TAG: icap_connect_timeout
+# This parameter specifies how long to wait for the TCP connect to
+# the requested ICAP server to complete before giving up and either
+# terminating the HTTP transaction or bypassing the failure.
+#
+# The default for optional services is peer_connect_timeout.
+# The default for essential services is connect_timeout.
+# If this option is explicitly set, its value applies to all services.
+#Default:
+# none
+
+# TAG: icap_io_timeout time-units
+# This parameter specifies how long to wait for an I/O activity on
+# an established, active ICAP connection before giving up and
+# either terminating the HTTP transaction or bypassing the
+# failure.
+#Default:
+# Use read_timeout.
+
+# TAG: icap_service_failure_limit limit [in memory-depth time-units]
+# The limit specifies the number of failures that Squid tolerates
+# when establishing a new TCP connection with an ICAP service. If
+# the number of failures exceeds the limit, the ICAP service is
+# not used for new ICAP requests until it is time to refresh its
+# OPTIONS.
+#
+# A negative value disables the limit. Without the limit, an ICAP
+# service will not be considered down due to connectivity failures
+# between ICAP OPTIONS requests.
+#
+# Squid forgets ICAP service failures older than the specified
+# value of memory-depth. The memory fading algorithm
+# is approximate because Squid does not remember individual
+# errors but groups them instead, splitting the option
+# value into ten time slots of equal length.
+#
+# When memory-depth is 0 and by default this option has no
+# effect on service failure expiration.
+#
+# Squid always forgets failures when updating service settings
+# using an ICAP OPTIONS transaction, regardless of this option
+# setting.
+#
+# For example,
+# # suspend service usage after 10 failures in 5 seconds:
+# icap_service_failure_limit 10 in 5 seconds
+#Default:
+# icap_service_failure_limit 10
+
+# TAG: icap_service_revival_delay
+# The delay specifies the number of seconds to wait after an ICAP
+# OPTIONS request failure before requesting the options again. The
+# failed ICAP service is considered "down" until fresh OPTIONS are
+# fetched.
+#
+# The actual delay cannot be smaller than the hardcoded minimum
+# delay of 30 seconds.
+#Default:
+# icap_service_revival_delay 180
+
+# TAG: icap_preview_enable on|off
+# The ICAP Preview feature allows the ICAP server to handle the
+# HTTP message by looking only at the beginning of the message body
+# or even without receiving the body at all. In some environments,
+# previews greatly speedup ICAP processing.
+#
+# During an ICAP OPTIONS transaction, the server may tell Squid what
+# HTTP messages should be previewed and how big the preview should be.
+# Squid will not use Preview if the server did not request one.
+#
+# To disable ICAP Preview for all ICAP services, regardless of
+# individual ICAP server OPTIONS responses, set this option to "off".
+#Example:
+#icap_preview_enable off
+#Default:
+# icap_preview_enable on
+
+# TAG: icap_preview_size
+# The default size of preview data to be sent to the ICAP server.
+# This value might be overwritten on a per server basis by OPTIONS requests.
+#Default:
+# No preview sent.
+
+# TAG: icap_206_enable on|off
+# 206 (Partial Content) responses is an ICAP extension that allows the
+# ICAP agents to optionally combine adapted and original HTTP message
+# content. The decision to combine is postponed until the end of the
+# ICAP response. Squid supports Partial Content extension by default.
+#
+# Activation of the Partial Content extension is negotiated with each
+# ICAP service during OPTIONS exchange. Most ICAP servers should handle
+# negotation correctly even if they do not support the extension, but
+# some might fail. To disable Partial Content support for all ICAP
+# services and to avoid any negotiation, set this option to "off".
+#
+# Example:
+# icap_206_enable off
+#Default:
+# icap_206_enable on
+
+# TAG: icap_default_options_ttl
+# The default TTL value for ICAP OPTIONS responses that don't have
+# an Options-TTL header.
+#Default:
+# icap_default_options_ttl 60
+
+# TAG: icap_persistent_connections on|off
+# Whether or not Squid should use persistent connections to
+# an ICAP server.
+#Default:
+# icap_persistent_connections on
+
+# TAG: adaptation_send_client_ip on|off
+# If enabled, Squid shares HTTP client IP information with adaptation
+# services. For ICAP, Squid adds the X-Client-IP header to ICAP requests.
+# For eCAP, Squid sets the libecap::metaClientIp transaction option.
+#
+# See also: adaptation_uses_indirect_client
+#Default:
+# adaptation_send_client_ip off
+
+# TAG: adaptation_send_username on|off
+# This sends authenticated HTTP client username (if available) to
+# the adaptation service.
+#
+# For ICAP, the username value is encoded based on the
+# icap_client_username_encode option and is sent using the header
+# specified by the icap_client_username_header option.
+#Default:
+# adaptation_send_username off
+
+# TAG: icap_client_username_header
+# ICAP request header name to use for adaptation_send_username.
+#Default:
+# icap_client_username_header X-Client-Username
+
+# TAG: icap_client_username_encode on|off
+# Whether to base64 encode the authenticated client username.
+#Default:
+# icap_client_username_encode off
+
+# TAG: icap_service
+# Defines a single ICAP service using the following format:
+#
+# icap_service id vectoring_point uri [option ...]
+#
+# id: ID
+# an opaque identifier or name which is used to direct traffic to
+# this specific service. Must be unique among all adaptation
+# services in squid.conf.
+#
+# vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache
+# This specifies at which point of transaction processing the
+# ICAP service should be activated. *_postcache vectoring points
+# are not yet supported.
+#
+# uri: icap://servername:port/servicepath
+# ICAP server and service location.
+#
+# ICAP does not allow a single service to handle both REQMOD and RESPMOD
+# transactions. Squid does not enforce that requirement. You can specify
+# services with the same service_url and different vectoring_points. You
+# can even specify multiple identical services as long as their
+# service_names differ.
+#
+# To activate a service, use the adaptation_access directive. To group
+# services, use adaptation_service_chain and adaptation_service_set.
+#
+# Service options are separated by white space. ICAP services support
+# the following name=value options:
+#
+# bypass=on|off|1|0
+# If set to 'on' or '1', the ICAP service is treated as
+# optional. If the service cannot be reached or malfunctions,
+# Squid will try to ignore any errors and process the message as
+# if the service was not enabled. No all ICAP errors can be
+# bypassed. If set to 0, the ICAP service is treated as
+# essential and all ICAP errors will result in an error page
+# returned to the HTTP client.
+#
+# Bypass is off by default: services are treated as essential.
+#
+# routing=on|off|1|0
+# If set to 'on' or '1', the ICAP service is allowed to
+# dynamically change the current message adaptation plan by
+# returning a chain of services to be used next. The services
+# are specified using the X-Next-Services ICAP response header
+# value, formatted as a comma-separated list of service names.
+# Each named service should be configured in squid.conf. Other
+# services are ignored. An empty X-Next-Services value results
+# in an empty plan which ends the current adaptation.
+#
+# Dynamic adaptation plan may cross or cover multiple supported
+# vectoring points in their natural processing order.
+#
+# Routing is not allowed by default: the ICAP X-Next-Services
+# response header is ignored.
+#
+# ipv6=on|off
+# Only has effect on split-stack systems. The default on those systems
+# is to use IPv4-only connections. When set to 'on' this option will
+# make Squid use IPv6-only connections to contact this ICAP service.
+#
+# on-overload=block|bypass|wait|force
+# If the service Max-Connections limit has been reached, do
+# one of the following for each new ICAP transaction:
+# * block: send an HTTP error response to the client
+# * bypass: ignore the "over-connected" ICAP service
+# * wait: wait (in a FIFO queue) for an ICAP connection slot
+# * force: proceed, ignoring the Max-Connections limit
+#
+# In SMP mode with N workers, each worker assumes the service
+# connection limit is Max-Connections/N, even though not all
+# workers may use a given service.
+#
+# The default value is "bypass" if service is bypassable,
+# otherwise it is set to "wait".
+#
+#
+# max-conn=number
+# Use the given number as the Max-Connections limit, regardless
+# of the Max-Connections value given by the service, if any.
+#
+# Older icap_service format without optional named parameters is
+# deprecated but supported for backward compatibility.
+#
+#Example:
+#icap_service svcBlocker reqmod_precache icap://icap1.mydomain.net:1344/reqmod bypass=0
+#icap_service svcLogger reqmod_precache icap://icap2.mydomain.net:1344/respmod routing=on
+#Default:
+# none
+
+# TAG: icap_class
+# This deprecated option was documented to define an ICAP service
+# chain, even though it actually defined a set of similar, redundant
+# services, and the chains were not supported.
+#
+# To define a set of redundant services, please use the
+# adaptation_service_set directive. For service chains, use
+# adaptation_service_chain.
+#Default:
+# none
+
+# TAG: icap_access
+# This option is deprecated. Please use adaptation_access, which
+# has the same ICAP functionality, but comes with better
+# documentation, and eCAP support.
+#Default:
+# none
+
+# eCAP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: ecap_enable on|off
+# Controls whether eCAP support is enabled.
+#Default:
+# ecap_enable off
+
+# TAG: ecap_service
+# Defines a single eCAP service
+#
+# ecap_service id vectoring_point uri [option ...]
+#
+# id: ID
+# an opaque identifier or name which is used to direct traffic to
+# this specific service. Must be unique among all adaptation
+# services in squid.conf.
+#
+# vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache
+# This specifies at which point of transaction processing the
+# eCAP service should be activated. *_postcache vectoring points
+# are not yet supported.
+#
+# uri: ecap://vendor/service_name?custom&cgi=style¶meters=optional
+# Squid uses the eCAP service URI to match this configuration
+# line with one of the dynamically loaded services. Each loaded
+# eCAP service must have a unique URI. Obtain the right URI from
+# the service provider.
+#
+# To activate a service, use the adaptation_access directive. To group
+# services, use adaptation_service_chain and adaptation_service_set.
+#
+# Service options are separated by white space. eCAP services support
+# the following name=value options:
+#
+# bypass=on|off|1|0
+# If set to 'on' or '1', the eCAP service is treated as optional.
+# If the service cannot be reached or malfunctions, Squid will try
+# to ignore any errors and process the message as if the service
+# was not enabled. No all eCAP errors can be bypassed.
+# If set to 'off' or '0', the eCAP service is treated as essential
+# and all eCAP errors will result in an error page returned to the
+# HTTP client.
+#
+# Bypass is off by default: services are treated as essential.
+#
+# routing=on|off|1|0
+# If set to 'on' or '1', the eCAP service is allowed to
+# dynamically change the current message adaptation plan by
+# returning a chain of services to be used next.
+#
+# Dynamic adaptation plan may cross or cover multiple supported
+# vectoring points in their natural processing order.
+#
+# Routing is not allowed by default.
+#
+# Older ecap_service format without optional named parameters is
+# deprecated but supported for backward compatibility.
+#
+#
+#Example:
+#ecap_service s1 reqmod_precache ecap://filters.R.us/leakDetector?on_error=block bypass=off
+#ecap_service s2 respmod_precache ecap://filters.R.us/virusFilter config=/etc/vf.cfg bypass=on
+#Default:
+# none
+
+# TAG: loadable_modules
+# Instructs Squid to load the specified dynamic module(s) or activate
+# preloaded module(s).
+#Example:
+#loadable_modules /usr/lib/MinimalAdapter.so
+#Default:
+# none
+
+# MESSAGE ADAPTATION OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: adaptation_service_set
+#
+# Configures an ordered set of similar, redundant services. This is
+# useful when hot standby or backup adaptation servers are available.
+#
+# adaptation_service_set set_name service_name1 service_name2 ...
+#
+# The named services are used in the set declaration order. The first
+# applicable adaptation service from the set is used first. The next
+# applicable service is tried if and only if the transaction with the
+# previous service fails and the message waiting to be adapted is still
+# intact.
+#
+# When adaptation starts, broken services are ignored as if they were
+# not a part of the set. A broken service is a down optional service.
+#
+# The services in a set must be attached to the same vectoring point
+# (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD).
+#
+# If all services in a set are optional then adaptation failures are
+# bypassable. If all services in the set are essential, then a
+# transaction failure with one service may still be retried using
+# another service from the set, but when all services fail, the master
+# transaction fails as well.
+#
+# A set may contain a mix of optional and essential services, but that
+# is likely to lead to surprising results because broken services become
+# ignored (see above), making previously bypassable failures fatal.
+# Technically, it is the bypassability of the last failed service that
+# matters.
+#
+# See also: adaptation_access adaptation_service_chain
+#
+#Example:
+#adaptation_service_set svcBlocker urlFilterPrimary urlFilterBackup
+#adaptation service_set svcLogger loggerLocal loggerRemote
+#Default:
+# none
+
+# TAG: adaptation_service_chain
+#
+# Configures a list of complementary services that will be applied
+# one-by-one, forming an adaptation chain or pipeline. This is useful
+# when Squid must perform different adaptations on the same message.
+#
+# adaptation_service_chain chain_name service_name1 svc_name2 ...
+#
+# The named services are used in the chain declaration order. The first
+# applicable adaptation service from the chain is used first. The next
+# applicable service is applied to the successful adaptation results of
+# the previous service in the chain.
+#
+# When adaptation starts, broken services are ignored as if they were
+# not a part of the chain. A broken service is a down optional service.
+#
+# Request satisfaction terminates the adaptation chain because Squid
+# does not currently allow declaration of RESPMOD services at the
+# "reqmod_precache" vectoring point (see icap_service or ecap_service).
+#
+# The services in a chain must be attached to the same vectoring point
+# (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD).
+#
+# A chain may contain a mix of optional and essential services. If an
+# essential adaptation fails (or the failure cannot be bypassed for
+# other reasons), the master transaction fails. Otherwise, the failure
+# is bypassed as if the failed adaptation service was not in the chain.
+#
+# See also: adaptation_access adaptation_service_set
+#
+#Example:
+#adaptation_service_chain svcRequest requestLogger urlFilter leakDetector
+#Default:
+# none
+
+# TAG: adaptation_access
+# Sends an HTTP transaction to an ICAP or eCAP adaptation service.
+#
+# adaptation_access service_name allow|deny [!]aclname...
+# adaptation_access set_name allow|deny [!]aclname...
+#
+# At each supported vectoring point, the adaptation_access
+# statements are processed in the order they appear in this
+# configuration file. Statements pointing to the following services
+# are ignored (i.e., skipped without checking their ACL):
+#
+# - services serving different vectoring points
+# - "broken-but-bypassable" services
+# - "up" services configured to ignore such transactions
+# (e.g., based on the ICAP Transfer-Ignore header).
+#
+# When a set_name is used, all services in the set are checked
+# using the same rules, to find the first applicable one. See
+# adaptation_service_set for details.
+#
+# If an access list is checked and there is a match, the
+# processing stops: For an "allow" rule, the corresponding
+# adaptation service is used for the transaction. For a "deny"
+# rule, no adaptation service is activated.
+#
+# It is currently not possible to apply more than one adaptation
+# service at the same vectoring point to the same HTTP transaction.
+#
+# See also: icap_service and ecap_service
+#
+#Example:
+#adaptation_access service_1 allow all
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: adaptation_service_iteration_limit
+# Limits the number of iterations allowed when applying adaptation
+# services to a message. If your longest adaptation set or chain
+# may have more than 16 services, increase the limit beyond its
+# default value of 16. If detecting infinite iteration loops sooner
+# is critical, make the iteration limit match the actual number
+# of services in your longest adaptation set or chain.
+#
+# Infinite adaptation loops are most likely with routing services.
+#
+# See also: icap_service routing=1
+#Default:
+# adaptation_service_iteration_limit 16
+
+# TAG: adaptation_masterx_shared_names
+# For each master transaction (i.e., the HTTP request and response
+# sequence, including all related ICAP and eCAP exchanges), Squid
+# maintains a table of metadata. The table entries are (name, value)
+# pairs shared among eCAP and ICAP exchanges. The table is destroyed
+# with the master transaction.
+#
+# This option specifies the table entry names that Squid must accept
+# from and forward to the adaptation transactions.
+#
+# An ICAP REQMOD or RESPMOD transaction may set an entry in the
+# shared table by returning an ICAP header field with a name
+# specified in adaptation_masterx_shared_names.
+#
+# An eCAP REQMOD or RESPMOD transaction may set an entry in the
+# shared table by implementing the libecap::visitEachOption() API
+# to provide an option with a name specified in
+# adaptation_masterx_shared_names.
+#
+# Squid will store and forward the set entry to subsequent adaptation
+# transactions within the same master transaction scope.
+#
+# Only one shared entry name is supported at this time.
+#
+#Example:
+## share authentication information among ICAP services
+#adaptation_masterx_shared_names X-Subscriber-ID
+#Default:
+# none
+
+# TAG: adaptation_meta
+# This option allows Squid administrator to add custom ICAP request
+# headers or eCAP options to Squid ICAP requests or eCAP transactions.
+# Use it to pass custom authentication tokens and other
+# transaction-state related meta information to an ICAP/eCAP service.
+#
+# The addition of a meta header is ACL-driven:
+# adaptation_meta name value [!]aclname ...
+#
+# Processing for a given header name stops after the first ACL list match.
+# Thus, it is impossible to add two headers with the same name. If no ACL
+# lists match for a given header name, no such header is added. For
+# example:
+#
+# # do not debug transactions except for those that need debugging
+# adaptation_meta X-Debug 1 needs_debugging
+#
+# # log all transactions except for those that must remain secret
+# adaptation_meta X-Log 1 !keep_secret
+#
+# # mark transactions from users in the "G 1" group
+# adaptation_meta X-Authenticated-Groups "G 1" authed_as_G1
+#
+# The "value" parameter may be a regular squid.conf token or a "double
+# quoted string". Within the quoted string, use backslash (\) to escape
+# any character, which is currently only useful for escaping backslashes
+# and double quotes. For example,
+# "this string has one backslash (\\) and two \"quotes\""
+#
+# Used adaptation_meta header values may be logged via %note
+# logformat code. If multiple adaptation_meta headers with the same name
+# are used during master transaction lifetime, the header values are
+# logged in the order they were used and duplicate values are ignored
+# (only the first repeated value will be logged).
+#Default:
+# none
+
+# TAG: icap_retry
+# This ACL determines which retriable ICAP transactions are
+# retried. Transactions that received a complete ICAP response
+# and did not have to consume or produce HTTP bodies to receive
+# that response are usually retriable.
+#
+# icap_retry allow|deny [!]aclname ...
+#
+# Squid automatically retries some ICAP I/O timeouts and errors
+# due to persistent connection race conditions.
+#
+# See also: icap_retry_limit
+#Default:
+# icap_retry deny all
+
+# TAG: icap_retry_limit
+# Limits the number of retries allowed.
+#
+# Communication errors due to persistent connection race
+# conditions are unavoidable, automatically retried, and do not
+# count against this limit.
+#
+# See also: icap_retry
+#Default:
+# No retries are allowed.
+
+# DNS OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: check_hostnames
+# For security and stability reasons Squid can check
+# hostnames for Internet standard RFC compliance. If you want
+# Squid to perform these checks turn this directive on.
+#Default:
+# check_hostnames off
+
+# TAG: allow_underscore
+# Underscore characters is not strictly allowed in Internet hostnames
+# but nevertheless used by many sites. Set this to off if you want
+# Squid to be strict about the standard.
+# This check is performed only when check_hostnames is set to on.
+#Default:
+# allow_underscore on
+
+# TAG: dns_retransmit_interval
+# Initial retransmit interval for DNS queries. The interval is
+# doubled each time all configured DNS servers have been tried.
+#Default:
+# dns_retransmit_interval 5 seconds
+
+# TAG: dns_timeout
+# DNS Query timeout. If no response is received to a DNS query
+# within this time all DNS servers for the queried domain
+# are assumed to be unavailable.
+#Default:
+# dns_timeout 30 seconds
+
+# TAG: dns_packet_max
+# Maximum number of bytes packet size to advertise via EDNS.
+# Set to "none" to disable EDNS large packet support.
+#
+# For legacy reasons DNS UDP replies will default to 512 bytes which
+# is too small for many responses. EDNS provides a means for Squid to
+# negotiate receiving larger responses back immediately without having
+# to failover with repeat requests. Responses larger than this limit
+# will retain the old behaviour of failover to TCP DNS.
+#
+# Squid has no real fixed limit internally, but allowing packet sizes
+# over 1500 bytes requires network jumbogram support and is usually not
+# necessary.
+#
+# WARNING: The RFC also indicates that some older resolvers will reply
+# with failure of the whole request if the extension is added. Some
+# resolvers have already been identified which will reply with mangled
+# EDNS response on occasion. Usually in response to many-KB jumbogram
+# sizes being advertised by Squid.
+# Squid will currently treat these both as an unable-to-resolve domain
+# even if it would be resolvable without EDNS.
+#Default:
+# EDNS disabled
+
+# TAG: dns_defnames on|off
+# Normally the RES_DEFNAMES resolver option is disabled
+# (see res_init(3)). This prevents caches in a hierarchy
+# from interpreting single-component hostnames locally. To allow
+# Squid to handle single-component names, enable this option.
+#Default:
+# Search for single-label domain names is disabled.
+
+# TAG: dns_multicast_local on|off
+# When set to on, Squid sends multicast DNS lookups on the local
+# network for domains ending in .local and .arpa.
+# This enables local servers and devices to be contacted in an
+# ad-hoc or zero-configuration network environment.
+#Default:
+# Search for .local and .arpa names is disabled.
+
+# TAG: dns_nameservers
+# Use this if you want to specify a list of DNS name servers
+# (IP addresses) to use instead of those given in your
+# /etc/resolv.conf file.
+#
+# On Windows platforms, if no value is specified here or in
+# the /etc/resolv.conf file, the list of DNS name servers are
+# taken from the Windows registry, both static and dynamic DHCP
+# configurations are supported.
+#
+# Example: dns_nameservers 10.0.0.1 192.172.0.4
+#Default:
+# Use operating system definitions
+
+# TAG: hosts_file
+# Location of the host-local IP name-address associations
+# database. Most Operating Systems have such a file on different
+# default locations:
+# - Un*X & Linux: /etc/hosts
+# - Windows NT/2000: %SystemRoot%\system32\drivers\etc\hosts
+# (%SystemRoot% value install default is c:\winnt)
+# - Windows XP/2003: %SystemRoot%\system32\drivers\etc\hosts
+# (%SystemRoot% value install default is c:\windows)
+# - Windows 9x/Me: %windir%\hosts
+# (%windir% value is usually c:\windows)
+# - Cygwin: /etc/hosts
+#
+# The file contains newline-separated definitions, in the
+# form ip_address_in_dotted_form name [name ...] names are
+# whitespace-separated. Lines beginning with an hash (#)
+# character are comments.
+#
+# The file is checked at startup and upon configuration.
+# If set to 'none', it won't be checked.
+# If append_domain is used, that domain will be added to
+# domain-local (i.e. not containing any dot character) host
+# definitions.
+#Default:
+# hosts_file /etc/hosts
+
+# TAG: append_domain
+# Appends local domain name to hostnames without any dots in
+# them. append_domain must begin with a period.
+#
+# Be warned there are now Internet names with no dots in
+# them using only top-domain names, so setting this may
+# cause some Internet sites to become unavailable.
+#
+#Example:
+# append_domain .yourdomain.com
+#Default:
+# Use operating system definitions
+
+# TAG: ignore_unknown_nameservers
+# By default Squid checks that DNS responses are received
+# from the same IP addresses they are sent to. If they
+# don't match, Squid ignores the response and writes a warning
+# message to cache.log. You can allow responses from unknown
+# nameservers by setting this option to 'off'.
+#Default:
+# ignore_unknown_nameservers on
+
+# TAG: dns_v4_first
+# With the IPv6 Internet being as fast or faster than IPv4 Internet
+# for most networks Squid prefers to contact websites over IPv6.
+#
+# This option reverses the order of preference to make Squid contact
+# dual-stack websites over IPv4 first. Squid will still perform both
+# IPv6 and IPv4 DNS lookups before connecting.
+#
+# WARNING:
+# This option will restrict the situations under which IPv6
+# connectivity is used (and tested), potentially hiding network
+# problems which would otherwise be detected and warned about.
+#Default:
+# dns_v4_first off
+
+# TAG: ipcache_size (number of entries)
+# Maximum number of DNS IP cache entries.
+#Default:
+# ipcache_size 1024
+
+# TAG: ipcache_low (percent)
+#Default:
+# ipcache_low 90
+
+# TAG: ipcache_high (percent)
+# The size, low-, and high-water marks for the IP cache.
+#Default:
+# ipcache_high 95
+
+# TAG: fqdncache_size (number of entries)
+# Maximum number of FQDN cache entries.
+#Default:
+# fqdncache_size 1024
+
+# MISCELLANEOUS
+# -----------------------------------------------------------------------------
+
+# TAG: configuration_includes_quoted_values on|off
+# If set, Squid will recognize each "quoted string" after a configuration
+# directive as a single parameter. The quotes are stripped before the
+# parameter value is interpreted or used.
+# See "Values with spaces, quotes, and other special characters"
+# section for more details.
+#Default:
+# configuration_includes_quoted_values off
+
+# TAG: memory_pools on|off
+# If set, Squid will keep pools of allocated (but unused) memory
+# available for future use. If memory is a premium on your
+# system and you believe your malloc library outperforms Squid
+# routines, disable this.
+#Default:
+# memory_pools on
+
+# TAG: memory_pools_limit (bytes)
+# Used only with memory_pools on:
+# memory_pools_limit 50 MB
+#
+# If set to a non-zero value, Squid will keep at most the specified
+# limit of allocated (but unused) memory in memory pools. All free()
+# requests that exceed this limit will be handled by your malloc
+# library. Squid does not pre-allocate any memory, just safe-keeps
+# objects that otherwise would be free()d. Thus, it is safe to set
+# memory_pools_limit to a reasonably high value even if your
+# configuration will use less memory.
+#
+# If set to none, Squid will keep all memory it can. That is, there
+# will be no limit on the total amount of memory used for safe-keeping.
+#
+# To disable memory allocation optimization, do not set
+# memory_pools_limit to 0 or none. Set memory_pools to "off" instead.
+#
+# An overhead for maintaining memory pools is not taken into account
+# when the limit is checked. This overhead is close to four bytes per
+# object kept. However, pools may actually _save_ memory because of
+# reduced memory thrashing in your malloc library.
+#Default:
+# memory_pools_limit 5 MB
+
+# TAG: forwarded_for on|off|transparent|truncate|delete
+# If set to "on", Squid will append your client's IP address
+# in the HTTP requests it forwards. By default it looks like:
+#
+# X-Forwarded-For: 192.1.2.3
+#
+# If set to "off", it will appear as
+#
+# X-Forwarded-For: unknown
+#
+# If set to "transparent", Squid will not alter the
+# X-Forwarded-For header in any way.
+#
+# If set to "delete", Squid will delete the entire
+# X-Forwarded-For header.
+#
+# If set to "truncate", Squid will remove all existing
+# X-Forwarded-For entries, and place the client IP as the sole entry.
+#Default:
+# forwarded_for on
+
+# TAG: cachemgr_passwd
+# Specify passwords for cachemgr operations.
+#
+# Usage: cachemgr_passwd password action action ...
+#
+# Some valid actions are (see cache manager menu for a full list):
+# 5min
+# 60min
+# asndb
+# authenticator
+# cbdata
+# client_list
+# comm_incoming
+# config *
+# counters
+# delay
+# digest_stats
+# dns
+# events
+# filedescriptors
+# fqdncache
+# histograms
+# http_headers
+# info
+# io
+# ipcache
+# mem
+# menu
+# netdb
+# non_peers
+# objects
+# offline_toggle *
+# pconn
+# peer_select
+# reconfigure *
+# redirector
+# refresh
+# server_list
+# shutdown *
+# store_digest
+# storedir
+# utilization
+# via_headers
+# vm_objects
+#
+# * Indicates actions which will not be performed without a
+# valid password, others can be performed if not listed here.
+#
+# To disable an action, set the password to "disable".
+# To allow performing an action without a password, set the
+# password to "none".
+#
+# Use the keyword "all" to set the same password for all actions.
+#
+#Example:
+# cachemgr_passwd secret shutdown
+# cachemgr_passwd lesssssssecret info stats/objects
+# cachemgr_passwd disable all
+#Default:
+# No password. Actions which require password are denied.
+
+# TAG: client_db on|off
+# If you want to disable collecting per-client statistics,
+# turn off client_db here.
+#Default:
+# client_db on
+
+# TAG: refresh_all_ims on|off
+# When you enable this option, squid will always check
+# the origin server for an update when a client sends an
+# If-Modified-Since request. Many browsers use IMS
+# requests when the user requests a reload, and this
+# ensures those clients receive the latest version.
+#
+# By default (off), squid may return a Not Modified response
+# based on the age of the cached version.
+#Default:
+# refresh_all_ims off
+
+# TAG: reload_into_ims on|off
+# When you enable this option, client no-cache or ``reload''
+# requests will be changed to If-Modified-Since requests.
+# Doing this VIOLATES the HTTP standard. Enabling this
+# feature could make you liable for problems which it
+# causes.
+#
+# see also refresh_pattern for a more selective approach.
+#Default:
+# reload_into_ims off
+
+# TAG: connect_retries
+# This sets the maximum number of connection attempts made for each
+# TCP connection. The connect_retries attempts must all still
+# complete within the connection timeout period.
+#
+# The default is not to re-try if the first connection attempt fails.
+# The (not recommended) maximum is 10 tries.
+#
+# A warning message will be generated if it is set to a too-high
+# value and the configured value will be over-ridden.
+#
+# Note: These re-tries are in addition to forward_max_tries
+# which limit how many different addresses may be tried to find
+# a useful server.
+#Default:
+# Do not retry failed connections.
+
+# TAG: retry_on_error
+# If set to ON Squid will automatically retry requests when
+# receiving an error response with status 403 (Forbidden),
+# 500 (Internal Error), 501 or 503 (Service not available).
+# Status 502 and 504 (Gateway errors) are always retried.
+#
+# This is mainly useful if you are in a complex cache hierarchy to
+# work around access control errors.
+#
+# NOTE: This retry will attempt to find another working destination.
+# Which is different from the server which just failed.
+#Default:
+# retry_on_error off
+
+# TAG: as_whois_server
+# WHOIS server to query for AS numbers. NOTE: AS numbers are
+# queried only when Squid starts up, not for every request.
+#Default:
+# as_whois_server whois.ra.net
+
+# TAG: offline_mode
+# Enable this option and Squid will never try to validate cached
+# objects.
+#Default:
+# offline_mode off
+
+# TAG: uri_whitespace
+# What to do with requests that have whitespace characters in the
+# URI. Options:
+#
+# strip: The whitespace characters are stripped out of the URL.
+# This is the behavior recommended by RFC2396 and RFC3986
+# for tolerant handling of generic URI.
+# NOTE: This is one difference between generic URI and HTTP URLs.
+#
+# deny: The request is denied. The user receives an "Invalid
+# Request" message.
+# This is the behaviour recommended by RFC2616 for safe
+# handling of HTTP request URL.
+#
+# allow: The request is allowed and the URI is not changed. The
+# whitespace characters remain in the URI. Note the
+# whitespace is passed to redirector processes if they
+# are in use.
+# Note this may be considered a violation of RFC2616
+# request parsing where whitespace is prohibited in the
+# URL field.
+#
+# encode: The request is allowed and the whitespace characters are
+# encoded according to RFC1738.
+#
+# chop: The request is allowed and the URI is chopped at the
+# first whitespace.
+#
+#
+# NOTE the current Squid implementation of encode and chop violates
+# RFC2616 by not using a 301 redirect after altering the URL.
+#Default:
+# uri_whitespace strip
+
+# TAG: chroot
+# Specifies a directory where Squid should do a chroot() while
+# initializing. This also causes Squid to fully drop root
+# privileges after initializing. This means, for example, if you
+# use a HTTP port less than 1024 and try to reconfigure, you may
+# get an error saying that Squid can not open the port.
+#Default:
+# none
+
+# TAG: balance_on_multiple_ip
+# Modern IP resolvers in squid sort lookup results by preferred access.
+# By default squid will use these IP in order and only rotates to
+# the next listed when the most preffered fails.
+#
+# Some load balancing servers based on round robin DNS have been
+# found not to preserve user session state across requests
+# to different IP addresses.
+#
+# Enabling this directive Squid rotates IP's per request.
+#Default:
+# balance_on_multiple_ip off
+
+# TAG: pipeline_prefetch
+# HTTP clients may send a pipeline of 1+N requests to Squid using a
+# single connection, without waiting for Squid to respond to the first
+# of those requests. This option limits the number of concurrent
+# requests Squid will try to handle in parallel. If set to N, Squid
+# will try to receive and process up to 1+N requests on the same
+# connection concurrently.
+#
+# Defaults to 0 (off) for bandwidth management and access logging
+# reasons.
+#
+# NOTE: pipelining requires persistent connections to clients.
+#
+# WARNING: pipelining breaks NTLM and Negotiate/Kerberos authentication.
+#Default:
+# Do not pre-parse pipelined requests.
+
+# TAG: high_response_time_warning (msec)
+# If the one-minute median response time exceeds this value,
+# Squid prints a WARNING with debug level 0 to get the
+# administrators attention. The value is in milliseconds.
+#Default:
+# disabled.
+
+# TAG: high_page_fault_warning
+# If the one-minute average page fault rate exceeds this
+# value, Squid prints a WARNING with debug level 0 to get
+# the administrators attention. The value is in page faults
+# per second.
+#Default:
+# disabled.
+
+# TAG: high_memory_warning
+# Note: This option is only available if Squid is rebuilt with the
+# GNU Malloc with mstats()
+#
+# If the memory usage (as determined by gnumalloc, if available and used)
+# exceeds this amount, Squid prints a WARNING with debug level 0 to get
+# the administrators attention.
+#Default:
+# disabled.
+
+# TAG: sleep_after_fork (microseconds)
+# When this is set to a non-zero value, the main Squid process
+# sleeps the specified number of microseconds after a fork()
+# system call. This sleep may help the situation where your
+# system reports fork() failures due to lack of (virtual)
+# memory. Note, however, if you have a lot of child
+# processes, these sleep delays will add up and your
+# Squid will not service requests for some amount of time
+# until all the child processes have been started.
+# On Windows value less then 1000 (1 milliseconds) are
+# rounded to 1000.
+#Default:
+# sleep_after_fork 0
+
+# TAG: windows_ipaddrchangemonitor on|off
+# Note: This option is only available if Squid is rebuilt with the
+# MS Windows
+#
+# On Windows Squid by default will monitor IP address changes and will
+# reconfigure itself after any detected event. This is very useful for
+# proxies connected to internet with dial-up interfaces.
+# In some cases (a Proxy server acting as VPN gateway is one) it could be
+# desiderable to disable this behaviour setting this to 'off'.
+# Note: after changing this, Squid service must be restarted.
+#Default:
+# windows_ipaddrchangemonitor on
+
+# TAG: eui_lookup
+# Whether to lookup the EUI or MAC address of a connected client.
+#Default:
+# eui_lookup on
+
+# TAG: max_filedescriptors
+# Reduce the maximum number of filedescriptors supported below
+# the usual operating system defaults.
+#
+# Remove from squid.conf to inherit the current ulimit setting.
+#
+# Note: Changing this requires a restart of Squid. Also
+# not all I/O types supports large values (eg on Windows).
+#Default:
+# Use operating system limits set by ulimit.
+
diff --git a/roles/squid/files/squid.s-proxy.conf b/roles/squid/files/squid.s-proxy.conf
new file mode 100644
index 0000000..34f00a3
--- /dev/null
+++ b/roles/squid/files/squid.s-proxy.conf
@@ -0,0 +1,8563 @@
+# WELCOME TO SQUID 4.6
+# ----------------------------
+#
+# This is the documentation for the Squid configuration file.
+# This documentation can also be found online at:
+# http://www.squid-cache.org/Doc/config/
+#
+# You may wish to look at the Squid home page and wiki for the
+# FAQ and other documentation:
+# http://www.squid-cache.org/
+# http://wiki.squid-cache.org/SquidFaq
+# http://wiki.squid-cache.org/ConfigExamples
+#
+# This documentation shows what the defaults for various directives
+# happen to be. If you don't need to change the default, you should
+# leave the line out of your squid.conf in most cases.
+#
+# In some cases "none" refers to no default setting at all,
+# while in other cases it refers to the value of the option
+# - the comments for that keyword indicate if this is the case.
+#
+
+# Configuration options can be included using the "include" directive.
+# Include takes a list of files to include. Quoting and wildcards are
+# supported.
+#
+# For example,
+#
+# include /path/to/included/file/squid.acl.config
+#
+# Includes can be nested up to a hard-coded depth of 16 levels.
+# This arbitrary restriction is to prevent recursive include references
+# from causing Squid entering an infinite loop whilst trying to load
+# configuration files.
+#
+# Values with byte units
+#
+# Squid accepts size units on some size related directives. All
+# such directives are documented with a default value displaying
+# a unit.
+#
+# Units accepted by Squid are:
+# bytes - byte
+# KB - Kilobyte (1024 bytes)
+# MB - Megabyte
+# GB - Gigabyte
+#
+# Values with spaces, quotes, and other special characters
+#
+# Squid supports directive parameters with spaces, quotes, and other
+# special characters. Surround such parameters with "double quotes". Use
+# the configuration_includes_quoted_values directive to enable or
+# disable that support.
+#
+# Squid supports reading configuration option parameters from external
+# files using the syntax:
+# parameters("/path/filename")
+# For example:
+# acl whitelist dstdomain parameters("/etc/squid/whitelist.txt")
+#
+# Conditional configuration
+#
+# If-statements can be used to make configuration directives
+# depend on conditions:
+#
+# if <CONDITION>
+# ... regular configuration directives ...
+# [else
+# ... regular configuration directives ...]
+# endif
+#
+# The else part is optional. The keywords "if", "else", and "endif"
+# must be typed on their own lines, as if they were regular
+# configuration directives.
+#
+# NOTE: An else-if condition is not supported.
+#
+# These individual conditions types are supported:
+#
+# true
+# Always evaluates to true.
+# false
+# Always evaluates to false.
+# <integer> = <integer>
+# Equality comparison of two integer numbers.
+#
+#
+# SMP-Related Macros
+#
+# The following SMP-related preprocessor macros can be used.
+#
+# ${process_name} expands to the current Squid process "name"
+# (e.g., squid1, squid2, or cache1).
+#
+# ${process_number} expands to the current Squid process
+# identifier, which is an integer number (e.g., 1, 2, 3) unique
+# across all Squid processes of the current service instance.
+#
+# ${service_name} expands into the current Squid service instance
+# name identifier which is provided by -n on the command line.
+#
+# Logformat Macros
+#
+# Logformat macros can be used in many places outside of the logformat
+# directive. In theory, all of the logformat codes can be used as %macros,
+# where they are supported. In practice, a %macro expands as a dash (-) when
+# the transaction does not yet have enough information and a value is needed.
+#
+# There is no definitive list of what tokens are available at the various
+# stages of the transaction.
+#
+# And some information may already be available to Squid but not yet
+# committed where the macro expansion code can access it (report
+# such instances!). The macro will be expanded into a single dash
+# ('-') in such cases. Not all macros have been tested.
+#
+
+# TAG: broken_vary_encoding
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: cache_vary
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: error_map
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: external_refresh_check
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: location_rewrite_program
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: refresh_stale_hit
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: cache_peer_domain
+# Replace with dstdomain ACLs and cache_peer_access.
+#Default:
+# none
+
+# TAG: ie_refresh
+# Remove this line. The behaviour enabled by this is no longer needed.
+#Default:
+# none
+
+# TAG: sslproxy_cafile
+# Remove this line. Use tls_outgoing_options cafile= instead.
+#Default:
+# none
+
+# TAG: sslproxy_capath
+# Remove this line. Use tls_outgoing_options capath= instead.
+#Default:
+# none
+
+# TAG: sslproxy_cipher
+# Remove this line. Use tls_outgoing_options cipher= instead.
+#Default:
+# none
+
+# TAG: sslproxy_client_certificate
+# Remove this line. Use tls_outgoing_options cert= instead.
+#Default:
+# none
+
+# TAG: sslproxy_client_key
+# Remove this line. Use tls_outgoing_options key= instead.
+#Default:
+# none
+
+# TAG: sslproxy_flags
+# Remove this line. Use tls_outgoing_options flags= instead.
+#Default:
+# none
+
+# TAG: sslproxy_options
+# Remove this line. Use tls_outgoing_options options= instead.
+#Default:
+# none
+
+# TAG: sslproxy_version
+# Remove this line. Use tls_outgoing_options options= instead.
+#Default:
+# none
+
+# TAG: hierarchy_stoplist
+# Remove this line. Use always_direct or cache_peer_access ACLs instead if you need to prevent cache_peer use.
+#Default:
+# none
+
+# TAG: log_access
+# Remove this line. Use acls with access_log directives to control access logging
+#Default:
+# none
+
+# TAG: log_icap
+# Remove this line. Use acls with icap_log directives to control icap logging
+#Default:
+# none
+
+# TAG: ignore_ims_on_miss
+# Remove this line. The HTTP/1.1 feature is now configured by 'cache_miss_revalidate'.
+#Default:
+# none
+
+# TAG: balance_on_multiple_ip
+# Remove this line. Squid performs a 'Happy Eyeballs' algorithm, this multiple-IP algorithm is not longer relevant.
+#Default:
+# none
+
+# TAG: chunked_request_body_max_size
+# Remove this line. Squid is now HTTP/1.1 compliant.
+#Default:
+# none
+
+# TAG: dns_v4_fallback
+# Remove this line. Squid performs a 'Happy Eyeballs' algorithm, the 'fallback' algorithm is no longer relevant.
+#Default:
+# none
+
+# TAG: emulate_httpd_log
+# Replace this with an access_log directive using the format 'common' or 'combined'.
+#Default:
+# none
+
+# TAG: forward_log
+# Use a regular access.log with ACL limiting it to MISS events.
+#Default:
+# none
+
+# TAG: ftp_list_width
+# Remove this line. Configure FTP page display using the CSS controls in errorpages.css instead.
+#Default:
+# none
+
+# TAG: ignore_expect_100
+# Remove this line. The HTTP/1.1 feature is now fully supported by default.
+#Default:
+# none
+
+# TAG: log_fqdn
+# Remove this option from your config. To log FQDN use %>A in the log format.
+#Default:
+# none
+
+# TAG: log_ip_on_direct
+# Remove this option from your config. To log server or peer names use %<A in the log format.
+#Default:
+# none
+
+# TAG: maximum_single_addr_tries
+# Replaced by connect_retries. The behaviour has changed, please read the documentation before altering.
+#Default:
+# none
+
+# TAG: referer_log
+# Replace this with an access_log directive using the format 'referrer'.
+#Default:
+# none
+
+# TAG: update_headers
+# Remove this line. The feature is supported by default in storage types where update is implemented.
+#Default:
+# none
+
+# TAG: url_rewrite_concurrency
+# Remove this line. Set the 'concurrency=' option of url_rewrite_children instead.
+#Default:
+# none
+
+# TAG: useragent_log
+# Replace this with an access_log directive using the format 'useragent'.
+#Default:
+# none
+
+# TAG: dns_testnames
+# Remove this line. DNS is no longer tested on startup.
+#Default:
+# none
+
+# TAG: extension_methods
+# Remove this line. All valid methods for HTTP are accepted by default.
+#Default:
+# none
+
+# TAG: zero_buffers
+#Default:
+# none
+
+# TAG: incoming_rate
+#Default:
+# none
+
+# TAG: server_http11
+# Remove this line. HTTP/1.1 is supported by default.
+#Default:
+# none
+
+# TAG: upgrade_http0.9
+# Remove this line. ICY/1.0 streaming protocol is supported by default.
+#Default:
+# none
+
+# TAG: zph_local
+# Alter these entries. Use the qos_flows directive instead.
+#Default:
+# none
+
+# TAG: header_access
+# Since squid-3.0 replace with request_header_access or reply_header_access
+# depending on whether you wish to match client requests or server replies.
+#Default:
+# none
+
+# TAG: httpd_accel_no_pmtu_disc
+# Since squid-3.0 use the 'disable-pmtu-discovery' flag on http_port instead.
+#Default:
+# none
+
+# TAG: wais_relay_host
+# Replace this line with 'cache_peer' configuration.
+#Default:
+# none
+
+# TAG: wais_relay_port
+# Replace this line with 'cache_peer' configuration.
+#Default:
+# none
+
+# OPTIONS FOR SMP
+# -----------------------------------------------------------------------------
+
+# TAG: workers
+# Number of main Squid processes or "workers" to fork and maintain.
+# 0: "no daemon" mode, like running "squid -N ..."
+# 1: "no SMP" mode, start one main Squid process daemon (default)
+# N: start N main Squid process daemons (i.e., SMP mode)
+#
+# In SMP mode, each worker does nearly all what a single Squid daemon
+# does (e.g., listen on http_port and forward HTTP requests).
+#Default:
+# SMP support disabled.
+
+# TAG: cpu_affinity_map
+# Usage: cpu_affinity_map process_numbers=P1,P2,... cores=C1,C2,...
+#
+# Sets 1:1 mapping between Squid processes and CPU cores. For example,
+#
+# cpu_affinity_map process_numbers=1,2,3,4 cores=1,3,5,7
+#
+# affects processes 1 through 4 only and places them on the first
+# four even cores, starting with core #1.
+#
+# CPU cores are numbered starting from 1. Requires support for
+# sched_getaffinity(2) and sched_setaffinity(2) system calls.
+#
+# Multiple cpu_affinity_map options are merged.
+#
+# See also: workers
+#Default:
+# Let operating system decide.
+
+# TAG: shared_memory_locking on|off
+# Whether to ensure that all required shared memory is available by
+# "locking" that shared memory into RAM when Squid starts. The
+# alternative is faster startup time followed by slightly slower
+# performance and, if not enough RAM is actually available during
+# runtime, mysterious crashes.
+#
+# SMP Squid uses many shared memory segments. These segments are
+# brought into Squid memory space using an mmap(2) system call. During
+# Squid startup, the mmap() call often succeeds regardless of whether
+# the system has enough RAM. In general, Squid cannot tell whether the
+# kernel applies this "optimistic" memory allocation policy (but
+# popular modern kernels usually use it).
+#
+# Later, if Squid attempts to actually access the mapped memory
+# regions beyond what the kernel is willing to allocate, the
+# "optimistic" kernel simply kills Squid kid with a SIGBUS signal.
+# Some of the memory limits enforced by the kernel are currently
+# poorly understood: We do not know how to detect and check them. This
+# option ensures that the mapped memory will be available.
+#
+# This option may have a positive performance side-effect: Locking
+# memory at start avoids runtime paging I/O. Paging slows Squid down.
+#
+# Locking memory may require a large enough RLIMIT_MEMLOCK OS limit,
+# CAP_IPC_LOCK capability, or equivalent.
+#Default:
+# shared_memory_locking off
+
+# TAG: hopeless_kid_revival_delay time-units
+# Normally, when a kid process dies, Squid immediately restarts the
+# kid. A kid experiencing frequent deaths is marked as "hopeless" for
+# the duration specified by this directive. Hopeless kids are not
+# automatically restarted.
+#
+# Currently, zero values are not supported because they result in
+# misconfigured SMP Squid instances running forever, endlessly
+# restarting each dying kid. To effectively disable hopeless kids
+# revival, set the delay to a huge value (e.g., 1 year).
+#
+# Reconfiguration also clears all hopeless kids designations, allowing
+# for manual revival of hopeless kids.
+#Default:
+# hopeless_kid_revival_delay 1 hour
+
+# OPTIONS FOR AUTHENTICATION
+# -----------------------------------------------------------------------------
+
+# TAG: auth_param
+# This is used to define parameters for the various authentication
+# schemes supported by Squid.
+#
+# format: auth_param scheme parameter [setting]
+#
+# The order in which authentication schemes are presented to the client is
+# dependent on the order the scheme first appears in config file. IE
+# has a bug (it's not RFC 2617 compliant) in that it will use the basic
+# scheme if basic is the first entry presented, even if more secure
+# schemes are presented. For now use the order in the recommended
+# settings section below. If other browsers have difficulties (don't
+# recognize the schemes offered even if you are using basic) either
+# put basic first, or disable the other schemes (by commenting out their
+# program entry).
+#
+# Once an authentication scheme is fully configured, it can only be
+# shutdown by shutting squid down and restarting. Changes can be made on
+# the fly and activated with a reconfigure. I.E. You can change to a
+# different helper, but not unconfigure the helper completely.
+#
+# Please note that while this directive defines how Squid processes
+# authentication it does not automatically activate authentication.
+# To use authentication you must in addition make use of ACLs based
+# on login name in http_access (proxy_auth, proxy_auth_regex or
+# external with %LOGIN used in the format tag). The browser will be
+# challenged for authentication on the first such acl encountered
+# in http_access processing and will also be re-challenged for new
+# login credentials if the request is being denied by a proxy_auth
+# type acl.
+#
+# WARNING: authentication can't be used in a transparently intercepting
+# proxy as the client then thinks it is talking to an origin server and
+# not the proxy. This is a limitation of bending the TCP/IP protocol to
+# transparently intercepting port 80, not a limitation in Squid.
+# Ports flagged 'transparent', 'intercept', or 'tproxy' have
+# authentication disabled.
+#
+# === Parameters common to all schemes. ===
+#
+# "program" cmdline
+# Specifies the command for the external authenticator.
+#
+# By default, each authentication scheme is not used unless a
+# program is specified.
+#
+# See http://wiki.squid-cache.org/Features/AddonHelpers for
+# more details on helper operations and creating your own.
+#
+# "key_extras" format
+# Specifies a string to be append to request line format for
+# the authentication helper. "Quoted" format values may contain
+# spaces and logformat %macros. In theory, any logformat %macro
+# can be used. In practice, a %macro expands as a dash (-) if
+# the helper request is sent before the required macro
+# information is available to Squid.
+#
+# By default, Squid uses request formats provided in
+# scheme-specific examples below (search for %credentials).
+#
+# The expanded key_extras value is added to the Squid credentials
+# cache and, hence, will affect authentication. It can be used to
+# autenticate different users with identical user names (e.g.,
+# when user authentication depends on http_port).
+#
+# Avoid adding frequently changing information to key_extras. For
+# example, if you add user source IP, and it changes frequently
+# in your environment, then max_user_ip ACL is going to treat
+# every user+IP combination as a unique "user", breaking the ACL
+# and wasting a lot of memory on those user records. It will also
+# force users to authenticate from scratch whenever their IP
+# changes.
+#
+# "realm" string
+# Specifies the protection scope (aka realm name) which is to be
+# reported to the client for the authentication scheme. It is
+# commonly part of the text the user will see when prompted for
+# their username and password.
+#
+# For Basic the default is "Squid proxy-caching web server".
+# For Digest there is no default, this parameter is mandatory.
+# For NTLM and Negotiate this parameter is ignored.
+#
+# "children" numberofchildren [startup=N] [idle=N] [concurrency=N]
+# [queue-size=N] [on-persistent-overload=action]
+#
+# The maximum number of authenticator processes to spawn. If
+# you start too few Squid will have to wait for them to process
+# a backlog of credential verifications, slowing it down. When
+# password verifications are done via a (slow) network you are
+# likely to need lots of authenticator processes.
+#
+# The startup= and idle= options permit some skew in the exact
+# amount run. A minimum of startup=N will begin during startup
+# and reconfigure. Squid will start more in groups of up to
+# idle=N in an attempt to meet traffic needs and to keep idle=N
+# free above those traffic needs up to the maximum.
+#
+# The concurrency= option sets the number of concurrent requests
+# the helper can process. The default of 0 is used for helpers
+# who only supports one request at a time. Setting this to a
+# number greater than 0 changes the protocol used to include a
+# channel ID field first on the request/response line, allowing
+# multiple requests to be sent to the same helper in parallel
+# without waiting for the response.
+#
+# Concurrency must not be set unless it's known the helper
+# supports the input format with channel-ID fields.
+#
+# The queue-size option sets the maximum number of queued
+# requests. A request is queued when no existing child can
+# accept it due to concurrency limit and no new child can be
+# started due to numberofchildren limit. The default maximum is
+# 2*numberofchildren. Squid is allowed to temporarily exceed the
+# configured maximum, marking the affected helper as
+# "overloaded". If the helper overload lasts more than 3
+# minutes, the action prescribed by the on-persistent-overload
+# option applies.
+#
+# The on-persistent-overload=action option specifies Squid
+# reaction to a new helper request arriving when the helper
+# has been overloaded for more that 3 minutes already. The number
+# of queued requests determines whether the helper is overloaded
+# (see the queue-size option).
+#
+# Two actions are supported:
+#
+# die Squid worker quits. This is the default behavior.
+#
+# ERR Squid treats the helper request as if it was
+# immediately submitted, and the helper immediately
+# replied with an ERR response. This action has no effect
+# on the already queued and in-progress helper requests.
+#
+# NOTE: NTLM and Negotiate schemes do not support concurrency
+# in the Squid code module even though some helpers can.
+#
+#
+#
+# === Example Configuration ===
+#
+# This configuration displays the recommended authentication scheme
+# order from most to least secure with recommended minimum configuration
+# settings for each scheme:
+#
+##auth_param negotiate program <uncomment and complete this line to activate>
+##auth_param negotiate children 20 startup=0 idle=1
+##auth_param negotiate keep_alive on
+##
+##auth_param digest program <uncomment and complete this line to activate>
+##auth_param digest children 20 startup=0 idle=1
+##auth_param digest realm Squid proxy-caching web server
+##auth_param digest nonce_garbage_interval 5 minutes
+##auth_param digest nonce_max_duration 30 minutes
+##auth_param digest nonce_max_count 50
+##
+##auth_param ntlm program <uncomment and complete this line to activate>
+##auth_param ntlm children 20 startup=0 idle=1
+##auth_param ntlm keep_alive on
+##
+##auth_param basic program <uncomment and complete this line>
+##auth_param basic children 5 startup=5 idle=1
+##auth_param basic realm Squid proxy-caching web server
+##auth_param basic credentialsttl 2 hours
+#Default:
+# none
+
+# TAG: authenticate_cache_garbage_interval
+# The time period between garbage collection across the username cache.
+# This is a trade-off between memory utilization (long intervals - say
+# 2 days) and CPU (short intervals - say 1 minute). Only change if you
+# have good reason to.
+#Default:
+# authenticate_cache_garbage_interval 1 hour
+
+# TAG: authenticate_ttl
+# The time a user & their credentials stay in the logged in
+# user cache since their last request. When the garbage
+# interval passes, all user credentials that have passed their
+# TTL are removed from memory.
+#Default:
+# authenticate_ttl 1 hour
+
+# TAG: authenticate_ip_ttl
+# If you use proxy authentication and the 'max_user_ip' ACL,
+# this directive controls how long Squid remembers the IP
+# addresses associated with each user. Use a small value
+# (e.g., 60 seconds) if your users might change addresses
+# quickly, as is the case with dialup. You might be safe
+# using a larger value (e.g., 2 hours) in a corporate LAN
+# environment with relatively static address assignments.
+#Default:
+# authenticate_ip_ttl 1 second
+
+# ACCESS CONTROLS
+# -----------------------------------------------------------------------------
+
+# TAG: external_acl_type
+# This option defines external acl classes using a helper program
+# to look up the status
+#
+# external_acl_type name [options] FORMAT /path/to/helper [helper arguments]
+#
+# Options:
+#
+# ttl=n TTL in seconds for cached results (defaults to 3600
+# for 1 hour)
+#
+# negative_ttl=n
+# TTL for cached negative lookups (default same
+# as ttl)
+#
+# grace=n Percentage remaining of TTL where a refresh of a
+# cached entry should be initiated without needing to
+# wait for a new reply. (default is for no grace period)
+#
+# cache=n The maximum number of entries in the result cache. The
+# default limit is 262144 entries. Each cache entry usually
+# consumes at least 256 bytes. Squid currently does not remove
+# expired cache entries until the limit is reached, so a proxy
+# will sooner or later reach the limit. The expanded FORMAT
+# value is used as the cache key, so if the details in FORMAT
+# are highly variable, a larger cache may be needed to produce
+# reduction in helper load.
+#
+# children-max=n
+# Maximum number of acl helper processes spawned to service
+# external acl lookups of this type. (default 5)
+#
+# children-startup=n
+# Minimum number of acl helper processes to spawn during
+# startup and reconfigure to service external acl lookups
+# of this type. (default 0)
+#
+# children-idle=n
+# Number of acl helper processes to keep ahead of traffic
+# loads. Squid will spawn this many at once whenever load
+# rises above the capabilities of existing processes.
+# Up to the value of children-max. (default 1)
+#
+# concurrency=n concurrency level per process. Only used with helpers
+# capable of processing more than one query at a time.
+#
+# queue-size=N The queue-size option sets the maximum number of
+# queued requests. A request is queued when no existing
+# helper can accept it due to concurrency limit and no
+# new helper can be started due to children-max limit.
+# If the queued requests exceed queue size, the acl is
+# ignored. The default value is set to 2*children-max.
+#
+# protocol=2.5 Compatibility mode for Squid-2.5 external acl helpers.
+#
+# ipv4 / ipv6 IP protocol used to communicate with this helper.
+# The default is to auto-detect IPv6 and use it when available.
+#
+#
+# FORMAT is a series of %macro codes. See logformat directive for a full list
+# of the accepted codes. Although note that at the time of any external ACL
+# being tested data may not be available and thus some %macro expand to '-'.
+#
+# In addition to the logformat codes; when processing external ACLs these
+# additional macros are made available:
+#
+# %ACL The name of the ACL being tested.
+#
+# %DATA The ACL arguments specified in the referencing config
+# 'acl ... external' line, separated by spaces (an
+# "argument string"). see acl external.
+#
+# If there are no ACL arguments %DATA expands to '-'.
+#
+# If you do not specify a DATA macro inside FORMAT,
+# Squid automatically appends %DATA to your FORMAT.
+# Note that Squid-3.x may expand %DATA to whitespace
+# or nothing in this case.
+#
+# By default, Squid applies URL-encoding to each ACL
+# argument inside the argument string. If an explicit
+# encoding modifier is used (e.g., %#DATA), then Squid
+# encodes the whole argument string as a single token
+# (e.g., with %#DATA, spaces between arguments become
+# %20).
+#
+# If SSL is enabled, the following formating codes become available:
+#
+# %USER_CERT SSL User certificate in PEM format
+# %USER_CERTCHAIN SSL User certificate chain in PEM format
+# %USER_CERT_xx SSL User certificate subject attribute xx
+# %USER_CA_CERT_xx SSL User certificate issuer attribute xx
+#
+#
+# NOTE: all other format codes accepted by older Squid versions
+# are deprecated.
+#
+#
+# General request syntax:
+#
+# [channel-ID] FORMAT-values
+#
+#
+# FORMAT-values consists of transaction details expanded with
+# whitespace separation per the config file FORMAT specification
+# using the FORMAT macros listed above.
+#
+# Request values sent to the helper are URL escaped to protect
+# each value in requests against whitespaces.
+#
+# If using protocol=2.5 then the request sent to the helper is not
+# URL escaped to protect against whitespace.
+#
+# NOTE: protocol=3.0 is deprecated as no longer necessary.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+#
+# The helper receives lines expanded per the above format specification
+# and for each input line returns 1 line starting with OK/ERR/BH result
+# code and optionally followed by additional keywords with more details.
+#
+#
+# General result syntax:
+#
+# [channel-ID] result keyword=value ...
+#
+# Result consists of one of the codes:
+#
+# OK
+# the ACL test produced a match.
+#
+# ERR
+# the ACL test does not produce a match.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified.
+#
+# The meaning of 'a match' is determined by your squid.conf
+# access control configuration. See the Squid wiki for details.
+#
+# Defined keywords:
+#
+# user= The users name (login)
+#
+# password= The users password (for login= cache_peer option)
+#
+# message= Message describing the reason for this response.
+# Available as %o in error pages.
+# Useful on (ERR and BH results).
+#
+# tag= Apply a tag to a request. Only sets a tag once,
+# does not alter existing tags.
+#
+# log= String to be logged in access.log. Available as
+# %ea in logformat specifications.
+#
+# clt_conn_tag= Associates a TAG with the client TCP connection.
+# Please see url_rewrite_program related documentation
+# for this kv-pair.
+#
+# Any keywords may be sent on any response whether OK, ERR or BH.
+#
+# All response keyword values need to be a single token with URL
+# escaping, or enclosed in double quotes (") and escaped using \ on
+# any double quotes or \ characters within the value. The wrapping
+# double quotes are removed before the value is interpreted by Squid.
+# \r and \n are also replace by CR and LF.
+#
+# Some example key values:
+#
+# user=John%20Smith
+# user="John Smith"
+# user="J. \"Bob\" Smith"
+#Default:
+# none
+
+# TAG: acl
+# Defining an Access List
+#
+# Every access list definition must begin with an aclname and acltype,
+# followed by either type-specific arguments or a quoted filename that
+# they are read from.
+#
+# acl aclname acltype argument ...
+# acl aclname acltype "file" ...
+#
+# When using "file", the file should contain one item per line.
+#
+#
+# ACL Options
+#
+# Some acl types supports options which changes their default behaviour:
+#
+# -i,+i By default, regular expressions are CASE-SENSITIVE. To make them
+# case-insensitive, use the -i option. To return case-sensitive
+# use the +i option between patterns, or make a new ACL line
+# without -i.
+#
+# -n Disable lookups and address type conversions. If lookup or
+# conversion is required because the parameter type (IP or
+# domain name) does not match the message address type (domain
+# name or IP), then the ACL would immediately declare a mismatch
+# without any warnings or lookups.
+#
+# -m[=delimiters]
+# Perform a list membership test, interpreting values as
+# comma-separated token lists and matching against individual
+# tokens instead of whole values.
+# The optional "delimiters" parameter specifies one or more
+# alternative non-alphanumeric delimiter characters.
+# non-alphanumeric delimiter characters.
+#
+# -- Used to stop processing all options, in the case the first acl
+# value has '-' character as first character (for example the '-'
+# is a valid domain name)
+#
+# Some acl types require suspending the current request in order
+# to access some external data source.
+# Those which do are marked with the tag [slow], those which
+# don't are marked as [fast].
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl
+# for further information
+#
+# ***** ACL TYPES AVAILABLE *****
+#
+# acl aclname src ip-address/mask ... # clients IP address [fast]
+# acl aclname src addr1-addr2/mask ... # range of addresses [fast]
+# acl aclname dst [-n] ip-address/mask ... # URL host's IP address [slow]
+# acl aclname localip ip-address/mask ... # IP address the client connected to [fast]
+#
+#if USE_SQUID_EUI
+# acl aclname arp mac-address ...
+# acl aclname eui64 eui64-address ...
+# # [fast]
+# # MAC (EUI-48) and EUI-64 addresses use xx:xx:xx:xx:xx:xx notation.
+# #
+# # The 'arp' ACL code is not portable to all operating systems.
+# # It works on Linux, Solaris, Windows, FreeBSD, and some other
+# # BSD variants.
+# #
+# # The eui_lookup directive is required to be 'on' (the default)
+# # and Squid built with --enable-eui for MAC/EUI addresses to be
+# # available for this ACL.
+# #
+# # Squid can only determine the MAC/EUI address for IPv4
+# # clients that are on the same subnet. If the client is on a
+# # different subnet, then Squid cannot find out its address.
+# #
+# # IPv6 protocol does not contain ARP. MAC/EUI is either
+# # encoded directly in the IPv6 address or not available.
+#endif
+# acl aclname clientside_mark mark[/mask] ...
+# # matches CONNMARK of an accepted connection [fast]
+# #
+# # mark and mask are unsigned integers (hex, octal, or decimal).
+# # If multiple marks are given, then the ACL matches if at least
+# # one mark matches.
+# #
+# # Uses netfilter-conntrack library.
+# # Requires building Squid with --enable-linux-netfilter.
+# #
+# # The client, various intermediaries, and Squid itself may set
+# # CONNMARK at various times. The last CONNMARK set wins. This ACL
+# # checks the mark present on an accepted connection or set by
+# # Squid afterwards, depending on the ACL check timing. This ACL
+# # effectively ignores any mark set by other agents after Squid has
+# # accepted the connection.
+#
+# acl aclname srcdomain .foo.com ...
+# # reverse lookup, from client IP [slow]
+# acl aclname dstdomain [-n] .foo.com ...
+# # Destination server from URL [fast]
+# acl aclname srcdom_regex [-i] \.foo\.com ...
+# # regex matching client name [slow]
+# acl aclname dstdom_regex [-n] [-i] \.foo\.com ...
+# # regex matching server [fast]
+# #
+# # For dstdomain and dstdom_regex a reverse lookup is tried if a IP
+# # based URL is used and no match is found. The name "none" is used
+# # if the reverse lookup fails.
+#
+# acl aclname src_as number ...
+# acl aclname dst_as number ...
+# # [fast]
+# # Except for access control, AS numbers can be used for
+# # routing of requests to specific caches. Here's an
+# # example for routing all requests for AS#1241 and only
+# # those to mycache.mydomain.net:
+# # acl asexample dst_as 1241
+# # cache_peer_access mycache.mydomain.net allow asexample
+# # cache_peer_access mycache_mydomain.net deny all
+#
+# acl aclname peername myPeer ...
+# acl aclname peername_regex [-i] regex-pattern ...
+# # [fast]
+# # match against a named cache_peer entry
+# # set unique name= on cache_peer lines for reliable use.
+#
+# acl aclname time [day-abbrevs] [h1:m1-h2:m2]
+# # [fast]
+# # day-abbrevs:
+# # S - Sunday
+# # M - Monday
+# # T - Tuesday
+# # W - Wednesday
+# # H - Thursday
+# # F - Friday
+# # A - Saturday
+# # h1:m1 must be less than h2:m2
+#
+# acl aclname url_regex [-i] ^http:// ...
+# # regex matching on whole URL [fast]
+# acl aclname urllogin [-i] [^a-zA-Z0-9] ...
+# # regex matching on URL login field
+# acl aclname urlpath_regex [-i] \.gif$ ...
+# # regex matching on URL path [fast]
+#
+# acl aclname port 80 70 21 0-1024... # destination TCP port [fast]
+# # ranges are alloed
+# acl aclname localport 3128 ... # TCP port the client connected to [fast]
+# # NP: for interception mode this is usually '80'
+#
+# acl aclname myportname 3128 ... # *_port name [fast]
+#
+# acl aclname proto HTTP FTP ... # request protocol [fast]
+#
+# acl aclname method GET POST ... # HTTP request method [fast]
+#
+# acl aclname http_status 200 301 500- 400-403 ...
+# # status code in reply [fast]
+#
+# acl aclname browser [-i] regexp ...
+# # pattern match on User-Agent header (see also req_header below) [fast]
+#
+# acl aclname referer_regex [-i] regexp ...
+# # pattern match on Referer header [fast]
+# # Referer is highly unreliable, so use with care
+#
+# acl aclname ident [-i] username ...
+# acl aclname ident_regex [-i] pattern ...
+# # string match on ident output [slow]
+# # use REQUIRED to accept any non-null ident.
+#
+# acl aclname proxy_auth [-i] username ...
+# acl aclname proxy_auth_regex [-i] pattern ...
+# # perform http authentication challenge to the client and match against
+# # supplied credentials [slow]
+# #
+# # takes a list of allowed usernames.
+# # use REQUIRED to accept any valid username.
+# #
+# # Will use proxy authentication in forward-proxy scenarios, and plain
+# # http authenticaiton in reverse-proxy scenarios
+# #
+# # NOTE: when a Proxy-Authentication header is sent but it is not
+# # needed during ACL checking the username is NOT logged
+# # in access.log.
+# #
+# # NOTE: proxy_auth requires a EXTERNAL authentication program
+# # to check username/password combinations (see
+# # auth_param directive).
+# #
+# # NOTE: proxy_auth can't be used in a transparent/intercepting proxy
+# # as the browser needs to be configured for using a proxy in order
+# # to respond to proxy authentication.
+#
+# acl aclname snmp_community string ...
+# # A community string to limit access to your SNMP Agent [fast]
+# # Example:
+# #
+# # acl snmppublic snmp_community public
+#
+# acl aclname maxconn number
+# # This will be matched when the client's IP address has
+# # more than <number> TCP connections established. [fast]
+# # NOTE: This only measures direct TCP links so X-Forwarded-For
+# # indirect clients are not counted.
+#
+# acl aclname max_user_ip [-s] number
+# # This will be matched when the user attempts to log in from more
+# # than <number> different ip addresses. The authenticate_ip_ttl
+# # parameter controls the timeout on the ip entries. [fast]
+# # If -s is specified the limit is strict, denying browsing
+# # from any further IP addresses until the ttl has expired. Without
+# # -s Squid will just annoy the user by "randomly" denying requests.
+# # (the counter is reset each time the limit is reached and a
+# # request is denied)
+# # NOTE: in acceleration mode or where there is mesh of child proxies,
+# # clients may appear to come from multiple addresses if they are
+# # going through proxy farms, so a limit of 1 may cause user problems.
+#
+# acl aclname random probability
+# # Pseudo-randomly match requests. Based on the probability given.
+# # Probability may be written as a decimal (0.333), fraction (1/3)
+# # or ratio of matches:non-matches (3:5).
+#
+# acl aclname req_mime_type [-i] mime-type ...
+# # regex match against the mime type of the request generated
+# # by the client. Can be used to detect file upload or some
+# # types HTTP tunneling requests [fast]
+# # NOTE: This does NOT match the reply. You cannot use this
+# # to match the returned file type.
+#
+# acl aclname req_header header-name [-i] any\.regex\.here
+# # regex match against any of the known request headers. May be
+# # thought of as a superset of "browser", "referer" and "mime-type"
+# # ACL [fast]
+#
+# acl aclname rep_mime_type [-i] mime-type ...
+# # regex match against the mime type of the reply received by
+# # squid. Can be used to detect file download or some
+# # types HTTP tunneling requests. [fast]
+# # NOTE: This has no effect in http_access rules. It only has
+# # effect in rules that affect the reply data stream such as
+# # http_reply_access.
+#
+# acl aclname rep_header header-name [-i] any\.regex\.here
+# # regex match against any of the known reply headers. May be
+# # thought of as a superset of "browser", "referer" and "mime-type"
+# # ACLs [fast]
+#
+# acl aclname external class_name [arguments...]
+# # external ACL lookup via a helper class defined by the
+# # external_acl_type directive [slow]
+#
+# acl aclname user_cert attribute values...
+# # match against attributes in a user SSL certificate
+# # attribute is one of DN/C/O/CN/L/ST or a numerical OID [fast]
+#
+# acl aclname ca_cert attribute values...
+# # match against attributes a users issuing CA SSL certificate
+# # attribute is one of DN/C/O/CN/L/ST or a numerical OID [fast]
+#
+# acl aclname ext_user [-i] username ...
+# acl aclname ext_user_regex [-i] pattern ...
+# # string match on username returned by external acl helper [slow]
+# # use REQUIRED to accept any non-null user name.
+#
+# acl aclname tag tagvalue ...
+# # string match on tag returned by external acl helper [fast]
+# # DEPRECATED. Only the first tag will match with this ACL.
+# # Use the 'note' ACL instead for handling multiple tag values.
+#
+# acl aclname hier_code codename ...
+# # string match against squid hierarchy code(s); [fast]
+# # e.g., DIRECT, PARENT_HIT, NONE, etc.
+# #
+# # NOTE: This has no effect in http_access rules. It only has
+# # effect in rules that affect the reply data stream such as
+# # http_reply_access.
+#
+# acl aclname note [-m[=delimiters]] name [value ...]
+# # match transaction annotation [fast]
+# # Without values, matches any annotation with a given name.
+# # With value(s), matches any annotation with a given name that
+# # also has one of the given values.
+# # If the -m flag is used, then the value of the named
+# # annotation is interpreted as a list of tokens, and the ACL
+# # matches individual name=token pairs rather than whole
+# # name=value pairs. See "ACL Options" above for more info.
+# # Annotation sources include note and adaptation_meta directives
+# # as well as helper and eCAP responses.
+#
+# acl aclname adaptation_service service ...
+# # Matches the name of any icap_service, ecap_service,
+# # adaptation_service_set, or adaptation_service_chain that Squid
+# # has used (or attempted to use) for the master transaction.
+# # This ACL must be defined after the corresponding adaptation
+# # service is named in squid.conf. This ACL is usable with
+# # adaptation_meta because it starts matching immediately after
+# # the service has been selected for adaptation.
+#
+# acl aclname transaction_initiator initiator ...
+# # Matches transaction's initiator [fast]
+# #
+# # Supported initiators are:
+# # esi: matches transactions fetching ESI resources
+# # certificate-fetching: matches transactions fetching
+# # a missing intermediate TLS certificate
+# # cache-digest: matches transactions fetching Cache Digests
+# # from a cache_peer
+# # htcp: matches HTCP requests from peers
+# # icp: matches ICP requests to peers
+# # icmp: matches ICMP RTT database (NetDB) requests to peers
+# # asn: matches asns db requests
+# # internal: matches any of the above
+# # client: matches transactions containing an HTTP or FTP
+# # client request received at a Squid *_port
+# # all: matches any transaction, including internal transactions
+# # without a configurable initiator and hopefully rare
+# # transactions without a known-to-Squid initiator
+# #
+# # Multiple initiators are ORed.
+#
+# acl aclname has component
+# # matches a transaction "component" [fast]
+# #
+# # Supported transaction components are:
+# # request: transaction has a request header (at least)
+# # response: transaction has a response header (at least)
+# # ALE: transaction has an internally-generated Access Log Entry
+# # structure; bugs notwithstanding, all transaction have it
+# #
+# # For example, the following configuration helps when dealing with HTTP
+# # clients that close connections without sending a request header:
+# #
+# # acl hasRequest has request
+# # acl logMe note important_transaction
+# # # avoid "logMe ACL is used in context without an HTTP request" warnings
+# # access_log ... logformat=detailed hasRequest logMe
+# # # log request-less transactions, instead of ignoring them
+# # access_log ... logformat=brief !hasRequest
+# #
+# # Multiple components are not supported for one "acl" rule, but
+# # can be specified (and are ORed) using multiple same-name rules:
+# #
+# # # OK, this strange logging daemon needs request or response,
+# # # but can work without either a request or a response:
+# # acl hasWhatMyLoggingDaemonNeeds has request
+# # acl hasWhatMyLoggingDaemonNeeds has response
+#
+# acl aclname any-of acl1 acl2 ...
+# # match any one of the acls [fast or slow]
+# # The first matching ACL stops further ACL evaluation.
+# #
+# # ACLs from multiple any-of lines with the same name are ORed.
+# # For example, A = (a1 or a2) or (a3 or a4) can be written as
+# # acl A any-of a1 a2
+# # acl A any-of a3 a4
+# #
+# # This group ACL is fast if all evaluated ACLs in the group are fast
+# # and slow otherwise.
+#
+# acl aclname all-of acl1 acl2 ...
+# # match all of the acls [fast or slow]
+# # The first mismatching ACL stops further ACL evaluation.
+# #
+# # ACLs from multiple all-of lines with the same name are ORed.
+# # For example, B = (b1 and b2) or (b3 and b4) can be written as
+# # acl B all-of b1 b2
+# # acl B all-of b3 b4
+# #
+# # This group ACL is fast if all evaluated ACLs in the group are fast
+# # and slow otherwise.
+#
+# Examples:
+# acl macaddress arp 09:00:2b:23:45:67
+# acl myexample dst_as 1241
+# acl password proxy_auth REQUIRED
+# acl fileupload req_mime_type -i ^multipart/form-data$
+# acl javascript rep_mime_type -i ^application/x-javascript$
+#
+#Default:
+# ACLs all, manager, localhost, and to_localhost are predefined.
+#
+#
+# Recommended minimum configuration:
+#
+
+# Example rule allowing access from your local networks.
+# Adapt to list your (internal) IP networks from where browsing
+# should be allowed
+#acl localnet src 0.0.0.1-0.255.255.255 # RFC 1122 "this" network (LAN)
+#acl localnet src 10.0.0.0/8 # RFC 1918 local private network (LAN)
+#acl localnet src 100.64.0.0/10 # RFC 6598 shared address space (CGN)
+#acl localnet src 169.254.0.0/16 # RFC 3927 link-local (directly plugged) machines
+acl localnet src 172.16.64.0/12 # RFC 1918 local private network (LAN)
+#acl localnet src 192.168.0.0/16 # RFC 1918 local private network (LAN)
+#acl localnet src fc00::/7 # RFC 4193 local private network range
+#acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
+
+acl SSL_ports port 443
+acl Safe_ports port 80 # http
+acl Safe_ports port 21 # ftp
+acl Safe_ports port 443 # https
+acl Safe_ports port 70 # gopher
+acl Safe_ports port 210 # wais
+acl Safe_ports port 1025-65535 # unregistered ports
+acl Safe_ports port 280 # http-mgmt
+acl Safe_ports port 488 # gss-http
+acl Safe_ports port 591 # filemaker
+acl Safe_ports port 777 # multiling http
+acl CONNECT method CONNECT
+
+# TAG: proxy_protocol_access
+# Determine which client proxies can be trusted to provide correct
+# information regarding real client IP address using PROXY protocol.
+#
+# Requests may pass through a chain of several other proxies
+# before reaching us. The original source details may by sent in:
+# * HTTP message Forwarded header, or
+# * HTTP message X-Forwarded-For header, or
+# * PROXY protocol connection header.
+#
+# This directive is solely for validating new PROXY protocol
+# connections received from a port flagged with require-proxy-header.
+# It is checked only once after TCP connection setup.
+#
+# A deny match results in TCP connection closure.
+#
+# An allow match is required for Squid to permit the corresponding
+# TCP connection, before Squid even looks for HTTP request headers.
+# If there is an allow match, Squid starts using PROXY header information
+# to determine the source address of the connection for all future ACL
+# checks, logging, etc.
+#
+# SECURITY CONSIDERATIONS:
+#
+# Any host from which we accept client IP details can place
+# incorrect information in the relevant header, and Squid
+# will use the incorrect information as if it were the
+# source address of the request. This may enable remote
+# hosts to bypass any access control restrictions that are
+# based on the client's source addresses.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# all TCP connections to ports with require-proxy-header will be denied
+
+# TAG: follow_x_forwarded_for
+# Determine which client proxies can be trusted to provide correct
+# information regarding real client IP address.
+#
+# Requests may pass through a chain of several other proxies
+# before reaching us. The original source details may by sent in:
+# * HTTP message Forwarded header, or
+# * HTTP message X-Forwarded-For header, or
+# * PROXY protocol connection header.
+#
+# PROXY protocol connections are controlled by the proxy_protocol_access
+# directive which is checked before this.
+#
+# If a request reaches us from a source that is allowed by this
+# directive, then we trust the information it provides regarding
+# the IP of the client it received from (if any).
+#
+# For the purpose of ACLs used in this directive the src ACL type always
+# matches the address we are testing and srcdomain matches its rDNS.
+#
+# On each HTTP request Squid checks for X-Forwarded-For header fields.
+# If found the header values are iterated in reverse order and an allow
+# match is required for Squid to continue on to the next value.
+# The verification ends when a value receives a deny match, cannot be
+# tested, or there are no more values to test.
+# NOTE: Squid does not yet follow the Forwarded HTTP header.
+#
+# The end result of this process is an IP address that we will
+# refer to as the indirect client address. This address may
+# be treated as the client address for access control, ICAP, delay
+# pools and logging, depending on the acl_uses_indirect_client,
+# icap_uses_indirect_client, delay_pool_uses_indirect_client,
+# log_uses_indirect_client and tproxy_uses_indirect_client options.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# SECURITY CONSIDERATIONS:
+#
+# Any host from which we accept client IP details can place
+# incorrect information in the relevant header, and Squid
+# will use the incorrect information as if it were the
+# source address of the request. This may enable remote
+# hosts to bypass any access control restrictions that are
+# based on the client's source addresses.
+#
+# For example:
+#
+# acl localhost src 127.0.0.1
+# acl my_other_proxy srcdomain .proxy.example.com
+# follow_x_forwarded_for allow localhost
+# follow_x_forwarded_for allow my_other_proxy
+#Default:
+# X-Forwarded-For header will be ignored.
+
+# TAG: acl_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in acl matching.
+#
+# NOTE: maxconn ACL considers direct TCP links and indirect
+# clients will always have zero. So no match.
+#Default:
+# acl_uses_indirect_client on
+
+# TAG: delay_pool_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in delay pools.
+#Default:
+# delay_pool_uses_indirect_client on
+
+# TAG: log_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in the access log.
+#Default:
+# log_uses_indirect_client on
+
+# TAG: tproxy_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address when spoofing the outgoing client.
+#
+# This has no effect on requests arriving in non-tproxy
+# mode ports.
+#
+# SECURITY WARNING: Usage of this option is dangerous
+# and should not be used trivially. Correct configuration
+# of follow_x_forwarded_for with a limited set of trusted
+# sources is required to prevent abuse of your proxy.
+#Default:
+# tproxy_uses_indirect_client off
+
+# TAG: spoof_client_ip
+# Control client IP address spoofing of TPROXY traffic based on
+# defined access lists.
+#
+# spoof_client_ip allow|deny [!]aclname ...
+#
+# If there are no "spoof_client_ip" lines present, the default
+# is to "allow" spoofing of any suitable request.
+#
+# Note that the cache_peer "no-tproxy" option overrides this ACL.
+#
+# This clause supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow spoofing on all TPROXY traffic.
+
+# TAG: http_access
+# Allowing or Denying access based on defined access lists
+#
+# To allow or deny a message received on an HTTP, HTTPS, or FTP port:
+# http_access allow|deny [!]aclname ...
+#
+# NOTE on default values:
+#
+# If there are no "access" lines present, the default is to deny
+# the request.
+#
+# If none of the "access" lines cause a match, the default is the
+# opposite of the last line in the list. If the last line was
+# deny, the default is allow. Conversely, if the last line
+# is allow, the default will be deny. For these reasons, it is a
+# good idea to have an "deny all" entry at the end of your access
+# lists to avoid potential confusion.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Default:
+# Deny, unless rules exist in squid.conf.
+#
+
+#
+# Recommended minimum Access Permission configuration:
+#
+# Deny requests to certain unsafe ports
+http_access deny !Safe_ports
+
+# Deny CONNECT to other than secure SSL ports
+http_access deny CONNECT !SSL_ports
+
+# Only allow cachemgr access from localhost
+http_access allow localnet
+http_access deny all
+
+# We strongly recommend the following be uncommented to protect innocent
+# web applications running on the proxy server who think the only
+# one who can access services on "localhost" is a local user
+#http_access deny to_localhost
+
+#
+# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
+#
+include /etc/squid/conf.d/*
+
+# Example rule allowing access from your local networks.
+# Adapt localnet in the ACL section to list your (internal) IP networks
+# from where browsing should be allowed
+#http_access allow localnet
+http_access allow localhost
+
+# And finally deny all other access to this proxy
+http_access deny all
+
+# TAG: adapted_http_access
+# Allowing or Denying access based on defined access lists
+#
+# Essentially identical to http_access, but runs after redirectors
+# and ICAP/eCAP adaptation. Allowing access control based on their
+# output.
+#
+# If not set then only http_access is used.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: http_reply_access
+# Allow replies to client requests. This is complementary to http_access.
+#
+# http_reply_access allow|deny [!] aclname ...
+#
+# NOTE: if there are no access lines present, the default is to allow
+# all replies.
+#
+# If none of the access lines cause a match the opposite of the
+# last line will apply. Thus it is good practice to end the rules
+# with an "allow all" or "deny all" entry.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: icp_access
+# Allowing or Denying access to the ICP port based on defined
+# access lists
+#
+# icp_access allow|deny [!]aclname ...
+#
+# NOTE: The default if no icp_access lines are present is to
+# deny all traffic. This default may cause problems with peers
+# using ICP.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow ICP queries from local networks only
+##icp_access allow localnet
+##icp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: htcp_access
+# Allowing or Denying access to the HTCP port based on defined
+# access lists
+#
+# htcp_access allow|deny [!]aclname ...
+#
+# See also htcp_clr_access for details on access control for
+# cache purge (CLR) HTCP messages.
+#
+# NOTE: The default if no htcp_access lines are present is to
+# deny all traffic. This default may cause problems with peers
+# using the htcp option.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow HTCP queries from local networks only
+##htcp_access allow localnet
+##htcp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: htcp_clr_access
+# Allowing or Denying access to purge content using HTCP based
+# on defined access lists.
+# See htcp_access for details on general HTCP access control.
+#
+# htcp_clr_access allow|deny [!]aclname ...
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow HTCP CLR requests from trusted peers
+#acl htcp_clr_peer src 192.0.2.2 2001:DB8::2
+#htcp_clr_access allow htcp_clr_peer
+#htcp_clr_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: miss_access
+# Determines whether network access is permitted when satisfying a request.
+#
+# For example;
+# to force your neighbors to use you as a sibling instead of
+# a parent.
+#
+# acl localclients src 192.0.2.0/24 2001:DB8::a:0/64
+# miss_access deny !localclients
+# miss_access allow all
+#
+# This means only your local clients are allowed to fetch relayed/MISS
+# replies from the network and all other clients can only fetch cached
+# objects (HITs).
+#
+# The default for this setting allows all clients who passed the
+# http_access rules to relay via this proxy.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: ident_lookup_access
+# A list of ACL elements which, if matched, cause an ident
+# (RFC 931) lookup to be performed for this request. For
+# example, you might choose to always perform ident lookups
+# for your main multi-user Unix boxes, but not for your Macs
+# and PCs. By default, ident lookups are not performed for
+# any requests.
+#
+# To enable ident lookups for specific client addresses, you
+# can follow this example:
+#
+# acl ident_aware_hosts src 198.168.1.0/24
+# ident_lookup_access allow ident_aware_hosts
+# ident_lookup_access deny all
+#
+# Only src type ACL checks are fully supported. A srcdomain
+# ACL might work at times, but it will not always provide
+# the correct result.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Unless rules exist in squid.conf, IDENT is not fetched.
+
+# TAG: reply_body_max_size size [acl acl...]
+# This option specifies the maximum size of a reply body. It can be
+# used to prevent users from downloading very large files, such as
+# MP3's and movies. When the reply headers are received, the
+# reply_body_max_size lines are processed, and the first line where
+# all (if any) listed ACLs are true is used as the maximum body size
+# for this reply.
+#
+# This size is checked twice. First when we get the reply headers,
+# we check the content-length value. If the content length value exists
+# and is larger than the allowed size, the request is denied and the
+# user receives an error message that says "the request or reply
+# is too large." If there is no content-length, and the reply
+# size exceeds this limit, the client's connection is just closed
+# and they will receive a partial reply.
+#
+# WARNING: downstream caches probably can not detect a partial reply
+# if there is no content-length header, so they will cache
+# partial responses and give them out as hits. You should NOT
+# use this option if you have downstream caches.
+#
+# WARNING: A maximum size smaller than the size of squid's error messages
+# will cause an infinite loop and crash squid. Ensure that the smallest
+# non-zero value you use is greater that the maximum header size plus
+# the size of your largest error page.
+#
+# If you set this parameter none (the default), there will be
+# no limit imposed.
+#
+# Configuration Format is:
+# reply_body_max_size SIZE UNITS [acl ...]
+# ie.
+# reply_body_max_size 10 MB
+#
+#Default:
+# No limit is applied.
+
+# TAG: on_unsupported_protocol
+# Determines Squid behavior when encountering strange requests at the
+# beginning of an accepted TCP connection or the beginning of a bumped
+# CONNECT tunnel. Controlling Squid reaction to unexpected traffic is
+# especially useful in interception environments where Squid is likely
+# to see connections for unsupported protocols that Squid should either
+# terminate or tunnel at TCP level.
+#
+# on_unsupported_protocol <action> [!]acl ...
+#
+# The first matching action wins. Only fast ACLs are supported.
+#
+# Supported actions are:
+#
+# tunnel: Establish a TCP connection with the intended server and
+# blindly shovel TCP packets between the client and server.
+#
+# respond: Respond with an error message, using the transfer protocol
+# for the Squid port that received the request (e.g., HTTP
+# for connections intercepted at the http_port). This is the
+# default.
+#
+# Squid expects the following traffic patterns:
+#
+# http_port: a plain HTTP request
+# https_port: SSL/TLS handshake followed by an [encrypted] HTTP request
+# ftp_port: a plain FTP command (no on_unsupported_protocol support yet!)
+# CONNECT tunnel on http_port: same as https_port
+# CONNECT tunnel on https_port: same as https_port
+#
+# Currently, this directive has effect on intercepted connections and
+# bumped tunnels only. Other cases are not supported because Squid
+# cannot know the intended destination of other traffic.
+#
+# For example:
+# # define what Squid errors indicate receiving non-HTTP traffic:
+# acl foreignProtocol squid_error ERR_PROTOCOL_UNKNOWN ERR_TOO_BIG
+# # define what Squid errors indicate receiving nothing:
+# acl serverTalksFirstProtocol squid_error ERR_REQUEST_START_TIMEOUT
+# # tunnel everything that does not look like HTTP:
+# on_unsupported_protocol tunnel foreignProtocol
+# # tunnel if we think the client waits for the server to talk first:
+# on_unsupported_protocol tunnel serverTalksFirstProtocol
+# # in all other error cases, just send an HTTP "error page" response:
+# on_unsupported_protocol respond all
+#
+# See also: squid_error ACL
+#Default:
+# Respond with an error message to unidentifiable traffic
+
+# NETWORK OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: http_port
+# Usage: port [mode] [options]
+# hostname:port [mode] [options]
+# 1.2.3.4:port [mode] [options]
+#
+# The socket addresses where Squid will listen for HTTP client
+# requests. You may specify multiple socket addresses.
+# There are three forms: port alone, hostname with port, and
+# IP address with port. If you specify a hostname or IP
+# address, Squid binds the socket to that specific
+# address. Most likely, you do not need to bind to a specific
+# address, so you can use the port number alone.
+#
+# If you are running Squid in accelerator mode, you
+# probably want to listen on port 80 also, or instead.
+#
+# The -a command line option may be used to specify additional
+# port(s) where Squid listens for proxy request. Such ports will
+# be plain proxy ports with no options.
+#
+# You may specify multiple socket addresses on multiple lines.
+#
+# Modes:
+#
+# intercept Support for IP-Layer NAT interception delivering
+# traffic to this Squid port.
+# NP: disables authentication on the port.
+#
+# tproxy Support Linux TPROXY (or BSD divert-to) with spoofing
+# of outgoing connections using the client IP address.
+# NP: disables authentication on the port.
+#
+# accel Accelerator / reverse proxy mode
+#
+# ssl-bump For each CONNECT request allowed by ssl_bump ACLs,
+# establish secure connection with the client and with
+# the server, decrypt HTTPS messages as they pass through
+# Squid, and treat them as unencrypted HTTP messages,
+# becoming the man-in-the-middle.
+#
+# The ssl_bump option is required to fully enable
+# bumping of CONNECT requests.
+#
+# Omitting the mode flag causes default forward proxy mode to be used.
+#
+#
+# Accelerator Mode Options:
+#
+# defaultsite=domainname
+# What to use for the Host: header if it is not present
+# in a request. Determines what site (not origin server)
+# accelerators should consider the default.
+#
+# no-vhost Disable using HTTP/1.1 Host header for virtual domain support.
+#
+# protocol= Protocol to reconstruct accelerated and intercepted
+# requests with. Defaults to HTTP/1.1 for http_port and
+# HTTPS/1.1 for https_port.
+# When an unsupported value is configured Squid will
+# produce a FATAL error.
+# Values: HTTP or HTTP/1.1, HTTPS or HTTPS/1.1
+#
+# vport Virtual host port support. Using the http_port number
+# instead of the port passed on Host: headers.
+#
+# vport=NN Virtual host port support. Using the specified port
+# number instead of the port passed on Host: headers.
+#
+# act-as-origin
+# Act as if this Squid is the origin server.
+# This currently means generate new Date: and Expires:
+# headers on HIT instead of adding Age:.
+#
+# ignore-cc Ignore request Cache-Control headers.
+#
+# WARNING: This option violates HTTP specifications if
+# used in non-accelerator setups.
+#
+# allow-direct Allow direct forwarding in accelerator mode. Normally
+# accelerated requests are denied direct forwarding as if
+# never_direct was used.
+#
+# WARNING: this option opens accelerator mode to security
+# vulnerabilities usually only affecting in interception
+# mode. Make sure to protect forwarding with suitable
+# http_access rules when using this.
+#
+#
+# SSL Bump Mode Options:
+# In addition to these options ssl-bump requires TLS/SSL options.
+#
+# generate-host-certificates[=<on|off>]
+# Dynamically create SSL server certificates for the
+# destination hosts of bumped CONNECT requests.When
+# enabled, the cert and key options are used to sign
+# generated certificates. Otherwise generated
+# certificate will be selfsigned.
+# If there is a CA certificate lifetime of the generated
+# certificate equals lifetime of the CA certificate. If
+# generated certificate is selfsigned lifetime is three
+# years.
+# This option is enabled by default when ssl-bump is used.
+# See the ssl-bump option above for more information.
+#
+# dynamic_cert_mem_cache_size=SIZE
+# Approximate total RAM size spent on cached generated
+# certificates. If set to zero, caching is disabled. The
+# default value is 4MB.
+#
+# TLS / SSL Options:
+#
+# tls-cert= Path to file containing an X.509 certificate (PEM format)
+# to be used in the TLS handshake ServerHello.
+#
+# If this certificate is constrained by KeyUsage TLS
+# feature it must allow HTTP server usage, along with
+# any additional restrictions imposed by your choice
+# of options= settings.
+#
+# When OpenSSL is used this file may also contain a
+# chain of intermediate CA certificates to send in the
+# TLS handshake.
+#
+# When GnuTLS is used this option (and any paired
+# tls-key= option) may be repeated to load multiple
+# certificates for different domains.
+#
+# Also, when generate-host-certificates=on is configured
+# the first tls-cert= option must be a CA certificate
+# capable of signing the automatically generated
+# certificates.
+#
+# tls-key= Path to a file containing private key file (PEM format)
+# for the previous tls-cert= option.
+#
+# If tls-key= is not specified tls-cert= is assumed to
+# reference a PEM file containing both the certificate
+# and private key.
+#
+# cipher= Colon separated list of supported ciphers.
+# NOTE: some ciphers such as EDH ciphers depend on
+# additional settings. If those settings are
+# omitted the ciphers may be silently ignored
+# by the OpenSSL library.
+#
+# options= Various SSL implementation options. The most important
+# being:
+#
+# NO_SSLv3 Disallow the use of SSLv3
+#
+# NO_TLSv1 Disallow the use of TLSv1.0
+#
+# NO_TLSv1_1 Disallow the use of TLSv1.1
+#
+# NO_TLSv1_2 Disallow the use of TLSv1.2
+#
+# SINGLE_DH_USE
+# Always create a new key when using
+# temporary/ephemeral DH key exchanges
+#
+# SINGLE_ECDH_USE
+# Enable ephemeral ECDH key exchange.
+# The adopted curve should be specified
+# using the tls-dh option.
+#
+# NO_TICKET
+# Disable use of RFC5077 session tickets.
+# Some servers may have problems
+# understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+#
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation for a
+# more complete list.
+#
+# clientca= File containing the list of CAs to use when
+# requesting a client certificate.
+#
+# tls-cafile= PEM file containing CA certificates to use when verifying
+# client certificates. If not configured clientca will be
+# used. May be repeated to load multiple files.
+#
+# capath= Directory containing additional CA certificates
+# and CRL lists to use when verifying client certificates.
+# Requires OpenSSL or LibreSSL.
+#
+# crlfile= File of additional CRL lists to use when verifying
+# the client certificate, in addition to CRLs stored in
+# the capath. Implies VERIFY_CRL flag below.
+#
+# tls-dh=[curve:]file
+# File containing DH parameters for temporary/ephemeral DH key
+# exchanges, optionally prefixed by a curve for ephemeral ECDH
+# key exchanges.
+# See OpenSSL documentation for details on how to create the
+# DH parameter file. Supported curves for ECDH can be listed
+# using the "openssl ecparam -list_curves" command.
+# WARNING: EDH and EECDH ciphers will be silently disabled if
+# this option is not set.
+#
+# sslflags= Various flags modifying the use of SSL:
+# DELAYED_AUTH
+# Don't request client certificates
+# immediately, but wait until acl processing
+# requires a certificate (not yet implemented).
+# NO_SESSION_REUSE
+# Don't allow for session reuse. Each connection
+# will result in a new SSL session.
+# VERIFY_CRL
+# Verify CRL lists when accepting client
+# certificates.
+# VERIFY_CRL_ALL
+# Verify CRL lists for all certificates in the
+# client certificate chain.
+#
+# tls-default-ca[=off]
+# Whether to use the system Trusted CAs. Default is OFF.
+#
+# tls-no-npn Do not use the TLS NPN extension to advertise HTTP/1.1.
+#
+# sslcontext= SSL session ID context identifier.
+#
+# Other Options:
+#
+# connection-auth[=on|off]
+# use connection-auth=off to tell Squid to prevent
+# forwarding Microsoft connection oriented authentication
+# (NTLM, Negotiate and Kerberos)
+#
+# disable-pmtu-discovery=
+# Control Path-MTU discovery usage:
+# off lets OS decide on what to do (default).
+# transparent disable PMTU discovery when transparent
+# support is enabled.
+# always disable always PMTU discovery.
+#
+# In many setups of transparently intercepting proxies
+# Path-MTU discovery can not work on traffic towards the
+# clients. This is the case when the intercepting device
+# does not fully track connections and fails to forward
+# ICMP must fragment messages to the cache server. If you
+# have such setup and experience that certain clients
+# sporadically hang or never complete requests set
+# disable-pmtu-discovery option to 'transparent'.
+#
+# name= Specifies a internal name for the port. Defaults to
+# the port specification (port or addr:port)
+#
+# tcpkeepalive[=idle,interval,timeout]
+# Enable TCP keepalive probes of idle connections.
+# In seconds; idle is the initial time before TCP starts
+# probing the connection, interval how often to probe, and
+# timeout the time before giving up.
+#
+# require-proxy-header
+# Require PROXY protocol version 1 or 2 connections.
+# The proxy_protocol_access is required to whitelist
+# downstream proxies which can be trusted.
+#
+# If you run Squid on a dual-homed machine with an internal
+# and an external interface we recommend you to specify the
+# internal address:port in http_port. This way Squid will only be
+# visible on the internal address.
+#
+#
+
+# Squid normally listens to port 3128
+http_port 8080
+
+# TAG: https_port
+# Usage: [ip:]port [mode] tls-cert=certificate.pem [options]
+#
+# The socket address where Squid will listen for client requests made
+# over TLS or SSL connections. Commonly referred to as HTTPS.
+#
+# This is most useful for situations where you are running squid in
+# accelerator mode and you want to do the TLS work at the accelerator
+# level.
+#
+# You may specify multiple socket addresses on multiple lines,
+# each with their own certificate and/or options.
+#
+# The tls-cert= option is mandatory on HTTPS ports.
+#
+# See http_port for a list of modes and options.
+#Default:
+# none
+
+# TAG: ftp_port
+# Enables Native FTP proxy by specifying the socket address where Squid
+# listens for FTP client requests. See http_port directive for various
+# ways to specify the listening address and mode.
+#
+# Usage: ftp_port address [mode] [options]
+#
+# WARNING: This is a new, experimental, complex feature that has seen
+# limited production exposure. Some Squid modules (e.g., caching) do not
+# currently work with native FTP proxying, and many features have not
+# even been tested for compatibility. Test well before deploying!
+#
+# Native FTP proxying differs substantially from proxying HTTP requests
+# with ftp:// URIs because Squid works as an FTP server and receives
+# actual FTP commands (rather than HTTP requests with FTP URLs).
+#
+# Native FTP commands accepted at ftp_port are internally converted or
+# wrapped into HTTP-like messages. The same happens to Native FTP
+# responses received from FTP origin servers. Those HTTP-like messages
+# are shoveled through regular access control and adaptation layers
+# between the FTP client and the FTP origin server. This allows Squid to
+# examine, adapt, block, and log FTP exchanges. Squid reuses most HTTP
+# mechanisms when shoveling wrapped FTP messages. For example,
+# http_access and adaptation_access directives are used.
+#
+# Modes:
+#
+# intercept Same as http_port intercept. The FTP origin address is
+# determined based on the intended destination of the
+# intercepted connection.
+#
+# tproxy Support Linux TPROXY for spoofing outgoing
+# connections using the client IP address.
+# NP: disables authentication and maybe IPv6 on the port.
+#
+# By default (i.e., without an explicit mode option), Squid extracts the
+# FTP origin address from the login@origin parameter of the FTP USER
+# command. Many popular FTP clients support such native FTP proxying.
+#
+# Options:
+#
+# name=token Specifies an internal name for the port. Defaults to
+# the port address. Usable with myportname ACL.
+#
+# ftp-track-dirs
+# Enables tracking of FTP directories by injecting extra
+# PWD commands and adjusting Request-URI (in wrapping
+# HTTP requests) to reflect the current FTP server
+# directory. Tracking is disabled by default.
+#
+# protocol=FTP Protocol to reconstruct accelerated and intercepted
+# requests with. Defaults to FTP. No other accepted
+# values have been tested with. An unsupported value
+# results in a FATAL error. Accepted values are FTP,
+# HTTP (or HTTP/1.1), and HTTPS (or HTTPS/1.1).
+#
+# Other http_port modes and options that are not specific to HTTP and
+# HTTPS may also work.
+#Default:
+# none
+
+# TAG: tcp_outgoing_tos
+# Allows you to select a TOS/Diffserv value for packets outgoing
+# on the server side, based on an ACL.
+#
+# tcp_outgoing_tos ds-field [!]aclname ...
+#
+# Example where normal_service_net uses the TOS value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# tcp_outgoing_tos 0x00 normal_service_net
+# tcp_outgoing_tos 0x20 good_service_net
+#
+# TOS/DSCP values really only have local significance - so you should
+# know what you're specifying. For more information, see RFC2474,
+# RFC2475, and RFC3260.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or
+# "default" to use whatever default your host has.
+# Note that only multiples of 4 are usable as the two rightmost bits have
+# been redefined for use by ECN (RFC 3168 section 23.1).
+# The squid parser will enforce this by masking away the ECN bits.
+#
+# Processing proceeds in the order specified, and stops at first fully
+# matching line.
+#
+# Only fast ACLs are supported.
+#Default:
+# none
+
+# TAG: clientside_tos
+# Allows you to select a TOS/DSCP value for packets being transmitted
+# on the client-side, based on an ACL.
+#
+# clientside_tos ds-field [!]aclname ...
+#
+# Example where normal_service_net uses the TOS value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# clientside_tos 0x00 normal_service_net
+# clientside_tos 0x20 good_service_net
+#
+# Note: This feature is incompatible with qos_flows. Any TOS values set here
+# will be overwritten by TOS values in qos_flows.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or
+# "default" to use whatever default your host has.
+# Note that only multiples of 4 are usable as the two rightmost bits have
+# been redefined for use by ECN (RFC 3168 section 23.1).
+# The squid parser will enforce this by masking away the ECN bits.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# none
+
+# TAG: tcp_outgoing_mark
+# Note: This option is only available if Squid is rebuilt with the
+# Packet MARK (Linux)
+#
+# Allows you to apply a Netfilter mark value to outgoing packets
+# on the server side, based on an ACL.
+#
+# tcp_outgoing_mark mark-value [!]aclname ...
+#
+# Example where normal_service_net uses the mark value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# tcp_outgoing_mark 0x00 normal_service_net
+# tcp_outgoing_mark 0x20 good_service_net
+#
+# Only fast ACLs are supported.
+#Default:
+# none
+
+# TAG: clientside_mark
+# Note: This option is only available if Squid is rebuilt with the
+# Packet MARK (Linux)
+#
+# Allows you to apply a Netfilter mark value to packets being transmitted
+# on the client-side, based on an ACL.
+#
+# clientside_mark mark-value [!]aclname ...
+#
+# Example where normal_service_net uses the mark value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# clientside_mark 0x00 normal_service_net
+# clientside_mark 0x20 good_service_net
+#
+# Note: This feature is incompatible with qos_flows. Any mark values set here
+# will be overwritten by mark values in qos_flows.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# none
+
+# TAG: qos_flows
+# Allows you to select a TOS/DSCP value to mark outgoing
+# connections to the client, based on where the reply was sourced.
+# For platforms using netfilter, allows you to set a netfilter mark
+# value instead of, or in addition to, a TOS value.
+#
+# By default this functionality is disabled. To enable it with the default
+# settings simply use "qos_flows mark" or "qos_flows tos". Default
+# settings will result in the netfilter mark or TOS value being copied
+# from the upstream connection to the client. Note that it is the connection
+# CONNMARK value not the packet MARK value that is copied.
+#
+# It is not currently possible to copy the mark or TOS value from the
+# client to the upstream connection request.
+#
+# TOS values really only have local significance - so you should
+# know what you're specifying. For more information, see RFC2474,
+# RFC2475, and RFC3260.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255.
+# Note that only multiples of 4 are usable as the two rightmost bits have
+# been redefined for use by ECN (RFC 3168 section 23.1).
+# The squid parser will enforce this by masking away the ECN bits.
+#
+# Mark values can be any unsigned 32-bit integer value.
+#
+# This setting is configured by setting the following values:
+#
+# tos|mark Whether to set TOS or netfilter mark values
+#
+# local-hit=0xFF Value to mark local cache hits.
+#
+# sibling-hit=0xFF Value to mark hits from sibling peers.
+#
+# parent-hit=0xFF Value to mark hits from parent peers.
+#
+# miss=0xFF[/mask] Value to mark cache misses. Takes precedence
+# over the preserve-miss feature (see below), unless
+# mask is specified, in which case only the bits
+# specified in the mask are written.
+#
+# The TOS variant of the following features are only possible on Linux
+# and require your kernel to be patched with the TOS preserving ZPH
+# patch, available from http://zph.bratcheda.org
+# No patch is needed to preserve the netfilter mark, which will work
+# with all variants of netfilter.
+#
+# disable-preserve-miss
+# This option disables the preservation of the TOS or netfilter
+# mark. By default, the existing TOS or netfilter mark value of
+# the response coming from the remote server will be retained
+# and masked with miss-mark.
+# NOTE: in the case of a netfilter mark, the mark must be set on
+# the connection (using the CONNMARK target) not on the packet
+# (MARK target).
+#
+# miss-mask=0xFF
+# Allows you to mask certain bits in the TOS or mark value
+# received from the remote server, before copying the value to
+# the TOS sent towards clients.
+# Default for tos: 0xFF (TOS from server is not changed).
+# Default for mark: 0xFFFFFFFF (mark from server is not changed).
+#
+# All of these features require the --enable-zph-qos compilation flag
+# (enabled by default). Netfilter marking also requires the
+# libnetfilter_conntrack libraries (--with-netfilter-conntrack) and
+# libcap 2.09+ (--with-libcap).
+#
+#Default:
+# none
+
+# TAG: tcp_outgoing_address
+# Allows you to map requests to different outgoing IP addresses
+# based on the username or source address of the user making
+# the request.
+#
+# tcp_outgoing_address ipaddr [[!]aclname] ...
+#
+# For example;
+# Forwarding clients with dedicated IPs for certain subnets.
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.2.0/24
+#
+# tcp_outgoing_address 2001:db8::c001 good_service_net
+# tcp_outgoing_address 10.1.0.2 good_service_net
+#
+# tcp_outgoing_address 2001:db8::beef normal_service_net
+# tcp_outgoing_address 10.1.0.1 normal_service_net
+#
+# tcp_outgoing_address 2001:db8::1
+# tcp_outgoing_address 10.1.0.3
+#
+# Processing proceeds in the order specified, and stops at first fully
+# matching line.
+#
+# Squid will add an implicit IP version test to each line.
+# Requests going to IPv4 websites will use the outgoing 10.1.0.* addresses.
+# Requests going to IPv6 websites will use the outgoing 2001:db8:* addresses.
+#
+#
+# NOTE: The use of this directive using client dependent ACLs is
+# incompatible with the use of server side persistent connections. To
+# ensure correct results it is best to set server_persistent_connections
+# to off when using this directive in such configurations.
+#
+# NOTE: The use of this directive to set a local IP on outgoing TCP links
+# is incompatible with using TPROXY to set client IP out outbound TCP links.
+# When needing to contact peers use the no-tproxy cache_peer option and the
+# client_dst_passthru directive re-enable normal forwarding such as this.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Address selection is performed by the operating system.
+
+# TAG: host_verify_strict
+# Regardless of this option setting, when dealing with intercepted
+# traffic, Squid always verifies that the destination IP address matches
+# the Host header domain or IP (called 'authority form URL').
+#
+# This enforcement is performed to satisfy a MUST-level requirement in
+# RFC 2616 section 14.23: "The Host field value MUST represent the naming
+# authority of the origin server or gateway given by the original URL".
+#
+# When set to ON:
+# Squid always responds with an HTTP 409 (Conflict) error
+# page and logs a security warning if there is no match.
+#
+# Squid verifies that the destination IP address matches
+# the Host header for forward-proxy and reverse-proxy traffic
+# as well. For those traffic types, Squid also enables the
+# following checks, comparing the corresponding Host header
+# and Request-URI components:
+#
+# * The host names (domain or IP) must be identical,
+# but valueless or missing Host header disables all checks.
+# For the two host names to match, both must be either IP
+# or FQDN.
+#
+# * Port numbers must be identical, but if a port is missing
+# the scheme-default port is assumed.
+#
+#
+# When set to OFF (the default):
+# Squid allows suspicious requests to continue but logs a
+# security warning and blocks caching of the response.
+#
+# * Forward-proxy traffic is not checked at all.
+#
+# * Reverse-proxy traffic is not checked at all.
+#
+# * Intercepted traffic which passes verification is handled
+# according to client_dst_passthru.
+#
+# * Intercepted requests which fail verification are sent
+# to the client original destination instead of DIRECT.
+# This overrides 'client_dst_passthru off'.
+#
+# For now suspicious intercepted CONNECT requests are always
+# responded to with an HTTP 409 (Conflict) error page.
+#
+#
+# SECURITY NOTE:
+#
+# As described in CVE-2009-0801 when the Host: header alone is used
+# to determine the destination of a request it becomes trivial for
+# malicious scripts on remote websites to bypass browser same-origin
+# security policy and sandboxing protections.
+#
+# The cause of this is that such applets are allowed to perform their
+# own HTTP stack, in which case the same-origin policy of the browser
+# sandbox only verifies that the applet tries to contact the same IP
+# as from where it was loaded at the IP level. The Host: header may
+# be different from the connected IP and approved origin.
+#
+#Default:
+# host_verify_strict off
+
+# TAG: client_dst_passthru
+# With NAT or TPROXY intercepted traffic Squid may pass the request
+# directly to the original client destination IP or seek a faster
+# source using the HTTP Host header.
+#
+# Using Host to locate alternative servers can provide faster
+# connectivity with a range of failure recovery options.
+# But can also lead to connectivity trouble when the client and
+# server are attempting stateful interactions unaware of the proxy.
+#
+# This option (on by default) prevents alternative DNS entries being
+# located to send intercepted traffic DIRECT to an origin server.
+# The clients original destination IP and port will be used instead.
+#
+# Regardless of this option setting, when dealing with intercepted
+# traffic Squid will verify the Host: header and any traffic which
+# fails Host verification will be treated as if this option were ON.
+#
+# see host_verify_strict for details on the verification process.
+#Default:
+# client_dst_passthru on
+
+# TLS OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: tls_outgoing_options
+# disable Do not support https:// URLs.
+#
+# cert=/path/to/client/certificate
+# A client X.509 certificate to use when connecting.
+#
+# key=/path/to/client/private_key
+# The private key corresponding to the cert= above.
+#
+# If key= is not specified cert= is assumed to
+# reference a PEM file containing both the certificate
+# and private key.
+#
+# cipher=... The list of valid TLS ciphers to use.
+#
+# min-version=1.N
+# The minimum TLS protocol version to permit.
+# To control SSLv3 use the options= parameter.
+# Supported Values: 1.0 (default), 1.1, 1.2
+#
+# options=... Specify various TLS/SSL implementation options.
+#
+# OpenSSL options most important are:
+#
+# NO_SSLv3 Disallow the use of SSLv3
+#
+# SINGLE_DH_USE
+# Always create a new key when using
+# temporary/ephemeral DH key exchanges
+#
+# NO_TICKET
+# Disable use of RFC5077 session tickets.
+# Some servers may have problems
+# understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+#
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation
+# for a more complete list.
+#
+# GnuTLS options most important are:
+#
+# %NO_TICKETS
+# Disable use of RFC5077 session tickets.
+# Some servers may have problems
+# understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+#
+# See the GnuTLS Priority Strings documentation
+# for a more complete list.
+# http://www.gnutls.org/manual/gnutls.html#Priority-Strings
+#
+#
+# cafile= PEM file containing CA certificates to use when verifying
+# the peer certificate. May be repeated to load multiple files.
+#
+# capath= A directory containing additional CA certificates to
+# use when verifying the peer certificate.
+# Requires OpenSSL or LibreSSL.
+#
+# crlfile=... A certificate revocation list file to use when
+# verifying the peer certificate.
+#
+# flags=... Specify various flags modifying the TLS implementation:
+#
+# DONT_VERIFY_PEER
+# Accept certificates even if they fail to
+# verify.
+# DONT_VERIFY_DOMAIN
+# Don't verify the peer certificate
+# matches the server name
+#
+# default-ca[=off]
+# Whether to use the system Trusted CAs. Default is ON.
+#
+# domain= The peer name as advertised in its certificate.
+# Used for verifying the correctness of the received peer
+# certificate. If not specified the peer hostname will be
+# used.
+#Default:
+# tls_outgoing_options min-version=1.0
+
+# SSL OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: ssl_unclean_shutdown
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Some browsers (especially MSIE) bugs out on SSL shutdown
+# messages.
+#Default:
+# ssl_unclean_shutdown off
+
+# TAG: ssl_engine
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# The OpenSSL engine to use. You will need to set this if you
+# would like to use hardware SSL acceleration for example.
+#Default:
+# none
+
+# TAG: sslproxy_session_ttl
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Sets the timeout value for SSL sessions
+#Default:
+# sslproxy_session_ttl 300
+
+# TAG: sslproxy_session_cache_size
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Sets the cache size to use for ssl session
+#Default:
+# sslproxy_session_cache_size 2 MB
+
+# TAG: sslproxy_foreign_intermediate_certs
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Many origin servers fail to send their full server certificate
+# chain for verification, assuming the client already has or can
+# easily locate any missing intermediate certificates.
+#
+# Squid uses the certificates from the specified file to fill in
+# these missing chains when trying to validate origin server
+# certificate chains.
+#
+# The file is expected to contain zero or more PEM-encoded
+# intermediate certificates. These certificates are not treated
+# as trusted root certificates, and any self-signed certificate in
+# this file will be ignored.
+#Default:
+# none
+
+# TAG: sslproxy_cert_sign_hash
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Sets the hashing algorithm to use when signing generated certificates.
+# Valid algorithm names depend on the OpenSSL library used. The following
+# names are usually available: sha1, sha256, sha512, and md5. Please see
+# your OpenSSL library manual for the available hashes. By default, Squids
+# that support this option use sha256 hashes.
+#
+# Squid does not forcefully purge cached certificates that were generated
+# with an algorithm other than the currently configured one. They remain
+# in the cache, subject to the regular cache eviction policy, and become
+# useful if the algorithm changes again.
+#Default:
+# none
+
+# TAG: ssl_bump
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# This option is consulted when a CONNECT request is received on
+# an http_port (or a new connection is intercepted at an
+# https_port), provided that port was configured with an ssl-bump
+# flag. The subsequent data on the connection is either treated as
+# HTTPS and decrypted OR tunneled at TCP level without decryption,
+# depending on the first matching bumping "action".
+#
+# ssl_bump <action> [!]acl ...
+#
+# The following bumping actions are currently supported:
+#
+# splice
+# Become a TCP tunnel without decrypting proxied traffic.
+# This is the default action.
+#
+# bump
+# When used on step SslBump1, establishes a secure connection
+# with the client first, then connect to the server.
+# When used on step SslBump2 or SslBump3, establishes a secure
+# connection with the server and, using a mimicked server
+# certificate, with the client.
+#
+# peek
+# Receive client (step SslBump1) or server (step SslBump2)
+# certificate while preserving the possibility of splicing the
+# connection. Peeking at the server certificate (during step 2)
+# usually precludes bumping of the connection at step 3.
+#
+# stare
+# Receive client (step SslBump1) or server (step SslBump2)
+# certificate while preserving the possibility of bumping the
+# connection. Staring at the server certificate (during step 2)
+# usually precludes splicing of the connection at step 3.
+#
+# terminate
+# Close client and server connections.
+#
+# Backward compatibility actions available at step SslBump1:
+#
+# client-first
+# Bump the connection. Establish a secure connection with the
+# client first, then connect to the server. This old mode does
+# not allow Squid to mimic server SSL certificate and does not
+# work with intercepted SSL connections.
+#
+# server-first
+# Bump the connection. Establish a secure connection with the
+# server first, then establish a secure connection with the
+# client, using a mimicked server certificate. Works with both
+# CONNECT requests and intercepted SSL connections, but does
+# not allow to make decisions based on SSL handshake info.
+#
+# peek-and-splice
+# Decide whether to bump or splice the connection based on
+# client-to-squid and server-to-squid SSL hello messages.
+# XXX: Remove.
+#
+# none
+# Same as the "splice" action.
+#
+# All ssl_bump rules are evaluated at each of the supported bumping
+# steps. Rules with actions that are impossible at the current step are
+# ignored. The first matching ssl_bump action wins and is applied at the
+# end of the current step. If no rules match, the splice action is used.
+# See the at_step ACL for a list of the supported SslBump steps.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# See also: http_port ssl-bump, https_port ssl-bump, and acl at_step.
+#
+#
+# # Example: Bump all TLS connections except those originating from
+# # localhost or those going to example.com.
+#
+# acl broken_sites ssl::server_name .example.com
+# ssl_bump splice localhost
+# ssl_bump splice broken_sites
+# ssl_bump bump all
+#Default:
+# Become a TCP tunnel without decrypting proxied traffic.
+
+# TAG: sslproxy_cert_error
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Use this ACL to bypass server certificate validation errors.
+#
+# For example, the following lines will bypass all validation errors
+# when talking to servers for example.com. All other
+# validation errors will result in ERR_SECURE_CONNECT_FAIL error.
+#
+# acl BrokenButTrustedServers dstdomain example.com
+# sslproxy_cert_error allow BrokenButTrustedServers
+# sslproxy_cert_error deny all
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+# Using slow acl types may result in server crashes
+#
+# Without this option, all server certificate validation errors
+# terminate the transaction to protect Squid and the client.
+#
+# SQUID_X509_V_ERR_INFINITE_VALIDATION error cannot be bypassed
+# but should not happen unless your OpenSSL library is buggy.
+#
+# SECURITY WARNING:
+# Bypassing validation errors is dangerous because an
+# error usually implies that the server cannot be trusted
+# and the connection may be insecure.
+#
+# See also: sslproxy_flags and DONT_VERIFY_PEER.
+#Default:
+# Server certificate errors terminate the transaction.
+
+# TAG: sslproxy_cert_sign
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+#
+# sslproxy_cert_sign <signing algorithm> acl ...
+#
+# The following certificate signing algorithms are supported:
+#
+# signTrusted
+# Sign using the configured CA certificate which is usually
+# placed in and trusted by end-user browsers. This is the
+# default for trusted origin server certificates.
+#
+# signUntrusted
+# Sign to guarantee an X509_V_ERR_CERT_UNTRUSTED browser error.
+# This is the default for untrusted origin server certificates
+# that are not self-signed (see ssl::certUntrusted).
+#
+# signSelf
+# Sign using a self-signed certificate with the right CN to
+# generate a X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT error in the
+# browser. This is the default for self-signed origin server
+# certificates (see ssl::certSelfSigned).
+#
+# This clause only supports fast acl types.
+#
+# When sslproxy_cert_sign acl(s) match, Squid uses the corresponding
+# signing algorithm to generate the certificate and ignores all
+# subsequent sslproxy_cert_sign options (the first match wins). If no
+# acl(s) match, the default signing algorithm is determined by errors
+# detected when obtaining and validating the origin server certificate.
+#
+# WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can
+# be used with sslproxy_cert_adapt, but if and only if Squid is bumping a
+# CONNECT request that carries a domain name. In all other cases (CONNECT
+# to an IP address or an intercepted SSL connection), Squid cannot detect
+# the domain mismatch at certificate generation time when
+# bump-server-first is used.
+#Default:
+# none
+
+# TAG: sslproxy_cert_adapt
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+#
+# sslproxy_cert_adapt <adaptation algorithm> acl ...
+#
+# The following certificate adaptation algorithms are supported:
+#
+# setValidAfter
+# Sets the "Not After" property to the "Not After" property of
+# the CA certificate used to sign generated certificates.
+#
+# setValidBefore
+# Sets the "Not Before" property to the "Not Before" property of
+# the CA certificate used to sign generated certificates.
+#
+# setCommonName or setCommonName{CN}
+# Sets Subject.CN property to the host name specified as a
+# CN parameter or, if no explicit CN parameter was specified,
+# extracted from the CONNECT request. It is a misconfiguration
+# to use setCommonName without an explicit parameter for
+# intercepted or tproxied SSL connections.
+#
+# This clause only supports fast acl types.
+#
+# Squid first groups sslproxy_cert_adapt options by adaptation algorithm.
+# Within a group, when sslproxy_cert_adapt acl(s) match, Squid uses the
+# corresponding adaptation algorithm to generate the certificate and
+# ignores all subsequent sslproxy_cert_adapt options in that algorithm's
+# group (i.e., the first match wins within each algorithm group). If no
+# acl(s) match, the default mimicking action takes place.
+#
+# WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can
+# be used with sslproxy_cert_adapt, but if and only if Squid is bumping a
+# CONNECT request that carries a domain name. In all other cases (CONNECT
+# to an IP address or an intercepted SSL connection), Squid cannot detect
+# the domain mismatch at certificate generation time when
+# bump-server-first is used.
+#Default:
+# none
+
+# TAG: sslpassword_program
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Specify a program used for entering SSL key passphrases
+# when using encrypted SSL certificate keys. If not specified
+# keys must either be unencrypted, or Squid started with the -N
+# option to allow it to query interactively for the passphrase.
+#
+# The key file name is given as argument to the program allowing
+# selection of the right password if you have multiple encrypted
+# keys.
+#Default:
+# none
+
+# OPTIONS RELATING TO EXTERNAL SSL_CRTD
+# -----------------------------------------------------------------------------
+
+# TAG: sslcrtd_program
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl-crtd
+#
+# Specify the location and options of the executable for certificate
+# generator.
+#
+# /usr/lib/squid/security_file_certgen program can use a disk cache to improve response
+# times on repeated requests. To enable caching, specify -s and -M
+# parameters. If those parameters are not given, the program generates
+# a new certificate on every request.
+#
+# For more information use:
+# /usr/lib/squid/security_file_certgen -h
+#Default:
+# sslcrtd_program /usr/lib/squid/security_file_certgen -s /var/spool/squid/ssl_db -M 4MB
+
+# TAG: sslcrtd_children
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl-crtd
+#
+# Specifies the maximum number of certificate generation processes that
+# Squid may spawn (numberofchildren) and several related options. Using
+# too few of these helper processes (a.k.a. "helpers") creates request
+# queues. Using too many helpers wastes your system resources. Squid
+# does not support spawning more than 32 helpers.
+#
+# Usage: numberofchildren [option]...
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=N
+#
+# Sets the minimum number of processes to spawn when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few children temporary slows Squid under load while it
+# tries to spawn enough additional processes to cope with traffic.
+#
+# idle=N
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# queue-size=N
+#
+# Sets the maximum number of queued requests. A request is queued when
+# no existing child is idle and no new child can be started due to
+# numberofchildren limit. If the queued requests exceed queue size for
+# more than 3 minutes squid aborts its operation. The default value is
+# set to 2*numberofchildren.
+#
+# You must have at least one ssl_crtd process.
+#Default:
+# sslcrtd_children 32 startup=5 idle=1
+
+# TAG: sslcrtvalidator_program
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Specify the location and options of the executable for ssl_crt_validator
+# process.
+#
+# Usage: sslcrtvalidator_program [ttl=n] [cache=n] path ...
+#
+# Options:
+# ttl=n TTL in seconds for cached results. The default is 60 secs
+# cache=n limit the result cache size. The default value is 2048
+#Default:
+# none
+
+# TAG: sslcrtvalidator_children
+# Note: This option is only available if Squid is rebuilt with the
+# --with-openssl
+#
+# Specifies the maximum number of certificate validation processes that
+# Squid may spawn (numberofchildren) and several related options. Using
+# too few of these helper processes (a.k.a. "helpers") creates request
+# queues. Using too many helpers wastes your system resources. Squid
+# does not support spawning more than 32 helpers.
+#
+# Usage: numberofchildren [option]...
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=N
+#
+# Sets the minimum number of processes to spawn when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few children temporary slows Squid under load while it
+# tries to spawn enough additional processes to cope with traffic.
+#
+# idle=N
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each certificate validator helper can handle in
+# parallel. A value of 0 indicates the certficate validator does not
+# support concurrency. Defaults to 1.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# a request ID in front of the request/response. The request
+# ID from the request must be echoed back with the response
+# to that request.
+#
+# queue-size=N
+#
+# Sets the maximum number of queued requests. A request is queued when
+# no existing child can accept it due to concurrency limit and no new
+# child can be started due to numberofchildren limit. If the queued
+# requests exceed queue size for more than 3 minutes squid aborts its
+# operation. The default value is set to 2*numberofchildren.
+#
+# You must have at least one ssl_crt_validator process.
+#Default:
+# sslcrtvalidator_children 32 startup=5 idle=1 concurrency=1
+
+# OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM
+# -----------------------------------------------------------------------------
+
+# TAG: cache_peer
+# To specify other caches in a hierarchy, use the format:
+#
+# cache_peer hostname type http-port icp-port [options]
+#
+# For example,
+#
+# # proxy icp
+# # hostname type port port options
+# # -------------------- -------- ----- ----- -----------
+# cache_peer parent.foo.net parent 3128 3130 default
+# cache_peer sib1.foo.net sibling 3128 3130 proxy-only
+# cache_peer sib2.foo.net sibling 3128 3130 proxy-only
+# cache_peer example.com parent 80 0 default
+# cache_peer cdn.example.com sibling 3128 0
+#
+# type: either 'parent', 'sibling', or 'multicast'.
+#
+# proxy-port: The port number where the peer accept HTTP requests.
+# For other Squid proxies this is usually 3128
+# For web servers this is usually 80
+#
+# icp-port: Used for querying neighbor caches about objects.
+# Set to 0 if the peer does not support ICP or HTCP.
+# See ICP and HTCP options below for additional details.
+#
+#
+# ==== ICP OPTIONS ====
+#
+# You MUST also set icp_port and icp_access explicitly when using these options.
+# The defaults will prevent peer traffic using ICP.
+#
+#
+# no-query Disable ICP queries to this neighbor.
+#
+# multicast-responder
+# Indicates the named peer is a member of a multicast group.
+# ICP queries will not be sent directly to the peer, but ICP
+# replies will be accepted from it.
+#
+# closest-only Indicates that, for ICP_OP_MISS replies, we'll only forward
+# CLOSEST_PARENT_MISSes and never FIRST_PARENT_MISSes.
+#
+# background-ping
+# To only send ICP queries to this neighbor infrequently.
+# This is used to keep the neighbor round trip time updated
+# and is usually used in conjunction with weighted-round-robin.
+#
+#
+# ==== HTCP OPTIONS ====
+#
+# You MUST also set htcp_port and htcp_access explicitly when using these options.
+# The defaults will prevent peer traffic using HTCP.
+#
+#
+# htcp Send HTCP, instead of ICP, queries to the neighbor.
+# You probably also want to set the "icp-port" to 4827
+# instead of 3130. This directive accepts a comma separated
+# list of options described below.
+#
+# htcp=oldsquid Send HTCP to old Squid versions (2.5 or earlier).
+#
+# htcp=no-clr Send HTCP to the neighbor but without
+# sending any CLR requests. This cannot be used with
+# only-clr.
+#
+# htcp=only-clr Send HTCP to the neighbor but ONLY CLR requests.
+# This cannot be used with no-clr.
+#
+# htcp=no-purge-clr
+# Send HTCP to the neighbor including CLRs but only when
+# they do not result from PURGE requests.
+#
+# htcp=forward-clr
+# Forward any HTCP CLR requests this proxy receives to the peer.
+#
+#
+# ==== PEER SELECTION METHODS ====
+#
+# The default peer selection method is ICP, with the first responding peer
+# being used as source. These options can be used for better load balancing.
+#
+#
+# default This is a parent cache which can be used as a "last-resort"
+# if a peer cannot be located by any of the peer-selection methods.
+# If specified more than once, only the first is used.
+#
+# round-robin Load-Balance parents which should be used in a round-robin
+# fashion in the absence of any ICP queries.
+# weight=N can be used to add bias.
+#
+# weighted-round-robin
+# Load-Balance parents which should be used in a round-robin
+# fashion with the frequency of each parent being based on the
+# round trip time. Closer parents are used more often.
+# Usually used for background-ping parents.
+# weight=N can be used to add bias.
+#
+# carp Load-Balance parents which should be used as a CARP array.
+# The requests will be distributed among the parents based on the
+# CARP load balancing hash function based on their weight.
+#
+# userhash Load-balance parents based on the client proxy_auth or ident username.
+#
+# sourcehash Load-balance parents based on the client source IP.
+#
+# multicast-siblings
+# To be used only for cache peers of type "multicast".
+# ALL members of this multicast group have "sibling"
+# relationship with it, not "parent". This is to a multicast
+# group when the requested object would be fetched only from
+# a "parent" cache, anyway. It's useful, e.g., when
+# configuring a pool of redundant Squid proxies, being
+# members of the same multicast group.
+#
+#
+# ==== PEER SELECTION OPTIONS ====
+#
+# weight=N use to affect the selection of a peer during any weighted
+# peer-selection mechanisms.
+# The weight must be an integer; default is 1,
+# larger weights are favored more.
+# This option does not affect parent selection if a peering
+# protocol is not in use.
+#
+# basetime=N Specify a base amount to be subtracted from round trip
+# times of parents.
+# It is subtracted before division by weight in calculating
+# which parent to fectch from. If the rtt is less than the
+# base time the rtt is set to a minimal value.
+#
+# ttl=N Specify a TTL to use when sending multicast ICP queries
+# to this address.
+# Only useful when sending to a multicast group.
+# Because we don't accept ICP replies from random
+# hosts, you must configure other group members as
+# peers with the 'multicast-responder' option.
+#
+# no-delay To prevent access to this neighbor from influencing the
+# delay pools.
+#
+# digest-url=URL Tell Squid to fetch the cache digest (if digests are
+# enabled) for this host from the specified URL rather
+# than the Squid default location.
+#
+#
+# ==== CARP OPTIONS ====
+#
+# carp-key=key-specification
+# use a different key than the full URL to hash against the peer.
+# the key-specification is a comma-separated list of the keywords
+# scheme, host, port, path, params
+# Order is not important.
+#
+# ==== ACCELERATOR / REVERSE-PROXY OPTIONS ====
+#
+# originserver Causes this parent to be contacted as an origin server.
+# Meant to be used in accelerator setups when the peer
+# is a web server.
+#
+# forceddomain=name
+# Set the Host header of requests forwarded to this peer.
+# Useful in accelerator setups where the server (peer)
+# expects a certain domain name but clients may request
+# others. ie example.com or www.example.com
+#
+# no-digest Disable request of cache digests.
+#
+# no-netdb-exchange
+# Disables requesting ICMP RTT database (NetDB).
+#
+#
+# ==== AUTHENTICATION OPTIONS ====
+#
+# login=user:password
+# If this is a personal/workgroup proxy and your parent
+# requires proxy authentication.
+#
+# Note: The string can include URL escapes (i.e. %20 for
+# spaces). This also means % must be written as %%.
+#
+# login=PASSTHRU
+# Send login details received from client to this peer.
+# Both Proxy- and WWW-Authorization headers are passed
+# without alteration to the peer.
+# Authentication is not required by Squid for this to work.
+#
+# Note: This will pass any form of authentication but
+# only Basic auth will work through a proxy unless the
+# connection-auth options are also used.
+#
+# login=PASS Send login details received from client to this peer.
+# Authentication is not required by this option.
+#
+# If there are no client-provided authentication headers
+# to pass on, but username and password are available
+# from an external ACL user= and password= result tags
+# they may be sent instead.
+#
+# Note: To combine this with proxy_auth both proxies must
+# share the same user database as HTTP only allows for
+# a single login (one for proxy, one for origin server).
+# Also be warned this will expose your users proxy
+# password to the peer. USE WITH CAUTION
+#
+# login=*:password
+# Send the username to the upstream cache, but with a
+# fixed password. This is meant to be used when the peer
+# is in another administrative domain, but it is still
+# needed to identify each user.
+# The star can optionally be followed by some extra
+# information which is added to the username. This can
+# be used to identify this proxy to the peer, similar to
+# the login=username:password option above.
+#
+# login=NEGOTIATE
+# If this is a personal/workgroup proxy and your parent
+# requires a secure proxy authentication.
+# The first principal from the default keytab or defined by
+# the environment variable KRB5_KTNAME will be used.
+#
+# WARNING: The connection may transmit requests from multiple
+# clients. Negotiate often assumes end-to-end authentication
+# and a single-client. Which is not strictly true here.
+#
+# login=NEGOTIATE:principal_name
+# If this is a personal/workgroup proxy and your parent
+# requires a secure proxy authentication.
+# The principal principal_name from the default keytab or
+# defined by the environment variable KRB5_KTNAME will be
+# used.
+#
+# WARNING: The connection may transmit requests from multiple
+# clients. Negotiate often assumes end-to-end authentication
+# and a single-client. Which is not strictly true here.
+#
+# connection-auth=on|off
+# Tell Squid that this peer does or not support Microsoft
+# connection oriented authentication, and any such
+# challenges received from there should be ignored.
+# Default is auto to automatically determine the status
+# of the peer.
+#
+# auth-no-keytab
+# Do not use a keytab to authenticate to a peer when
+# login=NEGOTIATE is specified. Let the GSSAPI
+# implementation determine which already existing
+# credentials cache to use instead.
+#
+#
+# ==== SSL / HTTPS / TLS OPTIONS ====
+#
+# tls Encrypt connections to this peer with TLS.
+#
+# sslcert=/path/to/ssl/certificate
+# A client X.509 certificate to use when connecting to
+# this peer.
+#
+# sslkey=/path/to/ssl/key
+# The private key corresponding to sslcert above.
+#
+# If sslkey= is not specified sslcert= is assumed to
+# reference a PEM file containing both the certificate
+# and private key.
+#
+# sslcipher=... The list of valid SSL ciphers to use when connecting
+# to this peer.
+#
+# tls-min-version=1.N
+# The minimum TLS protocol version to permit. To control
+# SSLv3 use the tls-options= parameter.
+# Supported Values: 1.0 (default), 1.1, 1.2
+#
+# tls-options=... Specify various TLS implementation options.
+#
+# OpenSSL options most important are:
+#
+# NO_SSLv3 Disallow the use of SSLv3
+#
+# SINGLE_DH_USE
+# Always create a new key when using
+# temporary/ephemeral DH key exchanges
+#
+# NO_TICKET
+# Disable use of RFC5077 session tickets.
+# Some servers may have problems
+# understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+#
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation for a
+# more complete list.
+#
+# GnuTLS options most important are:
+#
+# %NO_TICKETS
+# Disable use of RFC5077 session tickets.
+# Some servers may have problems
+# understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+#
+# See the GnuTLS Priority Strings documentation
+# for a more complete list.
+# http://www.gnutls.org/manual/gnutls.html#Priority-Strings
+#
+# tls-cafile= PEM file containing CA certificates to use when verifying
+# the peer certificate. May be repeated to load multiple files.
+#
+# sslcapath=... A directory containing additional CA certificates to
+# use when verifying the peer certificate.
+# Requires OpenSSL or LibreSSL.
+#
+# sslcrlfile=... A certificate revocation list file to use when
+# verifying the peer certificate.
+#
+# sslflags=... Specify various flags modifying the SSL implementation:
+#
+# DONT_VERIFY_PEER
+# Accept certificates even if they fail to
+# verify.
+#
+# DONT_VERIFY_DOMAIN
+# Don't verify the peer certificate
+# matches the server name
+#
+# ssldomain= The peer name as advertised in it's certificate.
+# Used for verifying the correctness of the received peer
+# certificate. If not specified the peer hostname will be
+# used.
+#
+# front-end-https[=off|on|auto]
+# Enable the "Front-End-Https: On" header needed when
+# using Squid as a SSL frontend in front of Microsoft OWA.
+# See MS KB document Q307347 for details on this header.
+# If set to auto the header will only be added if the
+# request is forwarded as a https:// URL.
+#
+# tls-default-ca[=off]
+# Whether to use the system Trusted CAs. Default is ON.
+#
+# tls-no-npn Do not use the TLS NPN extension to advertise HTTP/1.1.
+#
+# ==== GENERAL OPTIONS ====
+#
+# connect-timeout=N
+# A peer-specific connect timeout.
+# Also see the peer_connect_timeout directive.
+#
+# connect-fail-limit=N
+# How many times connecting to a peer must fail before
+# it is marked as down. Standby connection failures
+# count towards this limit. Default is 10.
+#
+# allow-miss Disable Squid's use of only-if-cached when forwarding
+# requests to siblings. This is primarily useful when
+# icp_hit_stale is used by the sibling. Excessive use
+# of this option may result in forwarding loops. One way
+# to prevent peering loops when using this option, is to
+# deny cache peer usage on requests from a peer:
+# acl fromPeer ...
+# cache_peer_access peerName deny fromPeer
+#
+# max-conn=N Limit the number of concurrent connections the Squid
+# may open to this peer, including already opened idle
+# and standby connections. There is no peer-specific
+# connection limit by default.
+#
+# A peer exceeding the limit is not used for new
+# requests unless a standby connection is available.
+#
+# max-conn currently works poorly with idle persistent
+# connections: When a peer reaches its max-conn limit,
+# and there are idle persistent connections to the peer,
+# the peer may not be selected because the limiting code
+# does not know whether Squid can reuse those idle
+# connections.
+#
+# standby=N Maintain a pool of N "hot standby" connections to an
+# UP peer, available for requests when no idle
+# persistent connection is available (or safe) to use.
+# By default and with zero N, no such pool is maintained.
+# N must not exceed the max-conn limit (if any).
+#
+# At start or after reconfiguration, Squid opens new TCP
+# standby connections until there are N connections
+# available and then replenishes the standby pool as
+# opened connections are used up for requests. A used
+# connection never goes back to the standby pool, but
+# may go to the regular idle persistent connection pool
+# shared by all peers and origin servers.
+#
+# Squid never opens multiple new standby connections
+# concurrently. This one-at-a-time approach minimizes
+# flooding-like effect on peers. Furthermore, just a few
+# standby connections should be sufficient in most cases
+# to supply most new requests with a ready-to-use
+# connection.
+#
+# Standby connections obey server_idle_pconn_timeout.
+# For the feature to work as intended, the peer must be
+# configured to accept and keep them open longer than
+# the idle timeout at the connecting Squid, to minimize
+# race conditions typical to idle used persistent
+# connections. Default request_timeout and
+# server_idle_pconn_timeout values ensure such a
+# configuration.
+#
+# name=xxx Unique name for the peer.
+# Required if you have multiple peers on the same host
+# but different ports.
+# This name can be used in cache_peer_access and similar
+# directives to identify the peer.
+# Can be used by outgoing access controls through the
+# peername ACL type.
+#
+# no-tproxy Do not use the client-spoof TPROXY support when forwarding
+# requests to this peer. Use normal address selection instead.
+# This overrides the spoof_client_ip ACL.
+#
+# proxy-only objects fetched from the peer will not be stored locally.
+#
+#Default:
+# none
+
+# TAG: cache_peer_access
+# Restricts usage of cache_peer proxies.
+#
+# Usage:
+# cache_peer_access peer-name allow|deny [!]aclname ...
+#
+# For the required peer-name parameter, use either the value of the
+# cache_peer name=value parameter or, if name=value is missing, the
+# cache_peer hostname parameter.
+#
+# This directive narrows down the selection of peering candidates, but
+# does not determine the order in which the selected candidates are
+# contacted. That order is determined by the peer selection algorithms
+# (see PEER SELECTION sections in the cache_peer documentation).
+#
+# If a deny rule matches, the corresponding peer will not be contacted
+# for the current transaction -- Squid will not send ICP queries and
+# will not forward HTTP requests to that peer. An allow match leaves
+# the corresponding peer in the selection. The first match for a given
+# peer wins for that peer.
+#
+# The relative order of cache_peer_access directives for the same peer
+# matters. The relative order of any two cache_peer_access directives
+# for different peers does not matter. To ease interpretation, it is a
+# good idea to group cache_peer_access directives for the same peer
+# together.
+#
+# A single cache_peer_access directive may be evaluated multiple times
+# for a given transaction because individual peer selection algorithms
+# may check it independently from each other. These redundant checks
+# may be optimized away in future Squid versions.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Default:
+# No peer usage restrictions.
+
+# TAG: neighbor_type_domain
+# Modify the cache_peer neighbor type when passing requests
+# about specific domains to the peer.
+#
+# Usage:
+# neighbor_type_domain neighbor parent|sibling domain domain ...
+#
+# For example:
+# cache_peer foo.example.com parent 3128 3130
+# neighbor_type_domain foo.example.com sibling .au .de
+#
+# The above configuration treats all requests to foo.example.com as a
+# parent proxy unless the request is for a .au or .de ccTLD domain name.
+#Default:
+# The peer type from cache_peer directive is used for all requests to that peer.
+
+# TAG: dead_peer_timeout (seconds)
+# This controls how long Squid waits to declare a peer cache
+# as "dead." If there are no ICP replies received in this
+# amount of time, Squid will declare the peer dead and not
+# expect to receive any further ICP replies. However, it
+# continues to send ICP queries, and will mark the peer as
+# alive upon receipt of the first subsequent ICP reply.
+#
+# This timeout also affects when Squid expects to receive ICP
+# replies from peers. If more than 'dead_peer' seconds have
+# passed since the last ICP reply was received, Squid will not
+# expect to receive an ICP reply on the next query. Thus, if
+# your time between requests is greater than this timeout, you
+# will see a lot of requests sent DIRECT to origin servers
+# instead of to your parents.
+#Default:
+# dead_peer_timeout 10 seconds
+
+# TAG: forward_max_tries
+# Limits the number of attempts to forward the request.
+#
+# For the purpose of this limit, Squid counts all high-level request
+# forwarding attempts, including any same-destination retries after
+# certain persistent connection failures and any attempts to use a
+# different peer. However, low-level connection reopening attempts
+# (enabled using connect_retries) are not counted.
+#
+# See also: forward_timeout and connect_retries.
+#Default:
+# forward_max_tries 25
+
+# MEMORY CACHE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_mem (bytes)
+# NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE.
+# IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL
+# USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER
+# THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS.
+#
+# 'cache_mem' specifies the ideal amount of memory to be used
+# for:
+# * In-Transit objects
+# * Hot Objects
+# * Negative-Cached objects
+#
+# Data for these objects are stored in 4 KB blocks. This
+# parameter specifies the ideal upper limit on the total size of
+# 4 KB blocks allocated. In-Transit objects take the highest
+# priority.
+#
+# In-transit objects have priority over the others. When
+# additional space is needed for incoming data, negative-cached
+# and hot objects will be released. In other words, the
+# negative-cached and hot objects will fill up any unused space
+# not needed for in-transit objects.
+#
+# If circumstances require, this limit will be exceeded.
+# Specifically, if your incoming request rate requires more than
+# 'cache_mem' of memory to hold in-transit objects, Squid will
+# exceed this limit to satisfy the new requests. When the load
+# decreases, blocks will be freed until the high-water mark is
+# reached. Thereafter, blocks will be used to store hot
+# objects.
+#
+# If shared memory caching is enabled, Squid does not use the shared
+# cache space for in-transit objects, but they still consume as much
+# local memory as they need. For more details about the shared memory
+# cache, see memory_cache_shared.
+#Default:
+# cache_mem 256 MB
+
+# TAG: maximum_object_size_in_memory (bytes)
+# Objects greater than this size will not be attempted to kept in
+# the memory cache. This should be set high enough to keep objects
+# accessed frequently in memory to improve performance whilst low
+# enough to keep larger objects from hoarding cache_mem.
+#Default:
+# maximum_object_size_in_memory 512 KB
+
+# TAG: memory_cache_shared on|off
+# Controls whether the memory cache is shared among SMP workers.
+#
+# The shared memory cache is meant to occupy cache_mem bytes and replace
+# the non-shared memory cache, although some entities may still be
+# cached locally by workers for now (e.g., internal and in-transit
+# objects may be served from a local memory cache even if shared memory
+# caching is enabled).
+#
+# By default, the memory cache is shared if and only if all of the
+# following conditions are satisfied: Squid runs in SMP mode with
+# multiple workers, cache_mem is positive, and Squid environment
+# supports required IPC primitives (e.g., POSIX shared memory segments
+# and GCC-style atomic operations).
+#
+# To avoid blocking locks, shared memory uses opportunistic algorithms
+# that do not guarantee that every cachable entity that could have been
+# shared among SMP workers will actually be shared.
+#Default:
+# "on" where supported if doing memory caching with multiple SMP workers.
+
+# TAG: memory_cache_mode
+# Controls which objects to keep in the memory cache (cache_mem)
+#
+# always Keep most recently fetched objects in memory (default)
+#
+# disk Only disk cache hits are kept in memory, which means
+# an object must first be cached on disk and then hit
+# a second time before cached in memory.
+#
+# network Only objects fetched from network is kept in memory
+#Default:
+# Keep the most recently fetched objects in memory
+
+# TAG: memory_replacement_policy
+# The memory replacement policy parameter determines which
+# objects are purged from memory when memory space is needed.
+#
+# See cache_replacement_policy for details on algorithms.
+#Default:
+# memory_replacement_policy lru
+
+# DISK CACHE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_replacement_policy
+# The cache replacement policy parameter determines which
+# objects are evicted (replaced) when disk space is needed.
+#
+# lru : Squid's original list based LRU policy
+# heap GDSF : Greedy-Dual Size Frequency
+# heap LFUDA: Least Frequently Used with Dynamic Aging
+# heap LRU : LRU policy implemented using a heap
+#
+# Applies to any cache_dir lines listed below this directive.
+#
+# The LRU policies keeps recently referenced objects.
+#
+# The heap GDSF policy optimizes object hit rate by keeping smaller
+# popular objects in cache so it has a better chance of getting a
+# hit. It achieves a lower byte hit rate than LFUDA though since
+# it evicts larger (possibly popular) objects.
+#
+# The heap LFUDA policy keeps popular objects in cache regardless of
+# their size and thus optimizes byte hit rate at the expense of
+# hit rate since one large, popular object will prevent many
+# smaller, slightly less popular objects from being cached.
+#
+# Both policies utilize a dynamic aging mechanism that prevents
+# cache pollution that can otherwise occur with frequency-based
+# replacement policies.
+#
+# NOTE: if using the LFUDA replacement policy you should increase
+# the value of maximum_object_size above its default of 4 MB to
+# to maximize the potential byte hit rate improvement of LFUDA.
+#
+# For more information about the GDSF and LFUDA cache replacement
+# policies see http://www.hpl.hp.com/techreports/1999/HPL-1999-69.html
+# and http://fog.hpl.external.hp.com/techreports/98/HPL-98-173.html.
+#Default:
+# cache_replacement_policy lru
+
+# TAG: minimum_object_size (bytes)
+# Objects smaller than this size will NOT be saved on disk. The
+# value is specified in bytes, and the default is 0 KB, which
+# means all responses can be stored.
+#Default:
+# no limit
+
+# TAG: maximum_object_size (bytes)
+# Set the default value for max-size parameter on any cache_dir.
+# The value is specified in bytes, and the default is 4 MB.
+#
+# If you wish to get a high BYTES hit ratio, you should probably
+# increase this (one 32 MB object hit counts for 3200 10KB
+# hits).
+#
+# If you wish to increase hit ratio more than you want to
+# save bandwidth you should leave this low.
+#
+# NOTE: if using the LFUDA replacement policy you should increase
+# this value to maximize the byte hit rate improvement of LFUDA!
+# See cache_replacement_policy for a discussion of this policy.
+#Default:
+# maximum_object_size 4 MB
+
+# TAG: cache_dir
+# Format:
+# cache_dir Type Directory-Name Fs-specific-data [options]
+#
+# You can specify multiple cache_dir lines to spread the
+# cache among different disk partitions.
+#
+# Type specifies the kind of storage system to use. Only "ufs"
+# is built by default. To enable any of the other storage systems
+# see the --enable-storeio configure option.
+#
+# 'Directory' is a top-level directory where cache swap
+# files will be stored. If you want to use an entire disk
+# for caching, this can be the mount-point directory.
+# The directory must exist and be writable by the Squid
+# process. Squid will NOT create this directory for you.
+#
+# In SMP configurations, cache_dir must not precede the workers option
+# and should use configuration macros or conditionals to give each
+# worker interested in disk caching a dedicated cache directory.
+#
+#
+# ==== The ufs store type ====
+#
+# "ufs" is the old well-known Squid storage format that has always
+# been there.
+#
+# Usage:
+# cache_dir ufs Directory-Name Mbytes L1 L2 [options]
+#
+# 'Mbytes' is the amount of disk space (MB) to use under this
+# directory. The default is 100 MB. Change this to suit your
+# configuration. Do NOT put the size of your disk drive here.
+# Instead, if you want Squid to use the entire disk drive,
+# subtract 20% and use that value.
+#
+# 'L1' is the number of first-level subdirectories which
+# will be created under the 'Directory'. The default is 16.
+#
+# 'L2' is the number of second-level subdirectories which
+# will be created under each first-level directory. The default
+# is 256.
+#
+#
+# ==== The aufs store type ====
+#
+# "aufs" uses the same storage format as "ufs", utilizing
+# POSIX-threads to avoid blocking the main Squid process on
+# disk-I/O. This was formerly known in Squid as async-io.
+#
+# Usage:
+# cache_dir aufs Directory-Name Mbytes L1 L2 [options]
+#
+# see argument descriptions under ufs above
+#
+#
+# ==== The diskd store type ====
+#
+# "diskd" uses the same storage format as "ufs", utilizing a
+# separate process to avoid blocking the main Squid process on
+# disk-I/O.
+#
+# Usage:
+# cache_dir diskd Directory-Name Mbytes L1 L2 [options] [Q1=n] [Q2=n]
+#
+# see argument descriptions under ufs above
+#
+# Q1 specifies the number of unacknowledged I/O requests when Squid
+# stops opening new files. If this many messages are in the queues,
+# Squid won't open new files. Default is 64
+#
+# Q2 specifies the number of unacknowledged messages when Squid
+# starts blocking. If this many messages are in the queues,
+# Squid blocks until it receives some replies. Default is 72
+#
+# When Q1 < Q2 (the default), the cache directory is optimized
+# for lower response time at the expense of a decrease in hit
+# ratio. If Q1 > Q2, the cache directory is optimized for
+# higher hit ratio at the expense of an increase in response
+# time.
+#
+#
+# ==== The rock store type ====
+#
+# Usage:
+# cache_dir rock Directory-Name Mbytes [options]
+#
+# The Rock Store type is a database-style storage. All cached
+# entries are stored in a "database" file, using fixed-size slots.
+# A single entry occupies one or more slots.
+#
+# If possible, Squid using Rock Store creates a dedicated kid
+# process called "disker" to avoid blocking Squid worker(s) on disk
+# I/O. One disker kid is created for each rock cache_dir. Diskers
+# are created only when Squid, running in daemon mode, has support
+# for the IpcIo disk I/O module.
+#
+# swap-timeout=msec: Squid will not start writing a miss to or
+# reading a hit from disk if it estimates that the swap operation
+# will take more than the specified number of milliseconds. By
+# default and when set to zero, disables the disk I/O time limit
+# enforcement. Ignored when using blocking I/O module because
+# blocking synchronous I/O does not allow Squid to estimate the
+# expected swap wait time.
+#
+# max-swap-rate=swaps/sec: Artificially limits disk access using
+# the specified I/O rate limit. Swap out requests that
+# would cause the average I/O rate to exceed the limit are
+# delayed. Individual swap in requests (i.e., hits or reads) are
+# not delayed, but they do contribute to measured swap rate and
+# since they are placed in the same FIFO queue as swap out
+# requests, they may wait longer if max-swap-rate is smaller.
+# This is necessary on file systems that buffer "too
+# many" writes and then start blocking Squid and other processes
+# while committing those writes to disk. Usually used together
+# with swap-timeout to avoid excessive delays and queue overflows
+# when disk demand exceeds available disk "bandwidth". By default
+# and when set to zero, disables the disk I/O rate limit
+# enforcement. Currently supported by IpcIo module only.
+#
+# slot-size=bytes: The size of a database "record" used for
+# storing cached responses. A cached response occupies at least
+# one slot and all database I/O is done using individual slots so
+# increasing this parameter leads to more disk space waste while
+# decreasing it leads to more disk I/O overheads. Should be a
+# multiple of your operating system I/O page size. Defaults to
+# 16KBytes. A housekeeping header is stored with each slot and
+# smaller slot-sizes will be rejected. The header is smaller than
+# 100 bytes.
+#
+#
+# ==== COMMON OPTIONS ====
+#
+# no-store no new objects should be stored to this cache_dir.
+#
+# min-size=n the minimum object size in bytes this cache_dir
+# will accept. It's used to restrict a cache_dir
+# to only store large objects (e.g. AUFS) while
+# other stores are optimized for smaller objects
+# (e.g. Rock).
+# Defaults to 0.
+#
+# max-size=n the maximum object size in bytes this cache_dir
+# supports.
+# The value in maximum_object_size directive sets
+# the default unless more specific details are
+# available (ie a small store capacity).
+#
+# Note: To make optimal use of the max-size limits you should order
+# the cache_dir lines with the smallest max-size value first.
+#
+#Default:
+# No disk cache. Store cache ojects only in memory.
+#
+
+# Uncomment and adjust the following to add a disk cache directory.
+#cache_dir ufs /var/spool/squid 100 16 256
+
+# TAG: store_dir_select_algorithm
+# How Squid selects which cache_dir to use when the response
+# object will fit into more than one.
+#
+# Regardless of which algorithm is used the cache_dir min-size
+# and max-size parameters are obeyed. As such they can affect
+# the selection algorithm by limiting the set of considered
+# cache_dir.
+#
+# Algorithms:
+#
+# least-load
+#
+# This algorithm is suited to caches with similar cache_dir
+# sizes and disk speeds.
+#
+# The disk with the least I/O pending is selected.
+# When there are multiple disks with the same I/O load ranking
+# the cache_dir with most available capacity is selected.
+#
+# When a mix of cache_dir sizes are configured the faster disks
+# have a naturally lower I/O loading and larger disks have more
+# capacity. So space used to store objects and data throughput
+# may be very unbalanced towards larger disks.
+#
+#
+# round-robin
+#
+# This algorithm is suited to caches with unequal cache_dir
+# disk sizes.
+#
+# Each cache_dir is selected in a rotation. The next suitable
+# cache_dir is used.
+#
+# Available cache_dir capacity is only considered in relation
+# to whether the object will fit and meets the min-size and
+# max-size parameters.
+#
+# Disk I/O loading is only considered to prevent overload on slow
+# disks. This algorithm does not spread objects by size, so any
+# I/O loading per-disk may appear very unbalanced and volatile.
+#
+# If several cache_dirs use similar min-size, max-size, or other
+# limits to to reject certain responses, then do not group such
+# cache_dir lines together, to avoid round-robin selection bias
+# towards the first cache_dir after the group. Instead, interleave
+# cache_dir lines from different groups. For example:
+#
+# store_dir_select_algorithm round-robin
+# cache_dir rock /hdd1 ... min-size=100000
+# cache_dir rock /ssd1 ... max-size=99999
+# cache_dir rock /hdd2 ... min-size=100000
+# cache_dir rock /ssd2 ... max-size=99999
+# cache_dir rock /hdd3 ... min-size=100000
+# cache_dir rock /ssd3 ... max-size=99999
+#Default:
+# store_dir_select_algorithm least-load
+
+# TAG: max_open_disk_fds
+# To avoid having disk as the I/O bottleneck Squid can optionally
+# bypass the on-disk cache if more than this amount of disk file
+# descriptors are open.
+#
+# A value of 0 indicates no limit.
+#Default:
+# no limit
+
+# TAG: cache_swap_low (percent, 0-100)
+# The low-water mark for AUFS/UFS/diskd cache object eviction by
+# the cache_replacement_policy algorithm.
+#
+# Removal begins when the swap (disk) usage of a cache_dir is
+# above this low-water mark and attempts to maintain utilization
+# near the low-water mark.
+#
+# As swap utilization increases towards the high-water mark set
+# by cache_swap_high object eviction becomes more agressive.
+#
+# The value difference in percentages between low- and high-water
+# marks represent an eviction rate of 300 objects per second and
+# the rate continues to scale in agressiveness by multiples of
+# this above the high-water mark.
+#
+# Defaults are 90% and 95%. If you have a large cache, 5% could be
+# hundreds of MB. If this is the case you may wish to set these
+# numbers closer together.
+#
+# See also cache_swap_high and cache_replacement_policy
+#Default:
+# cache_swap_low 90
+
+# TAG: cache_swap_high (percent, 0-100)
+# The high-water mark for AUFS/UFS/diskd cache object eviction by
+# the cache_replacement_policy algorithm.
+#
+# Removal begins when the swap (disk) usage of a cache_dir is
+# above the low-water mark set by cache_swap_low and attempts to
+# maintain utilization near the low-water mark.
+#
+# As swap utilization increases towards this high-water mark object
+# eviction becomes more agressive.
+#
+# The value difference in percentages between low- and high-water
+# marks represent an eviction rate of 300 objects per second and
+# the rate continues to scale in agressiveness by multiples of
+# this above the high-water mark.
+#
+# Defaults are 90% and 95%. If you have a large cache, 5% could be
+# hundreds of MB. If this is the case you may wish to set these
+# numbers closer together.
+#
+# See also cache_swap_low and cache_replacement_policy
+#Default:
+# cache_swap_high 95
+
+# LOGFILE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: logformat
+# Usage:
+#
+# logformat <name> <format specification>
+#
+# Defines an access log format.
+#
+# The <format specification> is a string with embedded % format codes
+#
+# % format codes all follow the same basic structure where all
+# components but the formatcode are optional and usually unnecessary,
+# especially when dealing with common codes.
+#
+# % [encoding] [-] [[0]width] [{arg}] formatcode [{arg}]
+#
+# encoding escapes or otherwise protects "special" characters:
+#
+# " Quoted string encoding where quote(") and
+# backslash(\) characters are \-escaped while
+# CR, LF, and TAB characters are encoded as \r,
+# \n, and \t two-character sequences.
+#
+# [ Custom Squid encoding where percent(%), square
+# brackets([]), backslash(\) and characters with
+# codes outside of [32,126] range are %-encoded.
+# SP is not encoded. Used by log_mime_hdrs.
+#
+# # URL encoding (a.k.a. percent-encoding) where
+# all URL unsafe and control characters (per RFC
+# 1738) are %-encoded.
+#
+# / Shell-like encoding where quote(") and
+# backslash(\) characters are \-escaped while CR
+# and LF characters are encoded as \r and \n
+# two-character sequences. Values containing SP
+# character(s) are surrounded by quotes(").
+#
+# ' Raw/as-is encoding with no escaping/quoting.
+#
+# Default encoding: When no explicit encoding is
+# specified, each %code determines its own encoding.
+# Most %codes use raw/as-is encoding, but some codes use
+# a so called "pass-through URL encoding" where all URL
+# unsafe and control characters (per RFC 1738) are
+# %-encoded, but the percent character(%) is left as is.
+#
+# - left aligned
+#
+# width minimum and/or maximum field width:
+# [width_min][.width_max]
+# When minimum starts with 0, the field is zero-padded.
+# String values exceeding maximum width are truncated.
+#
+# {arg} argument such as header name etc. This field may be
+# placed before or after the token, but not both at once.
+#
+# Format codes:
+#
+# % a literal % character
+# sn Unique sequence number per log line entry
+# err_code The ID of an error response served by Squid or
+# a similar internal error identifier.
+# err_detail Additional err_code-dependent error information.
+# note The annotation specified by the argument. Also
+# logs the adaptation meta headers set by the
+# adaptation_meta configuration parameter.
+# If no argument given all annotations logged.
+# The argument may include a separator to use with
+# annotation values:
+# name[:separator]
+# By default, multiple note values are separated with ","
+# and multiple notes are separated with "\r\n".
+# When logging named notes with %{name}note, the
+# explicitly configured separator is used between note
+# values. When logging all notes with %note, the
+# explicitly configured separator is used between
+# individual notes. There is currently no way to
+# specify both value and notes separators when logging
+# all notes with %note.
+#
+# Connection related format codes:
+#
+# >a Client source IP address
+# >A Client FQDN
+# >p Client source port
+# >eui Client source EUI (MAC address, EUI-48 or EUI-64 identifier)
+# >la Local IP address the client connected to
+# >lp Local port number the client connected to
+# >qos Client connection TOS/DSCP value set by Squid
+# >nfmark Client connection netfilter mark set by Squid
+#
+# la Local listening IP address the client connection was connected to.
+# lp Local listening port number the client connection was connected to.
+#
+# <a Server IP address of the last server or peer connection
+# <A Server FQDN or peer name
+# <p Server port number of the last server or peer connection
+# <la Local IP address of the last server or peer connection
+# <lp Local port number of the last server or peer connection
+# <qos Server connection TOS/DSCP value set by Squid
+# <nfmark Server connection netfilter mark set by Squid
+#
+# >handshake Raw client handshake
+# Initial client bytes received by Squid on a newly
+# accepted TCP connection or inside a just established
+# CONNECT tunnel. Squid stops accumulating handshake
+# bytes as soon as the handshake parser succeeds or
+# fails (determining whether the client is using the
+# expected protocol).
+#
+# For HTTP clients, the handshake is the request line.
+# For TLS clients, the handshake consists of all TLS
+# records up to and including the TLS record that
+# contains the last byte of the first ClientHello
+# message. For clients using an unsupported protocol,
+# this field contains the bytes received by Squid at the
+# time of the handshake parsing failure.
+#
+# See the on_unsupported_protocol directive for more
+# information on Squid handshake traffic expectations.
+#
+# Current support is limited to these contexts:
+# - http_port connections, but only when the
+# on_unsupported_protocol directive is in use.
+# - https_port connections (and CONNECT tunnels) that
+# are subject to the ssl_bump peek or stare action.
+#
+# To protect binary handshake data, this field is always
+# base64-encoded (RFC 4648 Section 4). If logformat
+# field encoding is configured, that encoding is applied
+# on top of base64. Otherwise, the computed base64 value
+# is recorded as is.
+#
+# Time related format codes:
+#
+# ts Seconds since epoch
+# tu subsecond time (milliseconds)
+# tl Local time. Optional strftime format argument
+# default %d/%b/%Y:%H:%M:%S %z
+# tg GMT time. Optional strftime format argument
+# default %d/%b/%Y:%H:%M:%S %z
+# tr Response time (milliseconds)
+# dt Total time spent making DNS lookups (milliseconds)
+# tS Approximate master transaction start time in
+# <full seconds since epoch>.<fractional seconds> format.
+# Currently, Squid considers the master transaction
+# started when a complete HTTP request header initiating
+# the transaction is received from the client. This is
+# the same value that Squid uses to calculate transaction
+# response time when logging %tr to access.log. Currently,
+# Squid uses millisecond resolution for %tS values,
+# similar to the default access.log "current time" field
+# (%ts.%03tu).
+#
+# Access Control related format codes:
+#
+# et Tag returned by external acl
+# ea Log string returned by external acl
+# un User name (any available)
+# ul User name from authentication
+# ue User name from external acl helper
+# ui User name from ident
+# un A user name. Expands to the first available name
+# from the following list of information sources:
+# - authenticated user name, like %ul
+# - user name supplied by an external ACL, like %ue
+# - SSL client name, like %us
+# - ident user name, like %ui
+# credentials Client credentials. The exact meaning depends on
+# the authentication scheme: For Basic authentication,
+# it is the password; for Digest, the realm sent by the
+# client; for NTLM and Negotiate, the client challenge
+# or client credentials prefixed with "YR " or "KK ".
+#
+# HTTP related format codes:
+#
+# REQUEST
+#
+# [http::]rm Request method (GET/POST etc)
+# [http::]>rm Request method from client
+# [http::]<rm Request method sent to server or peer
+#
+# [http::]ru Request URL received (or computed) and sanitized
+#
+# Logs request URI received from the client, a
+# request adaptation service, or a request
+# redirector (whichever was applied last).
+#
+# Computed URLs are URIs of internally generated
+# requests and various "error:..." URIs.
+#
+# Honors strip_query_terms and uri_whitespace.
+#
+# This field is not encoded by default. Encoding
+# this field using variants of %-encoding will
+# clash with uri_whitespace modifications that
+# also use %-encoding.
+#
+# [http::]>ru Request URL received from the client (or computed)
+#
+# Computed URLs are URIs of internally generated
+# requests and various "error:..." URIs.
+#
+# Unlike %ru, this request URI is not affected
+# by request adaptation, URL rewriting services,
+# and strip_query_terms.
+#
+# Honors uri_whitespace.
+#
+# This field is using pass-through URL encoding
+# by default. Encoding this field using other
+# variants of %-encoding will clash with
+# uri_whitespace modifications that also use
+# %-encoding.
+#
+# [http::]<ru Request URL sent to server or peer
+# [http::]>rs Request URL scheme from client
+# [http::]<rs Request URL scheme sent to server or peer
+# [http::]>rd Request URL domain from client
+# [http::]<rd Request URL domain sent to server or peer
+# [http::]>rP Request URL port from client
+# [http::]<rP Request URL port sent to server or peer
+# [http::]rp Request URL path excluding hostname
+# [http::]>rp Request URL path excluding hostname from client
+# [http::]<rp Request URL path excluding hostname sent to server or peer
+# [http::]rv Request protocol version
+# [http::]>rv Request protocol version from client
+# [http::]<rv Request protocol version sent to server or peer
+#
+# [http::]>h Original received request header.
+# Usually differs from the request header sent by
+# Squid, although most fields are often preserved.
+# Accepts optional header field name/value filter
+# argument using name[:[separator]element] format.
+# [http::]>ha Received request header after adaptation and
+# redirection (pre-cache REQMOD vectoring point).
+# Usually differs from the request header sent by
+# Squid, although most fields are often preserved.
+# Optional header name argument as for >h
+#
+# RESPONSE
+#
+# [http::]<Hs HTTP status code received from the next hop
+# [http::]>Hs HTTP status code sent to the client
+#
+# [http::]<h Reply header. Optional header name argument
+# as for >h
+#
+# [http::]mt MIME content type
+#
+#
+# SIZE COUNTERS
+#
+# [http::]st Total size of request + reply traffic with client
+# [http::]>st Total size of request received from client.
+# Excluding chunked encoding bytes.
+# [http::]<st Total size of reply sent to client (after adaptation)
+#
+# [http::]>sh Size of request headers received from client
+# [http::]<sh Size of reply headers sent to client (after adaptation)
+#
+# [http::]<sH Reply high offset sent
+# [http::]<sS Upstream object size
+#
+# [http::]<bs Number of HTTP-equivalent message body bytes
+# received from the next hop, excluding chunked
+# transfer encoding and control messages.
+# Generated FTP/Gopher listings are treated as
+# received bodies.
+#
+# TIMING
+#
+# [http::]<pt Peer response time in milliseconds. The timer starts
+# when the last request byte is sent to the next hop
+# and stops when the last response byte is received.
+# [http::]<tt Total time in milliseconds. The timer
+# starts with the first connect request (or write I/O)
+# sent to the first selected peer. The timer stops
+# with the last I/O with the last peer.
+#
+# Squid handling related format codes:
+#
+# Ss Squid request status (TCP_MISS etc)
+# Sh Squid hierarchy status (DEFAULT_PARENT etc)
+#
+# SSL-related format codes:
+#
+# ssl::bump_mode SslBump decision for the transaction:
+#
+# For CONNECT requests that initiated bumping of
+# a connection and for any request received on
+# an already bumped connection, Squid logs the
+# corresponding SslBump mode ("splice", "bump",
+# "peek", "stare", "terminate", "server-first"
+# or "client-first"). See the ssl_bump option
+# for more information about these modes.
+#
+# A "none" token is logged for requests that
+# triggered "ssl_bump" ACL evaluation matching
+# a "none" rule.
+#
+# In all other cases, a single dash ("-") is
+# logged.
+#
+# ssl::>sni SSL client SNI sent to Squid.
+#
+# ssl::>cert_subject
+# The Subject field of the received client
+# SSL certificate or a dash ('-') if Squid has
+# received an invalid/malformed certificate or
+# no certificate at all. Consider encoding the
+# logged value because Subject often has spaces.
+#
+# ssl::>cert_issuer
+# The Issuer field of the received client
+# SSL certificate or a dash ('-') if Squid has
+# received an invalid/malformed certificate or
+# no certificate at all. Consider encoding the
+# logged value because Issuer often has spaces.
+#
+# ssl::<cert_subject
+# The Subject field of the received server
+# TLS certificate or a dash ('-') if this is
+# not available. Consider encoding the logged
+# value because Subject often has spaces.
+#
+# ssl::<cert_issuer
+# The Issuer field of the received server
+# TLS certificate or a dash ('-') if this is
+# not available. Consider encoding the logged
+# value because Issuer often has spaces.
+#
+# ssl::<cert_errors
+# The list of certificate validation errors
+# detected by Squid (including OpenSSL and
+# certificate validation helper components). The
+# errors are listed in the discovery order. By
+# default, the error codes are separated by ':'.
+# Accepts an optional separator argument.
+#
+# %ssl::>negotiated_version The negotiated TLS version of the
+# client connection.
+#
+# %ssl::<negotiated_version The negotiated TLS version of the
+# last server or peer connection.
+#
+# %ssl::>received_hello_version The TLS version of the Hello
+# message received from TLS client.
+#
+# %ssl::<received_hello_version The TLS version of the Hello
+# message received from TLS server.
+#
+# %ssl::>received_supported_version The maximum TLS version
+# supported by the TLS client.
+#
+# %ssl::<received_supported_version The maximum TLS version
+# supported by the TLS server.
+#
+# %ssl::>negotiated_cipher The negotiated cipher of the
+# client connection.
+#
+# %ssl::<negotiated_cipher The negotiated cipher of the
+# last server or peer connection.
+#
+# If ICAP is enabled, the following code becomes available (as
+# well as ICAP log codes documented with the icap_log option):
+#
+# icap::tt Total ICAP processing time for the HTTP
+# transaction. The timer ticks when ICAP
+# ACLs are checked and when ICAP
+# transaction is in progress.
+#
+# If adaptation is enabled the following codes become available:
+#
+# adapt::<last_h The header of the last ICAP response or
+# meta-information from the last eCAP
+# transaction related to the HTTP transaction.
+# Like <h, accepts an optional header name
+# argument.
+#
+# adapt::sum_trs Summed adaptation transaction response
+# times recorded as a comma-separated list in
+# the order of transaction start time. Each time
+# value is recorded as an integer number,
+# representing response time of one or more
+# adaptation (ICAP or eCAP) transaction in
+# milliseconds. When a failed transaction is
+# being retried or repeated, its time is not
+# logged individually but added to the
+# replacement (next) transaction. See also:
+# adapt::all_trs.
+#
+# adapt::all_trs All adaptation transaction response times.
+# Same as adaptation_strs but response times of
+# individual transactions are never added
+# together. Instead, all transaction response
+# times are recorded individually.
+#
+# You can prefix adapt::*_trs format codes with adaptation
+# service name in curly braces to record response time(s) specific
+# to that service. For example: %{my_service}adapt::sum_trs
+#
+# The default formats available (which do not need re-defining) are:
+#
+#logformat squid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt
+#logformat common %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st %Ss:%Sh
+#logformat combined %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st "%{Referer}>h" "%{User-Agent}>h" %Ss:%Sh
+#logformat referrer %ts.%03tu %>a %{Referer}>h %ru
+#logformat useragent %>a [%tl] "%{User-Agent}>h"
+#
+# NOTE: When the log_mime_hdrs directive is set to ON.
+# The squid, common and combined formats have a safely encoded copy
+# of the mime headers appended to each line within a pair of brackets.
+#
+# NOTE: The common and combined formats are not quite true to the Apache definition.
+# The logs from Squid contain an extra status and hierarchy code appended.
+#
+#Default:
+# The format definitions squid, common, combined, referrer, useragent are built in.
+
+# TAG: access_log
+# Configures whether and how Squid logs HTTP and ICP transactions.
+# If access logging is enabled, a single line is logged for every
+# matching HTTP or ICP request. The recommended directive formats are:
+#
+# access_log <module>:<place> [option ...] [acl acl ...]
+# access_log none [acl acl ...]
+#
+# The following directive format is accepted but may be deprecated:
+# access_log <module>:<place> [<logformat name> [acl acl ...]]
+#
+# In most cases, the first ACL name must not contain the '=' character
+# and should not be equal to an existing logformat name. You can always
+# start with an 'all' ACL to work around those restrictions.
+#
+# Will log to the specified module:place using the specified format (which
+# must be defined in a logformat directive) those entries which match
+# ALL the acl's specified (which must be defined in acl clauses).
+# If no acl is specified, all requests will be logged to this destination.
+#
+# ===== Available options for the recommended directive format =====
+#
+# logformat=name Names log line format (either built-in or
+# defined by a logformat directive). Defaults
+# to 'squid'.
+#
+# buffer-size=64KB Defines approximate buffering limit for log
+# records (see buffered_logs). Squid should not
+# keep more than the specified size and, hence,
+# should flush records before the buffer becomes
+# full to avoid overflows under normal
+# conditions (the exact flushing algorithm is
+# module-dependent though). The on-error option
+# controls overflow handling.
+#
+# on-error=die|drop Defines action on unrecoverable errors. The
+# 'drop' action ignores (i.e., does not log)
+# affected log records. The default 'die' action
+# kills the affected worker. The drop action
+# support has not been tested for modules other
+# than tcp.
+#
+# rotate=N Specifies the number of log file rotations to
+# make when you run 'squid -k rotate'. The default
+# is to obey the logfile_rotate directive. Setting
+# rotate=0 will disable the file name rotation,
+# but the log files are still closed and re-opened.
+# This will enable you to rename the logfiles
+# yourself just before sending the rotate signal.
+# Only supported by the stdio module.
+#
+# ===== Modules Currently available =====
+#
+# none Do not log any requests matching these ACL.
+# Do not specify Place or logformat name.
+#
+# stdio Write each log line to disk immediately at the completion of
+# each request.
+# Place: the filename and path to be written.
+#
+# daemon Very similar to stdio. But instead of writing to disk the log
+# line is passed to a daemon helper for asychronous handling instead.
+# Place: varies depending on the daemon.
+#
+# log_file_daemon Place: the file name and path to be written.
+#
+# syslog To log each request via syslog facility.
+# Place: The syslog facility and priority level for these entries.
+# Place Format: facility.priority
+#
+# where facility could be any of:
+# authpriv, daemon, local0 ... local7 or user.
+#
+# And priority could be any of:
+# err, warning, notice, info, debug.
+#
+# udp To send each log line as text data to a UDP receiver.
+# Place: The destination host name or IP and port.
+# Place Format: //host:port
+#
+# tcp To send each log line as text data to a TCP receiver.
+# Lines may be accumulated before sending (see buffered_logs).
+# Place: The destination host name or IP and port.
+# Place Format: //host:port
+#
+# Default:
+# access_log daemon:/var/log/squid/access.log squid
+#Default:
+# access_log daemon:/var/log/squid/access.log squid
+
+# TAG: icap_log
+# ICAP log files record ICAP transaction summaries, one line per
+# transaction.
+#
+# The icap_log option format is:
+# icap_log <filepath> [<logformat name> [acl acl ...]]
+# icap_log none [acl acl ...]]
+#
+# Please see access_log option documentation for details. The two
+# kinds of logs share the overall configuration approach and many
+# features.
+#
+# ICAP processing of a single HTTP message or transaction may
+# require multiple ICAP transactions. In such cases, multiple
+# ICAP transaction log lines will correspond to a single access
+# log line.
+#
+# ICAP log supports many access.log logformat %codes. In ICAP context,
+# HTTP message-related %codes are applied to the HTTP message embedded
+# in an ICAP message. Logformat "%http::>..." codes are used for HTTP
+# messages embedded in ICAP requests while "%http::<..." codes are used
+# for HTTP messages embedded in ICAP responses. For example:
+#
+# http::>h To-be-adapted HTTP message headers sent by Squid to
+# the ICAP service. For REQMOD transactions, these are
+# HTTP request headers. For RESPMOD, these are HTTP
+# response headers, but Squid currently cannot log them
+# (i.e., %http::>h will expand to "-" for RESPMOD).
+#
+# http::<h Adapted HTTP message headers sent by the ICAP
+# service to Squid (i.e., HTTP request headers in regular
+# REQMOD; HTTP response headers in RESPMOD and during
+# request satisfaction in REQMOD).
+#
+# ICAP OPTIONS transactions do not embed HTTP messages.
+#
+# Several logformat codes below deal with ICAP message bodies. An ICAP
+# message body, if any, typically includes a complete HTTP message
+# (required HTTP headers plus optional HTTP message body). When
+# computing HTTP message body size for these logformat codes, Squid
+# either includes or excludes chunked encoding overheads; see
+# code-specific documentation for details.
+#
+# For Secure ICAP services, all size-related information is currently
+# computed before/after TLS encryption/decryption, as if TLS was not
+# in use at all.
+#
+# The following format codes are also available for ICAP logs:
+#
+# icap::<A ICAP server IP address. Similar to <A.
+#
+# icap::<service_name ICAP service name from the icap_service
+# option in Squid configuration file.
+#
+# icap::ru ICAP Request-URI. Similar to ru.
+#
+# icap::rm ICAP request method (REQMOD, RESPMOD, or
+# OPTIONS). Similar to existing rm.
+#
+# icap::>st The total size of the ICAP request sent to the ICAP
+# server (ICAP headers + ICAP body), including chunking
+# metadata (if any).
+#
+# icap::<st The total size of the ICAP response received from the
+# ICAP server (ICAP headers + ICAP body), including
+# chunking metadata (if any).
+#
+# icap::<bs The size of the ICAP response body received from the
+# ICAP server, excluding chunking metadata (if any).
+#
+# icap::tr Transaction response time (in
+# milliseconds). The timer starts when
+# the ICAP transaction is created and
+# stops when the transaction is completed.
+# Similar to tr.
+#
+# icap::tio Transaction I/O time (in milliseconds). The
+# timer starts when the first ICAP request
+# byte is scheduled for sending. The timers
+# stops when the last byte of the ICAP response
+# is received.
+#
+# icap::to Transaction outcome: ICAP_ERR* for all
+# transaction errors, ICAP_OPT for OPTION
+# transactions, ICAP_ECHO for 204
+# responses, ICAP_MOD for message
+# modification, and ICAP_SAT for request
+# satisfaction. Similar to Ss.
+#
+# icap::Hs ICAP response status code. Similar to Hs.
+#
+# icap::>h ICAP request header(s). Similar to >h.
+#
+# icap::<h ICAP response header(s). Similar to <h.
+#
+# The default ICAP log format, which can be used without an explicit
+# definition, is called icap_squid:
+#
+#logformat icap_squid %ts.%03tu %6icap::tr %>A %icap::to/%03icap::Hs %icap::<st %icap::rm %icap::ru %un -/%icap::<A -
+#
+# See also: logformat and %adapt::<last_h
+#Default:
+# none
+
+# TAG: logfile_daemon
+# Specify the path to the logfile-writing daemon. This daemon is
+# used to write the access and store logs, if configured.
+#
+# Squid sends a number of commands to the log daemon:
+# L<data>\n - logfile data
+# R\n - rotate file
+# T\n - truncate file
+# O\n - reopen file
+# F\n - flush file
+# r<n>\n - set rotate count to <n>
+# b<n>\n - 1 = buffer output, 0 = don't buffer output
+#
+# No responses is expected.
+#Default:
+# logfile_daemon /usr/lib/squid/log_file_daemon
+
+# TAG: stats_collection allow|deny acl acl...
+# This options allows you to control which requests gets accounted
+# in performance counters.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow logging for all transactions.
+
+# TAG: cache_store_log
+# Logs the activities of the storage manager. Shows which
+# objects are ejected from the cache, and which objects are
+# saved and for how long.
+# There are not really utilities to analyze this data, so you can safely
+# disable it (the default).
+#
+# Store log uses modular logging outputs. See access_log for the list
+# of modules supported.
+#
+# Example:
+# cache_store_log stdio:/var/log/squid/store.log
+# cache_store_log daemon:/var/log/squid/store.log
+#Default:
+# none
+
+# TAG: cache_swap_state
+# Location for the cache "swap.state" file. This index file holds
+# the metadata of objects saved on disk. It is used to rebuild
+# the cache during startup. Normally this file resides in each
+# 'cache_dir' directory, but you may specify an alternate
+# pathname here. Note you must give a full filename, not just
+# a directory. Since this is the index for the whole object
+# list you CANNOT periodically rotate it!
+#
+# If %s can be used in the file name it will be replaced with a
+# a representation of the cache_dir name where each / is replaced
+# with '.'. This is needed to allow adding/removing cache_dir
+# lines when cache_swap_log is being used.
+#
+# If have more than one 'cache_dir', and %s is not used in the name
+# these swap logs will have names such as:
+#
+# cache_swap_log.00
+# cache_swap_log.01
+# cache_swap_log.02
+#
+# The numbered extension (which is added automatically)
+# corresponds to the order of the 'cache_dir' lines in this
+# configuration file. If you change the order of the 'cache_dir'
+# lines in this file, these index files will NOT correspond to
+# the correct 'cache_dir' entry (unless you manually rename
+# them). We recommend you do NOT use this option. It is
+# better to keep these index files in each 'cache_dir' directory.
+#Default:
+# Store the journal inside its cache_dir
+
+# TAG: logfile_rotate
+# Specifies the default number of logfile rotations to make when you
+# type 'squid -k rotate'. The default is 10, which will rotate
+# with extensions 0 through 9. Setting logfile_rotate to 0 will
+# disable the file name rotation, but the logfiles are still closed
+# and re-opened. This will enable you to rename the logfiles
+# yourself just before sending the rotate signal.
+#
+# Note, from Squid-3.1 this option is only a default for cache.log,
+# that log can be rotated separately by using debug_options.
+#
+# Note, from Squid-4 this option is only a default for access.log
+# recorded by stdio: module. Those logs can be rotated separately by
+# using the rotate=N option on their access_log directive.
+#
+# Note, the 'squid -k rotate' command normally sends a USR1
+# signal to the running squid process. In certain situations
+# (e.g. on Linux with Async I/O), USR1 is used for other
+# purposes, so -k rotate uses another signal. It is best to get
+# in the habit of using 'squid -k rotate' instead of 'kill -USR1
+# <pid>'.
+#
+# Note, for Debian/Linux the default of logfile_rotate is
+# zero, since it includes external logfile-rotation methods.
+#Default:
+# logfile_rotate 0
+
+# TAG: mime_table
+# Path to Squid's icon configuration file.
+#
+# You shouldn't need to change this, but the default file contains
+# examples and formatting information if you do.
+#Default:
+# mime_table /usr/share/squid/mime.conf
+
+# TAG: log_mime_hdrs on|off
+# The Cache can record both the request and the response MIME
+# headers for each HTTP transaction. The headers are encoded
+# safely and will appear as two bracketed fields at the end of
+# the access log (for either the native or httpd-emulated log
+# formats). To enable this logging set log_mime_hdrs to 'on'.
+#Default:
+# log_mime_hdrs off
+
+# TAG: pid_filename
+# A filename to write the process-id to. To disable, enter "none".
+#Default:
+# pid_filename /var/run/squid.pid
+
+# TAG: client_netmask
+# A netmask for client addresses in logfiles and cachemgr output.
+# Change this to protect the privacy of your cache clients.
+# A netmask of 255.255.255.0 will log all IP's in that range with
+# the last digit set to '0'.
+#Default:
+# Log full client IP address
+
+# TAG: strip_query_terms
+# By default, Squid strips query terms from requested URLs before
+# logging. This protects your user's privacy and reduces log size.
+#
+# When investigating HIT/MISS or other caching behaviour you
+# will need to disable this to see the full URL used by Squid.
+#Default:
+# strip_query_terms on
+
+# TAG: buffered_logs on|off
+# Whether to write/send access_log records ASAP or accumulate them and
+# then write/send them in larger chunks. Buffering may improve
+# performance because it decreases the number of I/Os. However,
+# buffering increases the delay before log records become available to
+# the final recipient (e.g., a disk file or logging daemon) and,
+# hence, increases the risk of log records loss.
+#
+# Note that even when buffered_logs are off, Squid may have to buffer
+# records if it cannot write/send them immediately due to pending I/Os
+# (e.g., the I/O writing the previous log record) or connectivity loss.
+#
+# Currently honored by 'daemon' and 'tcp' access_log modules only.
+#Default:
+# buffered_logs off
+
+# TAG: netdb_filename
+# Where Squid stores it's netdb journal.
+# When enabled this journal preserves netdb state between restarts.
+#
+# To disable, enter "none".
+#Default:
+# netdb_filename stdio:/var/spool/squid/netdb.state
+
+# OPTIONS FOR TROUBLESHOOTING
+# -----------------------------------------------------------------------------
+
+# TAG: cache_log
+# Squid administrative logging file.
+#
+# This is where general information about Squid behavior goes. You can
+# increase the amount of data logged to this file and how often it is
+# rotated with "debug_options"
+#Default:
+# cache_log /var/log/squid/cache.log
+
+# TAG: debug_options
+# Logging options are set as section,level where each source file
+# is assigned a unique section. Lower levels result in less
+# output, Full debugging (level 9) can result in a very large
+# log file, so be careful.
+#
+# The magic word "ALL" sets debugging levels for all sections.
+# The default is to run with "ALL,1" to record important warnings.
+#
+# The rotate=N option can be used to keep more or less of these logs
+# than would otherwise be kept by logfile_rotate.
+# For most uses a single log should be enough to monitor current
+# events affecting Squid.
+#Default:
+# Log all critical and important messages.
+
+# TAG: coredump_dir
+# By default Squid leaves core files in the directory from where
+# it was started. If you set 'coredump_dir' to a directory
+# that exists, Squid will chdir() to that directory at startup
+# and coredump files will be left there.
+#
+#Default:
+# Use the directory from where Squid was started.
+#
+
+# Leave coredumps in the first cache dir
+coredump_dir /var/spool/squid
+
+# OPTIONS FOR FTP GATEWAYING
+# -----------------------------------------------------------------------------
+
+# TAG: ftp_user
+# If you want the anonymous login password to be more informative
+# (and enable the use of picky FTP servers), set this to something
+# reasonable for your domain, like wwwuser@somewhere.net
+#
+# The reason why this is domainless by default is the
+# request can be made on the behalf of a user in any domain,
+# depending on how the cache is used.
+# Some FTP server also validate the email address is valid
+# (for example perl.com).
+#Default:
+# ftp_user Squid@
+
+# TAG: ftp_passive
+# If your firewall does not allow Squid to use passive
+# connections, turn off this option.
+#
+# Use of ftp_epsv_all option requires this to be ON.
+#Default:
+# ftp_passive on
+
+# TAG: ftp_epsv_all
+# FTP Protocol extensions permit the use of a special "EPSV ALL" command.
+#
+# NATs may be able to put the connection on a "fast path" through the
+# translator, as the EPRT command will never be used and therefore,
+# translation of the data portion of the segments will never be needed.
+#
+# When a client only expects to do two-way FTP transfers this may be
+# useful.
+# If squid finds that it must do a three-way FTP transfer after issuing
+# an EPSV ALL command, the FTP session will fail.
+#
+# If you have any doubts about this option do not use it.
+# Squid will nicely attempt all other connection methods.
+#
+# Requires ftp_passive to be ON (default) for any effect.
+#Default:
+# ftp_epsv_all off
+
+# TAG: ftp_epsv
+# FTP Protocol extensions permit the use of a special "EPSV" command.
+#
+# NATs may be able to put the connection on a "fast path" through the
+# translator using EPSV, as the EPRT command will never be used
+# and therefore, translation of the data portion of the segments
+# will never be needed.
+#
+# EPSV is often required to interoperate with FTP servers on IPv6
+# networks. On the other hand, it may break some IPv4 servers.
+#
+# By default, EPSV may try EPSV with any FTP server. To fine tune
+# that decision, you may restrict EPSV to certain clients or servers
+# using ACLs:
+#
+# ftp_epsv allow|deny al1 acl2 ...
+#
+# WARNING: Disabling EPSV may cause problems with external NAT and IPv6.
+#
+# Only fast ACLs are supported.
+# Requires ftp_passive to be ON (default) for any effect.
+#Default:
+# none
+
+# TAG: ftp_eprt
+# FTP Protocol extensions permit the use of a special "EPRT" command.
+#
+# This extension provides a protocol neutral alternative to the
+# IPv4-only PORT command. When supported it enables active FTP data
+# channels over IPv6 and efficient NAT handling.
+#
+# Turning this OFF will prevent EPRT being attempted and will skip
+# straight to using PORT for IPv4 servers.
+#
+# Some devices are known to not handle this extension correctly and
+# may result in crashes. Devices which suport EPRT enough to fail
+# cleanly will result in Squid attempting PORT anyway. This directive
+# should only be disabled when EPRT results in device failures.
+#
+# WARNING: Doing so will convert Squid back to the old behavior with all
+# the related problems with external NAT devices/layers and IPv4-only FTP.
+#Default:
+# ftp_eprt on
+
+# TAG: ftp_sanitycheck
+# For security and data integrity reasons Squid by default performs
+# sanity checks of the addresses of FTP data connections ensure the
+# data connection is to the requested server. If you need to allow
+# FTP connections to servers using another IP address for the data
+# connection turn this off.
+#Default:
+# ftp_sanitycheck on
+
+# TAG: ftp_telnet_protocol
+# The FTP protocol is officially defined to use the telnet protocol
+# as transport channel for the control connection. However, many
+# implementations are broken and does not respect this aspect of
+# the FTP protocol.
+#
+# If you have trouble accessing files with ASCII code 255 in the
+# path or similar problems involving this ASCII code you can
+# try setting this directive to off. If that helps, report to the
+# operator of the FTP server in question that their FTP server
+# is broken and does not follow the FTP standard.
+#Default:
+# ftp_telnet_protocol on
+
+# OPTIONS FOR EXTERNAL SUPPORT PROGRAMS
+# -----------------------------------------------------------------------------
+
+# TAG: diskd_program
+# Specify the location of the diskd executable.
+# Note this is only useful if you have compiled in
+# diskd as one of the store io modules.
+#Default:
+# diskd_program /usr/lib/squid/diskd
+
+# TAG: unlinkd_program
+# Specify the location of the executable for file deletion process.
+#Default:
+# unlinkd_program /usr/lib/squid/unlinkd
+
+# TAG: pinger_program
+# Specify the location of the executable for the pinger process.
+#Default:
+# pinger_program /usr/lib/squid/pinger
+
+# TAG: pinger_enable
+# Control whether the pinger is active at run-time.
+# Enables turning ICMP pinger on and off with a simple
+# squid -k reconfigure.
+#Default:
+# pinger_enable on
+
+# OPTIONS FOR URL REWRITING
+# -----------------------------------------------------------------------------
+
+# TAG: url_rewrite_program
+# Specify the location of the executable URL rewriter to use.
+# Since they can perform almost any function there isn't one included.
+#
+# For each requested URL, the rewriter will receive on line with the format
+#
+# [channel-ID <SP>] URL [<SP> extras]<NL>
+#
+# See url_rewrite_extras on how to send "extras" with optional values to
+# the helper.
+# After processing the request the helper must reply using the following format:
+#
+# [channel-ID <SP>] result [<SP> kv-pairs]
+#
+# The result code can be:
+#
+# OK status=30N url="..."
+# Redirect the URL to the one supplied in 'url='.
+# 'status=' is optional and contains the status code to send
+# the client in Squids HTTP response. It must be one of the
+# HTTP redirect status codes: 301, 302, 303, 307, 308.
+# When no status is given Squid will use 302.
+#
+# OK rewrite-url="..."
+# Rewrite the URL to the one supplied in 'rewrite-url='.
+# The new URL is fetched directly by Squid and returned to
+# the client as the response to its request.
+#
+# OK
+# When neither of url= and rewrite-url= are sent Squid does
+# not change the URL.
+#
+# ERR
+# Do not change the URL.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified. The 'message=' key name is
+# reserved for delivering a log message.
+#
+#
+# In addition to the above kv-pairs Squid also understands the following
+# optional kv-pairs received from URL rewriters:
+# clt_conn_tag=TAG
+# Associates a TAG with the client TCP connection.
+# The TAG is treated as a regular annotation but persists across
+# future requests on the client connection rather than just the
+# current request. A helper may update the TAG during subsequent
+# requests be returning a new kv-pair.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+# WARNING: URL re-writing ability should be avoided whenever possible.
+# Use the URL redirect form of response instead.
+#
+# Re-write creates a difference in the state held by the client
+# and server. Possibly causing confusion when the server response
+# contains snippets of its view state. Embeded URLs, response
+# and content Location headers, etc. are not re-written by this
+# interface.
+#
+# By default, a URL rewriter is not used.
+#Default:
+# none
+
+# TAG: url_rewrite_children
+# Specifies the maximum number of redirector processes that Squid may
+# spawn (numberofchildren) and several related options. Using too few of
+# these helper processes (a.k.a. "helpers") creates request queues.
+# Using too many helpers wastes your system resources.
+#
+# Usage: numberofchildren [option]...
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=
+#
+# Sets a minimum of how many processes are to be spawned when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few will cause an initial slowdown in traffic as Squid
+# attempts to simultaneously spawn enough processes to cope.
+#
+# idle=
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each redirector helper can handle in
+# parallel. Defaults to 0 which indicates the redirector
+# is a old-style single threaded redirector.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# an ID in front of the request/response. The ID from the request
+# must be echoed back with the response to that request.
+#
+# queue-size=N
+#
+# Sets the maximum number of queued requests. A request is queued when
+# no existing child can accept it due to concurrency limit and no new
+# child can be started due to numberofchildren limit. The default
+# maximum is zero if url_rewrite_bypass is enabled and
+# 2*numberofchildren otherwise. If the queued requests exceed queue size
+# and redirector_bypass configuration option is set, then redirector is
+# bypassed. Otherwise, Squid is allowed to temporarily exceed the
+# configured maximum, marking the affected helper as "overloaded". If
+# the helper overload lasts more than 3 minutes, the action prescribed
+# by the on-persistent-overload option applies.
+#
+# on-persistent-overload=action
+#
+# Specifies Squid reaction to a new helper request arriving when the helper
+# has been overloaded for more that 3 minutes already. The number of queued
+# requests determines whether the helper is overloaded (see the queue-size
+# option).
+#
+# Two actions are supported:
+#
+# die Squid worker quits. This is the default behavior.
+#
+# ERR Squid treats the helper request as if it was
+# immediately submitted, and the helper immediately
+# replied with an ERR response. This action has no effect
+# on the already queued and in-progress helper requests.
+#Default:
+# url_rewrite_children 20 startup=0 idle=1 concurrency=0
+
+# TAG: url_rewrite_host_header
+# To preserve same-origin security policies in browsers and
+# prevent Host: header forgery by redirectors Squid rewrites
+# any Host: header in redirected requests.
+#
+# If you are running an accelerator this may not be a wanted
+# effect of a redirector. This directive enables you disable
+# Host: alteration in reverse-proxy traffic.
+#
+# WARNING: Entries are cached on the result of the URL rewriting
+# process, so be careful if you have domain-virtual hosts.
+#
+# WARNING: Squid and other software verifies the URL and Host
+# are matching, so be careful not to relay through other proxies
+# or inspecting firewalls with this disabled.
+#Default:
+# url_rewrite_host_header on
+
+# TAG: url_rewrite_access
+# If defined, this access list specifies which requests are
+# sent to the redirector processes.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: url_rewrite_bypass
+# When this is 'on', a request will not go through the
+# redirector if all the helpers are busy. If this is 'off' and the
+# redirector queue grows too large, the action is prescribed by the
+# on-persistent-overload option. You should only enable this if the
+# redirectors are not critical to your caching system. If you use
+# redirectors for access control, and you enable this option,
+# users may have access to pages they should not
+# be allowed to request.
+#
+# Enabling this option sets the default url_rewrite_children queue-size
+# option value to 0.
+#Default:
+# url_rewrite_bypass off
+
+# TAG: url_rewrite_extras
+# Specifies a string to be append to request line format for the
+# rewriter helper. "Quoted" format values may contain spaces and
+# logformat %macros. In theory, any logformat %macro can be used.
+# In practice, a %macro expands as a dash (-) if the helper request is
+# sent before the required macro information is available to Squid.
+#Default:
+# url_rewrite_extras "%>a/%>A %un %>rm myip=%la myport=%lp"
+
+# TAG: url_rewrite_timeout
+# Squid times active requests to redirector. The timeout value and Squid
+# reaction to a timed out request are configurable using the following
+# format:
+#
+# url_rewrite_timeout timeout time-units on_timeout=<action> [response=<quoted-response>]
+#
+# supported timeout actions:
+# fail Squid return a ERR_GATEWAY_FAILURE error page
+#
+# bypass Do not re-write the URL
+#
+# retry Send the lookup to the helper again
+#
+# use_configured_response
+# Use the <quoted-response> as helper response
+#Default:
+# Squid waits for the helper response forever
+
+# OPTIONS FOR STORE ID
+# -----------------------------------------------------------------------------
+
+# TAG: store_id_program
+# Specify the location of the executable StoreID helper to use.
+# Since they can perform almost any function there isn't one included.
+#
+# For each requested URL, the helper will receive one line with the format
+#
+# [channel-ID <SP>] URL [<SP> extras]<NL>
+#
+#
+# After processing the request the helper must reply using the following format:
+#
+# [channel-ID <SP>] result [<SP> kv-pairs]
+#
+# The result code can be:
+#
+# OK store-id="..."
+# Use the StoreID supplied in 'store-id='.
+#
+# ERR
+# The default is to use HTTP request URL as the store ID.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified.
+#
+# In addition to the above kv-pairs Squid also understands the following
+# optional kv-pairs received from URL rewriters:
+# clt_conn_tag=TAG
+# Associates a TAG with the client TCP connection.
+# Please see url_rewrite_program related documentation for this
+# kv-pair
+#
+# Helper programs should be prepared to receive and possibly ignore
+# additional whitespace-separated tokens on each input line.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+# NOTE: when using StoreID refresh_pattern will apply to the StoreID
+# returned from the helper and not the URL.
+#
+# WARNING: Wrong StoreID value returned by a careless helper may result
+# in the wrong cached response returned to the user.
+#
+# By default, a StoreID helper is not used.
+#Default:
+# none
+
+# TAG: store_id_extras
+# Specifies a string to be append to request line format for the
+# StoreId helper. "Quoted" format values may contain spaces and
+# logformat %macros. In theory, any logformat %macro can be used.
+# In practice, a %macro expands as a dash (-) if the helper request is
+# sent before the required macro information is available to Squid.
+#Default:
+# store_id_extras "%>a/%>A %un %>rm myip=%la myport=%lp"
+
+# TAG: store_id_children
+# Specifies the maximum number of StoreID helper processes that Squid
+# may spawn (numberofchildren) and several related options. Using
+# too few of these helper processes (a.k.a. "helpers") creates request
+# queues. Using too many helpers wastes your system resources.
+#
+# Usage: numberofchildren [option]...
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=
+#
+# Sets a minimum of how many processes are to be spawned when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few will cause an initial slowdown in traffic as Squid
+# attempts to simultaneously spawn enough processes to cope.
+#
+# idle=
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each storeID helper can handle in
+# parallel. Defaults to 0 which indicates the helper
+# is a old-style single threaded program.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# an ID in front of the request/response. The ID from the request
+# must be echoed back with the response to that request.
+#
+# queue-size=N
+#
+# Sets the maximum number of queued requests to N. A request is queued
+# when no existing child can accept it due to concurrency limit and no
+# new child can be started due to numberofchildren limit. The default
+# maximum is 2*numberofchildren. If the queued requests exceed queue
+# size and redirector_bypass configuration option is set, then
+# redirector is bypassed. Otherwise, Squid is allowed to temporarily
+# exceed the configured maximum, marking the affected helper as
+# "overloaded". If the helper overload lasts more than 3 minutes, the
+# action prescribed by the on-persistent-overload option applies.
+#
+# on-persistent-overload=action
+#
+# Specifies Squid reaction to a new helper request arriving when the helper
+# has been overloaded for more that 3 minutes already. The number of queued
+# requests determines whether the helper is overloaded (see the queue-size
+# option).
+#
+# Two actions are supported:
+#
+# die Squid worker quits. This is the default behavior.
+#
+# ERR Squid treats the helper request as if it was
+# immediately submitted, and the helper immediately
+# replied with an ERR response. This action has no effect
+# on the already queued and in-progress helper requests.
+#Default:
+# store_id_children 20 startup=0 idle=1 concurrency=0
+
+# TAG: store_id_access
+# If defined, this access list specifies which requests are
+# sent to the StoreID processes. By default all requests
+# are sent.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: store_id_bypass
+# When this is 'on', a request will not go through the
+# helper if all helpers are busy. If this is 'off' and the helper
+# queue grows too large, the action is prescribed by the
+# on-persistent-overload option. You should only enable this if the
+# helpers are not critical to your caching system. If you use
+# helpers for critical caching components, and you enable this
+# option, users may not get objects from cache.
+# This options sets default queue-size option of the store_id_children
+# to 0.
+#Default:
+# store_id_bypass on
+
+# OPTIONS FOR TUNING THE CACHE
+# -----------------------------------------------------------------------------
+
+# TAG: cache
+# Requests denied by this directive will not be served from the cache
+# and their responses will not be stored in the cache. This directive
+# has no effect on other transactions and on already cached responses.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# This and the two other similar caching directives listed below are
+# checked at different transaction processing stages, have different
+# access to response information, affect different cache operations,
+# and differ in slow ACLs support:
+#
+# * cache: Checked before Squid makes a hit/miss determination.
+# No access to reply information!
+# Denies both serving a hit and storing a miss.
+# Supports both fast and slow ACLs.
+# * send_hit: Checked after a hit was detected.
+# Has access to reply (hit) information.
+# Denies serving a hit only.
+# Supports fast ACLs only.
+# * store_miss: Checked before storing a cachable miss.
+# Has access to reply (miss) information.
+# Denies storing a miss only.
+# Supports fast ACLs only.
+#
+# If you are not sure which of the three directives to use, apply the
+# following decision logic:
+#
+# * If your ACL(s) are of slow type _and_ need response info, redesign.
+# Squid does not support that particular combination at this time.
+# Otherwise:
+# * If your directive ACL(s) are of slow type, use "cache"; and/or
+# * if your directive ACL(s) need no response info, use "cache".
+# Otherwise:
+# * If you do not want the response cached, use store_miss; and/or
+# * if you do not want a hit on a cached response, use send_hit.
+#Default:
+# By default, this directive is unused and has no effect.
+
+# TAG: send_hit
+# Responses denied by this directive will not be served from the cache
+# (but may still be cached, see store_miss). This directive has no
+# effect on the responses it allows and on the cached objects.
+#
+# Please see the "cache" directive for a summary of differences among
+# store_miss, send_hit, and cache directives.
+#
+# Unlike the "cache" directive, send_hit only supports fast acl
+# types. See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# For example:
+#
+# # apply custom Store ID mapping to some URLs
+# acl MapMe dstdomain .c.example.com
+# store_id_program ...
+# store_id_access allow MapMe
+#
+# # but prevent caching of special responses
+# # such as 302 redirects that cause StoreID loops
+# acl Ordinary http_status 200-299
+# store_miss deny MapMe !Ordinary
+#
+# # and do not serve any previously stored special responses
+# # from the cache (in case they were already cached before
+# # the above store_miss rule was in effect).
+# send_hit deny MapMe !Ordinary
+#Default:
+# By default, this directive is unused and has no effect.
+
+# TAG: store_miss
+# Responses denied by this directive will not be cached (but may still
+# be served from the cache, see send_hit). This directive has no
+# effect on the responses it allows and on the already cached responses.
+#
+# Please see the "cache" directive for a summary of differences among
+# store_miss, send_hit, and cache directives. See the
+# send_hit directive for a usage example.
+#
+# Unlike the "cache" directive, store_miss only supports fast acl
+# types. See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# By default, this directive is unused and has no effect.
+
+# TAG: max_stale time-units
+# This option puts an upper limit on how stale content Squid
+# will serve from the cache if cache validation fails.
+# Can be overriden by the refresh_pattern max-stale option.
+#Default:
+# max_stale 1 week
+
+# TAG: refresh_pattern
+# usage: refresh_pattern [-i] regex min percent max [options]
+#
+# By default, regular expressions are CASE-SENSITIVE. To make
+# them case-insensitive, use the -i option.
+#
+# 'Min' is the time (in minutes) an object without an explicit
+# expiry time should be considered fresh. The recommended
+# value is 0, any higher values may cause dynamic applications
+# to be erroneously cached unless the application designer
+# has taken the appropriate actions.
+#
+# 'Percent' is a percentage of the objects age (time since last
+# modification age) an object without explicit expiry time
+# will be considered fresh.
+#
+# 'Max' is an upper limit on how long objects without an explicit
+# expiry time will be considered fresh. The value is also used
+# to form Cache-Control: max-age header for a request sent from
+# Squid to origin/parent.
+#
+# options: override-expire
+# override-lastmod
+# reload-into-ims
+# ignore-reload
+# ignore-no-store
+# ignore-private
+# max-stale=NN
+# refresh-ims
+# store-stale
+#
+# override-expire enforces min age even if the server
+# sent an explicit expiry time (e.g., with the
+# Expires: header or Cache-Control: max-age). Doing this
+# VIOLATES the HTTP standard. Enabling this feature
+# could make you liable for problems which it causes.
+#
+# Note: override-expire does not enforce staleness - it only extends
+# freshness / min. If the server returns a Expires time which
+# is longer than your max time, Squid will still consider
+# the object fresh for that period of time.
+#
+# override-lastmod enforces min age even on objects
+# that were modified recently.
+#
+# reload-into-ims changes a client no-cache or ``reload''
+# request for a cached entry into a conditional request using
+# If-Modified-Since and/or If-None-Match headers, provided the
+# cached entry has a Last-Modified and/or a strong ETag header.
+# Doing this VIOLATES the HTTP standard. Enabling this feature
+# could make you liable for problems which it causes.
+#
+# ignore-reload ignores a client no-cache or ``reload''
+# header. Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which
+# it causes.
+#
+# ignore-no-store ignores any ``Cache-control: no-store''
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# ignore-private ignores any ``Cache-control: private''
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# refresh-ims causes squid to contact the origin server
+# when a client issues an If-Modified-Since request. This
+# ensures that the client will receive an updated version
+# if one is available.
+#
+# store-stale stores responses even if they don't have explicit
+# freshness or a validator (i.e., Last-Modified or an ETag)
+# present, or if they're already stale. By default, Squid will
+# not cache such responses because they usually can't be
+# reused. Note that such responses will be stale by default.
+#
+# max-stale=NN provide a maximum staleness factor. Squid won't
+# serve objects more stale than this even if it failed to
+# validate the object. Default: use the max_stale global limit.
+#
+# Basically a cached object is:
+#
+# FRESH if expire > now, else STALE
+# STALE if age > max
+# FRESH if lm-factor < percent, else STALE
+# FRESH if age < min
+# else STALE
+#
+# The refresh_pattern lines are checked in the order listed here.
+# The first entry which matches is used. If none of the entries
+# match the default will be used.
+#
+# Note, you must uncomment all the default lines if you want
+# to change one. The default setting is only active if none is
+# used.
+#
+#
+
+#
+# Add any of your own refresh_pattern entries above these.
+#
+refresh_pattern ^ftp: 1440 20% 10080
+refresh_pattern ^gopher: 1440 0% 1440
+refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
+refresh_pattern . 0 20% 4320
+
+# TAG: quick_abort_min (KB)
+#Default:
+# quick_abort_min 16 KB
+
+# TAG: quick_abort_max (KB)
+#Default:
+# quick_abort_max 16 KB
+
+# TAG: quick_abort_pct (percent)
+# The cache by default continues downloading aborted requests
+# which are almost completed (less than 16 KB remaining). This
+# may be undesirable on slow (e.g. SLIP) links and/or very busy
+# caches. Impatient users may tie up file descriptors and
+# bandwidth by repeatedly requesting and immediately aborting
+# downloads.
+#
+# When the user aborts a request, Squid will check the
+# quick_abort values to the amount of data transferred until
+# then.
+#
+# If the transfer has less than 'quick_abort_min' KB remaining,
+# it will finish the retrieval.
+#
+# If the transfer has more than 'quick_abort_max' KB remaining,
+# it will abort the retrieval.
+#
+# If more than 'quick_abort_pct' of the transfer has completed,
+# it will finish the retrieval.
+#
+# If you do not want any retrieval to continue after the client
+# has aborted, set both 'quick_abort_min' and 'quick_abort_max'
+# to '0 KB'.
+#
+# If you want retrievals to always continue if they are being
+# cached set 'quick_abort_min' to '-1 KB'.
+#Default:
+# quick_abort_pct 95
+
+# TAG: read_ahead_gap buffer-size
+# The amount of data the cache will buffer ahead of what has been
+# sent to the client when retrieving an object from another server.
+#Default:
+# read_ahead_gap 16 KB
+
+# TAG: negative_ttl time-units
+# Set the Default Time-to-Live (TTL) for failed requests.
+# Certain types of failures (such as "connection refused" and
+# "404 Not Found") are able to be negatively-cached for a short time.
+# Modern web servers should provide Expires: header, however if they
+# do not this can provide a minimum TTL.
+# The default is not to cache errors with unknown expiry details.
+#
+# Note that this is different from negative caching of DNS lookups.
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#Default:
+# negative_ttl 0 seconds
+
+# TAG: positive_dns_ttl time-units
+# Upper limit on how long Squid will cache positive DNS responses.
+# Default is 6 hours (360 minutes). This directive must be set
+# larger than negative_dns_ttl.
+#Default:
+# positive_dns_ttl 6 hours
+
+# TAG: negative_dns_ttl time-units
+# Time-to-Live (TTL) for negative caching of failed DNS lookups.
+# This also sets the lower cache limit on positive lookups.
+# Minimum value is 1 second, and it is not recommendable to go
+# much below 10 seconds.
+#Default:
+# negative_dns_ttl 1 minutes
+
+# TAG: range_offset_limit size [acl acl...]
+# usage: (size) [units] [[!]aclname]
+#
+# Sets an upper limit on how far (number of bytes) into the file
+# a Range request may be to cause Squid to prefetch the whole file.
+# If beyond this limit, Squid forwards the Range request as it is and
+# the result is NOT cached.
+#
+# This is to stop a far ahead range request (lets say start at 17MB)
+# from making Squid fetch the whole object up to that point before
+# sending anything to the client.
+#
+# Multiple range_offset_limit lines may be specified, and they will
+# be searched from top to bottom on each request until a match is found.
+# The first match found will be used. If no line matches a request, the
+# default limit of 0 bytes will be used.
+#
+# 'size' is the limit specified as a number of units.
+#
+# 'units' specifies whether to use bytes, KB, MB, etc.
+# If no units are specified bytes are assumed.
+#
+# A size of 0 causes Squid to never fetch more than the
+# client requested. (default)
+#
+# A size of 'none' causes Squid to always fetch the object from the
+# beginning so it may cache the result. (2.0 style)
+#
+# 'aclname' is the name of a defined ACL.
+#
+# NP: Using 'none' as the byte value here will override any quick_abort settings
+# that may otherwise apply to the range request. The range request will
+# be fully fetched from start to finish regardless of the client
+# actions. This affects bandwidth usage.
+#Default:
+# none
+
+# TAG: minimum_expiry_time (seconds)
+# The minimum caching time according to (Expires - Date)
+# headers Squid honors if the object can't be revalidated.
+# The default is 60 seconds.
+#
+# In reverse proxy environments it might be desirable to honor
+# shorter object lifetimes. It is most likely better to make
+# your server return a meaningful Last-Modified header however.
+#
+# In ESI environments where page fragments often have short
+# lifetimes, this will often be best set to 0.
+#Default:
+# minimum_expiry_time 60 seconds
+
+# TAG: store_avg_object_size (bytes)
+# Average object size, used to estimate number of objects your
+# cache can hold. The default is 13 KB.
+#
+# This is used to pre-seed the cache index memory allocation to
+# reduce expensive reallocate operations while handling clients
+# traffic. Too-large values may result in memory allocation during
+# peak traffic, too-small values will result in wasted memory.
+#
+# Check the cache manager 'info' report metrics for the real
+# object sizes seen by your Squid before tuning this.
+#Default:
+# store_avg_object_size 13 KB
+
+# TAG: store_objects_per_bucket
+# Target number of objects per bucket in the store hash table.
+# Lowering this value increases the total number of buckets and
+# also the storage maintenance rate. The default is 20.
+#Default:
+# store_objects_per_bucket 20
+
+# HTTP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: request_header_max_size (KB)
+# This specifies the maximum size for HTTP headers in a request.
+# Request headers are usually relatively small (about 512 bytes).
+# Placing a limit on the request header size will catch certain
+# bugs (for example with persistent connections) and possibly
+# buffer-overflow or denial-of-service attacks.
+#Default:
+# request_header_max_size 64 KB
+
+# TAG: reply_header_max_size (KB)
+# This specifies the maximum size for HTTP headers in a reply.
+# Reply headers are usually relatively small (about 512 bytes).
+# Placing a limit on the reply header size will catch certain
+# bugs (for example with persistent connections) and possibly
+# buffer-overflow or denial-of-service attacks.
+#Default:
+# reply_header_max_size 64 KB
+
+# TAG: request_body_max_size (bytes)
+# This specifies the maximum size for an HTTP request body.
+# In other words, the maximum size of a PUT/POST request.
+# A user who attempts to send a request with a body larger
+# than this limit receives an "Invalid Request" error message.
+# If you set this parameter to a zero (the default), there will
+# be no limit imposed.
+#
+# See also client_request_buffer_max_size for an alternative
+# limitation on client uploads which can be configured.
+#Default:
+# No limit.
+
+# TAG: client_request_buffer_max_size (bytes)
+# This specifies the maximum buffer size of a client request.
+# It prevents squid eating too much memory when somebody uploads
+# a large file.
+#Default:
+# client_request_buffer_max_size 512 KB
+
+# TAG: broken_posts
+# A list of ACL elements which, if matched, causes Squid to send
+# an extra CRLF pair after the body of a PUT/POST request.
+#
+# Some HTTP servers has broken implementations of PUT/POST,
+# and rely on an extra CRLF pair sent by some WWW clients.
+#
+# Quote from RFC2616 section 4.1 on this matter:
+#
+# Note: certain buggy HTTP/1.0 client implementations generate an
+# extra CRLF's after a POST request. To restate what is explicitly
+# forbidden by the BNF, an HTTP/1.1 client must not preface or follow
+# a request with an extra CRLF.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Example:
+# acl buggy_server url_regex ^http://....
+# broken_posts allow buggy_server
+#Default:
+# Obey RFC 2616.
+
+# TAG: adaptation_uses_indirect_client on|off
+# Controls whether the indirect client IP address (instead of the direct
+# client IP address) is passed to adaptation services.
+#
+# See also: follow_x_forwarded_for adaptation_send_client_ip
+#Default:
+# adaptation_uses_indirect_client on
+
+# TAG: via on|off
+# If set (default), Squid will include a Via header in requests and
+# replies as required by RFC2616.
+#Default:
+# via on
+
+# TAG: vary_ignore_expire on|off
+# Many HTTP servers supporting Vary gives such objects
+# immediate expiry time with no cache-control header
+# when requested by a HTTP/1.0 client. This option
+# enables Squid to ignore such expiry times until
+# HTTP/1.1 is fully implemented.
+#
+# WARNING: If turned on this may eventually cause some
+# varying objects not intended for caching to get cached.
+#Default:
+# vary_ignore_expire off
+
+# TAG: request_entities
+# Squid defaults to deny GET and HEAD requests with request entities,
+# as the meaning of such requests are undefined in the HTTP standard
+# even if not explicitly forbidden.
+#
+# Set this directive to on if you have clients which insists
+# on sending request entities in GET or HEAD requests. But be warned
+# that there is server software (both proxies and web servers) which
+# can fail to properly process this kind of request which may make you
+# vulnerable to cache pollution attacks if enabled.
+#Default:
+# request_entities off
+
+# TAG: request_header_access
+# Usage: request_header_access header_name allow|deny [!]aclname ...
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#
+# This option replaces the old 'anonymize_headers' and the
+# older 'http_anonymizer' option with something that is much
+# more configurable. A list of ACLs for each header name allows
+# removal of specific header fields under specific conditions.
+#
+# This option only applies to outgoing HTTP request headers (i.e.,
+# headers sent by Squid to the next HTTP hop such as a cache peer
+# or an origin server). The option has no effect during cache hit
+# detection. The equivalent adaptation vectoring point in ICAP
+# terminology is post-cache REQMOD.
+#
+# The option is applied to individual outgoing request header
+# fields. For each request header field F, Squid uses the first
+# qualifying sets of request_header_access rules:
+#
+# 1. Rules with header_name equal to F's name.
+# 2. Rules with header_name 'Other', provided F's name is not
+# on the hard-coded list of commonly used HTTP header names.
+# 3. Rules with header_name 'All'.
+#
+# Within that qualifying rule set, rule ACLs are checked as usual.
+# If ACLs of an "allow" rule match, the header field is allowed to
+# go through as is. If ACLs of a "deny" rule match, the header is
+# removed and request_header_replace is then checked to identify
+# if the removed header has a replacement. If no rules within the
+# set have matching ACLs, the header field is left as is.
+#
+# For example, to achieve the same behavior as the old
+# 'http_anonymizer standard' option, you should use:
+#
+# request_header_access From deny all
+# request_header_access Referer deny all
+# request_header_access User-Agent deny all
+#
+# Or, to reproduce the old 'http_anonymizer paranoid' feature
+# you should use:
+#
+# request_header_access Authorization allow all
+# request_header_access Proxy-Authorization allow all
+# request_header_access Cache-Control allow all
+# request_header_access Content-Length allow all
+# request_header_access Content-Type allow all
+# request_header_access Date allow all
+# request_header_access Host allow all
+# request_header_access If-Modified-Since allow all
+# request_header_access Pragma allow all
+# request_header_access Accept allow all
+# request_header_access Accept-Charset allow all
+# request_header_access Accept-Encoding allow all
+# request_header_access Accept-Language allow all
+# request_header_access Connection allow all
+# request_header_access All deny all
+#
+# HTTP reply headers are controlled with the reply_header_access directive.
+#
+# By default, all headers are allowed (no anonymizing is performed).
+#Default:
+# No limits.
+
+# TAG: reply_header_access
+# Usage: reply_header_access header_name allow|deny [!]aclname ...
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#
+# This option only applies to reply headers, i.e., from the
+# server to the client.
+#
+# This is the same as request_header_access, but in the other
+# direction. Please see request_header_access for detailed
+# documentation.
+#
+# For example, to achieve the same behavior as the old
+# 'http_anonymizer standard' option, you should use:
+#
+# reply_header_access Server deny all
+# reply_header_access WWW-Authenticate deny all
+# reply_header_access Link deny all
+#
+# Or, to reproduce the old 'http_anonymizer paranoid' feature
+# you should use:
+#
+# reply_header_access Allow allow all
+# reply_header_access WWW-Authenticate allow all
+# reply_header_access Proxy-Authenticate allow all
+# reply_header_access Cache-Control allow all
+# reply_header_access Content-Encoding allow all
+# reply_header_access Content-Length allow all
+# reply_header_access Content-Type allow all
+# reply_header_access Date allow all
+# reply_header_access Expires allow all
+# reply_header_access Last-Modified allow all
+# reply_header_access Location allow all
+# reply_header_access Pragma allow all
+# reply_header_access Content-Language allow all
+# reply_header_access Retry-After allow all
+# reply_header_access Title allow all
+# reply_header_access Content-Disposition allow all
+# reply_header_access Connection allow all
+# reply_header_access All deny all
+#
+# HTTP request headers are controlled with the request_header_access directive.
+#
+# By default, all headers are allowed (no anonymizing is
+# performed).
+#Default:
+# No limits.
+
+# TAG: request_header_replace
+# Usage: request_header_replace header_name message
+# Example: request_header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit)
+#
+# This option allows you to change the contents of headers
+# denied with request_header_access above, by replacing them
+# with some fixed string.
+#
+# This only applies to request headers, not reply headers.
+#
+# By default, headers are removed if denied.
+#Default:
+# none
+
+# TAG: reply_header_replace
+# Usage: reply_header_replace header_name message
+# Example: reply_header_replace Server Foo/1.0
+#
+# This option allows you to change the contents of headers
+# denied with reply_header_access above, by replacing them
+# with some fixed string.
+#
+# This only applies to reply headers, not request headers.
+#
+# By default, headers are removed if denied.
+#Default:
+# none
+
+# TAG: request_header_add
+# Usage: request_header_add field-name field-value [ acl ... ]
+# Example: request_header_add X-Client-CA "CA=%ssl::>cert_issuer" all
+#
+# This option adds header fields to outgoing HTTP requests (i.e.,
+# request headers sent by Squid to the next HTTP hop such as a
+# cache peer or an origin server). The option has no effect during
+# cache hit detection. The equivalent adaptation vectoring point
+# in ICAP terminology is post-cache REQMOD.
+#
+# Field-name is a token specifying an HTTP header name. If a
+# standard HTTP header name is used, Squid does not check whether
+# the new header conflicts with any existing headers or violates
+# HTTP rules. If the request to be modified already contains a
+# field with the same name, the old field is preserved but the
+# header field values are not merged.
+#
+# Field-value is either a token or a quoted string. If quoted
+# string format is used, then the surrounding quotes are removed
+# while escape sequences and %macros are processed.
+#
+# One or more Squid ACLs may be specified to restrict header
+# injection to matching requests. As always in squid.conf, all
+# ACLs in the ACL list must be satisfied for the insertion to
+# happen. The request_header_add supports fast ACLs only.
+#
+# See also: reply_header_add.
+#Default:
+# none
+
+# TAG: reply_header_add
+# Usage: reply_header_add field-name field-value [ acl ... ]
+# Example: reply_header_add X-Client-CA "CA=%ssl::>cert_issuer" all
+#
+# This option adds header fields to outgoing HTTP responses (i.e., response
+# headers delivered by Squid to the client). This option has no effect on
+# cache hit detection. The equivalent adaptation vectoring point in
+# ICAP terminology is post-cache RESPMOD. This option does not apply to
+# successful CONNECT replies.
+#
+# Field-name is a token specifying an HTTP header name. If a
+# standard HTTP header name is used, Squid does not check whether
+# the new header conflicts with any existing headers or violates
+# HTTP rules. If the response to be modified already contains a
+# field with the same name, the old field is preserved but the
+# header field values are not merged.
+#
+# Field-value is either a token or a quoted string. If quoted
+# string format is used, then the surrounding quotes are removed
+# while escape sequences and %macros are processed.
+#
+# One or more Squid ACLs may be specified to restrict header
+# injection to matching responses. As always in squid.conf, all
+# ACLs in the ACL list must be satisfied for the insertion to
+# happen. The reply_header_add option supports fast ACLs only.
+#
+# See also: request_header_add.
+#Default:
+# none
+
+# TAG: note
+# This option used to log custom information about the master
+# transaction. For example, an admin may configure Squid to log
+# which "user group" the transaction belongs to, where "user group"
+# will be determined based on a set of ACLs and not [just]
+# authentication information.
+# Values of key/value pairs can be logged using %{key}note macros:
+#
+# note key value acl ...
+# logformat myFormat ... %{key}note ...
+#Default:
+# none
+
+# TAG: relaxed_header_parser on|off|warn
+# In the default "on" setting Squid accepts certain forms
+# of non-compliant HTTP messages where it is unambiguous
+# what the sending application intended even if the message
+# is not correctly formatted. The messages is then normalized
+# to the correct form when forwarded by Squid.
+#
+# If set to "warn" then a warning will be emitted in cache.log
+# each time such HTTP error is encountered.
+#
+# If set to "off" then such HTTP errors will cause the request
+# or response to be rejected.
+#Default:
+# relaxed_header_parser on
+
+# TAG: collapsed_forwarding (on|off)
+# This option controls whether Squid is allowed to merge multiple
+# potentially cachable requests for the same URI before Squid knows
+# whether the response is going to be cachable.
+#
+# When enabled, instead of forwarding each concurrent request for
+# the same URL, Squid just sends the first of them. The other, so
+# called "collapsed" requests, wait for the response to the first
+# request and, if it happens to be cachable, use that response.
+# Here, "concurrent requests" means "received after the first
+# request headers were parsed and before the corresponding response
+# headers were parsed".
+#
+# This feature is disabled by default: enabling collapsed
+# forwarding needlessly delays forwarding requests that look
+# cachable (when they are collapsed) but then need to be forwarded
+# individually anyway because they end up being for uncachable
+# content. However, in some cases, such as acceleration of highly
+# cachable content with periodic or grouped expiration times, the
+# gains from collapsing [large volumes of simultaneous refresh
+# requests] outweigh losses from such delays.
+#
+# Squid collapses two kinds of requests: regular client requests
+# received on one of the listening ports and internal "cache
+# revalidation" requests which are triggered by those regular
+# requests hitting a stale cached object. Revalidation collapsing
+# is currently disabled for Squid instances containing SMP-aware
+# disk or memory caches and for Vary-controlled cached objects.
+#Default:
+# collapsed_forwarding off
+
+# TAG: collapsed_forwarding_shared_entries_limit (number of entries)
+# This limits the size of a table used for sharing information
+# about collapsible entries among SMP workers. Limiting sharing
+# too much results in cache content duplication and missed
+# collapsing opportunities. Using excessively large values
+# wastes shared memory.
+#
+# The limit should be significantly larger then the number of
+# concurrent collapsible entries one wants to share. For a cache
+# that handles less than 5000 concurrent requests, the default
+# setting of 16384 should be plenty.
+#
+# If the limit is set to zero, it disables sharing of collapsed
+# forwarding between SMP workers.
+#Default:
+# collapsed_forwarding_shared_entries_limit 16384
+
+# TIMEOUTS
+# -----------------------------------------------------------------------------
+
+# TAG: forward_timeout time-units
+# This parameter specifies how long Squid should at most attempt in
+# finding a forwarding path for the request before giving up.
+#Default:
+# forward_timeout 4 minutes
+
+# TAG: connect_timeout time-units
+# This parameter specifies how long to wait for the TCP connect to
+# the requested server or peer to complete before Squid should
+# attempt to find another path where to forward the request.
+#Default:
+# connect_timeout 1 minute
+
+# TAG: peer_connect_timeout time-units
+# This parameter specifies how long to wait for a pending TCP
+# connection to a peer cache. The default is 30 seconds. You
+# may also set different timeout values for individual neighbors
+# with the 'connect-timeout' option on a 'cache_peer' line.
+#Default:
+# peer_connect_timeout 30 seconds
+
+# TAG: read_timeout time-units
+# Applied on peer server connections.
+#
+# After each successful read(), the timeout will be extended by this
+# amount. If no data is read again after this amount of time,
+# the request is aborted and logged with ERR_READ_TIMEOUT.
+#
+# The default is 15 minutes.
+#Default:
+# read_timeout 15 minutes
+
+# TAG: write_timeout time-units
+# This timeout is tracked for all connections that have data
+# available for writing and are waiting for the socket to become
+# ready. After each successful write, the timeout is extended by
+# the configured amount. If Squid has data to write but the
+# connection is not ready for the configured duration, the
+# transaction associated with the connection is terminated. The
+# default is 15 minutes.
+#Default:
+# write_timeout 15 minutes
+
+# TAG: request_timeout
+# How long to wait for complete HTTP request headers after initial
+# connection establishment.
+#Default:
+# request_timeout 5 minutes
+
+# TAG: request_start_timeout
+# How long to wait for the first request byte after initial
+# connection establishment.
+#Default:
+# request_start_timeout 5 minutes
+
+# TAG: client_idle_pconn_timeout
+# How long to wait for the next HTTP request on a persistent
+# client connection after the previous request completes.
+#Default:
+# client_idle_pconn_timeout 2 minutes
+
+# TAG: ftp_client_idle_timeout
+# How long to wait for an FTP request on a connection to Squid ftp_port.
+# Many FTP clients do not deal with idle connection closures well,
+# necessitating a longer default timeout than client_idle_pconn_timeout
+# used for incoming HTTP requests.
+#Default:
+# ftp_client_idle_timeout 30 minutes
+
+# TAG: client_lifetime time-units
+# The maximum amount of time a client (browser) is allowed to
+# remain connected to the cache process. This protects the Cache
+# from having a lot of sockets (and hence file descriptors) tied up
+# in a CLOSE_WAIT state from remote clients that go away without
+# properly shutting down (either because of a network failure or
+# because of a poor client implementation). The default is one
+# day, 1440 minutes.
+#
+# NOTE: The default value is intended to be much larger than any
+# client would ever need to be connected to your cache. You
+# should probably change client_lifetime only as a last resort.
+# If you seem to have many client connections tying up
+# filedescriptors, we recommend first tuning the read_timeout,
+# request_timeout, persistent_request_timeout and quick_abort values.
+#Default:
+# client_lifetime 1 day
+
+# TAG: pconn_lifetime time-units
+# Desired maximum lifetime of a persistent connection.
+# When set, Squid will close a now-idle persistent connection that
+# exceeded configured lifetime instead of moving the connection into
+# the idle connection pool (or equivalent). No effect on ongoing/active
+# transactions. Connection lifetime is the time period from the
+# connection acceptance or opening time until "now".
+#
+# This limit is useful in environments with long-lived connections
+# where Squid configuration or environmental factors change during a
+# single connection lifetime. If unrestricted, some connections may
+# last for hours and even days, ignoring those changes that should
+# have affected their behavior or their existence.
+#
+# Currently, a new lifetime value supplied via Squid reconfiguration
+# has no effect on already idle connections unless they become busy.
+#
+# When set to '0' this limit is not used.
+#Default:
+# pconn_lifetime 0 seconds
+
+# TAG: half_closed_clients
+# Some clients may shutdown the sending side of their TCP
+# connections, while leaving their receiving sides open. Sometimes,
+# Squid can not tell the difference between a half-closed and a
+# fully-closed TCP connection.
+#
+# By default, Squid will immediately close client connections when
+# read(2) returns "no more data to read."
+#
+# Change this option to 'on' and Squid will keep open connections
+# until a read(2) or write(2) on the socket returns an error.
+# This may show some benefits for reverse proxies. But if not
+# it is recommended to leave OFF.
+#Default:
+# half_closed_clients off
+
+# TAG: server_idle_pconn_timeout
+# Timeout for idle persistent connections to servers and other
+# proxies.
+#Default:
+# server_idle_pconn_timeout 1 minute
+
+# TAG: ident_timeout
+# Maximum time to wait for IDENT lookups to complete.
+#
+# If this is too high, and you enabled IDENT lookups from untrusted
+# users, you might be susceptible to denial-of-service by having
+# many ident requests going at once.
+#Default:
+# ident_timeout 10 seconds
+
+# TAG: shutdown_lifetime time-units
+# When SIGTERM or SIGHUP is received, the cache is put into
+# "shutdown pending" mode until all active sockets are closed.
+# This value is the lifetime to set for all open descriptors
+# during shutdown mode. Any active clients after this many
+# seconds will receive a 'timeout' message.
+#Default:
+# shutdown_lifetime 30 seconds
+
+# ADMINISTRATIVE PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_mgr
+# Email-address of local cache manager who will receive
+# mail if the cache dies. The default is "webmaster".
+#Default:
+# cache_mgr webmaster
+
+# TAG: mail_from
+# From: email-address for mail sent when the cache dies.
+# The default is to use 'squid@unique_hostname'.
+#
+# See also: unique_hostname directive.
+#Default:
+# none
+
+# TAG: mail_program
+# Email program used to send mail if the cache dies.
+# The default is "mail". The specified program must comply
+# with the standard Unix mail syntax:
+# mail-program recipient < mailfile
+#
+# Optional command line options can be specified.
+#Default:
+# mail_program mail
+
+# TAG: cache_effective_user
+# If you start Squid as root, it will change its effective/real
+# UID/GID to the user specified below. The default is to change
+# to UID of proxy.
+# see also; cache_effective_group
+#Default:
+# cache_effective_user proxy
+
+# TAG: cache_effective_group
+# Squid sets the GID to the effective user's default group ID
+# (taken from the password file) and supplementary group list
+# from the groups membership.
+#
+# If you want Squid to run with a specific GID regardless of
+# the group memberships of the effective user then set this
+# to the group (or GID) you want Squid to run as. When set
+# all other group privileges of the effective user are ignored
+# and only this GID is effective. If Squid is not started as
+# root the user starting Squid MUST be member of the specified
+# group.
+#
+# This option is not recommended by the Squid Team.
+# Our preference is for administrators to configure a secure
+# user account for squid with UID/GID matching system policies.
+#Default:
+# Use system group memberships of the cache_effective_user account
+
+# TAG: httpd_suppress_version_string on|off
+# Suppress Squid version string info in HTTP headers and HTML error pages.
+#Default:
+# httpd_suppress_version_string off
+
+# TAG: visible_hostname
+# If you want to present a special hostname in error messages, etc,
+# define this. Otherwise, the return value of gethostname()
+# will be used. If you have multiple caches in a cluster and
+# get errors about IP-forwarding you must set them to have individual
+# names with this setting.
+#Default:
+# Automatically detect the system host name
+
+# TAG: unique_hostname
+# If you want to have multiple machines with the same
+# 'visible_hostname' you must give each machine a different
+# 'unique_hostname' so forwarding loops can be detected.
+#Default:
+# Copy the value from visible_hostname
+
+# TAG: hostname_aliases
+# A list of other DNS names your cache has.
+#Default:
+# none
+
+# TAG: umask
+# Minimum umask which should be enforced while the proxy
+# is running, in addition to the umask set at startup.
+#
+# For a traditional octal representation of umasks, start
+# your value with 0.
+#Default:
+# umask 027
+
+# OPTIONS FOR THE CACHE REGISTRATION SERVICE
+# -----------------------------------------------------------------------------
+#
+# This section contains parameters for the (optional) cache
+# announcement service. This service is provided to help
+# cache administrators locate one another in order to join or
+# create cache hierarchies.
+#
+# An 'announcement' message is sent (via UDP) to the registration
+# service by Squid. By default, the announcement message is NOT
+# SENT unless you enable it with 'announce_period' below.
+#
+# The announcement message includes your hostname, plus the
+# following information from this configuration file:
+#
+# http_port
+# icp_port
+# cache_mgr
+#
+# All current information is processed regularly and made
+# available on the Web at http://www.ircache.net/Cache/Tracker/.
+
+# TAG: announce_period
+# This is how frequently to send cache announcements.
+#
+# To enable announcing your cache, just set an announce period.
+#
+# Example:
+# announce_period 1 day
+#Default:
+# Announcement messages disabled.
+
+# TAG: announce_host
+# Set the hostname where announce registration messages will be sent.
+#
+# See also announce_port and announce_file
+#Default:
+# announce_host tracker.ircache.net
+
+# TAG: announce_file
+# The contents of this file will be included in the announce
+# registration messages.
+#Default:
+# none
+
+# TAG: announce_port
+# Set the port where announce registration messages will be sent.
+#
+# See also announce_host and announce_file
+#Default:
+# announce_port 3131
+
+# HTTPD-ACCELERATOR OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: httpd_accel_surrogate_id
+# Surrogates (http://www.esi.org/architecture_spec_1.0.html)
+# need an identification token to allow control targeting. Because
+# a farm of surrogates may all perform the same tasks, they may share
+# an identification token.
+#Default:
+# visible_hostname is used if no specific ID is set.
+
+# TAG: http_accel_surrogate_remote on|off
+# Remote surrogates (such as those in a CDN) honour the header
+# "Surrogate-Control: no-store-remote".
+#
+# Set this to on to have squid behave as a remote surrogate.
+#Default:
+# http_accel_surrogate_remote off
+
+# TAG: esi_parser libxml2|expat
+# Selects the XML parsing library to use when interpreting responses with
+# Edge Side Includes.
+#
+# To disable ESI handling completely, ./configure Squid with --disable-esi.
+#Default:
+# Selects libxml2 if available at ./configure time or libexpat otherwise.
+
+# DELAY POOL PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: delay_pools
+# This represents the number of delay pools to be used. For example,
+# if you have one class 2 delay pool and one class 3 delays pool, you
+# have a total of 2 delay pools.
+#
+# See also delay_parameters, delay_class, delay_access for pool
+# configuration details.
+#Default:
+# delay_pools 0
+
+# TAG: delay_class
+# This defines the class of each delay pool. There must be exactly one
+# delay_class line for each delay pool. For example, to define two
+# delay pools, one of class 2 and one of class 3, the settings above
+# and here would be:
+#
+# Example:
+# delay_pools 4 # 4 delay pools
+# delay_class 1 2 # pool 1 is a class 2 pool
+# delay_class 2 3 # pool 2 is a class 3 pool
+# delay_class 3 4 # pool 3 is a class 4 pool
+# delay_class 4 5 # pool 4 is a class 5 pool
+#
+# The delay pool classes are:
+#
+# class 1 Everything is limited by a single aggregate
+# bucket.
+#
+# class 2 Everything is limited by a single aggregate
+# bucket as well as an "individual" bucket chosen
+# from bits 25 through 32 of the IPv4 address.
+#
+# class 3 Everything is limited by a single aggregate
+# bucket as well as a "network" bucket chosen
+# from bits 17 through 24 of the IP address and a
+# "individual" bucket chosen from bits 17 through
+# 32 of the IPv4 address.
+#
+# class 4 Everything in a class 3 delay pool, with an
+# additional limit on a per user basis. This
+# only takes effect if the username is established
+# in advance - by forcing authentication in your
+# http_access rules.
+#
+# class 5 Requests are grouped according their tag (see
+# external_acl's tag= reply).
+#
+#
+# Each pool also requires a delay_parameters directive to configure the pool size
+# and speed limits used whenever the pool is applied to a request. Along with
+# a set of delay_access directives to determine when it is used.
+#
+# NOTE: If an IP address is a.b.c.d
+# -> bits 25 through 32 are "d"
+# -> bits 17 through 24 are "c"
+# -> bits 17 through 32 are "c * 256 + d"
+#
+# NOTE-2: Due to the use of bitmasks in class 2,3,4 pools they only apply to
+# IPv4 traffic. Class 1 and 5 pools may be used with IPv6 traffic.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# See also delay_parameters and delay_access.
+#Default:
+# none
+
+# TAG: delay_access
+# This is used to determine which delay pool a request falls into.
+#
+# delay_access is sorted per pool and the matching starts with pool 1,
+# then pool 2, ..., and finally pool N. The first delay pool where the
+# request is allowed is selected for the request. If it does not allow
+# the request to any pool then the request is not delayed (default).
+#
+# For example, if you want some_big_clients in delay
+# pool 1 and lotsa_little_clients in delay pool 2:
+#
+# delay_access 1 allow some_big_clients
+# delay_access 1 deny all
+# delay_access 2 allow lotsa_little_clients
+# delay_access 2 deny all
+# delay_access 3 allow authenticated_clients
+#
+# See also delay_parameters and delay_class.
+#
+#Default:
+# Deny using the pool, unless allow rules exist in squid.conf for the pool.
+
+# TAG: delay_parameters
+# This defines the parameters for a delay pool. Each delay pool has
+# a number of "buckets" associated with it, as explained in the
+# description of delay_class.
+#
+# For a class 1 delay pool, the syntax is:
+# delay_class pool 1
+# delay_parameters pool aggregate
+#
+# For a class 2 delay pool:
+# delay_class pool 2
+# delay_parameters pool aggregate individual
+#
+# For a class 3 delay pool:
+# delay_class pool 3
+# delay_parameters pool aggregate network individual
+#
+# For a class 4 delay pool:
+# delay_class pool 4
+# delay_parameters pool aggregate network individual user
+#
+# For a class 5 delay pool:
+# delay_class pool 5
+# delay_parameters pool tagrate
+#
+# The option variables are:
+#
+# pool a pool number - ie, a number between 1 and the
+# number specified in delay_pools as used in
+# delay_class lines.
+#
+# aggregate the speed limit parameters for the aggregate bucket
+# (class 1, 2, 3).
+#
+# individual the speed limit parameters for the individual
+# buckets (class 2, 3).
+#
+# network the speed limit parameters for the network buckets
+# (class 3).
+#
+# user the speed limit parameters for the user buckets
+# (class 4).
+#
+# tagrate the speed limit parameters for the tag buckets
+# (class 5).
+#
+# A pair of delay parameters is written restore/maximum, where restore is
+# the number of bytes (not bits - modem and network speeds are usually
+# quoted in bits) per second placed into the bucket, and maximum is the
+# maximum number of bytes which can be in the bucket at any time.
+#
+# There must be one delay_parameters line for each delay pool.
+#
+#
+# For example, if delay pool number 1 is a class 2 delay pool as in the
+# above example, and is being used to strictly limit each host to 64Kbit/sec
+# (plus overheads), with no overall limit, the line is:
+#
+# delay_parameters 1 none 8000/8000
+#
+# Note that 8 x 8K Byte/sec -> 64K bit/sec.
+#
+# Note that the word 'none' is used to represent no limit.
+#
+#
+# And, if delay pool number 2 is a class 3 delay pool as in the above
+# example, and you want to limit it to a total of 256Kbit/sec (strict limit)
+# with each 8-bit network permitted 64Kbit/sec (strict limit) and each
+# individual host permitted 4800bit/sec with a bucket maximum size of 64Kbits
+# to permit a decent web page to be downloaded at a decent speed
+# (if the network is not being limited due to overuse) but slow down
+# large downloads more significantly:
+#
+# delay_parameters 2 32000/32000 8000/8000 600/8000
+#
+# Note that 8 x 32K Byte/sec -> 256K bit/sec.
+# 8 x 8K Byte/sec -> 64K bit/sec.
+# 8 x 600 Byte/sec -> 4800 bit/sec.
+#
+#
+# Finally, for a class 4 delay pool as in the example - each user will
+# be limited to 128Kbits/sec no matter how many workstations they are logged into.:
+#
+# delay_parameters 4 32000/32000 8000/8000 600/64000 16000/16000
+#
+#
+# See also delay_class and delay_access.
+#
+#Default:
+# none
+
+# TAG: delay_initial_bucket_level (percent, 0-100)
+# The initial bucket percentage is used to determine how much is put
+# in each bucket when squid starts, is reconfigured, or first notices
+# a host accessing it (in class 2 and class 3, individual hosts and
+# networks only have buckets associated with them once they have been
+# "seen" by squid).
+#Default:
+# delay_initial_bucket_level 50
+
+# CLIENT DELAY POOL PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: client_delay_pools
+# This option specifies the number of client delay pools used. It must
+# preceed other client_delay_* options.
+#
+# Example:
+# client_delay_pools 2
+#
+# See also client_delay_parameters and client_delay_access.
+#Default:
+# client_delay_pools 0
+
+# TAG: client_delay_initial_bucket_level (percent, 0-no_limit)
+# This option determines the initial bucket size as a percentage of
+# max_bucket_size from client_delay_parameters. Buckets are created
+# at the time of the "first" connection from the matching IP. Idle
+# buckets are periodically deleted up.
+#
+# You can specify more than 100 percent but note that such "oversized"
+# buckets are not refilled until their size goes down to max_bucket_size
+# from client_delay_parameters.
+#
+# Example:
+# client_delay_initial_bucket_level 50
+#Default:
+# client_delay_initial_bucket_level 50
+
+# TAG: client_delay_parameters
+#
+# This option configures client-side bandwidth limits using the
+# following format:
+#
+# client_delay_parameters pool speed_limit max_bucket_size
+#
+# pool is an integer ID used for client_delay_access matching.
+#
+# speed_limit is bytes added to the bucket per second.
+#
+# max_bucket_size is the maximum size of a bucket, enforced after any
+# speed_limit additions.
+#
+# Please see the delay_parameters option for more information and
+# examples.
+#
+# Example:
+# client_delay_parameters 1 1024 2048
+# client_delay_parameters 2 51200 16384
+#
+# See also client_delay_access.
+#
+#Default:
+# none
+
+# TAG: client_delay_access
+# This option determines the client-side delay pool for the
+# request:
+#
+# client_delay_access pool_ID allow|deny acl_name
+#
+# All client_delay_access options are checked in their pool ID
+# order, starting with pool 1. The first checked pool with allowed
+# request is selected for the request. If no ACL matches or there
+# are no client_delay_access options, the request bandwidth is not
+# limited.
+#
+# The ACL-selected pool is then used to find the
+# client_delay_parameters for the request. Client-side pools are
+# not used to aggregate clients. Clients are always aggregated
+# based on their source IP addresses (one bucket per source IP).
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+# Additionally, only the client TCP connection details are available.
+# ACLs testing HTTP properties will not work.
+#
+# Please see delay_access for more examples.
+#
+# Example:
+# client_delay_access 1 allow low_rate_network
+# client_delay_access 2 allow vips_network
+#
+#
+# See also client_delay_parameters and client_delay_pools.
+#Default:
+# Deny use of the pool, unless allow rules exist in squid.conf for the pool.
+
+# WCCPv1 AND WCCPv2 CONFIGURATION OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: wccp_router
+# Use this option to define your WCCP ``home'' router for
+# Squid.
+#
+# wccp_router supports a single WCCP(v1) router
+#
+# wccp2_router supports multiple WCCPv2 routers
+#
+# only one of the two may be used at the same time and defines
+# which version of WCCP to use.
+#Default:
+# WCCP disabled.
+
+# TAG: wccp2_router
+# Use this option to define your WCCP ``home'' router for
+# Squid.
+#
+# wccp_router supports a single WCCP(v1) router
+#
+# wccp2_router supports multiple WCCPv2 routers
+#
+# only one of the two may be used at the same time and defines
+# which version of WCCP to use.
+#Default:
+# WCCPv2 disabled.
+
+# TAG: wccp_version
+# This directive is only relevant if you need to set up WCCP(v1)
+# to some very old and end-of-life Cisco routers. In all other
+# setups it must be left unset or at the default setting.
+# It defines an internal version in the WCCP(v1) protocol,
+# with version 4 being the officially documented protocol.
+#
+# According to some users, Cisco IOS 11.2 and earlier only
+# support WCCP version 3. If you're using that or an earlier
+# version of IOS, you may need to change this value to 3, otherwise
+# do not specify this parameter.
+#Default:
+# wccp_version 4
+
+# TAG: wccp2_rebuild_wait
+# If this is enabled Squid will wait for the cache dir rebuild to finish
+# before sending the first wccp2 HereIAm packet
+#Default:
+# wccp2_rebuild_wait on
+
+# TAG: wccp2_forwarding_method
+# WCCP2 allows the setting of forwarding methods between the
+# router/switch and the cache. Valid values are as follows:
+#
+# gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
+# l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
+#
+# Currently (as of IOS 12.4) cisco routers only support GRE.
+# Cisco switches only support the L2 redirect assignment method.
+#Default:
+# wccp2_forwarding_method gre
+
+# TAG: wccp2_return_method
+# WCCP2 allows the setting of return methods between the
+# router/switch and the cache for packets that the cache
+# decides not to handle. Valid values are as follows:
+#
+# gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
+# l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
+#
+# Currently (as of IOS 12.4) cisco routers only support GRE.
+# Cisco switches only support the L2 redirect assignment.
+#
+# If the "ip wccp redirect exclude in" command has been
+# enabled on the cache interface, then it is still safe for
+# the proxy server to use a l2 redirect method even if this
+# option is set to GRE.
+#Default:
+# wccp2_return_method gre
+
+# TAG: wccp2_assignment_method
+# WCCP2 allows the setting of methods to assign the WCCP hash
+# Valid values are as follows:
+#
+# hash - Hash assignment
+# mask - Mask assignment
+#
+# As a general rule, cisco routers support the hash assignment method
+# and cisco switches support the mask assignment method.
+#Default:
+# wccp2_assignment_method hash
+
+# TAG: wccp2_service
+# WCCP2 allows for multiple traffic services. There are two
+# types: "standard" and "dynamic". The standard type defines
+# one service id - http (id 0). The dynamic service ids can be from
+# 51 to 255 inclusive. In order to use a dynamic service id
+# one must define the type of traffic to be redirected; this is done
+# using the wccp2_service_info option.
+#
+# The "standard" type does not require a wccp2_service_info option,
+# just specifying the service id will suffice.
+#
+# MD5 service authentication can be enabled by adding
+# "password=<password>" to the end of this service declaration.
+#
+# Examples:
+#
+# wccp2_service standard 0 # for the 'web-cache' standard service
+# wccp2_service dynamic 80 # a dynamic service type which will be
+# # fleshed out with subsequent options.
+# wccp2_service standard 0 password=foo
+#Default:
+# Use the 'web-cache' standard service.
+
+# TAG: wccp2_service_info
+# Dynamic WCCPv2 services require further information to define the
+# traffic you wish to have diverted.
+#
+# The format is:
+#
+# wccp2_service_info <id> protocol=<protocol> flags=<flag>,<flag>..
+# priority=<priority> ports=<port>,<port>..
+#
+# The relevant WCCPv2 flags:
+# + src_ip_hash, dst_ip_hash
+# + source_port_hash, dst_port_hash
+# + src_ip_alt_hash, dst_ip_alt_hash
+# + src_port_alt_hash, dst_port_alt_hash
+# + ports_source
+#
+# The port list can be one to eight entries.
+#
+# Example:
+#
+# wccp2_service_info 80 protocol=tcp flags=src_ip_hash,ports_source
+# priority=240 ports=80
+#
+# Note: the service id must have been defined by a previous
+# 'wccp2_service dynamic <id>' entry.
+#Default:
+# none
+
+# TAG: wccp2_weight
+# Each cache server gets assigned a set of the destination
+# hash proportional to their weight.
+#Default:
+# wccp2_weight 10000
+
+# TAG: wccp_address
+# Use this option if you require WCCPv2 to use a specific
+# interface address.
+#
+# The default behavior is to not bind to any specific address.
+#Default:
+# Address selected by the operating system.
+
+# TAG: wccp2_address
+# Use this option if you require WCCP to use a specific
+# interface address.
+#
+# The default behavior is to not bind to any specific address.
+#Default:
+# Address selected by the operating system.
+
+# PERSISTENT CONNECTION HANDLING
+# -----------------------------------------------------------------------------
+#
+# Also see "pconn_timeout" in the TIMEOUTS section
+
+# TAG: client_persistent_connections
+# Persistent connection support for clients.
+# Squid uses persistent connections (when allowed). You can use
+# this option to disable persistent connections with clients.
+#Default:
+# client_persistent_connections on
+
+# TAG: server_persistent_connections
+# Persistent connection support for servers.
+# Squid uses persistent connections (when allowed). You can use
+# this option to disable persistent connections with servers.
+#Default:
+# server_persistent_connections on
+
+# TAG: persistent_connection_after_error
+# With this directive the use of persistent connections after
+# HTTP errors can be disabled. Useful if you have clients
+# who fail to handle errors on persistent connections proper.
+#Default:
+# persistent_connection_after_error on
+
+# TAG: detect_broken_pconn
+# Some servers have been found to incorrectly signal the use
+# of HTTP/1.0 persistent connections even on replies not
+# compatible, causing significant delays. This server problem
+# has mostly been seen on redirects.
+#
+# By enabling this directive Squid attempts to detect such
+# broken replies and automatically assume the reply is finished
+# after 10 seconds timeout.
+#Default:
+# detect_broken_pconn off
+
+# CACHE DIGEST OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: digest_generation
+# This controls whether the server will generate a Cache Digest
+# of its contents. By default, Cache Digest generation is
+# enabled if Squid is compiled with --enable-cache-digests defined.
+#Default:
+# digest_generation on
+
+# TAG: digest_bits_per_entry
+# This is the number of bits of the server's Cache Digest which
+# will be associated with the Digest entry for a given HTTP
+# Method and URL (public key) combination. The default is 5.
+#Default:
+# digest_bits_per_entry 5
+
+# TAG: digest_rebuild_period (seconds)
+# This is the wait time between Cache Digest rebuilds.
+#Default:
+# digest_rebuild_period 1 hour
+
+# TAG: digest_rewrite_period (seconds)
+# This is the wait time between Cache Digest writes to
+# disk.
+#Default:
+# digest_rewrite_period 1 hour
+
+# TAG: digest_swapout_chunk_size (bytes)
+# This is the number of bytes of the Cache Digest to write to
+# disk at a time. It defaults to 4096 bytes (4KB), the Squid
+# default swap page.
+#Default:
+# digest_swapout_chunk_size 4096 bytes
+
+# TAG: digest_rebuild_chunk_percentage (percent, 0-100)
+# This is the percentage of the Cache Digest to be scanned at a
+# time. By default it is set to 10% of the Cache Digest.
+#Default:
+# digest_rebuild_chunk_percentage 10
+
+# SNMP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: snmp_port
+# The port number where Squid listens for SNMP requests. To enable
+# SNMP support set this to a suitable port number. Port number
+# 3401 is often used for the Squid SNMP agent. By default it's
+# set to "0" (disabled)
+#
+# Example:
+# snmp_port 3401
+#Default:
+# SNMP disabled.
+
+# TAG: snmp_access
+# Allowing or denying access to the SNMP port.
+#
+# All access to the agent is denied by default.
+# usage:
+#
+# snmp_access allow|deny [!]aclname ...
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Example:
+# snmp_access allow snmppublic localhost
+# snmp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: snmp_incoming_address
+# Just like 'udp_incoming_address', but for the SNMP port.
+#
+# snmp_incoming_address is used for the SNMP socket receiving
+# messages from SNMP agents.
+#
+# The default snmp_incoming_address is to listen on all
+# available network interfaces.
+#Default:
+# Accept SNMP packets from all machine interfaces.
+
+# TAG: snmp_outgoing_address
+# Just like 'udp_outgoing_address', but for the SNMP port.
+#
+# snmp_outgoing_address is used for SNMP packets returned to SNMP
+# agents.
+#
+# If snmp_outgoing_address is not set it will use the same socket
+# as snmp_incoming_address. Only change this if you want to have
+# SNMP replies sent using another address than where this Squid
+# listens for SNMP queries.
+#
+# NOTE, snmp_incoming_address and snmp_outgoing_address can not have
+# the same value since they both use the same port.
+#Default:
+# Use snmp_incoming_address or an address selected by the operating system.
+
+# ICP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icp_port
+# The port number where Squid sends and receives ICP queries to
+# and from neighbor caches. The standard UDP port for ICP is 3130.
+#
+# Example:
+# icp_port 3130
+#Default:
+# ICP disabled.
+
+# TAG: htcp_port
+# The port number where Squid sends and receives HTCP queries to
+# and from neighbor caches. To turn it on you want to set it to
+# 4827.
+#
+# Example:
+# htcp_port 4827
+#Default:
+# HTCP disabled.
+
+# TAG: log_icp_queries on|off
+# If set, ICP queries are logged to access.log. You may wish
+# do disable this if your ICP load is VERY high to speed things
+# up or to simplify log analysis.
+#Default:
+# log_icp_queries on
+
+# TAG: udp_incoming_address
+# udp_incoming_address is used for UDP packets received from other
+# caches.
+#
+# The default behavior is to not bind to any specific address.
+#
+# Only change this if you want to have all UDP queries received on
+# a specific interface/address.
+#
+# NOTE: udp_incoming_address is used by the ICP, HTCP, and DNS
+# modules. Altering it will affect all of them in the same manner.
+#
+# see also; udp_outgoing_address
+#
+# NOTE, udp_incoming_address and udp_outgoing_address can not
+# have the same value since they both use the same port.
+#Default:
+# Accept packets from all machine interfaces.
+
+# TAG: udp_outgoing_address
+# udp_outgoing_address is used for UDP packets sent out to other
+# caches.
+#
+# The default behavior is to not bind to any specific address.
+#
+# Instead it will use the same socket as udp_incoming_address.
+# Only change this if you want to have UDP queries sent using another
+# address than where this Squid listens for UDP queries from other
+# caches.
+#
+# NOTE: udp_outgoing_address is used by the ICP, HTCP, and DNS
+# modules. Altering it will affect all of them in the same manner.
+#
+# see also; udp_incoming_address
+#
+# NOTE, udp_incoming_address and udp_outgoing_address can not
+# have the same value since they both use the same port.
+#Default:
+# Use udp_incoming_address or an address selected by the operating system.
+
+# TAG: icp_hit_stale on|off
+# If you want to return ICP_HIT for stale cache objects, set this
+# option to 'on'. If you have sibling relationships with caches
+# in other administrative domains, this should be 'off'. If you only
+# have sibling relationships with caches under your control,
+# it is probably okay to set this to 'on'.
+# If set to 'on', your siblings should use the option "allow-miss"
+# on their cache_peer lines for connecting to you.
+#Default:
+# icp_hit_stale off
+
+# TAG: minimum_direct_hops
+# If using the ICMP pinging stuff, do direct fetches for sites
+# which are no more than this many hops away.
+#Default:
+# minimum_direct_hops 4
+
+# TAG: minimum_direct_rtt (msec)
+# If using the ICMP pinging stuff, do direct fetches for sites
+# which are no more than this many rtt milliseconds away.
+#Default:
+# minimum_direct_rtt 400
+
+# TAG: netdb_low
+# The low water mark for the ICMP measurement database.
+#
+# Note: high watermark controlled by netdb_high directive.
+#
+# These watermarks are counts, not percents. The defaults are
+# (low) 900 and (high) 1000. When the high water mark is
+# reached, database entries will be deleted until the low
+# mark is reached.
+#Default:
+# netdb_low 900
+
+# TAG: netdb_high
+# The high water mark for the ICMP measurement database.
+#
+# Note: low watermark controlled by netdb_low directive.
+#
+# These watermarks are counts, not percents. The defaults are
+# (low) 900 and (high) 1000. When the high water mark is
+# reached, database entries will be deleted until the low
+# mark is reached.
+#Default:
+# netdb_high 1000
+
+# TAG: netdb_ping_period
+# The minimum period for measuring a site. There will be at
+# least this much delay between successive pings to the same
+# network. The default is five minutes.
+#Default:
+# netdb_ping_period 5 minutes
+
+# TAG: query_icmp on|off
+# If you want to ask your peers to include ICMP data in their ICP
+# replies, enable this option.
+#
+# If your peer has configured Squid (during compilation) with
+# '--enable-icmp' that peer will send ICMP pings to origin server
+# sites of the URLs it receives. If you enable this option the
+# ICP replies from that peer will include the ICMP data (if available).
+# Then, when choosing a parent cache, Squid will choose the parent with
+# the minimal RTT to the origin server. When this happens, the
+# hierarchy field of the access.log will be
+# "CLOSEST_PARENT_MISS". This option is off by default.
+#Default:
+# query_icmp off
+
+# TAG: test_reachability on|off
+# When this is 'on', ICP MISS replies will be ICP_MISS_NOFETCH
+# instead of ICP_MISS if the target host is NOT in the ICMP
+# database, or has a zero RTT.
+#Default:
+# test_reachability off
+
+# TAG: icp_query_timeout (msec)
+# Normally Squid will automatically determine an optimal ICP
+# query timeout value based on the round-trip-time of recent ICP
+# queries. If you want to override the value determined by
+# Squid, set this 'icp_query_timeout' to a non-zero value. This
+# value is specified in MILLISECONDS, so, to use a 2-second
+# timeout (the old default), you would write:
+#
+# icp_query_timeout 2000
+#Default:
+# Dynamic detection.
+
+# TAG: maximum_icp_query_timeout (msec)
+# Normally the ICP query timeout is determined dynamically. But
+# sometimes it can lead to very large values (say 5 seconds).
+# Use this option to put an upper limit on the dynamic timeout
+# value. Do NOT use this option to always use a fixed (instead
+# of a dynamic) timeout value. To set a fixed timeout see the
+# 'icp_query_timeout' directive.
+#Default:
+# maximum_icp_query_timeout 2000
+
+# TAG: minimum_icp_query_timeout (msec)
+# Normally the ICP query timeout is determined dynamically. But
+# sometimes it can lead to very small timeouts, even lower than
+# the normal latency variance on your link due to traffic.
+# Use this option to put an lower limit on the dynamic timeout
+# value. Do NOT use this option to always use a fixed (instead
+# of a dynamic) timeout value. To set a fixed timeout see the
+# 'icp_query_timeout' directive.
+#Default:
+# minimum_icp_query_timeout 5
+
+# TAG: background_ping_rate time-units
+# Controls how often the ICP pings are sent to siblings that
+# have background-ping set.
+#Default:
+# background_ping_rate 10 seconds
+
+# MULTICAST ICP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: mcast_groups
+# This tag specifies a list of multicast groups which your server
+# should join to receive multicasted ICP queries.
+#
+# NOTE! Be very careful what you put here! Be sure you
+# understand the difference between an ICP _query_ and an ICP
+# _reply_. This option is to be set only if you want to RECEIVE
+# multicast queries. Do NOT set this option to SEND multicast
+# ICP (use cache_peer for that). ICP replies are always sent via
+# unicast, so this option does not affect whether or not you will
+# receive replies from multicast group members.
+#
+# You must be very careful to NOT use a multicast address which
+# is already in use by another group of caches.
+#
+# If you are unsure about multicast, please read the Multicast
+# chapter in the Squid FAQ (http://www.squid-cache.org/FAQ/).
+#
+# Usage: mcast_groups 239.128.16.128 224.0.1.20
+#
+# By default, Squid doesn't listen on any multicast groups.
+#Default:
+# none
+
+# TAG: mcast_miss_addr
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# If you enable this option, every "cache miss" URL will
+# be sent out on the specified multicast address.
+#
+# Do not enable this option unless you are are absolutely
+# certain you understand what you are doing.
+#Default:
+# disabled.
+
+# TAG: mcast_miss_ttl
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# This is the time-to-live value for packets multicasted
+# when multicasting off cache miss URLs is enabled. By
+# default this is set to 'site scope', i.e. 16.
+#Default:
+# mcast_miss_ttl 16
+
+# TAG: mcast_miss_port
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# This is the port number to be used in conjunction with
+# 'mcast_miss_addr'.
+#Default:
+# mcast_miss_port 3135
+
+# TAG: mcast_miss_encode_key
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# The URLs that are sent in the multicast miss stream are
+# encrypted. This is the encryption key.
+#Default:
+# mcast_miss_encode_key XXXXXXXXXXXXXXXX
+
+# TAG: mcast_icp_query_timeout (msec)
+# For multicast peers, Squid regularly sends out ICP "probes" to
+# count how many other peers are listening on the given multicast
+# address. This value specifies how long Squid should wait to
+# count all the replies. The default is 2000 msec, or 2
+# seconds.
+#Default:
+# mcast_icp_query_timeout 2000
+
+# INTERNAL ICON OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icon_directory
+# Where the icons are stored. These are normally kept in
+# /usr/share/squid/icons
+#Default:
+# icon_directory /usr/share/squid/icons
+
+# TAG: global_internal_static
+# This directive controls is Squid should intercept all requests for
+# /squid-internal-static/ no matter which host the URL is requesting
+# (default on setting), or if nothing special should be done for
+# such URLs (off setting). The purpose of this directive is to make
+# icons etc work better in complex cache hierarchies where it may
+# not always be possible for all corners in the cache mesh to reach
+# the server generating a directory listing.
+#Default:
+# global_internal_static on
+
+# TAG: short_icon_urls
+# If this is enabled Squid will use short URLs for icons.
+# If disabled it will revert to the old behavior of including
+# it's own name and port in the URL.
+#
+# If you run a complex cache hierarchy with a mix of Squid and
+# other proxies you may need to disable this directive.
+#Default:
+# short_icon_urls on
+
+# ERROR PAGE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: error_directory
+# If you wish to create your own versions of the default
+# error files to customize them to suit your company copy
+# the error/template files to another directory and point
+# this tag at them.
+#
+# WARNING: This option will disable multi-language support
+# on error pages if used.
+#
+# The squid developers are interested in making squid available in
+# a wide variety of languages. If you are making translations for a
+# language that Squid does not currently provide please consider
+# contributing your translation back to the project.
+# http://wiki.squid-cache.org/Translations
+#
+# The squid developers working on translations are happy to supply drop-in
+# translated error files in exchange for any new language contributions.
+#Default:
+# Send error pages in the clients preferred language
+
+# TAG: error_default_language
+# Set the default language which squid will send error pages in
+# if no existing translation matches the clients language
+# preferences.
+#
+# If unset (default) generic English will be used.
+#
+# The squid developers are interested in making squid available in
+# a wide variety of languages. If you are interested in making
+# translations for any language see the squid wiki for details.
+# http://wiki.squid-cache.org/Translations
+#Default:
+# Generate English language pages.
+
+# TAG: error_log_languages
+# Log to cache.log what languages users are attempting to
+# auto-negotiate for translations.
+#
+# Successful negotiations are not logged. Only failures
+# have meaning to indicate that Squid may need an upgrade
+# of its error page translations.
+#Default:
+# error_log_languages on
+
+# TAG: err_page_stylesheet
+# CSS Stylesheet to pattern the display of Squid default error pages.
+#
+# For information on CSS see http://www.w3.org/Style/CSS/
+#Default:
+# err_page_stylesheet /etc/squid/errorpage.css
+
+# TAG: err_html_text
+# HTML text to include in error messages. Make this a "mailto"
+# URL to your admin address, or maybe just a link to your
+# organizations Web page.
+#
+# To include this in your error messages, you must rewrite
+# the error template files (found in the "errors" directory).
+# Wherever you want the 'err_html_text' line to appear,
+# insert a %L tag in the error template file.
+#Default:
+# none
+
+# TAG: email_err_data on|off
+# If enabled, information about the occurred error will be
+# included in the mailto links of the ERR pages (if %W is set)
+# so that the email body contains the data.
+# Syntax is <A HREF="mailto:%w%W">%w</A>
+#Default:
+# email_err_data on
+
+# TAG: deny_info
+# Usage: deny_info err_page_name acl
+# or deny_info http://... acl
+# or deny_info TCP_RESET acl
+#
+# This can be used to return a ERR_ page for requests which
+# do not pass the 'http_access' rules. Squid remembers the last
+# acl it evaluated in http_access, and if a 'deny_info' line exists
+# for that ACL Squid returns a corresponding error page.
+#
+# The acl is typically the last acl on the http_access deny line which
+# denied access. The exceptions to this rule are:
+# - When Squid needs to request authentication credentials. It's then
+# the first authentication related acl encountered
+# - When none of the http_access lines matches. It's then the last
+# acl processed on the last http_access line.
+# - When the decision to deny access was made by an adaptation service,
+# the acl name is the corresponding eCAP or ICAP service_name.
+#
+# NP: If providing your own custom error pages with error_directory
+# you may also specify them by your custom file name:
+# Example: deny_info ERR_CUSTOM_ACCESS_DENIED bad_guys
+#
+# By defaut Squid will send "403 Forbidden". A different 4xx or 5xx
+# may be specified by prefixing the file name with the code and a colon.
+# e.g. 404:ERR_CUSTOM_ACCESS_DENIED
+#
+# Alternatively you can tell Squid to reset the TCP connection
+# by specifying TCP_RESET.
+#
+# Or you can specify an error URL or URL pattern. The browsers will
+# get redirected to the specified URL after formatting tags have
+# been replaced. Redirect will be done with 302 or 307 according to
+# HTTP/1.1 specs. A different 3xx code may be specified by prefixing
+# the URL. e.g. 303:http://example.com/
+#
+# URL FORMAT TAGS:
+# %a - username (if available. Password NOT included)
+# %B - FTP path URL
+# %e - Error number
+# %E - Error description
+# %h - Squid hostname
+# %H - Request domain name
+# %i - Client IP Address
+# %M - Request Method
+# %O - Unescaped message result from external ACL helper
+# %o - Message result from external ACL helper
+# %p - Request Port number
+# %P - Request Protocol name
+# %R - Request URL path
+# %T - Timestamp in RFC 1123 format
+# %U - Full canonical URL from client
+# (HTTPS URLs terminate with *)
+# %u - Full canonical URL from client
+# %w - Admin email from squid.conf
+# %x - Error name
+# %% - Literal percent (%) code
+#
+#Default:
+# none
+
+# OPTIONS INFLUENCING REQUEST FORWARDING
+# -----------------------------------------------------------------------------
+
+# TAG: nonhierarchical_direct
+# By default, Squid will send any non-hierarchical requests
+# (not cacheable request type) direct to origin servers.
+#
+# When this is set to "off", Squid will prefer to send these
+# requests to parents.
+#
+# Note that in most configurations, by turning this off you will only
+# add latency to these request without any improvement in global hit
+# ratio.
+#
+# This option only sets a preference. If the parent is unavailable a
+# direct connection to the origin server may still be attempted. To
+# completely prevent direct connections use never_direct.
+#Default:
+# nonhierarchical_direct on
+
+# TAG: prefer_direct
+# Normally Squid tries to use parents for most requests. If you for some
+# reason like it to first try going direct and only use a parent if
+# going direct fails set this to on.
+#
+# By combining nonhierarchical_direct off and prefer_direct on you
+# can set up Squid to use a parent as a backup path if going direct
+# fails.
+#
+# Note: If you want Squid to use parents for all requests see
+# the never_direct directive. prefer_direct only modifies how Squid
+# acts on cacheable requests.
+#Default:
+# prefer_direct off
+
+# TAG: cache_miss_revalidate on|off
+# RFC 7232 defines a conditional request mechanism to prevent
+# response objects being unnecessarily transferred over the network.
+# If that mechanism is used by the client and a cache MISS occurs
+# it can prevent new cache entries being created.
+#
+# This option determines whether Squid on cache MISS will pass the
+# client revalidation request to the server or tries to fetch new
+# content for caching. It can be useful while the cache is mostly
+# empty to more quickly have the cache populated by generating
+# non-conditional GETs.
+#
+# When set to 'on' (default), Squid will pass all client If-* headers
+# to the server. This permits server responses without a cacheable
+# payload to be delivered and on MISS no new cache entry is created.
+#
+# When set to 'off' and if the request is cacheable, Squid will
+# remove the clients If-Modified-Since and If-None-Match headers from
+# the request sent to the server. This requests a 200 status response
+# from the server to create a new cache entry with.
+#Default:
+# cache_miss_revalidate on
+
+# TAG: always_direct
+# Usage: always_direct allow|deny [!]aclname ...
+#
+# Here you can use ACL elements to specify requests which should
+# ALWAYS be forwarded by Squid to the origin servers without using
+# any peers. For example, to always directly forward requests for
+# local servers ignoring any parents or siblings you may have use
+# something like:
+#
+# acl local-servers dstdomain my.domain.net
+# always_direct allow local-servers
+#
+# To always forward FTP requests directly, use
+#
+# acl FTP proto FTP
+# always_direct allow FTP
+#
+# NOTE: There is a similar, but opposite option named
+# 'never_direct'. You need to be aware that "always_direct deny
+# foo" is NOT the same thing as "never_direct allow foo". You
+# may need to use a deny rule to exclude a more-specific case of
+# some other rule. Example:
+#
+# acl local-external dstdomain external.foo.net
+# acl local-servers dstdomain .foo.net
+# always_direct deny local-external
+# always_direct allow local-servers
+#
+# NOTE: If your goal is to make the client forward the request
+# directly to the origin server bypassing Squid then this needs
+# to be done in the client configuration. Squid configuration
+# can only tell Squid how Squid should fetch the object.
+#
+# NOTE: This directive is not related to caching. The replies
+# is cached as usual even if you use always_direct. To not cache
+# the replies see the 'cache' directive.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Prevent any cache_peer being used for this request.
+
+# TAG: never_direct
+# Usage: never_direct allow|deny [!]aclname ...
+#
+# never_direct is the opposite of always_direct. Please read
+# the description for always_direct if you have not already.
+#
+# With 'never_direct' you can use ACL elements to specify
+# requests which should NEVER be forwarded directly to origin
+# servers. For example, to force the use of a proxy for all
+# requests, except those in your local domain use something like:
+#
+# acl local-servers dstdomain .foo.net
+# never_direct deny local-servers
+# never_direct allow all
+#
+# or if Squid is inside a firewall and there are local intranet
+# servers inside the firewall use something like:
+#
+# acl local-intranet dstdomain .foo.net
+# acl local-external dstdomain external.foo.net
+# always_direct deny local-external
+# always_direct allow local-intranet
+# never_direct allow all
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow DNS results to be used for this request.
+
+# ADVANCED NETWORKING OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: incoming_udp_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_udp_average 6
+
+# TAG: incoming_tcp_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_tcp_average 4
+
+# TAG: incoming_dns_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_dns_average 4
+
+# TAG: min_udp_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_udp_poll_cnt 8
+
+# TAG: min_dns_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_dns_poll_cnt 8
+
+# TAG: min_tcp_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_tcp_poll_cnt 8
+
+# TAG: accept_filter
+# FreeBSD:
+#
+# The name of an accept(2) filter to install on Squid's
+# listen socket(s). This feature is perhaps specific to
+# FreeBSD and requires support in the kernel.
+#
+# The 'httpready' filter delays delivering new connections
+# to Squid until a full HTTP request has been received.
+# See the accf_http(9) man page for details.
+#
+# The 'dataready' filter delays delivering new connections
+# to Squid until there is some data to process.
+# See the accf_dataready(9) man page for details.
+#
+# Linux:
+#
+# The 'data' filter delays delivering of new connections
+# to Squid until there is some data to process by TCP_ACCEPT_DEFER.
+# You may optionally specify a number of seconds to wait by
+# 'data=N' where N is the number of seconds. Defaults to 30
+# if not specified. See the tcp(7) man page for details.
+#EXAMPLE:
+## FreeBSD
+#accept_filter httpready
+## Linux
+#accept_filter data
+#Default:
+# none
+
+# TAG: client_ip_max_connections
+# Set an absolute limit on the number of connections a single
+# client IP can use. Any more than this and Squid will begin to drop
+# new connections from the client until it closes some links.
+#
+# Note that this is a global limit. It affects all HTTP, HTCP, Gopher and FTP
+# connections from the client. For finer control use the ACL access controls.
+#
+# Requires client_db to be enabled (the default).
+#
+# WARNING: This may noticably slow down traffic received via external proxies
+# or NAT devices and cause them to rebound error messages back to their clients.
+#Default:
+# No limit.
+
+# TAG: tcp_recv_bufsize (bytes)
+# Size of receive buffer to set for TCP sockets. Probably just
+# as easy to change your kernel's default.
+# Omit from squid.conf to use the default buffer size.
+#Default:
+# Use operating system TCP defaults.
+
+# ICAP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icap_enable on|off
+# If you want to enable the ICAP module support, set this to on.
+#Default:
+# icap_enable off
+
+# TAG: icap_connect_timeout
+# This parameter specifies how long to wait for the TCP connect to
+# the requested ICAP server to complete before giving up and either
+# terminating the HTTP transaction or bypassing the failure.
+#
+# The default for optional services is peer_connect_timeout.
+# The default for essential services is connect_timeout.
+# If this option is explicitly set, its value applies to all services.
+#Default:
+# none
+
+# TAG: icap_io_timeout time-units
+# This parameter specifies how long to wait for an I/O activity on
+# an established, active ICAP connection before giving up and
+# either terminating the HTTP transaction or bypassing the
+# failure.
+#Default:
+# Use read_timeout.
+
+# TAG: icap_service_failure_limit limit [in memory-depth time-units]
+# The limit specifies the number of failures that Squid tolerates
+# when establishing a new TCP connection with an ICAP service. If
+# the number of failures exceeds the limit, the ICAP service is
+# not used for new ICAP requests until it is time to refresh its
+# OPTIONS.
+#
+# A negative value disables the limit. Without the limit, an ICAP
+# service will not be considered down due to connectivity failures
+# between ICAP OPTIONS requests.
+#
+# Squid forgets ICAP service failures older than the specified
+# value of memory-depth. The memory fading algorithm
+# is approximate because Squid does not remember individual
+# errors but groups them instead, splitting the option
+# value into ten time slots of equal length.
+#
+# When memory-depth is 0 and by default this option has no
+# effect on service failure expiration.
+#
+# Squid always forgets failures when updating service settings
+# using an ICAP OPTIONS transaction, regardless of this option
+# setting.
+#
+# For example,
+# # suspend service usage after 10 failures in 5 seconds:
+# icap_service_failure_limit 10 in 5 seconds
+#Default:
+# icap_service_failure_limit 10
+
+# TAG: icap_service_revival_delay
+# The delay specifies the number of seconds to wait after an ICAP
+# OPTIONS request failure before requesting the options again. The
+# failed ICAP service is considered "down" until fresh OPTIONS are
+# fetched.
+#
+# The actual delay cannot be smaller than the hardcoded minimum
+# delay of 30 seconds.
+#Default:
+# icap_service_revival_delay 180
+
+# TAG: icap_preview_enable on|off
+# The ICAP Preview feature allows the ICAP server to handle the
+# HTTP message by looking only at the beginning of the message body
+# or even without receiving the body at all. In some environments,
+# previews greatly speedup ICAP processing.
+#
+# During an ICAP OPTIONS transaction, the server may tell Squid what
+# HTTP messages should be previewed and how big the preview should be.
+# Squid will not use Preview if the server did not request one.
+#
+# To disable ICAP Preview for all ICAP services, regardless of
+# individual ICAP server OPTIONS responses, set this option to "off".
+#Example:
+#icap_preview_enable off
+#Default:
+# icap_preview_enable on
+
+# TAG: icap_preview_size
+# The default size of preview data to be sent to the ICAP server.
+# This value might be overwritten on a per server basis by OPTIONS requests.
+#Default:
+# No preview sent.
+
+# TAG: icap_206_enable on|off
+# 206 (Partial Content) responses is an ICAP extension that allows the
+# ICAP agents to optionally combine adapted and original HTTP message
+# content. The decision to combine is postponed until the end of the
+# ICAP response. Squid supports Partial Content extension by default.
+#
+# Activation of the Partial Content extension is negotiated with each
+# ICAP service during OPTIONS exchange. Most ICAP servers should handle
+# negotation correctly even if they do not support the extension, but
+# some might fail. To disable Partial Content support for all ICAP
+# services and to avoid any negotiation, set this option to "off".
+#
+# Example:
+# icap_206_enable off
+#Default:
+# icap_206_enable on
+
+# TAG: icap_default_options_ttl
+# The default TTL value for ICAP OPTIONS responses that don't have
+# an Options-TTL header.
+#Default:
+# icap_default_options_ttl 60
+
+# TAG: icap_persistent_connections on|off
+# Whether or not Squid should use persistent connections to
+# an ICAP server.
+#Default:
+# icap_persistent_connections on
+
+# TAG: adaptation_send_client_ip on|off
+# If enabled, Squid shares HTTP client IP information with adaptation
+# services. For ICAP, Squid adds the X-Client-IP header to ICAP requests.
+# For eCAP, Squid sets the libecap::metaClientIp transaction option.
+#
+# See also: adaptation_uses_indirect_client
+#Default:
+# adaptation_send_client_ip off
+
+# TAG: adaptation_send_username on|off
+# This sends authenticated HTTP client username (if available) to
+# the adaptation service.
+#
+# For ICAP, the username value is encoded based on the
+# icap_client_username_encode option and is sent using the header
+# specified by the icap_client_username_header option.
+#Default:
+# adaptation_send_username off
+
+# TAG: icap_client_username_header
+# ICAP request header name to use for adaptation_send_username.
+#Default:
+# icap_client_username_header X-Client-Username
+
+# TAG: icap_client_username_encode on|off
+# Whether to base64 encode the authenticated client username.
+#Default:
+# icap_client_username_encode off
+
+# TAG: icap_service
+# Defines a single ICAP service using the following format:
+#
+# icap_service id vectoring_point uri [option ...]
+#
+# id: ID
+# an opaque identifier or name which is used to direct traffic to
+# this specific service. Must be unique among all adaptation
+# services in squid.conf.
+#
+# vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache
+# This specifies at which point of transaction processing the
+# ICAP service should be activated. *_postcache vectoring points
+# are not yet supported.
+#
+# uri: icap://servername:port/servicepath
+# ICAP server and service location.
+# icaps://servername:port/servicepath
+# The "icap:" URI scheme is used for traditional ICAP server and
+# service location (default port is 1344, connections are not
+# encrypted). The "icaps:" URI scheme is for Secure ICAP
+# services that use SSL/TLS-encrypted ICAP connections (by
+# default, on port 11344).
+#
+# ICAP does not allow a single service to handle both REQMOD and RESPMOD
+# transactions. Squid does not enforce that requirement. You can specify
+# services with the same service_url and different vectoring_points. You
+# can even specify multiple identical services as long as their
+# service_names differ.
+#
+# To activate a service, use the adaptation_access directive. To group
+# services, use adaptation_service_chain and adaptation_service_set.
+#
+# Service options are separated by white space. ICAP services support
+# the following name=value options:
+#
+# bypass=on|off|1|0
+# If set to 'on' or '1', the ICAP service is treated as
+# optional. If the service cannot be reached or malfunctions,
+# Squid will try to ignore any errors and process the message as
+# if the service was not enabled. No all ICAP errors can be
+# bypassed. If set to 0, the ICAP service is treated as
+# essential and all ICAP errors will result in an error page
+# returned to the HTTP client.
+#
+# Bypass is off by default: services are treated as essential.
+#
+# routing=on|off|1|0
+# If set to 'on' or '1', the ICAP service is allowed to
+# dynamically change the current message adaptation plan by
+# returning a chain of services to be used next. The services
+# are specified using the X-Next-Services ICAP response header
+# value, formatted as a comma-separated list of service names.
+# Each named service should be configured in squid.conf. Other
+# services are ignored. An empty X-Next-Services value results
+# in an empty plan which ends the current adaptation.
+#
+# Dynamic adaptation plan may cross or cover multiple supported
+# vectoring points in their natural processing order.
+#
+# Routing is not allowed by default: the ICAP X-Next-Services
+# response header is ignored.
+#
+# ipv6=on|off
+# Only has effect on split-stack systems. The default on those systems
+# is to use IPv4-only connections. When set to 'on' this option will
+# make Squid use IPv6-only connections to contact this ICAP service.
+#
+# on-overload=block|bypass|wait|force
+# If the service Max-Connections limit has been reached, do
+# one of the following for each new ICAP transaction:
+# * block: send an HTTP error response to the client
+# * bypass: ignore the "over-connected" ICAP service
+# * wait: wait (in a FIFO queue) for an ICAP connection slot
+# * force: proceed, ignoring the Max-Connections limit
+#
+# In SMP mode with N workers, each worker assumes the service
+# connection limit is Max-Connections/N, even though not all
+# workers may use a given service.
+#
+# The default value is "bypass" if service is bypassable,
+# otherwise it is set to "wait".
+#
+#
+# max-conn=number
+# Use the given number as the Max-Connections limit, regardless
+# of the Max-Connections value given by the service, if any.
+#
+# connection-encryption=on|off
+# Determines the ICAP service effect on the connections_encrypted
+# ACL.
+#
+# The default is "on" for Secure ICAP services (i.e., those
+# with the icaps:// service URIs scheme) and "off" for plain ICAP
+# services.
+#
+# Does not affect ICAP connections (e.g., does not turn Secure
+# ICAP on or off).
+#
+# ==== ICAPS / TLS OPTIONS ====
+#
+# These options are used for Secure ICAP (icaps://....) services only.
+#
+# tls-cert=/path/to/ssl/certificate
+# A client X.509 certificate to use when connecting to
+# this ICAP server.
+#
+# tls-key=/path/to/ssl/key
+# The private key corresponding to the previous
+# tls-cert= option.
+#
+# If tls-key= is not specified tls-cert= is assumed to
+# reference a PEM file containing both the certificate
+# and private key.
+#
+# tls-cipher=... The list of valid TLS/SSL ciphers to use when connecting
+# to this icap server.
+#
+# tls-min-version=1.N
+# The minimum TLS protocol version to permit. To control
+# SSLv3 use the tls-options= parameter.
+# Supported Values: 1.0 (default), 1.1, 1.2
+#
+# tls-options=... Specify various OpenSSL library options:
+#
+# NO_SSLv3 Disallow the use of SSLv3
+#
+# SINGLE_DH_USE
+# Always create a new key when using
+# temporary/ephemeral DH key exchanges
+#
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation for a
+# more complete list. Options relevant only to SSLv2 are
+# not supported.
+#
+# tls-cafile= PEM file containing CA certificates to use when verifying
+# the icap server certificate.
+# Use to specify intermediate CA certificate(s) if not sent
+# by the server. Or the full CA chain for the server when
+# using the tls-default-ca=off flag.
+# May be repeated to load multiple files.
+#
+# tls-capath=... A directory containing additional CA certificates to
+# use when verifying the icap server certificate.
+# Requires OpenSSL or LibreSSL.
+#
+# tls-crlfile=... A certificate revocation list file to use when
+# verifying the icap server certificate.
+#
+# tls-flags=... Specify various flags modifying the Squid TLS implementation:
+#
+# DONT_VERIFY_PEER
+# Accept certificates even if they fail to
+# verify.
+# DONT_VERIFY_DOMAIN
+# Don't verify the icap server certificate
+# matches the server name
+#
+# tls-default-ca[=off]
+# Whether to use the system Trusted CAs. Default is ON.
+#
+# tls-domain= The icap server name as advertised in it's certificate.
+# Used for verifying the correctness of the received icap
+# server certificate. If not specified the icap server
+# hostname extracted from ICAP URI will be used.
+#
+# Older icap_service format without optional named parameters is
+# deprecated but supported for backward compatibility.
+#
+#Example:
+#icap_service svcBlocker reqmod_precache icap://icap1.mydomain.net:1344/reqmod bypass=0
+#icap_service svcLogger reqmod_precache icaps://icap2.mydomain.net:11344/reqmod routing=on
+#Default:
+# none
+
+# TAG: icap_class
+# This deprecated option was documented to define an ICAP service
+# chain, even though it actually defined a set of similar, redundant
+# services, and the chains were not supported.
+#
+# To define a set of redundant services, please use the
+# adaptation_service_set directive. For service chains, use
+# adaptation_service_chain.
+#Default:
+# none
+
+# TAG: icap_access
+# This option is deprecated. Please use adaptation_access, which
+# has the same ICAP functionality, but comes with better
+# documentation, and eCAP support.
+#Default:
+# none
+
+# eCAP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: ecap_enable on|off
+# Controls whether eCAP support is enabled.
+#Default:
+# ecap_enable off
+
+# TAG: ecap_service
+# Defines a single eCAP service
+#
+# ecap_service id vectoring_point uri [option ...]
+#
+# id: ID
+# an opaque identifier or name which is used to direct traffic to
+# this specific service. Must be unique among all adaptation
+# services in squid.conf.
+#
+# vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache
+# This specifies at which point of transaction processing the
+# eCAP service should be activated. *_postcache vectoring points
+# are not yet supported.
+#
+# uri: ecap://vendor/service_name?custom&cgi=style¶meters=optional
+# Squid uses the eCAP service URI to match this configuration
+# line with one of the dynamically loaded services. Each loaded
+# eCAP service must have a unique URI. Obtain the right URI from
+# the service provider.
+#
+# To activate a service, use the adaptation_access directive. To group
+# services, use adaptation_service_chain and adaptation_service_set.
+#
+# Service options are separated by white space. eCAP services support
+# the following name=value options:
+#
+# bypass=on|off|1|0
+# If set to 'on' or '1', the eCAP service is treated as optional.
+# If the service cannot be reached or malfunctions, Squid will try
+# to ignore any errors and process the message as if the service
+# was not enabled. No all eCAP errors can be bypassed.
+# If set to 'off' or '0', the eCAP service is treated as essential
+# and all eCAP errors will result in an error page returned to the
+# HTTP client.
+#
+# Bypass is off by default: services are treated as essential.
+#
+# routing=on|off|1|0
+# If set to 'on' or '1', the eCAP service is allowed to
+# dynamically change the current message adaptation plan by
+# returning a chain of services to be used next.
+#
+# Dynamic adaptation plan may cross or cover multiple supported
+# vectoring points in their natural processing order.
+#
+# Routing is not allowed by default.
+#
+# connection-encryption=on|off
+# Determines the eCAP service effect on the connections_encrypted
+# ACL.
+#
+# Defaults to "on", which does not taint the master transaction
+# w.r.t. that ACL.
+#
+# Does not affect eCAP API calls.
+#
+# Older ecap_service format without optional named parameters is
+# deprecated but supported for backward compatibility.
+#
+#
+#Example:
+#ecap_service s1 reqmod_precache ecap://filters.R.us/leakDetector?on_error=block bypass=off
+#ecap_service s2 respmod_precache ecap://filters.R.us/virusFilter config=/etc/vf.cfg bypass=on
+#Default:
+# none
+
+# TAG: loadable_modules
+# Instructs Squid to load the specified dynamic module(s) or activate
+# preloaded module(s).
+#Example:
+#loadable_modules /usr/lib/MinimalAdapter.so
+#Default:
+# none
+
+# MESSAGE ADAPTATION OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: adaptation_service_set
+#
+# Configures an ordered set of similar, redundant services. This is
+# useful when hot standby or backup adaptation servers are available.
+#
+# adaptation_service_set set_name service_name1 service_name2 ...
+#
+# The named services are used in the set declaration order. The first
+# applicable adaptation service from the set is used first. The next
+# applicable service is tried if and only if the transaction with the
+# previous service fails and the message waiting to be adapted is still
+# intact.
+#
+# When adaptation starts, broken services are ignored as if they were
+# not a part of the set. A broken service is a down optional service.
+#
+# The services in a set must be attached to the same vectoring point
+# (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD).
+#
+# If all services in a set are optional then adaptation failures are
+# bypassable. If all services in the set are essential, then a
+# transaction failure with one service may still be retried using
+# another service from the set, but when all services fail, the master
+# transaction fails as well.
+#
+# A set may contain a mix of optional and essential services, but that
+# is likely to lead to surprising results because broken services become
+# ignored (see above), making previously bypassable failures fatal.
+# Technically, it is the bypassability of the last failed service that
+# matters.
+#
+# See also: adaptation_access adaptation_service_chain
+#
+#Example:
+#adaptation_service_set svcBlocker urlFilterPrimary urlFilterBackup
+#adaptation service_set svcLogger loggerLocal loggerRemote
+#Default:
+# none
+
+# TAG: adaptation_service_chain
+#
+# Configures a list of complementary services that will be applied
+# one-by-one, forming an adaptation chain or pipeline. This is useful
+# when Squid must perform different adaptations on the same message.
+#
+# adaptation_service_chain chain_name service_name1 svc_name2 ...
+#
+# The named services are used in the chain declaration order. The first
+# applicable adaptation service from the chain is used first. The next
+# applicable service is applied to the successful adaptation results of
+# the previous service in the chain.
+#
+# When adaptation starts, broken services are ignored as if they were
+# not a part of the chain. A broken service is a down optional service.
+#
+# Request satisfaction terminates the adaptation chain because Squid
+# does not currently allow declaration of RESPMOD services at the
+# "reqmod_precache" vectoring point (see icap_service or ecap_service).
+#
+# The services in a chain must be attached to the same vectoring point
+# (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD).
+#
+# A chain may contain a mix of optional and essential services. If an
+# essential adaptation fails (or the failure cannot be bypassed for
+# other reasons), the master transaction fails. Otherwise, the failure
+# is bypassed as if the failed adaptation service was not in the chain.
+#
+# See also: adaptation_access adaptation_service_set
+#
+#Example:
+#adaptation_service_chain svcRequest requestLogger urlFilter leakDetector
+#Default:
+# none
+
+# TAG: adaptation_access
+# Sends an HTTP transaction to an ICAP or eCAP adaptation service.
+#
+# adaptation_access service_name allow|deny [!]aclname...
+# adaptation_access set_name allow|deny [!]aclname...
+#
+# At each supported vectoring point, the adaptation_access
+# statements are processed in the order they appear in this
+# configuration file. Statements pointing to the following services
+# are ignored (i.e., skipped without checking their ACL):
+#
+# - services serving different vectoring points
+# - "broken-but-bypassable" services
+# - "up" services configured to ignore such transactions
+# (e.g., based on the ICAP Transfer-Ignore header).
+#
+# When a set_name is used, all services in the set are checked
+# using the same rules, to find the first applicable one. See
+# adaptation_service_set for details.
+#
+# If an access list is checked and there is a match, the
+# processing stops: For an "allow" rule, the corresponding
+# adaptation service is used for the transaction. For a "deny"
+# rule, no adaptation service is activated.
+#
+# It is currently not possible to apply more than one adaptation
+# service at the same vectoring point to the same HTTP transaction.
+#
+# See also: icap_service and ecap_service
+#
+#Example:
+#adaptation_access service_1 allow all
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: adaptation_service_iteration_limit
+# Limits the number of iterations allowed when applying adaptation
+# services to a message. If your longest adaptation set or chain
+# may have more than 16 services, increase the limit beyond its
+# default value of 16. If detecting infinite iteration loops sooner
+# is critical, make the iteration limit match the actual number
+# of services in your longest adaptation set or chain.
+#
+# Infinite adaptation loops are most likely with routing services.
+#
+# See also: icap_service routing=1
+#Default:
+# adaptation_service_iteration_limit 16
+
+# TAG: adaptation_masterx_shared_names
+# For each master transaction (i.e., the HTTP request and response
+# sequence, including all related ICAP and eCAP exchanges), Squid
+# maintains a table of metadata. The table entries are (name, value)
+# pairs shared among eCAP and ICAP exchanges. The table is destroyed
+# with the master transaction.
+#
+# This option specifies the table entry names that Squid must accept
+# from and forward to the adaptation transactions.
+#
+# An ICAP REQMOD or RESPMOD transaction may set an entry in the
+# shared table by returning an ICAP header field with a name
+# specified in adaptation_masterx_shared_names.
+#
+# An eCAP REQMOD or RESPMOD transaction may set an entry in the
+# shared table by implementing the libecap::visitEachOption() API
+# to provide an option with a name specified in
+# adaptation_masterx_shared_names.
+#
+# Squid will store and forward the set entry to subsequent adaptation
+# transactions within the same master transaction scope.
+#
+# Only one shared entry name is supported at this time.
+#
+#Example:
+## share authentication information among ICAP services
+#adaptation_masterx_shared_names X-Subscriber-ID
+#Default:
+# none
+
+# TAG: adaptation_meta
+# This option allows Squid administrator to add custom ICAP request
+# headers or eCAP options to Squid ICAP requests or eCAP transactions.
+# Use it to pass custom authentication tokens and other
+# transaction-state related meta information to an ICAP/eCAP service.
+#
+# The addition of a meta header is ACL-driven:
+# adaptation_meta name value [!]aclname ...
+#
+# Processing for a given header name stops after the first ACL list match.
+# Thus, it is impossible to add two headers with the same name. If no ACL
+# lists match for a given header name, no such header is added. For
+# example:
+#
+# # do not debug transactions except for those that need debugging
+# adaptation_meta X-Debug 1 needs_debugging
+#
+# # log all transactions except for those that must remain secret
+# adaptation_meta X-Log 1 !keep_secret
+#
+# # mark transactions from users in the "G 1" group
+# adaptation_meta X-Authenticated-Groups "G 1" authed_as_G1
+#
+# The "value" parameter may be a regular squid.conf token or a "double
+# quoted string". Within the quoted string, use backslash (\) to escape
+# any character, which is currently only useful for escaping backslashes
+# and double quotes. For example,
+# "this string has one backslash (\\) and two \"quotes\""
+#
+# Used adaptation_meta header values may be logged via %note
+# logformat code. If multiple adaptation_meta headers with the same name
+# are used during master transaction lifetime, the header values are
+# logged in the order they were used and duplicate values are ignored
+# (only the first repeated value will be logged).
+#Default:
+# none
+
+# TAG: icap_retry
+# This ACL determines which retriable ICAP transactions are
+# retried. Transactions that received a complete ICAP response
+# and did not have to consume or produce HTTP bodies to receive
+# that response are usually retriable.
+#
+# icap_retry allow|deny [!]aclname ...
+#
+# Squid automatically retries some ICAP I/O timeouts and errors
+# due to persistent connection race conditions.
+#
+# See also: icap_retry_limit
+#Default:
+# icap_retry deny all
+
+# TAG: icap_retry_limit
+# Limits the number of retries allowed.
+#
+# Communication errors due to persistent connection race
+# conditions are unavoidable, automatically retried, and do not
+# count against this limit.
+#
+# See also: icap_retry
+#Default:
+# No retries are allowed.
+
+# DNS OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: check_hostnames
+# For security and stability reasons Squid can check
+# hostnames for Internet standard RFC compliance. If you want
+# Squid to perform these checks turn this directive on.
+#Default:
+# check_hostnames off
+
+# TAG: allow_underscore
+# Underscore characters is not strictly allowed in Internet hostnames
+# but nevertheless used by many sites. Set this to off if you want
+# Squid to be strict about the standard.
+# This check is performed only when check_hostnames is set to on.
+#Default:
+# allow_underscore on
+
+# TAG: dns_retransmit_interval
+# Initial retransmit interval for DNS queries. The interval is
+# doubled each time all configured DNS servers have been tried.
+#Default:
+# dns_retransmit_interval 5 seconds
+
+# TAG: dns_timeout
+# DNS Query timeout. If no response is received to a DNS query
+# within this time all DNS servers for the queried domain
+# are assumed to be unavailable.
+#Default:
+# dns_timeout 30 seconds
+
+# TAG: dns_packet_max
+# Maximum number of bytes packet size to advertise via EDNS.
+# Set to "none" to disable EDNS large packet support.
+#
+# For legacy reasons DNS UDP replies will default to 512 bytes which
+# is too small for many responses. EDNS provides a means for Squid to
+# negotiate receiving larger responses back immediately without having
+# to failover with repeat requests. Responses larger than this limit
+# will retain the old behaviour of failover to TCP DNS.
+#
+# Squid has no real fixed limit internally, but allowing packet sizes
+# over 1500 bytes requires network jumbogram support and is usually not
+# necessary.
+#
+# WARNING: The RFC also indicates that some older resolvers will reply
+# with failure of the whole request if the extension is added. Some
+# resolvers have already been identified which will reply with mangled
+# EDNS response on occasion. Usually in response to many-KB jumbogram
+# sizes being advertised by Squid.
+# Squid will currently treat these both as an unable-to-resolve domain
+# even if it would be resolvable without EDNS.
+#Default:
+# EDNS disabled
+
+# TAG: dns_defnames on|off
+# Normally the RES_DEFNAMES resolver option is disabled
+# (see res_init(3)). This prevents caches in a hierarchy
+# from interpreting single-component hostnames locally. To allow
+# Squid to handle single-component names, enable this option.
+#Default:
+# Search for single-label domain names is disabled.
+
+# TAG: dns_multicast_local on|off
+# When set to on, Squid sends multicast DNS lookups on the local
+# network for domains ending in .local and .arpa.
+# This enables local servers and devices to be contacted in an
+# ad-hoc or zero-configuration network environment.
+#Default:
+# Search for .local and .arpa names is disabled.
+
+# TAG: dns_nameservers
+# Use this if you want to specify a list of DNS name servers
+# (IP addresses) to use instead of those given in your
+# /etc/resolv.conf file.
+#
+# On Windows platforms, if no value is specified here or in
+# the /etc/resolv.conf file, the list of DNS name servers are
+# taken from the Windows registry, both static and dynamic DHCP
+# configurations are supported.
+#
+# Example: dns_nameservers 10.0.0.1 192.172.0.4
+#Default:
+# Use operating system definitions
+
+# TAG: hosts_file
+# Location of the host-local IP name-address associations
+# database. Most Operating Systems have such a file on different
+# default locations:
+# - Un*X & Linux: /etc/hosts
+# - Windows NT/2000: %SystemRoot%\system32\drivers\etc\hosts
+# (%SystemRoot% value install default is c:\winnt)
+# - Windows XP/2003: %SystemRoot%\system32\drivers\etc\hosts
+# (%SystemRoot% value install default is c:\windows)
+# - Windows 9x/Me: %windir%\hosts
+# (%windir% value is usually c:\windows)
+# - Cygwin: /etc/hosts
+#
+# The file contains newline-separated definitions, in the
+# form ip_address_in_dotted_form name [name ...] names are
+# whitespace-separated. Lines beginning with an hash (#)
+# character are comments.
+#
+# The file is checked at startup and upon configuration.
+# If set to 'none', it won't be checked.
+# If append_domain is used, that domain will be added to
+# domain-local (i.e. not containing any dot character) host
+# definitions.
+#Default:
+# hosts_file /etc/hosts
+
+# TAG: append_domain
+# Appends local domain name to hostnames without any dots in
+# them. append_domain must begin with a period.
+#
+# Be warned there are now Internet names with no dots in
+# them using only top-domain names, so setting this may
+# cause some Internet sites to become unavailable.
+#
+#Example:
+# append_domain .yourdomain.com
+#Default:
+# Use operating system definitions
+
+# TAG: ignore_unknown_nameservers
+# By default Squid checks that DNS responses are received
+# from the same IP addresses they are sent to. If they
+# don't match, Squid ignores the response and writes a warning
+# message to cache.log. You can allow responses from unknown
+# nameservers by setting this option to 'off'.
+#Default:
+# ignore_unknown_nameservers on
+
+# TAG: dns_v4_first
+# With the IPv6 Internet being as fast or faster than IPv4 Internet
+# for most networks Squid prefers to contact websites over IPv6.
+#
+# This option reverses the order of preference to make Squid contact
+# dual-stack websites over IPv4 first. Squid will still perform both
+# IPv6 and IPv4 DNS lookups before connecting.
+#
+# WARNING:
+# This option will restrict the situations under which IPv6
+# connectivity is used (and tested), potentially hiding network
+# problems which would otherwise be detected and warned about.
+#Default:
+# dns_v4_first off
+
+# TAG: ipcache_size (number of entries)
+# Maximum number of DNS IP cache entries.
+#Default:
+# ipcache_size 1024
+
+# TAG: ipcache_low (percent)
+#Default:
+# ipcache_low 90
+
+# TAG: ipcache_high (percent)
+# The size, low-, and high-water marks for the IP cache.
+#Default:
+# ipcache_high 95
+
+# TAG: fqdncache_size (number of entries)
+# Maximum number of FQDN cache entries.
+#Default:
+# fqdncache_size 1024
+
+# MISCELLANEOUS
+# -----------------------------------------------------------------------------
+
+# TAG: configuration_includes_quoted_values on|off
+# If set, Squid will recognize each "quoted string" after a configuration
+# directive as a single parameter. The quotes are stripped before the
+# parameter value is interpreted or used.
+# See "Values with spaces, quotes, and other special characters"
+# section for more details.
+#Default:
+# configuration_includes_quoted_values off
+
+# TAG: memory_pools on|off
+# If set, Squid will keep pools of allocated (but unused) memory
+# available for future use. If memory is a premium on your
+# system and you believe your malloc library outperforms Squid
+# routines, disable this.
+#Default:
+# memory_pools on
+
+# TAG: memory_pools_limit (bytes)
+# Used only with memory_pools on:
+# memory_pools_limit 50 MB
+#
+# If set to a non-zero value, Squid will keep at most the specified
+# limit of allocated (but unused) memory in memory pools. All free()
+# requests that exceed this limit will be handled by your malloc
+# library. Squid does not pre-allocate any memory, just safe-keeps
+# objects that otherwise would be free()d. Thus, it is safe to set
+# memory_pools_limit to a reasonably high value even if your
+# configuration will use less memory.
+#
+# If set to none, Squid will keep all memory it can. That is, there
+# will be no limit on the total amount of memory used for safe-keeping.
+#
+# To disable memory allocation optimization, do not set
+# memory_pools_limit to 0 or none. Set memory_pools to "off" instead.
+#
+# An overhead for maintaining memory pools is not taken into account
+# when the limit is checked. This overhead is close to four bytes per
+# object kept. However, pools may actually _save_ memory because of
+# reduced memory thrashing in your malloc library.
+#Default:
+# memory_pools_limit 5 MB
+
+# TAG: forwarded_for on|off|transparent|truncate|delete
+# If set to "on", Squid will append your client's IP address
+# in the HTTP requests it forwards. By default it looks like:
+#
+# X-Forwarded-For: 192.1.2.3
+#
+# If set to "off", it will appear as
+#
+# X-Forwarded-For: unknown
+#
+# If set to "transparent", Squid will not alter the
+# X-Forwarded-For header in any way.
+#
+# If set to "delete", Squid will delete the entire
+# X-Forwarded-For header.
+#
+# If set to "truncate", Squid will remove all existing
+# X-Forwarded-For entries, and place the client IP as the sole entry.
+#Default:
+# forwarded_for on
+
+# TAG: cachemgr_passwd
+# Specify passwords for cachemgr operations.
+#
+# Usage: cachemgr_passwd password action action ...
+#
+# Some valid actions are (see cache manager menu for a full list):
+# 5min
+# 60min
+# asndb
+# authenticator
+# cbdata
+# client_list
+# comm_incoming
+# config *
+# counters
+# delay
+# digest_stats
+# dns
+# events
+# filedescriptors
+# fqdncache
+# histograms
+# http_headers
+# info
+# io
+# ipcache
+# mem
+# menu
+# netdb
+# non_peers
+# objects
+# offline_toggle *
+# pconn
+# peer_select
+# reconfigure *
+# redirector
+# refresh
+# server_list
+# shutdown *
+# store_digest
+# storedir
+# utilization
+# via_headers
+# vm_objects
+#
+# * Indicates actions which will not be performed without a
+# valid password, others can be performed if not listed here.
+#
+# To disable an action, set the password to "disable".
+# To allow performing an action without a password, set the
+# password to "none".
+#
+# Use the keyword "all" to set the same password for all actions.
+#
+#Example:
+# cachemgr_passwd secret shutdown
+# cachemgr_passwd lesssssssecret info stats/objects
+# cachemgr_passwd disable all
+#Default:
+# No password. Actions which require password are denied.
+
+# TAG: client_db on|off
+# If you want to disable collecting per-client statistics,
+# turn off client_db here.
+#Default:
+# client_db on
+
+# TAG: refresh_all_ims on|off
+# When you enable this option, squid will always check
+# the origin server for an update when a client sends an
+# If-Modified-Since request. Many browsers use IMS
+# requests when the user requests a reload, and this
+# ensures those clients receive the latest version.
+#
+# By default (off), squid may return a Not Modified response
+# based on the age of the cached version.
+#Default:
+# refresh_all_ims off
+
+# TAG: reload_into_ims on|off
+# When you enable this option, client no-cache or ``reload''
+# requests will be changed to If-Modified-Since requests.
+# Doing this VIOLATES the HTTP standard. Enabling this
+# feature could make you liable for problems which it
+# causes.
+#
+# see also refresh_pattern for a more selective approach.
+#Default:
+# reload_into_ims off
+
+# TAG: connect_retries
+# Limits the number of reopening attempts when establishing a single
+# TCP connection. All these attempts must still complete before the
+# applicable connection opening timeout expires.
+#
+# By default and when connect_retries is set to zero, Squid does not
+# retry failed connection opening attempts.
+#
+# The (not recommended) maximum is 10 tries. An attempt to configure a
+# higher value results in the value of 10 being used (with a warning).
+#
+# Squid may open connections to retry various high-level forwarding
+# failures. For an outside observer, that activity may look like a
+# low-level connection reopening attempt, but those high-level retries
+# are governed by forward_max_tries instead.
+#
+# See also: connect_timeout, forward_timeout, icap_connect_timeout,
+# ident_timeout, and forward_max_tries.
+#Default:
+# Do not retry failed connections.
+
+# TAG: retry_on_error
+# If set to ON Squid will automatically retry requests when
+# receiving an error response with status 403 (Forbidden),
+# 500 (Internal Error), 501 or 503 (Service not available).
+# Status 502 and 504 (Gateway errors) are always retried.
+#
+# This is mainly useful if you are in a complex cache hierarchy to
+# work around access control errors.
+#
+# NOTE: This retry will attempt to find another working destination.
+# Which is different from the server which just failed.
+#Default:
+# retry_on_error off
+
+# TAG: as_whois_server
+# WHOIS server to query for AS numbers. NOTE: AS numbers are
+# queried only when Squid starts up, not for every request.
+#Default:
+# as_whois_server whois.ra.net
+
+# TAG: offline_mode
+# Enable this option and Squid will never try to validate cached
+# objects.
+#Default:
+# offline_mode off
+
+# TAG: uri_whitespace
+# What to do with requests that have whitespace characters in the
+# URI. Options:
+#
+# strip: The whitespace characters are stripped out of the URL.
+# This is the behavior recommended by RFC2396 and RFC3986
+# for tolerant handling of generic URI.
+# NOTE: This is one difference between generic URI and HTTP URLs.
+#
+# deny: The request is denied. The user receives an "Invalid
+# Request" message.
+# This is the behaviour recommended by RFC2616 for safe
+# handling of HTTP request URL.
+#
+# allow: The request is allowed and the URI is not changed. The
+# whitespace characters remain in the URI. Note the
+# whitespace is passed to redirector processes if they
+# are in use.
+# Note this may be considered a violation of RFC2616
+# request parsing where whitespace is prohibited in the
+# URL field.
+#
+# encode: The request is allowed and the whitespace characters are
+# encoded according to RFC1738.
+#
+# chop: The request is allowed and the URI is chopped at the
+# first whitespace.
+#
+#
+# NOTE the current Squid implementation of encode and chop violates
+# RFC2616 by not using a 301 redirect after altering the URL.
+#Default:
+# uri_whitespace strip
+
+# TAG: chroot
+# Specifies a directory where Squid should do a chroot() while
+# initializing. This also causes Squid to fully drop root
+# privileges after initializing. This means, for example, if you
+# use a HTTP port less than 1024 and try to reconfigure, you may
+# get an error saying that Squid can not open the port.
+#Default:
+# none
+
+# TAG: pipeline_prefetch
+# HTTP clients may send a pipeline of 1+N requests to Squid using a
+# single connection, without waiting for Squid to respond to the first
+# of those requests. This option limits the number of concurrent
+# requests Squid will try to handle in parallel. If set to N, Squid
+# will try to receive and process up to 1+N requests on the same
+# connection concurrently.
+#
+# Defaults to 0 (off) for bandwidth management and access logging
+# reasons.
+#
+# NOTE: pipelining requires persistent connections to clients.
+#
+# WARNING: pipelining breaks NTLM and Negotiate/Kerberos authentication.
+#Default:
+# Do not pre-parse pipelined requests.
+
+# TAG: high_response_time_warning (msec)
+# If the one-minute median response time exceeds this value,
+# Squid prints a WARNING with debug level 0 to get the
+# administrators attention. The value is in milliseconds.
+#Default:
+# disabled.
+
+# TAG: high_page_fault_warning
+# If the one-minute average page fault rate exceeds this
+# value, Squid prints a WARNING with debug level 0 to get
+# the administrators attention. The value is in page faults
+# per second.
+#Default:
+# disabled.
+
+# TAG: high_memory_warning
+# Note: This option is only available if Squid is rebuilt with the
+# GNU Malloc with mstats()
+#
+# If the memory usage (as determined by gnumalloc, if available and used)
+# exceeds this amount, Squid prints a WARNING with debug level 0 to get
+# the administrators attention.
+#Default:
+# disabled.
+
+# TAG: sleep_after_fork (microseconds)
+# When this is set to a non-zero value, the main Squid process
+# sleeps the specified number of microseconds after a fork()
+# system call. This sleep may help the situation where your
+# system reports fork() failures due to lack of (virtual)
+# memory. Note, however, if you have a lot of child
+# processes, these sleep delays will add up and your
+# Squid will not service requests for some amount of time
+# until all the child processes have been started.
+# On Windows value less then 1000 (1 milliseconds) are
+# rounded to 1000.
+#Default:
+# sleep_after_fork 0
+
+# TAG: windows_ipaddrchangemonitor on|off
+# Note: This option is only available if Squid is rebuilt with the
+# MS Windows
+#
+# On Windows Squid by default will monitor IP address changes and will
+# reconfigure itself after any detected event. This is very useful for
+# proxies connected to internet with dial-up interfaces.
+# In some cases (a Proxy server acting as VPN gateway is one) it could be
+# desiderable to disable this behaviour setting this to 'off'.
+# Note: after changing this, Squid service must be restarted.
+#Default:
+# windows_ipaddrchangemonitor on
+
+# TAG: eui_lookup
+# Whether to lookup the EUI or MAC address of a connected client.
+#Default:
+# eui_lookup on
+
+# TAG: max_filedescriptors
+# Reduce the maximum number of filedescriptors supported below
+# the usual operating system defaults.
+#
+# Remove from squid.conf to inherit the current ulimit setting.
+#
+# Note: Changing this requires a restart of Squid. Also
+# not all I/O types supports large values (eg on Windows).
+#Default:
+# Use operating system limits set by ulimit.
+
+# TAG: force_request_body_continuation
+# This option controls how Squid handles data upload requests from HTTP
+# and FTP agents that require a "Please Continue" control message response
+# to actually send the request body to Squid. It is mostly useful in
+# adaptation environments.
+#
+# When Squid receives an HTTP request with an "Expect: 100-continue"
+# header or an FTP upload command (e.g., STOR), Squid normally sends the
+# request headers or FTP command information to an adaptation service (or
+# peer) and waits for a response. Most adaptation services (and some
+# broken peers) may not respond to Squid at that stage because they may
+# decide to wait for the HTTP request body or FTP data transfer. However,
+# that request body or data transfer may never come because Squid has not
+# responded with the HTTP 100 or FTP 150 (Please Continue) control message
+# to the request sender yet!
+#
+# An allow match tells Squid to respond with the HTTP 100 or FTP 150
+# (Please Continue) control message on its own, before forwarding the
+# request to an adaptation service or peer. Such a response usually forces
+# the request sender to proceed with sending the body. A deny match tells
+# Squid to delay that control response until the origin server confirms
+# that the request body is needed. Delaying is the default behavior.
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: server_pconn_for_nonretriable
+# This option provides fine-grained control over persistent connection
+# reuse when forwarding HTTP requests that Squid cannot retry. It is useful
+# in environments where opening new connections is very expensive
+# (e.g., all connections are secured with TLS with complex client and server
+# certificate validation) and race conditions associated with persistent
+# connections are very rare and/or only cause minor problems.
+#
+# HTTP prohibits retrying unsafe and non-idempotent requests (e.g., POST).
+# Squid limitations also prohibit retrying all requests with bodies (e.g., PUT).
+# By default, when forwarding such "risky" requests, Squid opens a new
+# connection to the server or cache_peer, even if there is an idle persistent
+# connection available. When Squid is configured to risk sending a non-retriable
+# request on a previously used persistent connection, and the server closes
+# the connection before seeing that risky request, the user gets an error response
+# from Squid. In most cases, that error response will be HTTP 502 (Bad Gateway)
+# with ERR_ZERO_SIZE_OBJECT or ERR_WRITE_ERROR (peer connection reset) error detail.
+#
+# If an allow rule matches, Squid reuses an available idle persistent connection
+# (if any) for the request that Squid cannot retry. If a deny rule matches, then
+# Squid opens a new connection for the request that Squid cannot retry.
+#
+# This option does not affect requests that Squid can retry. They will reuse idle
+# persistent connections (if any).
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# Example:
+# acl SpeedIsWorthTheRisk method POST
+# server_pconn_for_nonretriable allow SpeedIsWorthTheRisk
+#Default:
+# Open new connections for forwarding requests Squid cannot retry safely.
+
diff --git a/roles/squid/files/squid.s-proxy.conf.old b/roles/squid/files/squid.s-proxy.conf.old
new file mode 100644
index 0000000..b9e46ab
--- /dev/null
+++ b/roles/squid/files/squid.s-proxy.conf.old
@@ -0,0 +1,7656 @@
+# WELCOME TO SQUID 3.4.8
+# ----------------------------
+#
+# This is the documentation for the Squid configuration file.
+# This documentation can also be found online at:
+# http://www.squid-cache.org/Doc/config/
+#
+# You may wish to look at the Squid home page and wiki for the
+# FAQ and other documentation:
+# http://www.squid-cache.org/
+# http://wiki.squid-cache.org/SquidFaq
+# http://wiki.squid-cache.org/ConfigExamples
+#
+# This documentation shows what the defaults for various directives
+# happen to be. If you don't need to change the default, you should
+# leave the line out of your squid.conf in most cases.
+#
+# In some cases "none" refers to no default setting at all,
+# while in other cases it refers to the value of the option
+# - the comments for that keyword indicate if this is the case.
+#
+
+# Configuration options can be included using the "include" directive.
+# Include takes a list of files to include. Quoting and wildcards are
+# supported.
+#
+# For example,
+#
+# include /path/to/included/file/squid.acl.config
+#
+# Includes can be nested up to a hard-coded depth of 16 levels.
+# This arbitrary restriction is to prevent recursive include references
+# from causing Squid entering an infinite loop whilst trying to load
+# configuration files.
+#
+# Values with byte units
+#
+# Squid accepts size units on some size related directives. All
+# such directives are documented with a default value displaying
+# a unit.
+#
+# Units accepted by Squid are:
+# bytes - byte
+# KB - Kilobyte (1024 bytes)
+# MB - Megabyte
+# GB - Gigabyte
+#
+# Values with spaces, quotes, and other special characters
+#
+# Squid supports directive parameters with spaces, quotes, and other
+# special characters. Surround such parameters with "double quotes". Use
+# the configuration_includes_quoted_values directive to enable or
+# disable that support.
+#
+# For example;
+#
+# configuration_includes_quoted_values on
+# acl group external groupCheck Administrators "Internet Users" Guest
+# configuration_includes_quoted_values off
+#
+#
+# Conditional configuration
+#
+# If-statements can be used to make configuration directives
+# depend on conditions:
+#
+# if <CONDITION>
+# ... regular configuration directives ...
+# [else
+# ... regular configuration directives ...]
+# endif
+#
+# The else part is optional. The keywords "if", "else", and "endif"
+# must be typed on their own lines, as if they were regular
+# configuration directives.
+#
+# NOTE: An else-if condition is not supported.
+#
+# These individual conditions types are supported:
+#
+# true
+# Always evaluates to true.
+# false
+# Always evaluates to false.
+# <integer> = <integer>
+# Equality comparison of two integer numbers.
+#
+#
+# SMP-Related Macros
+#
+# The following SMP-related preprocessor macros can be used.
+#
+# ${process_name} expands to the current Squid process "name"
+# (e.g., squid1, squid2, or cache1).
+#
+# ${process_number} expands to the current Squid process
+# identifier, which is an integer number (e.g., 1, 2, 3) unique
+# across all Squid processes.
+
+# TAG: broken_vary_encoding
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: cache_vary
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: collapsed_forwarding
+# This option is not yet supported by Squid-3. see http://bugs.squid-cache.org/show_bug.cgi?id=3495
+#Default:
+# none
+
+# TAG: error_map
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: external_refresh_check
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: location_rewrite_program
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: refresh_stale_hit
+# This option is not yet supported by Squid-3.
+#Default:
+# none
+
+# TAG: ignore_ims_on_miss
+# Remove this line. The HTTP/1.1 feature is now configured by 'cache_miss_revalidate'.
+#Default:
+# none
+
+# TAG: ignore_expect_100
+# Remove this line. The HTTP/1.1 feature is now fully supported by default.
+#Default:
+# none
+
+# TAG: dns_v4_fallback
+# Remove this line. Squid performs a 'Happy Eyeballs' algorithm, the 'fallback' algorithm is no longer relevant.
+#Default:
+# none
+
+# TAG: ftp_list_width
+# Remove this line. Configure FTP page display using the CSS controls in errorpages.css instead.
+#Default:
+# none
+
+# TAG: maximum_single_addr_tries
+# Replaced by connect_retries. The behaviour has changed, please read the documentation before altering.
+#Default:
+# none
+
+# TAG: update_headers
+# Remove this line. The feature is supported by default in storage types where update is implemented.
+#Default:
+# none
+
+# TAG: url_rewrite_concurrency
+# Remove this line. Set the 'concurrency=' option of url_rewrite_children instead.
+#Default:
+# none
+
+# TAG: dns_testnames
+# Remove this line. DNS is no longer tested on startup.
+#Default:
+# none
+
+# TAG: extension_methods
+# Remove this line. All valid methods for HTTP are accepted by default.
+#Default:
+# none
+
+# TAG: zero_buffers
+#Default:
+# none
+
+# TAG: incoming_rate
+#Default:
+# none
+
+# TAG: server_http11
+# Remove this line. HTTP/1.1 is supported by default.
+#Default:
+# none
+
+# TAG: upgrade_http0.9
+# Remove this line. ICY/1.0 streaming protocol is supported by default.
+#Default:
+# none
+
+# TAG: zph_local
+# Alter these entries. Use the qos_flows directive instead.
+#Default:
+# none
+
+# TAG: header_access
+# Since squid-3.0 replace with request_header_access or reply_header_access
+# depending on whether you wish to match client requests or server replies.
+#Default:
+# none
+
+# TAG: httpd_accel_no_pmtu_disc
+# Since squid-3.0 use the 'disable-pmtu-discovery' flag on http_port instead.
+#Default:
+# none
+
+# TAG: wais_relay_host
+# Replace this line with 'cache_peer' configuration.
+#Default:
+# none
+
+# TAG: wais_relay_port
+# Replace this line with 'cache_peer' configuration.
+#Default:
+# none
+
+# OPTIONS FOR AUTHENTICATION
+# -----------------------------------------------------------------------------
+
+# TAG: auth_param
+# This is used to define parameters for the various authentication
+# schemes supported by Squid.
+#
+# format: auth_param scheme parameter [setting]
+#
+# The order in which authentication schemes are presented to the client is
+# dependent on the order the scheme first appears in config file. IE
+# has a bug (it's not RFC 2617 compliant) in that it will use the basic
+# scheme if basic is the first entry presented, even if more secure
+# schemes are presented. For now use the order in the recommended
+# settings section below. If other browsers have difficulties (don't
+# recognize the schemes offered even if you are using basic) either
+# put basic first, or disable the other schemes (by commenting out their
+# program entry).
+#
+# Once an authentication scheme is fully configured, it can only be
+# shutdown by shutting squid down and restarting. Changes can be made on
+# the fly and activated with a reconfigure. I.E. You can change to a
+# different helper, but not unconfigure the helper completely.
+#
+# Please note that while this directive defines how Squid processes
+# authentication it does not automatically activate authentication.
+# To use authentication you must in addition make use of ACLs based
+# on login name in http_access (proxy_auth, proxy_auth_regex or
+# external with %LOGIN used in the format tag). The browser will be
+# challenged for authentication on the first such acl encountered
+# in http_access processing and will also be re-challenged for new
+# login credentials if the request is being denied by a proxy_auth
+# type acl.
+#
+# WARNING: authentication can't be used in a transparently intercepting
+# proxy as the client then thinks it is talking to an origin server and
+# not the proxy. This is a limitation of bending the TCP/IP protocol to
+# transparently intercepting port 80, not a limitation in Squid.
+# Ports flagged 'transparent', 'intercept', or 'tproxy' have
+# authentication disabled.
+#
+# === Parameters for the basic scheme follow. ===
+#
+# "program" cmdline
+# Specify the command for the external authenticator. Such a program
+# reads a line containing "username password" and replies with one of
+# three results:
+#
+# OK
+# the user exists.
+#
+# ERR
+# the user does not exist.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified.
+#
+# "ERR" and "BH" results may optionally be followed by message="..."
+# containing a description available as %m in the returned error page.
+#
+# If you use an authenticator, make sure you have 1 acl of type
+# proxy_auth.
+#
+# By default, the basic authentication scheme is not used unless a
+# program is specified.
+#
+# If you want to use the traditional NCSA proxy authentication, set
+# this line to something like
+#
+# auth_param basic program /usr/lib/squid3/basic_ncsa_auth /usr/etc/passwd
+#
+# "utf8" on|off
+# HTTP uses iso-latin-1 as character set, while some authentication
+# backends such as LDAP expects UTF-8. If this is set to on Squid will
+# translate the HTTP iso-latin-1 charset to UTF-8 before sending the
+# username & password to the helper.
+#
+# "children" numberofchildren [startup=N] [idle=N] [concurrency=N]
+# The maximum number of authenticator processes to spawn. If you start too few
+# Squid will have to wait for them to process a backlog of credential
+# verifications, slowing it down. When password verifications are
+# done via a (slow) network you are likely to need lots of
+# authenticator processes.
+#
+# The startup= and idle= options permit some skew in the exact amount
+# run. A minimum of startup=N will begin during startup and reconfigure.
+# Squid will start more in groups of up to idle=N in an attempt to meet
+# traffic needs and to keep idle=N free above those traffic needs up to
+# the maximum.
+#
+# The concurrency= option sets the number of concurrent requests the
+# helper can process. The default of 0 is used for helpers who only
+# supports one request at a time. Setting this to a number greater than
+# 0 changes the protocol used to include a channel number first on the
+# request/response line, allowing multiple requests to be sent to the
+# same helper in parallel without waiting for the response.
+# Must not be set unless it's known the helper supports this.
+#
+# auth_param basic children 20 startup=0 idle=1
+#
+# "realm" realmstring
+# Specifies the realm name which is to be reported to the
+# client for the basic proxy authentication scheme (part of
+# the text the user will see when prompted their username and
+# password). There is no default.
+# auth_param basic realm Squid proxy-caching web server
+#
+# "credentialsttl" timetolive
+# Specifies how long squid assumes an externally validated
+# username:password pair is valid for - in other words how
+# often the helper program is called for that user. Set this
+# low to force revalidation with short lived passwords. Note
+# setting this high does not impact your susceptibility
+# to replay attacks unless you are using an one-time password
+# system (such as SecureID). If you are using such a system,
+# you will be vulnerable to replay attacks unless you also
+# use the max_user_ip ACL in an http_access rule.
+#
+# "casesensitive" on|off
+# Specifies if usernames are case sensitive. Most user databases are
+# case insensitive allowing the same username to be spelled using both
+# lower and upper case letters, but some are case sensitive. This
+# makes a big difference for user_max_ip ACL processing and similar.
+# auth_param basic casesensitive off
+#
+# === Parameters for the digest scheme follow ===
+#
+# "program" cmdline
+# Specify the command for the external authenticator. Such
+# a program reads a line containing "username":"realm" and
+# replies with one of three results:
+#
+# OK ha1="..."
+# the user exists. The ha1= key is mandatory and
+# contains the appropriate H(A1) value, hex encoded.
+# See rfc 2616 for the definition of H(A1).
+#
+# ERR
+# the user does not exist.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified.
+#
+# "ERR" and "BH" results may optionally be followed by message="..."
+# containing a description available as %m in the returned error page.
+#
+# By default, the digest authentication scheme is not used unless a
+# program is specified.
+#
+# If you want to use a digest authenticator, set this line to
+# something like
+#
+# auth_param digest program /usr/lib/squid3/digest_pw_auth /usr/etc/digpass
+#
+# "utf8" on|off
+# HTTP uses iso-latin-1 as character set, while some authentication
+# backends such as LDAP expects UTF-8. If this is set to on Squid will
+# translate the HTTP iso-latin-1 charset to UTF-8 before sending the
+# username & password to the helper.
+#
+# "children" numberofchildren [startup=N] [idle=N] [concurrency=N]
+# The maximum number of authenticator processes to spawn (default 5).
+# If you start too few Squid will have to wait for them to
+# process a backlog of H(A1) calculations, slowing it down.
+# When the H(A1) calculations are done via a (slow) network
+# you are likely to need lots of authenticator processes.
+#
+# The startup= and idle= options permit some skew in the exact amount
+# run. A minimum of startup=N will begin during startup and reconfigure.
+# Squid will start more in groups of up to idle=N in an attempt to meet
+# traffic needs and to keep idle=N free above those traffic needs up to
+# the maximum.
+#
+# The concurrency= option sets the number of concurrent requests the
+# helper can process. The default of 0 is used for helpers who only
+# supports one request at a time. Setting this to a number greater than
+# 0 changes the protocol used to include a channel number first on the
+# request/response line, allowing multiple requests to be sent to the
+# same helper in parallel without waiting for the response.
+# Must not be set unless it's known the helper supports this.
+#
+# auth_param digest children 20 startup=0 idle=1
+#
+# "realm" realmstring
+# Specifies the realm name which is to be reported to the
+# client for the digest proxy authentication scheme (part of
+# the text the user will see when prompted their username and
+# password). There is no default.
+# auth_param digest realm Squid proxy-caching web server
+#
+# "nonce_garbage_interval" timeinterval
+# Specifies the interval that nonces that have been issued
+# to client_agent's are checked for validity.
+#
+# "nonce_max_duration" timeinterval
+# Specifies the maximum length of time a given nonce will be
+# valid for.
+#
+# "nonce_max_count" number
+# Specifies the maximum number of times a given nonce can be
+# used.
+#
+# "nonce_strictness" on|off
+# Determines if squid requires strict increment-by-1 behavior
+# for nonce counts, or just incrementing (off - for use when
+# user agents generate nonce counts that occasionally miss 1
+# (ie, 1,2,4,6)). Default off.
+#
+# "check_nonce_count" on|off
+# This directive if set to off can disable the nonce count check
+# completely to work around buggy digest qop implementations in
+# certain mainstream browser versions. Default on to check the
+# nonce count to protect from authentication replay attacks.
+#
+# "post_workaround" on|off
+# This is a workaround to certain buggy browsers who sends
+# an incorrect request digest in POST requests when reusing
+# the same nonce as acquired earlier on a GET request.
+#
+# === NTLM scheme options follow ===
+#
+# "program" cmdline
+# Specify the command for the external NTLM authenticator.
+# Such a program reads exchanged NTLMSSP packets with
+# the browser via Squid until authentication is completed.
+# If you use an NTLM authenticator, make sure you have 1 acl
+# of type proxy_auth. By default, the NTLM authenticator program
+# is not used.
+#
+# NOTE: In Debian the ntlm_auth program is distributed in the winbindd package
+# which is required for this auth scheme to work
+#
+# auth_param ntlm program /usr/bin/ntlm_auth
+#
+# "children" numberofchildren [startup=N] [idle=N]
+# The maximum number of authenticator processes to spawn (default 5).
+# If you start too few Squid will have to wait for them to
+# process a backlog of credential verifications, slowing it
+# down. When credential verifications are done via a (slow)
+# network you are likely to need lots of authenticator
+# processes.
+#
+# The startup= and idle= options permit some skew in the exact amount
+# run. A minimum of startup=N will begin during startup and reconfigure.
+# Squid will start more in groups of up to idle=N in an attempt to meet
+# traffic needs and to keep idle=N free above those traffic needs up to
+# the maximum.
+#
+# auth_param ntlm children 20 startup=0 idle=1
+#
+# "keep_alive" on|off
+# If you experience problems with PUT/POST requests when using the
+# Negotiate authentication scheme then you can try setting this to
+# off. This will cause Squid to forcibly close the connection on
+# the initial requests where the browser asks which schemes are
+# supported by the proxy.
+#
+# auth_param ntlm keep_alive on
+#
+# === Options for configuring the NEGOTIATE auth-scheme follow ===
+#
+# "program" cmdline
+# Specify the command for the external Negotiate authenticator.
+# This protocol is used in Microsoft Active-Directory enabled setups with
+# the Microsoft Internet Explorer or Mozilla Firefox browsers.
+# Its main purpose is to exchange credentials with the Squid proxy
+# using the Kerberos mechanisms.
+# If you use a Negotiate authenticator, make sure you have at least
+# one acl of type proxy_auth active. By default, the negotiate
+# authenticator program is not used.
+# The only supported program for this role is the ntlm_auth
+# program distributed as part of Samba, version 4 or later.
+#
+# NOTE: In Debian the ntlm_auth program is distributed in the winbindd package
+# which is required for this auth scheme to work
+#
+# auth_param negotiate program /usr/bin/ntlm_auth --helper-protocol=gss-spnego
+#
+# "children" numberofchildren [startup=N] [idle=N]
+# The maximum number of authenticator processes to spawn (default 5).
+# If you start too few Squid will have to wait for them to
+# process a backlog of credential verifications, slowing it
+# down. When credential verifications are done via a (slow)
+# network you are likely to need lots of authenticator
+# processes.
+#
+# The startup= and idle= options permit some skew in the exact amount
+# run. A minimum of startup=N will begin during startup and reconfigure.
+# Squid will start more in groups of up to idle=N in an attempt to meet
+# traffic needs and to keep idle=N free above those traffic needs up to
+# the maximum.
+#
+# auth_param negotiate children 20 startup=0 idle=1
+#
+# "keep_alive" on|off
+# If you experience problems with PUT/POST requests when using the
+# Negotiate authentication scheme then you can try setting this to
+# off. This will cause Squid to forcibly close the connection on
+# the initial requests where the browser asks which schemes are
+# supported by the proxy.
+#
+# auth_param negotiate keep_alive on
+#
+#
+# Examples:
+#
+##Recommended minimum configuration per scheme:
+##auth_param negotiate program <uncomment and complete this line to activate>
+##auth_param negotiate children 20 startup=0 idle=1
+##auth_param negotiate keep_alive on
+##
+##auth_param ntlm program <uncomment and complete this line to activate>
+##auth_param ntlm children 20 startup=0 idle=1
+##auth_param ntlm keep_alive on
+##
+##auth_param digest program <uncomment and complete this line>
+##auth_param digest children 20 startup=0 idle=1
+##auth_param digest realm Squid proxy-caching web server
+##auth_param digest nonce_garbage_interval 5 minutes
+##auth_param digest nonce_max_duration 30 minutes
+##auth_param digest nonce_max_count 50
+##
+##auth_param basic program <uncomment and complete this line>
+##auth_param basic children 5 startup=5 idle=1
+##auth_param basic realm Squid proxy-caching web server
+##auth_param basic credentialsttl 2 hours
+#Default:
+# none
+
+# TAG: authenticate_cache_garbage_interval
+# The time period between garbage collection across the username cache.
+# This is a trade-off between memory utilization (long intervals - say
+# 2 days) and CPU (short intervals - say 1 minute). Only change if you
+# have good reason to.
+#Default:
+# authenticate_cache_garbage_interval 1 hour
+
+# TAG: authenticate_ttl
+# The time a user & their credentials stay in the logged in
+# user cache since their last request. When the garbage
+# interval passes, all user credentials that have passed their
+# TTL are removed from memory.
+#Default:
+# authenticate_ttl 1 hour
+
+# TAG: authenticate_ip_ttl
+# If you use proxy authentication and the 'max_user_ip' ACL,
+# this directive controls how long Squid remembers the IP
+# addresses associated with each user. Use a small value
+# (e.g., 60 seconds) if your users might change addresses
+# quickly, as is the case with dialup. You might be safe
+# using a larger value (e.g., 2 hours) in a corporate LAN
+# environment with relatively static address assignments.
+#Default:
+# authenticate_ip_ttl 1 second
+
+# ACCESS CONTROLS
+# -----------------------------------------------------------------------------
+
+# TAG: external_acl_type
+# This option defines external acl classes using a helper program
+# to look up the status
+#
+# external_acl_type name [options] FORMAT.. /path/to/helper [helper arguments..]
+#
+# Options:
+#
+# ttl=n TTL in seconds for cached results (defaults to 3600
+# for 1 hour)
+# negative_ttl=n
+# TTL for cached negative lookups (default same
+# as ttl)
+# children-max=n
+# Maximum number of acl helper processes spawned to service
+# external acl lookups of this type. (default 20)
+# children-startup=n
+# Minimum number of acl helper processes to spawn during
+# startup and reconfigure to service external acl lookups
+# of this type. (default 0)
+# children-idle=n
+# Number of acl helper processes to keep ahead of traffic
+# loads. Squid will spawn this many at once whenever load
+# rises above the capabilities of existing processes.
+# Up to the value of children-max. (default 1)
+# concurrency=n concurrency level per process. Only used with helpers
+# capable of processing more than one query at a time.
+# cache=n limit the result cache size, default is 262144.
+# grace=n Percentage remaining of TTL where a refresh of a
+# cached entry should be initiated without needing to
+# wait for a new reply. (default is for no grace period)
+# protocol=2.5 Compatibility mode for Squid-2.5 external acl helpers
+# ipv4 / ipv6 IP protocol used to communicate with this helper.
+# The default is to auto-detect IPv6 and use it when available.
+#
+# FORMAT specifications
+#
+# %LOGIN Authenticated user login name
+# %EXT_USER Username from previous external acl
+# %EXT_LOG Log details from previous external acl
+# %EXT_TAG Tag from previous external acl
+# %IDENT Ident user name
+# %SRC Client IP
+# %SRCPORT Client source port
+# %URI Requested URI
+# %DST Requested host
+# %PROTO Requested protocol
+# %PORT Requested port
+# %PATH Requested URL path
+# %METHOD Request method
+# %MYADDR Squid interface address
+# %MYPORT Squid http_port number
+# %PATH Requested URL-path (including query-string if any)
+# %USER_CERT SSL User certificate in PEM format
+# %USER_CERTCHAIN SSL User certificate chain in PEM format
+# %USER_CERT_xx SSL User certificate subject attribute xx
+# %USER_CA_CERT_xx SSL User certificate issuer attribute xx
+#
+# %>{Header} HTTP request header "Header"
+# %>{Hdr:member}
+# HTTP request header "Hdr" list member "member"
+# %>{Hdr:;member}
+# HTTP request header list member using ; as
+# list separator. ; can be any non-alphanumeric
+# character.
+#
+# %<{Header} HTTP reply header "Header"
+# %<{Hdr:member}
+# HTTP reply header "Hdr" list member "member"
+# %<{Hdr:;member}
+# HTTP reply header list member using ; as
+# list separator. ; can be any non-alphanumeric
+# character.
+#
+# %ACL The name of the ACL being tested.
+# %DATA The ACL arguments. If not used then any arguments
+# is automatically added at the end of the line
+# sent to the helper.
+# NOTE: this will encode the arguments as one token,
+# whereas the default will pass each separately.
+#
+# %% The percent sign. Useful for helpers which need
+# an unchanging input format.
+#
+#
+# General request syntax:
+#
+# [channel-ID] FORMAT-values [acl-values ...]
+#
+#
+# FORMAT-values consists of transaction details expanded with
+# whitespace separation per the config file FORMAT specification
+# using the FORMAT macros listed above.
+#
+# acl-values consists of any string specified in the referencing
+# config 'acl ... external' line. see the "acl external" directive.
+#
+# Request values sent to the helper are URL escaped to protect
+# each value in requests against whitespaces.
+#
+# If using protocol=2.5 then the request sent to the helper is not
+# URL escaped to protect against whitespace.
+#
+# NOTE: protocol=3.0 is deprecated as no longer necessary.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+#
+# The helper receives lines expanded per the above format specification
+# and for each input line returns 1 line starting with OK/ERR/BH result
+# code and optionally followed by additional keywords with more details.
+#
+#
+# General result syntax:
+#
+# [channel-ID] result keyword=value ...
+#
+# Result consists of one of the codes:
+#
+# OK
+# the ACL test produced a match.
+#
+# ERR
+# the ACL test does not produce a match.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified.
+#
+# The meaning of 'a match' is determined by your squid.conf
+# access control configuration. See the Squid wiki for details.
+#
+# Defined keywords:
+#
+# user= The users name (login)
+#
+# password= The users password (for login= cache_peer option)
+#
+# message= Message describing the reason for this response.
+# Available as %o in error pages.
+# Useful on (ERR and BH results).
+#
+# tag= Apply a tag to a request. Only sets a tag once,
+# does not alter existing tags.
+#
+# log= String to be logged in access.log. Available as
+# %ea in logformat specifications.
+#
+# Any keywords may be sent on any response whether OK, ERR or BH.
+#
+# All response keyword values need to be a single token with URL
+# escaping, or enclosed in double quotes (") and escaped using \ on
+# any double quotes or \ characters within the value. The wrapping
+# double quotes are removed before the value is interpreted by Squid.
+# \r and \n are also replace by CR and LF.
+#
+# Some example key values:
+#
+# user=John%20Smith
+# user="John Smith"
+# user="J. \"Bob\" Smith"
+#Default:
+# none
+
+# TAG: acl
+# Defining an Access List
+#
+# Every access list definition must begin with an aclname and acltype,
+# followed by either type-specific arguments or a quoted filename that
+# they are read from.
+#
+# acl aclname acltype argument ...
+# acl aclname acltype "file" ...
+#
+# When using "file", the file should contain one item per line.
+#
+# Some acl types supports options which changes their default behaviour.
+# The available options are:
+#
+# -i,+i By default, regular expressions are CASE-SENSITIVE. To make them
+# case-insensitive, use the -i option. To return case-sensitive
+# use the +i option between patterns, or make a new ACL line
+# without -i.
+#
+# -n Disable lookups and address type conversions. If lookup or
+# conversion is required because the parameter type (IP or
+# domain name) does not match the message address type (domain
+# name or IP), then the ACL would immediately declare a mismatch
+# without any warnings or lookups.
+#
+# -- Used to stop processing all options, in the case the first acl
+# value has '-' character as first character (for example the '-'
+# is a valid domain name)
+#
+# Some acl types require suspending the current request in order
+# to access some external data source.
+# Those which do are marked with the tag [slow], those which
+# don't are marked as [fast].
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl
+# for further information
+#
+# ***** ACL TYPES AVAILABLE *****
+#
+# acl aclname src ip-address/mask ... # clients IP address [fast]
+# acl aclname src addr1-addr2/mask ... # range of addresses [fast]
+# acl aclname dst [-n] ip-address/mask ... # URL host's IP address [slow]
+# acl aclname localip ip-address/mask ... # IP address the client connected to [fast]
+#
+# acl aclname arp mac-address ... (xx:xx:xx:xx:xx:xx notation)
+# # The arp ACL requires the special configure option --enable-arp-acl.
+# # Furthermore, the ARP ACL code is not portable to all operating systems.
+# # It works on Linux, Solaris, Windows, FreeBSD, and some
+# # other *BSD variants.
+# # [fast]
+# #
+# # NOTE: Squid can only determine the MAC address for clients that are on
+# # the same subnet. If the client is on a different subnet,
+# # then Squid cannot find out its MAC address.
+#
+# acl aclname srcdomain .foo.com ...
+# # reverse lookup, from client IP [slow]
+# acl aclname dstdomain [-n] .foo.com ...
+# # Destination server from URL [fast]
+# acl aclname srcdom_regex [-i] \.foo\.com ...
+# # regex matching client name [slow]
+# acl aclname dstdom_regex [-n] [-i] \.foo\.com ...
+# # regex matching server [fast]
+# #
+# # For dstdomain and dstdom_regex a reverse lookup is tried if a IP
+# # based URL is used and no match is found. The name "none" is used
+# # if the reverse lookup fails.
+#
+# acl aclname src_as number ...
+# acl aclname dst_as number ...
+# # [fast]
+# # Except for access control, AS numbers can be used for
+# # routing of requests to specific caches. Here's an
+# # example for routing all requests for AS#1241 and only
+# # those to mycache.mydomain.net:
+# # acl asexample dst_as 1241
+# # cache_peer_access mycache.mydomain.net allow asexample
+# # cache_peer_access mycache_mydomain.net deny all
+#
+# acl aclname peername myPeer ...
+# # [fast]
+# # match against a named cache_peer entry
+# # set unique name= on cache_peer lines for reliable use.
+#
+# acl aclname time [day-abbrevs] [h1:m1-h2:m2]
+# # [fast]
+# # day-abbrevs:
+# # S - Sunday
+# # M - Monday
+# # T - Tuesday
+# # W - Wednesday
+# # H - Thursday
+# # F - Friday
+# # A - Saturday
+# # h1:m1 must be less than h2:m2
+#
+# acl aclname url_regex [-i] ^http:// ...
+# # regex matching on whole URL [fast]
+# acl aclname urllogin [-i] [^a-zA-Z0-9] ...
+# # regex matching on URL login field
+# acl aclname urlpath_regex [-i] \.gif$ ...
+# # regex matching on URL path [fast]
+#
+# acl aclname port 80 70 21 0-1024... # destination TCP port [fast]
+# # ranges are alloed
+# acl aclname localport 3128 ... # TCP port the client connected to [fast]
+# # NP: for interception mode this is usually '80'
+#
+# acl aclname myportname 3128 ... # http(s)_port name [fast]
+#
+# acl aclname proto HTTP FTP ... # request protocol [fast]
+#
+# acl aclname method GET POST ... # HTTP request method [fast]
+#
+# acl aclname http_status 200 301 500- 400-403 ...
+# # status code in reply [fast]
+#
+# acl aclname browser [-i] regexp ...
+# # pattern match on User-Agent header (see also req_header below) [fast]
+#
+# acl aclname referer_regex [-i] regexp ...
+# # pattern match on Referer header [fast]
+# # Referer is highly unreliable, so use with care
+#
+# acl aclname ident username ...
+# acl aclname ident_regex [-i] pattern ...
+# # string match on ident output [slow]
+# # use REQUIRED to accept any non-null ident.
+#
+# acl aclname proxy_auth [-i] username ...
+# acl aclname proxy_auth_regex [-i] pattern ...
+# # perform http authentication challenge to the client and match against
+# # supplied credentials [slow]
+# #
+# # takes a list of allowed usernames.
+# # use REQUIRED to accept any valid username.
+# #
+# # Will use proxy authentication in forward-proxy scenarios, and plain
+# # http authenticaiton in reverse-proxy scenarios
+# #
+# # NOTE: when a Proxy-Authentication header is sent but it is not
+# # needed during ACL checking the username is NOT logged
+# # in access.log.
+# #
+# # NOTE: proxy_auth requires a EXTERNAL authentication program
+# # to check username/password combinations (see
+# # auth_param directive).
+# #
+# # NOTE: proxy_auth can't be used in a transparent/intercepting proxy
+# # as the browser needs to be configured for using a proxy in order
+# # to respond to proxy authentication.
+#
+# acl aclname snmp_community string ...
+# # A community string to limit access to your SNMP Agent [fast]
+# # Example:
+# #
+# # acl snmppublic snmp_community public
+#
+# acl aclname maxconn number
+# # This will be matched when the client's IP address has
+# # more than <number> TCP connections established. [fast]
+# # NOTE: This only measures direct TCP links so X-Forwarded-For
+# # indirect clients are not counted.
+#
+# acl aclname max_user_ip [-s] number
+# # This will be matched when the user attempts to log in from more
+# # than <number> different ip addresses. The authenticate_ip_ttl
+# # parameter controls the timeout on the ip entries. [fast]
+# # If -s is specified the limit is strict, denying browsing
+# # from any further IP addresses until the ttl has expired. Without
+# # -s Squid will just annoy the user by "randomly" denying requests.
+# # (the counter is reset each time the limit is reached and a
+# # request is denied)
+# # NOTE: in acceleration mode or where there is mesh of child proxies,
+# # clients may appear to come from multiple addresses if they are
+# # going through proxy farms, so a limit of 1 may cause user problems.
+#
+# acl aclname random probability
+# # Pseudo-randomly match requests. Based on the probability given.
+# # Probability may be written as a decimal (0.333), fraction (1/3)
+# # or ratio of matches:non-matches (3:5).
+#
+# acl aclname req_mime_type [-i] mime-type ...
+# # regex match against the mime type of the request generated
+# # by the client. Can be used to detect file upload or some
+# # types HTTP tunneling requests [fast]
+# # NOTE: This does NOT match the reply. You cannot use this
+# # to match the returned file type.
+#
+# acl aclname req_header header-name [-i] any\.regex\.here
+# # regex match against any of the known request headers. May be
+# # thought of as a superset of "browser", "referer" and "mime-type"
+# # ACL [fast]
+#
+# acl aclname rep_mime_type [-i] mime-type ...
+# # regex match against the mime type of the reply received by
+# # squid. Can be used to detect file download or some
+# # types HTTP tunneling requests. [fast]
+# # NOTE: This has no effect in http_access rules. It only has
+# # effect in rules that affect the reply data stream such as
+# # http_reply_access.
+#
+# acl aclname rep_header header-name [-i] any\.regex\.here
+# # regex match against any of the known reply headers. May be
+# # thought of as a superset of "browser", "referer" and "mime-type"
+# # ACLs [fast]
+#
+# acl aclname external class_name [arguments...]
+# # external ACL lookup via a helper class defined by the
+# # external_acl_type directive [slow]
+#
+# acl aclname user_cert attribute values...
+# # match against attributes in a user SSL certificate
+# # attribute is one of DN/C/O/CN/L/ST [fast]
+#
+# acl aclname ca_cert attribute values...
+# # match against attributes a users issuing CA SSL certificate
+# # attribute is one of DN/C/O/CN/L/ST [fast]
+#
+# acl aclname ext_user username ...
+# acl aclname ext_user_regex [-i] pattern ...
+# # string match on username returned by external acl helper [slow]
+# # use REQUIRED to accept any non-null user name.
+#
+# acl aclname tag tagvalue ...
+# # string match on tag returned by external acl helper [slow]
+#
+# acl aclname hier_code codename ...
+# # string match against squid hierarchy code(s); [fast]
+# # e.g., DIRECT, PARENT_HIT, NONE, etc.
+# #
+# # NOTE: This has no effect in http_access rules. It only has
+# # effect in rules that affect the reply data stream such as
+# # http_reply_access.
+#
+# acl aclname note name [value ...]
+# # match transaction annotation [fast]
+# # Without values, matches any annotation with a given name.
+# # With value(s), matches any annotation with a given name that
+# # also has one of the given values.
+# # Names and values are compared using a string equality test.
+# # Annotation sources include note and adaptation_meta directives
+# # as well as helper and eCAP responses.
+#
+# acl aclname any-of acl1 acl2 ...
+# # match any one of the acls [fast or slow]
+# # The first matching ACL stops further ACL evaluation.
+# #
+# # ACLs from multiple any-of lines with the same name are ORed.
+# # For example, A = (a1 or a2) or (a3 or a4) can be written as
+# # acl A any-of a1 a2
+# # acl A any-of a3 a4
+# #
+# # This group ACL is fast if all evaluated ACLs in the group are fast
+# # and slow otherwise.
+#
+# acl aclname all-of acl1 acl2 ...
+# # match all of the acls [fast or slow]
+# # The first mismatching ACL stops further ACL evaluation.
+# #
+# # ACLs from multiple all-of lines with the same name are ORed.
+# # For example, B = (b1 and b2) or (b3 and b4) can be written as
+# # acl B all-of b1 b2
+# # acl B all-of b3 b4
+# #
+# # This group ACL is fast if all evaluated ACLs in the group are fast
+# # and slow otherwise.
+#
+# Examples:
+# acl macaddress arp 09:00:2b:23:45:67
+# acl myexample dst_as 1241
+# acl password proxy_auth REQUIRED
+# acl fileupload req_mime_type -i ^multipart/form-data$
+# acl javascript rep_mime_type -i ^application/x-javascript$
+#
+#Default:
+# ACLs all, manager, localhost, and to_localhost are predefined.
+#
+#
+# Recommended minimum configuration:
+#
+
+# Example rule allowing access from your local networks.
+# Adapt to list your (internal) IP networks from where browsing
+# should be allowed
+#acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
+acl localnet src 172.16.64.0/24 # RFC1918 possible internal network
+#acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
+#acl localnet src fc00::/7 # RFC 4193 local private network range
+#acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
+
+acl SSL_ports port 443
+acl Safe_ports port 80 # http
+acl Safe_ports port 21 # ftp
+acl Safe_ports port 443 # https
+acl Safe_ports port 70 # gopher
+acl Safe_ports port 210 # wais
+acl Safe_ports port 1025-65535 # unregistered ports
+acl Safe_ports port 280 # http-mgmt
+acl Safe_ports port 488 # gss-http
+acl Safe_ports port 591 # filemaker
+acl Safe_ports port 777 # multiling http
+acl CONNECT method CONNECT
+
+# TAG: follow_x_forwarded_for
+# Allowing or Denying the X-Forwarded-For header to be followed to
+# find the original source of a request.
+#
+# Requests may pass through a chain of several other proxies
+# before reaching us. The X-Forwarded-For header will contain a
+# comma-separated list of the IP addresses in the chain, with the
+# rightmost address being the most recent.
+#
+# If a request reaches us from a source that is allowed by this
+# configuration item, then we consult the X-Forwarded-For header
+# to see where that host received the request from. If the
+# X-Forwarded-For header contains multiple addresses, we continue
+# backtracking until we reach an address for which we are not allowed
+# to follow the X-Forwarded-For header, or until we reach the first
+# address in the list. For the purpose of ACL used in the
+# follow_x_forwarded_for directive the src ACL type always matches
+# the address we are testing and srcdomain matches its rDNS.
+#
+# The end result of this process is an IP address that we will
+# refer to as the indirect client address. This address may
+# be treated as the client address for access control, ICAP, delay
+# pools and logging, depending on the acl_uses_indirect_client,
+# icap_uses_indirect_client, delay_pool_uses_indirect_client,
+# log_uses_indirect_client and tproxy_uses_indirect_client options.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# SECURITY CONSIDERATIONS:
+#
+# Any host for which we follow the X-Forwarded-For header
+# can place incorrect information in the header, and Squid
+# will use the incorrect information as if it were the
+# source address of the request. This may enable remote
+# hosts to bypass any access control restrictions that are
+# based on the client's source addresses.
+#
+# For example:
+#
+# acl localhost src 127.0.0.1
+# acl my_other_proxy srcdomain .proxy.example.com
+# follow_x_forwarded_for allow localhost
+# follow_x_forwarded_for allow my_other_proxy
+#Default:
+# X-Forwarded-For header will be ignored.
+
+# TAG: acl_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in acl matching.
+#
+# NOTE: maxconn ACL considers direct TCP links and indirect
+# clients will always have zero. So no match.
+#Default:
+# acl_uses_indirect_client on
+
+# TAG: delay_pool_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in delay pools.
+#Default:
+# delay_pool_uses_indirect_client on
+
+# TAG: log_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address in the access log.
+#Default:
+# log_uses_indirect_client on
+
+# TAG: tproxy_uses_indirect_client on|off
+# Controls whether the indirect client address
+# (see follow_x_forwarded_for) is used instead of the
+# direct client address when spoofing the outgoing client.
+#
+# This has no effect on requests arriving in non-tproxy
+# mode ports.
+#
+# SECURITY WARNING: Usage of this option is dangerous
+# and should not be used trivially. Correct configuration
+# of follow_x_forewarded_for with a limited set of trusted
+# sources is required to prevent abuse of your proxy.
+#Default:
+# tproxy_uses_indirect_client off
+
+# TAG: spoof_client_ip
+# Control client IP address spoofing of TPROXY traffic based on
+# defined access lists.
+#
+# spoof_client_ip allow|deny [!]aclname ...
+#
+# If there are no "spoof_client_ip" lines present, the default
+# is to "allow" spoofing of any suitable request.
+#
+# Note that the cache_peer "no-tproxy" option overrides this ACL.
+#
+# This clause supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow spoofing on all TPROXY traffic.
+
+# TAG: http_access
+# Allowing or Denying access based on defined access lists
+#
+# Access to the HTTP port:
+# http_access allow|deny [!]aclname ...
+#
+# NOTE on default values:
+#
+# If there are no "access" lines present, the default is to deny
+# the request.
+#
+# If none of the "access" lines cause a match, the default is the
+# opposite of the last line in the list. If the last line was
+# deny, the default is allow. Conversely, if the last line
+# is allow, the default will be deny. For these reasons, it is a
+# good idea to have an "deny all" entry at the end of your access
+# lists to avoid potential confusion.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Default:
+# Deny, unless rules exist in squid.conf.
+#
+
+#
+# Recommended minimum Access Permission configuration:
+#
+# Deny requests to certain unsafe ports
+http_access deny !Safe_ports
+
+# Deny CONNECT to other than secure SSL ports
+http_access deny CONNECT !SSL_ports
+
+# Only allow cachemgr access from localhost
+http_access allow localnet
+http_access deny all
+
+# We strongly recommend the following be uncommented to protect innocent
+# web applications running on the proxy server who think the only
+# one who can access services on "localhost" is a local user
+#http_access deny to_localhost
+
+#
+# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
+#
+
+# Example rule allowing access from your local networks.
+# Adapt localnet in the ACL section to list your (internal) IP networks
+# from where browsing should be allowed
+http_access allow localnet
+http_access allow localhost
+
+# And finally deny all other access to this proxy
+http_access deny all
+
+# TAG: adapted_http_access
+# Allowing or Denying access based on defined access lists
+#
+# Essentially identical to http_access, but runs after redirectors
+# and ICAP/eCAP adaptation. Allowing access control based on their
+# output.
+#
+# If not set then only http_access is used.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: http_reply_access
+# Allow replies to client requests. This is complementary to http_access.
+#
+# http_reply_access allow|deny [!] aclname ...
+#
+# NOTE: if there are no access lines present, the default is to allow
+# all replies.
+#
+# If none of the access lines cause a match the opposite of the
+# last line will apply. Thus it is good practice to end the rules
+# with an "allow all" or "deny all" entry.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: icp_access
+# Allowing or Denying access to the ICP port based on defined
+# access lists
+#
+# icp_access allow|deny [!]aclname ...
+#
+# NOTE: The default if no icp_access lines are present is to
+# deny all traffic. This default may cause problems with peers
+# using ICP.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow ICP queries from local networks only
+##icp_access allow localnet
+##icp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: htcp_access
+# Allowing or Denying access to the HTCP port based on defined
+# access lists
+#
+# htcp_access allow|deny [!]aclname ...
+#
+# See also htcp_clr_access for details on access control for
+# cache purge (CLR) HTCP messages.
+#
+# NOTE: The default if no htcp_access lines are present is to
+# deny all traffic. This default may cause problems with peers
+# using the htcp option.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow HTCP queries from local networks only
+##htcp_access allow localnet
+##htcp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: htcp_clr_access
+# Allowing or Denying access to purge content using HTCP based
+# on defined access lists.
+# See htcp_access for details on general HTCP access control.
+#
+# htcp_clr_access allow|deny [!]aclname ...
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+## Allow HTCP CLR requests from trusted peers
+#acl htcp_clr_peer src 192.0.2.2 2001:DB8::2
+#htcp_clr_access allow htcp_clr_peer
+#htcp_clr_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: miss_access
+# Determins whether network access is permitted when satisfying a request.
+#
+# For example;
+# to force your neighbors to use you as a sibling instead of
+# a parent.
+#
+# acl localclients src 192.0.2.0/24 2001:DB8::a:0/64
+# miss_access deny !localclients
+# miss_access allow all
+#
+# This means only your local clients are allowed to fetch relayed/MISS
+# replies from the network and all other clients can only fetch cached
+# objects (HITs).
+#
+# The default for this setting allows all clients who passed the
+# http_access rules to relay via this proxy.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: ident_lookup_access
+# A list of ACL elements which, if matched, cause an ident
+# (RFC 931) lookup to be performed for this request. For
+# example, you might choose to always perform ident lookups
+# for your main multi-user Unix boxes, but not for your Macs
+# and PCs. By default, ident lookups are not performed for
+# any requests.
+#
+# To enable ident lookups for specific client addresses, you
+# can follow this example:
+#
+# acl ident_aware_hosts src 198.168.1.0/24
+# ident_lookup_access allow ident_aware_hosts
+# ident_lookup_access deny all
+#
+# Only src type ACL checks are fully supported. A srcdomain
+# ACL might work at times, but it will not always provide
+# the correct result.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Unless rules exist in squid.conf, IDENT is not fetched.
+
+# TAG: reply_body_max_size size [acl acl...]
+# This option specifies the maximum size of a reply body. It can be
+# used to prevent users from downloading very large files, such as
+# MP3's and movies. When the reply headers are received, the
+# reply_body_max_size lines are processed, and the first line where
+# all (if any) listed ACLs are true is used as the maximum body size
+# for this reply.
+#
+# This size is checked twice. First when we get the reply headers,
+# we check the content-length value. If the content length value exists
+# and is larger than the allowed size, the request is denied and the
+# user receives an error message that says "the request or reply
+# is too large." If there is no content-length, and the reply
+# size exceeds this limit, the client's connection is just closed
+# and they will receive a partial reply.
+#
+# WARNING: downstream caches probably can not detect a partial reply
+# if there is no content-length header, so they will cache
+# partial responses and give them out as hits. You should NOT
+# use this option if you have downstream caches.
+#
+# WARNING: A maximum size smaller than the size of squid's error messages
+# will cause an infinite loop and crash squid. Ensure that the smallest
+# non-zero value you use is greater that the maximum header size plus
+# the size of your largest error page.
+#
+# If you set this parameter none (the default), there will be
+# no limit imposed.
+#
+# Configuration Format is:
+# reply_body_max_size SIZE UNITS [acl ...]
+# ie.
+# reply_body_max_size 10 MB
+#
+#Default:
+# No limit is applied.
+
+# NETWORK OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: http_port
+# Usage: port [mode] [options]
+# hostname:port [mode] [options]
+# 1.2.3.4:port [mode] [options]
+#
+# The socket addresses where Squid will listen for HTTP client
+# requests. You may specify multiple socket addresses.
+# There are three forms: port alone, hostname with port, and
+# IP address with port. If you specify a hostname or IP
+# address, Squid binds the socket to that specific
+# address. Most likely, you do not need to bind to a specific
+# address, so you can use the port number alone.
+#
+# If you are running Squid in accelerator mode, you
+# probably want to listen on port 80 also, or instead.
+#
+# The -a command line option may be used to specify additional
+# port(s) where Squid listens for proxy request. Such ports will
+# be plain proxy ports with no options.
+#
+# You may specify multiple socket addresses on multiple lines.
+#
+# Modes:
+#
+# intercept Support for IP-Layer interception of
+# outgoing requests without browser settings.
+# NP: disables authentication and IPv6 on the port.
+#
+# tproxy Support Linux TPROXY for spoofing outgoing
+# connections using the client IP address.
+# NP: disables authentication and maybe IPv6 on the port.
+#
+# accel Accelerator / reverse proxy mode
+#
+# ssl-bump For each CONNECT request allowed by ssl_bump ACLs,
+# establish secure connection with the client and with
+# the server, decrypt HTTPS messages as they pass through
+# Squid, and treat them as unencrypted HTTP messages,
+# becoming the man-in-the-middle.
+#
+# The ssl_bump option is required to fully enable
+# bumping of CONNECT requests.
+#
+# Omitting the mode flag causes default forward proxy mode to be used.
+#
+#
+# Accelerator Mode Options:
+#
+# defaultsite=domainname
+# What to use for the Host: header if it is not present
+# in a request. Determines what site (not origin server)
+# accelerators should consider the default.
+#
+# no-vhost Disable using HTTP/1.1 Host header for virtual domain support.
+#
+# protocol= Protocol to reconstruct accelerated requests with.
+# Defaults to http for http_port and https for
+# https_port
+#
+# vport Virtual host port support. Using the http_port number
+# instead of the port passed on Host: headers.
+#
+# vport=NN Virtual host port support. Using the specified port
+# number instead of the port passed on Host: headers.
+#
+# act-as-origin
+# Act as if this Squid is the origin server.
+# This currently means generate new Date: and Expires:
+# headers on HIT instead of adding Age:.
+#
+# ignore-cc Ignore request Cache-Control headers.
+#
+# WARNING: This option violates HTTP specifications if
+# used in non-accelerator setups.
+#
+# allow-direct Allow direct forwarding in accelerator mode. Normally
+# accelerated requests are denied direct forwarding as if
+# never_direct was used.
+#
+# WARNING: this option opens accelerator mode to security
+# vulnerabilities usually only affecting in interception
+# mode. Make sure to protect forwarding with suitable
+# http_access rules when using this.
+#
+#
+# SSL Bump Mode Options:
+# In addition to these options ssl-bump requires TLS/SSL options.
+#
+# generate-host-certificates[=<on|off>]
+# Dynamically create SSL server certificates for the
+# destination hosts of bumped CONNECT requests.When
+# enabled, the cert and key options are used to sign
+# generated certificates. Otherwise generated
+# certificate will be selfsigned.
+# If there is a CA certificate lifetime of the generated
+# certificate equals lifetime of the CA certificate. If
+# generated certificate is selfsigned lifetime is three
+# years.
+# This option is enabled by default when ssl-bump is used.
+# See the ssl-bump option above for more information.
+#
+# dynamic_cert_mem_cache_size=SIZE
+# Approximate total RAM size spent on cached generated
+# certificates. If set to zero, caching is disabled. The
+# default value is 4MB.
+#
+# TLS / SSL Options:
+#
+# cert= Path to SSL certificate (PEM format).
+#
+# key= Path to SSL private key file (PEM format)
+# if not specified, the certificate file is
+# assumed to be a combined certificate and
+# key file.
+#
+# version= The version of SSL/TLS supported
+# 1 automatic (default)
+# 2 SSLv2 only
+# 3 SSLv3 only
+# 4 TLSv1.0 only
+# 5 TLSv1.1 only
+# 6 TLSv1.2 only
+#
+# cipher= Colon separated list of supported ciphers.
+# NOTE: some ciphers such as EDH ciphers depend on
+# additional settings. If those settings are
+# omitted the ciphers may be silently ignored
+# by the OpenSSL library.
+#
+# options= Various SSL implementation options. The most important
+# being:
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1.0
+# NO_TLSv1_1 Disallow the use of TLSv1.1
+# NO_TLSv1_2 Disallow the use of TLSv1.2
+# SINGLE_DH_USE Always create a new key when using
+# temporary/ephemeral DH key exchanges
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+# See OpenSSL SSL_CTX_set_options documentation for a
+# complete list of options.
+#
+# clientca= File containing the list of CAs to use when
+# requesting a client certificate.
+#
+# cafile= File containing additional CA certificates to
+# use when verifying client certificates. If unset
+# clientca will be used.
+#
+# capath= Directory containing additional CA certificates
+# and CRL lists to use when verifying client certificates.
+#
+# crlfile= File of additional CRL lists to use when verifying
+# the client certificate, in addition to CRLs stored in
+# the capath. Implies VERIFY_CRL flag below.
+#
+# dhparams= File containing DH parameters for temporary/ephemeral
+# DH key exchanges. See OpenSSL documentation for details
+# on how to create this file.
+# WARNING: EDH ciphers will be silently disabled if this
+# option is not set.
+#
+# sslflags= Various flags modifying the use of SSL:
+# DELAYED_AUTH
+# Don't request client certificates
+# immediately, but wait until acl processing
+# requires a certificate (not yet implemented).
+# NO_DEFAULT_CA
+# Don't use the default CA lists built in
+# to OpenSSL.
+# NO_SESSION_REUSE
+# Don't allow for session reuse. Each connection
+# will result in a new SSL session.
+# VERIFY_CRL
+# Verify CRL lists when accepting client
+# certificates.
+# VERIFY_CRL_ALL
+# Verify CRL lists for all certificates in the
+# client certificate chain.
+#
+# sslcontext= SSL session ID context identifier.
+#
+# Other Options:
+#
+# connection-auth[=on|off]
+# use connection-auth=off to tell Squid to prevent
+# forwarding Microsoft connection oriented authentication
+# (NTLM, Negotiate and Kerberos)
+#
+# disable-pmtu-discovery=
+# Control Path-MTU discovery usage:
+# off lets OS decide on what to do (default).
+# transparent disable PMTU discovery when transparent
+# support is enabled.
+# always disable always PMTU discovery.
+#
+# In many setups of transparently intercepting proxies
+# Path-MTU discovery can not work on traffic towards the
+# clients. This is the case when the intercepting device
+# does not fully track connections and fails to forward
+# ICMP must fragment messages to the cache server. If you
+# have such setup and experience that certain clients
+# sporadically hang or never complete requests set
+# disable-pmtu-discovery option to 'transparent'.
+#
+# name= Specifies a internal name for the port. Defaults to
+# the port specification (port or addr:port)
+#
+# tcpkeepalive[=idle,interval,timeout]
+# Enable TCP keepalive probes of idle connections.
+# In seconds; idle is the initial time before TCP starts
+# probing the connection, interval how often to probe, and
+# timeout the time before giving up.
+#
+# If you run Squid on a dual-homed machine with an internal
+# and an external interface we recommend you to specify the
+# internal address:port in http_port. This way Squid will only be
+# visible on the internal address.
+#
+#
+
+# Squid normally listens to port 3128
+#http_port 3128
+http_port 8080
+
+# TAG: https_port
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Usage: [ip:]port cert=certificate.pem [key=key.pem] [mode] [options...]
+#
+# The socket address where Squid will listen for client requests made
+# over TLS or SSL connections. Commonly referred to as HTTPS.
+#
+# This is most useful for situations where you are running squid in
+# accelerator mode and you want to do the SSL work at the accelerator level.
+#
+# You may specify multiple socket addresses on multiple lines,
+# each with their own SSL certificate and/or options.
+#
+# Modes:
+#
+# accel Accelerator / reverse proxy mode
+#
+# intercept Support for IP-Layer interception of
+# outgoing requests without browser settings.
+# NP: disables authentication and IPv6 on the port.
+#
+# tproxy Support Linux TPROXY for spoofing outgoing
+# connections using the client IP address.
+# NP: disables authentication and maybe IPv6 on the port.
+#
+# ssl-bump For each intercepted connection allowed by ssl_bump
+# ACLs, establish a secure connection with the client and with
+# the server, decrypt HTTPS messages as they pass through
+# Squid, and treat them as unencrypted HTTP messages,
+# becoming the man-in-the-middle.
+#
+# An "ssl_bump server-first" match is required to
+# fully enable bumping of intercepted SSL connections.
+#
+# Requires tproxy or intercept.
+#
+# Omitting the mode flag causes default forward proxy mode to be used.
+#
+#
+# See http_port for a list of generic options
+#
+#
+# SSL Options:
+#
+# cert= Path to SSL certificate (PEM format).
+#
+# key= Path to SSL private key file (PEM format)
+# if not specified, the certificate file is
+# assumed to be a combined certificate and
+# key file.
+#
+# version= The version of SSL/TLS supported
+# 1 automatic (default)
+# 2 SSLv2 only
+# 3 SSLv3 only
+# 4 TLSv1 only
+#
+# cipher= Colon separated list of supported ciphers.
+#
+# options= Various SSL engine options. The most important
+# being:
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1
+# SINGLE_DH_USE Always create a new key when using
+# temporary/ephemeral DH key exchanges
+# See src/ssl_support.c or OpenSSL SSL_CTX_set_options
+# documentation for a complete list of options.
+#
+# clientca= File containing the list of CAs to use when
+# requesting a client certificate.
+#
+# cafile= File containing additional CA certificates to
+# use when verifying client certificates. If unset
+# clientca will be used.
+#
+# capath= Directory containing additional CA certificates
+# and CRL lists to use when verifying client certificates.
+#
+# crlfile= File of additional CRL lists to use when verifying
+# the client certificate, in addition to CRLs stored in
+# the capath. Implies VERIFY_CRL flag below.
+#
+# dhparams= File containing DH parameters for temporary/ephemeral
+# DH key exchanges.
+#
+# sslflags= Various flags modifying the use of SSL:
+# DELAYED_AUTH
+# Don't request client certificates
+# immediately, but wait until acl processing
+# requires a certificate (not yet implemented).
+# NO_DEFAULT_CA
+# Don't use the default CA lists built in
+# to OpenSSL.
+# NO_SESSION_REUSE
+# Don't allow for session reuse. Each connection
+# will result in a new SSL session.
+# VERIFY_CRL
+# Verify CRL lists when accepting client
+# certificates.
+# VERIFY_CRL_ALL
+# Verify CRL lists for all certificates in the
+# client certificate chain.
+#
+# sslcontext= SSL session ID context identifier.
+#
+# generate-host-certificates[=<on|off>]
+# Dynamically create SSL server certificates for the
+# destination hosts of bumped SSL requests.When
+# enabled, the cert and key options are used to sign
+# generated certificates. Otherwise generated
+# certificate will be selfsigned.
+# If there is CA certificate life time of generated
+# certificate equals lifetime of CA certificate. If
+# generated certificate is selfsigned lifetime is three
+# years.
+# This option is enabled by default when SslBump is used.
+# See the sslBump option above for more information.
+#
+# dynamic_cert_mem_cache_size=SIZE
+# Approximate total RAM size spent on cached generated
+# certificates. If set to zero, caching is disabled. The
+# default value is 4MB.
+#
+# See http_port for a list of available options.
+#Default:
+# none
+
+# TAG: tcp_outgoing_tos
+# Allows you to select a TOS/Diffserv value for packets outgoing
+# on the server side, based on an ACL.
+#
+# tcp_outgoing_tos ds-field [!]aclname ...
+#
+# Example where normal_service_net uses the TOS value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# tcp_outgoing_tos 0x00 normal_service_net
+# tcp_outgoing_tos 0x20 good_service_net
+#
+# TOS/DSCP values really only have local significance - so you should
+# know what you're specifying. For more information, see RFC2474,
+# RFC2475, and RFC3260.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or
+# "default" to use whatever default your host has. Note that in
+# practice often only multiples of 4 is usable as the two rightmost bits
+# have been redefined for use by ECN (RFC 3168 section 23.1).
+#
+# Processing proceeds in the order specified, and stops at first fully
+# matching line.
+#Default:
+# none
+
+# TAG: clientside_tos
+# Allows you to select a TOS/Diffserv value for packets being transmitted
+# on the client-side, based on an ACL.
+#
+# clientside_tos ds-field [!]aclname ...
+#
+# Example where normal_service_net uses the TOS value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# clientside_tos 0x00 normal_service_net
+# clientside_tos 0x20 good_service_net
+#
+# Note: This feature is incompatible with qos_flows. Any TOS values set here
+# will be overwritten by TOS values in qos_flows.
+#Default:
+# none
+
+# TAG: tcp_outgoing_mark
+# Note: This option is only available if Squid is rebuilt with the
+# Packet MARK (Linux)
+#
+# Allows you to apply a Netfilter mark value to outgoing packets
+# on the server side, based on an ACL.
+#
+# tcp_outgoing_mark mark-value [!]aclname ...
+#
+# Example where normal_service_net uses the mark value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# tcp_outgoing_mark 0x00 normal_service_net
+# tcp_outgoing_mark 0x20 good_service_net
+#Default:
+# none
+
+# TAG: clientside_mark
+# Note: This option is only available if Squid is rebuilt with the
+# Packet MARK (Linux)
+#
+# Allows you to apply a Netfilter mark value to packets being transmitted
+# on the client-side, based on an ACL.
+#
+# clientside_mark mark-value [!]aclname ...
+#
+# Example where normal_service_net uses the mark value 0x00
+# and good_service_net uses 0x20
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.1.0/24
+# clientside_mark 0x00 normal_service_net
+# clientside_mark 0x20 good_service_net
+#
+# Note: This feature is incompatible with qos_flows. Any mark values set here
+# will be overwritten by mark values in qos_flows.
+#Default:
+# none
+
+# TAG: qos_flows
+# Allows you to select a TOS/DSCP value to mark outgoing
+# connections to the client, based on where the reply was sourced.
+# For platforms using netfilter, allows you to set a netfilter mark
+# value instead of, or in addition to, a TOS value.
+#
+# By default this functionality is disabled. To enable it with the default
+# settings simply use "qos_flows mark" or "qos_flows tos". Default
+# settings will result in the netfilter mark or TOS value being copied
+# from the upstream connection to the client. Note that it is the connection
+# CONNMARK value not the packet MARK value that is copied.
+#
+# It is not currently possible to copy the mark or TOS value from the
+# client to the upstream connection request.
+#
+# TOS values really only have local significance - so you should
+# know what you're specifying. For more information, see RFC2474,
+# RFC2475, and RFC3260.
+#
+# The TOS/DSCP byte must be exactly that - a octet value 0 - 255. Note that
+# in practice often only multiples of 4 is usable as the two rightmost bits
+# have been redefined for use by ECN (RFC 3168 section 23.1).
+#
+# Mark values can be any unsigned 32-bit integer value.
+#
+# This setting is configured by setting the following values:
+#
+# tos|mark Whether to set TOS or netfilter mark values
+#
+# local-hit=0xFF Value to mark local cache hits.
+#
+# sibling-hit=0xFF Value to mark hits from sibling peers.
+#
+# parent-hit=0xFF Value to mark hits from parent peers.
+#
+# miss=0xFF[/mask] Value to mark cache misses. Takes precedence
+# over the preserve-miss feature (see below), unless
+# mask is specified, in which case only the bits
+# specified in the mask are written.
+#
+# The TOS variant of the following features are only possible on Linux
+# and require your kernel to be patched with the TOS preserving ZPH
+# patch, available from http://zph.bratcheda.org
+# No patch is needed to preserve the netfilter mark, which will work
+# with all variants of netfilter.
+#
+# disable-preserve-miss
+# This option disables the preservation of the TOS or netfilter
+# mark. By default, the existing TOS or netfilter mark value of
+# the response coming from the remote server will be retained
+# and masked with miss-mark.
+# NOTE: in the case of a netfilter mark, the mark must be set on
+# the connection (using the CONNMARK target) not on the packet
+# (MARK target).
+#
+# miss-mask=0xFF
+# Allows you to mask certain bits in the TOS or mark value
+# received from the remote server, before copying the value to
+# the TOS sent towards clients.
+# Default for tos: 0xFF (TOS from server is not changed).
+# Default for mark: 0xFFFFFFFF (mark from server is not changed).
+#
+# All of these features require the --enable-zph-qos compilation flag
+# (enabled by default). Netfilter marking also requires the
+# libnetfilter_conntrack libraries (--with-netfilter-conntrack) and
+# libcap 2.09+ (--with-libcap).
+#
+#Default:
+# none
+
+# TAG: tcp_outgoing_address
+# Allows you to map requests to different outgoing IP addresses
+# based on the username or source address of the user making
+# the request.
+#
+# tcp_outgoing_address ipaddr [[!]aclname] ...
+#
+# For example;
+# Forwarding clients with dedicated IPs for certain subnets.
+#
+# acl normal_service_net src 10.0.0.0/24
+# acl good_service_net src 10.0.2.0/24
+#
+# tcp_outgoing_address 2001:db8::c001 good_service_net
+# tcp_outgoing_address 10.1.0.2 good_service_net
+#
+# tcp_outgoing_address 2001:db8::beef normal_service_net
+# tcp_outgoing_address 10.1.0.1 normal_service_net
+#
+# tcp_outgoing_address 2001:db8::1
+# tcp_outgoing_address 10.1.0.3
+#
+# Processing proceeds in the order specified, and stops at first fully
+# matching line.
+#
+# Squid will add an implicit IP version test to each line.
+# Requests going to IPv4 websites will use the outgoing 10.1.0.* addresses.
+# Requests going to IPv6 websites will use the outgoing 2001:db8:* addresses.
+#
+#
+# NOTE: The use of this directive using client dependent ACLs is
+# incompatible with the use of server side persistent connections. To
+# ensure correct results it is best to set server_persistent_connections
+# to off when using this directive in such configurations.
+#
+# NOTE: The use of this directive to set a local IP on outgoing TCP links
+# is incompatible with using TPROXY to set client IP out outbound TCP links.
+# When needing to contact peers use the no-tproxy cache_peer option and the
+# client_dst_passthru directive re-enable normal forwarding such as this.
+#
+#Default:
+# Address selection is performed by the operating system.
+
+# TAG: host_verify_strict
+# Regardless of this option setting, when dealing with intercepted
+# traffic, Squid always verifies that the destination IP address matches
+# the Host header domain or IP (called 'authority form URL').
+#
+# This enforcement is performed to satisfy a MUST-level requirement in
+# RFC 2616 section 14.23: "The Host field value MUST represent the naming
+# authority of the origin server or gateway given by the original URL".
+#
+# When set to ON:
+# Squid always responds with an HTTP 409 (Conflict) error
+# page and logs a security warning if there is no match.
+#
+# Squid verifies that the destination IP address matches
+# the Host header for forward-proxy and reverse-proxy traffic
+# as well. For those traffic types, Squid also enables the
+# following checks, comparing the corresponding Host header
+# and Request-URI components:
+#
+# * The host names (domain or IP) must be identical,
+# but valueless or missing Host header disables all checks.
+# For the two host names to match, both must be either IP
+# or FQDN.
+#
+# * Port numbers must be identical, but if a port is missing
+# the scheme-default port is assumed.
+#
+#
+# When set to OFF (the default):
+# Squid allows suspicious requests to continue but logs a
+# security warning and blocks caching of the response.
+#
+# * Forward-proxy traffic is not checked at all.
+#
+# * Reverse-proxy traffic is not checked at all.
+#
+# * Intercepted traffic which passes verification is handled
+# according to client_dst_passthru.
+#
+# * Intercepted requests which fail verification are sent
+# to the client original destination instead of DIRECT.
+# This overrides 'client_dst_passthru off'.
+#
+# For now suspicious intercepted CONNECT requests are always
+# responded to with an HTTP 409 (Conflict) error page.
+#
+#
+# SECURITY NOTE:
+#
+# As described in CVE-2009-0801 when the Host: header alone is used
+# to determine the destination of a request it becomes trivial for
+# malicious scripts on remote websites to bypass browser same-origin
+# security policy and sandboxing protections.
+#
+# The cause of this is that such applets are allowed to perform their
+# own HTTP stack, in which case the same-origin policy of the browser
+# sandbox only verifies that the applet tries to contact the same IP
+# as from where it was loaded at the IP level. The Host: header may
+# be different from the connected IP and approved origin.
+#
+#Default:
+# host_verify_strict off
+
+# TAG: client_dst_passthru
+# With NAT or TPROXY intercepted traffic Squid may pass the request
+# directly to the original client destination IP or seek a faster
+# source using the HTTP Host header.
+#
+# Using Host to locate alternative servers can provide faster
+# connectivity with a range of failure recovery options.
+# But can also lead to connectivity trouble when the client and
+# server are attempting stateful interactions unaware of the proxy.
+#
+# This option (on by default) prevents alternative DNS entries being
+# located to send intercepted traffic DIRECT to an origin server.
+# The clients original destination IP and port will be used instead.
+#
+# Regardless of this option setting, when dealing with intercepted
+# traffic Squid will verify the Host: header and any traffic which
+# fails Host verification will be treated as if this option were ON.
+#
+# see host_verify_strict for details on the verification process.
+#Default:
+# client_dst_passthru on
+
+# SSL OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: ssl_unclean_shutdown
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Some browsers (especially MSIE) bugs out on SSL shutdown
+# messages.
+#Default:
+# ssl_unclean_shutdown off
+
+# TAG: ssl_engine
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# The OpenSSL engine to use. You will need to set this if you
+# would like to use hardware SSL acceleration for example.
+#Default:
+# none
+
+# TAG: sslproxy_client_certificate
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Client SSL Certificate to use when proxying https:// URLs
+#Default:
+# none
+
+# TAG: sslproxy_client_key
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Client SSL Key to use when proxying https:// URLs
+#Default:
+# none
+
+# TAG: sslproxy_version
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# SSL version level to use when proxying https:// URLs
+#
+# The versions of SSL/TLS supported:
+#
+# 1 automatic (default)
+# 2 SSLv2 only
+# 3 SSLv3 only
+# 4 TLSv1.0 only
+# 5 TLSv1.1 only
+# 6 TLSv1.2 only
+#Default:
+# automatic SSL/TLS version negotiation
+
+# TAG: sslproxy_options
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# SSL implementation options to use when proxying https:// URLs
+#
+# The most important being:
+#
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1.0
+# NO_TLSv1_1 Disallow the use of TLSv1.1
+# NO_TLSv1_2 Disallow the use of TLSv1.2
+# SINGLE_DH_USE
+# Always create a new key when using temporary/ephemeral
+# DH key exchanges
+# SSL_OP_NO_TICKET
+# Disable use of RFC5077 session tickets. Some servers
+# may have problems understanding the TLS extension due
+# to ambiguous specification in RFC4507.
+# ALL Enable various bug workarounds suggested as "harmless"
+# by OpenSSL. Be warned that this may reduce SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation for a
+# complete list of possible options.
+#Default:
+# none
+
+# TAG: sslproxy_cipher
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# SSL cipher list to use when proxying https:// URLs
+#
+# Colon separated list of supported ciphers.
+#Default:
+# none
+
+# TAG: sslproxy_cafile
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# file containing CA certificates to use when verifying server
+# certificates while proxying https:// URLs
+#Default:
+# none
+
+# TAG: sslproxy_capath
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# directory containing CA certificates to use when verifying
+# server certificates while proxying https:// URLs
+#Default:
+# none
+
+# TAG: ssl_bump
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# This option is consulted when a CONNECT request is received on
+# an http_port (or a new connection is intercepted at an
+# https_port), provided that port was configured with an ssl-bump
+# flag. The subsequent data on the connection is either treated as
+# HTTPS and decrypted OR tunneled at TCP level without decryption,
+# depending on the first bumping "mode" which ACLs match.
+#
+# ssl_bump <mode> [!]acl ...
+#
+# The following bumping modes are supported:
+#
+# client-first
+# Allow bumping of the connection. Establish a secure connection
+# with the client first, then connect to the server. This old mode
+# does not allow Squid to mimic server SSL certificate and does
+# not work with intercepted SSL connections.
+#
+# server-first
+# Allow bumping of the connection. Establish a secure connection
+# with the server first, then establish a secure connection with
+# the client, using a mimicked server certificate. Works with both
+# CONNECT requests and intercepted SSL connections.
+#
+# none
+# Become a TCP tunnel without decoding the connection.
+# Works with both CONNECT requests and intercepted SSL
+# connections. This is the default behavior when no
+# ssl_bump option is given or no ssl_bump ACLs match.
+#
+# By default, no connections are bumped.
+#
+# The first matching ssl_bump option wins. If no ACLs match, the
+# connection is not bumped. Unlike most allow/deny ACL lists, ssl_bump
+# does not have an implicit "negate the last given option" rule. You
+# must make that rule explicit if you convert old ssl_bump allow/deny
+# rules that rely on such an implicit rule.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# See also: http_port ssl-bump, https_port ssl-bump
+#
+#
+# # Example: Bump all requests except those originating from
+# # localhost or those going to example.com.
+#
+# acl broken_sites dstdomain .example.com
+# ssl_bump none localhost
+# ssl_bump none broken_sites
+# ssl_bump server-first all
+#Default:
+# Does not bump unless rules are present in squid.conf
+
+# TAG: sslproxy_flags
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Various flags modifying the use of SSL while proxying https:// URLs:
+# DONT_VERIFY_PEER Accept certificates that fail verification.
+# For refined control, see sslproxy_cert_error.
+# NO_DEFAULT_CA Don't use the default CA list built in
+# to OpenSSL.
+#Default:
+# none
+
+# TAG: sslproxy_cert_error
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Use this ACL to bypass server certificate validation errors.
+#
+# For example, the following lines will bypass all validation errors
+# when talking to servers for example.com. All other
+# validation errors will result in ERR_SECURE_CONNECT_FAIL error.
+#
+# acl BrokenButTrustedServers dstdomain example.com
+# sslproxy_cert_error allow BrokenButTrustedServers
+# sslproxy_cert_error deny all
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+# Using slow acl types may result in server crashes
+#
+# Without this option, all server certificate validation errors
+# terminate the transaction to protect Squid and the client.
+#
+# SQUID_X509_V_ERR_INFINITE_VALIDATION error cannot be bypassed
+# but should not happen unless your OpenSSL library is buggy.
+#
+# SECURITY WARNING:
+# Bypassing validation errors is dangerous because an
+# error usually implies that the server cannot be trusted
+# and the connection may be insecure.
+#
+# See also: sslproxy_flags and DONT_VERIFY_PEER.
+#Default:
+# Server certificate errors terminate the transaction.
+
+# TAG: sslproxy_cert_sign
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+#
+# sslproxy_cert_sign <signing algorithm> acl ...
+#
+# The following certificate signing algorithms are supported:
+#
+# signTrusted
+# Sign using the configured CA certificate which is usually
+# placed in and trusted by end-user browsers. This is the
+# default for trusted origin server certificates.
+#
+# signUntrusted
+# Sign to guarantee an X509_V_ERR_CERT_UNTRUSTED browser error.
+# This is the default for untrusted origin server certificates
+# that are not self-signed (see ssl::certUntrusted).
+#
+# signSelf
+# Sign using a self-signed certificate with the right CN to
+# generate a X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT error in the
+# browser. This is the default for self-signed origin server
+# certificates (see ssl::certSelfSigned).
+#
+# This clause only supports fast acl types.
+#
+# When sslproxy_cert_sign acl(s) match, Squid uses the corresponding
+# signing algorithm to generate the certificate and ignores all
+# subsequent sslproxy_cert_sign options (the first match wins). If no
+# acl(s) match, the default signing algorithm is determined by errors
+# detected when obtaining and validating the origin server certificate.
+#
+# WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can
+# be used with sslproxy_cert_adapt, but if and only if Squid is bumping a
+# CONNECT request that carries a domain name. In all other cases (CONNECT
+# to an IP address or an intercepted SSL connection), Squid cannot detect
+# the domain mismatch at certificate generation time when
+# bump-server-first is used.
+#Default:
+# none
+
+# TAG: sslproxy_cert_adapt
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+#
+# sslproxy_cert_adapt <adaptation algorithm> acl ...
+#
+# The following certificate adaptation algorithms are supported:
+#
+# setValidAfter
+# Sets the "Not After" property to the "Not After" property of
+# the CA certificate used to sign generated certificates.
+#
+# setValidBefore
+# Sets the "Not Before" property to the "Not Before" property of
+# the CA certificate used to sign generated certificates.
+#
+# setCommonName or setCommonName{CN}
+# Sets Subject.CN property to the host name specified as a
+# CN parameter or, if no explicit CN parameter was specified,
+# extracted from the CONNECT request. It is a misconfiguration
+# to use setCommonName without an explicit parameter for
+# intercepted or tproxied SSL connections.
+#
+# This clause only supports fast acl types.
+#
+# Squid first groups sslproxy_cert_adapt options by adaptation algorithm.
+# Within a group, when sslproxy_cert_adapt acl(s) match, Squid uses the
+# corresponding adaptation algorithm to generate the certificate and
+# ignores all subsequent sslproxy_cert_adapt options in that algorithm's
+# group (i.e., the first match wins within each algorithm group). If no
+# acl(s) match, the default mimicking action takes place.
+#
+# WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can
+# be used with sslproxy_cert_adapt, but if and only if Squid is bumping a
+# CONNECT request that carries a domain name. In all other cases (CONNECT
+# to an IP address or an intercepted SSL connection), Squid cannot detect
+# the domain mismatch at certificate generation time when
+# bump-server-first is used.
+#Default:
+# none
+
+# TAG: sslpassword_program
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Specify a program used for entering SSL key passphrases
+# when using encrypted SSL certificate keys. If not specified
+# keys must either be unencrypted, or Squid started with the -N
+# option to allow it to query interactively for the passphrase.
+#
+# The key file name is given as argument to the program allowing
+# selection of the right password if you have multiple encrypted
+# keys.
+#Default:
+# none
+
+# OPTIONS RELATING TO EXTERNAL SSL_CRTD
+# -----------------------------------------------------------------------------
+
+# TAG: sslcrtd_program
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl-crtd
+#
+# Specify the location and options of the executable for ssl_crtd process.
+# /usr/lib/squid3/ssl_crtd program requires -s and -M parameters
+# For more information use:
+# /usr/lib/squid3/ssl_crtd -h
+#Default:
+# sslcrtd_program /usr/lib/squid3/ssl_crtd -s /var/lib/ssl_db -M 4MB
+
+# TAG: sslcrtd_children
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl-crtd
+#
+# The maximum number of processes spawn to service ssl server.
+# The maximum this may be safely set to is 32.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=N
+#
+# Sets the minimum number of processes to spawn when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few children temporary slows Squid under load while it
+# tries to spawn enough additional processes to cope with traffic.
+#
+# idle=N
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# You must have at least one ssl_crtd process.
+#Default:
+# sslcrtd_children 32 startup=5 idle=1
+
+# TAG: sslcrtvalidator_program
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# Specify the location and options of the executable for ssl_crt_validator
+# process.
+#
+# Usage: sslcrtvalidator_program [ttl=n] [cache=n] path ...
+#
+# Options:
+# ttl=n TTL in seconds for cached results. The default is 60 secs
+# cache=n limit the result cache size. The default value is 2048
+#Default:
+# none
+
+# TAG: sslcrtvalidator_children
+# Note: This option is only available if Squid is rebuilt with the
+# --enable-ssl
+#
+# The maximum number of processes spawn to service SSL server.
+# The maximum this may be safely set to is 32.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=N
+#
+# Sets the minimum number of processes to spawn when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few children temporary slows Squid under load while it
+# tries to spawn enough additional processes to cope with traffic.
+#
+# idle=N
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each certificate validator helper can handle in
+# parallel. A value of 0 indicates the certficate validator does not
+# support concurrency. Defaults to 1.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# a request ID in front of the request/response. The request
+# ID from the request must be echoed back with the response
+# to that request.
+#
+# You must have at least one ssl_crt_validator process.
+#Default:
+# sslcrtvalidator_children 32 startup=5 idle=1 concurrency=1
+
+# OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM
+# -----------------------------------------------------------------------------
+
+# TAG: cache_peer
+# To specify other caches in a hierarchy, use the format:
+#
+# cache_peer hostname type http-port icp-port [options]
+#
+# For example,
+#
+# # proxy icp
+# # hostname type port port options
+# # -------------------- -------- ----- ----- -----------
+# cache_peer parent.foo.net parent 3128 3130 default
+# cache_peer sib1.foo.net sibling 3128 3130 proxy-only
+# cache_peer sib2.foo.net sibling 3128 3130 proxy-only
+# cache_peer example.com parent 80 0 default
+# cache_peer cdn.example.com sibling 3128 0
+#
+# type: either 'parent', 'sibling', or 'multicast'.
+#
+# proxy-port: The port number where the peer accept HTTP requests.
+# For other Squid proxies this is usually 3128
+# For web servers this is usually 80
+#
+# icp-port: Used for querying neighbor caches about objects.
+# Set to 0 if the peer does not support ICP or HTCP.
+# See ICP and HTCP options below for additional details.
+#
+#
+# ==== ICP OPTIONS ====
+#
+# You MUST also set icp_port and icp_access explicitly when using these options.
+# The defaults will prevent peer traffic using ICP.
+#
+#
+# no-query Disable ICP queries to this neighbor.
+#
+# multicast-responder
+# Indicates the named peer is a member of a multicast group.
+# ICP queries will not be sent directly to the peer, but ICP
+# replies will be accepted from it.
+#
+# closest-only Indicates that, for ICP_OP_MISS replies, we'll only forward
+# CLOSEST_PARENT_MISSes and never FIRST_PARENT_MISSes.
+#
+# background-ping
+# To only send ICP queries to this neighbor infrequently.
+# This is used to keep the neighbor round trip time updated
+# and is usually used in conjunction with weighted-round-robin.
+#
+#
+# ==== HTCP OPTIONS ====
+#
+# You MUST also set htcp_port and htcp_access explicitly when using these options.
+# The defaults will prevent peer traffic using HTCP.
+#
+#
+# htcp Send HTCP, instead of ICP, queries to the neighbor.
+# You probably also want to set the "icp-port" to 4827
+# instead of 3130. This directive accepts a comma separated
+# list of options described below.
+#
+# htcp=oldsquid Send HTCP to old Squid versions (2.5 or earlier).
+#
+# htcp=no-clr Send HTCP to the neighbor but without
+# sending any CLR requests. This cannot be used with
+# only-clr.
+#
+# htcp=only-clr Send HTCP to the neighbor but ONLY CLR requests.
+# This cannot be used with no-clr.
+#
+# htcp=no-purge-clr
+# Send HTCP to the neighbor including CLRs but only when
+# they do not result from PURGE requests.
+#
+# htcp=forward-clr
+# Forward any HTCP CLR requests this proxy receives to the peer.
+#
+#
+# ==== PEER SELECTION METHODS ====
+#
+# The default peer selection method is ICP, with the first responding peer
+# being used as source. These options can be used for better load balancing.
+#
+#
+# default This is a parent cache which can be used as a "last-resort"
+# if a peer cannot be located by any of the peer-selection methods.
+# If specified more than once, only the first is used.
+#
+# round-robin Load-Balance parents which should be used in a round-robin
+# fashion in the absence of any ICP queries.
+# weight=N can be used to add bias.
+#
+# weighted-round-robin
+# Load-Balance parents which should be used in a round-robin
+# fashion with the frequency of each parent being based on the
+# round trip time. Closer parents are used more often.
+# Usually used for background-ping parents.
+# weight=N can be used to add bias.
+#
+# carp Load-Balance parents which should be used as a CARP array.
+# The requests will be distributed among the parents based on the
+# CARP load balancing hash function based on their weight.
+#
+# userhash Load-balance parents based on the client proxy_auth or ident username.
+#
+# sourcehash Load-balance parents based on the client source IP.
+#
+# multicast-siblings
+# To be used only for cache peers of type "multicast".
+# ALL members of this multicast group have "sibling"
+# relationship with it, not "parent". This is to a multicast
+# group when the requested object would be fetched only from
+# a "parent" cache, anyway. It's useful, e.g., when
+# configuring a pool of redundant Squid proxies, being
+# members of the same multicast group.
+#
+#
+# ==== PEER SELECTION OPTIONS ====
+#
+# weight=N use to affect the selection of a peer during any weighted
+# peer-selection mechanisms.
+# The weight must be an integer; default is 1,
+# larger weights are favored more.
+# This option does not affect parent selection if a peering
+# protocol is not in use.
+#
+# basetime=N Specify a base amount to be subtracted from round trip
+# times of parents.
+# It is subtracted before division by weight in calculating
+# which parent to fectch from. If the rtt is less than the
+# base time the rtt is set to a minimal value.
+#
+# ttl=N Specify a TTL to use when sending multicast ICP queries
+# to this address.
+# Only useful when sending to a multicast group.
+# Because we don't accept ICP replies from random
+# hosts, you must configure other group members as
+# peers with the 'multicast-responder' option.
+#
+# no-delay To prevent access to this neighbor from influencing the
+# delay pools.
+#
+# digest-url=URL Tell Squid to fetch the cache digest (if digests are
+# enabled) for this host from the specified URL rather
+# than the Squid default location.
+#
+#
+# ==== CARP OPTIONS ====
+#
+# carp-key=key-specification
+# use a different key than the full URL to hash against the peer.
+# the key-specification is a comma-separated list of the keywords
+# scheme, host, port, path, params
+# Order is not important.
+#
+# ==== ACCELERATOR / REVERSE-PROXY OPTIONS ====
+#
+# originserver Causes this parent to be contacted as an origin server.
+# Meant to be used in accelerator setups when the peer
+# is a web server.
+#
+# forceddomain=name
+# Set the Host header of requests forwarded to this peer.
+# Useful in accelerator setups where the server (peer)
+# expects a certain domain name but clients may request
+# others. ie example.com or www.example.com
+#
+# no-digest Disable request of cache digests.
+#
+# no-netdb-exchange
+# Disables requesting ICMP RTT database (NetDB).
+#
+#
+# ==== AUTHENTICATION OPTIONS ====
+#
+# login=user:password
+# If this is a personal/workgroup proxy and your parent
+# requires proxy authentication.
+#
+# Note: The string can include URL escapes (i.e. %20 for
+# spaces). This also means % must be written as %%.
+#
+# login=PASSTHRU
+# Send login details received from client to this peer.
+# Both Proxy- and WWW-Authorization headers are passed
+# without alteration to the peer.
+# Authentication is not required by Squid for this to work.
+#
+# Note: This will pass any form of authentication but
+# only Basic auth will work through a proxy unless the
+# connection-auth options are also used.
+#
+# login=PASS Send login details received from client to this peer.
+# Authentication is not required by this option.
+#
+# If there are no client-provided authentication headers
+# to pass on, but username and password are available
+# from an external ACL user= and password= result tags
+# they may be sent instead.
+#
+# Note: To combine this with proxy_auth both proxies must
+# share the same user database as HTTP only allows for
+# a single login (one for proxy, one for origin server).
+# Also be warned this will expose your users proxy
+# password to the peer. USE WITH CAUTION
+#
+# login=*:password
+# Send the username to the upstream cache, but with a
+# fixed password. This is meant to be used when the peer
+# is in another administrative domain, but it is still
+# needed to identify each user.
+# The star can optionally be followed by some extra
+# information which is added to the username. This can
+# be used to identify this proxy to the peer, similar to
+# the login=username:password option above.
+#
+# login=NEGOTIATE
+# If this is a personal/workgroup proxy and your parent
+# requires a secure proxy authentication.
+# The first principal from the default keytab or defined by
+# the environment variable KRB5_KTNAME will be used.
+#
+# WARNING: The connection may transmit requests from multiple
+# clients. Negotiate often assumes end-to-end authentication
+# and a single-client. Which is not strictly true here.
+#
+# login=NEGOTIATE:principal_name
+# If this is a personal/workgroup proxy and your parent
+# requires a secure proxy authentication.
+# The principal principal_name from the default keytab or
+# defined by the environment variable KRB5_KTNAME will be
+# used.
+#
+# WARNING: The connection may transmit requests from multiple
+# clients. Negotiate often assumes end-to-end authentication
+# and a single-client. Which is not strictly true here.
+#
+# connection-auth=on|off
+# Tell Squid that this peer does or not support Microsoft
+# connection oriented authentication, and any such
+# challenges received from there should be ignored.
+# Default is auto to automatically determine the status
+# of the peer.
+#
+#
+# ==== SSL / HTTPS / TLS OPTIONS ====
+#
+# ssl Encrypt connections to this peer with SSL/TLS.
+#
+# sslcert=/path/to/ssl/certificate
+# A client SSL certificate to use when connecting to
+# this peer.
+#
+# sslkey=/path/to/ssl/key
+# The private SSL key corresponding to sslcert above.
+# If 'sslkey' is not specified 'sslcert' is assumed to
+# reference a combined file containing both the
+# certificate and the key.
+#
+# sslversion=1|2|3|4|5|6
+# The SSL version to use when connecting to this peer
+# 1 = automatic (default)
+# 2 = SSL v2 only
+# 3 = SSL v3 only
+# 4 = TLS v1.0 only
+# 5 = TLS v1.1 only
+# 6 = TLS v1.2 only
+#
+# sslcipher=... The list of valid SSL ciphers to use when connecting
+# to this peer.
+#
+# ssloptions=... Specify various SSL implementation options:
+#
+# NO_SSLv2 Disallow the use of SSLv2
+# NO_SSLv3 Disallow the use of SSLv3
+# NO_TLSv1 Disallow the use of TLSv1.0
+# NO_TLSv1_1 Disallow the use of TLSv1.1
+# NO_TLSv1_2 Disallow the use of TLSv1.2
+# SINGLE_DH_USE
+# Always create a new key when using
+# temporary/ephemeral DH key exchanges
+# ALL Enable various bug workarounds
+# suggested as "harmless" by OpenSSL
+# Be warned that this reduces SSL/TLS
+# strength to some attacks.
+#
+# See the OpenSSL SSL_CTX_set_options documentation for a
+# more complete list.
+#
+# sslcafile=... A file containing additional CA certificates to use
+# when verifying the peer certificate.
+#
+# sslcapath=... A directory containing additional CA certificates to
+# use when verifying the peer certificate.
+#
+# sslcrlfile=... A certificate revocation list file to use when
+# verifying the peer certificate.
+#
+# sslflags=... Specify various flags modifying the SSL implementation:
+#
+# DONT_VERIFY_PEER
+# Accept certificates even if they fail to
+# verify.
+# NO_DEFAULT_CA
+# Don't use the default CA list built in
+# to OpenSSL.
+# DONT_VERIFY_DOMAIN
+# Don't verify the peer certificate
+# matches the server name
+#
+# ssldomain= The peer name as advertised in it's certificate.
+# Used for verifying the correctness of the received peer
+# certificate. If not specified the peer hostname will be
+# used.
+#
+# front-end-https
+# Enable the "Front-End-Https: On" header needed when
+# using Squid as a SSL frontend in front of Microsoft OWA.
+# See MS KB document Q307347 for details on this header.
+# If set to auto the header will only be added if the
+# request is forwarded as a https:// URL.
+#
+#
+# ==== GENERAL OPTIONS ====
+#
+# connect-timeout=N
+# A peer-specific connect timeout.
+# Also see the peer_connect_timeout directive.
+#
+# connect-fail-limit=N
+# How many times connecting to a peer must fail before
+# it is marked as down. Default is 10.
+#
+# allow-miss Disable Squid's use of only-if-cached when forwarding
+# requests to siblings. This is primarily useful when
+# icp_hit_stale is used by the sibling. To extensive use
+# of this option may result in forwarding loops, and you
+# should avoid having two-way peerings with this option.
+# For example to deny peer usage on requests from peer
+# by denying cache_peer_access if the source is a peer.
+#
+# max-conn=N Limit the amount of connections Squid may open to this
+# peer. see also
+#
+# name=xxx Unique name for the peer.
+# Required if you have multiple peers on the same host
+# but different ports.
+# This name can be used in cache_peer_access and similar
+# directives to dentify the peer.
+# Can be used by outgoing access controls through the
+# peername ACL type.
+#
+# no-tproxy Do not use the client-spoof TPROXY support when forwarding
+# requests to this peer. Use normal address selection instead.
+# This overrides the spoof_client_ip ACL.
+#
+# proxy-only objects fetched from the peer will not be stored locally.
+#
+#Default:
+# none
+
+# TAG: cache_peer_domain
+# Use to limit the domains for which a neighbor cache will be
+# queried.
+#
+# Usage:
+# cache_peer_domain cache-host domain [domain ...]
+# cache_peer_domain cache-host !domain
+#
+# For example, specifying
+#
+# cache_peer_domain parent.foo.net .edu
+#
+# has the effect such that UDP query packets are sent to
+# 'bigserver' only when the requested object exists on a
+# server in the .edu domain. Prefixing the domainname
+# with '!' means the cache will be queried for objects
+# NOT in that domain.
+#
+# NOTE: * Any number of domains may be given for a cache-host,
+# either on the same or separate lines.
+# * When multiple domains are given for a particular
+# cache-host, the first matched domain is applied.
+# * Cache hosts with no domain restrictions are queried
+# for all requests.
+# * There are no defaults.
+# * There is also a 'cache_peer_access' tag in the ACL
+# section.
+#Default:
+# none
+
+# TAG: cache_peer_access
+# Similar to 'cache_peer_domain' but provides more flexibility by
+# using ACL elements.
+#
+# Usage:
+# cache_peer_access cache-host allow|deny [!]aclname ...
+#
+# The syntax is identical to 'http_access' and the other lists of
+# ACL elements. See the comments for 'http_access' below, or
+# the Squid FAQ (http://wiki.squid-cache.org/SquidFaq/SquidAcl).
+#Default:
+# none
+
+# TAG: neighbor_type_domain
+# Modify the cache_peer neighbor type when passing requests
+# about specific domains to the peer.
+#
+# Usage:
+# neighbor_type_domain neighbor parent|sibling domain domain ...
+#
+# For example:
+# cache_peer foo.example.com parent 3128 3130
+# neighbor_type_domain foo.example.com sibling .au .de
+#
+# The above configuration treats all requests to foo.example.com as a
+# parent proxy unless the request is for a .au or .de ccTLD domain name.
+#Default:
+# The peer type from cache_peer directive is used for all requests to that peer.
+
+# TAG: dead_peer_timeout (seconds)
+# This controls how long Squid waits to declare a peer cache
+# as "dead." If there are no ICP replies received in this
+# amount of time, Squid will declare the peer dead and not
+# expect to receive any further ICP replies. However, it
+# continues to send ICP queries, and will mark the peer as
+# alive upon receipt of the first subsequent ICP reply.
+#
+# This timeout also affects when Squid expects to receive ICP
+# replies from peers. If more than 'dead_peer' seconds have
+# passed since the last ICP reply was received, Squid will not
+# expect to receive an ICP reply on the next query. Thus, if
+# your time between requests is greater than this timeout, you
+# will see a lot of requests sent DIRECT to origin servers
+# instead of to your parents.
+#Default:
+# dead_peer_timeout 10 seconds
+
+# TAG: forward_max_tries
+# Controls how many different forward paths Squid will try
+# before giving up. See also forward_timeout.
+#
+# NOTE: connect_retries (default: none) can make each of these
+# possible forwarding paths be tried multiple times.
+#Default:
+# forward_max_tries 10
+
+# TAG: hierarchy_stoplist
+# A list of words which, if found in a URL, cause the object to
+# be handled directly by this cache. In other words, use this
+# to not query neighbor caches for certain objects. You may
+# list this option multiple times.
+#
+# Example:
+# hierarchy_stoplist cgi-bin ?
+#
+# Note: never_direct overrides this option.
+#Default:
+# none
+
+# MEMORY CACHE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_mem (bytes)
+# NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE.
+# IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL
+# USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER
+# THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS.
+#
+# 'cache_mem' specifies the ideal amount of memory to be used
+# for:
+# * In-Transit objects
+# * Hot Objects
+# * Negative-Cached objects
+#
+# Data for these objects are stored in 4 KB blocks. This
+# parameter specifies the ideal upper limit on the total size of
+# 4 KB blocks allocated. In-Transit objects take the highest
+# priority.
+#
+# In-transit objects have priority over the others. When
+# additional space is needed for incoming data, negative-cached
+# and hot objects will be released. In other words, the
+# negative-cached and hot objects will fill up any unused space
+# not needed for in-transit objects.
+#
+# If circumstances require, this limit will be exceeded.
+# Specifically, if your incoming request rate requires more than
+# 'cache_mem' of memory to hold in-transit objects, Squid will
+# exceed this limit to satisfy the new requests. When the load
+# decreases, blocks will be freed until the high-water mark is
+# reached. Thereafter, blocks will be used to store hot
+# objects.
+#
+# If shared memory caching is enabled, Squid does not use the shared
+# cache space for in-transit objects, but they still consume as much
+# local memory as they need. For more details about the shared memory
+# cache, see memory_cache_shared.
+#Default:
+# cache_mem 256 MB
+
+# TAG: maximum_object_size_in_memory (bytes)
+# Objects greater than this size will not be attempted to kept in
+# the memory cache. This should be set high enough to keep objects
+# accessed frequently in memory to improve performance whilst low
+# enough to keep larger objects from hoarding cache_mem.
+#Default:
+# maximum_object_size_in_memory 512 KB
+
+# TAG: memory_cache_shared on|off
+# Controls whether the memory cache is shared among SMP workers.
+#
+# The shared memory cache is meant to occupy cache_mem bytes and replace
+# the non-shared memory cache, although some entities may still be
+# cached locally by workers for now (e.g., internal and in-transit
+# objects may be served from a local memory cache even if shared memory
+# caching is enabled).
+#
+# By default, the memory cache is shared if and only if all of the
+# following conditions are satisfied: Squid runs in SMP mode with
+# multiple workers, cache_mem is positive, and Squid environment
+# supports required IPC primitives (e.g., POSIX shared memory segments
+# and GCC-style atomic operations).
+#
+# To avoid blocking locks, shared memory uses opportunistic algorithms
+# that do not guarantee that every cachable entity that could have been
+# shared among SMP workers will actually be shared.
+#
+# Currently, entities exceeding 32KB in size cannot be shared.
+#Default:
+# "on" where supported if doing memory caching with multiple SMP workers.
+
+# TAG: memory_cache_mode
+# Controls which objects to keep in the memory cache (cache_mem)
+#
+# always Keep most recently fetched objects in memory (default)
+#
+# disk Only disk cache hits are kept in memory, which means
+# an object must first be cached on disk and then hit
+# a second time before cached in memory.
+#
+# network Only objects fetched from network is kept in memory
+#Default:
+# Keep the most recently fetched objects in memory
+
+# TAG: memory_replacement_policy
+# The memory replacement policy parameter determines which
+# objects are purged from memory when memory space is needed.
+#
+# See cache_replacement_policy for details on algorithms.
+#Default:
+# memory_replacement_policy lru
+
+# DISK CACHE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_replacement_policy
+# The cache replacement policy parameter determines which
+# objects are evicted (replaced) when disk space is needed.
+#
+# lru : Squid's original list based LRU policy
+# heap GDSF : Greedy-Dual Size Frequency
+# heap LFUDA: Least Frequently Used with Dynamic Aging
+# heap LRU : LRU policy implemented using a heap
+#
+# Applies to any cache_dir lines listed below this directive.
+#
+# The LRU policies keeps recently referenced objects.
+#
+# The heap GDSF policy optimizes object hit rate by keeping smaller
+# popular objects in cache so it has a better chance of getting a
+# hit. It achieves a lower byte hit rate than LFUDA though since
+# it evicts larger (possibly popular) objects.
+#
+# The heap LFUDA policy keeps popular objects in cache regardless of
+# their size and thus optimizes byte hit rate at the expense of
+# hit rate since one large, popular object will prevent many
+# smaller, slightly less popular objects from being cached.
+#
+# Both policies utilize a dynamic aging mechanism that prevents
+# cache pollution that can otherwise occur with frequency-based
+# replacement policies.
+#
+# NOTE: if using the LFUDA replacement policy you should increase
+# the value of maximum_object_size above its default of 4 MB to
+# to maximize the potential byte hit rate improvement of LFUDA.
+#
+# For more information about the GDSF and LFUDA cache replacement
+# policies see http://www.hpl.hp.com/techreports/1999/HPL-1999-69.html
+# and http://fog.hpl.external.hp.com/techreports/98/HPL-98-173.html.
+#Default:
+# cache_replacement_policy lru
+
+# TAG: minimum_object_size (bytes)
+# Objects smaller than this size will NOT be saved on disk. The
+# value is specified in bytes, and the default is 0 KB, which
+# means all responses can be stored.
+#Default:
+# no limit
+
+# TAG: maximum_object_size (bytes)
+# Set the default value for max-size parameter on any cache_dir.
+# The value is specified in bytes, and the default is 4 MB.
+#
+# If you wish to get a high BYTES hit ratio, you should probably
+# increase this (one 32 MB object hit counts for 3200 10KB
+# hits).
+#
+# If you wish to increase hit ratio more than you want to
+# save bandwidth you should leave this low.
+#
+# NOTE: if using the LFUDA replacement policy you should increase
+# this value to maximize the byte hit rate improvement of LFUDA!
+# See cache_replacement_policy for a discussion of this policy.
+#Default:
+# maximum_object_size 4 MB
+
+# TAG: cache_dir
+# Format:
+# cache_dir Type Directory-Name Fs-specific-data [options]
+#
+# You can specify multiple cache_dir lines to spread the
+# cache among different disk partitions.
+#
+# Type specifies the kind of storage system to use. Only "ufs"
+# is built by default. To enable any of the other storage systems
+# see the --enable-storeio configure option.
+#
+# 'Directory' is a top-level directory where cache swap
+# files will be stored. If you want to use an entire disk
+# for caching, this can be the mount-point directory.
+# The directory must exist and be writable by the Squid
+# process. Squid will NOT create this directory for you.
+#
+# In SMP configurations, cache_dir must not precede the workers option
+# and should use configuration macros or conditionals to give each
+# worker interested in disk caching a dedicated cache directory.
+#
+#
+# ==== The ufs store type ====
+#
+# "ufs" is the old well-known Squid storage format that has always
+# been there.
+#
+# Usage:
+# cache_dir ufs Directory-Name Mbytes L1 L2 [options]
+#
+# 'Mbytes' is the amount of disk space (MB) to use under this
+# directory. The default is 100 MB. Change this to suit your
+# configuration. Do NOT put the size of your disk drive here.
+# Instead, if you want Squid to use the entire disk drive,
+# subtract 20% and use that value.
+#
+# 'L1' is the number of first-level subdirectories which
+# will be created under the 'Directory'. The default is 16.
+#
+# 'L2' is the number of second-level subdirectories which
+# will be created under each first-level directory. The default
+# is 256.
+#
+#
+# ==== The aufs store type ====
+#
+# "aufs" uses the same storage format as "ufs", utilizing
+# POSIX-threads to avoid blocking the main Squid process on
+# disk-I/O. This was formerly known in Squid as async-io.
+#
+# Usage:
+# cache_dir aufs Directory-Name Mbytes L1 L2 [options]
+#
+# see argument descriptions under ufs above
+#
+#
+# ==== The diskd store type ====
+#
+# "diskd" uses the same storage format as "ufs", utilizing a
+# separate process to avoid blocking the main Squid process on
+# disk-I/O.
+#
+# Usage:
+# cache_dir diskd Directory-Name Mbytes L1 L2 [options] [Q1=n] [Q2=n]
+#
+# see argument descriptions under ufs above
+#
+# Q1 specifies the number of unacknowledged I/O requests when Squid
+# stops opening new files. If this many messages are in the queues,
+# Squid won't open new files. Default is 64
+#
+# Q2 specifies the number of unacknowledged messages when Squid
+# starts blocking. If this many messages are in the queues,
+# Squid blocks until it receives some replies. Default is 72
+#
+# When Q1 < Q2 (the default), the cache directory is optimized
+# for lower response time at the expense of a decrease in hit
+# ratio. If Q1 > Q2, the cache directory is optimized for
+# higher hit ratio at the expense of an increase in response
+# time.
+#
+#
+# ==== The rock store type ====
+#
+# Usage:
+# cache_dir rock Directory-Name Mbytes <max-size=bytes> [options]
+#
+# The Rock Store type is a database-style storage. All cached
+# entries are stored in a "database" file, using fixed-size slots,
+# one entry per slot. The database size is specified in MB. The
+# slot size is specified in bytes using the max-size option. See
+# below for more info on the max-size option.
+#
+# If possible, Squid using Rock Store creates a dedicated kid
+# process called "disker" to avoid blocking Squid worker(s) on disk
+# I/O. One disker kid is created for each rock cache_dir. Diskers
+# are created only when Squid, running in daemon mode, has support
+# for the IpcIo disk I/O module.
+#
+# swap-timeout=msec: Squid will not start writing a miss to or
+# reading a hit from disk if it estimates that the swap operation
+# will take more than the specified number of milliseconds. By
+# default and when set to zero, disables the disk I/O time limit
+# enforcement. Ignored when using blocking I/O module because
+# blocking synchronous I/O does not allow Squid to estimate the
+# expected swap wait time.
+#
+# max-swap-rate=swaps/sec: Artificially limits disk access using
+# the specified I/O rate limit. Swap out requests that
+# would cause the average I/O rate to exceed the limit are
+# delayed. Individual swap in requests (i.e., hits or reads) are
+# not delayed, but they do contribute to measured swap rate and
+# since they are placed in the same FIFO queue as swap out
+# requests, they may wait longer if max-swap-rate is smaller.
+# This is necessary on file systems that buffer "too
+# many" writes and then start blocking Squid and other processes
+# while committing those writes to disk. Usually used together
+# with swap-timeout to avoid excessive delays and queue overflows
+# when disk demand exceeds available disk "bandwidth". By default
+# and when set to zero, disables the disk I/O rate limit
+# enforcement. Currently supported by IpcIo module only.
+#
+#
+# ==== The coss store type ====
+#
+# NP: COSS filesystem in Squid-3 has been deemed too unstable for
+# production use and has thus been removed from this release.
+# We hope that it can be made usable again soon.
+#
+# block-size=n defines the "block size" for COSS cache_dir's.
+# Squid uses file numbers as block numbers. Since file numbers
+# are limited to 24 bits, the block size determines the maximum
+# size of the COSS partition. The default is 512 bytes, which
+# leads to a maximum cache_dir size of 512<<24, or 8 GB. Note
+# you should not change the coss block size after Squid
+# has written some objects to the cache_dir.
+#
+# The coss file store has changed from 2.5. Now it uses a file
+# called 'stripe' in the directory names in the config - and
+# this will be created by squid -z.
+#
+#
+# ==== COMMON OPTIONS ====
+#
+# no-store no new objects should be stored to this cache_dir.
+#
+# min-size=n the minimum object size in bytes this cache_dir
+# will accept. It's used to restrict a cache_dir
+# to only store large objects (e.g. AUFS) while
+# other stores are optimized for smaller objects
+# (e.g. COSS).
+# Defaults to 0.
+#
+# max-size=n the maximum object size in bytes this cache_dir
+# supports.
+# The value in maximum_object_size directive sets
+# the default unless more specific details are
+# available (ie a small store capacity).
+#
+# Note: To make optimal use of the max-size limits you should order
+# the cache_dir lines with the smallest max-size value first.
+#
+# Note for coss, max-size must be less than COSS_MEMBUF_SZ,
+# which can be changed with the --with-coss-membuf-size=N configure
+# option.
+#
+#Default:
+# No disk cache. Store cache ojects only in memory.
+#
+
+# Uncomment and adjust the following to add a disk cache directory.
+#cache_dir ufs /var/spool/squid3 100 16 256
+
+# TAG: store_dir_select_algorithm
+# How Squid selects which cache_dir to use when the response
+# object will fit into more than one.
+#
+# Regardless of which algorithm is used the cache_dir min-size
+# and max-size parameters are obeyed. As such they can affect
+# the selection algorithm by limiting the set of considered
+# cache_dir.
+#
+# Algorithms:
+#
+# least-load
+#
+# This algorithm is suited to caches with similar cache_dir
+# sizes and disk speeds.
+#
+# The disk with the least I/O pending is selected.
+# When there are multiple disks with the same I/O load ranking
+# the cache_dir with most available capacity is selected.
+#
+# When a mix of cache_dir sizes are configured the faster disks
+# have a naturally lower I/O loading and larger disks have more
+# capacity. So space used to store objects and data throughput
+# may be very unbalanced towards larger disks.
+#
+#
+# round-robin
+#
+# This algorithm is suited to caches with unequal cache_dir
+# disk sizes.
+#
+# Each cache_dir is selected in a rotation. The next suitable
+# cache_dir is used.
+#
+# Available cache_dir capacity is only considered in relation
+# to whether the object will fit and meets the min-size and
+# max-size parameters.
+#
+# Disk I/O loading is only considered to prevent overload on slow
+# disks. This algorithm does not spread objects by size, so any
+# I/O loading per-disk may appear very unbalanced and volatile.
+#
+#Default:
+# store_dir_select_algorithm least-load
+
+# TAG: max_open_disk_fds
+# To avoid having disk as the I/O bottleneck Squid can optionally
+# bypass the on-disk cache if more than this amount of disk file
+# descriptors are open.
+#
+# A value of 0 indicates no limit.
+#Default:
+# no limit
+
+# TAG: cache_swap_low (percent, 0-100)
+# The low-water mark for cache object replacement.
+# Replacement begins when the swap (disk) usage is above the
+# low-water mark and attempts to maintain utilization near the
+# low-water mark. As swap utilization gets close to high-water
+# mark object eviction becomes more aggressive. If utilization is
+# close to the low-water mark less replacement is done each time.
+#
+# Defaults are 90% and 95%. If you have a large cache, 5% could be
+# hundreds of MB. If this is the case you may wish to set these
+# numbers closer together.
+#
+# See also cache_swap_high
+#Default:
+# cache_swap_low 90
+
+# TAG: cache_swap_high (percent, 0-100)
+# The high-water mark for cache object replacement.
+# Replacement begins when the swap (disk) usage is above the
+# low-water mark and attempts to maintain utilization near the
+# low-water mark. As swap utilization gets close to high-water
+# mark object eviction becomes more aggressive. If utilization is
+# close to the low-water mark less replacement is done each time.
+#
+# Defaults are 90% and 95%. If you have a large cache, 5% could be
+# hundreds of MB. If this is the case you may wish to set these
+# numbers closer together.
+#
+# See also cache_swap_low
+#Default:
+# cache_swap_high 95
+
+# LOGFILE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: logformat
+# Usage:
+#
+# logformat <name> <format specification>
+#
+# Defines an access log format.
+#
+# The <format specification> is a string with embedded % format codes
+#
+# % format codes all follow the same basic structure where all but
+# the formatcode is optional. Output strings are automatically escaped
+# as required according to their context and the output format
+# modifiers are usually not needed, but can be specified if an explicit
+# output format is desired.
+#
+# % ["|[|'|#] [-] [[0]width] [{argument}] formatcode
+#
+# " output in quoted string format
+# [ output in squid text log format as used by log_mime_hdrs
+# # output in URL quoted format
+# ' output as-is
+#
+# - left aligned
+#
+# width minimum and/or maximum field width:
+# [width_min][.width_max]
+# When minimum starts with 0, the field is zero-padded.
+# String values exceeding maximum width are truncated.
+#
+# {arg} argument such as header name etc
+#
+# Format codes:
+#
+# % a literal % character
+# sn Unique sequence number per log line entry
+# err_code The ID of an error response served by Squid or
+# a similar internal error identifier.
+# err_detail Additional err_code-dependent error information.
+# note The annotation specified by the argument. Also
+# logs the adaptation meta headers set by the
+# adaptation_meta configuration parameter.
+# If no argument given all annotations logged.
+# The argument may include a separator to use with
+# annotation values:
+# name[:separator]
+# By default, multiple note values are separated with ","
+# and multiple notes are separated with "\r\n".
+# When logging named notes with %{name}note, the
+# explicitly configured separator is used between note
+# values. When logging all notes with %note, the
+# explicitly configured separator is used between
+# individual notes. There is currently no way to
+# specify both value and notes separators when logging
+# all notes with %note.
+#
+# Connection related format codes:
+#
+# >a Client source IP address
+# >A Client FQDN
+# >p Client source port
+# >eui Client source EUI (MAC address, EUI-48 or EUI-64 identifier)
+# >la Local IP address the client connected to
+# >lp Local port number the client connected to
+# >qos Client connection TOS/DSCP value set by Squid
+# >nfmark Client connection netfilter mark set by Squid
+#
+# la Local listening IP address the client connection was connected to.
+# lp Local listening port number the client connection was connected to.
+#
+# <a Server IP address of the last server or peer connection
+# <A Server FQDN or peer name
+# <p Server port number of the last server or peer connection
+# <la Local IP address of the last server or peer connection
+# <lp Local port number of the last server or peer connection
+# <qos Server connection TOS/DSCP value set by Squid
+# <nfmark Server connection netfilter mark set by Squid
+#
+# Time related format codes:
+#
+# ts Seconds since epoch
+# tu subsecond time (milliseconds)
+# tl Local time. Optional strftime format argument
+# default %d/%b/%Y:%H:%M:%S %z
+# tg GMT time. Optional strftime format argument
+# default %d/%b/%Y:%H:%M:%S %z
+# tr Response time (milliseconds)
+# dt Total time spent making DNS lookups (milliseconds)
+#
+# Access Control related format codes:
+#
+# et Tag returned by external acl
+# ea Log string returned by external acl
+# un User name (any available)
+# ul User name from authentication
+# ue User name from external acl helper
+# ui User name from ident
+# us User name from SSL
+#
+# HTTP related format codes:
+#
+# [http::]>h Original received request header.
+# Usually differs from the request header sent by
+# Squid, although most fields are often preserved.
+# Accepts optional header field name/value filter
+# argument using name[:[separator]element] format.
+# [http::]>ha Received request header after adaptation and
+# redirection (pre-cache REQMOD vectoring point).
+# Usually differs from the request header sent by
+# Squid, although most fields are often preserved.
+# Optional header name argument as for >h
+# [http::]<h Reply header. Optional header name argument
+# as for >h
+# [http::]>Hs HTTP status code sent to the client
+# [http::]<Hs HTTP status code received from the next hop
+# [http::]<bs Number of HTTP-equivalent message body bytes
+# received from the next hop, excluding chunked
+# transfer encoding and control messages.
+# Generated FTP/Gopher listings are treated as
+# received bodies.
+# [http::]mt MIME content type
+# [http::]rm Request method (GET/POST etc)
+# [http::]>rm Request method from client
+# [http::]<rm Request method sent to server or peer
+# [http::]ru Request URL from client (historic, filtered for logging)
+# [http::]>ru Request URL from client
+# [http::]<ru Request URL sent to server or peer
+# [http::]rp Request URL-Path excluding hostname
+# [http::]>rp Request URL-Path excluding hostname from client
+# [http::]<rp Request URL-Path excluding hostname sento to server or peer
+# [http::]rv Request protocol version
+# [http::]>rv Request protocol version from client
+# [http::]<rv Request protocol version sent to server or peer
+# [http::]<st Sent reply size including HTTP headers
+# [http::]>st Received request size including HTTP headers. In the
+# case of chunked requests the chunked encoding metadata
+# are not included
+# [http::]>sh Received HTTP request headers size
+# [http::]<sh Sent HTTP reply headers size
+# [http::]st Request+Reply size including HTTP headers
+# [http::]<sH Reply high offset sent
+# [http::]<sS Upstream object size
+# [http::]<pt Peer response time in milliseconds. The timer starts
+# when the last request byte is sent to the next hop
+# and stops when the last response byte is received.
+# [http::]<tt Total server-side time in milliseconds. The timer
+# starts with the first connect request (or write I/O)
+# sent to the first selected peer. The timer stops
+# with the last I/O with the last peer.
+#
+# Squid handling related format codes:
+#
+# Ss Squid request status (TCP_MISS etc)
+# Sh Squid hierarchy status (DEFAULT_PARENT etc)
+#
+# SSL-related format codes:
+#
+# ssl::bump_mode SslBump decision for the transaction:
+#
+# For CONNECT requests that initiated bumping of
+# a connection and for any request received on
+# an already bumped connection, Squid logs the
+# corresponding SslBump mode ("server-first" or
+# "client-first"). See the ssl_bump option for
+# more information about these modes.
+#
+# A "none" token is logged for requests that
+# triggered "ssl_bump" ACL evaluation matching
+# either a "none" rule or no rules at all.
+#
+# In all other cases, a single dash ("-") is
+# logged.
+#
+# If ICAP is enabled, the following code becomes available (as
+# well as ICAP log codes documented with the icap_log option):
+#
+# icap::tt Total ICAP processing time for the HTTP
+# transaction. The timer ticks when ICAP
+# ACLs are checked and when ICAP
+# transaction is in progress.
+#
+# If adaptation is enabled the following three codes become available:
+#
+# adapt::<last_h The header of the last ICAP response or
+# meta-information from the last eCAP
+# transaction related to the HTTP transaction.
+# Like <h, accepts an optional header name
+# argument.
+#
+# adapt::sum_trs Summed adaptation transaction response
+# times recorded as a comma-separated list in
+# the order of transaction start time. Each time
+# value is recorded as an integer number,
+# representing response time of one or more
+# adaptation (ICAP or eCAP) transaction in
+# milliseconds. When a failed transaction is
+# being retried or repeated, its time is not
+# logged individually but added to the
+# replacement (next) transaction. See also:
+# adapt::all_trs.
+#
+# adapt::all_trs All adaptation transaction response times.
+# Same as adaptation_strs but response times of
+# individual transactions are never added
+# together. Instead, all transaction response
+# times are recorded individually.
+#
+# You can prefix adapt::*_trs format codes with adaptation
+# service name in curly braces to record response time(s) specific
+# to that service. For example: %{my_service}adapt::sum_trs
+#
+# If SSL is enabled, the following formating codes become available:
+#
+# %ssl::>cert_subject The Subject field of the received client
+# SSL certificate or a dash ('-') if Squid has
+# received an invalid/malformed certificate or
+# no certificate at all. Consider encoding the
+# logged value because Subject often has spaces.
+#
+# %ssl::>cert_issuer The Issuer field of the received client
+# SSL certificate or a dash ('-') if Squid has
+# received an invalid/malformed certificate or
+# no certificate at all. Consider encoding the
+# logged value because Issuer often has spaces.
+#
+# The default formats available (which do not need re-defining) are:
+#
+#logformat squid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt
+#logformat common %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st %Ss:%Sh
+#logformat combined %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st "%{Referer}>h" "%{User-Agent}>h" %Ss:%Sh
+#logformat referrer %ts.%03tu %>a %{Referer}>h %ru
+#logformat useragent %>a [%tl] "%{User-Agent}>h"
+#
+# NOTE: When the log_mime_hdrs directive is set to ON.
+# The squid, common and combined formats have a safely encoded copy
+# of the mime headers appended to each line within a pair of brackets.
+#
+# NOTE: The common and combined formats are not quite true to the Apache definition.
+# The logs from Squid contain an extra status and hierarchy code appended.
+#
+#Default:
+# The format definitions squid, common, combined, referrer, useragent are built in.
+
+# TAG: access_log
+# Configures whether and how Squid logs HTTP and ICP transactions.
+# If access logging is enabled, a single line is logged for every
+# matching HTTP or ICP request. The recommended directive formats are:
+#
+# access_log <module>:<place> [option ...] [acl acl ...]
+# access_log none [acl acl ...]
+#
+# The following directive format is accepted but may be deprecated:
+# access_log <module>:<place> [<logformat name> [acl acl ...]]
+#
+# In most cases, the first ACL name must not contain the '=' character
+# and should not be equal to an existing logformat name. You can always
+# start with an 'all' ACL to work around those restrictions.
+#
+# Will log to the specified module:place using the specified format (which
+# must be defined in a logformat directive) those entries which match
+# ALL the acl's specified (which must be defined in acl clauses).
+# If no acl is specified, all requests will be logged to this destination.
+#
+# ===== Available options for the recommended directive format =====
+#
+# logformat=name Names log line format (either built-in or
+# defined by a logformat directive). Defaults
+# to 'squid'.
+#
+# buffer-size=64KB Defines approximate buffering limit for log
+# records (see buffered_logs). Squid should not
+# keep more than the specified size and, hence,
+# should flush records before the buffer becomes
+# full to avoid overflows under normal
+# conditions (the exact flushing algorithm is
+# module-dependent though). The on-error option
+# controls overflow handling.
+#
+# on-error=die|drop Defines action on unrecoverable errors. The
+# 'drop' action ignores (i.e., does not log)
+# affected log records. The default 'die' action
+# kills the affected worker. The drop action
+# support has not been tested for modules other
+# than tcp.
+#
+# ===== Modules Currently available =====
+#
+# none Do not log any requests matching these ACL.
+# Do not specify Place or logformat name.
+#
+# stdio Write each log line to disk immediately at the completion of
+# each request.
+# Place: the filename and path to be written.
+#
+# daemon Very similar to stdio. But instead of writing to disk the log
+# line is passed to a daemon helper for asychronous handling instead.
+# Place: varies depending on the daemon.
+#
+# log_file_daemon Place: the file name and path to be written.
+#
+# syslog To log each request via syslog facility.
+# Place: The syslog facility and priority level for these entries.
+# Place Format: facility.priority
+#
+# where facility could be any of:
+# authpriv, daemon, local0 ... local7 or user.
+#
+# And priority could be any of:
+# err, warning, notice, info, debug.
+#
+# udp To send each log line as text data to a UDP receiver.
+# Place: The destination host name or IP and port.
+# Place Format: //host:port
+#
+# tcp To send each log line as text data to a TCP receiver.
+# Lines may be accumulated before sending (see buffered_logs).
+# Place: The destination host name or IP and port.
+# Place Format: //host:port
+#
+# Default:
+# access_log daemon:/var/log/squid3/access.log squid
+#Default:
+# access_log daemon:/var/log/squid3/access.log squid
+
+# TAG: icap_log
+# ICAP log files record ICAP transaction summaries, one line per
+# transaction.
+#
+# The icap_log option format is:
+# icap_log <filepath> [<logformat name> [acl acl ...]]
+# icap_log none [acl acl ...]]
+#
+# Please see access_log option documentation for details. The two
+# kinds of logs share the overall configuration approach and many
+# features.
+#
+# ICAP processing of a single HTTP message or transaction may
+# require multiple ICAP transactions. In such cases, multiple
+# ICAP transaction log lines will correspond to a single access
+# log line.
+#
+# ICAP log uses logformat codes that make sense for an ICAP
+# transaction. Header-related codes are applied to the HTTP header
+# embedded in an ICAP server response, with the following caveats:
+# For REQMOD, there is no HTTP response header unless the ICAP
+# server performed request satisfaction. For RESPMOD, the HTTP
+# request header is the header sent to the ICAP server. For
+# OPTIONS, there are no HTTP headers.
+#
+# The following format codes are also available for ICAP logs:
+#
+# icap::<A ICAP server IP address. Similar to <A.
+#
+# icap::<service_name ICAP service name from the icap_service
+# option in Squid configuration file.
+#
+# icap::ru ICAP Request-URI. Similar to ru.
+#
+# icap::rm ICAP request method (REQMOD, RESPMOD, or
+# OPTIONS). Similar to existing rm.
+#
+# icap::>st Bytes sent to the ICAP server (TCP payload
+# only; i.e., what Squid writes to the socket).
+#
+# icap::<st Bytes received from the ICAP server (TCP
+# payload only; i.e., what Squid reads from
+# the socket).
+#
+# icap::<bs Number of message body bytes received from the
+# ICAP server. ICAP message body, if any, usually
+# includes encapsulated HTTP message headers and
+# possibly encapsulated HTTP message body. The
+# HTTP body part is dechunked before its size is
+# computed.
+#
+# icap::tr Transaction response time (in
+# milliseconds). The timer starts when
+# the ICAP transaction is created and
+# stops when the transaction is completed.
+# Similar to tr.
+#
+# icap::tio Transaction I/O time (in milliseconds). The
+# timer starts when the first ICAP request
+# byte is scheduled for sending. The timers
+# stops when the last byte of the ICAP response
+# is received.
+#
+# icap::to Transaction outcome: ICAP_ERR* for all
+# transaction errors, ICAP_OPT for OPTION
+# transactions, ICAP_ECHO for 204
+# responses, ICAP_MOD for message
+# modification, and ICAP_SAT for request
+# satisfaction. Similar to Ss.
+#
+# icap::Hs ICAP response status code. Similar to Hs.
+#
+# icap::>h ICAP request header(s). Similar to >h.
+#
+# icap::<h ICAP response header(s). Similar to <h.
+#
+# The default ICAP log format, which can be used without an explicit
+# definition, is called icap_squid:
+#
+#logformat icap_squid %ts.%03tu %6icap::tr %>a %icap::to/%03icap::Hs %icap::<size %icap::rm %icap::ru% %un -/%icap::<A -
+#
+# See also: logformat, log_icap, and %adapt::<last_h
+#Default:
+# none
+
+# TAG: logfile_daemon
+# Specify the path to the logfile-writing daemon. This daemon is
+# used to write the access and store logs, if configured.
+#
+# Squid sends a number of commands to the log daemon:
+# L<data>\n - logfile data
+# R\n - rotate file
+# T\n - truncate file
+# O\n - reopen file
+# F\n - flush file
+# r<n>\n - set rotate count to <n>
+# b<n>\n - 1 = buffer output, 0 = don't buffer output
+#
+# No responses is expected.
+#Default:
+# logfile_daemon /usr/lib/squid3/log_file_daemon
+
+# TAG: log_access
+# Remove this line. Use acls with access_log directives to control access logging
+#Default:
+# none
+
+# TAG: log_icap
+# Remove this line. Use acls with icap_log directives to control icap logging
+#Default:
+# none
+
+# TAG: stats_collection allow|deny acl acl...
+# This options allows you to control which requests gets accounted
+# in performance counters.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow logging for all transactions.
+
+# TAG: cache_store_log
+# Logs the activities of the storage manager. Shows which
+# objects are ejected from the cache, and which objects are
+# saved and for how long.
+# There are not really utilities to analyze this data, so you can safely
+# disable it (the default).
+#
+# Store log uses modular logging outputs. See access_log for the list
+# of modules supported.
+#
+# Example:
+# cache_store_log stdio:/var/log/squid3/store.log
+# cache_store_log daemon:/var/log/squid3/store.log
+#Default:
+# none
+
+# TAG: cache_swap_state
+# Location for the cache "swap.state" file. This index file holds
+# the metadata of objects saved on disk. It is used to rebuild
+# the cache during startup. Normally this file resides in each
+# 'cache_dir' directory, but you may specify an alternate
+# pathname here. Note you must give a full filename, not just
+# a directory. Since this is the index for the whole object
+# list you CANNOT periodically rotate it!
+#
+# If %s can be used in the file name it will be replaced with a
+# a representation of the cache_dir name where each / is replaced
+# with '.'. This is needed to allow adding/removing cache_dir
+# lines when cache_swap_log is being used.
+#
+# If have more than one 'cache_dir', and %s is not used in the name
+# these swap logs will have names such as:
+#
+# cache_swap_log.00
+# cache_swap_log.01
+# cache_swap_log.02
+#
+# The numbered extension (which is added automatically)
+# corresponds to the order of the 'cache_dir' lines in this
+# configuration file. If you change the order of the 'cache_dir'
+# lines in this file, these index files will NOT correspond to
+# the correct 'cache_dir' entry (unless you manually rename
+# them). We recommend you do NOT use this option. It is
+# better to keep these index files in each 'cache_dir' directory.
+#Default:
+# Store the journal inside its cache_dir
+
+# TAG: logfile_rotate
+# Specifies the number of logfile rotations to make when you
+# type 'squid -k rotate'. The default is 10, which will rotate
+# with extensions 0 through 9. Setting logfile_rotate to 0 will
+# disable the file name rotation, but the logfiles are still closed
+# and re-opened. This will enable you to rename the logfiles
+# yourself just before sending the rotate signal.
+#
+# Note, the 'squid -k rotate' command normally sends a USR1
+# signal to the running squid process. In certain situations
+# (e.g. on Linux with Async I/O), USR1 is used for other
+# purposes, so -k rotate uses another signal. It is best to get
+# in the habit of using 'squid -k rotate' instead of 'kill -USR1
+# <pid>'.
+#
+# Note, from Squid-3.1 this option is only a default for cache.log,
+# that log can be rotated separately by using debug_options.
+#
+# Note2, for Debian/Linux the default of logfile_rotate is
+# zero, since it includes external logfile-rotation methods.
+#Default:
+# logfile_rotate 0
+
+# TAG: emulate_httpd_log
+# Replace this with an access_log directive using the format 'common' or 'combined'.
+#Default:
+# none
+
+# TAG: log_ip_on_direct
+# Remove this option from your config. To log server or peer names use %<A in the log format.
+#Default:
+# none
+
+# TAG: mime_table
+# Path to Squid's icon configuration file.
+#
+# You shouldn't need to change this, but the default file contains
+# examples and formatting information if you do.
+#Default:
+# mime_table /usr/share/squid3/mime.conf
+
+# TAG: log_mime_hdrs on|off
+# The Cache can record both the request and the response MIME
+# headers for each HTTP transaction. The headers are encoded
+# safely and will appear as two bracketed fields at the end of
+# the access log (for either the native or httpd-emulated log
+# formats). To enable this logging set log_mime_hdrs to 'on'.
+#Default:
+# log_mime_hdrs off
+
+# TAG: useragent_log
+# Replace this with an access_log directive using the format 'useragent'.
+#Default:
+# none
+
+# TAG: referer_log
+# Replace this with an access_log directive using the format 'referrer'.
+#Default:
+# none
+
+# TAG: pid_filename
+# A filename to write the process-id to. To disable, enter "none".
+#Default:
+# pid_filename /var/run/squid3.pid
+
+# TAG: log_fqdn
+# Remove this option from your config. To log FQDN use %>A in the log format.
+#Default:
+# none
+
+# TAG: client_netmask
+# A netmask for client addresses in logfiles and cachemgr output.
+# Change this to protect the privacy of your cache clients.
+# A netmask of 255.255.255.0 will log all IP's in that range with
+# the last digit set to '0'.
+#Default:
+# Log full client IP address
+
+# TAG: forward_log
+# Use a regular access.log with ACL limiting it to MISS events.
+#Default:
+# none
+
+# TAG: strip_query_terms
+# By default, Squid strips query terms from requested URLs before
+# logging. This protects your user's privacy and reduces log size.
+#
+# When investigating HIT/MISS or other caching behaviour you
+# will need to disable this to see the full URL used by Squid.
+#Default:
+# strip_query_terms on
+
+# TAG: buffered_logs on|off
+# Whether to write/send access_log records ASAP or accumulate them and
+# then write/send them in larger chunks. Buffering may improve
+# performance because it decreases the number of I/Os. However,
+# buffering increases the delay before log records become available to
+# the final recipient (e.g., a disk file or logging daemon) and,
+# hence, increases the risk of log records loss.
+#
+# Note that even when buffered_logs are off, Squid may have to buffer
+# records if it cannot write/send them immediately due to pending I/Os
+# (e.g., the I/O writing the previous log record) or connectivity loss.
+#
+# Currently honored by 'daemon' and 'tcp' access_log modules only.
+#Default:
+# buffered_logs off
+
+# TAG: netdb_filename
+# Where Squid stores it's netdb journal.
+# When enabled this journal preserves netdb state between restarts.
+#
+# To disable, enter "none".
+#Default:
+# netdb_filename stdio:/var/log/squid3/netdb.state
+
+# OPTIONS FOR TROUBLESHOOTING
+# -----------------------------------------------------------------------------
+
+# TAG: cache_log
+# Squid administrative logging file.
+#
+# This is where general information about Squid behavior goes. You can
+# increase the amount of data logged to this file and how often it is
+# rotated with "debug_options"
+#Default:
+# cache_log /var/log/squid3/cache.log
+
+# TAG: debug_options
+# Logging options are set as section,level where each source file
+# is assigned a unique section. Lower levels result in less
+# output, Full debugging (level 9) can result in a very large
+# log file, so be careful.
+#
+# The magic word "ALL" sets debugging levels for all sections.
+# The default is to run with "ALL,1" to record important warnings.
+#
+# The rotate=N option can be used to keep more or less of these logs
+# than would otherwise be kept by logfile_rotate.
+# For most uses a single log should be enough to monitor current
+# events affecting Squid.
+#Default:
+# Log all critical and important messages.
+
+# TAG: coredump_dir
+# By default Squid leaves core files in the directory from where
+# it was started. If you set 'coredump_dir' to a directory
+# that exists, Squid will chdir() to that directory at startup
+# and coredump files will be left there.
+#
+#Default:
+# Use the directory from where Squid was started.
+#
+
+# Leave coredumps in the first cache dir
+coredump_dir /var/spool/squid3
+
+# OPTIONS FOR FTP GATEWAYING
+# -----------------------------------------------------------------------------
+
+# TAG: ftp_user
+# If you want the anonymous login password to be more informative
+# (and enable the use of picky FTP servers), set this to something
+# reasonable for your domain, like wwwuser@somewhere.net
+#
+# The reason why this is domainless by default is the
+# request can be made on the behalf of a user in any domain,
+# depending on how the cache is used.
+# Some FTP server also validate the email address is valid
+# (for example perl.com).
+#Default:
+# ftp_user Squid@
+
+# TAG: ftp_passive
+# If your firewall does not allow Squid to use passive
+# connections, turn off this option.
+#
+# Use of ftp_epsv_all option requires this to be ON.
+#Default:
+# ftp_passive on
+
+# TAG: ftp_epsv_all
+# FTP Protocol extensions permit the use of a special "EPSV ALL" command.
+#
+# NATs may be able to put the connection on a "fast path" through the
+# translator, as the EPRT command will never be used and therefore,
+# translation of the data portion of the segments will never be needed.
+#
+# When a client only expects to do two-way FTP transfers this may be
+# useful.
+# If squid finds that it must do a three-way FTP transfer after issuing
+# an EPSV ALL command, the FTP session will fail.
+#
+# If you have any doubts about this option do not use it.
+# Squid will nicely attempt all other connection methods.
+#
+# Requires ftp_passive to be ON (default) for any effect.
+#Default:
+# ftp_epsv_all off
+
+# TAG: ftp_epsv
+# FTP Protocol extensions permit the use of a special "EPSV" command.
+#
+# NATs may be able to put the connection on a "fast path" through the
+# translator using EPSV, as the EPRT command will never be used
+# and therefore, translation of the data portion of the segments
+# will never be needed.
+#
+# Turning this OFF will prevent EPSV being attempted.
+# WARNING: Doing so will convert Squid back to the old behavior with all
+# the related problems with external NAT devices/layers.
+#
+# Requires ftp_passive to be ON (default) for any effect.
+#Default:
+# ftp_epsv on
+
+# TAG: ftp_eprt
+# FTP Protocol extensions permit the use of a special "EPRT" command.
+#
+# This extension provides a protocol neutral alternative to the
+# IPv4-only PORT command. When supported it enables active FTP data
+# channels over IPv6 and efficient NAT handling.
+#
+# Turning this OFF will prevent EPRT being attempted and will skip
+# straight to using PORT for IPv4 servers.
+#
+# Some devices are known to not handle this extension correctly and
+# may result in crashes. Devices which suport EPRT enough to fail
+# cleanly will result in Squid attempting PORT anyway. This directive
+# should only be disabled when EPRT results in device failures.
+#
+# WARNING: Doing so will convert Squid back to the old behavior with all
+# the related problems with external NAT devices/layers and IPv4-only FTP.
+#Default:
+# ftp_eprt on
+
+# TAG: ftp_sanitycheck
+# For security and data integrity reasons Squid by default performs
+# sanity checks of the addresses of FTP data connections ensure the
+# data connection is to the requested server. If you need to allow
+# FTP connections to servers using another IP address for the data
+# connection turn this off.
+#Default:
+# ftp_sanitycheck on
+
+# TAG: ftp_telnet_protocol
+# The FTP protocol is officially defined to use the telnet protocol
+# as transport channel for the control connection. However, many
+# implementations are broken and does not respect this aspect of
+# the FTP protocol.
+#
+# If you have trouble accessing files with ASCII code 255 in the
+# path or similar problems involving this ASCII code you can
+# try setting this directive to off. If that helps, report to the
+# operator of the FTP server in question that their FTP server
+# is broken and does not follow the FTP standard.
+#Default:
+# ftp_telnet_protocol on
+
+# OPTIONS FOR EXTERNAL SUPPORT PROGRAMS
+# -----------------------------------------------------------------------------
+
+# TAG: diskd_program
+# Specify the location of the diskd executable.
+# Note this is only useful if you have compiled in
+# diskd as one of the store io modules.
+#Default:
+# diskd_program /usr/lib/squid3/diskd
+
+# TAG: unlinkd_program
+# Specify the location of the executable for file deletion process.
+#Default:
+# unlinkd_program /usr/lib/squid3/unlinkd
+
+# TAG: pinger_program
+# Specify the location of the executable for the pinger process.
+#Default:
+# pinger_program /usr/lib/squid3/pinger
+
+# TAG: pinger_enable
+# Control whether the pinger is active at run-time.
+# Enables turning ICMP pinger on and off with a simple
+# squid -k reconfigure.
+#Default:
+# pinger_enable on
+
+# OPTIONS FOR URL REWRITING
+# -----------------------------------------------------------------------------
+
+# TAG: url_rewrite_program
+# Specify the location of the executable URL rewriter to use.
+# Since they can perform almost any function there isn't one included.
+#
+# For each requested URL, the rewriter will receive on line with the format
+#
+# [channel-ID <SP>] URL <SP> client_ip "/" fqdn <SP> user <SP> method [<SP> kv-pairs]<NL>
+#
+#
+# After processing the request the helper must reply using the following format:
+#
+# [channel-ID <SP>] result [<SP> kv-pairs]
+#
+# The result code can be:
+#
+# OK status=30N url="..."
+# Redirect the URL to the one supplied in 'url='.
+# 'status=' is optional and contains the status code to send
+# the client in Squids HTTP response. It must be one of the
+# HTTP redirect status codes: 301, 302, 303, 307, 308.
+# When no status is given Squid will use 302.
+#
+# OK rewrite-url="..."
+# Rewrite the URL to the one supplied in 'rewrite-url='.
+# The new URL is fetched directly by Squid and returned to
+# the client as the response to its request.
+#
+# OK
+# When neither of url= and rewrite-url= are sent Squid does
+# not change the URL.
+#
+# ERR
+# Do not change the URL.
+#
+# BH
+# An internal error occurred in the helper, preventing
+# a result being identified. The 'message=' key name is
+# reserved for delivering a log message.
+#
+#
+# In the future, the interface protocol will be extended with
+# key=value pairs ("kv-pairs" shown above). Helper programs
+# should be prepared to receive and possibly ignore additional
+# whitespace-separated tokens on each input line.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+# WARNING: URL re-writing ability should be avoided whenever possible.
+# Use the URL redirect form of response instead.
+#
+# Re-write creates a difference in the state held by the client
+# and server. Possibly causing confusion when the server response
+# contains snippets of its view state. Embeded URLs, response
+# and content Location headers, etc. are not re-written by this
+# interface.
+#
+# By default, a URL rewriter is not used.
+#Default:
+# none
+
+# TAG: url_rewrite_children
+# The maximum number of redirector processes to spawn. If you limit
+# it too few Squid will have to wait for them to process a backlog of
+# URLs, slowing it down. If you allow too many they will use RAM
+# and other system resources noticably.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=
+#
+# Sets a minimum of how many processes are to be spawned when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few will cause an initial slowdown in traffic as Squid
+# attempts to simultaneously spawn enough processes to cope.
+#
+# idle=
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each redirector helper can handle in
+# parallel. Defaults to 0 which indicates the redirector
+# is a old-style single threaded redirector.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# an ID in front of the request/response. The ID from the request
+# must be echoed back with the response to that request.
+#Default:
+# url_rewrite_children 20 startup=0 idle=1 concurrency=0
+
+# TAG: url_rewrite_host_header
+# To preserve same-origin security policies in browsers and
+# prevent Host: header forgery by redirectors Squid rewrites
+# any Host: header in redirected requests.
+#
+# If you are running an accelerator this may not be a wanted
+# effect of a redirector. This directive enables you disable
+# Host: alteration in reverse-proxy traffic.
+#
+# WARNING: Entries are cached on the result of the URL rewriting
+# process, so be careful if you have domain-virtual hosts.
+#
+# WARNING: Squid and other software verifies the URL and Host
+# are matching, so be careful not to relay through other proxies
+# or inspecting firewalls with this disabled.
+#Default:
+# url_rewrite_host_header on
+
+# TAG: url_rewrite_access
+# If defined, this access list specifies which requests are
+# sent to the redirector processes.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: url_rewrite_bypass
+# When this is 'on', a request will not go through the
+# redirector if all the helpers are busy. If this is 'off'
+# and the redirector queue grows too large, Squid will exit
+# with a FATAL error and ask you to increase the number of
+# redirectors. You should only enable this if the redirectors
+# are not critical to your caching system. If you use
+# redirectors for access control, and you enable this option,
+# users may have access to pages they should not
+# be allowed to request.
+#Default:
+# url_rewrite_bypass off
+
+# OPTIONS FOR STORE ID
+# -----------------------------------------------------------------------------
+
+# TAG: store_id_program
+# Specify the location of the executable StoreID helper to use.
+# Since they can perform almost any function there isn't one included.
+#
+# For each requested URL, the helper will receive one line with the format
+#
+# [channel-ID <SP>] URL <SP> client_ip "/" fqdn <SP> user <SP> method [<SP> kv-pairs]<NL>
+#
+#
+# After processing the request the helper must reply using the following format:
+#
+# [channel-ID <SP>] result [<SP> kv-pairs]
+#
+# The result code can be:
+#
+# OK store-id="..."
+# Use the StoreID supplied in 'store-id='.
+#
+# ERR
+# The default is to use HTTP request URL as the store ID.
+#
+# BH
+# An internal error occured in the helper, preventing
+# a result being identified.
+#
+#
+# Helper programs should be prepared to receive and possibly ignore additional
+# kv-pairs with keys they do not support.
+#
+# When using the concurrency= option the protocol is changed by
+# introducing a query channel tag in front of the request/response.
+# The query channel tag is a number between 0 and concurrency-1.
+# This value must be echoed back unchanged to Squid as the first part
+# of the response relating to its request.
+#
+# NOTE: when using StoreID refresh_pattern will apply to the StoreID
+# returned from the helper and not the URL.
+#
+# WARNING: Wrong StoreID value returned by a careless helper may result
+# in the wrong cached response returned to the user.
+#
+# By default, a StoreID helper is not used.
+#Default:
+# none
+
+# TAG: store_id_children
+# The maximum number of StoreID helper processes to spawn. If you limit
+# it too few Squid will have to wait for them to process a backlog of
+# requests, slowing it down. If you allow too many they will use RAM
+# and other system resources noticably.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=
+#
+# Sets a minimum of how many processes are to be spawned when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few will cause an initial slowdown in traffic as Squid
+# attempts to simultaneously spawn enough processes to cope.
+#
+# idle=
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#
+# concurrency=
+#
+# The number of requests each storeID helper can handle in
+# parallel. Defaults to 0 which indicates the helper
+# is a old-style single threaded program.
+#
+# When this directive is set to a value >= 1 then the protocol
+# used to communicate with the helper is modified to include
+# an ID in front of the request/response. The ID from the request
+# must be echoed back with the response to that request.
+#Default:
+# store_id_children 20 startup=0 idle=1 concurrency=0
+
+# TAG: store_id_access
+# If defined, this access list specifies which requests are
+# sent to the StoreID processes. By default all requests
+# are sent.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: store_id_bypass
+# When this is 'on', a request will not go through the
+# helper if all helpers are busy. If this is 'off'
+# and the helper queue grows too large, Squid will exit
+# with a FATAL error and ask you to increase the number of
+# helpers. You should only enable this if the helperss
+# are not critical to your caching system. If you use
+# helpers for critical caching components, and you enable this
+# option, users may not get objects from cache.
+#Default:
+# store_id_bypass on
+
+# OPTIONS FOR TUNING THE CACHE
+# -----------------------------------------------------------------------------
+
+# TAG: cache
+# A list of ACL elements which, if matched and denied, cause the request to
+# not be satisfied from the cache and the reply to not be cached.
+# In other words, use this to force certain objects to never be cached.
+#
+# You must use the words 'allow' or 'deny' to indicate whether items
+# matching the ACL should be allowed or denied into the cache.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow caching, unless rules exist in squid.conf.
+
+# TAG: max_stale time-units
+# This option puts an upper limit on how stale content Squid
+# will serve from the cache if cache validation fails.
+# Can be overriden by the refresh_pattern max-stale option.
+#Default:
+# max_stale 1 week
+
+# TAG: refresh_pattern
+# usage: refresh_pattern [-i] regex min percent max [options]
+#
+# By default, regular expressions are CASE-SENSITIVE. To make
+# them case-insensitive, use the -i option.
+#
+# 'Min' is the time (in minutes) an object without an explicit
+# expiry time should be considered fresh. The recommended
+# value is 0, any higher values may cause dynamic applications
+# to be erroneously cached unless the application designer
+# has taken the appropriate actions.
+#
+# 'Percent' is a percentage of the objects age (time since last
+# modification age) an object without explicit expiry time
+# will be considered fresh.
+#
+# 'Max' is an upper limit on how long objects without an explicit
+# expiry time will be considered fresh.
+#
+# options: override-expire
+# override-lastmod
+# reload-into-ims
+# ignore-reload
+# ignore-no-store
+# ignore-must-revalidate
+# ignore-private
+# ignore-auth
+# max-stale=NN
+# refresh-ims
+# store-stale
+#
+# override-expire enforces min age even if the server
+# sent an explicit expiry time (e.g., with the
+# Expires: header or Cache-Control: max-age). Doing this
+# VIOLATES the HTTP standard. Enabling this feature
+# could make you liable for problems which it causes.
+#
+# Note: override-expire does not enforce staleness - it only extends
+# freshness / min. If the server returns a Expires time which
+# is longer than your max time, Squid will still consider
+# the object fresh for that period of time.
+#
+# override-lastmod enforces min age even on objects
+# that were modified recently.
+#
+# reload-into-ims changes a client no-cache or ``reload''
+# request for a cached entry into a conditional request using
+# If-Modified-Since and/or If-None-Match headers, provided the
+# cached entry has a Last-Modified and/or a strong ETag header.
+# Doing this VIOLATES the HTTP standard. Enabling this feature
+# could make you liable for problems which it causes.
+#
+# ignore-reload ignores a client no-cache or ``reload''
+# header. Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which
+# it causes.
+#
+# ignore-no-store ignores any ``Cache-control: no-store''
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# ignore-must-revalidate ignores any ``Cache-Control: must-revalidate``
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# ignore-private ignores any ``Cache-control: private''
+# headers received from a server. Doing this VIOLATES
+# the HTTP standard. Enabling this feature could make you
+# liable for problems which it causes.
+#
+# ignore-auth caches responses to requests with authorization,
+# as if the originserver had sent ``Cache-control: public''
+# in the response header. Doing this VIOLATES the HTTP standard.
+# Enabling this feature could make you liable for problems which
+# it causes.
+#
+# refresh-ims causes squid to contact the origin server
+# when a client issues an If-Modified-Since request. This
+# ensures that the client will receive an updated version
+# if one is available.
+#
+# store-stale stores responses even if they don't have explicit
+# freshness or a validator (i.e., Last-Modified or an ETag)
+# present, or if they're already stale. By default, Squid will
+# not cache such responses because they usually can't be
+# reused. Note that such responses will be stale by default.
+#
+# max-stale=NN provide a maximum staleness factor. Squid won't
+# serve objects more stale than this even if it failed to
+# validate the object. Default: use the max_stale global limit.
+#
+# Basically a cached object is:
+#
+# FRESH if expires < now, else STALE
+# STALE if age > max
+# FRESH if lm-factor < percent, else STALE
+# FRESH if age < min
+# else STALE
+#
+# The refresh_pattern lines are checked in the order listed here.
+# The first entry which matches is used. If none of the entries
+# match the default will be used.
+#
+# Note, you must uncomment all the default lines if you want
+# to change one. The default setting is only active if none is
+# used.
+#
+#
+
+#
+# Add any of your own refresh_pattern entries above these.
+#
+refresh_pattern ^ftp: 1440 20% 10080
+refresh_pattern ^gopher: 1440 0% 1440
+refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
+refresh_pattern . 0 20% 4320
+
+# TAG: quick_abort_min (KB)
+#Default:
+# quick_abort_min 16 KB
+
+# TAG: quick_abort_max (KB)
+#Default:
+# quick_abort_max 16 KB
+
+# TAG: quick_abort_pct (percent)
+# The cache by default continues downloading aborted requests
+# which are almost completed (less than 16 KB remaining). This
+# may be undesirable on slow (e.g. SLIP) links and/or very busy
+# caches. Impatient users may tie up file descriptors and
+# bandwidth by repeatedly requesting and immediately aborting
+# downloads.
+#
+# When the user aborts a request, Squid will check the
+# quick_abort values to the amount of data transferred until
+# then.
+#
+# If the transfer has less than 'quick_abort_min' KB remaining,
+# it will finish the retrieval.
+#
+# If the transfer has more than 'quick_abort_max' KB remaining,
+# it will abort the retrieval.
+#
+# If more than 'quick_abort_pct' of the transfer has completed,
+# it will finish the retrieval.
+#
+# If you do not want any retrieval to continue after the client
+# has aborted, set both 'quick_abort_min' and 'quick_abort_max'
+# to '0 KB'.
+#
+# If you want retrievals to always continue if they are being
+# cached set 'quick_abort_min' to '-1 KB'.
+#Default:
+# quick_abort_pct 95
+
+# TAG: read_ahead_gap buffer-size
+# The amount of data the cache will buffer ahead of what has been
+# sent to the client when retrieving an object from another server.
+#Default:
+# read_ahead_gap 16 KB
+
+# TAG: negative_ttl time-units
+# Set the Default Time-to-Live (TTL) for failed requests.
+# Certain types of failures (such as "connection refused" and
+# "404 Not Found") are able to be negatively-cached for a short time.
+# Modern web servers should provide Expires: header, however if they
+# do not this can provide a minimum TTL.
+# The default is not to cache errors with unknown expiry details.
+#
+# Note that this is different from negative caching of DNS lookups.
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#Default:
+# negative_ttl 0 seconds
+
+# TAG: positive_dns_ttl time-units
+# Upper limit on how long Squid will cache positive DNS responses.
+# Default is 6 hours (360 minutes). This directive must be set
+# larger than negative_dns_ttl.
+#Default:
+# positive_dns_ttl 6 hours
+
+# TAG: negative_dns_ttl time-units
+# Time-to-Live (TTL) for negative caching of failed DNS lookups.
+# This also sets the lower cache limit on positive lookups.
+# Minimum value is 1 second, and it is not recommendable to go
+# much below 10 seconds.
+#Default:
+# negative_dns_ttl 1 minutes
+
+# TAG: range_offset_limit size [acl acl...]
+# usage: (size) [units] [[!]aclname]
+#
+# Sets an upper limit on how far (number of bytes) into the file
+# a Range request may be to cause Squid to prefetch the whole file.
+# If beyond this limit, Squid forwards the Range request as it is and
+# the result is NOT cached.
+#
+# This is to stop a far ahead range request (lets say start at 17MB)
+# from making Squid fetch the whole object up to that point before
+# sending anything to the client.
+#
+# Multiple range_offset_limit lines may be specified, and they will
+# be searched from top to bottom on each request until a match is found.
+# The first match found will be used. If no line matches a request, the
+# default limit of 0 bytes will be used.
+#
+# 'size' is the limit specified as a number of units.
+#
+# 'units' specifies whether to use bytes, KB, MB, etc.
+# If no units are specified bytes are assumed.
+#
+# A size of 0 causes Squid to never fetch more than the
+# client requested. (default)
+#
+# A size of 'none' causes Squid to always fetch the object from the
+# beginning so it may cache the result. (2.0 style)
+#
+# 'aclname' is the name of a defined ACL.
+#
+# NP: Using 'none' as the byte value here will override any quick_abort settings
+# that may otherwise apply to the range request. The range request will
+# be fully fetched from start to finish regardless of the client
+# actions. This affects bandwidth usage.
+#Default:
+# none
+
+# TAG: minimum_expiry_time (seconds)
+# The minimum caching time according to (Expires - Date)
+# headers Squid honors if the object can't be revalidated.
+# The default is 60 seconds.
+#
+# In reverse proxy environments it might be desirable to honor
+# shorter object lifetimes. It is most likely better to make
+# your server return a meaningful Last-Modified header however.
+#
+# In ESI environments where page fragments often have short
+# lifetimes, this will often be best set to 0.
+#Default:
+# minimum_expiry_time 60 seconds
+
+# TAG: store_avg_object_size (bytes)
+# Average object size, used to estimate number of objects your
+# cache can hold. The default is 13 KB.
+#
+# This is used to pre-seed the cache index memory allocation to
+# reduce expensive reallocate operations while handling clients
+# traffic. Too-large values may result in memory allocation during
+# peak traffic, too-small values will result in wasted memory.
+#
+# Check the cache manager 'info' report metrics for the real
+# object sizes seen by your Squid before tuning this.
+#Default:
+# store_avg_object_size 13 KB
+
+# TAG: store_objects_per_bucket
+# Target number of objects per bucket in the store hash table.
+# Lowering this value increases the total number of buckets and
+# also the storage maintenance rate. The default is 20.
+#Default:
+# store_objects_per_bucket 20
+
+# HTTP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: request_header_max_size (KB)
+# This specifies the maximum size for HTTP headers in a request.
+# Request headers are usually relatively small (about 512 bytes).
+# Placing a limit on the request header size will catch certain
+# bugs (for example with persistent connections) and possibly
+# buffer-overflow or denial-of-service attacks.
+#Default:
+# request_header_max_size 64 KB
+
+# TAG: reply_header_max_size (KB)
+# This specifies the maximum size for HTTP headers in a reply.
+# Reply headers are usually relatively small (about 512 bytes).
+# Placing a limit on the reply header size will catch certain
+# bugs (for example with persistent connections) and possibly
+# buffer-overflow or denial-of-service attacks.
+#Default:
+# reply_header_max_size 64 KB
+
+# TAG: request_body_max_size (bytes)
+# This specifies the maximum size for an HTTP request body.
+# In other words, the maximum size of a PUT/POST request.
+# A user who attempts to send a request with a body larger
+# than this limit receives an "Invalid Request" error message.
+# If you set this parameter to a zero (the default), there will
+# be no limit imposed.
+#
+# See also client_request_buffer_max_size for an alternative
+# limitation on client uploads which can be configured.
+#Default:
+# No limit.
+
+# TAG: client_request_buffer_max_size (bytes)
+# This specifies the maximum buffer size of a client request.
+# It prevents squid eating too much memory when somebody uploads
+# a large file.
+#Default:
+# client_request_buffer_max_size 512 KB
+
+# TAG: chunked_request_body_max_size (bytes)
+# A broken or confused HTTP/1.1 client may send a chunked HTTP
+# request to Squid. Squid does not have full support for that
+# feature yet. To cope with such requests, Squid buffers the
+# entire request and then dechunks request body to create a
+# plain HTTP/1.0 request with a known content length. The plain
+# request is then used by the rest of Squid code as usual.
+#
+# The option value specifies the maximum size of the buffer used
+# to hold the request before the conversion. If the chunked
+# request size exceeds the specified limit, the conversion
+# fails, and the client receives an "unsupported request" error,
+# as if dechunking was disabled.
+#
+# Dechunking is enabled by default. To disable conversion of
+# chunked requests, set the maximum to zero.
+#
+# Request dechunking feature and this option in particular are a
+# temporary hack. When chunking requests and responses are fully
+# supported, there will be no need to buffer a chunked request.
+#Default:
+# chunked_request_body_max_size 64 KB
+
+# TAG: broken_posts
+# A list of ACL elements which, if matched, causes Squid to send
+# an extra CRLF pair after the body of a PUT/POST request.
+#
+# Some HTTP servers has broken implementations of PUT/POST,
+# and rely on an extra CRLF pair sent by some WWW clients.
+#
+# Quote from RFC2616 section 4.1 on this matter:
+#
+# Note: certain buggy HTTP/1.0 client implementations generate an
+# extra CRLF's after a POST request. To restate what is explicitly
+# forbidden by the BNF, an HTTP/1.1 client must not preface or follow
+# a request with an extra CRLF.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Example:
+# acl buggy_server url_regex ^http://....
+# broken_posts allow buggy_server
+#Default:
+# Obey RFC 2616.
+
+# TAG: adaptation_uses_indirect_client on|off
+# Controls whether the indirect client IP address (instead of the direct
+# client IP address) is passed to adaptation services.
+#
+# See also: follow_x_forwarded_for adaptation_send_client_ip
+#Default:
+# adaptation_uses_indirect_client on
+
+# TAG: via on|off
+# If set (default), Squid will include a Via header in requests and
+# replies as required by RFC2616.
+#Default:
+# via on
+
+# TAG: ie_refresh on|off
+# Microsoft Internet Explorer up until version 5.5 Service
+# Pack 1 has an issue with transparent proxies, wherein it
+# is impossible to force a refresh. Turning this on provides
+# a partial fix to the problem, by causing all IMS-REFRESH
+# requests from older IE versions to check the origin server
+# for fresh content. This reduces hit ratio by some amount
+# (~10% in my experience), but allows users to actually get
+# fresh content when they want it. Note because Squid
+# cannot tell if the user is using 5.5 or 5.5SP1, the behavior
+# of 5.5 is unchanged from old versions of Squid (i.e. a
+# forced refresh is impossible). Newer versions of IE will,
+# hopefully, continue to have the new behavior and will be
+# handled based on that assumption. This option defaults to
+# the old Squid behavior, which is better for hit ratios but
+# worse for clients using IE, if they need to be able to
+# force fresh content.
+#Default:
+# ie_refresh off
+
+# TAG: vary_ignore_expire on|off
+# Many HTTP servers supporting Vary gives such objects
+# immediate expiry time with no cache-control header
+# when requested by a HTTP/1.0 client. This option
+# enables Squid to ignore such expiry times until
+# HTTP/1.1 is fully implemented.
+#
+# WARNING: If turned on this may eventually cause some
+# varying objects not intended for caching to get cached.
+#Default:
+# vary_ignore_expire off
+
+# TAG: request_entities
+# Squid defaults to deny GET and HEAD requests with request entities,
+# as the meaning of such requests are undefined in the HTTP standard
+# even if not explicitly forbidden.
+#
+# Set this directive to on if you have clients which insists
+# on sending request entities in GET or HEAD requests. But be warned
+# that there is server software (both proxies and web servers) which
+# can fail to properly process this kind of request which may make you
+# vulnerable to cache pollution attacks if enabled.
+#Default:
+# request_entities off
+
+# TAG: request_header_access
+# Usage: request_header_access header_name allow|deny [!]aclname ...
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#
+# This option replaces the old 'anonymize_headers' and the
+# older 'http_anonymizer' option with something that is much
+# more configurable. A list of ACLs for each header name allows
+# removal of specific header fields under specific conditions.
+#
+# This option only applies to outgoing HTTP request headers (i.e.,
+# headers sent by Squid to the next HTTP hop such as a cache peer
+# or an origin server). The option has no effect during cache hit
+# detection. The equivalent adaptation vectoring point in ICAP
+# terminology is post-cache REQMOD.
+#
+# The option is applied to individual outgoing request header
+# fields. For each request header field F, Squid uses the first
+# qualifying sets of request_header_access rules:
+#
+# 1. Rules with header_name equal to F's name.
+# 2. Rules with header_name 'Other', provided F's name is not
+# on the hard-coded list of commonly used HTTP header names.
+# 3. Rules with header_name 'All'.
+#
+# Within that qualifying rule set, rule ACLs are checked as usual.
+# If ACLs of an "allow" rule match, the header field is allowed to
+# go through as is. If ACLs of a "deny" rule match, the header is
+# removed and request_header_replace is then checked to identify
+# if the removed header has a replacement. If no rules within the
+# set have matching ACLs, the header field is left as is.
+#
+# For example, to achieve the same behavior as the old
+# 'http_anonymizer standard' option, you should use:
+#
+# request_header_access From deny all
+# request_header_access Referer deny all
+# request_header_access User-Agent deny all
+#
+# Or, to reproduce the old 'http_anonymizer paranoid' feature
+# you should use:
+#
+# request_header_access Authorization allow all
+# request_header_access Proxy-Authorization allow all
+# request_header_access Cache-Control allow all
+# request_header_access Content-Length allow all
+# request_header_access Content-Type allow all
+# request_header_access Date allow all
+# request_header_access Host allow all
+# request_header_access If-Modified-Since allow all
+# request_header_access Pragma allow all
+# request_header_access Accept allow all
+# request_header_access Accept-Charset allow all
+# request_header_access Accept-Encoding allow all
+# request_header_access Accept-Language allow all
+# request_header_access Connection allow all
+# request_header_access All deny all
+#
+# HTTP reply headers are controlled with the reply_header_access directive.
+#
+# By default, all headers are allowed (no anonymizing is performed).
+#Default:
+# No limits.
+
+# TAG: reply_header_access
+# Usage: reply_header_access header_name allow|deny [!]aclname ...
+#
+# WARNING: Doing this VIOLATES the HTTP standard. Enabling
+# this feature could make you liable for problems which it
+# causes.
+#
+# This option only applies to reply headers, i.e., from the
+# server to the client.
+#
+# This is the same as request_header_access, but in the other
+# direction. Please see request_header_access for detailed
+# documentation.
+#
+# For example, to achieve the same behavior as the old
+# 'http_anonymizer standard' option, you should use:
+#
+# reply_header_access Server deny all
+# reply_header_access WWW-Authenticate deny all
+# reply_header_access Link deny all
+#
+# Or, to reproduce the old 'http_anonymizer paranoid' feature
+# you should use:
+#
+# reply_header_access Allow allow all
+# reply_header_access WWW-Authenticate allow all
+# reply_header_access Proxy-Authenticate allow all
+# reply_header_access Cache-Control allow all
+# reply_header_access Content-Encoding allow all
+# reply_header_access Content-Length allow all
+# reply_header_access Content-Type allow all
+# reply_header_access Date allow all
+# reply_header_access Expires allow all
+# reply_header_access Last-Modified allow all
+# reply_header_access Location allow all
+# reply_header_access Pragma allow all
+# reply_header_access Content-Language allow all
+# reply_header_access Retry-After allow all
+# reply_header_access Title allow all
+# reply_header_access Content-Disposition allow all
+# reply_header_access Connection allow all
+# reply_header_access All deny all
+#
+# HTTP request headers are controlled with the request_header_access directive.
+#
+# By default, all headers are allowed (no anonymizing is
+# performed).
+#Default:
+# No limits.
+
+# TAG: request_header_replace
+# Usage: request_header_replace header_name message
+# Example: request_header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit)
+#
+# This option allows you to change the contents of headers
+# denied with request_header_access above, by replacing them
+# with some fixed string.
+#
+# This only applies to request headers, not reply headers.
+#
+# By default, headers are removed if denied.
+#Default:
+# none
+
+# TAG: reply_header_replace
+# Usage: reply_header_replace header_name message
+# Example: reply_header_replace Server Foo/1.0
+#
+# This option allows you to change the contents of headers
+# denied with reply_header_access above, by replacing them
+# with some fixed string.
+#
+# This only applies to reply headers, not request headers.
+#
+# By default, headers are removed if denied.
+#Default:
+# none
+
+# TAG: request_header_add
+# Usage: request_header_add field-name field-value acl1 [acl2] ...
+# Example: request_header_add X-Client-CA "CA=%ssl::>cert_issuer" all
+#
+# This option adds header fields to outgoing HTTP requests (i.e.,
+# request headers sent by Squid to the next HTTP hop such as a
+# cache peer or an origin server). The option has no effect during
+# cache hit detection. The equivalent adaptation vectoring point
+# in ICAP terminology is post-cache REQMOD.
+#
+# Field-name is a token specifying an HTTP header name. If a
+# standard HTTP header name is used, Squid does not check whether
+# the new header conflicts with any existing headers or violates
+# HTTP rules. If the request to be modified already contains a
+# field with the same name, the old field is preserved but the
+# header field values are not merged.
+#
+# Field-value is either a token or a quoted string. If quoted
+# string format is used, then the surrounding quotes are removed
+# while escape sequences and %macros are processed.
+#
+# In theory, all of the logformat codes can be used as %macros.
+# However, unlike logging (which happens at the very end of
+# transaction lifetime), the transaction may not yet have enough
+# information to expand a macro when the new header value is needed.
+# And some information may already be available to Squid but not yet
+# committed where the macro expansion code can access it (report
+# such instances!). The macro will be expanded into a single dash
+# ('-') in such cases. Not all macros have been tested.
+#
+# One or more Squid ACLs may be specified to restrict header
+# injection to matching requests. As always in squid.conf, all
+# ACLs in an option ACL list must be satisfied for the insertion
+# to happen. The request_header_add option supports fast ACLs
+# only.
+#Default:
+# none
+
+# TAG: note
+# This option used to log custom information about the master
+# transaction. For example, an admin may configure Squid to log
+# which "user group" the transaction belongs to, where "user group"
+# will be determined based on a set of ACLs and not [just]
+# authentication information.
+# Values of key/value pairs can be logged using %{key}note macros:
+#
+# note key value acl ...
+# logformat myFormat ... %{key}note ...
+#Default:
+# none
+
+# TAG: relaxed_header_parser on|off|warn
+# In the default "on" setting Squid accepts certain forms
+# of non-compliant HTTP messages where it is unambiguous
+# what the sending application intended even if the message
+# is not correctly formatted. The messages is then normalized
+# to the correct form when forwarded by Squid.
+#
+# If set to "warn" then a warning will be emitted in cache.log
+# each time such HTTP error is encountered.
+#
+# If set to "off" then such HTTP errors will cause the request
+# or response to be rejected.
+#Default:
+# relaxed_header_parser on
+
+# TIMEOUTS
+# -----------------------------------------------------------------------------
+
+# TAG: forward_timeout time-units
+# This parameter specifies how long Squid should at most attempt in
+# finding a forwarding path for the request before giving up.
+#Default:
+# forward_timeout 4 minutes
+
+# TAG: connect_timeout time-units
+# This parameter specifies how long to wait for the TCP connect to
+# the requested server or peer to complete before Squid should
+# attempt to find another path where to forward the request.
+#Default:
+# connect_timeout 1 minute
+
+# TAG: peer_connect_timeout time-units
+# This parameter specifies how long to wait for a pending TCP
+# connection to a peer cache. The default is 30 seconds. You
+# may also set different timeout values for individual neighbors
+# with the 'connect-timeout' option on a 'cache_peer' line.
+#Default:
+# peer_connect_timeout 30 seconds
+
+# TAG: read_timeout time-units
+# The read_timeout is applied on server-side connections. After
+# each successful read(), the timeout will be extended by this
+# amount. If no data is read again after this amount of time,
+# the request is aborted and logged with ERR_READ_TIMEOUT. The
+# default is 15 minutes.
+#Default:
+# read_timeout 15 minutes
+
+# TAG: write_timeout time-units
+# This timeout is tracked for all connections that have data
+# available for writing and are waiting for the socket to become
+# ready. After each successful write, the timeout is extended by
+# the configured amount. If Squid has data to write but the
+# connection is not ready for the configured duration, the
+# transaction associated with the connection is terminated. The
+# default is 15 minutes.
+#Default:
+# write_timeout 15 minutes
+
+# TAG: request_timeout
+# How long to wait for complete HTTP request headers after initial
+# connection establishment.
+#Default:
+# request_timeout 5 minutes
+
+# TAG: client_idle_pconn_timeout
+# How long to wait for the next HTTP request on a persistent
+# client connection after the previous request completes.
+#Default:
+# client_idle_pconn_timeout 2 minutes
+
+# TAG: client_lifetime time-units
+# The maximum amount of time a client (browser) is allowed to
+# remain connected to the cache process. This protects the Cache
+# from having a lot of sockets (and hence file descriptors) tied up
+# in a CLOSE_WAIT state from remote clients that go away without
+# properly shutting down (either because of a network failure or
+# because of a poor client implementation). The default is one
+# day, 1440 minutes.
+#
+# NOTE: The default value is intended to be much larger than any
+# client would ever need to be connected to your cache. You
+# should probably change client_lifetime only as a last resort.
+# If you seem to have many client connections tying up
+# filedescriptors, we recommend first tuning the read_timeout,
+# request_timeout, persistent_request_timeout and quick_abort values.
+#Default:
+# client_lifetime 1 day
+
+# TAG: half_closed_clients
+# Some clients may shutdown the sending side of their TCP
+# connections, while leaving their receiving sides open. Sometimes,
+# Squid can not tell the difference between a half-closed and a
+# fully-closed TCP connection.
+#
+# By default, Squid will immediately close client connections when
+# read(2) returns "no more data to read."
+#
+# Change this option to 'on' and Squid will keep open connections
+# until a read(2) or write(2) on the socket returns an error.
+# This may show some benefits for reverse proxies. But if not
+# it is recommended to leave OFF.
+#Default:
+# half_closed_clients off
+
+# TAG: server_idle_pconn_timeout
+# Timeout for idle persistent connections to servers and other
+# proxies.
+#Default:
+# server_idle_pconn_timeout 1 minute
+
+# TAG: ident_timeout
+# Maximum time to wait for IDENT lookups to complete.
+#
+# If this is too high, and you enabled IDENT lookups from untrusted
+# users, you might be susceptible to denial-of-service by having
+# many ident requests going at once.
+#Default:
+# ident_timeout 10 seconds
+
+# TAG: shutdown_lifetime time-units
+# When SIGTERM or SIGHUP is received, the cache is put into
+# "shutdown pending" mode until all active sockets are closed.
+# This value is the lifetime to set for all open descriptors
+# during shutdown mode. Any active clients after this many
+# seconds will receive a 'timeout' message.
+#Default:
+# shutdown_lifetime 30 seconds
+
+# ADMINISTRATIVE PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: cache_mgr
+# Email-address of local cache manager who will receive
+# mail if the cache dies. The default is "webmaster".
+#Default:
+# cache_mgr webmaster
+
+# TAG: mail_from
+# From: email-address for mail sent when the cache dies.
+# The default is to use 'squid@unique_hostname'.
+#
+# See also: unique_hostname directive.
+#Default:
+# none
+
+# TAG: mail_program
+# Email program used to send mail if the cache dies.
+# The default is "mail". The specified program must comply
+# with the standard Unix mail syntax:
+# mail-program recipient < mailfile
+#
+# Optional command line options can be specified.
+#Default:
+# mail_program mail
+
+# TAG: cache_effective_user
+# If you start Squid as root, it will change its effective/real
+# UID/GID to the user specified below. The default is to change
+# to UID of proxy.
+# see also; cache_effective_group
+#Default:
+# cache_effective_user proxy
+
+# TAG: cache_effective_group
+# Squid sets the GID to the effective user's default group ID
+# (taken from the password file) and supplementary group list
+# from the groups membership.
+#
+# If you want Squid to run with a specific GID regardless of
+# the group memberships of the effective user then set this
+# to the group (or GID) you want Squid to run as. When set
+# all other group privileges of the effective user are ignored
+# and only this GID is effective. If Squid is not started as
+# root the user starting Squid MUST be member of the specified
+# group.
+#
+# This option is not recommended by the Squid Team.
+# Our preference is for administrators to configure a secure
+# user account for squid with UID/GID matching system policies.
+#Default:
+# Use system group memberships of the cache_effective_user account
+
+# TAG: httpd_suppress_version_string on|off
+# Suppress Squid version string info in HTTP headers and HTML error pages.
+#Default:
+# httpd_suppress_version_string off
+
+# TAG: visible_hostname
+# If you want to present a special hostname in error messages, etc,
+# define this. Otherwise, the return value of gethostname()
+# will be used. If you have multiple caches in a cluster and
+# get errors about IP-forwarding you must set them to have individual
+# names with this setting.
+#Default:
+# Automatically detect the system host name
+
+# TAG: unique_hostname
+# If you want to have multiple machines with the same
+# 'visible_hostname' you must give each machine a different
+# 'unique_hostname' so forwarding loops can be detected.
+#Default:
+# Copy the value from visible_hostname
+
+# TAG: hostname_aliases
+# A list of other DNS names your cache has.
+#Default:
+# none
+
+# TAG: umask
+# Minimum umask which should be enforced while the proxy
+# is running, in addition to the umask set at startup.
+#
+# For a traditional octal representation of umasks, start
+# your value with 0.
+#Default:
+# umask 027
+
+# OPTIONS FOR THE CACHE REGISTRATION SERVICE
+# -----------------------------------------------------------------------------
+#
+# This section contains parameters for the (optional) cache
+# announcement service. This service is provided to help
+# cache administrators locate one another in order to join or
+# create cache hierarchies.
+#
+# An 'announcement' message is sent (via UDP) to the registration
+# service by Squid. By default, the announcement message is NOT
+# SENT unless you enable it with 'announce_period' below.
+#
+# The announcement message includes your hostname, plus the
+# following information from this configuration file:
+#
+# http_port
+# icp_port
+# cache_mgr
+#
+# All current information is processed regularly and made
+# available on the Web at http://www.ircache.net/Cache/Tracker/.
+
+# TAG: announce_period
+# This is how frequently to send cache announcements.
+#
+# To enable announcing your cache, just set an announce period.
+#
+# Example:
+# announce_period 1 day
+#Default:
+# Announcement messages disabled.
+
+# TAG: announce_host
+# Set the hostname where announce registration messages will be sent.
+#
+# See also announce_port and announce_file
+#Default:
+# announce_host tracker.ircache.net
+
+# TAG: announce_file
+# The contents of this file will be included in the announce
+# registration messages.
+#Default:
+# none
+
+# TAG: announce_port
+# Set the port where announce registration messages will be sent.
+#
+# See also announce_host and announce_file
+#Default:
+# announce_port 3131
+
+# HTTPD-ACCELERATOR OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: httpd_accel_surrogate_id
+# Surrogates (http://www.esi.org/architecture_spec_1.0.html)
+# need an identification token to allow control targeting. Because
+# a farm of surrogates may all perform the same tasks, they may share
+# an identification token.
+#Default:
+# visible_hostname is used if no specific ID is set.
+
+# TAG: http_accel_surrogate_remote on|off
+# Remote surrogates (such as those in a CDN) honour the header
+# "Surrogate-Control: no-store-remote".
+#
+# Set this to on to have squid behave as a remote surrogate.
+#Default:
+# http_accel_surrogate_remote off
+
+# TAG: esi_parser libxml2|expat|custom
+# ESI markup is not strictly XML compatible. The custom ESI parser
+# will give higher performance, but cannot handle non ASCII character
+# encodings.
+#Default:
+# esi_parser custom
+
+# DELAY POOL PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: delay_pools
+# This represents the number of delay pools to be used. For example,
+# if you have one class 2 delay pool and one class 3 delays pool, you
+# have a total of 2 delay pools.
+#
+# See also delay_parameters, delay_class, delay_access for pool
+# configuration details.
+#Default:
+# delay_pools 0
+
+# TAG: delay_class
+# This defines the class of each delay pool. There must be exactly one
+# delay_class line for each delay pool. For example, to define two
+# delay pools, one of class 2 and one of class 3, the settings above
+# and here would be:
+#
+# Example:
+# delay_pools 4 # 4 delay pools
+# delay_class 1 2 # pool 1 is a class 2 pool
+# delay_class 2 3 # pool 2 is a class 3 pool
+# delay_class 3 4 # pool 3 is a class 4 pool
+# delay_class 4 5 # pool 4 is a class 5 pool
+#
+# The delay pool classes are:
+#
+# class 1 Everything is limited by a single aggregate
+# bucket.
+#
+# class 2 Everything is limited by a single aggregate
+# bucket as well as an "individual" bucket chosen
+# from bits 25 through 32 of the IPv4 address.
+#
+# class 3 Everything is limited by a single aggregate
+# bucket as well as a "network" bucket chosen
+# from bits 17 through 24 of the IP address and a
+# "individual" bucket chosen from bits 17 through
+# 32 of the IPv4 address.
+#
+# class 4 Everything in a class 3 delay pool, with an
+# additional limit on a per user basis. This
+# only takes effect if the username is established
+# in advance - by forcing authentication in your
+# http_access rules.
+#
+# class 5 Requests are grouped according their tag (see
+# external_acl's tag= reply).
+#
+#
+# Each pool also requires a delay_parameters directive to configure the pool size
+# and speed limits used whenever the pool is applied to a request. Along with
+# a set of delay_access directives to determine when it is used.
+#
+# NOTE: If an IP address is a.b.c.d
+# -> bits 25 through 32 are "d"
+# -> bits 17 through 24 are "c"
+# -> bits 17 through 32 are "c * 256 + d"
+#
+# NOTE-2: Due to the use of bitmasks in class 2,3,4 pools they only apply to
+# IPv4 traffic. Class 1 and 5 pools may be used with IPv6 traffic.
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+# See also delay_parameters and delay_access.
+#Default:
+# none
+
+# TAG: delay_access
+# This is used to determine which delay pool a request falls into.
+#
+# delay_access is sorted per pool and the matching starts with pool 1,
+# then pool 2, ..., and finally pool N. The first delay pool where the
+# request is allowed is selected for the request. If it does not allow
+# the request to any pool then the request is not delayed (default).
+#
+# For example, if you want some_big_clients in delay
+# pool 1 and lotsa_little_clients in delay pool 2:
+#
+# delay_access 1 allow some_big_clients
+# delay_access 1 deny all
+# delay_access 2 allow lotsa_little_clients
+# delay_access 2 deny all
+# delay_access 3 allow authenticated_clients
+#
+# See also delay_parameters and delay_class.
+#
+#Default:
+# Deny using the pool, unless allow rules exist in squid.conf for the pool.
+
+# TAG: delay_parameters
+# This defines the parameters for a delay pool. Each delay pool has
+# a number of "buckets" associated with it, as explained in the
+# description of delay_class.
+#
+# For a class 1 delay pool, the syntax is:
+# delay_pools pool 1
+# delay_parameters pool aggregate
+#
+# For a class 2 delay pool:
+# delay_pools pool 2
+# delay_parameters pool aggregate individual
+#
+# For a class 3 delay pool:
+# delay_pools pool 3
+# delay_parameters pool aggregate network individual
+#
+# For a class 4 delay pool:
+# delay_pools pool 4
+# delay_parameters pool aggregate network individual user
+#
+# For a class 5 delay pool:
+# delay_pools pool 5
+# delay_parameters pool tagrate
+#
+# The option variables are:
+#
+# pool a pool number - ie, a number between 1 and the
+# number specified in delay_pools as used in
+# delay_class lines.
+#
+# aggregate the speed limit parameters for the aggregate bucket
+# (class 1, 2, 3).
+#
+# individual the speed limit parameters for the individual
+# buckets (class 2, 3).
+#
+# network the speed limit parameters for the network buckets
+# (class 3).
+#
+# user the speed limit parameters for the user buckets
+# (class 4).
+#
+# tagrate the speed limit parameters for the tag buckets
+# (class 5).
+#
+# A pair of delay parameters is written restore/maximum, where restore is
+# the number of bytes (not bits - modem and network speeds are usually
+# quoted in bits) per second placed into the bucket, and maximum is the
+# maximum number of bytes which can be in the bucket at any time.
+#
+# There must be one delay_parameters line for each delay pool.
+#
+#
+# For example, if delay pool number 1 is a class 2 delay pool as in the
+# above example, and is being used to strictly limit each host to 64Kbit/sec
+# (plus overheads), with no overall limit, the line is:
+#
+# delay_parameters 1 -1/-1 8000/8000
+#
+# Note that 8 x 8000 KByte/sec -> 64Kbit/sec.
+#
+# Note that the figure -1 is used to represent "unlimited".
+#
+#
+# And, if delay pool number 2 is a class 3 delay pool as in the above
+# example, and you want to limit it to a total of 256Kbit/sec (strict limit)
+# with each 8-bit network permitted 64Kbit/sec (strict limit) and each
+# individual host permitted 4800bit/sec with a bucket maximum size of 64Kbits
+# to permit a decent web page to be downloaded at a decent speed
+# (if the network is not being limited due to overuse) but slow down
+# large downloads more significantly:
+#
+# delay_parameters 2 32000/32000 8000/8000 600/8000
+#
+# Note that 8 x 32000 KByte/sec -> 256Kbit/sec.
+# 8 x 8000 KByte/sec -> 64Kbit/sec.
+# 8 x 600 Byte/sec -> 4800bit/sec.
+#
+#
+# Finally, for a class 4 delay pool as in the example - each user will
+# be limited to 128Kbits/sec no matter how many workstations they are logged into.:
+#
+# delay_parameters 4 32000/32000 8000/8000 600/64000 16000/16000
+#
+#
+# See also delay_class and delay_access.
+#
+#Default:
+# none
+
+# TAG: delay_initial_bucket_level (percent, 0-100)
+# The initial bucket percentage is used to determine how much is put
+# in each bucket when squid starts, is reconfigured, or first notices
+# a host accessing it (in class 2 and class 3, individual hosts and
+# networks only have buckets associated with them once they have been
+# "seen" by squid).
+#Default:
+# delay_initial_bucket_level 50
+
+# CLIENT DELAY POOL PARAMETERS
+# -----------------------------------------------------------------------------
+
+# TAG: client_delay_pools
+# This option specifies the number of client delay pools used. It must
+# preceed other client_delay_* options.
+#
+# Example:
+# client_delay_pools 2
+#
+# See also client_delay_parameters and client_delay_access.
+#Default:
+# client_delay_pools 0
+
+# TAG: client_delay_initial_bucket_level (percent, 0-no_limit)
+# This option determines the initial bucket size as a percentage of
+# max_bucket_size from client_delay_parameters. Buckets are created
+# at the time of the "first" connection from the matching IP. Idle
+# buckets are periodically deleted up.
+#
+# You can specify more than 100 percent but note that such "oversized"
+# buckets are not refilled until their size goes down to max_bucket_size
+# from client_delay_parameters.
+#
+# Example:
+# client_delay_initial_bucket_level 50
+#Default:
+# client_delay_initial_bucket_level 50
+
+# TAG: client_delay_parameters
+#
+# This option configures client-side bandwidth limits using the
+# following format:
+#
+# client_delay_parameters pool speed_limit max_bucket_size
+#
+# pool is an integer ID used for client_delay_access matching.
+#
+# speed_limit is bytes added to the bucket per second.
+#
+# max_bucket_size is the maximum size of a bucket, enforced after any
+# speed_limit additions.
+#
+# Please see the delay_parameters option for more information and
+# examples.
+#
+# Example:
+# client_delay_parameters 1 1024 2048
+# client_delay_parameters 2 51200 16384
+#
+# See also client_delay_access.
+#
+#Default:
+# none
+
+# TAG: client_delay_access
+# This option determines the client-side delay pool for the
+# request:
+#
+# client_delay_access pool_ID allow|deny acl_name
+#
+# All client_delay_access options are checked in their pool ID
+# order, starting with pool 1. The first checked pool with allowed
+# request is selected for the request. If no ACL matches or there
+# are no client_delay_access options, the request bandwidth is not
+# limited.
+#
+# The ACL-selected pool is then used to find the
+# client_delay_parameters for the request. Client-side pools are
+# not used to aggregate clients. Clients are always aggregated
+# based on their source IP addresses (one bucket per source IP).
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+# Additionally, only the client TCP connection details are available.
+# ACLs testing HTTP properties will not work.
+#
+# Please see delay_access for more examples.
+#
+# Example:
+# client_delay_access 1 allow low_rate_network
+# client_delay_access 2 allow vips_network
+#
+#
+# See also client_delay_parameters and client_delay_pools.
+#Default:
+# Deny use of the pool, unless allow rules exist in squid.conf for the pool.
+
+# WCCPv1 AND WCCPv2 CONFIGURATION OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: wccp_router
+# Use this option to define your WCCP ``home'' router for
+# Squid.
+#
+# wccp_router supports a single WCCP(v1) router
+#
+# wccp2_router supports multiple WCCPv2 routers
+#
+# only one of the two may be used at the same time and defines
+# which version of WCCP to use.
+#Default:
+# WCCP disabled.
+
+# TAG: wccp2_router
+# Use this option to define your WCCP ``home'' router for
+# Squid.
+#
+# wccp_router supports a single WCCP(v1) router
+#
+# wccp2_router supports multiple WCCPv2 routers
+#
+# only one of the two may be used at the same time and defines
+# which version of WCCP to use.
+#Default:
+# WCCPv2 disabled.
+
+# TAG: wccp_version
+# This directive is only relevant if you need to set up WCCP(v1)
+# to some very old and end-of-life Cisco routers. In all other
+# setups it must be left unset or at the default setting.
+# It defines an internal version in the WCCP(v1) protocol,
+# with version 4 being the officially documented protocol.
+#
+# According to some users, Cisco IOS 11.2 and earlier only
+# support WCCP version 3. If you're using that or an earlier
+# version of IOS, you may need to change this value to 3, otherwise
+# do not specify this parameter.
+#Default:
+# wccp_version 4
+
+# TAG: wccp2_rebuild_wait
+# If this is enabled Squid will wait for the cache dir rebuild to finish
+# before sending the first wccp2 HereIAm packet
+#Default:
+# wccp2_rebuild_wait on
+
+# TAG: wccp2_forwarding_method
+# WCCP2 allows the setting of forwarding methods between the
+# router/switch and the cache. Valid values are as follows:
+#
+# gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
+# l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
+#
+# Currently (as of IOS 12.4) cisco routers only support GRE.
+# Cisco switches only support the L2 redirect assignment method.
+#Default:
+# wccp2_forwarding_method gre
+
+# TAG: wccp2_return_method
+# WCCP2 allows the setting of return methods between the
+# router/switch and the cache for packets that the cache
+# decides not to handle. Valid values are as follows:
+#
+# gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
+# l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
+#
+# Currently (as of IOS 12.4) cisco routers only support GRE.
+# Cisco switches only support the L2 redirect assignment.
+#
+# If the "ip wccp redirect exclude in" command has been
+# enabled on the cache interface, then it is still safe for
+# the proxy server to use a l2 redirect method even if this
+# option is set to GRE.
+#Default:
+# wccp2_return_method gre
+
+# TAG: wccp2_assignment_method
+# WCCP2 allows the setting of methods to assign the WCCP hash
+# Valid values are as follows:
+#
+# hash - Hash assignment
+# mask - Mask assignment
+#
+# As a general rule, cisco routers support the hash assignment method
+# and cisco switches support the mask assignment method.
+#Default:
+# wccp2_assignment_method hash
+
+# TAG: wccp2_service
+# WCCP2 allows for multiple traffic services. There are two
+# types: "standard" and "dynamic". The standard type defines
+# one service id - http (id 0). The dynamic service ids can be from
+# 51 to 255 inclusive. In order to use a dynamic service id
+# one must define the type of traffic to be redirected; this is done
+# using the wccp2_service_info option.
+#
+# The "standard" type does not require a wccp2_service_info option,
+# just specifying the service id will suffice.
+#
+# MD5 service authentication can be enabled by adding
+# "password=<password>" to the end of this service declaration.
+#
+# Examples:
+#
+# wccp2_service standard 0 # for the 'web-cache' standard service
+# wccp2_service dynamic 80 # a dynamic service type which will be
+# # fleshed out with subsequent options.
+# wccp2_service standard 0 password=foo
+#Default:
+# Use the 'web-cache' standard service.
+
+# TAG: wccp2_service_info
+# Dynamic WCCPv2 services require further information to define the
+# traffic you wish to have diverted.
+#
+# The format is:
+#
+# wccp2_service_info <id> protocol=<protocol> flags=<flag>,<flag>..
+# priority=<priority> ports=<port>,<port>..
+#
+# The relevant WCCPv2 flags:
+# + src_ip_hash, dst_ip_hash
+# + source_port_hash, dst_port_hash
+# + src_ip_alt_hash, dst_ip_alt_hash
+# + src_port_alt_hash, dst_port_alt_hash
+# + ports_source
+#
+# The port list can be one to eight entries.
+#
+# Example:
+#
+# wccp2_service_info 80 protocol=tcp flags=src_ip_hash,ports_source
+# priority=240 ports=80
+#
+# Note: the service id must have been defined by a previous
+# 'wccp2_service dynamic <id>' entry.
+#Default:
+# none
+
+# TAG: wccp2_weight
+# Each cache server gets assigned a set of the destination
+# hash proportional to their weight.
+#Default:
+# wccp2_weight 10000
+
+# TAG: wccp_address
+# Use this option if you require WCCPv2 to use a specific
+# interface address.
+#
+# The default behavior is to not bind to any specific address.
+#Default:
+# Address selected by the operating system.
+
+# TAG: wccp2_address
+# Use this option if you require WCCP to use a specific
+# interface address.
+#
+# The default behavior is to not bind to any specific address.
+#Default:
+# Address selected by the operating system.
+
+# PERSISTENT CONNECTION HANDLING
+# -----------------------------------------------------------------------------
+#
+# Also see "pconn_timeout" in the TIMEOUTS section
+
+# TAG: client_persistent_connections
+# Persistent connection support for clients.
+# Squid uses persistent connections (when allowed). You can use
+# this option to disable persistent connections with clients.
+#Default:
+# client_persistent_connections on
+
+# TAG: server_persistent_connections
+# Persistent connection support for servers.
+# Squid uses persistent connections (when allowed). You can use
+# this option to disable persistent connections with servers.
+#Default:
+# server_persistent_connections on
+
+# TAG: persistent_connection_after_error
+# With this directive the use of persistent connections after
+# HTTP errors can be disabled. Useful if you have clients
+# who fail to handle errors on persistent connections proper.
+#Default:
+# persistent_connection_after_error on
+
+# TAG: detect_broken_pconn
+# Some servers have been found to incorrectly signal the use
+# of HTTP/1.0 persistent connections even on replies not
+# compatible, causing significant delays. This server problem
+# has mostly been seen on redirects.
+#
+# By enabling this directive Squid attempts to detect such
+# broken replies and automatically assume the reply is finished
+# after 10 seconds timeout.
+#Default:
+# detect_broken_pconn off
+
+# CACHE DIGEST OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: digest_generation
+# This controls whether the server will generate a Cache Digest
+# of its contents. By default, Cache Digest generation is
+# enabled if Squid is compiled with --enable-cache-digests defined.
+#Default:
+# digest_generation on
+
+# TAG: digest_bits_per_entry
+# This is the number of bits of the server's Cache Digest which
+# will be associated with the Digest entry for a given HTTP
+# Method and URL (public key) combination. The default is 5.
+#Default:
+# digest_bits_per_entry 5
+
+# TAG: digest_rebuild_period (seconds)
+# This is the wait time between Cache Digest rebuilds.
+#Default:
+# digest_rebuild_period 1 hour
+
+# TAG: digest_rewrite_period (seconds)
+# This is the wait time between Cache Digest writes to
+# disk.
+#Default:
+# digest_rewrite_period 1 hour
+
+# TAG: digest_swapout_chunk_size (bytes)
+# This is the number of bytes of the Cache Digest to write to
+# disk at a time. It defaults to 4096 bytes (4KB), the Squid
+# default swap page.
+#Default:
+# digest_swapout_chunk_size 4096 bytes
+
+# TAG: digest_rebuild_chunk_percentage (percent, 0-100)
+# This is the percentage of the Cache Digest to be scanned at a
+# time. By default it is set to 10% of the Cache Digest.
+#Default:
+# digest_rebuild_chunk_percentage 10
+
+# SNMP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: snmp_port
+# The port number where Squid listens for SNMP requests. To enable
+# SNMP support set this to a suitable port number. Port number
+# 3401 is often used for the Squid SNMP agent. By default it's
+# set to "0" (disabled)
+#
+# Example:
+# snmp_port 3401
+#Default:
+# SNMP disabled.
+
+# TAG: snmp_access
+# Allowing or denying access to the SNMP port.
+#
+# All access to the agent is denied by default.
+# usage:
+#
+# snmp_access allow|deny [!]aclname ...
+#
+# This clause only supports fast acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#
+#Example:
+# snmp_access allow snmppublic localhost
+# snmp_access deny all
+#Default:
+# Deny, unless rules exist in squid.conf.
+
+# TAG: snmp_incoming_address
+# Just like 'udp_incoming_address', but for the SNMP port.
+#
+# snmp_incoming_address is used for the SNMP socket receiving
+# messages from SNMP agents.
+#
+# The default snmp_incoming_address is to listen on all
+# available network interfaces.
+#Default:
+# Accept SNMP packets from all machine interfaces.
+
+# TAG: snmp_outgoing_address
+# Just like 'udp_outgoing_address', but for the SNMP port.
+#
+# snmp_outgoing_address is used for SNMP packets returned to SNMP
+# agents.
+#
+# If snmp_outgoing_address is not set it will use the same socket
+# as snmp_incoming_address. Only change this if you want to have
+# SNMP replies sent using another address than where this Squid
+# listens for SNMP queries.
+#
+# NOTE, snmp_incoming_address and snmp_outgoing_address can not have
+# the same value since they both use the same port.
+#Default:
+# Use snmp_incoming_address or an address selected by the operating system.
+
+# ICP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icp_port
+# The port number where Squid sends and receives ICP queries to
+# and from neighbor caches. The standard UDP port for ICP is 3130.
+#
+# Example:
+# icp_port 3130
+#Default:
+# ICP disabled.
+
+# TAG: htcp_port
+# The port number where Squid sends and receives HTCP queries to
+# and from neighbor caches. To turn it on you want to set it to
+# 4827.
+#
+# Example:
+# htcp_port 4827
+#Default:
+# HTCP disabled.
+
+# TAG: log_icp_queries on|off
+# If set, ICP queries are logged to access.log. You may wish
+# do disable this if your ICP load is VERY high to speed things
+# up or to simplify log analysis.
+#Default:
+# log_icp_queries on
+
+# TAG: udp_incoming_address
+# udp_incoming_address is used for UDP packets received from other
+# caches.
+#
+# The default behavior is to not bind to any specific address.
+#
+# Only change this if you want to have all UDP queries received on
+# a specific interface/address.
+#
+# NOTE: udp_incoming_address is used by the ICP, HTCP, and DNS
+# modules. Altering it will affect all of them in the same manner.
+#
+# see also; udp_outgoing_address
+#
+# NOTE, udp_incoming_address and udp_outgoing_address can not
+# have the same value since they both use the same port.
+#Default:
+# Accept packets from all machine interfaces.
+
+# TAG: udp_outgoing_address
+# udp_outgoing_address is used for UDP packets sent out to other
+# caches.
+#
+# The default behavior is to not bind to any specific address.
+#
+# Instead it will use the same socket as udp_incoming_address.
+# Only change this if you want to have UDP queries sent using another
+# address than where this Squid listens for UDP queries from other
+# caches.
+#
+# NOTE: udp_outgoing_address is used by the ICP, HTCP, and DNS
+# modules. Altering it will affect all of them in the same manner.
+#
+# see also; udp_incoming_address
+#
+# NOTE, udp_incoming_address and udp_outgoing_address can not
+# have the same value since they both use the same port.
+#Default:
+# Use udp_incoming_address or an address selected by the operating system.
+
+# TAG: icp_hit_stale on|off
+# If you want to return ICP_HIT for stale cache objects, set this
+# option to 'on'. If you have sibling relationships with caches
+# in other administrative domains, this should be 'off'. If you only
+# have sibling relationships with caches under your control,
+# it is probably okay to set this to 'on'.
+# If set to 'on', your siblings should use the option "allow-miss"
+# on their cache_peer lines for connecting to you.
+#Default:
+# icp_hit_stale off
+
+# TAG: minimum_direct_hops
+# If using the ICMP pinging stuff, do direct fetches for sites
+# which are no more than this many hops away.
+#Default:
+# minimum_direct_hops 4
+
+# TAG: minimum_direct_rtt (msec)
+# If using the ICMP pinging stuff, do direct fetches for sites
+# which are no more than this many rtt milliseconds away.
+#Default:
+# minimum_direct_rtt 400
+
+# TAG: netdb_low
+# The low water mark for the ICMP measurement database.
+#
+# Note: high watermark controlled by netdb_high directive.
+#
+# These watermarks are counts, not percents. The defaults are
+# (low) 900 and (high) 1000. When the high water mark is
+# reached, database entries will be deleted until the low
+# mark is reached.
+#Default:
+# netdb_low 900
+
+# TAG: netdb_high
+# The high water mark for the ICMP measurement database.
+#
+# Note: low watermark controlled by netdb_low directive.
+#
+# These watermarks are counts, not percents. The defaults are
+# (low) 900 and (high) 1000. When the high water mark is
+# reached, database entries will be deleted until the low
+# mark is reached.
+#Default:
+# netdb_high 1000
+
+# TAG: netdb_ping_period
+# The minimum period for measuring a site. There will be at
+# least this much delay between successive pings to the same
+# network. The default is five minutes.
+#Default:
+# netdb_ping_period 5 minutes
+
+# TAG: query_icmp on|off
+# If you want to ask your peers to include ICMP data in their ICP
+# replies, enable this option.
+#
+# If your peer has configured Squid (during compilation) with
+# '--enable-icmp' that peer will send ICMP pings to origin server
+# sites of the URLs it receives. If you enable this option the
+# ICP replies from that peer will include the ICMP data (if available).
+# Then, when choosing a parent cache, Squid will choose the parent with
+# the minimal RTT to the origin server. When this happens, the
+# hierarchy field of the access.log will be
+# "CLOSEST_PARENT_MISS". This option is off by default.
+#Default:
+# query_icmp off
+
+# TAG: test_reachability on|off
+# When this is 'on', ICP MISS replies will be ICP_MISS_NOFETCH
+# instead of ICP_MISS if the target host is NOT in the ICMP
+# database, or has a zero RTT.
+#Default:
+# test_reachability off
+
+# TAG: icp_query_timeout (msec)
+# Normally Squid will automatically determine an optimal ICP
+# query timeout value based on the round-trip-time of recent ICP
+# queries. If you want to override the value determined by
+# Squid, set this 'icp_query_timeout' to a non-zero value. This
+# value is specified in MILLISECONDS, so, to use a 2-second
+# timeout (the old default), you would write:
+#
+# icp_query_timeout 2000
+#Default:
+# Dynamic detection.
+
+# TAG: maximum_icp_query_timeout (msec)
+# Normally the ICP query timeout is determined dynamically. But
+# sometimes it can lead to very large values (say 5 seconds).
+# Use this option to put an upper limit on the dynamic timeout
+# value. Do NOT use this option to always use a fixed (instead
+# of a dynamic) timeout value. To set a fixed timeout see the
+# 'icp_query_timeout' directive.
+#Default:
+# maximum_icp_query_timeout 2000
+
+# TAG: minimum_icp_query_timeout (msec)
+# Normally the ICP query timeout is determined dynamically. But
+# sometimes it can lead to very small timeouts, even lower than
+# the normal latency variance on your link due to traffic.
+# Use this option to put an lower limit on the dynamic timeout
+# value. Do NOT use this option to always use a fixed (instead
+# of a dynamic) timeout value. To set a fixed timeout see the
+# 'icp_query_timeout' directive.
+#Default:
+# minimum_icp_query_timeout 5
+
+# TAG: background_ping_rate time-units
+# Controls how often the ICP pings are sent to siblings that
+# have background-ping set.
+#Default:
+# background_ping_rate 10 seconds
+
+# MULTICAST ICP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: mcast_groups
+# This tag specifies a list of multicast groups which your server
+# should join to receive multicasted ICP queries.
+#
+# NOTE! Be very careful what you put here! Be sure you
+# understand the difference between an ICP _query_ and an ICP
+# _reply_. This option is to be set only if you want to RECEIVE
+# multicast queries. Do NOT set this option to SEND multicast
+# ICP (use cache_peer for that). ICP replies are always sent via
+# unicast, so this option does not affect whether or not you will
+# receive replies from multicast group members.
+#
+# You must be very careful to NOT use a multicast address which
+# is already in use by another group of caches.
+#
+# If you are unsure about multicast, please read the Multicast
+# chapter in the Squid FAQ (http://www.squid-cache.org/FAQ/).
+#
+# Usage: mcast_groups 239.128.16.128 224.0.1.20
+#
+# By default, Squid doesn't listen on any multicast groups.
+#Default:
+# none
+
+# TAG: mcast_miss_addr
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# If you enable this option, every "cache miss" URL will
+# be sent out on the specified multicast address.
+#
+# Do not enable this option unless you are are absolutely
+# certain you understand what you are doing.
+#Default:
+# disabled.
+
+# TAG: mcast_miss_ttl
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# This is the time-to-live value for packets multicasted
+# when multicasting off cache miss URLs is enabled. By
+# default this is set to 'site scope', i.e. 16.
+#Default:
+# mcast_miss_ttl 16
+
+# TAG: mcast_miss_port
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# This is the port number to be used in conjunction with
+# 'mcast_miss_addr'.
+#Default:
+# mcast_miss_port 3135
+
+# TAG: mcast_miss_encode_key
+# Note: This option is only available if Squid is rebuilt with the
+# -DMULTICAST_MISS_STREAM define
+#
+# The URLs that are sent in the multicast miss stream are
+# encrypted. This is the encryption key.
+#Default:
+# mcast_miss_encode_key XXXXXXXXXXXXXXXX
+
+# TAG: mcast_icp_query_timeout (msec)
+# For multicast peers, Squid regularly sends out ICP "probes" to
+# count how many other peers are listening on the given multicast
+# address. This value specifies how long Squid should wait to
+# count all the replies. The default is 2000 msec, or 2
+# seconds.
+#Default:
+# mcast_icp_query_timeout 2000
+
+# INTERNAL ICON OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icon_directory
+# Where the icons are stored. These are normally kept in
+# /usr/share/squid3/icons
+#Default:
+# icon_directory /usr/share/squid3/icons
+
+# TAG: global_internal_static
+# This directive controls is Squid should intercept all requests for
+# /squid-internal-static/ no matter which host the URL is requesting
+# (default on setting), or if nothing special should be done for
+# such URLs (off setting). The purpose of this directive is to make
+# icons etc work better in complex cache hierarchies where it may
+# not always be possible for all corners in the cache mesh to reach
+# the server generating a directory listing.
+#Default:
+# global_internal_static on
+
+# TAG: short_icon_urls
+# If this is enabled Squid will use short URLs for icons.
+# If disabled it will revert to the old behavior of including
+# it's own name and port in the URL.
+#
+# If you run a complex cache hierarchy with a mix of Squid and
+# other proxies you may need to disable this directive.
+#Default:
+# short_icon_urls on
+
+# ERROR PAGE OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: error_directory
+# If you wish to create your own versions of the default
+# error files to customize them to suit your company copy
+# the error/template files to another directory and point
+# this tag at them.
+#
+# WARNING: This option will disable multi-language support
+# on error pages if used.
+#
+# The squid developers are interested in making squid available in
+# a wide variety of languages. If you are making translations for a
+# language that Squid does not currently provide please consider
+# contributing your translation back to the project.
+# http://wiki.squid-cache.org/Translations
+#
+# The squid developers working on translations are happy to supply drop-in
+# translated error files in exchange for any new language contributions.
+#Default:
+# Send error pages in the clients preferred language
+
+# TAG: error_default_language
+# Set the default language which squid will send error pages in
+# if no existing translation matches the clients language
+# preferences.
+#
+# If unset (default) generic English will be used.
+#
+# The squid developers are interested in making squid available in
+# a wide variety of languages. If you are interested in making
+# translations for any language see the squid wiki for details.
+# http://wiki.squid-cache.org/Translations
+#Default:
+# Generate English language pages.
+
+# TAG: error_log_languages
+# Log to cache.log what languages users are attempting to
+# auto-negotiate for translations.
+#
+# Successful negotiations are not logged. Only failures
+# have meaning to indicate that Squid may need an upgrade
+# of its error page translations.
+#Default:
+# error_log_languages on
+
+# TAG: err_page_stylesheet
+# CSS Stylesheet to pattern the display of Squid default error pages.
+#
+# For information on CSS see http://www.w3.org/Style/CSS/
+#Default:
+# err_page_stylesheet /etc/squid3/errorpage.css
+
+# TAG: err_html_text
+# HTML text to include in error messages. Make this a "mailto"
+# URL to your admin address, or maybe just a link to your
+# organizations Web page.
+#
+# To include this in your error messages, you must rewrite
+# the error template files (found in the "errors" directory).
+# Wherever you want the 'err_html_text' line to appear,
+# insert a %L tag in the error template file.
+#Default:
+# none
+
+# TAG: email_err_data on|off
+# If enabled, information about the occurred error will be
+# included in the mailto links of the ERR pages (if %W is set)
+# so that the email body contains the data.
+# Syntax is <A HREF="mailto:%w%W">%w</A>
+#Default:
+# email_err_data on
+
+# TAG: deny_info
+# Usage: deny_info err_page_name acl
+# or deny_info http://... acl
+# or deny_info TCP_RESET acl
+#
+# This can be used to return a ERR_ page for requests which
+# do not pass the 'http_access' rules. Squid remembers the last
+# acl it evaluated in http_access, and if a 'deny_info' line exists
+# for that ACL Squid returns a corresponding error page.
+#
+# The acl is typically the last acl on the http_access deny line which
+# denied access. The exceptions to this rule are:
+# - When Squid needs to request authentication credentials. It's then
+# the first authentication related acl encountered
+# - When none of the http_access lines matches. It's then the last
+# acl processed on the last http_access line.
+# - When the decision to deny access was made by an adaptation service,
+# the acl name is the corresponding eCAP or ICAP service_name.
+#
+# NP: If providing your own custom error pages with error_directory
+# you may also specify them by your custom file name:
+# Example: deny_info ERR_CUSTOM_ACCESS_DENIED bad_guys
+#
+# By defaut Squid will send "403 Forbidden". A different 4xx or 5xx
+# may be specified by prefixing the file name with the code and a colon.
+# e.g. 404:ERR_CUSTOM_ACCESS_DENIED
+#
+# Alternatively you can tell Squid to reset the TCP connection
+# by specifying TCP_RESET.
+#
+# Or you can specify an error URL or URL pattern. The browsers will
+# get redirected to the specified URL after formatting tags have
+# been replaced. Redirect will be done with 302 or 307 according to
+# HTTP/1.1 specs. A different 3xx code may be specified by prefixing
+# the URL. e.g. 303:http://example.com/
+#
+# URL FORMAT TAGS:
+# %a - username (if available. Password NOT included)
+# %B - FTP path URL
+# %e - Error number
+# %E - Error description
+# %h - Squid hostname
+# %H - Request domain name
+# %i - Client IP Address
+# %M - Request Method
+# %o - Message result from external ACL helper
+# %p - Request Port number
+# %P - Request Protocol name
+# %R - Request URL path
+# %T - Timestamp in RFC 1123 format
+# %U - Full canonical URL from client
+# (HTTPS URLs terminate with *)
+# %u - Full canonical URL from client
+# %w - Admin email from squid.conf
+# %x - Error name
+# %% - Literal percent (%) code
+#
+#Default:
+# none
+
+# OPTIONS INFLUENCING REQUEST FORWARDING
+# -----------------------------------------------------------------------------
+
+# TAG: nonhierarchical_direct
+# By default, Squid will send any non-hierarchical requests
+# (matching hierarchy_stoplist or not cacheable request type) direct
+# to origin servers.
+#
+# When this is set to "off", Squid will prefer to send these
+# requests to parents.
+#
+# Note that in most configurations, by turning this off you will only
+# add latency to these request without any improvement in global hit
+# ratio.
+#
+# This option only sets a preference. If the parent is unavailable a
+# direct connection to the origin server may still be attempted. To
+# completely prevent direct connections use never_direct.
+#Default:
+# nonhierarchical_direct on
+
+# TAG: prefer_direct
+# Normally Squid tries to use parents for most requests. If you for some
+# reason like it to first try going direct and only use a parent if
+# going direct fails set this to on.
+#
+# By combining nonhierarchical_direct off and prefer_direct on you
+# can set up Squid to use a parent as a backup path if going direct
+# fails.
+#
+# Note: If you want Squid to use parents for all requests see
+# the never_direct directive. prefer_direct only modifies how Squid
+# acts on cacheable requests.
+#Default:
+# prefer_direct off
+
+# TAG: cache_miss_revalidate on|off
+# RFC 7232 defines a conditional request mechanism to prevent
+# response objects being unnecessarily transferred over the network.
+# If that mechanism is used by the client and a cache MISS occurs
+# it can prevent new cache entries being created.
+#
+# This option determines whether Squid on cache MISS will pass the
+# client revalidation request to the server or tries to fetch new
+# content for caching. It can be useful while the cache is mostly
+# empty to more quickly have the cache populated by generating
+# non-conditional GETs.
+#
+# When set to 'on' (default), Squid will pass all client If-* headers
+# to the server. This permits server responses without a cacheable
+# payload to be delivered and on MISS no new cache entry is created.
+#
+# When set to 'off' and if the request is cacheable, Squid will
+# remove the clients If-Modified-Since and If-None-Match headers from
+# the request sent to the server. This requests a 200 status response
+# from the server to create a new cache entry with.
+#Default:
+# cache_miss_revalidate on
+
+# TAG: always_direct
+# Usage: always_direct allow|deny [!]aclname ...
+#
+# Here you can use ACL elements to specify requests which should
+# ALWAYS be forwarded by Squid to the origin servers without using
+# any peers. For example, to always directly forward requests for
+# local servers ignoring any parents or siblings you may have use
+# something like:
+#
+# acl local-servers dstdomain my.domain.net
+# always_direct allow local-servers
+#
+# To always forward FTP requests directly, use
+#
+# acl FTP proto FTP
+# always_direct allow FTP
+#
+# NOTE: There is a similar, but opposite option named
+# 'never_direct'. You need to be aware that "always_direct deny
+# foo" is NOT the same thing as "never_direct allow foo". You
+# may need to use a deny rule to exclude a more-specific case of
+# some other rule. Example:
+#
+# acl local-external dstdomain external.foo.net
+# acl local-servers dstdomain .foo.net
+# always_direct deny local-external
+# always_direct allow local-servers
+#
+# NOTE: If your goal is to make the client forward the request
+# directly to the origin server bypassing Squid then this needs
+# to be done in the client configuration. Squid configuration
+# can only tell Squid how Squid should fetch the object.
+#
+# NOTE: This directive is not related to caching. The replies
+# is cached as usual even if you use always_direct. To not cache
+# the replies see the 'cache' directive.
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Prevent any cache_peer being used for this request.
+
+# TAG: never_direct
+# Usage: never_direct allow|deny [!]aclname ...
+#
+# never_direct is the opposite of always_direct. Please read
+# the description for always_direct if you have not already.
+#
+# With 'never_direct' you can use ACL elements to specify
+# requests which should NEVER be forwarded directly to origin
+# servers. For example, to force the use of a proxy for all
+# requests, except those in your local domain use something like:
+#
+# acl local-servers dstdomain .foo.net
+# never_direct deny local-servers
+# never_direct allow all
+#
+# or if Squid is inside a firewall and there are local intranet
+# servers inside the firewall use something like:
+#
+# acl local-intranet dstdomain .foo.net
+# acl local-external dstdomain external.foo.net
+# always_direct deny local-external
+# always_direct allow local-intranet
+# never_direct allow all
+#
+# This clause supports both fast and slow acl types.
+# See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.
+#Default:
+# Allow DNS results to be used for this request.
+
+# ADVANCED NETWORKING OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: incoming_udp_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_udp_average 6
+
+# TAG: incoming_tcp_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_tcp_average 4
+
+# TAG: incoming_dns_average
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# incoming_dns_average 4
+
+# TAG: min_udp_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_udp_poll_cnt 8
+
+# TAG: min_dns_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_dns_poll_cnt 8
+
+# TAG: min_tcp_poll_cnt
+# Heavy voodoo here. I can't even believe you are reading this.
+# Are you crazy? Don't even think about adjusting these unless
+# you understand the algorithms in comm_select.c first!
+#Default:
+# min_tcp_poll_cnt 8
+
+# TAG: accept_filter
+# FreeBSD:
+#
+# The name of an accept(2) filter to install on Squid's
+# listen socket(s). This feature is perhaps specific to
+# FreeBSD and requires support in the kernel.
+#
+# The 'httpready' filter delays delivering new connections
+# to Squid until a full HTTP request has been received.
+# See the accf_http(9) man page for details.
+#
+# The 'dataready' filter delays delivering new connections
+# to Squid until there is some data to process.
+# See the accf_dataready(9) man page for details.
+#
+# Linux:
+#
+# The 'data' filter delays delivering of new connections
+# to Squid until there is some data to process by TCP_ACCEPT_DEFER.
+# You may optionally specify a number of seconds to wait by
+# 'data=N' where N is the number of seconds. Defaults to 30
+# if not specified. See the tcp(7) man page for details.
+#EXAMPLE:
+## FreeBSD
+#accept_filter httpready
+## Linux
+#accept_filter data
+#Default:
+# none
+
+# TAG: client_ip_max_connections
+# Set an absolute limit on the number of connections a single
+# client IP can use. Any more than this and Squid will begin to drop
+# new connections from the client until it closes some links.
+#
+# Note that this is a global limit. It affects all HTTP, HTCP, Gopher and FTP
+# connections from the client. For finer control use the ACL access controls.
+#
+# Requires client_db to be enabled (the default).
+#
+# WARNING: This may noticably slow down traffic received via external proxies
+# or NAT devices and cause them to rebound error messages back to their clients.
+#Default:
+# No limit.
+
+# TAG: tcp_recv_bufsize (bytes)
+# Size of receive buffer to set for TCP sockets. Probably just
+# as easy to change your kernel's default.
+# Omit from squid.conf to use the default buffer size.
+#Default:
+# Use operating system TCP defaults.
+
+# ICAP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: icap_enable on|off
+# If you want to enable the ICAP module support, set this to on.
+#Default:
+# icap_enable off
+
+# TAG: icap_connect_timeout
+# This parameter specifies how long to wait for the TCP connect to
+# the requested ICAP server to complete before giving up and either
+# terminating the HTTP transaction or bypassing the failure.
+#
+# The default for optional services is peer_connect_timeout.
+# The default for essential services is connect_timeout.
+# If this option is explicitly set, its value applies to all services.
+#Default:
+# none
+
+# TAG: icap_io_timeout time-units
+# This parameter specifies how long to wait for an I/O activity on
+# an established, active ICAP connection before giving up and
+# either terminating the HTTP transaction or bypassing the
+# failure.
+#Default:
+# Use read_timeout.
+
+# TAG: icap_service_failure_limit limit [in memory-depth time-units]
+# The limit specifies the number of failures that Squid tolerates
+# when establishing a new TCP connection with an ICAP service. If
+# the number of failures exceeds the limit, the ICAP service is
+# not used for new ICAP requests until it is time to refresh its
+# OPTIONS.
+#
+# A negative value disables the limit. Without the limit, an ICAP
+# service will not be considered down due to connectivity failures
+# between ICAP OPTIONS requests.
+#
+# Squid forgets ICAP service failures older than the specified
+# value of memory-depth. The memory fading algorithm
+# is approximate because Squid does not remember individual
+# errors but groups them instead, splitting the option
+# value into ten time slots of equal length.
+#
+# When memory-depth is 0 and by default this option has no
+# effect on service failure expiration.
+#
+# Squid always forgets failures when updating service settings
+# using an ICAP OPTIONS transaction, regardless of this option
+# setting.
+#
+# For example,
+# # suspend service usage after 10 failures in 5 seconds:
+# icap_service_failure_limit 10 in 5 seconds
+#Default:
+# icap_service_failure_limit 10
+
+# TAG: icap_service_revival_delay
+# The delay specifies the number of seconds to wait after an ICAP
+# OPTIONS request failure before requesting the options again. The
+# failed ICAP service is considered "down" until fresh OPTIONS are
+# fetched.
+#
+# The actual delay cannot be smaller than the hardcoded minimum
+# delay of 30 seconds.
+#Default:
+# icap_service_revival_delay 180
+
+# TAG: icap_preview_enable on|off
+# The ICAP Preview feature allows the ICAP server to handle the
+# HTTP message by looking only at the beginning of the message body
+# or even without receiving the body at all. In some environments,
+# previews greatly speedup ICAP processing.
+#
+# During an ICAP OPTIONS transaction, the server may tell Squid what
+# HTTP messages should be previewed and how big the preview should be.
+# Squid will not use Preview if the server did not request one.
+#
+# To disable ICAP Preview for all ICAP services, regardless of
+# individual ICAP server OPTIONS responses, set this option to "off".
+#Example:
+#icap_preview_enable off
+#Default:
+# icap_preview_enable on
+
+# TAG: icap_preview_size
+# The default size of preview data to be sent to the ICAP server.
+# This value might be overwritten on a per server basis by OPTIONS requests.
+#Default:
+# No preview sent.
+
+# TAG: icap_206_enable on|off
+# 206 (Partial Content) responses is an ICAP extension that allows the
+# ICAP agents to optionally combine adapted and original HTTP message
+# content. The decision to combine is postponed until the end of the
+# ICAP response. Squid supports Partial Content extension by default.
+#
+# Activation of the Partial Content extension is negotiated with each
+# ICAP service during OPTIONS exchange. Most ICAP servers should handle
+# negotation correctly even if they do not support the extension, but
+# some might fail. To disable Partial Content support for all ICAP
+# services and to avoid any negotiation, set this option to "off".
+#
+# Example:
+# icap_206_enable off
+#Default:
+# icap_206_enable on
+
+# TAG: icap_default_options_ttl
+# The default TTL value for ICAP OPTIONS responses that don't have
+# an Options-TTL header.
+#Default:
+# icap_default_options_ttl 60
+
+# TAG: icap_persistent_connections on|off
+# Whether or not Squid should use persistent connections to
+# an ICAP server.
+#Default:
+# icap_persistent_connections on
+
+# TAG: adaptation_send_client_ip on|off
+# If enabled, Squid shares HTTP client IP information with adaptation
+# services. For ICAP, Squid adds the X-Client-IP header to ICAP requests.
+# For eCAP, Squid sets the libecap::metaClientIp transaction option.
+#
+# See also: adaptation_uses_indirect_client
+#Default:
+# adaptation_send_client_ip off
+
+# TAG: adaptation_send_username on|off
+# This sends authenticated HTTP client username (if available) to
+# the adaptation service.
+#
+# For ICAP, the username value is encoded based on the
+# icap_client_username_encode option and is sent using the header
+# specified by the icap_client_username_header option.
+#Default:
+# adaptation_send_username off
+
+# TAG: icap_client_username_header
+# ICAP request header name to use for adaptation_send_username.
+#Default:
+# icap_client_username_header X-Client-Username
+
+# TAG: icap_client_username_encode on|off
+# Whether to base64 encode the authenticated client username.
+#Default:
+# icap_client_username_encode off
+
+# TAG: icap_service
+# Defines a single ICAP service using the following format:
+#
+# icap_service id vectoring_point uri [option ...]
+#
+# id: ID
+# an opaque identifier or name which is used to direct traffic to
+# this specific service. Must be unique among all adaptation
+# services in squid.conf.
+#
+# vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache
+# This specifies at which point of transaction processing the
+# ICAP service should be activated. *_postcache vectoring points
+# are not yet supported.
+#
+# uri: icap://servername:port/servicepath
+# ICAP server and service location.
+#
+# ICAP does not allow a single service to handle both REQMOD and RESPMOD
+# transactions. Squid does not enforce that requirement. You can specify
+# services with the same service_url and different vectoring_points. You
+# can even specify multiple identical services as long as their
+# service_names differ.
+#
+# To activate a service, use the adaptation_access directive. To group
+# services, use adaptation_service_chain and adaptation_service_set.
+#
+# Service options are separated by white space. ICAP services support
+# the following name=value options:
+#
+# bypass=on|off|1|0
+# If set to 'on' or '1', the ICAP service is treated as
+# optional. If the service cannot be reached or malfunctions,
+# Squid will try to ignore any errors and process the message as
+# if the service was not enabled. No all ICAP errors can be
+# bypassed. If set to 0, the ICAP service is treated as
+# essential and all ICAP errors will result in an error page
+# returned to the HTTP client.
+#
+# Bypass is off by default: services are treated as essential.
+#
+# routing=on|off|1|0
+# If set to 'on' or '1', the ICAP service is allowed to
+# dynamically change the current message adaptation plan by
+# returning a chain of services to be used next. The services
+# are specified using the X-Next-Services ICAP response header
+# value, formatted as a comma-separated list of service names.
+# Each named service should be configured in squid.conf. Other
+# services are ignored. An empty X-Next-Services value results
+# in an empty plan which ends the current adaptation.
+#
+# Dynamic adaptation plan may cross or cover multiple supported
+# vectoring points in their natural processing order.
+#
+# Routing is not allowed by default: the ICAP X-Next-Services
+# response header is ignored.
+#
+# ipv6=on|off
+# Only has effect on split-stack systems. The default on those systems
+# is to use IPv4-only connections. When set to 'on' this option will
+# make Squid use IPv6-only connections to contact this ICAP service.
+#
+# on-overload=block|bypass|wait|force
+# If the service Max-Connections limit has been reached, do
+# one of the following for each new ICAP transaction:
+# * block: send an HTTP error response to the client
+# * bypass: ignore the "over-connected" ICAP service
+# * wait: wait (in a FIFO queue) for an ICAP connection slot
+# * force: proceed, ignoring the Max-Connections limit
+#
+# In SMP mode with N workers, each worker assumes the service
+# connection limit is Max-Connections/N, even though not all
+# workers may use a given service.
+#
+# The default value is "bypass" if service is bypassable,
+# otherwise it is set to "wait".
+#
+#
+# max-conn=number
+# Use the given number as the Max-Connections limit, regardless
+# of the Max-Connections value given by the service, if any.
+#
+# Older icap_service format without optional named parameters is
+# deprecated but supported for backward compatibility.
+#
+#Example:
+#icap_service svcBlocker reqmod_precache icap://icap1.mydomain.net:1344/reqmod bypass=0
+#icap_service svcLogger reqmod_precache icap://icap2.mydomain.net:1344/respmod routing=on
+#Default:
+# none
+
+# TAG: icap_class
+# This deprecated option was documented to define an ICAP service
+# chain, even though it actually defined a set of similar, redundant
+# services, and the chains were not supported.
+#
+# To define a set of redundant services, please use the
+# adaptation_service_set directive. For service chains, use
+# adaptation_service_chain.
+#Default:
+# none
+
+# TAG: icap_access
+# This option is deprecated. Please use adaptation_access, which
+# has the same ICAP functionality, but comes with better
+# documentation, and eCAP support.
+#Default:
+# none
+
+# eCAP OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: ecap_enable on|off
+# Controls whether eCAP support is enabled.
+#Default:
+# ecap_enable off
+
+# TAG: ecap_service
+# Defines a single eCAP service
+#
+# ecap_service id vectoring_point uri [option ...]
+#
+# id: ID
+# an opaque identifier or name which is used to direct traffic to
+# this specific service. Must be unique among all adaptation
+# services in squid.conf.
+#
+# vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache
+# This specifies at which point of transaction processing the
+# eCAP service should be activated. *_postcache vectoring points
+# are not yet supported.
+#
+# uri: ecap://vendor/service_name?custom&cgi=style¶meters=optional
+# Squid uses the eCAP service URI to match this configuration
+# line with one of the dynamically loaded services. Each loaded
+# eCAP service must have a unique URI. Obtain the right URI from
+# the service provider.
+#
+# To activate a service, use the adaptation_access directive. To group
+# services, use adaptation_service_chain and adaptation_service_set.
+#
+# Service options are separated by white space. eCAP services support
+# the following name=value options:
+#
+# bypass=on|off|1|0
+# If set to 'on' or '1', the eCAP service is treated as optional.
+# If the service cannot be reached or malfunctions, Squid will try
+# to ignore any errors and process the message as if the service
+# was not enabled. No all eCAP errors can be bypassed.
+# If set to 'off' or '0', the eCAP service is treated as essential
+# and all eCAP errors will result in an error page returned to the
+# HTTP client.
+#
+# Bypass is off by default: services are treated as essential.
+#
+# routing=on|off|1|0
+# If set to 'on' or '1', the eCAP service is allowed to
+# dynamically change the current message adaptation plan by
+# returning a chain of services to be used next.
+#
+# Dynamic adaptation plan may cross or cover multiple supported
+# vectoring points in their natural processing order.
+#
+# Routing is not allowed by default.
+#
+# Older ecap_service format without optional named parameters is
+# deprecated but supported for backward compatibility.
+#
+#
+#Example:
+#ecap_service s1 reqmod_precache ecap://filters.R.us/leakDetector?on_error=block bypass=off
+#ecap_service s2 respmod_precache ecap://filters.R.us/virusFilter config=/etc/vf.cfg bypass=on
+#Default:
+# none
+
+# TAG: loadable_modules
+# Instructs Squid to load the specified dynamic module(s) or activate
+# preloaded module(s).
+#Example:
+#loadable_modules /usr/lib/MinimalAdapter.so
+#Default:
+# none
+
+# MESSAGE ADAPTATION OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: adaptation_service_set
+#
+# Configures an ordered set of similar, redundant services. This is
+# useful when hot standby or backup adaptation servers are available.
+#
+# adaptation_service_set set_name service_name1 service_name2 ...
+#
+# The named services are used in the set declaration order. The first
+# applicable adaptation service from the set is used first. The next
+# applicable service is tried if and only if the transaction with the
+# previous service fails and the message waiting to be adapted is still
+# intact.
+#
+# When adaptation starts, broken services are ignored as if they were
+# not a part of the set. A broken service is a down optional service.
+#
+# The services in a set must be attached to the same vectoring point
+# (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD).
+#
+# If all services in a set are optional then adaptation failures are
+# bypassable. If all services in the set are essential, then a
+# transaction failure with one service may still be retried using
+# another service from the set, but when all services fail, the master
+# transaction fails as well.
+#
+# A set may contain a mix of optional and essential services, but that
+# is likely to lead to surprising results because broken services become
+# ignored (see above), making previously bypassable failures fatal.
+# Technically, it is the bypassability of the last failed service that
+# matters.
+#
+# See also: adaptation_access adaptation_service_chain
+#
+#Example:
+#adaptation_service_set svcBlocker urlFilterPrimary urlFilterBackup
+#adaptation service_set svcLogger loggerLocal loggerRemote
+#Default:
+# none
+
+# TAG: adaptation_service_chain
+#
+# Configures a list of complementary services that will be applied
+# one-by-one, forming an adaptation chain or pipeline. This is useful
+# when Squid must perform different adaptations on the same message.
+#
+# adaptation_service_chain chain_name service_name1 svc_name2 ...
+#
+# The named services are used in the chain declaration order. The first
+# applicable adaptation service from the chain is used first. The next
+# applicable service is applied to the successful adaptation results of
+# the previous service in the chain.
+#
+# When adaptation starts, broken services are ignored as if they were
+# not a part of the chain. A broken service is a down optional service.
+#
+# Request satisfaction terminates the adaptation chain because Squid
+# does not currently allow declaration of RESPMOD services at the
+# "reqmod_precache" vectoring point (see icap_service or ecap_service).
+#
+# The services in a chain must be attached to the same vectoring point
+# (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD).
+#
+# A chain may contain a mix of optional and essential services. If an
+# essential adaptation fails (or the failure cannot be bypassed for
+# other reasons), the master transaction fails. Otherwise, the failure
+# is bypassed as if the failed adaptation service was not in the chain.
+#
+# See also: adaptation_access adaptation_service_set
+#
+#Example:
+#adaptation_service_chain svcRequest requestLogger urlFilter leakDetector
+#Default:
+# none
+
+# TAG: adaptation_access
+# Sends an HTTP transaction to an ICAP or eCAP adaptation service.
+#
+# adaptation_access service_name allow|deny [!]aclname...
+# adaptation_access set_name allow|deny [!]aclname...
+#
+# At each supported vectoring point, the adaptation_access
+# statements are processed in the order they appear in this
+# configuration file. Statements pointing to the following services
+# are ignored (i.e., skipped without checking their ACL):
+#
+# - services serving different vectoring points
+# - "broken-but-bypassable" services
+# - "up" services configured to ignore such transactions
+# (e.g., based on the ICAP Transfer-Ignore header).
+#
+# When a set_name is used, all services in the set are checked
+# using the same rules, to find the first applicable one. See
+# adaptation_service_set for details.
+#
+# If an access list is checked and there is a match, the
+# processing stops: For an "allow" rule, the corresponding
+# adaptation service is used for the transaction. For a "deny"
+# rule, no adaptation service is activated.
+#
+# It is currently not possible to apply more than one adaptation
+# service at the same vectoring point to the same HTTP transaction.
+#
+# See also: icap_service and ecap_service
+#
+#Example:
+#adaptation_access service_1 allow all
+#Default:
+# Allow, unless rules exist in squid.conf.
+
+# TAG: adaptation_service_iteration_limit
+# Limits the number of iterations allowed when applying adaptation
+# services to a message. If your longest adaptation set or chain
+# may have more than 16 services, increase the limit beyond its
+# default value of 16. If detecting infinite iteration loops sooner
+# is critical, make the iteration limit match the actual number
+# of services in your longest adaptation set or chain.
+#
+# Infinite adaptation loops are most likely with routing services.
+#
+# See also: icap_service routing=1
+#Default:
+# adaptation_service_iteration_limit 16
+
+# TAG: adaptation_masterx_shared_names
+# For each master transaction (i.e., the HTTP request and response
+# sequence, including all related ICAP and eCAP exchanges), Squid
+# maintains a table of metadata. The table entries are (name, value)
+# pairs shared among eCAP and ICAP exchanges. The table is destroyed
+# with the master transaction.
+#
+# This option specifies the table entry names that Squid must accept
+# from and forward to the adaptation transactions.
+#
+# An ICAP REQMOD or RESPMOD transaction may set an entry in the
+# shared table by returning an ICAP header field with a name
+# specified in adaptation_masterx_shared_names.
+#
+# An eCAP REQMOD or RESPMOD transaction may set an entry in the
+# shared table by implementing the libecap::visitEachOption() API
+# to provide an option with a name specified in
+# adaptation_masterx_shared_names.
+#
+# Squid will store and forward the set entry to subsequent adaptation
+# transactions within the same master transaction scope.
+#
+# Only one shared entry name is supported at this time.
+#
+#Example:
+## share authentication information among ICAP services
+#adaptation_masterx_shared_names X-Subscriber-ID
+#Default:
+# none
+
+# TAG: adaptation_meta
+# This option allows Squid administrator to add custom ICAP request
+# headers or eCAP options to Squid ICAP requests or eCAP transactions.
+# Use it to pass custom authentication tokens and other
+# transaction-state related meta information to an ICAP/eCAP service.
+#
+# The addition of a meta header is ACL-driven:
+# adaptation_meta name value [!]aclname ...
+#
+# Processing for a given header name stops after the first ACL list match.
+# Thus, it is impossible to add two headers with the same name. If no ACL
+# lists match for a given header name, no such header is added. For
+# example:
+#
+# # do not debug transactions except for those that need debugging
+# adaptation_meta X-Debug 1 needs_debugging
+#
+# # log all transactions except for those that must remain secret
+# adaptation_meta X-Log 1 !keep_secret
+#
+# # mark transactions from users in the "G 1" group
+# adaptation_meta X-Authenticated-Groups "G 1" authed_as_G1
+#
+# The "value" parameter may be a regular squid.conf token or a "double
+# quoted string". Within the quoted string, use backslash (\) to escape
+# any character, which is currently only useful for escaping backslashes
+# and double quotes. For example,
+# "this string has one backslash (\\) and two \"quotes\""
+#
+# Used adaptation_meta header values may be logged via %note
+# logformat code. If multiple adaptation_meta headers with the same name
+# are used during master transaction lifetime, the header values are
+# logged in the order they were used and duplicate values are ignored
+# (only the first repeated value will be logged).
+#Default:
+# none
+
+# TAG: icap_retry
+# This ACL determines which retriable ICAP transactions are
+# retried. Transactions that received a complete ICAP response
+# and did not have to consume or produce HTTP bodies to receive
+# that response are usually retriable.
+#
+# icap_retry allow|deny [!]aclname ...
+#
+# Squid automatically retries some ICAP I/O timeouts and errors
+# due to persistent connection race conditions.
+#
+# See also: icap_retry_limit
+#Default:
+# icap_retry deny all
+
+# TAG: icap_retry_limit
+# Limits the number of retries allowed.
+#
+# Communication errors due to persistent connection race
+# conditions are unavoidable, automatically retried, and do not
+# count against this limit.
+#
+# See also: icap_retry
+#Default:
+# No retries are allowed.
+
+# DNS OPTIONS
+# -----------------------------------------------------------------------------
+
+# TAG: check_hostnames
+# For security and stability reasons Squid can check
+# hostnames for Internet standard RFC compliance. If you want
+# Squid to perform these checks turn this directive on.
+#Default:
+# check_hostnames off
+
+# TAG: allow_underscore
+# Underscore characters is not strictly allowed in Internet hostnames
+# but nevertheless used by many sites. Set this to off if you want
+# Squid to be strict about the standard.
+# This check is performed only when check_hostnames is set to on.
+#Default:
+# allow_underscore on
+
+# TAG: cache_dns_program
+# Note: This option is only available if Squid is rebuilt with the
+# --disable-internal-dns
+#
+# Specify the location of the executable for dnslookup process.
+#Default:
+# cache_dns_program /usr/lib/squid3/dnsserver
+
+# TAG: dns_children
+# Note: This option is only available if Squid is rebuilt with the
+# --disable-internal-dns
+#
+# The maximum number of processes spawn to service DNS name lookups.
+# If you limit it too few Squid will have to wait for them to process
+# a backlog of requests, slowing it down. If you allow too many they
+# will use RAM and other system resources noticably.
+# The maximum this may be safely set to is 32.
+#
+# The startup= and idle= options allow some measure of skew in your
+# tuning.
+#
+# startup=
+#
+# Sets a minimum of how many processes are to be spawned when Squid
+# starts or reconfigures. When set to zero the first request will
+# cause spawning of the first child process to handle it.
+#
+# Starting too few will cause an initial slowdown in traffic as Squid
+# attempts to simultaneously spawn enough processes to cope.
+#
+# idle=
+#
+# Sets a minimum of how many processes Squid is to try and keep available
+# at all times. When traffic begins to rise above what the existing
+# processes can handle this many more will be spawned up to the maximum
+# configured. A minimum setting of 1 is required.
+#Default:
+# dns_children 32 startup=1 idle=1
+
+# TAG: dns_retransmit_interval
+# Initial retransmit interval for DNS queries. The interval is
+# doubled each time all configured DNS servers have been tried.
+#Default:
+# dns_retransmit_interval 5 seconds
+
+# TAG: dns_timeout
+# DNS Query timeout. If no response is received to a DNS query
+# within this time all DNS servers for the queried domain
+# are assumed to be unavailable.
+#Default:
+# dns_timeout 30 seconds
+
+# TAG: dns_packet_max
+# Maximum number of bytes packet size to advertise via EDNS.
+# Set to "none" to disable EDNS large packet support.
+#
+# For legacy reasons DNS UDP replies will default to 512 bytes which
+# is too small for many responses. EDNS provides a means for Squid to
+# negotiate receiving larger responses back immediately without having
+# to failover with repeat requests. Responses larger than this limit
+# will retain the old behaviour of failover to TCP DNS.
+#
+# Squid has no real fixed limit internally, but allowing packet sizes
+# over 1500 bytes requires network jumbogram support and is usually not
+# necessary.
+#
+# WARNING: The RFC also indicates that some older resolvers will reply
+# with failure of the whole request if the extension is added. Some
+# resolvers have already been identified which will reply with mangled
+# EDNS response on occasion. Usually in response to many-KB jumbogram
+# sizes being advertised by Squid.
+# Squid will currently treat these both as an unable-to-resolve domain
+# even if it would be resolvable without EDNS.
+#Default:
+# EDNS disabled
+
+# TAG: dns_defnames on|off
+# Normally the RES_DEFNAMES resolver option is disabled
+# (see res_init(3)). This prevents caches in a hierarchy
+# from interpreting single-component hostnames locally. To allow
+# Squid to handle single-component names, enable this option.
+#Default:
+# Search for single-label domain names is disabled.
+
+# TAG: dns_multicast_local on|off
+# When set to on, Squid sends multicast DNS lookups on the local
+# network for domains ending in .local and .arpa.
+# This enables local servers and devices to be contacted in an
+# ad-hoc or zero-configuration network environment.
+#Default:
+# Search for .local and .arpa names is disabled.
+
+# TAG: dns_nameservers
+# Use this if you want to specify a list of DNS name servers
+# (IP addresses) to use instead of those given in your
+# /etc/resolv.conf file.
+#
+# On Windows platforms, if no value is specified here or in
+# the /etc/resolv.conf file, the list of DNS name servers are
+# taken from the Windows registry, both static and dynamic DHCP
+# configurations are supported.
+#
+# Example: dns_nameservers 10.0.0.1 192.172.0.4
+#Default:
+# Use operating system definitions
+
+# TAG: hosts_file
+# Location of the host-local IP name-address associations
+# database. Most Operating Systems have such a file on different
+# default locations:
+# - Un*X & Linux: /etc/hosts
+# - Windows NT/2000: %SystemRoot%\system32\drivers\etc\hosts
+# (%SystemRoot% value install default is c:\winnt)
+# - Windows XP/2003: %SystemRoot%\system32\drivers\etc\hosts
+# (%SystemRoot% value install default is c:\windows)
+# - Windows 9x/Me: %windir%\hosts
+# (%windir% value is usually c:\windows)
+# - Cygwin: /etc/hosts
+#
+# The file contains newline-separated definitions, in the
+# form ip_address_in_dotted_form name [name ...] names are
+# whitespace-separated. Lines beginning with an hash (#)
+# character are comments.
+#
+# The file is checked at startup and upon configuration.
+# If set to 'none', it won't be checked.
+# If append_domain is used, that domain will be added to
+# domain-local (i.e. not containing any dot character) host
+# definitions.
+#Default:
+# hosts_file /etc/hosts
+
+# TAG: append_domain
+# Appends local domain name to hostnames without any dots in
+# them. append_domain must begin with a period.
+#
+# Be warned there are now Internet names with no dots in
+# them using only top-domain names, so setting this may
+# cause some Internet sites to become unavailable.
+#
+#Example:
+# append_domain .yourdomain.com
+#Default:
+# Use operating system definitions
+
+# TAG: ignore_unknown_nameservers
+# By default Squid checks that DNS responses are received
+# from the same IP addresses they are sent to. If they
+# don't match, Squid ignores the response and writes a warning
+# message to cache.log. You can allow responses from unknown
+# nameservers by setting this option to 'off'.
+#Default:
+# ignore_unknown_nameservers on
+
+# TAG: dns_v4_first
+# With the IPv6 Internet being as fast or faster than IPv4 Internet
+# for most networks Squid prefers to contact websites over IPv6.
+#
+# This option reverses the order of preference to make Squid contact
+# dual-stack websites over IPv4 first. Squid will still perform both
+# IPv6 and IPv4 DNS lookups before connecting.
+#
+# WARNING:
+# This option will restrict the situations under which IPv6
+# connectivity is used (and tested), potentially hiding network
+# problems which would otherwise be detected and warned about.
+#Default:
+# dns_v4_first off
+
+# TAG: ipcache_size (number of entries)
+# Maximum number of DNS IP cache entries.
+#Default:
+# ipcache_size 1024
+
+# TAG: ipcache_low (percent)
+#Default:
+# ipcache_low 90
+
+# TAG: ipcache_high (percent)
+# The size, low-, and high-water marks for the IP cache.
+#Default:
+# ipcache_high 95
+
+# TAG: fqdncache_size (number of entries)
+# Maximum number of FQDN cache entries.
+#Default:
+# fqdncache_size 1024
+
+# MISCELLANEOUS
+# -----------------------------------------------------------------------------
+
+# TAG: configuration_includes_quoted_values on|off
+# Previous Squid versions have defined "quoted/string" as syntax for
+# ACL to signifiy the value is an included file containing values and
+# has treated the " characters in other places of the configuration file
+# as part of the parameter value it was used for.
+#
+# For compatibility with existing installations that behaviour
+# remains the default.
+#
+# If this directive is set to 'on', Squid will start parsing each
+# "quoted string" as a single configuration directive parameter. The
+# quotes are stripped before the parameter value is interpreted or use.
+#
+# That will continue for all lines until this directive is set to 'off',
+# where Squid will return to the default configuration parsing.
+#
+# For example;
+#
+# configuration_includes_quoted_values on
+# acl group external groupCheck Administrators "Internet Users" Guest
+# configuration_includes_quoted_values off
+#
+#Default:
+# configuration_includes_quoted_values off
+
+# TAG: memory_pools on|off
+# If set, Squid will keep pools of allocated (but unused) memory
+# available for future use. If memory is a premium on your
+# system and you believe your malloc library outperforms Squid
+# routines, disable this.
+#Default:
+# memory_pools on
+
+# TAG: memory_pools_limit (bytes)
+# Used only with memory_pools on:
+# memory_pools_limit 50 MB
+#
+# If set to a non-zero value, Squid will keep at most the specified
+# limit of allocated (but unused) memory in memory pools. All free()
+# requests that exceed this limit will be handled by your malloc
+# library. Squid does not pre-allocate any memory, just safe-keeps
+# objects that otherwise would be free()d. Thus, it is safe to set
+# memory_pools_limit to a reasonably high value even if your
+# configuration will use less memory.
+#
+# If set to none, Squid will keep all memory it can. That is, there
+# will be no limit on the total amount of memory used for safe-keeping.
+#
+# To disable memory allocation optimization, do not set
+# memory_pools_limit to 0 or none. Set memory_pools to "off" instead.
+#
+# An overhead for maintaining memory pools is not taken into account
+# when the limit is checked. This overhead is close to four bytes per
+# object kept. However, pools may actually _save_ memory because of
+# reduced memory thrashing in your malloc library.
+#Default:
+# memory_pools_limit 5 MB
+
+# TAG: forwarded_for on|off|transparent|truncate|delete
+# If set to "on", Squid will append your client's IP address
+# in the HTTP requests it forwards. By default it looks like:
+#
+# X-Forwarded-For: 192.1.2.3
+#
+# If set to "off", it will appear as
+#
+# X-Forwarded-For: unknown
+#
+# If set to "transparent", Squid will not alter the
+# X-Forwarded-For header in any way.
+#
+# If set to "delete", Squid will delete the entire
+# X-Forwarded-For header.
+#
+# If set to "truncate", Squid will remove all existing
+# X-Forwarded-For entries, and place the client IP as the sole entry.
+#Default:
+# forwarded_for on
+
+# TAG: cachemgr_passwd
+# Specify passwords for cachemgr operations.
+#
+# Usage: cachemgr_passwd password action action ...
+#
+# Some valid actions are (see cache manager menu for a full list):
+# 5min
+# 60min
+# asndb
+# authenticator
+# cbdata
+# client_list
+# comm_incoming
+# config *
+# counters
+# delay
+# digest_stats
+# dns
+# events
+# filedescriptors
+# fqdncache
+# histograms
+# http_headers
+# info
+# io
+# ipcache
+# mem
+# menu
+# netdb
+# non_peers
+# objects
+# offline_toggle *
+# pconn
+# peer_select
+# reconfigure *
+# redirector
+# refresh
+# server_list
+# shutdown *
+# store_digest
+# storedir
+# utilization
+# via_headers
+# vm_objects
+#
+# * Indicates actions which will not be performed without a
+# valid password, others can be performed if not listed here.
+#
+# To disable an action, set the password to "disable".
+# To allow performing an action without a password, set the
+# password to "none".
+#
+# Use the keyword "all" to set the same password for all actions.
+#
+#Example:
+# cachemgr_passwd secret shutdown
+# cachemgr_passwd lesssssssecret info stats/objects
+# cachemgr_passwd disable all
+#Default:
+# No password. Actions which require password are denied.
+
+# TAG: client_db on|off
+# If you want to disable collecting per-client statistics,
+# turn off client_db here.
+#Default:
+# client_db on
+
+# TAG: refresh_all_ims on|off
+# When you enable this option, squid will always check
+# the origin server for an update when a client sends an
+# If-Modified-Since request. Many browsers use IMS
+# requests when the user requests a reload, and this
+# ensures those clients receive the latest version.
+#
+# By default (off), squid may return a Not Modified response
+# based on the age of the cached version.
+#Default:
+# refresh_all_ims off
+
+# TAG: reload_into_ims on|off
+# When you enable this option, client no-cache or ``reload''
+# requests will be changed to If-Modified-Since requests.
+# Doing this VIOLATES the HTTP standard. Enabling this
+# feature could make you liable for problems which it
+# causes.
+#
+# see also refresh_pattern for a more selective approach.
+#Default:
+# reload_into_ims off
+
+# TAG: connect_retries
+# This sets the maximum number of connection attempts made for each
+# TCP connection. The connect_retries attempts must all still
+# complete within the connection timeout period.
+#
+# The default is not to re-try if the first connection attempt fails.
+# The (not recommended) maximum is 10 tries.
+#
+# A warning message will be generated if it is set to a too-high
+# value and the configured value will be over-ridden.
+#
+# Note: These re-tries are in addition to forward_max_tries
+# which limit how many different addresses may be tried to find
+# a useful server.
+#Default:
+# Do not retry failed connections.
+
+# TAG: retry_on_error
+# If set to ON Squid will automatically retry requests when
+# receiving an error response with status 403 (Forbidden),
+# 500 (Internal Error), 501 or 503 (Service not available).
+# Status 502 and 504 (Gateway errors) are always retried.
+#
+# This is mainly useful if you are in a complex cache hierarchy to
+# work around access control errors.
+#
+# NOTE: This retry will attempt to find another working destination.
+# Which is different from the server which just failed.
+#Default:
+# retry_on_error off
+
+# TAG: as_whois_server
+# WHOIS server to query for AS numbers. NOTE: AS numbers are
+# queried only when Squid starts up, not for every request.
+#Default:
+# as_whois_server whois.ra.net
+
+# TAG: offline_mode
+# Enable this option and Squid will never try to validate cached
+# objects.
+#Default:
+# offline_mode off
+
+# TAG: uri_whitespace
+# What to do with requests that have whitespace characters in the
+# URI. Options:
+#
+# strip: The whitespace characters are stripped out of the URL.
+# This is the behavior recommended by RFC2396 and RFC3986
+# for tolerant handling of generic URI.
+# NOTE: This is one difference between generic URI and HTTP URLs.
+#
+# deny: The request is denied. The user receives an "Invalid
+# Request" message.
+# This is the behaviour recommended by RFC2616 for safe
+# handling of HTTP request URL.
+#
+# allow: The request is allowed and the URI is not changed. The
+# whitespace characters remain in the URI. Note the
+# whitespace is passed to redirector processes if they
+# are in use.
+# Note this may be considered a violation of RFC2616
+# request parsing where whitespace is prohibited in the
+# URL field.
+#
+# encode: The request is allowed and the whitespace characters are
+# encoded according to RFC1738.
+#
+# chop: The request is allowed and the URI is chopped at the
+# first whitespace.
+#
+#
+# NOTE the current Squid implementation of encode and chop violates
+# RFC2616 by not using a 301 redirect after altering the URL.
+#Default:
+# uri_whitespace strip
+
+# TAG: chroot
+# Specifies a directory where Squid should do a chroot() while
+# initializing. This also causes Squid to fully drop root
+# privileges after initializing. This means, for example, if you
+# use a HTTP port less than 1024 and try to reconfigure, you may
+# get an error saying that Squid can not open the port.
+#Default:
+# none
+
+# TAG: balance_on_multiple_ip
+# Modern IP resolvers in squid sort lookup results by preferred access.
+# By default squid will use these IP in order and only rotates to
+# the next listed when the most preffered fails.
+#
+# Some load balancing servers based on round robin DNS have been
+# found not to preserve user session state across requests
+# to different IP addresses.
+#
+# Enabling this directive Squid rotates IP's per request.
+#Default:
+# balance_on_multiple_ip off
+
+# TAG: pipeline_prefetch
+# HTTP clients may send a pipeline of 1+N requests to Squid using a
+# single connection, without waiting for Squid to respond to the first
+# of those requests. This option limits the number of concurrent
+# requests Squid will try to handle in parallel. If set to N, Squid
+# will try to receive and process up to 1+N requests on the same
+# connection concurrently.
+#
+# Defaults to 0 (off) for bandwidth management and access logging
+# reasons.
+#
+# NOTE: pipelining requires persistent connections to clients.
+#
+# WARNING: pipelining breaks NTLM and Negotiate/Kerberos authentication.
+#Default:
+# Do not pre-parse pipelined requests.
+
+# TAG: high_response_time_warning (msec)
+# If the one-minute median response time exceeds this value,
+# Squid prints a WARNING with debug level 0 to get the
+# administrators attention. The value is in milliseconds.
+#Default:
+# disabled.
+
+# TAG: high_page_fault_warning
+# If the one-minute average page fault rate exceeds this
+# value, Squid prints a WARNING with debug level 0 to get
+# the administrators attention. The value is in page faults
+# per second.
+#Default:
+# disabled.
+
+# TAG: high_memory_warning
+# Note: This option is only available if Squid is rebuilt with the
+# GNU Malloc with mstats()
+#
+# If the memory usage (as determined by mallinfo) exceeds
+# this amount, Squid prints a WARNING with debug level 0 to get
+# the administrators attention.
+#Default:
+# disabled.
+
+# TAG: sleep_after_fork (microseconds)
+# When this is set to a non-zero value, the main Squid process
+# sleeps the specified number of microseconds after a fork()
+# system call. This sleep may help the situation where your
+# system reports fork() failures due to lack of (virtual)
+# memory. Note, however, if you have a lot of child
+# processes, these sleep delays will add up and your
+# Squid will not service requests for some amount of time
+# until all the child processes have been started.
+# On Windows value less then 1000 (1 milliseconds) are
+# rounded to 1000.
+#Default:
+# sleep_after_fork 0
+
+# TAG: windows_ipaddrchangemonitor on|off
+# Note: This option is only available if Squid is rebuilt with the
+# MS Windows
+#
+# On Windows Squid by default will monitor IP address changes and will
+# reconfigure itself after any detected event. This is very useful for
+# proxies connected to internet with dial-up interfaces.
+# In some cases (a Proxy server acting as VPN gateway is one) it could be
+# desiderable to disable this behaviour setting this to 'off'.
+# Note: after changing this, Squid service must be restarted.
+#Default:
+# windows_ipaddrchangemonitor on
+
+# TAG: eui_lookup
+# Whether to lookup the EUI or MAC address of a connected client.
+#Default:
+# eui_lookup on
+
+# TAG: max_filedescriptors
+# Reduce the maximum number of filedescriptors supported below
+# the usual operating system defaults.
+#
+# Remove from squid.conf to inherit the current ulimit setting.
+#
+# Note: Changing this requires a restart of Squid. Also
+# not all I/O types supports large values (eg on Windows).
+#Default:
+# Use operating system limits set by ulimit.
+
+# TAG: workers
+# Number of main Squid processes or "workers" to fork and maintain.
+# 0: "no daemon" mode, like running "squid -N ..."
+# 1: "no SMP" mode, start one main Squid process daemon (default)
+# N: start N main Squid process daemons (i.e., SMP mode)
+#
+# In SMP mode, each worker does nearly all what a single Squid daemon
+# does (e.g., listen on http_port and forward HTTP requests).
+#Default:
+# SMP support disabled.
+
+# TAG: cpu_affinity_map
+# Usage: cpu_affinity_map process_numbers=P1,P2,... cores=C1,C2,...
+#
+# Sets 1:1 mapping between Squid processes and CPU cores. For example,
+#
+# cpu_affinity_map process_numbers=1,2,3,4 cores=1,3,5,7
+#
+# affects processes 1 through 4 only and places them on the first
+# four even cores, starting with core #1.
+#
+# CPU cores are numbered starting from 1. Requires support for
+# sched_getaffinity(2) and sched_setaffinity(2) system calls.
+#
+# Multiple cpu_affinity_map options are merged.
+#
+# See also: workers
+#Default:
+# Let operating system decide.
+
diff --git a/roles/squid/handlers/main.yml b/roles/squid/handlers/main.yml
new file mode 100644
index 0000000..d309cc2
--- /dev/null
+++ b/roles/squid/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart squid
+ service: name=squid state=restarted
diff --git a/roles/squid/tasks/main.yml b/roles/squid/tasks/main.yml
new file mode 100644
index 0000000..ae557d8
--- /dev/null
+++ b/roles/squid/tasks/main.yml
@@ -0,0 +1,9 @@
+---
+
+- name: Installation squid
+ apt: name=squid state=present
+
+- name: Copie du fichier squid.conf
+ copy: src=squid.{{ansible_hostname}}.conf dest=/etc/squid/squid.conf
+ notify:
+ - restart squid
diff --git a/roles/ssh-cli/tasks/main.yml b/roles/ssh-cli/tasks/main.yml
new file mode 100644
index 0000000..ea32e53
--- /dev/null
+++ b/roles/ssh-cli/tasks/main.yml
@@ -0,0 +1,10 @@
+---
+
+- name: Creation de .ssh
+ file: path=/root/.ssh mode=0700 state=directory
+
+- name: Copie cle public s-adm
+ shell: curl 192.168.99.99/id_rsa.pub > ~/.ssh/authorized_keys
+
+#- name: Copie cle public s-spec
+# shell: curl 192.168.99.10/id_rsa.pub >> ~/.ssh/authorized_keys
diff --git a/roles/sshk/tasks/main.yml b/roles/sshk/tasks/main.yml
new file mode 100644
index 0000000..8c89382
--- /dev/null
+++ b/roles/sshk/tasks/main.yml
@@ -0,0 +1,10 @@
+---
+
+
+- name: creation user admu
+ user: name=admu comment="admu" shell=/bin/bash
+
+- name: Copie cle ssh
+ authorized_key: user=root key="{{lookup('file','/home/admu/.ssh/id_rsa_pub') }}"
+
+
diff --git a/roles/syslog-cli/handlers/main.yml b/roles/syslog-cli/handlers/main.yml
new file mode 100644
index 0000000..4e86192
--- /dev/null
+++ b/roles/syslog-cli/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: Redemarrage syslog
+ service: name=rsyslog state=restarted
diff --git a/roles/syslog-cli/tasks/main.yml b/roles/syslog-cli/tasks/main.yml
new file mode 100644
index 0000000..8100030
--- /dev/null
+++ b/roles/syslog-cli/tasks/main.yml
@@ -0,0 +1,6 @@
+---
+ - name: configuration du serveur de logs.
+ lineinfile: dest=/etc/rsyslog.conf regexp='^' line='*.* @syslog.gsb.adm' state=present
+ notify:
+ - Redemarrage syslog
+
diff --git a/roles/syslog/handlers/main.yml b/roles/syslog/handlers/main.yml
new file mode 100644
index 0000000..4e86192
--- /dev/null
+++ b/roles/syslog/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: Redemarrage syslog
+ service: name=rsyslog state=restarted
diff --git a/roles/syslog/tasks/main.yml b/roles/syslog/tasks/main.yml
new file mode 100644
index 0000000..2e9c30f
--- /dev/null
+++ b/roles/syslog/tasks/main.yml
@@ -0,0 +1,10 @@
+---
+- name: configuration port UDP
+ replace: dest=/etc/rsyslog.conf regexp='^#module\(load="imudp"\)' replace='module(load="imudp")' backup=yes
+ notify:
+ - Redemarrage syslog
+
+- name: configuration port 514
+ replace: dest=/etc/rsyslog.conf regexp='^#input\(type="imudp" port="514"\)' replace='input(type="imudp" port="514")' backup=yes
+ notify:
+ - Redemarrage syslog
diff --git a/roles/user-yb/tasks/main.yml b/roles/user-yb/tasks/main.yml
new file mode 100644
index 0000000..89118cf
--- /dev/null
+++ b/roles/user-yb/tasks/main.yml
@@ -0,0 +1,47 @@
+---
+ - name: Installation des paquets
+ apt: name={{item}} state=present force=yes
+ with_items:
+ - dmidecode
+ - hwdata
+ - ucf
+ - hdparm
+ - perl
+ - libuniversal-require-perl
+ - libwww-perl
+ - libparse-edid-perl
+ - libproc-daemon-perl
+ - libfile-which-perl
+ - libhttp-daemon-perl
+ - libxml-treepp-perl
+ - libyaml-perl
+ - libnet-cups-perl
+ - libnet-ip-perl
+ - libdigest-sha-perl
+ - libsocket-getaddrinfo-perl
+ - libtext-template-perl
+
+ - name: Creation du repertoire fi
+ file: path=/root/fi state=directory owner=www-data group=www-data
+
+ - name: Installation de fusioninventory
+ get_url:
+ url: http://debian.fusioninventory.org/downloads/fusioninventory-agent_2.5-3_all.deb
+ dest: /root/fi
+ remote_src: yes
+ owner: www-data
+ group: www-data
+
+ - name: Installation du paquet .deb
+ apt:
+ deb: /root/fi/fusioninventory-agent_2.5-3_all.deb
+
+ - name: Configuration du fichier agent.cfg
+ replace:
+ dest: /etc/fusioninventory/agent.cfg
+ regexp: '#server = http://server.domain.com/glpi/plugins/fusioninventory/'
+ replace: 'server = http://172.16.0.9/plugins/fusioninventory/'
+ backup: yes
+
+ - debug:
+ msg: "Faire un systemectl restart fusioninventory-agent puis un reload"
diff --git a/roles/vpn-stg-l/files/ipsec.conf b/roles/vpn-stg-l/files/ipsec.conf
new file mode 100644
index 0000000..42954c2
--- /dev/null
+++ b/roles/vpn-stg-l/files/ipsec.conf
@@ -0,0 +1,22 @@
+config setup
+ charondebug="all"
+ uniqueids=yes
+ strictcrlpolicy=no
+conn %default
+conn tunnel #
+ left=192.168.0.52
+ leftsubnet=172.16.128.0/24
+ right=192.168.0.51
+ rightsubnet=192.168.0.0/16, 172.16.0.0/24
+ ike=aes256-sha2_256-modp1024!
+ esp=aes256-sha2_256!
+ keyingtries=0
+ ikelifetime=1h
+ lifetime=8h
+ dpddelay=30
+ dpdtimeout=120
+ dpdaction=restart
+ authby=secret
+ auto=start
+ keyexchange=ikev2
+ type=tunnel
diff --git a/roles/vpn-stg-l/files/ipsec.secrets b/roles/vpn-stg-l/files/ipsec.secrets
new file mode 100644
index 0000000..65d30ce
--- /dev/null
+++ b/roles/vpn-stg-l/files/ipsec.secrets
@@ -0,0 +1,8 @@
+# This file holds shared secrets or RSA private keys for authentication.
+
+# RSA private key for this host, authenticating it to any other host
+# which knows the public part.
+
+# this file is managed with debconf and will contain the automatically created private key
+include /var/lib/strongswan/ipsec.secrets.inc
+192.168.0.52 192.168.0.51 : PSK 'root'
\ No newline at end of file
diff --git a/roles/vpn-stg-l/files/sysctl.conf b/roles/vpn-stg-l/files/sysctl.conf
new file mode 100644
index 0000000..b138754
--- /dev/null
+++ b/roles/vpn-stg-l/files/sysctl.conf
@@ -0,0 +1,60 @@
+#
+# /etc/sysctl.conf - Configuration file for setting system variables
+# See /etc/sysctl.d/ for additonal system variables
+# See sysctl.conf (5) for information.
+#
+
+#kernel.domainname = example.com
+
+# Uncomment the following to stop low-level messages on console
+#kernel.printk = 3 4 1 3
+
+##############################################################3
+# Functions previously found in netbase
+#
+
+# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
+# Turn on Source Address Verification in all interfaces to
+# prevent some spoofing attacks
+#net.ipv4.conf.default.rp_filter=1
+#net.ipv4.conf.all.rp_filter=1
+
+# Uncomment the next line to enable TCP/IP SYN cookies
+# See http://lwn.net/Articles/277146/
+# Note: This may impact IPv6 TCP sessions too
+#net.ipv4.tcp_syncookies=1
+
+# Uncomment the next line to enable packet forwarding for IPv4
+net.ipv4.ip_forward=1
+
+# Uncomment the next line to enable packet forwarding for IPv6
+# Enabling this option disables Stateless Address Autoconfiguration
+# based on Router Advertisements for this host
+#net.ipv6.conf.all.forwarding=1
+
+
+###################################################################
+# Additional settings - these settings can improve the network
+# security of the host and prevent against some network attacks
+# including spoofing attacks and man in the middle attacks through
+# redirection. Some network environments, however, require that these
+# settings are disabled so review and enable them as needed.
+#
+# Do not accept ICMP redirects (prevent MITM attacks)
+#net.ipv4.conf.all.accept_redirects = 0
+#net.ipv6.conf.all.accept_redirects = 0
+# _or_
+# Accept ICMP redirects only for gateways listed in our default
+# gateway list (enabled by default)
+# net.ipv4.conf.all.secure_redirects = 1
+#
+# Do not send ICMP redirects (we are not a router)
+#net.ipv4.conf.all.send_redirects = 0
+#
+# Do not accept IP source route packets (we are not a router)
+#net.ipv4.conf.all.accept_source_route = 0
+#net.ipv6.conf.all.accept_source_route = 0
+#
+# Log Martian Packets
+#net.ipv4.conf.all.log_martians = 1
+#
diff --git a/roles/vpn-stg-l/handlers/main.yml b/roles/vpn-stg-l/handlers/main.yml
new file mode 100644
index 0000000..719832b
--- /dev/null
+++ b/roles/vpn-stg-l/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+ - name: restart ipsec
+ service: name=ipsec state=restarted
+
diff --git a/roles/vpn-stg-l/tasks/main.yml b/roles/vpn-stg-l/tasks/main.yml
new file mode 100644
index 0000000..73c001a
--- /dev/null
+++ b/roles/vpn-stg-l/tasks/main.yml
@@ -0,0 +1,21 @@
+---
+#Installation ipsec strongswan côté gauche pour le fichier de secret partagé
+ - name: install strongswan, fichier secret partagé
+ apt: name=strongswan state=present
+
+ - name: install tcpdump
+ apt: name=tcpdump state=present update_cache=yes
+
+ - name: activation du routage
+ copy: src=sysctl.conf dest=/etc/sysctl.conf
+
+ - name: Copie fichier ipsec.conf
+ copy: src=ipsec.conf dest=/etc/ipsec.conf
+ notify: restart ipsec
+
+ - name: Copie fichier ipsec.secrets
+ copy: src=ipsec.secrets dest=/etc/ipsec.secrets
+ notify: restart ipsec
+
+ - name: Message d'information
+ debug: msg="Veuillez consulter le document "r-vp.txt" dans ansible/gsb/doc"
\ No newline at end of file
diff --git a/roles/vpn-stg-r/files/ipsec.conf b/roles/vpn-stg-r/files/ipsec.conf
new file mode 100644
index 0000000..9f3e471
--- /dev/null
+++ b/roles/vpn-stg-r/files/ipsec.conf
@@ -0,0 +1,22 @@
+config setup
+ charondebug="all"
+ uniqueids=yes
+ strictcrlpolicy=no
+conn %default
+conn tunnel #
+ left=192.168.0.51
+ leftsubnet=192.168.0.0/16, 172.16.0.0/24
+ right=192.168.0.52
+ rightsubnet=172.16.128.0/24
+ ike=aes256-sha2_256-modp1024!
+ esp=aes256-sha2_256!
+ keyingtries=0
+ ikelifetime=1h
+ lifetime=8h
+ dpddelay=30
+ dpdtimeout=120
+ dpdaction=restart
+ authby=secret
+ auto=start
+ keyexchange=ikev2
+ type=tunnel
diff --git a/roles/vpn-stg-r/files/ipsec.secrets b/roles/vpn-stg-r/files/ipsec.secrets
new file mode 100644
index 0000000..9d46a82
--- /dev/null
+++ b/roles/vpn-stg-r/files/ipsec.secrets
@@ -0,0 +1,8 @@
+# This file holds shared secrets or RSA private keys for authentication.
+
+# RSA private key for this host, authenticating it to any other host
+# which knows the public part.
+
+# this file is managed with debconf and will contain the automatically created private key
+include /var/lib/strongswan/ipsec.secrets.inc
+192.168.0.51 192.168.0.52 : PSK 'root'
\ No newline at end of file
diff --git a/roles/vpn-stg-r/files/sysctl.conf b/roles/vpn-stg-r/files/sysctl.conf
new file mode 100644
index 0000000..b138754
--- /dev/null
+++ b/roles/vpn-stg-r/files/sysctl.conf
@@ -0,0 +1,60 @@
+#
+# /etc/sysctl.conf - Configuration file for setting system variables
+# See /etc/sysctl.d/ for additonal system variables
+# See sysctl.conf (5) for information.
+#
+
+#kernel.domainname = example.com
+
+# Uncomment the following to stop low-level messages on console
+#kernel.printk = 3 4 1 3
+
+##############################################################3
+# Functions previously found in netbase
+#
+
+# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
+# Turn on Source Address Verification in all interfaces to
+# prevent some spoofing attacks
+#net.ipv4.conf.default.rp_filter=1
+#net.ipv4.conf.all.rp_filter=1
+
+# Uncomment the next line to enable TCP/IP SYN cookies
+# See http://lwn.net/Articles/277146/
+# Note: This may impact IPv6 TCP sessions too
+#net.ipv4.tcp_syncookies=1
+
+# Uncomment the next line to enable packet forwarding for IPv4
+net.ipv4.ip_forward=1
+
+# Uncomment the next line to enable packet forwarding for IPv6
+# Enabling this option disables Stateless Address Autoconfiguration
+# based on Router Advertisements for this host
+#net.ipv6.conf.all.forwarding=1
+
+
+###################################################################
+# Additional settings - these settings can improve the network
+# security of the host and prevent against some network attacks
+# including spoofing attacks and man in the middle attacks through
+# redirection. Some network environments, however, require that these
+# settings are disabled so review and enable them as needed.
+#
+# Do not accept ICMP redirects (prevent MITM attacks)
+#net.ipv4.conf.all.accept_redirects = 0
+#net.ipv6.conf.all.accept_redirects = 0
+# _or_
+# Accept ICMP redirects only for gateways listed in our default
+# gateway list (enabled by default)
+# net.ipv4.conf.all.secure_redirects = 1
+#
+# Do not send ICMP redirects (we are not a router)
+#net.ipv4.conf.all.send_redirects = 0
+#
+# Do not accept IP source route packets (we are not a router)
+#net.ipv4.conf.all.accept_source_route = 0
+#net.ipv6.conf.all.accept_source_route = 0
+#
+# Log Martian Packets
+#net.ipv4.conf.all.log_martians = 1
+#
diff --git a/roles/vpn-stg-r/handlers/main.yml b/roles/vpn-stg-r/handlers/main.yml
new file mode 100644
index 0000000..719832b
--- /dev/null
+++ b/roles/vpn-stg-r/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+ - name: restart ipsec
+ service: name=ipsec state=restarted
+
diff --git a/roles/vpn-stg-r/tasks/main.yml b/roles/vpn-stg-r/tasks/main.yml
new file mode 100644
index 0000000..5160f44
--- /dev/null
+++ b/roles/vpn-stg-r/tasks/main.yml
@@ -0,0 +1,21 @@
+---
+#Installation ipsec strongswan côté droit pour le fichier de secret partagé
+ - name: install strongswan, fichier secret partagé
+ apt: name=strongswan state=present
+
+ - name: install tcpdump
+ apt: name=tcpdump state=present update_cache=yes
+
+ - name: activation du routage
+ copy: src=sysctl.conf dest=/etc/sysctl.conf
+
+ - name: Copie fichier ipsec.conf
+ copy: src=ipsec.conf dest=/etc/ipsec.conf
+ notify: restart ipsec
+
+ - name: Copie fichier ipsec.secrets
+ copy: src=ipsec.secrets dest=/etc/ipsec.secrets
+ notify: restart ipsec
+
+ - name: Message d'information
+ debug: msg="Veuillez consulter le document "r-vp.txt" dans ansible/gsb/doc"
\ No newline at end of file
diff --git a/roles/vpn/files/sysctl.conf b/roles/vpn/files/sysctl.conf
new file mode 100644
index 0000000..b138754
--- /dev/null
+++ b/roles/vpn/files/sysctl.conf
@@ -0,0 +1,60 @@
+#
+# /etc/sysctl.conf - Configuration file for setting system variables
+# See /etc/sysctl.d/ for additonal system variables
+# See sysctl.conf (5) for information.
+#
+
+#kernel.domainname = example.com
+
+# Uncomment the following to stop low-level messages on console
+#kernel.printk = 3 4 1 3
+
+##############################################################3
+# Functions previously found in netbase
+#
+
+# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
+# Turn on Source Address Verification in all interfaces to
+# prevent some spoofing attacks
+#net.ipv4.conf.default.rp_filter=1
+#net.ipv4.conf.all.rp_filter=1
+
+# Uncomment the next line to enable TCP/IP SYN cookies
+# See http://lwn.net/Articles/277146/
+# Note: This may impact IPv6 TCP sessions too
+#net.ipv4.tcp_syncookies=1
+
+# Uncomment the next line to enable packet forwarding for IPv4
+net.ipv4.ip_forward=1
+
+# Uncomment the next line to enable packet forwarding for IPv6
+# Enabling this option disables Stateless Address Autoconfiguration
+# based on Router Advertisements for this host
+#net.ipv6.conf.all.forwarding=1
+
+
+###################################################################
+# Additional settings - these settings can improve the network
+# security of the host and prevent against some network attacks
+# including spoofing attacks and man in the middle attacks through
+# redirection. Some network environments, however, require that these
+# settings are disabled so review and enable them as needed.
+#
+# Do not accept ICMP redirects (prevent MITM attacks)
+#net.ipv4.conf.all.accept_redirects = 0
+#net.ipv6.conf.all.accept_redirects = 0
+# _or_
+# Accept ICMP redirects only for gateways listed in our default
+# gateway list (enabled by default)
+# net.ipv4.conf.all.secure_redirects = 1
+#
+# Do not send ICMP redirects (we are not a router)
+#net.ipv4.conf.all.send_redirects = 0
+#
+# Do not accept IP source route packets (we are not a router)
+#net.ipv4.conf.all.accept_source_route = 0
+#net.ipv6.conf.all.accept_source_route = 0
+#
+# Log Martian Packets
+#net.ipv4.conf.all.log_martians = 1
+#
diff --git a/roles/vpn/handlers/main.yml b/roles/vpn/handlers/main.yml
new file mode 100644
index 0000000..75fe472
--- /dev/null
+++ b/roles/vpn/handlers/main.yml
@@ -0,0 +1,6 @@
+---
+ - name: restart racoon
+ service: name=racoon state=restarted
+
+ - name: restart setkey
+ service: name=setkey state=restarted
diff --git a/roles/vpn/tasks/main.yml b/roles/vpn/tasks/main.yml
new file mode 100644
index 0000000..5288385
--- /dev/null
+++ b/roles/vpn/tasks/main.yml
@@ -0,0 +1,23 @@
+---
+ - name: Installation Racoon
+ apt: name=racoon state=present update_cache=yes
+
+ - name: install ipsec-tools
+ apt: name=ipsec-tools state=present update_cache=yes
+
+ - name: install tcpdump
+ apt: name=tcpdump state=present update_cache=yes
+
+ - name: generation racoon.conf
+ template: src=racoon.conf.j2 dest=/etc/racoon/racoon.conf
+
+ - name: generation ipsec-tools.conf
+ template: src=ipsec-tools.conf.j2 dest=/etc/ipsec-tools.conf
+ notify: restart setkey
+
+ - name: generation psk.txt
+ template: src=psk.txt.j2 dest=/etc/racoon/psk.txt
+ notify: restart racoon
+
+ - name: activation du routage
+ copy: src=sysctl.conf dest=/etc/sysctl.conf
diff --git a/roles/vpn/templates/ipsec-tools.conf.j2 b/roles/vpn/templates/ipsec-tools.conf.j2
new file mode 100755
index 0000000..d5205df
--- /dev/null
+++ b/roles/vpn/templates/ipsec-tools.conf.j2
@@ -0,0 +1,9 @@
+flush;
+spdflush;
+
+spdadd {{ mynet }}/24 {{ remnet }}/24 any -P out ipsec
+ esp/tunnel/{{ ip1 }}-{{ remip }}/require;
+
+spdadd {{ remnet }}/24 {{ mynet }}/24 any -P in ipsec
+ esp/tunnel/{{ remip }}-{{ ip1 }}/require;
+
diff --git a/roles/vpn/templates/psk.txt.j2 b/roles/vpn/templates/psk.txt.j2
new file mode 100644
index 0000000..12e07d4
--- /dev/null
+++ b/roles/vpn/templates/psk.txt.j2
@@ -0,0 +1,2 @@
+{{ remip }} secret
+
diff --git a/roles/vpn/templates/racoon.conf.j2 b/roles/vpn/templates/racoon.conf.j2
new file mode 100644
index 0000000..d5d52a7
--- /dev/null
+++ b/roles/vpn/templates/racoon.conf.j2
@@ -0,0 +1,19 @@
+path pre_shared_key "/etc/racoon/psk.txt";
+
+remote {{ remip }} {
+ exchange_mode main,aggressive;
+ proposal {
+ encryption_algorithm 3des;
+ hash_algorithm sha1;
+ authentication_method pre_shared_key;
+ dh_group 2;
+ }
+}
+
+sainfo address {{ mynet }}/24 any address {{ remnet }}/24 any {
+ pfs_group 2;
+ lifetime time 1 hour ;
+ encryption_algorithm 3des, blowfish 448, rijndael ;
+ authentication_algorithm hmac_sha1, hmac_md5 ;
+ compression_algorithm deflate ;
+}
diff --git a/roles/webautoconf/files/wpad.dat b/roles/webautoconf/files/wpad.dat
new file mode 100644
index 0000000..30b5560
--- /dev/null
+++ b/roles/webautoconf/files/wpad.dat
@@ -0,0 +1,12 @@
+// config automatique
+// PS - 2015-06-09
+function FindProxyForURL(url, host)
+ {
+ if (isPlainHostName(host) ||
+ dnsDomainIs(host, "gsb.lan") ||
+ isInNet(host, "172.16.0.0", "255.255.255.0") ||
+ isInNet(host, "127.0.0.1", "255.255.255.255"))
+ return "DIRECT";
+ else
+ return "PROXY 172.16.0.2:8080";
+ }
diff --git a/roles/webautoconf/tasks/main.yml b/roles/webautoconf/tasks/main.yml
new file mode 100644
index 0000000..b43eede
--- /dev/null
+++ b/roles/webautoconf/tasks/main.yml
@@ -0,0 +1,9 @@
+---
+
+- name: Installation lighttpd
+ apt: name=lighttpd state=present
+
+- name: Copie wpad.dat
+ copy: src=wpad.dat dest=/var/www/html
+
+
diff --git a/roles/wordpress/files/wordpress-4.4.1-fr_FR.tar.gz b/roles/wordpress/files/wordpress-4.4.1-fr_FR.tar.gz
new file mode 100644
index 0000000..0068222
Binary files /dev/null and b/roles/wordpress/files/wordpress-4.4.1-fr_FR.tar.gz differ
diff --git a/roles/wordpress/handlers/main.yml b/roles/wordpress/handlers/main.yml
new file mode 100644
index 0000000..b8b354d
--- /dev/null
+++ b/roles/wordpress/handlers/main.yml
@@ -0,0 +1,3 @@
+---
+ - name: restart apache2
+ service: name=apache2 state=restarted
diff --git a/roles/wordpress/tasks/main.yml b/roles/wordpress/tasks/main.yml
new file mode 100644
index 0000000..4c6f47a
--- /dev/null
+++ b/roles/wordpress/tasks/main.yml
@@ -0,0 +1,40 @@
+---
+- name: Téléchargement de wordpress
+ get_url:
+ url: http://depl/gsbstore/wordpress-5.3.2-fr_FR.tar.gz
+ dest: /var/www/html
+
+- name: Extraction du fichier wordpress
+ unarchive:
+ src: /var/www/html/wordpress-5.3.2-fr_FR.tar.gz
+ dest: /var/www/html
+
+- name: Fix permissions owner
+ shell: chown -R www-data /var/www/html/wordpress
+
+- name: Fix permissions groups
+ shell: chgrp -R www-data /var/www/html/wordpress
+
+- name: Mettre à jour le site Apache par défaut
+ lineinfile:
+ dest: /etc/apache2/sites-enabled/000-default.conf
+ regexp: "(.)+DocumentRoot /var/www/html"
+ line: "DocumentRoot /var/www/html/wordpress"
+
+- name: restart apache2
+ service:
+ name: apache2
+ state: restarted
+
+- name: Mettre à jour le fichier de configuration WordPress
+ lineinfile:
+ dest: /var/www/html/wordpress/wp-config-sample.php
+ backup: yes
+ regexp: "{{ item.regexp }}"
+ line: "{{ item.line }}"
+ with_items:
+ - {'regexp': "define\\('DB_NAME', '(.)+'\\);", 'line': "define('DB_NAME', 'wordpress');"}
+ - {'regexp': "define\\('DB_HOST', '(.)+'\\);", 'line': "define('DB_HOST', 'localhost');"}
+ - {'regexp': "define\\('DB_USER', '(.)+'\\);", 'line': "define('DB_USER', 'wp');"}
+ - {'regexp': "define\\('DB_PASSWORD', '(.)+'\\);", 'line': "define('DB_PASSWORD', 'wp');"}
+
diff --git a/roles/x509-l/files/ipsec.conf b/roles/x509-l/files/ipsec.conf
new file mode 100644
index 0000000..f671978
--- /dev/null
+++ b/roles/x509-l/files/ipsec.conf
@@ -0,0 +1,25 @@
+config setup
+ charondebug="all"
+ uniqueids=yes
+ strictcrlpolicy=no
+conn %default
+conn tunnel #
+ left=192.168.0.52
+ leftsubnet=172.16.128.0/24
+ right=192.168.0.51
+ rightsubnet=192.168.0.0/16, 172.16.0.0/24
+ ike=aes256-sha2_256-modp1024!
+ esp=aes256-sha2_256!
+ keyingtries=0
+ ikelifetime=1h
+ lifetime=8h
+ dpddelay=30
+ dpdtimeout=120
+ dpdaction=restart
+ #authby=secret
+ auto=start
+ keyexchange=ikev2
+ type=tunnel
+ leftcert=r-vp2Cert.pem
+ leftid="C=CH, O=GSB, CN=r-vp2"
+ rightid="C=CH, O=GSB, CN=r-vp1"
\ No newline at end of file
diff --git a/roles/x509-l/files/ipsec.secrets b/roles/x509-l/files/ipsec.secrets
new file mode 100644
index 0000000..d5cfa53
--- /dev/null
+++ b/roles/x509-l/files/ipsec.secrets
@@ -0,0 +1,9 @@
+# This file holds shared secrets or RSA private keys for authentication.
+
+# RSA private key for this host, authenticating it to any other host
+# which knows the public part.
+
+# this file is managed with debconf and will contain the automatically created private key
+#include /var/lib/strongswan/ipsec.secrets.inc
+#192.168.0.52 192.168.0.51 : PSK 'root'
+: RSA r-vp2Key.pem
\ No newline at end of file
diff --git a/roles/x509-l/files/sysctl.conf b/roles/x509-l/files/sysctl.conf
new file mode 100644
index 0000000..b138754
--- /dev/null
+++ b/roles/x509-l/files/sysctl.conf
@@ -0,0 +1,60 @@
+#
+# /etc/sysctl.conf - Configuration file for setting system variables
+# See /etc/sysctl.d/ for additonal system variables
+# See sysctl.conf (5) for information.
+#
+
+#kernel.domainname = example.com
+
+# Uncomment the following to stop low-level messages on console
+#kernel.printk = 3 4 1 3
+
+##############################################################3
+# Functions previously found in netbase
+#
+
+# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
+# Turn on Source Address Verification in all interfaces to
+# prevent some spoofing attacks
+#net.ipv4.conf.default.rp_filter=1
+#net.ipv4.conf.all.rp_filter=1
+
+# Uncomment the next line to enable TCP/IP SYN cookies
+# See http://lwn.net/Articles/277146/
+# Note: This may impact IPv6 TCP sessions too
+#net.ipv4.tcp_syncookies=1
+
+# Uncomment the next line to enable packet forwarding for IPv4
+net.ipv4.ip_forward=1
+
+# Uncomment the next line to enable packet forwarding for IPv6
+# Enabling this option disables Stateless Address Autoconfiguration
+# based on Router Advertisements for this host
+#net.ipv6.conf.all.forwarding=1
+
+
+###################################################################
+# Additional settings - these settings can improve the network
+# security of the host and prevent against some network attacks
+# including spoofing attacks and man in the middle attacks through
+# redirection. Some network environments, however, require that these
+# settings are disabled so review and enable them as needed.
+#
+# Do not accept ICMP redirects (prevent MITM attacks)
+#net.ipv4.conf.all.accept_redirects = 0
+#net.ipv6.conf.all.accept_redirects = 0
+# _or_
+# Accept ICMP redirects only for gateways listed in our default
+# gateway list (enabled by default)
+# net.ipv4.conf.all.secure_redirects = 1
+#
+# Do not send ICMP redirects (we are not a router)
+#net.ipv4.conf.all.send_redirects = 0
+#
+# Do not accept IP source route packets (we are not a router)
+#net.ipv4.conf.all.accept_source_route = 0
+#net.ipv6.conf.all.accept_source_route = 0
+#
+# Log Martian Packets
+#net.ipv4.conf.all.log_martians = 1
+#
diff --git a/roles/x509-l/handlers/main.yml b/roles/x509-l/handlers/main.yml
new file mode 100644
index 0000000..719832b
--- /dev/null
+++ b/roles/x509-l/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+ - name: restart ipsec
+ service: name=ipsec state=restarted
+
diff --git a/roles/x509-l/tasks/main.yml b/roles/x509-l/tasks/main.yml
new file mode 100644
index 0000000..b42d977
--- /dev/null
+++ b/roles/x509-l/tasks/main.yml
@@ -0,0 +1,21 @@
+---
+#Installation ipsec strongswan côté gauche pour la communication via certificat
+ - name: 1. install strongswan, com via certificat
+ apt: name=strongswan state=present
+
+ - name: install tcpdump
+ apt: name=tcpdump state=present update_cache=yes
+
+ - name: activation du routage
+ copy: src=sysctl.conf dest=/etc/sysctl.conf
+
+ - name: Copie fichier ipsec.conf
+ copy: src=ipsec.conf dest=/etc/ipsec.conf
+ notify: restart ipsec
+
+ - name: Copie fichier ipsec.secrets
+ copy: src=ipsec.secrets dest=/etc/ipsec.secrets
+ notify: restart ipsec
+
+ - name: Message d'information
+ debug: msg="Veuillez consulter le document "r-vp.txt" dans ansible/gsb/doc"
\ No newline at end of file
diff --git a/roles/x509-r/files/generate.sh b/roles/x509-r/files/generate.sh
new file mode 100755
index 0000000..4adff04
--- /dev/null
+++ b/roles/x509-r/files/generate.sh
@@ -0,0 +1,19 @@
+#!/bin/bash
+
+cd /etc/ipsec.d
+
+ipsec pki --gen --type rsa --size 4096 --outform pem > private/strongswanKey.pem
+
+ipsec pki --self --ca --lifetime 3650 --in private/strongswanKey.pem --type rsa --dn "C=CH, O=GSB, CN=Root CA" --outform pem > cacerts/strongswanCert.pem
+
+ipsec pki --gen --type rsa --size 2048 --outform pem > private/r-vp1Key.pem
+
+chmod 600 private/r-vp1Key.pem
+
+ipsec pki --pub --in private/r-vp1Key.pem --type rsa | ipsec pki --issue --lifetime 730 --cacert cacerts/strongswanCert.pem --cakey private/strongswanKey.pem --dn "C=CH, O=GSB, CN=r-vp1" --san r-vp1 --flag serverAuth --flag ikeIntermediate --outform pem > certs/r-vp1Cert.pem
+
+ipsec pki --gen --type rsa --size 2048 --outform pem > private/r-vp2Key.pem
+
+chmod 600 private/r-vp2Key.pem
+
+ipsec pki --pub --in private/r-vp2Key.pem --type rsa | ipsec pki --issue --lifetime 730 --cacert cacerts/strongswanCert.pem --cakey private/strongswanKey.pem --dn "C=CH, O=GSB, CN=r-vp2" --san r-vp2 --flag serverAuth --flag ikeIntermediate --outform pem > certs/r-vp2Cert.pem
\ No newline at end of file
diff --git a/roles/x509-r/files/ipsec.conf b/roles/x509-r/files/ipsec.conf
new file mode 100644
index 0000000..62dfa9c
--- /dev/null
+++ b/roles/x509-r/files/ipsec.conf
@@ -0,0 +1,25 @@
+config setup
+ charondebug="all"
+ uniqueids=yes
+ strictcrlpolicy=no
+conn %default
+conn tunnel #
+ left=192.168.0.51
+ leftsubnet=192.168.0.0/16, 172.16.0.0/24
+ right=192.168.0.52
+ rightsubnet=172.16.128.0/24
+ ike=aes256-sha2_256-modp1024!
+ esp=aes256-sha2_256!
+ keyingtries=0
+ ikelifetime=1h
+ lifetime=8h
+ dpddelay=30
+ dpdtimeout=120
+ dpdaction=restart
+ #authby=secret
+ auto=start
+ keyexchange=ikev2
+ type=tunnel
+ leftcert=r-vp1Cert.pem
+ leftid="C=CH, O=GSB, CN=r-vp1"
+ rightid="C=CH, O=GSB, CN=r-vp2"
\ No newline at end of file
diff --git a/roles/x509-r/files/ipsec.secrets b/roles/x509-r/files/ipsec.secrets
new file mode 100644
index 0000000..4965c70
--- /dev/null
+++ b/roles/x509-r/files/ipsec.secrets
@@ -0,0 +1,9 @@
+# This file holds shared secrets or RSA private keys for authentication.
+
+# RSA private key for this host, authenticating it to any other host
+# which knows the public part.
+
+# this file is managed with debconf and will contain the automatically created private key
+#include /var/lib/strongswan/ipsec.secrets.inc
+#192.168.0.51 192.168.0.52 : PSK 'root'
+: RSA r-vp1Key.pem
\ No newline at end of file
diff --git a/roles/x509-r/files/recupKey.sh b/roles/x509-r/files/recupKey.sh
new file mode 100755
index 0000000..049a432
--- /dev/null
+++ b/roles/x509-r/files/recupKey.sh
@@ -0,0 +1,16 @@
+#!/bin/bash
+
+REMH=192.168.0.52
+
+cd /etc/ipsec.d
+
+scp cacerts/strongswanCert.pem root@$REMH:/etc/ipsec.d/cacerts
+
+scp certs/r-vp2Cert.pem root@$REMH:/etc/ipsec.d/certs
+
+scp certs/r-vp1Cert.pem root@$REMH:/etc/ipsec.d/certs
+
+scp private/r-vp2Key.pem root@$REMH:/etc/ipsec.d/private
+
+scp private/r-vp1Key.pem root@$REMH:/etc/ipsec.d/private
+
diff --git a/roles/x509-r/files/sysctl.conf b/roles/x509-r/files/sysctl.conf
new file mode 100644
index 0000000..b138754
--- /dev/null
+++ b/roles/x509-r/files/sysctl.conf
@@ -0,0 +1,60 @@
+#
+# /etc/sysctl.conf - Configuration file for setting system variables
+# See /etc/sysctl.d/ for additonal system variables
+# See sysctl.conf (5) for information.
+#
+
+#kernel.domainname = example.com
+
+# Uncomment the following to stop low-level messages on console
+#kernel.printk = 3 4 1 3
+
+##############################################################3
+# Functions previously found in netbase
+#
+
+# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
+# Turn on Source Address Verification in all interfaces to
+# prevent some spoofing attacks
+#net.ipv4.conf.default.rp_filter=1
+#net.ipv4.conf.all.rp_filter=1
+
+# Uncomment the next line to enable TCP/IP SYN cookies
+# See http://lwn.net/Articles/277146/
+# Note: This may impact IPv6 TCP sessions too
+#net.ipv4.tcp_syncookies=1
+
+# Uncomment the next line to enable packet forwarding for IPv4
+net.ipv4.ip_forward=1
+
+# Uncomment the next line to enable packet forwarding for IPv6
+# Enabling this option disables Stateless Address Autoconfiguration
+# based on Router Advertisements for this host
+#net.ipv6.conf.all.forwarding=1
+
+
+###################################################################
+# Additional settings - these settings can improve the network
+# security of the host and prevent against some network attacks
+# including spoofing attacks and man in the middle attacks through
+# redirection. Some network environments, however, require that these
+# settings are disabled so review and enable them as needed.
+#
+# Do not accept ICMP redirects (prevent MITM attacks)
+#net.ipv4.conf.all.accept_redirects = 0
+#net.ipv6.conf.all.accept_redirects = 0
+# _or_
+# Accept ICMP redirects only for gateways listed in our default
+# gateway list (enabled by default)
+# net.ipv4.conf.all.secure_redirects = 1
+#
+# Do not send ICMP redirects (we are not a router)
+#net.ipv4.conf.all.send_redirects = 0
+#
+# Do not accept IP source route packets (we are not a router)
+#net.ipv4.conf.all.accept_source_route = 0
+#net.ipv6.conf.all.accept_source_route = 0
+#
+# Log Martian Packets
+#net.ipv4.conf.all.log_martians = 1
+#
diff --git a/roles/x509-r/handlers/main.yml b/roles/x509-r/handlers/main.yml
new file mode 100644
index 0000000..719832b
--- /dev/null
+++ b/roles/x509-r/handlers/main.yml
@@ -0,0 +1,4 @@
+---
+ - name: restart ipsec
+ service: name=ipsec state=restarted
+
diff --git a/roles/x509-r/tasks/main.yml b/roles/x509-r/tasks/main.yml
new file mode 100644
index 0000000..edf5992
--- /dev/null
+++ b/roles/x509-r/tasks/main.yml
@@ -0,0 +1,36 @@
+---
+#Installation ipsec strongswan côté droit pour la communication via certificat
+ - name: install strongswan, com via certificat
+ apt: name=strongswan state=present
+
+ - name: install strongswan-pki
+ apt: name=strongswan-pki state=present
+
+ - name: install tcpdump
+ apt: name=tcpdump state=present update_cache=yes
+
+ - name: activation du routage
+ copy: src=sysctl.conf dest=/etc/sysctl.conf
+
+ - name: Copie fichier ipsec.conf
+ copy: src=ipsec.conf dest=/etc/ipsec.conf
+ notify: restart ipsec
+
+ - name: Copie fichier ipsec.secrets
+ copy: src=ipsec.secrets dest=/etc/ipsec.secrets
+ notify: restart ipsec
+
+ - name: Copie fichier generate.sh
+ copy: src=generate.sh dest=/root/
+
+ - name: Generation de la CA et des certificats
+ shell: /bin/bash /root/generate.sh >> generate-log.txt
+
+ - name: Copie fichier recupKey.sh
+ copy: src=recupKey.sh dest=/root/
+
+ - name: Lancement recupKey.sh
+ shell: /bin/bash /root/recupKey.sh
+
+ - name: Message d'information
+ debug: msg="Veuillez consulter le document "r-vp.txt" dans ansible/gsb/doc"
\ No newline at end of file
diff --git a/s-adm.yml b/s-adm.yml
new file mode 100644
index 0000000..169c8c1
--- /dev/null
+++ b/s-adm.yml
@@ -0,0 +1,15 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - s-ssh
+ - dnsmasq
+ - squid
+ # - webautoconf
+ - snmp-agent
+ - syslog-cli
+ - post
+
diff --git a/s-agence.yml b/s-agence.yml
new file mode 100644
index 0000000..8de8bee
--- /dev/null
+++ b/s-agence.yml
@@ -0,0 +1,9 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/s-appli.yml b/s-appli.yml
new file mode 100644
index 0000000..1cb07f9
--- /dev/null
+++ b/s-appli.yml
@@ -0,0 +1,13 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - appli
+ - ssh-cli
+ - syslog-cli
+ - snmp-agent
+ - post
+
diff --git a/s-backup.yml b/s-backup.yml
new file mode 100644
index 0000000..0ca3cad
--- /dev/null
+++ b/s-backup.yml
@@ -0,0 +1,11 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+# - proxy3
+# - snmp-agent
+# - ssh-cli
+ - syslog-cli
+ - post
diff --git a/s-bdd.yml b/s-bdd.yml
new file mode 100644
index 0000000..83e4dc1
--- /dev/null
+++ b/s-bdd.yml
@@ -0,0 +1,23 @@
+---
+ - hosts: localhost
+ connection: local
+ vars:
+ maria_dbhost: "192.168.102.254"
+ maria_dbname: "wordpress"
+ maria_dbuser: "wp"
+ maria_dbpasswd: "wp"
+
+
+ roles:
+ - base
+ - goss
+# - s-lb-bd
+ - mariadb
+ - role: db-user
+ cli_ip: "192.168.102.1"
+ - role: db-user
+ cli_ip: "192.168.102.2"
+ - role: db-user
+ cli_ip: "192.168.102.3"
+ - snmp-agent
+ - post
diff --git a/s-docker.yml b/s-docker.yml
new file mode 100644
index 0000000..b7343ac
--- /dev/null
+++ b/s-docker.yml
@@ -0,0 +1,14 @@
+---
+- hosts: localhost
+ connection: local
+ # include: config.yml
+ roles:
+ - base
+ - goss
+ - snmp-agent
+ - ssh-cli
+ - syslog-cli
+ - docker-openvas-ab
+ #- docker-iredmail-ab
+ - post
+
diff --git a/s-fog.yml b/s-fog.yml
new file mode 100644
index 0000000..56d1490
--- /dev/null
+++ b/s-fog.yml
@@ -0,0 +1,12 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - fog
+ - dhcp-fog
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/s-graylog.yml b/s-graylog.yml
new file mode 100644
index 0000000..0127d98
--- /dev/null
+++ b/s-graylog.yml
@@ -0,0 +1,12 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - docker-graylog
+ - ssh-cli
+ - syslog
+ - post
+
diff --git a/s-infra.yml b/s-infra.yml
new file mode 100644
index 0000000..c7bf1ff
--- /dev/null
+++ b/s-infra.yml
@@ -0,0 +1,14 @@
+---
+- hosts: localhost
+ connection: local
+ # include: config.yml
+ roles:
+ - base
+ - goss
+ - dns-master
+ - webautoconf
+ - snmp-agent
+ - syslog-cli
+ - ssh-cli
+ - post
+
diff --git a/s-itil.yml b/s-itil.yml
new file mode 100644
index 0000000..5bab648
--- /dev/null
+++ b/s-itil.yml
@@ -0,0 +1,24 @@
+---
+- hosts: localhost
+ connection: local
+
+ vars:
+
+ glpi_version: "9.4.5"
+ fd_version: "9.4+1.1"
+ fd_version64: "x64_2.5.2"
+ fd_version86: "x86_2.5.2"
+ glpi_dir: "/var/www/html/glpi"
+ glpi_dbhost: "127.0.0.1"
+ glpi_dbname: "glpi"
+ glpi_dbuser: "glpi"
+ glpi_dbpasswd: "glpi"
+
+ roles:
+ - base
+ - goss
+ - snmp-agent
+ - itil
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/s-lb-bd.yml b/s-lb-bd.yml
new file mode 100644
index 0000000..656c459
--- /dev/null
+++ b/s-lb-bd.yml
@@ -0,0 +1,23 @@
+---
+ - hosts: localhost
+ connection: local
+ vars:
+ maria_dbhost: "192.168.102.254"
+ maria_dbname: "wordpress"
+ maria_dbuser: "wp"
+ maria_dbpasswd: "wp"
+
+
+ roles:
+ - base
+ - goss
+ #- s-lb-bd-ab
+ - mariadb-ab
+ - role: db-user
+ cli_ip: "192.168.102.1"
+ - role: db-user
+ cli_ip: "192.168.102.2"
+ - role: db-user
+ cli_ip: "192.168.102.3"
+ - snmp-agent
+ - post
diff --git a/s-lb-web1.yml b/s-lb-web1.yml
new file mode 100644
index 0000000..0c1dc9b
--- /dev/null
+++ b/s-lb-web1.yml
@@ -0,0 +1,11 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - s-lb-web-ab
+ - snmp-agent
+ - s-nas-client
+ - post
+
diff --git a/s-lb-web2.yml b/s-lb-web2.yml
new file mode 100644
index 0000000..0c1dc9b
--- /dev/null
+++ b/s-lb-web2.yml
@@ -0,0 +1,11 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - s-lb-web-ab
+ - snmp-agent
+ - s-nas-client
+ - post
+
diff --git a/s-lb-web3.yml b/s-lb-web3.yml
new file mode 100644
index 0000000..0c1dc9b
--- /dev/null
+++ b/s-lb-web3.yml
@@ -0,0 +1,11 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - s-lb-web-ab
+ - snmp-agent
+ - s-nas-client
+ - post
+
diff --git a/s-lb-wordpress.yml b/s-lb-wordpress.yml
new file mode 100644
index 0000000..ed195a5
--- /dev/null
+++ b/s-lb-wordpress.yml
@@ -0,0 +1,18 @@
+---
+ - hosts: localhost
+ connection: local
+ vars:
+ wp_mysql_db: "wordpress"
+ wp_mysql_user: "wp"
+ wp_mysql_password: "wp"
+ wp_mysql_host: "192.168.102.50"
+
+ roles:
+ - base
+ - goss
+ - apache2
+ - s-lb-wordpress
+ - snmp-agent
+ - post
+ - mysql
+ - php-fpm
diff --git a/s-lb-wordpress2.yml b/s-lb-wordpress2.yml
new file mode 100644
index 0000000..ed195a5
--- /dev/null
+++ b/s-lb-wordpress2.yml
@@ -0,0 +1,18 @@
+---
+ - hosts: localhost
+ connection: local
+ vars:
+ wp_mysql_db: "wordpress"
+ wp_mysql_user: "wp"
+ wp_mysql_password: "wp"
+ wp_mysql_host: "192.168.102.50"
+
+ roles:
+ - base
+ - goss
+ - apache2
+ - s-lb-wordpress
+ - snmp-agent
+ - post
+ - mysql
+ - php-fpm
diff --git a/s-lb-wordpress3.yml b/s-lb-wordpress3.yml
new file mode 100644
index 0000000..ed195a5
--- /dev/null
+++ b/s-lb-wordpress3.yml
@@ -0,0 +1,18 @@
+---
+ - hosts: localhost
+ connection: local
+ vars:
+ wp_mysql_db: "wordpress"
+ wp_mysql_user: "wp"
+ wp_mysql_password: "wp"
+ wp_mysql_host: "192.168.102.50"
+
+ roles:
+ - base
+ - goss
+ - apache2
+ - s-lb-wordpress
+ - snmp-agent
+ - post
+ - mysql
+ - php-fpm
diff --git a/s-lb.yml b/s-lb.yml
new file mode 100644
index 0000000..7b0374f
--- /dev/null
+++ b/s-lb.yml
@@ -0,0 +1,11 @@
+---
+ - hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - s-lb-ab
+ - snmp-agent
+ - post
+
diff --git a/s-mess.yml b/s-mess.yml
new file mode 100644
index 0000000..ca8244b
--- /dev/null
+++ b/s-mess.yml
@@ -0,0 +1,11 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - docker-iredmail-ab
+ - ssh-cli
+ - syslog-cli
+ - snmp-agent
+ - post
diff --git a/s-mon-gm.yml b/s-mon-gm.yml
new file mode 100644
index 0000000..6a75616
--- /dev/null
+++ b/s-mon-gm.yml
@@ -0,0 +1,13 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - icinga-gm
+ - postfix
+ - ssh-cli
+ - syslog
+ - post
+
diff --git a/s-mon-kb.yml b/s-mon-kb.yml
new file mode 100644
index 0000000..4989d8b
--- /dev/null
+++ b/s-mon-kb.yml
@@ -0,0 +1,13 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - icinga-kb
+ - postfix
+ - ssh-cli
+ - syslog
+ - post
+
diff --git a/s-mon-yb.yml b/s-mon-yb.yml
new file mode 100644
index 0000000..3ba8297
--- /dev/null
+++ b/s-mon-yb.yml
@@ -0,0 +1,13 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - icinga-yb
+ - postfix
+ - ssh-cli
+ - syslog
+ - post
+
diff --git a/s-mon.yml b/s-mon.yml
new file mode 100644
index 0000000..e9b2915
--- /dev/null
+++ b/s-mon.yml
@@ -0,0 +1,13 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - icinga-fk
+ - postfix-fk
+ - ssh-cli
+ - syslog
+ - post
+
diff --git a/s-nas.yml b/s-nas.yml
new file mode 100644
index 0000000..357cdb8
--- /dev/null
+++ b/s-nas.yml
@@ -0,0 +1,17 @@
+---
+- hosts: localhost
+ connection: local
+ vars:
+ wp_mysql_db: "wordpress"
+ wp_mysql_user: "wp"
+ wp_mysql_password: "wp"
+ wp_mysql_host: "192.168.102.254"
+
+ roles:
+ - base
+ - snmp-agent
+ - s-lb-wordpress
+ - s-nas-server
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/s-proxy.yml b/s-proxy.yml
new file mode 100644
index 0000000..7083cdc
--- /dev/null
+++ b/s-proxy.yml
@@ -0,0 +1,12 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - goss
+ - squid
+ - snmp-agent
+ - ssh-cli
+ - syslog-cli
+ - post
diff --git a/s-test.yml b/s-test.yml
new file mode 100644
index 0000000..521df21
--- /dev/null
+++ b/s-test.yml
@@ -0,0 +1,12 @@
+---
+- hosts: localhost
+ connection: local
+ # include: config.yml
+ roles:
+ - base
+ - goss
+ - snmp-agent
+ - syslog-cli
+ - ssh-cli
+ - post
+
diff --git a/s-web.yml b/s-web.yml
new file mode 100644
index 0000000..6b5b855
--- /dev/null
+++ b/s-web.yml
@@ -0,0 +1,14 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - apache2
+ - snmp-agent
+ - ssh-cli
+ - syslog-cli
+ - post
+ #- mysql
+ - wordpress
+
diff --git a/s-web1.yml b/s-web1.yml
new file mode 100644
index 0000000..708b134
--- /dev/null
+++ b/s-web1.yml
@@ -0,0 +1,11 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - s-lb-web
+ - snmp-agent
+ - s-nas-client
+ - post
+
diff --git a/s-web2.yml b/s-web2.yml
new file mode 100644
index 0000000..708b134
--- /dev/null
+++ b/s-web2.yml
@@ -0,0 +1,11 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - s-lb-web
+ - snmp-agent
+ - s-nas-client
+ - post
+
diff --git a/scripts/Windows/addint-r-ext.bat b/scripts/Windows/addint-r-ext.bat
new file mode 100644
index 0000000..6954297
--- /dev/null
+++ b/scripts/Windows/addint-r-ext.bat
@@ -0,0 +1,31 @@
+cd C:\Program Files\Oracle\VirtualBox
+
+VBoxManage modifyvm r-ext --nic1 intnet
+VBoxManage modifyvm r-ext --intnet1 "n-adm"
+VBoxManage modifyvm r-ext --nictype1 82540EM
+VBoxManage modifyvm r-ext --cableconnected1 on
+VBoxManage modifyvm r-ext --nicpromisc1 allow-all
+
+VBoxManage modifyvm r-ext --nic2 intnet
+VBoxManage modifyvm r-ext --intnet2 "n-dmz"
+VBoxManage modifyvm r-ext --nictype2 82540EM
+VBoxManage modifyvm r-ext --cableconnected2 on
+VBoxManage modifyvm r-ext --nicpromisc2 allow-all
+
+VBoxManage modifyvm r-ext --nic3 bridged
+VBoxManage modifyvm r-ext --bridgeadapter3 "enp0s3"
+VBoxManage modifyvm r-ext --nictype3 82540EM
+VBoxManage modifyvm r-ext --cableconnected3 on
+VBoxManage modifyvm r-ext --nicpromisc3 allow-all
+
+VBoxManage modifyvm r-ext --nic4 intnet
+VBoxManage modifyvm r-ext --intnet4 "n-linkv"
+VBoxManage modifyvm r-ext --nictype4 82540EM
+VBoxManage modifyvm r-ext --cableconnected4 on
+VBoxManage modifyvm r-ext --nicpromisc4 allow-all
+
+VBoxManage modifyvm r-ext --nic5 intnet
+VBoxManage modifyvm r-ext --intnet5 "n-link"
+VBoxManage modifyvm r-ext --nictype5 82540EM
+VBoxManage modifyvm r-ext --cableconnected5 on
+VBoxManage modifyvm r-ext --nicpromisc5 allow-all
diff --git a/scripts/Windows/addint-r-int.bat b/scripts/Windows/addint-r-int.bat
new file mode 100644
index 0000000..cefd634
--- /dev/null
+++ b/scripts/Windows/addint-r-int.bat
@@ -0,0 +1,33 @@
+cd C:\Program Files\Oracle\VirtualBox
+
+VBoxManage modifyvm r-int --nic1 intnet
+VBoxManage modifyvm r-int --intnet1 "n-adm"
+VBoxManage modifyvm r-int --nictype1 82540EM
+VBoxManage modifyvm r-int --cableconnected1 on
+VBoxManage modifyvm r-int --nicpromisc1 allow-all
+
+VBoxManage modifyvm r-int --nic2 intnet
+VBoxManage modifyvm r-int --intnet2 "n-link"
+VBoxManage modifyvm r-int --nictype2 82540EM
+VBoxManage modifyvm r-int --cableconnected2 on
+VBoxManage modifyvm r-int --nicpromisc2 allow-all
+
+VBoxManage modifyvm r-int --nic3 intnet
+VBoxManage modifyvm r-int --intnet3 "n-wifi"
+VBoxManage modifyvm r-int --nictype3 82540EM
+VBoxManage modifyvm r-int --cableconnected3 on
+VBoxManage modifyvm r-int --nicpromisc3 allow-all
+
+VBoxManage modifyvm r-int --nic4 intnet
+VBoxManage modifyvm r-int --intnet4 "n-user"
+VBoxManage modifyvm r-int --nictype4 82540EM
+VBoxManage modifyvm r-int --cableconnected4 on
+VBoxManage modifyvm r-int --nicpromisc4 allow-all
+
+VBoxManage modifyvm r-int --nic5 intnet
+VBoxManage modifyvm r-int --intnet5 "n-infra"
+VBoxManage modifyvm r-int --nictype5 82540EM
+VBoxManage modifyvm r-int --cableconnected5 on
+VBoxManage modifyvm r-int --nicpromisc5 allow-all
+
+
diff --git a/scripts/addint.r-ext b/scripts/addint.r-ext
new file mode 100755
index 0000000..e2d5e96
--- /dev/null
+++ b/scripts/addint.r-ext
@@ -0,0 +1,42 @@
+#!/bin/bash
+nom=r-ext
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-dmz (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-dmz"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
+
+# (enp0s9)
+
+VBoxManage modifyvm $nom --nic3 bridged
+VBoxManage modifyvm $nom --bridgeadapter3 "eno1"
+VBoxManage modifyvm $nom --nictype3 82540EM
+VBoxManage modifyvm $nom --cableconnected3 on
+VBoxManage modifyvm $nom --nicpromisc3 allow-all
+
+# N-linkv (enp0s10)
+
+VBoxManage modifyvm $nom --nic4 intnet
+VBoxManage modifyvm $nom --intnet4 "n-linkv"
+VBoxManage modifyvm $nom --nictype4 82540EM
+VBoxManage modifyvm $nom --cableconnected4 on
+VBoxManage modifyvm $nom --nicpromisc4 allow-all
+
+# N-link (enp0s16)
+
+VBoxManage modifyvm $nom --nic5 intnet
+VBoxManage modifyvm $nom --intnet5 "n-link"
+VBoxManage modifyvm $nom --nictype5 82540EM
+VBoxManage modifyvm $nom --cableconnected5 on
+VBoxManage modifyvm $nom --nicpromisc5 allow-all
diff --git a/scripts/addint.r-int b/scripts/addint.r-int
new file mode 100755
index 0000000..720fdd7
--- /dev/null
+++ b/scripts/addint.r-int
@@ -0,0 +1,41 @@
+#!/bin/bash
+nom=r-int
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+# N-link (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-link"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
+
+# N-wifi (enp0s9)
+
+VBoxManage modifyvm $nom --nic3 intnet
+VBoxManage modifyvm $nom --intnet3 "n-wifi"
+VBoxManage modifyvm $nom --nictype3 82540EM
+VBoxManage modifyvm $nom --cableconnected3 on
+VBoxManage modifyvm $nom --nicpromisc3 allow-all
+
+# N-user (enp0s10)
+
+VBoxManage modifyvm $nom --nic4 intnet
+VBoxManage modifyvm $nom --intnet4 "n-user"
+VBoxManage modifyvm $nom --nictype4 82540EM
+VBoxManage modifyvm $nom --cableconnected4 on
+VBoxManage modifyvm $nom --nicpromisc4 allow-all
+
+# N-infra (enp0s16)
+
+VBoxManage modifyvm $nom --nic5 intnet
+VBoxManage modifyvm $nom --intnet5 "n-infra"
+VBoxManage modifyvm $nom --nictype5 82540EM
+VBoxManage modifyvm $nom --cableconnected5 on
+VBoxManage modifyvm $nom --nicpromisc5 allow-all
diff --git a/scripts/addint.s-adm b/scripts/addint.s-adm
new file mode 100755
index 0000000..da6c9de
--- /dev/null
+++ b/scripts/addint.s-adm
@@ -0,0 +1,16 @@
+#!/bin/bash
+nom=s-adm
+
+VBoxManage modifyvm $nom --nic1 bridged
+VBoxManage modifyvm $nom --bridgeadapter1 "eno1"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+#(enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-adm"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
\ No newline at end of file
diff --git a/scripts/addint.s-infra b/scripts/addint.s-infra
new file mode 100755
index 0000000..3cf7d32
--- /dev/null
+++ b/scripts/addint.s-infra
@@ -0,0 +1,18 @@
+#!/bin/bash
+nom=s-infra
+
+#(enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+#(enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-infra"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
diff --git a/scripts/addint.s-lb b/scripts/addint.s-lb
new file mode 100755
index 0000000..b90a5a2
--- /dev/null
+++ b/scripts/addint.s-lb
@@ -0,0 +1,26 @@
+#!/bin/bash
+nom=s-lb
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-dmz (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-dmz"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
+
+# N-dmz-lb (enp0s9)
+
+VBoxManage modifyvm $nom --nic3 intnet
+VBoxManage modifyvm $nom --intnet3 "n-dmz-lb"
+VBoxManage modifyvm $nom --nictype3 82540EM
+VBoxManage modifyvm $nom --cableconnected3 on
+VBoxManage modifyvm $nom --nicpromisc3 allow-all
diff --git a/scripts/addint.s-lb-bd b/scripts/addint.s-lb-bd
new file mode 100755
index 0000000..325f6b9
--- /dev/null
+++ b/scripts/addint.s-lb-bd
@@ -0,0 +1,18 @@
+#!/bin/bash
+nom=s-lb-bd
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-dmz-db (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-dmz-db"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
diff --git a/scripts/addint.s-lb-web1 b/scripts/addint.s-lb-web1
new file mode 100755
index 0000000..afb7269
--- /dev/null
+++ b/scripts/addint.s-lb-web1
@@ -0,0 +1,26 @@
+#!/bin/bash
+nom=s-lb-web1
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-dmz-lb (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-dmz-lb"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
+
+# N-dmz-db (enp0s9)
+
+VBoxManage modifyvm $nom --nic3 intnet
+VBoxManage modifyvm $nom --intnet3 "n-dmz-db"
+VBoxManage modifyvm $nom --nictype3 82540EM
+VBoxManage modifyvm $nom --cableconnected3 on
+VBoxManage modifyvm $nom --nicpromisc3 allow-all
diff --git a/scripts/addint.s-lb-web2 b/scripts/addint.s-lb-web2
new file mode 100755
index 0000000..13605fc
--- /dev/null
+++ b/scripts/addint.s-lb-web2
@@ -0,0 +1,26 @@
+#!/bin/bash
+nom=s-lb-web2
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-dmz-lb (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-dmz-lb"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
+
+# N-dmz-db (enp0s9)
+
+VBoxManage modifyvm $nom --nic3 intnet
+VBoxManage modifyvm $nom --intnet3 "n-dmz-db"
+VBoxManage modifyvm $nom --nictype3 82540EM
+VBoxManage modifyvm $nom --cableconnected3 on
+VBoxManage modifyvm $nom --nicpromisc3 allow-all
diff --git a/scripts/addint.s-lb-web3 b/scripts/addint.s-lb-web3
new file mode 100755
index 0000000..2d29eb6
--- /dev/null
+++ b/scripts/addint.s-lb-web3
@@ -0,0 +1,26 @@
+#!/bin/bash
+nom=s-lb-web3
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-dmz-lb (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-dmz-lb"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
+
+# N-dmz-db (enp0s9)
+
+VBoxManage modifyvm $nom --nic3 intnet
+VBoxManage modifyvm $nom --intnet3 "n-dmz-db"
+VBoxManage modifyvm $nom --nictype3 82540EM
+VBoxManage modifyvm $nom --cableconnected3 on
+VBoxManage modifyvm $nom --nicpromisc3 allow-all
diff --git a/scripts/addint.s-mon-kb b/scripts/addint.s-mon-kb
new file mode 100755
index 0000000..be39c26
--- /dev/null
+++ b/scripts/addint.s-mon-kb
@@ -0,0 +1,18 @@
+#!/bin/bash
+nom=s-mon-kb
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-infra (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-infra"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
diff --git a/scripts/addint.s-nas b/scripts/addint.s-nas
new file mode 100755
index 0000000..ae4584b
--- /dev/null
+++ b/scripts/addint.s-nas
@@ -0,0 +1,18 @@
+#!/bin/bash
+nom=s-nas
+
+# N-adm (enp0s3)
+
+VBoxManage modifyvm $nom --nic1 intnet
+VBoxManage modifyvm $nom --intnet1 "n-adm"
+VBoxManage modifyvm $nom --nictype1 82540EM
+VBoxManage modifyvm $nom --cableconnected1 on
+VBoxManage modifyvm $nom --nicpromisc1 allow-all
+
+# N-dmz-db (enp0s8)
+
+VBoxManage modifyvm $nom --nic2 intnet
+VBoxManage modifyvm $nom --intnet2 "n-dmz-db"
+VBoxManage modifyvm $nom --nictype2 82540EM
+VBoxManage modifyvm $nom --cableconnected2 on
+VBoxManage modifyvm $nom --nicpromisc2 allow-all
diff --git a/scripts/getall-2019 b/scripts/getall-2019
new file mode 100644
index 0000000..b37a753
--- /dev/null
+++ b/scripts/getall-2019
@@ -0,0 +1,16 @@
+#!/bin/bash
+GLPIREL=9.3.3
+wget -nc https://github.com/glpi-project/glpi/releases/download/$GLPIREL/glpi-$GLPIREL.tgz
+
+wget -nc https://github.com/fusioninventory/fusioninventory-for-glpi/releases/download/glpi9.3%2B1.2/fusioninventory-9.3+1.2.tar.gz
+
+FIAGREL=2.4.2
+wget -nc https://github.com/fusioninventory/fusioninventory-agent/releases/download/$FIAGREL/fusioninventory-agent_windows-x64_$FIAGREL.exe
+
+wget -nc https://github.com/fusioninventory/fusioninventory-agent/releases/download/$FIAGREL/fusioninventory-agent_windows-x86_$FIAGREL.exe
+
+FOGREL=1.5.5
+wget -nc https://github.com/FOGProject/fogproject/archive/$FOGREL.tar.gz -O fogproject-$FOGREL.tar.gz
+
+#wget -nc https://fr.wordpress.org/wordpress-4.9.1-fr_FR.tar.gz
+wget -nc https://fr.wordpress.org/wordpress-5.0.3-fr_FR.tar.gz
diff --git a/scripts/lb-http.bash b/scripts/lb-http.bash
new file mode 100644
index 0000000..019b660
--- /dev/null
+++ b/scripts/lb-http.bash
@@ -0,0 +1,6 @@
+#!/bin/bash
+
+while [ 1 ]
+do
+ curl --max-time 1 192.168.100.10/wordpress/
+done
\ No newline at end of file
diff --git a/scripts/recup-s-lb.bash b/scripts/recup-s-lb.bash
new file mode 100644
index 0000000..08323c9
--- /dev/null
+++ b/scripts/recup-s-lb.bash
@@ -0,0 +1,4 @@
+#!/bin/bash
+while [ 1 ]; do
+wget index.html http://192.168.100.10
+done
diff --git a/tests/s-infra.test b/tests/s-infra.test
new file mode 100755
index 0000000..f35a313
--- /dev/null
+++ b/tests/s-infra.test
@@ -0,0 +1,24 @@
+#!/bin/bash
+
+# Tests resolution directe dans gsb.lan nom court
+host s-infra
+host s-mon
+
+# Tests resolution directe nom long
+host s-infra.gsb.lan
+host s-mon.gsb.lan
+
+# Tests resolution inverse
+host 172.16.0.2
+host 172.16.0.9
+
+# Tests resolution hors zone
+host lemonde.fr
+host free.fr
+
+# Tests de connectivite
+ping -c 2 172.16.0.254
+ping -c 2 s-adm.gsb.adm
+
+# Test wpad
+curl wpad/wpad.dat
diff --git a/tests/s-proxy.test b/tests/s-proxy.test
new file mode 100755
index 0000000..a3bdbe3
--- /dev/null
+++ b/tests/s-proxy.test
@@ -0,0 +1,17 @@
+#!/bin/bash
+
+# Test wpad
+curl wpad/wpad.dat
+
+# Verification ouverture port 8080
+netstat -ln|grep 8080
+
+# Affichage access.log
+tail -5 /var/log/squid3/access.log
+
+# Affichage cache.log
+tail /var/log/squid3/cache.log
+
+
+# Affichage curl
+curl s-proxy:8080
diff --git a/user-yb.yml b/user-yb.yml
new file mode 100644
index 0000000..e889b3f
--- /dev/null
+++ b/user-yb.yml
@@ -0,0 +1,9 @@
+---
+- hosts: localhost
+ connection: local
+
+ roles:
+ - base
+ - syslog-cli
+ - post
+ - user-yb
diff --git a/windows/gsb-dossiers.cmd b/windows/gsb-dossiers.cmd
new file mode 100644
index 0000000..dfbc281
--- /dev/null
+++ b/windows/gsb-dossiers.cmd
@@ -0,0 +1,15 @@
+mkdir C:\gsb\partages
+cd C:\gsb\partages
+mkdir compta
+mkdir ventes
+mkdir public
+cd C:\gsb
+mkdir users
+
+
+for %%g in (gg-compta gg-ventes) do net group %%g /add
+
+net share compta=C:\gsb\partages\compta /grant:"Utilisateurs du domaine":FULL
+net share ventes=C:\gsb\partages\ventes /grant:"Utilisateurs du domaine":FULL
+net share commun=C:\gsb\partages\commun /grant:"Utilisateurs du domaine":FULL
+net share public=C:\gsb\partages\public /grant:"Utilisateurs du domaine":FULL
\ No newline at end of file
diff --git a/windows/mkusr-compta.cmd b/windows/mkusr-compta.cmd
new file mode 100644
index 0000000..00c956d
--- /dev/null
+++ b/windows/mkusr-compta.cmd
@@ -0,0 +1,4 @@
+call mkusr aDupont "Albert Dupon" gg-compta
+call mkusr cSeum "Claire Seum" gg-compta
+call mkusr nPaul "Nicolas Paul" gg-compta
+call mkusr atour "Alexandre Tour" gg-compta
diff --git a/windows/mkusr-ventes.cmd b/windows/mkusr-ventes.cmd
new file mode 100644
index 0000000..4ff36aa
--- /dev/null
+++ b/windows/mkusr-ventes.cmd
@@ -0,0 +1,5 @@
+@echo off
+call mkusr aDeloin "Alain Deloin" gg-ventes
+call mkusr sDel "Simon del" gg-ventes
+call mkusr aSalet "alfred Salet" gg-ventes
+call mkusr tInio "Thomas Inio" gg-ventes
\ No newline at end of file
diff --git a/windows/mkusr.cmd b/windows/mkusr.cmd
new file mode 100644
index 0000000..75fb801
--- /dev/null
+++ b/windows/mkusr.cmd
@@ -0,0 +1,7 @@
+@echo off
+echo Creation de %1 - %2
+mkdir C:\gsb\users\%1
+net user %1 Azerty1+ /fullname:%2 /homedir:\\cd\%1$ /ScriptPath:%3.cmd /add
+net share %1$=C:\gsb\users\%1
+icacls "C:\gsb\users\%1" /Grant:r %1:M /T
+net group %3 %1 /add
\ No newline at end of file