On Mon, 2005-08-29 at 15:26 -0700, Antonio Olivares wrote: > > --- Alexander Dalloz <ad+lists@xxxxxxxxx> wrote: > > > Am Mo, den 29.08.2005 schrieb Antonio Olivares um > > 15:08: > > > > You are using DHCP, so remove what I mark > > > > > [olivares@rio ~]$ cat > > > /etc/sysconfig/network-scripts/ifcfg-eth0 > > > DEVICE=eth0 > > > BOOTPROTO=dhcp > > > BROADCAST=10.154.23.255 delete > > > IPADDR=10.154.17.34 delete > > > NETMASK=255.255.248.0 delete > > > NETWORK=10.154.16.0 delete > > > ONBOOT=yes > > > TYPE=Ethernet > > > HWADDR=00:50:2c:a6:19:28 > > > USERCTL=no > > > PEERDNS=yes > > > GATEWAY=10.154.16.1 delete (even with static IP > > configuration the GATEWAY > > > > setting mostly ever has to be in > > /etc/sysconfig/network) > > > IPV6INIT=no > > > [olivares@rio ~]$ cat /etc/sysconfig/network > > > NETWORKING=yes > > > HOSTNAME=rio > > > > These data are assigned by the DHCP server. Please > > see my other reply: > > not only your IP changed but too the subnet got > > smaller. Maybe the > > gateway changed too, but that should be done > > automatically by receiving > > the IP data from the DHCP server. > > > > Alexander > > > > > > -- > > Alexander Dalloz | Enger, Germany | GPG > > http://pgp.mit.edu 0xB366A773 > > legal statement: http://www.uni-x.org/legal.html > > Fedora Core 2 GNU/Linux on Athlon with kernel > > 2.6.11-1.35_FC2smp > > Serendipity 20:05:16 up 7 days, 16:48, load average: > > 0.05, 0.08, 0.10 > > > -- > > fedora-list mailing list > > fedora-list@xxxxxxxxxx > > To unsubscribe: > http://www.redhat.com/mailman/listinfo/fedora-list > > First of all, I would like to say thanks to Jeff and > Alexander for helping me out with this issue. I have > made the changes suggested but I get a big error > message. I am confused a bit, but the problem is a > smaller one than before. > > [olivares@rio ~]$ cat > /etc/sysconfig/network-scripts/ifcfg-eth0 > DEVICE=eth0 > BOOTPROTO=dhcp > ONBOOT=yes > TYPE=Ethernet > HWADDR=00:50:2c:a6:19:28 > USERCTL=no > PEERDNS=yes > IPV6INIT=no Good, that looks right for a dhcp client. > [olivares@rio ~]$ cat > /etc/sysconfig/network-scripts/ifcfg-eth1 > # 3Com Corporation 3c905 100BaseTX [Boomerang] > DEVICE=eth1 > ONBOOT=yes > BOOTPROTO=dhcp > HWADDR=00:60:97:C5:2A:C3 > NETMASK=255.255.255.0 > USERCTL=yes > PEERDNS=no > GATEWAY=eth0 > TYPE=Ethernet > IPADDR=192.168.100.1 NO. You said this would be a dhcp server for the attached network. You should set a static IP on this interface. BOOTPROTO=none NETWORK=192.168.100.0 BROADCAST=192.168.100.255 Do not set the gateway. That line should be removed (it is invalid anyway). After this, the config for your dhcp server should be the main part that is needed. Make certain the dhcp server is handing out addresses in the 192.168.100 network, and that it ONLY answers to requests on eth1. Your dhcp config should pass the gateway address (this interface), dns server, IP, and netmask (and hostname if you want) to the machines on this subnet. Last, but not least, you will need to set up NAT and ip forwarding so the machines on the eth1 interface will be able to reach the other side of this host and receive replies. > [olivares@rio ~]$ > > [root@rio ~]# service dhcpd start > dhcpd: unrecognized service > [root@rio ~]# kedit & > [1] 4457 > [root@rio ~]# Link points to "/tmp/ksocket-root" > Link points to "/tmp/kde-root" > kbuildsycoca running... > Reusing existing ksycoca > [root@rio ~]# route -n > Kernel IP routing table > Destination Gateway Genmask Flags > Metric Ref Use Iface > 192.168.100.0 0.0.0.0 255.255.255.0 U > 0 0 0 eth1 > 10.154.19.0 0.0.0.0 255.255.255.0 U > 0 0 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U > 0 0 0 eth0 > 0.0.0.0 10.154.19.1 0.0.0.0 UG > 0 0 0 eth0 Good, only one subnet on eth1, and the default route on eth0 > [root@rio ~]# rpm -qa | grep dhcp > dhcpv6_client-0.10-8 > [root@rio ~]# route add -host 255.255.255.255 dev eth1 > [root@rio ~]# cat /etc/dhcpd.conf > # > # Global Settings > # > > # Turn on Dynamic DNS: > ddns-domainname "domain.lan"; > ddns-update-style interim; > ddns-updates on; > > # Don't allow clients to update DNS, make the server > do it > # based on the hostname passed by the DHCP client: > deny client-updates; > allow unknown-clients; > > # > # 10.0.0.0/255.255.255.0 Scope Settings > # > subnet 10.0.0.0 netmask 255.255.255.0 { > > # Range of DHCP assigned addresses for this > scope > range 10.0.0.100 > 10.0.0.200; > # 1 day > default-lease-time 86400; > # 2 days > max-lease-time 172800; > > # Configure the client's default Gateway: > option subnet-mask 255.255.255.0; > option broadcast-address 10.0.0.255; > option routers 10.0.0.2; > > # Configure the client's DNS settings: > option domain-name "domain.lan"; > option domain-name-servers 10.0.0.1; > You are assigning the interface eth1 an address in the 192.168.100.X network with netmask of 255.255.255.0 You must serve out addresses with the same netmask and network. Something like the following _________________________________________________________ subnet 192.168.100.0 netmask 255.255.255.0 { # Range of DHCP assigned addresses for this scope range 192.168.100.100 192.168.100.200; # 1 day default-lease-time 86400; # 2 days max-lease-time 172800; # Configure the client's default Gateway: option subnet-mask 255.255.255.0; option broadcast-address 192.168.100.255; option routers 192.168.100.1; # Configure the client's DNS settings: option domain-name "domain.lan"; option domain-name-servers XXX.XXX.XXX.XXX; _________________________________________________________ The domain-name-servers will be the same as your host uses for it's own DNS server, thus the client requests will be just passed on through. Or it will be this host and you can run a caching name server for your subnet. That probably is not needed. > }[root@rio ~]# touch /var/state/dhcpd/dhcpd.leases > touch: cannot touch `/var/state/dhcpd/dhcpd.leases': > No such file or directory > [root@rio ~]# cd /var/ > [root@rio var]# ls > account crash empty lib lock mail opt > run tmp > cache db gdm local log nis preserve > spool yp > [root@rio var]# mkdir state > [root@rio var]# cd state/ > [root@rio state]# ls > [root@rio state]# mkdir dhcp > [root@rio state]# cd dhcp/ > [root@rio dhcp]# ls > [root@rio dhcp]# cd .. > [root@rio state]# ls > dhcp > [root@rio state]# cd .. > [root@rio var]# cd .. > [root@rio /]# ls > bin dev home lib media mnt proc sbin > srv tmp var > boot etc initrd lost+found misc opt root > selinux sys usr > [root@rio /]# touch /var/state/dhcpd/dhcpd.leases > touch: cannot touch `/var/state/dhcpd/dhcpd.leases': > No such file or directory > [root@rio /]# touch /var/state/dhcp/dhcpd.leases > [root@rio /]# cd /usr/sbin/ > [root@rio sbin]# dhcpd -d -f > -bash: dhcpd: command not found > [root@rio sbin]# dhcp -d -f > -bash: dhcp: command not found > [root@rio sbin]# cd /home/olivares/ > [root@rio olivares]# ls > c dhcp-3.0.1-44_FC3.i386.rpm Downloads > netbeans-4.0 > c.0502161545 Documents > Firefox_wallpaper.png tmp > Desktop Documents.tar.gz j2re1.4.2_06 > vpd.properties > [root@rio olivares]# rpm -ivh > dhcp-3.0.1-44_FC3.i386.rpm > warning: dhcp-3.0.1-44_FC3.i386.rpm: V3 DSA signature: > NOKEY, key ID 4f2a6fd2 > Preparing... > ########################################### [100%] > 1:dhcp > ########################################### [100%] > [root@rio olivares]# dhcpd -d -f > [root@rio olivares]# chkconfig dhcpd on > > running system-config-services, I got the following > message. > > ------------------------------------------------------- > > dhcpd failed. The error was: Starting dhcpd: Internet > Systems Consortium DHCP Server V3.0.1 > Copyright 2004 Internet Systems Consortium. > All rights reserved. > For info, please visit http://www.isc.org/sw/dhcp/ > Wrote 0 leases to leases file. > > No subnet declaration for eth1 (192.168.100.1). > ** Ignoring requests on eth1. If this is not what > you want, please write a subnet declaration > in your dhcpd.conf file for the network segment > to which interface eth1 is attached. ** > > > No subnet declaration for eth0 (10.154.19.136). > ** 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. ** > > > Not configured to listen on any interfaces! > You MUST not allow dhcp communications on eth0 since that network already has a dhcp server. > If you did not get this software from ftp.isc.org, > please > get the latest from ftp.isc.org and install that > before > requesting help. > > If you did get this software from ftp.isc.org and have > not > yet read the README, please read it before requesting > help. > If you intend to request help from the > dhcp-server@xxxxxxx > mailing list, please read the section on the README > about > submitting bug reports and requests for help. > > Please do not under any circumstances send requests > for > help directly to the authors of this software - please > send them to the appropriate mailing list as described > in > the README file. > > exiting. > [FAILED] > > > Best Regards, > > Antonio > > HTH Jeff
