On Fri, 2006-12-15 at 07:12 -0800, Sergio Silva wrote:
> Tenho um servidor fazendo as funções de roteador e DHCP
> ( 192.168.20.252 e 192.168.200.1). Gostaria que somente a rede
> 192.168.200.0 fosse atendida pelo DHCP.
> Já coloquei a opção INTERFACES="eth1" no arquivo /etc/sysconfig/dhcp e
> nãso funcionou.
man dhcpd.conf
search in it for "address" and "listen"
configure listen parameters in /etc/dhcpd.conf
Put your listening address for the server after the local-address
option.
e.g. local-address 192.168.200.255
> No subnet declaration for eth0 (192.168.20.252).
> ** Ignoring requests on eth0. If this is not what
> you want, please write a subnet declaration
> in your dhcpd.conf file for the network segment
> to which interface eth0 is attached. **
e.g. subnet 192.168.200.0 netmask 255.255.255.0
> Can't bind to dhcp address: Address already in use
> Please make sure there is no other dhcp server
> running and that there's no entry for dhcp or
> bootp in /etc/inetd.conf. Also make sure you
> are not running HP JetAdmin software, which
> includes a bootp server.
You might have another DHCP server on your LAN. You have to configure
each to work separately.
You might have another DHCP-like server on the same computer, you'd have
to stop one, or configure them to listen on different interfaces.
Post your /etc/dhcpd.conf file if you need more help.
Here's an example, with *SOME* of your addresses inserted into it, it
might not work for you without some changes:
--------------------------- begin ---------------------------------
authoritative;
allow client-updates;
include "/etc/rndc.key";
default-lease-time 21600; # 2 hours
max-lease-time 43200; # 24 hours
min-lease-time 30; # 30 seconds
server-name "boss";
local-address 192.168.200.255
## DHCP + dynamic DNS server options (next 4 lines)
#ddns-domainname "lan.example.com.";
#ddns-rev-domainname "in-addr.arpa.";
#ddns-update-style interim;
#ddns-updates on;
option domain-name "lan.example.com.";
option ntp-servers lan.example.com;
option ip-forwarding off;
shared-network lan.example.com {
subnet 192.168.200.1 netmask 255.255.255.0 {
range 192.168.2.2 192.168.200.253;
option routers 192.168.200.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.200.255;
option domain-name-servers 192.168.200.1;
## For DHCP + dynamic DNS (next two zone statements)
# zone lan.example.com. {
# primary 192.168.200.1;
# key rndckey;
# }
#
# zone 1.168.192.in-addr.arpa. {
# primary 192.168.200.1;
# key rndckey;
# }
}
}
-------------------------- end -------------------------------
You can delete the # DHCP + dynamic DNS sections if you don't have DHCP
and DNS servers talking to each other. If you do, then write something
like them, without hashes commenting them out.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
