SSH y Configurar DHCP
ssh
Para acceder a un ordenador (a traveś de consola) desde otro con SO Windows,
instalamos un programa que se llama putty (en www.putty.com)
y al ejecutarlo escribimos la ip del ordenador al que queramos acceder.
Por ejemplo, desde el ordenador de MA (Casa Cultura) accedemos al servidor
colocado en Secretaria (Ayto) , en E\p\ppp\p.exe
alli ponemos la ip del servidor 192.168.100.1
y cuando entramos en consola ponemos
ssh -l root 192.168.100.10
dhcp
Para instalar DHCP en este servidor intermedio para que sea el el que de las ips
de los pc del Ayto.
1 emerge dhcp -pv (para ver si esta o no instalado el dhcp)
(para ver lo de chroot hacemos el emerge dhcp)
2 accedemos al archivo dhcpd.conf (que esta en el directorio
chroot/dhcp/etc/dhcp
En este archivo ponemos varias cosas:
subnet: 192.168.100.0
netmask: 255.255.255.0
range 192.168.100.60 192.168.100.99
name servers: 192.168.100.10
192.168.1.11 (router adsl Casa Cultura)
option routers: 192.168.100.10
broadcast: 192.168.100.255
domainserver: aytomf.local
creamos una funcion:
host prueba {
hardware ethernet (mac del pc MA, en este caso)
fixed address: 192.168.100.150 }
De esta forma al ordenador que tiene esa mac le asignamos la ip concreta, al
resto de ordenadores desconocidos.....se les asigna ip....de la red 1 (la antigua)
Dentro de la subred de ayto antigua poner la clase pool {
rango de ips
unknown clients;
}
Para poder entrar en el servidor 192.168.100.20 hay que cambiar la ip del pc
(en este caso MA) a la siguiente:
ip 192.168.100.102 (xej)
puerta enlace 192.168.100.10
DNS preferida 192.168.1.11 (router casa cultura)
ADDRESS POOLS
The pool declaration can be used to specify a pool of addresses that
will be treated differently than another pool of addresses, even on the
same network segment or subnet. For example, you may want to provide
a large set of addresses that can be assigned to DHCP clients that are
registered to your DHCP server, while providing a smaller set of
addresses, possibly with short lease times, that are available for
unknown clients. If you have a firewall, you may be able to arrange
for addresses from one pool to be allowed access to the Internet, while
addresses in another pool are not, thus encouraging users to register
their DHCP clients. To do this, you would set up a pair of pool dec-
larations:
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.254;
# Unknown clients get this pool.
pool {
option domain-name-servers bogus.example.com;
max-lease-time 300;
range 10.0.0.200 10.0.0.253;
allow unknown-clients;
}
# Known clients get this pool.
pool {
option domain-name-servers ns1.example.com, ns2.example.com;
max-lease-time 28800;
range 10.0.0.5 10.0.0.199;
deny unknown-clients;
}
}
It is also possible to set up entirely different subnets for known and
unknown clients - address pools exist at the level of shared networks,
so address ranges within pool declarations can be on different subnets.
As you can see in the preceding example, pools can have permit lists
that control which clients are allowed access to the pool and which
aren't. Each entry in a pool's permit list is introduced with the
allow or deny keyword. If a pool has a permit list, then only those
clients that match specific entries on the permit list will be eligible
to be assigned addresses from the pool. If a pool has a deny list,
then only those clients that do not match any entries on the deny list
will be eligible. If both permit and deny lists exist for a pool,
then only clients that match the permit list and do not match the deny
list will be allowed access.


