Uncategorized

Realització de backups​ El qe farem per fer la realitzacio de backup sera fer-ho amb un script ja que com no hi han 

Infrastructura Configuració de xarxa dinàmica per clients des del DHCP Click Configuració de xarxa estàtica per servidors des del DHCP Click Configuració d’un master DNS per la resolució del domini propi Click Configuració d’un slave DNS per la resolució del domini propi Click Resolució de noms per clients dinàmica (DNS-DHCP) Click

Makrosoft Laboratori de treball Click Infraestructura de serveis Click Pla de protecció Click Servei de Directori Click Unitat de xarxa Click Configuració clients Click Còpies de seguretat Click Servidor de correu electrònic Click

Configuració de xarxa estàtica per servidors des del DHCP Per fer la configuració d’una xarxa estàtica pels servidors, des de la torre DCHP, el primer que haurem de fer serà accedir l’arxiu de configuració. sudo vi /etc/dhcp/dhcpd.conf I ara una vegada dintre afegirem aquestes lineas per fer que els nostres servidors w2k19 server, i Debian per aconseguir que la nostra màquina tingui la IP fixa pels servidor # w2k19 host puerto-5 { hardware ethernet 08:00:27:A5:3B:27; <–Mac de la vostre maquina fixed-address 192.168.100.133; <– Ip que es quedara aquesta maquina de manera fixa } # Debian host puerto-7 { hardware ethernet 08:00:27:87:18:A5; <–Mac de la vostre maquina fixed-address 192.168.100.134; <– Ip que es quedara aquesta maquina de }

Configuració de xarxa estàtica per servidors des del DHCP

Configuració de xarxa dinàmica per clients des del DHCP Per a la configuració de l’assignació dinàmica d’adreces IP mitjançant DHCP a cada subxarxa (VLAN), s’ha utilitzat la directiva range. Aquesta línia especifica el grup d’IPs que el servidor DHCP pot concedir als clients, deixant adreces lliures fora d’aquest rang per a l’assignació d’IPs estàtiques (fixes). Per exemple, per a la VLAN 40, la línia range 192.168.100.130 192.168.100.142; defineix l’àmbit dinàmic. D’aquesta manera, es reserva l’adreça 192.168.100.129 per al router (passarel·la o gateway) i es deixen lliures les adreces des de la 192.168.100.143 fins a la 192.168.100.158 per al seu ús estàtic en servidors o evitant conflictes amb la distribució automàtica. Per fer aquesta configuracio ho farem dintre d’aquest arxiu  sudo vi /etc/dhcp/dhcpd.conf I dintre d’aquest arxiu afegirem aquesta configuració en el nostre arxiu. # VLAN 40 subnet 192.168.100.128 netmask 255.255.255.240 { range 192.168.100.130 192.168.100.142; option routers 192.168.100.129; }

SAI 1. Política de l’empresa

Compartició de claus SSH amb la pasarel·la El primer pass serà, compartir des de les nostres màquines, a la passerella, per fer-ho o farem amb la següent comanda, això ho farem des de totes les màquines dels companys del grup. ssh-copy-id usuari_passarella@ip_passarella Resultat de la comanda [08:39:28][~][agarcia@agarcia]-$ ssh-copy-id grup3@172.25.205.12 /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed — if you are prompted now it is to install the new keys grup3@172.25.205.12's password: Number of key(s) added: 1 Now try logging into the machine, with: "ssh 'grup3@172.25.205.12'" and check to make sure that only the key(s) you wanted were added. [08:54:11][~][agarcia@agarcia]-$ Ara una vegada ja compartida des de les nostres màquines, el que ens faltarà serà des de la passerella fer la compartició a les nostres màquines, per fer-ho ser aigual que l’anterior comanda però canviant l’usuari i la IP, i això ho faré a tots els usuaris dels membres del grup. ssh-copy-id usuari_membre@ip_membre Resultat de la comanda grup3@debian:~$ ssh-copy-id agarcia@192.168.100.2 /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/home/grup3/.ssh/id_rsa.pub" /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed — if you are prompted now it is to install the new keys agarcia@192.168.100.2's password: Number of key(s) added: 1 Now try logging into the machine, with: "ssh 'agarcia@192.168.100.2'" and check to make sure that only the key(s) you wanted were added.

