yann.lereuille/siotp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Ajout des fichiers configs dhcp et dns avec la carte réseau

Browse Source
This commit is contained in:
yann.lereuille 2025-02-17 09:31:55 +01:00
parent 6e4a091d0a
commit b48e82f549
7 changed files with 252 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
sisr1/tp03-reseau-prive/srv-service/carte_reseau/interfaces Normal file
View File

@ -0,0 +1,17 @@
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug enp0s3
#iface enp0s3 inet dhcp
auto enp0s3
iface enp0s3 inet static
address 172.16.0.2/24
gateway 172.16.0.1

115
sisr1/tp03-reseau-prive/srv-service/dhcp/dhcpd.conf Normal file
View File

@ -0,0 +1,115 @@
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
#log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
subnet 172.16.0.0 netmask 255.255.255.0 {
range 172.16.0.50 172.16.0.149;
#option broadcast-address 10.254.239.31;
option routers 172.16.0.1;
option domain-name-servers 172.16.0.2, 172.16.0.3;
option domain-name "monlabo.lan";
}
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.example.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
host srv-admin-yl {
hardware ethernet 08:00:27:b8:da:8b;
fixed-address 172.16.0.1;
}
host srv-dns2 {
hardware ethernet 08:00:27:95:ad:90;
fixed-address 172.16.0.3;
}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}

18
sisr1/tp03-reseau-prive/srv-service/dhcp/isc-dhcp-server Normal file
View File

@ -0,0 +1,18 @@
# Defaults for isc-dhcp-server (sourced by /etc/init.d/isc-dhcp-server)
# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
#DHCPDv4_CONF=/etc/dhcp/dhcpd.conf
#DHCPDv6_CONF=/etc/dhcp/dhcpd6.conf
# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
#DHCPDv4_PID=/var/run/dhcpd.pid
#DHCPDv6_PID=/var/run/dhcpd6.pid
# Additional options to start dhcpd with.
# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
#OPTIONS=""
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="enp0s3"
INTERFACESv6=""

28
sisr1/tp03-reseau-prive/srv-service/dns/db.monlabo.lan Normal file
View File

@ -0,0 +1,28 @@
;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA srv-service.monlabo.lan. root.monlabo.lan. (
2 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
NS srv-service.monlabo.lan.
NS srv-dns2.monlabo.lan.
srv-service.monlabo.lan. A 172.16.0.2
srv-dns2.monlabo.lan. A 172.16.0.3
srv-admin-yl.monlabo.lan. A 172.16.0.1
srvdhcp IN CNAME srv-service.monlabo.lan.
dhcp IN CNAME srv-service.monlabo.lan.
srvdns IN CNAME srv-service.monlabo.lan.
srvdns1 IN CNAME srv-service.monlabo.lan.
srvdns2 IN CNAME srv-dns2.monlabo.lan.
dns1 IN CNAME srv-service.monlabo.lan.
dns IN CNAME srv-service.monlabo.lan.
dns2 IN CNAME srv-dns2.monlabo.lan.
srvadmin IN CNAME srv-admin-yl.monlabo.lan.
router IN CNAME srv-admin-yl.monlabo.lan.
gateway IN CNAME srv-admin-yl.monlabo.lan.

30
sisr1/tp03-reseau-prive/srv-service/dns/db.monlabo.lan.rev Normal file
View File

@ -0,0 +1,30 @@
;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA srv-service.monlabo.lan. root.srv-service.monlabo.lan. (
2 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
NS srv-service.monlabo.lan.
NS srv-dns2.monlabo.lan.
3 IN PTR srv-dns2.monlabo.lan.
1 IN PTR srv-admin-yl.monlabo.lan.
2 IN PTR srv-service.monlabo.lan.
srvdhcp IN CNAME srv-service.monlabo.lan.
dhcp IN CNAME srv-service.monlabo.lan.
srvdns IN CNAME srv-service.monlabo.lan.
srvdns1 IN CNAME srv-service.monlabo.lan.
srvdns2 IN CNAME srv-dns2.monlabo.lan.
dns1 IN CNAME srv-service.monlabo.lan.
dns IN CNAME srv-service.monlabo.lan.
dns2 IN CNAME srv-dns2.monlabo.lan.
srvadmin IN CNAME srv-admin-yl.monlabo.lan.
router IN CNAME srv-admin-yl.monlabo.lan.
gateway IN CNAME srv-admin-yl.monlabo.lan.

20
sisr1/tp03-reseau-prive/srv-service/dns/named.conf.local Normal file
View File

@ -0,0 +1,20 @@
//
// Do any local configuration here
// zone directe
zone "monlabo.lan" {
type master;
file "/etc/bind/db.monlabo.lan";
};
// zone inverse
zone "0.16.172.in-addr.arpa" {
type master;
notify no;
file "etc/bind/db.monlabo.lan.rev";
};
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

24
sisr1/tp03-reseau-prive/srv-service/dns/named.conf.options Normal file
View File

@ -0,0 +1,24 @@
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
forwarders {
10.121.38.7; //DNS lycée
};
//========================================================================
// If BIND logs error messages about the root key being expired,
// you will need to update your keys. See https://www.isc.org/bind-keys
//========================================================================
dnssec-validation no;
listen-on-v6 { any; };
};