11.5.1 : configuration de base d’un périphérique Cisco

Étant donnée une adresse IP de 198.133.219.0/24, avec 4 bits empruntés pour des sous-réseaux, ajoutez les informations suivantes dans le tableau ci-dessus, soit sur votre ordinateur portable, soit sur une feuille de papier. (Conseil : ajoutez d'abord le numéro de sous-réseau, puis l'adresse d'hôte. Les informations d'adresse seront faciles à calculer si le numéro de sous-réseau est ajouté en premier.)
Nombre maximal de sous-réseaux utilisables (n'oubliez pas le premier sous-réseau, numéroté 0) ?
Nombre d'hôtes utilisables par sous-réseau ?

Solution : 4 bits = 15 sous réseaux ( 15 sous réseaux alors il nous faut 16 @ 16= 8*2 )
Nombre d’hôtes utilisables par sous-réseau : ________14_________
( 2*n -2 = 2*8 -2 = 14 )

Adresse IP : 198.133.219.0 Masque de sous-réseau : 255.255.255.240
# | Sous-réseau | Première adresse d’hôte | Dernière adresse d’hôte | Diffusion
0 198.133.219.0 198.133.219.1 198.133.219.14 198.133.219.15
1 198.133.219.16 198.133.219.17 198.133.219.30 198.133.219.31
2 198.133.219.32 198.133.219.33 198.133.219.46 198.133.219.47
3 198.133.219.48 198.133.219.49 198.133.219.62 198.133.219.63
4 198.133.219.64 198.133.219.65 198.133.219.78 198.133.219.79
5 198.133.219.80 198.133.219.81 198.133.219.94 198.133.219.95
6 198.133.219.96 198.133.219.97 198.133.219.110 198.133.219.111
7 198.133.219.112 198.133.219.113 198.133.219.126 198.133.219.127
8 198.133.219.128 198.133.219.129 198.133.219.142 198.133.219.143
9 198.133.219.144 198.133.219.145 198.133.219.158 198.133.219.159
10 198.133.219.160 198.133.219.161 198.133.219.174 198.133.219.175
11 198.133.219.176 198.133.219.177 198.133.219.190 198.133.219.191
12 198.133.219.192 198.133.219.193 198.133.219.206 198.133.219.207
13 198.133.219.208 198.133.219.209 198.133.219.222 198.133.219.223
14 198.133.219.224 198.133.219.225 198.133.219.238 198.133.219.239
15 198.133.219.240 198.133.219.241 198.133.219.254 198.133.219.255

Commentaires

Posts les plus consultés de ce blog

Open Media Vault NAS change password

Known Root Password Login to the OMV using the root user and the current password via SSH or Console enter the following command passwd root The new password is now active. Unknown Root Password, but Admin Access to OMV GUI is Available In this scenario we still can help ourselves with the GUI. The method we use is, that we create a cron job for the root user which then resets the password. Navigate to System -> Cron Jobs Press the +Add button UN-tick the enabled box, so that the cronjob does not run automatically. put into the command field the following line, replace newpasswd with your password: echo "root:newpasswd" | chpasswd press okay select the newly created cron job Click the run button. in the opening window click the start button. It will shortly deactivate and activate again. open ssh or console and login as root with your new password. Root and Admin Password Unknown If you do not know the root password, you need to boot with a Li

Zimbra install let's encrypt

https://inguide.in/how-to-install-free-ssl-certificate-on-zimbra-mail-server/ Je change le domaine ingu.pw In the article Install Zimbra Mail Server o n CentOS 8, we learned to install Zimbra on CentOS. This article discusses the steps required to install the Let’s Encrypt free SSL certificate in Zimbra. Installing Free SSL Certificate on Zimbra: Method 1 This method is a proven one though you have to manually do all the steps. Another method discussed below is partially automatic, which might come in handy if you didn’t encounter any error during installation (working at the time of writing this article). So, let’s begin with method 1. First of all, add epel repository to the server 1 [root@mail ~]# yum -y install epel-release Install snapd Now, install snapd package with the following command 1 [root@mail ~]# sudo yum install snapd After the above step, you need to enable snapd. 1 [root@mail ~]# sudo systemctl enable --now snapd.socket Sometimes, the above command isn’t suffic

cPanel DDOS attack - Mitigate Slowloris Attacks - mod_qos

Apache mod_evasive Mod_evasive is a module available for the Apache HTTP server that can automatically block attacks by rate-limiting any IP that sends too many requests in a short time. Start by installing the module from WHM’s EasyApache 4 interface. Select the Currently Installed Packages profile, search for mod_evasive in the Apache Modules section, and then install it. The default settings are good for most servers, but you can tweak them further by editing the configuration file /etc/apache2/conf.d/300-mod_evasive.conf . You can also whitelist specific IP addresses or classes, so legitimate requests are not blocked. Configure CSF to block attacks While mod_evasive works very well, it only protects the Apache webserver. In order to harden other services as well, you can install the free ConfigServer Security & Firewall (CSF), which also includes a WHM plugin. As the root user, install CSF with these terminal commands: cd /usr/src rm -fv csf.tgz wget https://down

BTK Apprendre et faire apprendre

Rechercher dans ce blog