Desplegament amb vagrant El nostre codi del vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure("2") do |config| config.vm.define "debian" do |demo| demo.vm.box = "debian" demo.vm.network "public_network", :bridge => "eth0", :adapter => 2 demo.vm.provider "virtualbox" do |vb| vb.gui = false vb.memory = "512" end end end Vagrant.configure("2") do |config| config.vm.define "ubuntu" do |demo| demo.vm.box = "ubuntu" demo.vm.network "public_network", :bridge => "eth0", :adapter => 2 demo.vm.provider "virtualbox" do |vb| vb.gui = false vb.memory = "512" end end end Vagrant.configure("2") do |config| config.vm.define "rocky" do |demo| demo.vm.box = "rocky" demo.vm.network "public_network", :bridge => "eth0", :adapter => 2 demo.vm.provider "virtualbox" do |vb| vb.gui = false vb.memory = "512" end end end Vagrant.configure("2") do |config| config.vm.define "w10" do |demo| demo.vm.box = "w10" demo.vm.communicator = "winrm" demo.winrm.username = "vagrant" demo.winrm.password = "vagrant" demo.vm.network "public_network", :bridge => "eth0", :adapter => 2 demo.vm.provider "virtualbox" do |vb| vb.gui = false vb.memory = "2048" end end end Vagrant.configure("2") do |config| config.vm.define "w2k19" do |demo| demo.vm.box = "w2k19" demo.vm.communicator = "winrm" demo.winrm.username = "vagrant" demo.winrm.password = "vagrant" demo.vm.provider "virtualbox" do |vb| demo.vm.network "public_network", :bridge => "eth0", :adapter => 2 vb.gui = false vb.memory = "2042" end end end Alberto Jo tindre a la meva màquina tindre el servidor, és a dir el w2k19, i la Debian, i faré una comprovació fent un vagrant up amb el Vagrantfile del grup. w2k19 [09:49:12][test][agarcia@agarcia]-$ vagrant up w2k19 Bringing machine 'w2k19' up with 'virtualbox' provider… ==> w2k19: Clearing any previously set forwarded ports… ==> w2k19: Clearing any previously set network interfaces… ==> w2k19: Preparing network interfaces based on configuration… w2k19: Adapter 1: nat w2k19: Adapter 2: bridged ==> w2k19: Forwarding ports… w2k19: 5985 (guest) => 55985 (host) (adapter 1) w2k19: 5986 (guest) => 55986 (host) (adapter 1) w2k19: 22 (guest) => 2222 (host) (adapter 1) ==> w2k19: Running 'pre-boot' VM customizations… ==> w2k19: Booting VM… ==> w2k19: Waiting for machine to boot. This may take a few minutes… w2k19: WinRM address: 127.0.0.1:55985 w2k19: WinRM username: vagrant w2k19: WinRM execution_time_limit: PT2H w2k19: WinRM transport: negotiate ==> w2k19: Machine booted and ready! ==> w2k19: Checking for guest additions in VM… ==> w2k19: Configuring and enabling network interfaces… ==> w2k19: Mounting shared folders… w2k19: /home/agarcia/Documents/test => /vagrant ==> w2k19: Machine already provisioned. Run `vagrant provision` or use the `–provision` ==> w2k19: flag to force provisioning. Provisioners marked to run always will still run. Debian [09:50:34][test][agarcia@agarcia]-$ vagrant up debian Bringing machine 'debian' up with 'virtualbox' provider… ==> debian: Clearing any previously set forwarded ports… ==> debian: Fixed port collision for 22 => 2222. Now on port 2200. ==> debian: Clearing any previously set network interfaces… ==> debian: Preparing network interfaces based on configuration… debian: Adapter 1: nat debian: Adapter 2: bridged ==> debian: Forwarding ports… debian: 22 (guest) => 2200 (host) (adapter 1) ==> debian: Running 'pre-boot' VM customizations… ==> debian: Booting VM… ==> debian: Waiting for machine to boot. This may take a few minutes… debian: SSH address: 127.0.0.1:2200 debian: SSH username: vagrant debian: SSH auth method: private key ==> debian: Machine booted and ready! ==> debian: Checking for guest additions in VM… debian: The guest additions on this VM do not match the installed version of debian: VirtualBox! In most cases this is fine, but in rare cases it can debian: prevent things such as shared folders from working properly. If you see debian: shared folder errors, please make sure the guest additions within the debian: virtual machine match the version of VirtualBox you have installed on debian: your host and reload your VM. debian: debian: Guest Additions Version: 6.0.0 r127566 debian: VirtualBox Version: 7.2 ==> debian: Configuring and enabling network interfaces… ==> debian: Mounting shared folders… debian: /home/agarcia/Documents/test => /vagrant ==> debian: Machine already provisioned. Run `vagrant provision` or use the `–provision` ==> debian: flag to force provisioning. Provisioners marked to run always will still run. Adrian El Adrian a la seva màquina tindrà les maquinés usuaris, és a dir la w10, Rocky, Ubuntu, i farem una comprovació del vagant up. W10 [10:37:53][Box][alopez@alopez]-$ vagrant up w10 Bringing machine 'w10' up with 'virtualbox' provider… ==> w10: Clearing any previously set forwarded ports… ==> w10: Clearing any previously set network interfaces… ==> w10: Preparing network interfaces based on configuration… w10: Adapter 1: nat w10: Adapter 2: bridged ==> w10: Forwarding ports… w10: 5985 (guest) => 55985 (host) (adapter 1) w10: 5986 (guest) => 55986 (host) (adapter 1) w10: 22 (guest) => 2222 (host) (adapter 1) ==> w10: Running 'pre-boot' VM customizations… ==> w10: Booting VM… ==> w10: Waiting for machine to boot. This may take a few minutes… w10: WinRM address: 127.0.0.1:55985 w10: WinRM username: vagrant w10: WinRM execution_time_limit: PT2H w10: WinRM transport: negotiate ==> w10: Machine booted and ready! ==> w10: Checking for guest additions in VM… ==> w10: Configuring and enabling network interfaces… ==> w10: Mounting shared folders… w10: /home/alopez/Documents => /vagrant ==> w10: Machine already provisioned. Run vagrant provision or use the –provision ==> w10: flag to force provisioning. Provisioners marked to run always will still run. Rocky [10:42:21][Box][alopez@alopez]-$ vagrant up rocky Bringing machine 'rocky' up with 'virtualbox' provider… ==> rocky: Clearing any previously set forwarded ports… ==> rocky: Fixed port collision for 22 => 2222. Now on port 2201. ==> rocky: Clearing any previously set network interfaces… ==> rocky: Preparing network interfaces based on configuration… rocky: Adapter 1: nat rocky: Adapter 2: bridged ==> rocky: Forwarding ports… rocky: 22 (guest) => 2201 (host) (adapter 1) ==> rocky: Running 'pre-boot' VM customizations… ==> rocky: Booting VM… ==> rocky: Waiting for machine to boot. This may take a few minutes… rocky: SSH address: 127.0.0.1:2201 Ubuntu [10:40:53][Box][alopez@alopez]-$ vagrant up ubuntu Bringing machine 'ubuntu' up with 'virtualbox' provider… ==> ubuntu: Clearing any previously set forwarded ports… ==> ubuntu: Fixed port collision for 22 => 2222. Now on port 2200. ==> ubuntu: Clearing any previously set network interfaces… ==> ubuntu: Preparing network interfaces based on configuration… ubuntu: Adapter 1: nat ubuntu: Adapter 2: bridged ==> ubuntu: Forwarding ports… ubuntu: 22 (guest) => 2200 (host) (adapter 1) ==> ubuntu: Running 'pre-boot' VM customizations… ==> ubuntu: … Read more

Assignació de MVs a cada integrant Per aquest repte hem de fer l’assignació de funcions, i responsables de qui tindrà les mv, hem fet la repartició de les 4 Vlans assignant 1 per cada membre del grup. Vlan Responable Us Contingut 1 VLAN Jan Clients Ubuntu, Rocky i W10. 2 VLAN Adrian Laboratori Ubuntu, Rocky i W10. 3 VLAN 4 VLAN Alberto Server w2k19, Debian