Re: Make a DHCP server using Fedora - Help
--- On Mon, 11/17/08, Marko Vojinovic [EMAIL PROTECTED] wrote: From: Marko Vojinovic [EMAIL PROTECTED] Subject: Re: Make a DHCP server using Fedora - Help To: [EMAIL PROTECTED], fedora-list@redhat.com Cc: [EMAIL PROTECTED] Date: Monday, November 17, 2008, 10:49 AM Ok, it seems we are getting somewhere. :-) Nov 17 07:27:07 localhost dhcpd: Wrote 0 leases to leases file. Nov 17 07:27:07 localhost dhcpd: Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24 Nov 17 07:27:07 localhost dhcpd: Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24 Nov 17 07:27:07 localhost dhcpd: Sending on Socket/fallback/fallback-net Nov 17 07:31:06 localhost dhcpd: DHCPINFORM from 10.154.19.25 via eth0 Nov 17 07:31:06 localhost dhcpd: DHCPACK to 10.154.19.25 (00:19:b9:10:16:92) via eth0 This is normal, dhcpd is active and running, listens to all devices and does nothing on eth0, as configured. The eth1 is a problem, but not related to dhcpd. [EMAIL PROTECTED] ~]# dhcpd -f There is no need to start it explicitly. The service dhcpd restart should be enough. [EMAIL PROTECTED] ~]# cat /etc/sysconfig/dhcpd DHCPDARGS= This is ok. [EMAIL PROTECTED] ~]# ls /etc/sysconfig/network-scripts/ifcfg-eth* -l -rw-r--r-- 3 root root 130 2007-04-03 12:36 /etc/sysconfig/network-scripts/ifcfg-eth0 I see. There is no ifcfg-eth1. [EMAIL PROTECTED] ~]# ifconfig -a eth1 Link encap:Ethernet HWaddr 00:60:97:C5:2A:C3 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:18 Base address:0xdf00 And this tells it all. The eth1 is not configured and running. I also wonder if I should have a ifcfg-eth1 file in /etc/sysconfig/network-scripts/ Yes, definitely. The system-config-network gui should create it for you. Open it, and see if eth1 is listed in the Devices tab. If not, click New to create it (follow the wizard). Then click Edit to edit its configuration: In the General tab: * Activate the device when computer starts --- should be the only checked option, everything else should be *unchecked* * Activate the static IP settings: * Address: 192.168.0.1 * Subnet mask: 255.255.255.0 * Gateway: leave empty for now In the Hardware Device tab: * Hardware: eth1 * Device alias --- unchecked * Bind to MAC --- checked * Hit the probe button and make sure the MAC is 00:60:97:C5:2A:C3 (don't type it yourself, the button should fill it for you). Click OK to close the window and return to the main one. In the File menu choose Save to save the new configuration. Close the gui. Go to /etc/sysconfig/network-scripts/ and verify that there exists an ifcfg-eth1 file, with the contents like the following: TYPE=Ethernet DNS1=10.154.16.130 DEVICE=eth1 BOOTPROTO=none NETMASK=255.255.255.0 IPADDR=192.168.0.1 DNS2=10.128.0.4 ONBOOT=yes USERCTL=no PEERDNS=yes IPV6INIT=no NM_CONTROLLED=no If this is ok, do a service network restart followed by the service dhcpd restart. Post the output of ifconfig and tail -f /var/log/messages. This should do it (hopefully), if you have no hardware/driver problems with the eth1 card. Also, verify that the cable is connected into eth1, that the led light is on, that the corresponding light on the switch is also on, etc. In other words, make sure that the hardware part of the setup is ok. HTH, :-) Marko I am making the changes and I am seeing new things :) [EMAIL PROTECTED] ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1 # Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] DEVICE=eth1 HWADDR=00:60:97:c5:2a:c3 BOOTPROTO=none IPADDR=192.168.0.1 ONBOOT=yes USERCTL=no PEERDNS=yes IPV6INIT=no NM_CONTROLLED=no TYPE=Ethernet [EMAIL PROTECTED] ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0E:A6:42:59:AF inet addr:10.154.19.210 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::20e:a6ff:fe42:59af/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2535 errors:0 dropped:0 overruns:0 frame:0 TX packets:1985 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1074701 (1.0 MiB) TX bytes:401481 (392.0 KiB) Interrupt:22 Base address:0x6000 eth1 Link encap:Ethernet HWaddr 00:60:97:C5:2A:C3 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::260:97ff:fec5:2ac3/64 Scope:Link
Re: Make a DHCP server using Fedora - Help
--- On Wed, 11/19/08, Antonio Olivares [EMAIL PROTECTED] wrote: From: Antonio Olivares [EMAIL PROTECTED] Subject: Re: Make a DHCP server using Fedora - Help To: fedora-list@redhat.com, [EMAIL PROTECTED] Date: Wednesday, November 19, 2008, 5:24 AM --- On Tue, 11/18/08, Marko Vojinovic [EMAIL PROTECTED] wrote: From: Marko Vojinovic [EMAIL PROTECTED] Subject: Re: Make a DHCP server using Fedora - Help To: fedora-list@redhat.com Cc: [EMAIL PROTECTED] Date: Tuesday, November 18, 2008, 3:14 PM On Monday 17 November 2008 18:49, Marko Vojinovic wrote: I also wonder if I should have a ifcfg-eth1 file in /etc/sysconfig/network-scripts/ Yes, definitely. The system-config-network gui should create it for you. Open it, and see if eth1 is listed in the Devices tab. If not, click New to create it (follow the wizard). Then click Edit to edit its configuration: In the General tab: * Activate the device when computer starts --- should be the only checked option, everything else should be *unchecked* * Activate the static IP settings: * Address: 192.168.0.1 * Subnet mask: 255.255.255.0 * Gateway: leave empty for now In the Hardware Device tab: * Hardware: eth1 * Device alias --- unchecked * Bind to MAC --- checked * Hit the probe button and make sure the MAC is 00:60:97:C5:2A:C3 (don't type it yourself, the button should fill it for you). Click OK to close the window and return to the main one. In the File menu choose Save to save the new configuration. Close the gui. Go to /etc/sysconfig/network-scripts/ and verify that there exists an ifcfg-eth1 file, with the contents like the following: TYPE=Ethernet DNS1=10.154.16.130 DEVICE=eth1 BOOTPROTO=none NETMASK=255.255.255.0 IPADDR=192.168.0.1 DNS2=10.128.0.4 ONBOOT=yes USERCTL=no PEERDNS=yes IPV6INIT=no NM_CONTROLLED=no If this is ok, do a service network restart followed by the service dhcpd restart. Post the output of ifconfig and tail -f /var/log/messages. This should do it (hopefully), if you have no hardware/driver problems with the eth1 card. Also, verify that the cable is connected into eth1, that the led light is on, that the corresponding light on the switch is also on, etc. In other words, make sure that the hardware part of the setup is ok. HTH, :-) Marko Did you manage to do what I described? Yes, It is very close to working. The machines get an IP, get DNS, but cannot browse. Thank you for your guidance, and patience. Nov 19 07:02:23 localhost dhcpd: DHCPDISCOVER from 00:d0:b7:c1:09:58 via eth1 Nov 19 07:02:24 localhost dhcpd: DHCPOFFER on 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 07:02:24 localhost dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.1) from 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 07:02:24 localhost dhcpd: DHCPACK on 192.168.0.2 to 00:d0:b7:c1:09:58 (6355-hthhzebqqx) via eth1 Nov 19 07:02:26 localhost dhcpd: DHCPDISCOVER from 00:11:2f:35:88:2e via eth1 Nov 19 07:02:27 localhost dhcpd: DHCPOFFER on 192.168.0.3 to 00:11:2f:35:88:2e via eth1 Nov 19 07:02:27 localhost dhcpd: DHCPREQUEST for 192.168.0.3 (192.168.0.1) from 00:11:2f:35:88:2e via eth1 Nov 19 07:02:27 localhost dhcpd: DHCPACK on 192.168.0.3 to 00:11:2f:35:88:2e via eth1 Nov 19 07:03:16 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:03:16 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Nov 19 07:03:21 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:03:21 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Nov 19 07:04:53 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:04:53 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Nov 19 07:04:57 localhost dhcpd: DHCPINFORM from 192.168.0.2 via eth1 Nov 19 07:04:57 localhost dhcpd: DHCPACK to 192.168.0.2 (00:d0:b7:c1:09:58) via eth1 Regards, Antonio :-) Marko -- BTW, I am getting DHCP requests from other machines in the school network :( I only want the network for my own machines in the classroom not the others. Here's what I am getting Nov 19 07:14:27 localhost dhcpd
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote: No, there is DNS, and they are the same as the host machine. It might be another little thing, maybe the packet forwarding or Iptables stuff? Thank you very much for your guidance :) It is much closer than before. You have to deal with routing and NAT somewhere. You might avoid it if you run a nameserver and squid proxy on the host and configure the clients to use the proxy. Otherwise you need the host to route the packets if you have a NAT gateway elsewhere, or to route and NAT if nothing but the host knows about this subnet. -- Les Mikesell [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote: BTW, I am getting DHCP requests from other machines in the school network :( I only want the network for my own machines in the classroom not the others. Here's what I am getting Nov 19 07:14:27 localhost dhcpd: DHCPDISCOVER from 00:50:2c:a2:23:28 via eth0: network 10.154.19.0/24: no free leases Nov 19 07:14:27 localhost dhcpd: DHCPREQUEST for 10.154.19.248 (10.154.16.130) from 00:50:2c:a2:23:28 via eth0: unknown lease 10.154.19.248. Nov 19 07:18:50 localhost ntpd[2082]: synchronized to 72.249.76.84, stratum 2 Nov 19 07:24:25 localhost dhcpd: DHCPREQUEST for 10.154.19.94 from 00:40:f4:ea:ee:d3 via eth0: unknown lease 10.154.19.94. Nov 19 07:25:34 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 19 07:25:34 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 19 07:25:37 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 19 07:25:37 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 19 07:26:51 localhost dhcpd: DHCPREQUEST for 10.154.19.133 from 00:0c:f1:76:fc:68 via eth0: unknown lease 10.154.19.133. Nov 19 07:27:25 localhost dhcpd: DHCPINFORM from 10.154.19.165 via eth0 Nov 19 07:27:25 localhost dhcpd: DHCPACK to 10.154.19.165 (00:08:74:2e:70:e7) via eth0 Nov 19 07:27:28 localhost dhcpd: DHCPINFORM from 10.154.19.165 via eth0 Nov 19 07:27:28 localhost dhcpd: DHCPACK to 10.154.19.165 (00:08:74:2e:70:e7) via eth0 Nov 19 07:30:08 localhost dhcpd: DHCPINFORM from 10.154.19.63 via eth0 Nov 19 07:30:08 localhost dhcpd: DHCPACK to 10.154.19.63 (00:12:3f:31:8d:b4) via eth0 Nov 19 07:30:11 localhost dhcpd: DHCPINFORM from 10.154.19.63 via eth0 Nov 19 07:30:11 localhost dhcpd: DHCPACK to 10.154.19.63 (00:12:3f:31:8d:b4) via eth0 Nov 19 07:32:38 localhost dhcpd: DHCPINFORM from 10.154.19.133 via eth0 Nov 19 07:32:38 localhost dhcpd: DHCPACK to 10.154.19.133 (00:0c:f1:76:fc:68) via eth0 Nov 19 07:33:57 localhost dhcpd: DHCPDISCOVER from 00:08:a1:0f:53:35 via eth0: network 10.154.19.0/24: no free leases Nov 19 07:33:57 localhost dhcpd: DHCPREQUEST for 10.154.19.91 (10.154.16.130) from 00:08:a1:0f:53:35 via eth0: unknown lease 10.154.19.91. Nov 19 07:34:13 localhost dhcpd: DHCPINFORM from 10.154.19.91 via eth0 Nov 19 07:34:13 localhost dhcpd: DHCPACK to 10.154.19.91 (00:08:a1:0f:53:35) via eth0 Nov 19 07:34:16 localhost dhcpd: DHCPINFORM from 10.154.19.91 via eth0 Nov 19 07:34:16 localhost dhcpd: DHCPACK to 10.154.19.91 (00:08:a1:0f:53:35) via eth0 Thank you very much again for helping out. Your client subnet should be physically isolated from rest of the building's network. That is, the host should have one interface on the main net and another connected to a separate switch where your dhcp clients connect. You will break the rest of the main network if you connect your dhcp-serving interface there. -- Les Mikesell [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Wed, 11/19/08, Les Mikesell [EMAIL PROTECTED] wrote: From: Les Mikesell [EMAIL PROTECTED] Subject: Re: Make a DHCP server using Fedora - Help To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Date: Wednesday, November 19, 2008, 5:55 AM Antonio Olivares wrote: No, there is DNS, and they are the same as the host machine. It might be another little thing, maybe the packet forwarding or Iptables stuff? Thank you very much for your guidance :) It is much closer than before. You have to deal with routing and NAT somewhere. You might avoid it if you run a nameserver and squid proxy on the host and configure the clients to use the proxy. Otherwise you need the host to route the packets if you have a NAT gateway elsewhere, or to route and NAT if nothing but the host knows about this subnet. -- Les Mikesell [EMAIL PROTECTED] I added the following and saved them iptables-save upon reading another page: http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html it says iptables and has this part: # Forward all packets from eth1 (internal network) to eth0 (the public internet) iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT # Forward packets that are part of existing and related connections from eth0 to eth1 iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT # Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0 iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a. I added everything here except last line Enable SNAT, I do not know what that means, I know it is close. I can ping the host machine, it gets an ip, it gets DNS, and all, but cannot surf :( Thanks, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote: --- On Wed, 11/19/08, Les Mikesell [EMAIL PROTECTED] wrote: From: Les Mikesell [EMAIL PROTECTED] Subject: Re: Make a DHCP server using Fedora - Help To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Date: Wednesday, November 19, 2008, 5:55 AM Antonio Olivares wrote: No, there is DNS, and they are the same as the host machine. It might be another little thing, maybe the packet forwarding or Iptables stuff? Thank you very much for your guidance :) It is much closer than before. You have to deal with routing and NAT somewhere. You might avoid it if you run a nameserver and squid proxy on the host and configure the clients to use the proxy. Otherwise you need the host to route the packets if you have a NAT gateway elsewhere, or to route and NAT if nothing but the host knows about this subnet. -- Les Mikesell [EMAIL PROTECTED] I added the following and saved them iptables-save upon reading another page: http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html The advice to add: net.ipv4.ip_forward = 1 to /etc/sysctl.conf only takes effect after the next reboot. If you want to change this on the fly you can: echo 1 /proc/sys/net/ipv4/ip_forward it says iptables and has this part: # Forward all packets from eth1 (internal network) to eth0 (the public internet) iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT # Forward packets that are part of existing and related connections from eth0 to eth1 iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT # Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0 iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a. I added everything here except last line Enable SNAT, I do not know what that means, I know it is close. I can ping the host machine, it gets an ip, it gets DNS, and all, but cannot surf :( Anywhere you send packets needs some way to get the response back to the sender. One way to do this is to plan things so all of your private subnets are unique and add routes toward the gateway interfaces for everything else. Another way is to NAT the source address as it goes out the already-known interface. That way the rest of the world does not need to know about your new private subnet. As a packet goes out, the source address of the client will be replaced with the address of the forwarding interface and the host performing this will maintain a table of connections to do the reverse mapping as the reply packets come back. If you tcpdump your eth0 interface now, you'll probably see packets being forwarded out but nothing coming back because the rest of the net/world doesn't know the route back. When you add the SNAT, it will look like the host machine itself to the rest of the world. The argument to -s is the range of original addresses to replace, -o is the outbound interface, and --to-source is the IP of the outbound interface on the host. -- Les Mikesell [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
After this breakthrough I also found out or not sure here? is that iptables are forwarding packets to eth1 upon reading another page: http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html it says iptables and has this part: # Forward all packets from eth1 (internal network) to eth0 (the public internet) iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT # Forward packets that are part of existing and related connections from eth0 to eth1 iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT # Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0 iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a. Then it recommends visiting the other page which was referenced before. I will probably get to this machine tomorrow or on Monday. I hope that I can get this working and with advice from the list I believe it can get done. Regards, Antonio -- I see that the forwarding is not there anymore :( See here: [EMAIL PROTECTED] ~]# cat /etc/sysconfig/iptables # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -p 50 -j ACCEPT -A RH-Firewall-1-INPUT -p 51 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT I can try using system-config-firewall to allow it or how do I do it, I added it manually and then ran iptables-save, but it is not there anymore :( Thank you all for your help, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Mon, 11/17/08, Marko Vojinovic [EMAIL PROTECTED] wrote:
From: Marko Vojinovic [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], fedora-list@redhat.com
Cc: [EMAIL PROTECTED]
Date: Monday, November 17, 2008, 5:13 AM
:-)
I had changed back and forth between eth0 and eth1 and
now it is and
should be eth0 :)
[EMAIL PROTECTED] ~]# cat /etc/sysconfig/dhcpd
DHCPDARGS=eth0
This is probably the culprit at this point... For the setup
I suggested,
this is plain wrong --- it instructs dhcpd to listen only
on eth0, which
is precisely the opposite of what we want (to listen on
eth1 and ignore
eth0).
Either delete the eth0 from the above line, or
change it to eth1.
Restart dhcpd and look at /var/log/messages again.
I did as you suggested and I still cannot connect the
machines to the new
server :(
/etc/dhcpd.conf
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
subnet 10.154.19.0 netmask 255.255.255.0 {
} # this means don't do anything with the big
network
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1; # your server is the
router for classroom
option subnet-mask 255.255.255.0; # the mask given to
classroom
option domain-name-servers 10.154.16.130, 10.128.0.4;
# dns servers
range 192.168.0.2 192.168.0.254; # the pool of
addresses for classroom
}
This is ok (or at least looks that way :-) ).
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:
[ OK ]
Maybe it is safer to do service dhcpd stop and
then service dhcpd
start. The restart version assumes that
dhcpd is already running, which
may not be true...
[EMAIL PROTECTED] ~]#
It starts up but no leases show up, I am trying to
ping computer from
windows 2000 machine and from another machine running
rawhide
No leases show up because dhcpd was wrongly listening
*only* on eth0 in
/etc/sysconfig/dhcpd, while in /etc/dhcpd.conf it is
instructed to give
leases to requests from eth1.
Make sure to set win2k and rawhide machines to configure
their network
settings automatically, ie. using dhcp
protocol.
And just to be sure, post the output of
ifconfig. Dhcpd will not work on
eth1 if it is not set up properly and active...
tail -f /var/log/messages show:
Nov 16 18:56:40 localhost dhcpd: Internet Systems
Consortium DHCP Server
4.0.0
Nov 16 18:56:40 localhost dhcpd: Copyright 2004-2007
Internet Systems
Consortium.
Nov 16 18:56:40 localhost dhcpd: All rights reserved.
Nov 16 18:56:40 localhost dhcpd: For info, please
visit
http://www.isc.org/sw/dhcp/
Nov 16 18:56:40 localhost dhcpd: Not searching LDAP
since ldap-server,
ldap-port and ldap-base-dn were not specified in the
config file
Nov 16 18:56:40 localhost dhcpd: Wrote 0 leases to
leases file.
Nov 16 18:56:40 localhost dhcpd: Listening on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:40 localhost dhcpd: Sending on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:40 localhost dhcpd: Sending on
Socket/fallback/fallback-net
Nov 16 19:06:27 localhost dhcpd: DHCPINFORM from
10.154.19.33 via eth0
Nov 16 19:06:27 localhost dhcpd: DHCPACK to
10.154.19.33
(00:0f:1f:86:fc:70) via eth0
This is again because it was listening to eth0 (and doing
nothing with it).
Make sure to change the line
DHCPDARGS=eth0
into
DHCPDARGS=
in /etc/sysconfig/dhcpd, and try again. :-)
HTH, :-)
Marko
Did that, but still no go :(
Nov 17 07:27:07 localhost dhcpd: Wrote 0 leases to leases file.
Nov 17 07:27:07 localhost dhcpd: Listening on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 17 07:27:07 localhost dhcpd: Sending on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 17 07:27:07 localhost dhcpd: Sending on Socket/fallback/fallback-net
Nov 17 07:31:06 localhost dhcpd: DHCPINFORM from 10.154.19.25 via eth0
Nov 17 07:31:06 localhost dhcpd: DHCPACK to 10.154.19.25 (00:19:b9:10:16:92)
via eth0
Nov 17 07:31:09 localhost dhcpd: DHCPINFORM from 10.154.19.25 via eth0
Nov 17 07:31:09 localhost dhcpd: DHCPACK to 10.154.19.25 (00:19:b9:10:16:92)
via eth0
Nov 17 07:31:27 localhost dhcpd: DHCPINFORM from 10.154.19.14 via eth0
Nov 17 07:31:27 localhost dhcpd: DHCPACK to 10.154.19.14 (00:0f:1f:86:fc:26)
via eth0
Nov 17 07:31:30 localhost dhcpd: DHCPINFORM from 10.154.19.14 via eth0
Nov 17 07:31:30 localhost dhcpd: DHCPACK to 10.154.19.14 (00:0f:1f:86:fc:26)
via eth0
Nov 17 07:32:54 localhost dhcpd: DHCPINFORM from
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote:
--- On Sun, 11/16/08, Marko Vojinovic [EMAIL PROTECTED] wrote:
###
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
...snip...
Save, do a service dhcpd restart (it should say
OK), then
tail -f /var/log/messages and watch what is
going on. Restart the clients
(one by one if you wish to examine /var/log/messages after
each client,
otherwise you may restart them all simultaneously :-)...).
[[ N.B. I suppose you have configured the clients to use
dhcp and not have
anything statically assigned... ]]
What should be going on is that the clients in the
classroom ask for IP
configuration (dhcp request), then dhcpd replies with the
data above (dhcp
offer) and then each client accepts this offer. If all goes
well, up to this
point each client should have a 192.168.0.* IP assigned
dynamically, and be
able to ping any other client with such address, as well as
the server,
192.168.0.1. If this doesn't happen, tell us what does
happen.
...snip...
I did as you suggested and I still cannot connect the machines to the new
server :(
Before even trying to connect, after you reload the dhcpd, do netstat -ta and
look to see if the server is listening (state LISTEN) on the dhcp port.
Also ifconfig eth1 and netstat -rn so we can be sure you did what people
intended you to do.
/etc/dhcpd.conf
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
subnet 10.154.19.0 netmask 255.255.255.0 {
} # this means don't do anything with the big network
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1; # your server is the router for classroom
option subnet-mask 255.255.255.0; # the mask given to classroom
option domain-name-servers 10.154.16.130, 10.128.0.4; # dns servers
range 192.168.0.2 192.168.0.254; # the pool of addresses for classroom
}
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:[ OK ]
[EMAIL PROTECTED] ~]#
It starts up but no leases show up, I am trying to ping computer from windows
2000 machine and from another machine running rawhide
tail -f /var/log/messages show:
Nov 16 18:51:13 localhost ntpd[2004]: kernel time sync status change 4001
Nov 16 18:54:24 localhost dhcpd: DHCPREQUEST for 10.154.19.129 from 00:06:5b:4f:d7:d2 via eth0: unknown lease 10.154.19.129.
Nov 16 18:56:32 localhost dhcpd: Internet Systems Consortium DHCP Server 4.0.0
Nov 16 18:56:32 localhost dhcpd: Copyright 2004-2007 Internet Systems Consortium.
Nov 16 18:56:32 localhost dhcpd: All rights reserved.
Nov 16 18:56:32 localhost dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 16 18:56:32 localhost dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Nov 16 18:56:32 localhost dhcpd: Wrote 0 leases to leases file.
Nov 16 18:56:32 localhost dhcpd: Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:32 localhost dhcpd: Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:32 localhost dhcpd: Sending on Socket/fallback/fallback-net
Nov 16 18:56:40 localhost dhcpd: Internet Systems Consortium DHCP Server 4.0.0
Nov 16 18:56:40 localhost dhcpd: Copyright 2004-2007 Internet Systems Consortium.
Nov 16 18:56:40 localhost dhcpd: All rights reserved.
Nov 16 18:56:40 localhost dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Nov 16 18:56:40 localhost dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Nov 16 18:56:40 localhost dhcpd: Wrote 0 leases to leases file.
Nov 16 18:56:40 localhost dhcpd: Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:40 localhost dhcpd: Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:40 localhost dhcpd: Sending on Socket/fallback/fallback-net
Nov 16 19:06:27 localhost dhcpd:
Re: Make a DHCP server using Fedora - Help
On Sun, 2008-11-16 at 17:13 -0800, Antonio Olivares wrote: Nov 16 19:06:27 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0 Nov 16 19:06:27 localhost dhcpd: DHCPACK to 10.154.19.33 (00:0f:1f:86:fc:70) via eth0 Nov 16 19:06:30 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0 Nov 16 19:06:30 localhost dhcpd: DHCPACK to 10.154.19.33 (00:0f:1f:86:fc:70) via eth0 Nov 16 19:12:24 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 16 19:12:24 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 16 19:12:27 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 16 19:12:27 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 16 19:12:57 localhost dhcpd: DHCPINFORM from 10.154.19.227 via eth0 Nov 16 19:12:57 localhost dhcpd: DHCPACK to 10.154.19.227 (00:19:b9:2a:19:37) via eth0 Nov 16 19:13:01 localhost dhcpd: DHCPINFORM from 10.154.19.227 via eth0 Nov 16 19:13:01 localhost dhcpd: DHCPACK to 10.154.19.227 (00:19:b9:2a:19:37) via eth0 The above logs look like clients *are* connecting and getting given IPs (the ack acknowledge entries). If it weren't for that, I'd have been suggesting checking the server isn't firewalled off from the clients. Perhaps you should also show us some logs from the clients. Are these entries from the clients you expect to work with, or are you getting clients from someone else's network? Having two DHCP servers on a network is a recipe for disaster, unless you know what you're doing, so you can configure them to work co-operatively, or not to interfere with each other. I'm not sure if you've detailed the topology of your network, either. On my server, admittedly it's still FC4, but you should see something similar, I see the following logged when a client joins: Nov 18 04:28:37 server dhcpd: DHCPDISCOVER from 00:1e:57:0a:65:e4 via eth0 Nov 18 04:28:37 server dhcpd: DHCPOFFER on 192.168.1.23 to 00:1e:57:0a:65:e4 via eth0 Nov 18 04:28:37 server dhcpd: DHCPREQUEST for 192.168.1.23 (192.168.1.2) from 00:1e:57:0a:65:e4 via eth0 Nov 18 04:28:37 server dhcpd: DHCPACK on 192.168.1.23 to 00:1e:57:0a:65:e4 via eth0 Which *may* also have some log entries about writing leases, but that depends on whether the leases file needed modifying at the time. If a client reconnects during their lease, it won't need to. Above was logged with a Fedora laptop joined the LAN. And below, when a Windows PC joined. It's slightly different in behaviour, and sends the hostname (bracketed) along, as well. Nov 17 14:14:20 server dhcpd: Wrote 0 deleted host decls to leases file. Nov 17 14:14:20 server dhcpd: Wrote 0 new dynamic host decls to leases file. Nov 17 14:14:20 server dhcpd: Wrote 9 leases to leases file. Nov 17 14:14:20 server dhcpd: DHCPREQUEST for 192.168.1.194 from 00:05:1c:19:dd:2f (hewie) via eth0 Nov 17 14:14:20 server dhcpd: DHCPACK on 192.168.1.194 to 00:05:1c:19:dd:2f (hewie) via eth0 Nov 17 14:16:49 server dhcpd: DHCPINFORM from 192.168.1.194 via eth0 Nov 17 14:16:49 server dhcpd: DHCPACK to 192.168.1.194 Nov 17 14:16:52 server dhcpd: DHCPINFORM from 192.168.1.194 via eth0 Nov 17 14:16:52 server dhcpd: DHCPACK to 192.168.1.194 There may be delays between some things, as the system may wait before writing settings to file (that helps when you have a large LAN, so the drive isn't thrashed by every client), and some clients do more chatting a little while after setup. And the logs on my client, using F9, show this: Nov 18 04:28:35 laptop NetworkManager: info DHCP: device wlan0 state changed (null) - preinit Nov 18 04:28:35 laptop dhclient: Listening on LPF/wlan0/00:1e:57:0a:65:e4 Nov 18 04:28:35 laptop dhclient: Sending on LPF/wlan0/00:1e:57:0a:65:e4 Nov 18 04:28:35 laptop dhclient: Sending on Socket/fallback Nov 18 04:28:38 laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Nov 18 04:28:38 laptop dhclient: DHCPOFFER from 192.168.1.2 Nov 18 04:28:38 laptop dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Nov 18 04:28:38 laptop dhclient: DHCPACK from 192.168.1.2 Nov 18 04:28:38 laptop NetworkManager: info DHCP: device wlan0 state changed preinit - bound Nov 18 04:28:38 laptop NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... Nov 18 04:28:38 laptop NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... Nov 18 04:28:38 laptop NetworkManager: infoaddress 192.168.1.23 Nov 18 04:28:38 laptop NetworkManager: infoprefix 24 (255.255.255.0) Nov 18 04:28:38 laptop NetworkManager: infogateway 192.168.1.254 Nov 18 04:28:38 laptop NetworkManager: infohostname 'laptop-wireless' Nov 18 04:28:38 laptop NetworkManager: infonameserver '192.168.1.2' Nov 18 04:28:38 laptop NetworkManager: infodomain name 'lan.example.com.' Nov 18 04:28:38 laptop NetworkManager: info Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Nov 18 04:28:38 laptop NetworkManager: info
Re: Make a DHCP server using Fedora - Help
--- On Mon, 11/17/08, Bill Davidsen [EMAIL PROTECTED] wrote:
From: Bill Davidsen [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: fedora-list@redhat.com
Date: Monday, November 17, 2008, 12:03 PM
Antonio Olivares wrote:
--- On Sun, 11/16/08, Marko Vojinovic
[EMAIL PROTECTED] wrote:
###
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
...snip...
Save, do a service dhcpd restart (it
should say
OK), then
tail -f /var/log/messages and watch
what is
going on. Restart the clients (one by one if you
wish to examine /var/log/messages after
each client, otherwise you may restart them all
simultaneously :-)...).
[[ N.B. I suppose you have configured the clients
to use
dhcp and not have anything statically assigned...
]]
What should be going on is that the clients in the
classroom ask for IP configuration (dhcp request),
then dhcpd replies with the
data above (dhcp offer) and then each client
accepts this offer. If all goes
well, up to this point each client should have a
192.168.0.* IP assigned
dynamically, and be able to ping any other client
with such address, as well as
the server, 192.168.0.1. If this doesn't
happen, tell us what does
happen.
...snip...
I did as you suggested and I still cannot connect the
machines to the new server :(
Before even trying to connect, after you reload the dhcpd,
do netstat -ta and look to see if the server is
listening (state LISTEN) on the dhcp port.
Also ifconfig eth1 and netstat -rn
so we can be sure you did what people intended you to do.
/etc/dhcpd.conf
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
subnet 10.154.19.0 netmask 255.255.255.0 {
} # this means don't do anything with the big
network
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1; # your server is the
router for classroom
option subnet-mask 255.255.255.0; # the mask given to
classroom
option domain-name-servers 10.154.16.130, 10.128.0.4;
# dns servers
range 192.168.0.2 192.168.0.254; # the pool of
addresses for classroom
}
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:
[ OK ]
[EMAIL PROTECTED] ~]#
It starts up but no leases show up, I am trying to
ping computer from windows 2000 machine and from another
machine running rawhide
tail -f /var/log/messages show:
Nov 16 18:51:13 localhost ntpd[2004]: kernel time sync
status change 4001 Nov 16 18:54:24 localhost dhcpd:
DHCPREQUEST for 10.154.19.129 from 00:06:5b:4f:d7:d2 via
eth0: unknown lease 10.154.19.129.
Nov 16 18:56:32 localhost dhcpd: Internet Systems
Consortium DHCP Server 4.0.0 Nov 16 18:56:32 localhost
dhcpd: Copyright 2004-2007 Internet Systems Consortium.
Nov 16 18:56:32 localhost dhcpd: All rights
reserved. Nov 16 18:56:32
localhost dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
Nov 16 18:56:32
localhost dhcpd: Not searching LDAP since ldap-server,
ldap-port and ldap-base-dn were not specified in the config
file Nov 16 18:56:32 localhost
dhcpd: Wrote 0 leases to leases file. Nov 16
18:56:32 localhost dhcpd: Listening on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16
18:56:32 localhost dhcpd: Sending on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16
18:56:32 localhost dhcpd: Sending on
Socket/fallback/fallback-net Nov 16 18:56:40 localhost
dhcpd: Internet Systems Consortium DHCP Server 4.0.0 Nov 16
18:56:40 localhost dhcpd: Copyright 2004-2007 Internet
Systems Consortium.
Nov 16 18:56:40
localhost dhcpd: All rights reserved.
Nov 16 18:56:40 localhost dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
Nov 16 18:56:40
localhost dhcpd: Not searching LDAP since ldap-server,
ldap-port and ldap-base-dn were not specified in the config
file Nov 16 18:56:40 localhost
dhcpd: Wrote 0 leases to leases file. Nov 16
18:56:40 localhost dhcpd: Listening on
LPF/eth0/00:0e:a6:42:59:af
Re: Make a DHCP server using Fedora - Help
--- On Mon, 11/17/08, Tim [EMAIL PROTECTED] wrote: From: Tim [EMAIL PROTECTED] Subject: Re: Make a DHCP server using Fedora - Help To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Date: Monday, November 17, 2008, 2:23 PM On Sun, 2008-11-16 at 17:13 -0800, Antonio Olivares wrote: Nov 16 19:06:27 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0 Nov 16 19:06:27 localhost dhcpd: DHCPACK to 10.154.19.33 (00:0f:1f:86:fc:70) via eth0 Nov 16 19:06:30 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0 Nov 16 19:06:30 localhost dhcpd: DHCPACK to 10.154.19.33 (00:0f:1f:86:fc:70) via eth0 Nov 16 19:12:24 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 16 19:12:24 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 16 19:12:27 localhost dhcpd: DHCPINFORM from 10.154.19.94 via eth0 Nov 16 19:12:27 localhost dhcpd: DHCPACK to 10.154.19.94 (00:40:f4:ea:ee:d3) via eth0 Nov 16 19:12:57 localhost dhcpd: DHCPINFORM from 10.154.19.227 via eth0 Nov 16 19:12:57 localhost dhcpd: DHCPACK to 10.154.19.227 (00:19:b9:2a:19:37) via eth0 Nov 16 19:13:01 localhost dhcpd: DHCPINFORM from 10.154.19.227 via eth0 Nov 16 19:13:01 localhost dhcpd: DHCPACK to 10.154.19.227 (00:19:b9:2a:19:37) via eth0 The above logs look like clients *are* connecting and getting given IPs (the ack acknowledge entries). If it weren't for that, I'd have been suggesting checking the server isn't firewalled off from the clients. Perhaps you should also show us some logs from the clients. Are these entries from the clients you expect to work with, or are you getting clients from someone else's network? Having two DHCP servers on a network is a recipe for disaster, unless you know what you're doing, so you can configure them to work co-operatively, or not to interfere with each other. That is probably the case since the machines are looking for the big network to get their ip's and other machines at school are trying to connect to mine, the machines I have I can put them via mac address, but since I am learning I wanted to avoid that. THe file /etc/sysconfig/network-scripts/ifcfg-eth1 did not exist and I created it. I also tried to change the file /etc/syconfig/dhcpd to change the args to eth1, but file was read-only. I have webmin installed, but I am having trouble with the dhcp server. I'm not sure if you've detailed the topology of your network, either. I have put it up, but you might have missed it. My machine is connected to a local network and is given an address via dhcp which is static according to mac address I get address ip address 10.154.19.210 netmask 255.255.255.0 gateway 10.154.19.1 and the nameservers 10.128.0.4 10.154.16.130 [EMAIL PROTECTED] ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0E:A6:42:59:AF inet addr:10.154.19.210 Bcast:10.154.19.255 Mask:255.255.255.0 inet6 addr: fe80::20e:a6ff:fe42:59af/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:186850 errors:0 dropped:0 overruns:0 frame:0 TX packets:98727 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:152818248 (145.7 MiB) TX bytes:13202535 (12.5 MiB) Interrupt:22 eth1 Link encap:Ethernet HWaddr 00:60:97:C5:2A:C3 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:18 Base address:0xdf00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:5557 errors:0 dropped:0 overruns:0 frame:0 TX packets:5557 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:884348 (863.6 KiB) TX bytes:884348 (863.6 KiB) pan0 Link encap:Ethernet HWaddr 4A:5C:5C:CB:EA:F1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) [EMAIL PROTECTED] ~]# On my server, admittedly it's still FC4, but you should see something similar, I see the following logged when a client joins: Nov 18 04:28:37 server dhcpd: DHCPDISCOVER from 00:1e:57:0a:65:e4 via eth0
Re: Make a DHCP server using Fedora - Help
Antonio Olivares: Nov 16 19:06:27 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0 Nov 16 19:06:27 localhost dhcpd: DHCPACK to 10.154.19.33 (00:0f:1f:86:fc:70) via eth0 Nov 16 19:06:30 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0 Nov 16 19:06:30 localhost dhcpd: DHCPACK to 10.154.19.33 (00:0f:1f:86:fc:70) via eth0 Tim: The above logs look like clients *are* connecting and getting given IPs (the ack acknowledge entries). Perhaps I should say, looks like they have an IP (inform), and they're being allowed to keep on using it (ack). If you want to see devices get assigned IPs, you might have to make them release their current IP, then try and get another one. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.27.5-37.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Mike Cloaked wrote: Mike Cloaked wrote: I did not see the reply from Paul H on fixing the SElinux issues - was this a private reply? If so could you let us know the fix - as I will be moving to a machine running DHCP with SElinux enabled when F10 comes out. I was looking through the selinux list and just saw the reply there - I did not realise you had posted on that list also Hello, What is the output by the following ? cat /etc/selinux/config Thanks ! Edward. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Sun, 11/16/08, Mike Cloaked [EMAIL PROTECTED] wrote:
From: Mike Cloaked [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: fedora-list@redhat.com
Date: Sunday, November 16, 2008, 2:19 AM
Antonio Olivares wrote:
I might go to work and try it out. I will change the
numbers and also add
more time in the leases. I have been given great
advice by several
helpful people, notably yourself, Tim and Marko (also
Paul H. for selinux
denying dhpcd). I have to make the changes in the
/etc/dhcpd.conf file
and try it out. I will test with a Windows 2000
machine and a Fedora
rawhide box and upon success or failure. I will
report back.
I did not see the reply from Paul H on fixing the SElinux
issues - was this
a private reply?
no, to fedora-selinux-list
thread: avc: denied { write } for pid=5267 comm=dhcpd name=dhcpd.pid
If so could you let us know the fix - as
I will be moving
to a machine running DHCP with SElinux enabled when F10
comes out.
see below :)
Thanks
Mike
--
View this message in context:
http://www.nabble.com/Make-a-DHCP-server-using-Fedora---Help-tp20511161p20523913.html
Sent from the Fedora List mailing list archive at
Nabble.com.
--
I encountered an error/avc denial:
running
# tail -f /var/log/messages:
--
Nov 14 20:03:40 localhost kernel: type=1400
audit(1226714620.135:183): avc: denied { read } for pid=5267
comm=dhcpd name=dhcpd.pid dev=dm-0 ino=3244731
scontext=unconfined_u:system_r:dhcpd_t:s0
tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file Nov 14
20:03:40 localhost kernel: type=1400 audit(1226714620.135:184): avc:
denied { write } for pid=5267 comm=dhcpd name=dhcpd.pid
dev=dm-0 ino=3244731scontext=unconfined_u:system_r:dhcpd_t:s0
tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file Nov 14
20:03:40 localhost dhcpd: Can't create PID file /var/run/dhcpd.pid:
Permission denied.
How can I allow it to work?
Setroubleshoot has not kicked in to warn me so I do not know a fix as
of this moment :(
/var/run/dhcpd.pid should be dhcpd_var_run_t, not var_run_t.
--
Paul replied:
Try:
# restorecon -v /var/run /var/run/dhcpd.pid
Paul.
--
Now I do not get the denial. I sent the message to [EMAIL PROTECTED] and Paul
answered my question/plea for help.
Regards,
Antonio
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Sat, 11/15/08, Tim [EMAIL PROTECTED] wrote:
From: Tim [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: Community assistance, encouragement, and advice for using Fedora.
fedora-list@redhat.com
Date: Saturday, November 15, 2008, 7:42 PM
On Sat, 2008-11-15 at 19:43 -0700, Craig White wrote:
you don't need bind to run unless you want to
provide DNS services.
There are advantages in doing so, but I'd learn how to
do DHCP, then
learn the next thing.
With a local DHCP and DNS server, particular if they talk
to each other,
you simplify client network configuration. Your DHCP
server assigns
them addresses, and your DNS server reseolves all their
addresses. You
don't need to play with hosts files on each PC, nor any
other part of
their network configuration, it's all centrally
managed. For anything
more than a three PC LAN, it soon gets annoying if you have
to keep
updating all their hosts files.
As Craig said, it can be simpler to use something that does
that for
you, such as a modem/router with its own DHCP server,
there's far less
things for you to have to configure. But, any of the ones
that I've
looked at, don't act as a local DNS server for their
own DHCP records.
So, you're stuck with fixing IPs in its DHCP server,
then messing with
hosts files on each PC.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.27.5-37.fc9.i686
Don't send private replies to my address, the mailbox
is ignored. I
read messages from the public lists.
--
I am working on it, but without success :(
I have installed webmin and made the corresponding changes that were suggested
[EMAIL PROTECTED] ~]# cd /home/olivares/Downloads/
[EMAIL PROTECTED] Downloads]# rpm -ivh webmin-1.441-1.noarch.rpm
Preparing...### [100%]
Operating system is Redhat Linux
1:webmin ### [100%]
Webmin install complete. You can now login to https://localhost:1/
as root with your root password.
[EMAIL PROTECTED] Downloads]# cat /etc/dhcpd.conf
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
log-facility local7;
subnet 10.154.19.0 netmask 255.255.255.0 {
range 10.154.19.1 10.154.19.20;
}
I changed DHCPDARG=eth0 as was suggested, but not working.
Nov 16 12:39:06 localhost dhcpd: of the dhcpd.conf file.
Nov 16 12:39:09 localhost dhcpd: DHCPINFORM from 10.154.19.11 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 12:39:30 localhost dhcpd: DHCPINFORM from 10.154.19.117 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 12:43:56 localhost dhcpd: DHCPINFORM from 10.154.19.246 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 12:44:01 localhost dhcpd: DHCPINFORM from 10.154.19.246 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 12:45:44 localhost dhcpd: DHCPINFORM from 10.154.19.19 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 12:45:47 localhost dhcpd: DHCPINFORM from 10.154.19.19 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 12:53:50 localhost dhcpd: DHCPINFORM from 10.154.19.235 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 13:03:04 localhost dhcpd: DHCPINFORM from 10.154.19.227 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 13:03:07 localhost dhcpd: DHCPINFORM from 10.154.19.227 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 13:03:44 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 13:03:47 localhost dhcpd: DHCPINFORM from 10.154.19.33 via eth0: not
authoritative for subnet 10.154.19.0
Nov 16 13:08:24 localhost kernel: Kernel logging (proc) stopped.
The original machine gets its ip from a central server and then I want to use
it as a server for several machines in my classroom.
It connects to 10.154.19.210 which is its address in the BIG network. it
gets DNS 10.154.16.130, 10.128.0.4 and gateway 10.154.19.1
I have been playing with webmin, but either I get [FAILED] messages or it
appears to work, but the machines cannot connect to it, or get their own IPs.
Thank you for hanging in there with me.
Antonio
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Antonio and others, I'm writing the stuff below off the top of my head ---
please feel free to correct me if necessarry, I may have slipped here or
there... ;-)
On Sunday 16 November 2008 20:52, Antonio Olivares wrote:
I changed DHCPDARG=eth0 as was suggested, but not working.
I missed this part. Where did you put this?
The original machine gets its ip from a central server and then I want to
use it as a server for several machines in my classroom.
It connects to 10.154.19.210 which is its address in the BIG network. it
gets DNS 10.154.16.130, 10.128.0.4 and gateway 10.154.19.1
Ok. I suggest the following setup. Get the cable coming from the big network
and plug it into your eth0. Then, take a small hub/switch/router/whatever and
connect your classroom computers to it (I guess this is already set up). Make
sure that *no* cable connects your hub to the big network. Instead, connect
the hub to the eth1 of your server. Your server should be the only link
between the big network and classroom network.
Leave eth0 configuration for later.
Configure eth1 device to have a *static* (manually assigned) IP address,
say, 192.168.0.1 with netmask 255.255.255.0 and bring it up. Do this using
system-config-network interface and running service network restart. Make
sure there is nothing related to NetworkManager active in the setup.
Next, configure dhcpd.conf in the following (most elementary) way, for the
time being:
###
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
subnet 10.154.19.0 netmask 255.255.255.0 {
} # this means don't do anything with the big network
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1 # your server is the router for classroom
option subnet-mask 255.255.255.0 # the mask given to classroom
option domain-name-servers 10.154.16.130, 10.128.0.4; # dns servers
range 192.168.0.2 192.168.0.254 # the pool of addresses for classroom
}
###
Save, do a service dhcpd restart (it should say OK), then
tail -f /var/log/messages and watch what is going on. Restart the clients
(one by one if you wish to examine /var/log/messages after each client,
otherwise you may restart them all simultaneously :-)...).
[[ N.B. I suppose you have configured the clients to use dhcp and not have
anything statically assigned... ]]
What should be going on is that the clients in the classroom ask for IP
configuration (dhcp request), then dhcpd replies with the data above (dhcp
offer) and then each client accepts this offer. If all goes well, up to this
point each client should have a 192.168.0.* IP assigned dynamically, and be
able to ping any other client with such address, as well as the server,
192.168.0.1. If this doesn't happen, tell us what does happen.
If all is well, up to now you have a working dhcpd configuration and each
client has an IP assigned. In /var/lib/dhcp/dhcpd.leases you have a list
stating which client (distinguished by its MAC address) has which IP assigned
to it. The leases file may have some stale/old/obsolete information (because
you have been playing with dhcpd before) --- ignore it, look at the bottom of
the file, where fresh information is stored.
The next step is to configure NAT (network address translation) on your
server's firewall, in order to allow the clients to access the big network
using your server as a router. But this is a different problem --- first make
sure the above configuration works, and then we'll go to the NAT
configuration after that. One step at a time. ;-)
HTH, :-)
Marko
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Sun, 11/16/08, Marko Vojinovic [EMAIL PROTECTED] wrote:
From: Marko Vojinovic [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: fedora-list@redhat.com, [EMAIL PROTECTED]
Date: Sunday, November 16, 2008, 4:49 PM
Antonio and others, I'm writing the stuff below off the
top of my head ---
please feel free to correct me if necessarry, I may have
slipped here or
there... ;-)
On Sunday 16 November 2008 20:52, Antonio Olivares wrote:
I changed DHCPDARG=eth0 as was suggested, but not
working.
I missed this part. Where did you put this?
I had changed back and forth between eth0 and eth1 and now it is and should be
eth0 :)
[EMAIL PROTECTED] ~]# cat /etc/sysconfig/dhcpd
DHCPDARGS=eth0
The original machine gets its ip from a central server
and then I want to
use it as a server for several machines in my
classroom.
It connects to 10.154.19.210 which is its address in
the BIG network. it
gets DNS 10.154.16.130, 10.128.0.4 and gateway
10.154.19.1
Ok. I suggest the following setup. Get the cable coming
from the big network
and plug it into your eth0. Then, take a small
hub/switch/router/whatever and
connect your classroom computers to it (I guess this is
already set up). Make
sure that *no* cable connects your hub to the
big network. Instead, connect
the hub to the eth1 of your server. Your server should be
the only link
between the big network and classroom network.
Leave eth0 configuration for later.
Configure eth1 device to have a *static* (manually
assigned) IP address,
say, 192.168.0.1 with netmask 255.255.255.0 and bring it
up. Do this using
system-config-network interface and running
service network restart. Make
sure there is nothing related to NetworkManager active in
the setup.
Next, configure dhcpd.conf in the following (most
elementary) way, for the
time being:
###
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
subnet 10.154.19.0 netmask 255.255.255.0 {
} # this means don't do anything with the big network
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1 # your server is the router for
classroom
option subnet-mask 255.255.255.0 # the mask given to
classroom
option domain-name-servers 10.154.16.130, 10.128.0.4; # dns
servers
range 192.168.0.2 192.168.0.254 # the pool of addresses
for classroom
}
###
Save, do a service dhcpd restart (it should say
OK), then
tail -f /var/log/messages and watch what is
going on. Restart the clients
(one by one if you wish to examine /var/log/messages after
each client,
otherwise you may restart them all simultaneously :-)...).
[[ N.B. I suppose you have configured the clients to use
dhcp and not have
anything statically assigned... ]]
What should be going on is that the clients in the
classroom ask for IP
configuration (dhcp request), then dhcpd replies with the
data above (dhcp
offer) and then each client accepts this offer. If all goes
well, up to this
point each client should have a 192.168.0.* IP assigned
dynamically, and be
able to ping any other client with such address, as well as
the server,
192.168.0.1. If this doesn't happen, tell us what does
happen.
If all is well, up to now you have a working dhcpd
configuration and each
client has an IP assigned. In /var/lib/dhcp/dhcpd.leases
you have a list
stating which client (distinguished by its MAC address) has
which IP assigned
to it. The leases file may have some stale/old/obsolete
information (because
you have been playing with dhcpd before) --- ignore it,
look at the bottom of
the file, where fresh information is stored.
The next step is to configure NAT (network address
translation) on your
server's firewall, in order to allow the clients to
access the big network
using your server as a router. But this is a different
problem --- first make
sure the above configuration works, and then we'll go
to the NAT
configuration after that. One step at a time. ;-)
HTH, :-)
Marko
I will sure try this and hopefully it will work. I will report back.
Thank you for your help as well :)
Regards,
Antonio
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Sun, 11/16/08, Marko Vojinovic [EMAIL PROTECTED] wrote:
###
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
subnet 10.154.19.0 netmask 255.255.255.0 {
} # this means don't do anything with the big network
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1 # your server is the router for
classroom
option subnet-mask 255.255.255.0 # the mask given to
classroom
option domain-name-servers 10.154.16.130, 10.128.0.4; # dns
servers
range 192.168.0.2 192.168.0.254 # the pool of addresses
for classroom
}
###
Save, do a service dhcpd restart (it should say
OK), then
tail -f /var/log/messages and watch what is
going on. Restart the clients
(one by one if you wish to examine /var/log/messages after
each client,
otherwise you may restart them all simultaneously :-)...).
[[ N.B. I suppose you have configured the clients to use
dhcp and not have
anything statically assigned... ]]
What should be going on is that the clients in the
classroom ask for IP
configuration (dhcp request), then dhcpd replies with the
data above (dhcp
offer) and then each client accepts this offer. If all goes
well, up to this
point each client should have a 192.168.0.* IP assigned
dynamically, and be
able to ping any other client with such address, as well as
the server,
192.168.0.1. If this doesn't happen, tell us what does
happen.
If all is well, up to now you have a working dhcpd
configuration and each
client has an IP assigned. In /var/lib/dhcp/dhcpd.leases
you have a list
stating which client (distinguished by its MAC address) has
which IP assigned
to it. The leases file may have some stale/old/obsolete
information (because
you have been playing with dhcpd before) --- ignore it,
look at the bottom of
the file, where fresh information is stored.
The next step is to configure NAT (network address
translation) on your
server's firewall, in order to allow the clients to
access the big network
using your server as a router. But this is a different
problem --- first make
sure the above configuration works, and then we'll go
to the NAT
configuration after that. One step at a time. ;-)
HTH, :-)
Marko
I did as you suggested and I still cannot connect the machines to the new
server :(
/etc/dhcpd.conf
default-lease-time 21600; #600
max-lease-time 43200; #7200
ddns-update-style none;
authoritative;
subnet 10.154.19.0 netmask 255.255.255.0 {
} # this means don't do anything with the big network
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1; # your server is the router for classroom
option subnet-mask 255.255.255.0; # the mask given to classroom
option domain-name-servers 10.154.16.130, 10.128.0.4; # dns servers
range 192.168.0.2 192.168.0.254; # the pool of addresses for classroom
}
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd restart
Starting dhcpd:[ OK ]
[EMAIL PROTECTED] ~]#
It starts up but no leases show up, I am trying to ping computer from windows
2000 machine and from another machine running rawhide
tail -f /var/log/messages show:
Nov 16 18:51:13 localhost ntpd[2004]: kernel time sync status change 4001
Nov 16 18:54:24 localhost dhcpd: DHCPREQUEST for 10.154.19.129 from
00:06:5b:4f:d7:d2 via eth0: unknown lease 10.154.19.129.
Nov 16 18:56:32 localhost dhcpd: Internet Systems Consortium DHCP Server 4.0.0
Nov 16 18:56:32 localhost dhcpd: Copyright 2004-2007 Internet Systems
Consortium.
Nov 16 18:56:32 localhost dhcpd: All rights reserved.
Nov 16 18:56:32 localhost dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
Nov 16 18:56:32 localhost dhcpd: Not searching LDAP since ldap-server,
ldap-port and ldap-base-dn were not specified in the config file
Nov 16 18:56:32 localhost dhcpd: Wrote 0 leases to leases file.
Nov 16 18:56:32 localhost dhcpd: Listening on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:32 localhost dhcpd: Sending on
LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Nov 16 18:56:32 localhost dhcpd: Sending on Socket/fallback/fallback-net
Nov 16 18:56:40 localhost dhcpd: Internet Systems Consortium DHCP Server 4.0.0
Nov 16 18:56:40 localhost dhcpd: Copyright 2004-2007 Internet Systems
Consortium.
Re: Make a DHCP server using Fedora - Help
On Fri, 2008-11-14 at 17:42 -0800, Antonio Olivares wrote:
subnet 10.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
}
It seems pointlessly redundant to declare a subnet twice. And stranger
to declare it differently. I see no point for the first one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Sat, 11/15/08, Tim [EMAIL PROTECTED] wrote:
From: Tim [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for
using Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 1:57 AM
On Fri, 2008-11-14 at 17:42 -0800, Antonio Olivares wrote:
subnet 10.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
It seems pointlessly redundant to declare a subnet twice.
And stranger
to declare it differently. I see no point for the first
one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my address, the mailbox
is ignored. I
read messages from the public lists.
Which one should I keep Tim, the first one or the second one?
I have tried before and not succeeded, I want to succeed this time.
The machine that will become the server has gateway 10.154.19.1, is it okay to
make the server
10.154.19.0 ?
Also the machine's netmask is 255.255.255.0 and the netmask of the server
should it be 255.255.255.0 or 255.255.255.254 or other thing?
Thanks,
Antonio
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Antonio Olivares wrote:
--- On Sat, 11/15/08, Tim [EMAIL PROTECTED] wrote:
From: Tim [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for
using Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 1:57 AM
On Fri, 2008-11-14 at 17:42 -0800, Antonio Olivares wrote:
subnet 10.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
It seems pointlessly redundant to declare a subnet twice.
And stranger
to declare it differently. I see no point for the first
one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my address, the mailbox
is ignored. I
read messages from the public lists.
Which one should I keep Tim, the first one or the second one?
I have tried before and not succeeded, I want to succeed this time.
The machine that will become the server has gateway 10.154.19.1, is it okay to
make the server
10.154.19.0 ?
Also the machine's netmask is 255.255.255.0 and the netmask of the server
should it be 255.255.255.0 or 255.255.255.254 or other thing?
Thanks,
Antonio
Dear You,
Please try these :
subnet 10.154.19.0 netmask 255.255.255.224
{
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,rtr-239-0-2.example.org;
}
Good luck !
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Sat, 11/15/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for
using Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 7:06 AM
Antonio Olivares wrote:
--- On Sat, 11/15/08, Tim
[EMAIL PROTECTED] wrote:
From: Tim [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community
assistance, encouragement, and advice for using
Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 1:57 AM
On Fri, 2008-11-14 at 17:42 -0800, Antonio Olivares
wrote:
subnet 10.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
It seems pointlessly redundant to declare a subnet
twice.
And stranger
to declare it differently. I see no point for the
first
one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my address, the
mailbox
is ignored. I
read messages from the public lists.
Which one should I keep Tim, the first one or the
second one?
I have tried before and not succeeded, I want to
succeed this time.
The machine that will become the server has gateway
10.154.19.1, is it okay to make the server
10.154.19.0 ?
Also the machine's netmask is 255.255.255.0 and the
netmask of the server should it be 255.255.255.0 or
255.255.255.254 or other thing?
Thanks,
Antonio
Dear You,
Please try these :
subnet 10.154.19.0 netmask 255.255.255.224
{
range 10.154.19.10 10.154.19.20;
option routers
rtr-239-0-1.example.org,rtr-239-0-2.example.org;
}
Good luck !
I tried that and it does not work :(
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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;
# Use this to enble / disable dynamic dns updates globally.
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.154.19.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
}
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not
specified in the config file
Wrote 0 leases to leases file.
No subnet declaration for eth0 (10.154.19.210).
** 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!
This version of ISC DHCP is based on the release available
on ftp.isc.org. Features have been added and other changes
have been made to the base software release in order to make
it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site:
http://bugzilla.redhat.com
exiting.
I also have added to iptables two lines and ran iptables-save
when I read the following:
upon reading another page:
http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html
it says iptables and has this part:
# Forward all packets from eth1 (internal network) to eth0 (the public internet)
iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
# Forward packets that are part of existing and related connections from eth0
to eth1
iptables -A FORWARD -i eth0
Re: Make a DHCP server using Fedora - Help
--- On Sat, 11/15/08, Antonio Olivares [EMAIL PROTECTED] wrote:
subnet 10.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224
{
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
It seems pointlessly redundant to declare a
subnet
twice.
And stranger
to declare it differently. I see no point for
the
first
one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my address,
the
mailbox
is ignored. I
read messages from the public lists.
Which one should I keep Tim, the first one or the
second one?
I have tried before and not succeeded, I want to
succeed this time.
The machine that will become the server has
gateway
10.154.19.1, is it okay to make the server
10.154.19.0 ?
Also the machine's netmask is 255.255.255.0
and the
netmask of the server should it be 255.255.255.0 or
255.255.255.254 or other thing?
Thanks,
Antonio
Dear You,
Please try these :
subnet 10.154.19.0 netmask 255.255.255.224
{
range 10.154.19.10 10.154.19.20;
option routers
rtr-239-0-1.example.org,rtr-239-0-2.example.org;
}
Good luck !
I tried that and it does not work :(
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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;
# Use this to enble / disable dynamic dns updates globally.
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.154.19.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
No subnet declaration for eth0 (10.154.19.210).
** 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!
This version of ISC DHCP is based on the release available
on ftp.isc.org. Features have been added and other changes
have been made to the base software release in order to
make
it work better with this distribution.
Please report for this software via the Red Hat Bugzilla
site:
http://bugzilla.redhat.com
exiting.
I also have added to iptables two lines and ran
iptables-save
when I read the following:
upon reading another page:
http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html
it says iptables and has this part:
# Forward all packets from eth1 (internal network) to eth0
(the public internet)
iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
# Forward packets that are part of existing and related
connections from eth0 to eth1
iptables -A FORWARD -i eth0 -o eth1 -m state --state
ESTABLISHED,RELATED -j ACCEPT
# Enable SNAT functionality on eth0. a.b.c.d are generally
the ip of the eth0
iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j
SNAT --to-source a.
Added === iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
and === iptables -A FORWARD -i eth0 -o eth1 -m state
--state ESTABLISHED,RELATED -j ACCEPT
Did not add SNAT, does that make a difference?
[EMAIL PROTECTED] ~]# iptables-save
Re: Make a DHCP server using Fedora - Help
On Sat, 2008-11-15 at 09:48 -0800, Antonio Olivares wrote:
--- On Sat, 11/15/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for
using Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 7:06 AM
Antonio Olivares wrote:
--- On Sat, 11/15/08, Tim
[EMAIL PROTECTED] wrote:
From: Tim [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community
assistance, encouragement, and advice for using
Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 1:57 AM
On Fri, 2008-11-14 at 17:42 -0800, Antonio Olivares
wrote:
subnet 10.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
It seems pointlessly redundant to declare a subnet
twice.
And stranger
to declare it differently. I see no point for the
first
one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my address, the
mailbox
is ignored. I
read messages from the public lists.
Which one should I keep Tim, the first one or the
second one?
I have tried before and not succeeded, I want to
succeed this time.
The machine that will become the server has gateway
10.154.19.1, is it okay to make the server
10.154.19.0 ?
Also the machine's netmask is 255.255.255.0 and the
netmask of the server should it be 255.255.255.0 or
255.255.255.254 or other thing?
Thanks,
Antonio
Dear You,
Please try these :
subnet 10.154.19.0 netmask 255.255.255.224
{
range 10.154.19.10 10.154.19.20;
option routers
rtr-239-0-1.example.org,rtr-239-0-2.example.org;
}
Good luck !
I tried that and it does not work :(
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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;
# Use this to enble / disable dynamic dns updates globally.
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.154.19.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
}
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not
specified in the config file
Wrote 0 leases to leases file.
No subnet declaration for eth0 (10.154.19.210).
** 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. **
/etc/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
authoritative;
log-facility local7;
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option domain-name-servers $DNS_SERVER_IP_ADDRESS_1, $DNS_SERVER_IP_ADDRESS_2;
option domain-name $YOUR_DOMAIN_NAME;
option broadcast-address 10.154.19.31;
option subnet-mask 255.255.255.224;
option routers 10.154.19.1 ; # just a guess
ddns-updates off
Re: Make a DHCP server using Fedora - Help
On Sat, 2008-11-15 at 11:11 -0700, Craig White wrote:
On Sat, 2008-11-15 at 09:48 -0800, Antonio Olivares wrote:
--- On Sat, 11/15/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community assistance, encouragement, and advice
for using Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 7:06 AM
Antonio Olivares wrote:
--- On Sat, 11/15/08, Tim
[EMAIL PROTECTED] wrote:
From: Tim [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community
assistance, encouragement, and advice for using
Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 1:57 AM
On Fri, 2008-11-14 at 17:42 -0800, Antonio Olivares
wrote:
subnet 10.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
It seems pointlessly redundant to declare a subnet
twice.
And stranger
to declare it differently. I see no point for the
first
one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my address, the
mailbox
is ignored. I
read messages from the public lists.
Which one should I keep Tim, the first one or the
second one?
I have tried before and not succeeded, I want to
succeed this time.
The machine that will become the server has gateway
10.154.19.1, is it okay to make the server
10.154.19.0 ?
Also the machine's netmask is 255.255.255.0 and the
netmask of the server should it be 255.255.255.0 or
255.255.255.254 or other thing?
Thanks,
Antonio
Dear You,
Please try these :
subnet 10.154.19.0 netmask 255.255.255.224
{
range 10.154.19.10 10.154.19.20;
option routers
rtr-239-0-1.example.org,rtr-239-0-2.example.org;
}
Good luck !
I tried that and it does not work :(
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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;
# Use this to enble / disable dynamic dns updates globally.
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.154.19.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
}
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not
specified in the config file
Wrote 0 leases to leases file.
No subnet declaration for eth0 (10.154.19.210).
** 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. **
/etc/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
authoritative;
log-facility local7;
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option domain-name-servers $DNS_SERVER_IP_ADDRESS_1
Re: Make a DHCP server using Fedora - Help
--- On Sat, 11/15/08, Craig White [EMAIL PROTECTED] wrote:
From: Craig White [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: Community assistance, encouragement, and advice for using Fedora.
fedora-list@redhat.com
Date: Saturday, November 15, 2008, 10:20 AM
On Sat, 2008-11-15 at 11:11 -0700, Craig White wrote:
On Sat, 2008-11-15 at 09:48 -0800, Antonio Olivares
wrote:
--- On Sat, 11/15/08, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora
- Help
To: [EMAIL PROTECTED], Community
assistance, encouragement, and advice for using
Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 7:06 AM
Antonio Olivares wrote:
--- On Sat, 11/15/08, Tim
[EMAIL PROTECTED] wrote:
From: Tim
[EMAIL PROTECTED]
Subject: Re: Make a DHCP server
using Fedora - Help
To: [EMAIL PROTECTED],
Community
assistance, encouragement, and advice for
using
Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008,
1:57 AM
On Fri, 2008-11-14 at 17:42 -0800,
Antonio Olivares
wrote:
subnet 10.154.19.0 netmask
255.255.255.0 {
}
# This is a very basic subnet
declaration.
subnet 10.154.19.0 netmask
255.255.255.224 {
range 10.154.19.10
10.154.19.20;
option routers
rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
It seems pointlessly redundant to
declare a subnet
twice.
And stranger
to declare it differently. I see no
point for the
first
one.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.26.6-79.fc9.i686
Don't send private replies to my
address, the
mailbox
is ignored. I
read messages from the public lists.
Which one should I keep Tim, the first
one or the
second one?
I have tried before and not succeeded,
I want to
succeed this time.
The machine that will become the server
has gateway
10.154.19.1, is it okay to make the server
10.154.19.0 ?
Also the machine's netmask is
255.255.255.0 and the
netmask of the server should it be
255.255.255.0 or
255.255.255.254 or other thing?
Thanks,
Antonio
Dear You,
Please try these :
subnet 10.154.19.0 netmask
255.255.255.224
{
range 10.154.19.10 10.154.19.20;
option routers
rtr-239-0-1.example.org,rtr-239-0-2.example.org;
}
Good luck !
I tried that and it does not work :(
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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;
# Use this to enble / disable dynamic dns updates
globally.
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.154.19.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org,
rtr-239-0-2.example.org;
}
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit
http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port
and ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
No subnet declaration for eth0 (10.154.19.210).
** 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
Re: Make a DHCP server using Fedora - Help
On Saturday 15 November 2008 01:09, Antonio Olivares wrote: I am trying once again, something that I have not succeeded in doing. I have tried before: http://marc.info/?l=fedora-listm=112527669314098w=4 Haven't read the whole thread, sorry, just the beggining. But I hope I didn't miss much info. ;-) Now I am at it again, this time, I want to succeed. I have read the documentation again and I can't succeed, I have tried copying different /etc/dhcpcd.conf files from different places, but not working The dhcpd configuration is highly network-dependent. You should never expect that somebody else's dhcpd.conf will Just Work for you. It typically Just Won't. You have to understand what and how to configure and write your own dhcpd.conf. I have two nic's one from the motherboard and a different one(PCI) [EMAIL PROTECTED] ~]# lspci 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller 01:08.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] Ok. Which do you want to be used for what purpose? How are they connected to outside world? What is your network topology? Try to think like this --- there is generally the up network (the outside world, not to be served with dhcpd) and down network (the local one, which should accept your dhcp offers). How are these two connected to the interfaces? [EMAIL PROTECTED] network-scripts]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0E:A6:42:59:AF inet addr:10.154.19.210 Bcast:10.154.19.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:60:97:C5:2A:C3 inet6 addr: fe80::260:97ff:fec5:2ac3/64 Scope:Link I see no IPv4 information for eth1. Depending on your topology, you should probably have it configured and up (with a static IP, if this is to be a link to the down network). I have read the howto's from here: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch08_:_Conf iguring_the_DHCP_Server and http://www.howtoforge.com/perfect-server-fedora9 as well as the article in Red Hat Magazine. I've never read those articles, nor I intend to fwiw. But more importantly, have you read man dhcpd and man dhcpd.conf? Further, have you understood what is said there? This is essential for correct dhcpd operation. The main moral for servers: Understand What You Are Doing. If you need help on this, feel free to ask, or read some book on tcp/ip to learn the details about network structure. That's what I did and have never ever had any problems configuring dhcpd, since. :-) [EMAIL PROTECTED] ~]# service dhcpd start Starting dhcpd:[FAILED] Ok, so something is wrong. ;-) [EMAIL PROTECTED] ~]# dhcpd -f [snip] No subnet declaration for eth0 (10.154.19.210). ** 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. ** So, is this what you want, or not? You have to make it clear on what device (eth0 or eth1 or both) the dhcpd will listen. Where is your down network and where is the up one? Typically, you *do not* want to listen on the up interface, and you *do* want to listen on the down interface. [[ N.B. In some network setups, the up network may not even exist. In other setups, you may want to listen on both up and down networks. You need to specify what exactly you want to achieve. ]] Not configured to listen on any interfaces! So this is why it fails. The dhcpd.conf file is not configured correctly (or at all). Or the eth1 interface is not up and running (separate problem --- configure it, check cables and such...). Or both. [EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf # dhcpd.conf # # Sample configuration file for ISC dhcpd Example dhcpd.conf files are mainly targeted for educational purposes, not usability. Do not just copy-paste the example to /etc/dhcpd.conf and expect that to work. The example is there to teach you syntax and typical configuration, in order to help you write your own setup, not to substitute that writing. # option definitions common to all supported networks... option domain-name example.org; Is this your domain-name? I doubt. ;-) Fill in the real one. If you don't know, ask your ISP, they should know. If they haven't given you one (typical home-network dhcpd setup with a single link to outside), invent one. Do you want/have a dns server working in your local network? option domain-name-servers ns1.example.org, ns2.example.org; So, what are your domain-name servers? Ask your ISP and use theirs, if you do not have a local dns. I usually put IP numbers here, not fqdn. default-lease-time 600; max-lease-time 7200; Ok, suit for yourself, adjust these as you wish. # Use this to enble / disable dynamic dns updates globally. #ddns-update-style none; Do you want dynamic updating of your local dns server? Probably not
Re: Make a DHCP server using Fedora - Help
Tim:
It seems pointlessly redundant to declare a subnet twice. And stranger
to declare it differently. I see no point for the first one.
Antonio Olivares:
Which one should I keep Tim, the first one or the second one?
I believe my last sentence should have answered that.
The machine that will become the server has gateway 10.154.19.1, is
it okay to make the server 10.154.19.0 ?
Addresses ending with zero or 255 (x.y.z.0 and x.y.z.255) are generally
regarded as special purpose addresses, and machines would normally be
assigned addresses from 1 to 254 as the last quad.
It's not a hard and fast rule, there are exceptions. But some things
make assumptions, and get their knickers in a twist if you try to do
otherwise.
There's two conventions of using the .1 or .254 address for your
router/gateway, but that's just a convention, and about the only thing
that insisted on one of them was the *old* Windows internet connection
sharing, that insisted on using 192.168.0.1 for the gateway PC.
Also the machine's netmask is 255.255.255.0 and the netmask of the
server should it be 255.255.255.0 or 255.255.255.254 or other thing?
If everything is actually on the same subnet (e.g, they're wired
together through a switch or router, and they can all connect to each
other without having to go through a gateway) then they should all have
the same netmask. For the average home network, using 192.168.x.y
addressing, then the 255.255.255.0 netmask suffices.
If there are separate physical networks, or you have some need to carve
up how you're using it, then you can use more restrictive netmasks, and
you may have to, for those networks to work (they need to know the
boundary between the same network and the outside network, so they can
make connections to the outside one through the gateway between them).
I would suggest that whatever PC you're running the DHCP server on
should have a fixed IP address, and for that to be fixed in your network
configuration, not trying to get the DHCP server to set its own IP
address. This, probably, also means ensuring that the NetworkManager
service is turned off, and the older network service is used.
My DHCP server still runs on a Fedora Core 4 box, and I have no
parameters set into it for what interface it listens to, there's only
one network interface on the box.
My working /etc/dhcp.conf file is below, with example.com being used as
an example domain name. It has more options than you'd need, and some
you probably should remove.
authoritative;
include /etc/rndc.key;
# (This is the same key used by BIND and the rndc tool, it's needed to
# be able to update DNS records.)
# Server configuration:
ddns-domainname example.com.;
ddns-rev-domainname in-addr.arpa.;
ddns-update-style interim;
ddns-updateson;
allow client-updates;
default-lease-time 21600; # 6 hours
max-lease-time 43200; # 12 hours
# Client configuration:
option domain-name example.com.;
option pop-server pop3.example.com;
option smtp-server smtp.example.com;
option wpad-curlcode 252 = text;
option wpad-curlhttp://proxy.example.com/wpad.dat;;
option www-server www.example.com;
option ntp-servers time.example.com;
#option time-offset 34200; # Australian Central Standard Time
option time-offset 37800; # Central Australia Daylight Time
option ip-forwardingoff;# tell clients not to act as gateways (?)
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.200; # allocate IPs within this range
option routers 192.168.0.1; # default gateway
option subnet-mask 255.255.255.0;
option broadcast-address192.168.0.255;
option domain-name-servers 192.168.0.1;
option netbios-name-servers 192.168.0.1; # WINS
option netbios-dd-server192.168.0.1; # SMB
option netbios-node-type 8;
option netbios-scope ;
option finger-server192.168.0.1;
zone 0.168.192.in-addr.arpa. {
primary 192.168.0.1;
key rndckey;
}
zone example.com. {
primary 192.168.0.1;
key rndckey;
}
}
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.27.5-37.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
On Sat, 2008-11-15 at 11:26 -0800, Antonio Olivares wrote:
--- On Sat, 11/15/08, Craig White [EMAIL PROTECTED] wrote:
/etc/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
authoritative;
log-facility local7;
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option domain-name-servers $DNS_SERVER_IP_ADDRESS_1,
$DNS_SERVER_IP_ADDRESS_2;
option domain-name $YOUR_DOMAIN_NAME;
option broadcast-address 10.154.19.31;
option subnet-mask 255.255.255.224;
option routers 10.154.19.1 ; # just a guess
ddns-updates off;
}
/etc/sysconfig/dhcpd
DHCPDARGS=eth0 # recommended
# other things to note...default and max lease times
are really short. Many more options can be added such as
WINS, NTP servers, etc.
Webmin (http://www.webmin.com) makes a lot of this
very trivial
given your other e-mail that came after I sent this which
included this
information...
eth0 Link encap:Ethernet HWaddr 00:0E:A6:42:59:AF
inet addr:10.154.19.210 Bcast:10.154.19.255
Mask:255.255.255.0
the class C subnet means that my broadcast address and
subnet masks
should match these above.
Craig
--
Thank you Craig for your input, I will change this on Monday and test it out.
So
subnet 10.154.19.0 netmask 255.255.255.254 {
should be changed to
== subnet 10.154.19.0 netmask 255.255.255.0 {
range 10.154.19.10 10.154.19.20;
option domain-name-servers $DNS_SERVER_IP_ADDRESS_1, $DNS_SERVER_IP_ADDRESS_2;
option domain-name $YOUR_DOMAIN_NAME;
option broadcast-address 10.154.19.31; to
option broadcast-address 10.154.19.255;
for $DNS_SERVER_IP_ADDRESS_1, $DNS_SERVER_IP_ADDRESS_2 should it I leave them
as is or do I put the ones that are on the host machine? or will it pick them
up automagically?
Do I need to have bind running as well?
Sorry to ask too many questions. Last time I was trying this, I tried
webmin, but I got confused with iptables and other little things. Will the
iptables part that I put in suffice also.
Thank you for your time and advice. When I get back to work on Monday, I
will try these suggestions and post back if I succeed or still have questions.
Tim gave some good advice and I was really pressed for time and wanted
to reply because you weren't getting good answers.
No - you don't need bind to run unless you want to provide DNS services.
You really need to understand networking basics...i.e. TCP/IP. One you
understand network address, broadcast address, subnet mask stuff, DHCP
is pretty easy. If you don't understand that stuff, you really don't
want to run a DHCP or BIND server and would be better off buying a
router type of appliance that will do that for you.
Craig
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Sat, 11/15/08, Craig White [EMAIL PROTECTED] wrote:
From: Craig White [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: [EMAIL PROTECTED], Community assistance, encouragement, and advice for
using Fedora. fedora-list@redhat.com
Date: Saturday, November 15, 2008, 6:43 PM
On Sat, 2008-11-15 at 11:26 -0800, Antonio Olivares wrote:
--- On Sat, 11/15/08, Craig White
[EMAIL PROTECTED] wrote:
/etc/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
authoritative;
log-facility local7;
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option domain-name-servers
$DNS_SERVER_IP_ADDRESS_1,
$DNS_SERVER_IP_ADDRESS_2;
option domain-name
$YOUR_DOMAIN_NAME;
option broadcast-address 10.154.19.31;
option subnet-mask 255.255.255.224;
option routers 10.154.19.1 ; # just a guess
ddns-updates off;
}
/etc/sysconfig/dhcpd
DHCPDARGS=eth0 # recommended
# other things to note...default and max
lease times
are really short. Many more options can be added
such as
WINS, NTP servers, etc.
Webmin (http://www.webmin.com) makes a lot
of this
very trivial
given your other e-mail that came after I sent
this which
included this
information...
eth0 Link encap:Ethernet HWaddr
00:0E:A6:42:59:AF
inet addr:10.154.19.210
Bcast:10.154.19.255
Mask:255.255.255.0
the class C subnet means that my broadcast
address and
subnet masks
should match these above.
Craig
--
Thank you Craig for your input, I will change this on
Monday and test it out.
So
subnet 10.154.19.0 netmask 255.255.255.254 {
should be changed to
== subnet 10.154.19.0 netmask 255.255.255.0 {
range 10.154.19.10 10.154.19.20;
option domain-name-servers $DNS_SERVER_IP_ADDRESS_1,
$DNS_SERVER_IP_ADDRESS_2;
option domain-name $YOUR_DOMAIN_NAME;
option broadcast-address 10.154.19.31; to
option broadcast-address 10.154.19.255;
for $DNS_SERVER_IP_ADDRESS_1, $DNS_SERVER_IP_ADDRESS_2
should it I leave them as is or do I put the ones that are
on the host machine? or will it pick them up automagically?
Do I need to have bind running as well?
Sorry to ask too many questions. Last time I was
trying this, I tried webmin, but I got confused with
iptables and other little things. Will the iptables part
that I put in suffice also.
Thank you for your time and advice. When I get back
to work on Monday, I will try these suggestions and post
back if I succeed or still have questions.
Tim gave some good advice and I was really pressed for time
and wanted
to reply because you weren't getting good answers.
No - you don't need bind to run unless you want to
provide DNS services.
You really need to understand networking basics...i.e.
TCP/IP. One you
understand network address, broadcast address, subnet mask
stuff, DHCP
is pretty easy. If you don't understand that stuff, you
really don't
want to run a DHCP or BIND server and would be better off
buying a
router type of appliance that will do that for you.
Craig
I might go to work and try it out. I will change the numbers and also add more
time in the leases. I have been given great advice by several helpful people,
notably yourself, Tim and Marko (also Paul H. for selinux denying dhpcd). I
have to make the changes in the /etc/dhcpd.conf file and try it out. I will
test with a Windows 2000 machine and a Fedora rawhide box and upon success or
failure. I will report back.
Thank you all for your help and guidance.
Regards,
Antonio
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
On Sat, 2008-11-15 at 19:43 -0700, Craig White wrote: you don't need bind to run unless you want to provide DNS services. There are advantages in doing so, but I'd learn how to do DHCP, then learn the next thing. With a local DHCP and DNS server, particular if they talk to each other, you simplify client network configuration. Your DHCP server assigns them addresses, and your DNS server reseolves all their addresses. You don't need to play with hosts files on each PC, nor any other part of their network configuration, it's all centrally managed. For anything more than a three PC LAN, it soon gets annoying if you have to keep updating all their hosts files. As Craig said, it can be simpler to use something that does that for you, such as a modem/router with its own DHCP server, there's far less things for you to have to configure. But, any of the ones that I've looked at, don't act as a local DNS server for their own DHCP records. So, you're stuck with fixing IPs in its DHCP server, then messing with hosts files on each PC. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.27.5-37.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
--- On Fri, 11/14/08, Sam Varshavchik [EMAIL PROTECTED] wrote:
From: Sam Varshavchik [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: Community assistance, encouragement, and advice for using Fedora.
fedora-list@redhat.com
Date: Friday, November 14, 2008, 5:23 PM
Antonio Olivares writes:
[EMAIL PROTECTED] network-scripts]# ifconfig -a
eth0 Link encap:Ethernet HWaddr
00:0E:A6:42:59:AFinet addr:10.154.19.210
Bcast:10.154.19.255 Mask:255.255.255.0
Your eth0 has ip 10.154.19.210
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.For
info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 class
decls to leases file.
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to
leases file. Wrote 0 leases
to leases file.
No subnet declaration for eth0 (10.154.19.210).
dhcpd is telling you, right here, what's broken.
# 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;
}
What's this? Your eth0's IP address is
10.154.19.210. You need remove all subnet declarations in
dhcp.conf, and provide a subnet declaration for
10.154.19.0/24
--
Ok,
I changed the /etc/dhcpd.conf
and I get [EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet 10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not
specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
^C
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:[FAILED]
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet 10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not
specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
but service still fails :(
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:[FAILED]
Here's file:
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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;
# Use this to enble / disable dynamic dns updates globally.
#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.154.19.0 netmask 255.255.255.0 {
}
# This is a very basic subnet declaration.
subnet 10.154.19.0 netmask 255.255.255.224 {
range 10.154.19.10 10.154.19.20;
option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
}
Thank you for helping out!
Antonio
Re: Make a DHCP server using Fedora - Help
--- On Fri, 11/14/08, Antonio Olivares [EMAIL PROTECTED] wrote:
From: Antonio Olivares [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: Community assistance, encouragement, and advice for using Fedora.
fedora-list@redhat.com
Date: Friday, November 14, 2008, 5:42 PM
--- On Fri, 11/14/08, Sam Varshavchik
[EMAIL PROTECTED] wrote:
From: Sam Varshavchik [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: Community assistance, encouragement, and
advice for using Fedora.
fedora-list@redhat.com
Date: Friday, November 14, 2008, 5:23 PM
Antonio Olivares writes:
[EMAIL PROTECTED] network-scripts]# ifconfig -a
eth0 Link encap:Ethernet HWaddr
00:0E:A6:42:59:AFinet addr:10.154.19.210
Bcast:10.154.19.255 Mask:255.255.255.0
Your eth0 has ip 10.154.19.210
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For
info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server, ldap-port
and
ldap-base-dn were not specified in the config file
Wrote 0
class
decls to leases file.
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls
to
leases file. Wrote 0
leases
to leases file.
No subnet declaration for eth0 (10.154.19.210).
dhcpd is telling you, right here, what's broken.
# 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;
}
What's this? Your eth0's IP address is
10.154.19.210. You need remove all subnet declarations
in
dhcp.conf, and provide a subnet declaration for
10.154.19.0/24
--
Ok,
I changed the /etc/dhcpd.conf
and I get [EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet
10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
^C
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet
10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
but service still fails :(
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
Here's file:
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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;
# Use this to enble / disable dynamic dns updates globally.
#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
Re: Make a DHCP server using Fedora - Help
--- On Fri, 11/14/08, Antonio Olivares [EMAIL PROTECTED] wrote:
From: Antonio Olivares [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: fedora-list@redhat.com
Date: Friday, November 14, 2008, 5:52 PM
--- On Fri, 11/14/08, Antonio Olivares
[EMAIL PROTECTED] wrote:
From: Antonio Olivares [EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora - Help
To: Community assistance, encouragement, and
advice for using Fedora.
fedora-list@redhat.com
Date: Friday, November 14, 2008, 5:42 PM
--- On Fri, 11/14/08, Sam Varshavchik
[EMAIL PROTECTED] wrote:
From: Sam Varshavchik
[EMAIL PROTECTED]
Subject: Re: Make a DHCP server using Fedora -
Help
To: Community assistance, encouragement,
and
advice for using Fedora.
fedora-list@redhat.com
Date: Friday, November 14, 2008, 5:23 PM
Antonio Olivares writes:
[EMAIL PROTECTED] network-scripts]# ifconfig
-a
eth0 Link encap:Ethernet HWaddr
00:0E:A6:42:59:AFinet
addr:10.154.19.210
Bcast:10.154.19.255 Mask:255.255.255.0
Your eth0 has ip 10.154.19.210
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server
4.0.0
Copyright 2004-2007 Internet Systems
Consortium.
All rights reserved.
For
info, please visit http://www.isc.org/sw/dhcp/
Not searching LDAP since ldap-server,
ldap-port
and
ldap-base-dn were not specified in the config
file
Wrote 0
class
decls to leases file.
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host
decls
to
leases file.
Wrote 0
leases
to leases file.
No subnet declaration for eth0
(10.154.19.210).
dhcpd is telling you, right here, what's
broken.
# 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;
}
What's this? Your eth0's IP address is
10.154.19.210. You need remove all subnet
declarations
in
dhcp.conf, and provide a subnet declaration for
10.154.19.0/24
--
Ok,
I changed the /etc/dhcpd.conf
and I get [EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet
10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
^C
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet
10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
but service still fails :(
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[FAILED]
Here's file:
[EMAIL PROTECTED] ~]# cat /etc/dhcpd.conf
# 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
Re: Make a DHCP server using Fedora - Help
--- On Fri, 11/14/08, Antonio Olivares [EMAIL PROTECTED] wrote:
Breakthrough, changed the ARGS to
[EMAIL PROTECTED] ~]$ cat /etc/sysconfig/dhcpd
# Command line options here
DHCPDARGS=eth0
and it is working :)
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet
10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
^C
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[ OK ]
but now selinux gets in the way :(
Nov 14 20:03:40 localhost kernel: type=1400
audit(1226714620.135:183): avc: denied { read } for
pid=5267 comm=dhcpd name=dhcpd.pid
dev=dm-0 ino=3244731
scontext=unconfined_u:system_r:dhcpd_t:s0
tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file
Nov 14 20:03:40 localhost kernel: type=1400
audit(1226714620.135:184): avc: denied { write } for
pid=5267 comm=dhcpd name=dhcpd.pid
dev=dm-0
ino=3244731scontext=unconfined_u:system_r:dhcpd_t:s0
tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file
Nov 14 20:03:40 localhost dhcpd: Can't create PID file
/var/run/dhcpd.pid: Permission denied.
How can I allow it to work?
Thanks,
Antonio
--
After this breakthrough I also found out or not sure here?
is that iptables are forwarding packets to eth1
upon reading another page:
http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html
it says iptables and has this part:
# Forward all packets from eth1 (internal network) to eth0 (the public internet)
iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
# Forward packets that are part of existing and related connections from eth0
to eth1
iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j
ACCEPT
# Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0
iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a.
Then it recommends visiting the other page which was referenced before.
I will probably get to this machine tomorrow or on Monday. I hope that I can
get this working and with advice from the list I believe it can get done.
Regards,
Antonio
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Make a DHCP server using Fedora - Help
Dear You,
Sorry...
What is your problem ?
Thanks !
Edward.
Antonio Olivares wrote:
--- On Fri, 11/14/08, Antonio Olivares [EMAIL PROTECTED] wrote:
Breakthrough, changed the ARGS to
[EMAIL PROTECTED] ~]$ cat /etc/sysconfig/dhcpd
# Command line options here
DHCPDARGS=eth0
and it is working :)
[EMAIL PROTECTED] ~]# dhcpd -f
Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Warning: subnet 10.154.19.0/27 overlaps subnet
10.154.19.0/24
Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
Listening on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on LPF/eth0/00:0e:a6:42:59:af/10.154.19.0/24
Sending on Socket/fallback/fallback-net
^C
[EMAIL PROTECTED] ~]# service dhcpd stop
[EMAIL PROTECTED] ~]# service dhcpd start
Starting dhcpd:
[ OK ]
but now selinux gets in the way :(
Nov 14 20:03:40 localhost kernel: type=1400
audit(1226714620.135:183): avc: denied { read } for
pid=5267 comm=dhcpd name=dhcpd.pid
dev=dm-0 ino=3244731
scontext=unconfined_u:system_r:dhcpd_t:s0
tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file
Nov 14 20:03:40 localhost kernel: type=1400
audit(1226714620.135:184): avc: denied { write } for
pid=5267 comm=dhcpd name=dhcpd.pid
dev=dm-0
ino=3244731scontext=unconfined_u:system_r:dhcpd_t:s0
tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file
Nov 14 20:03:40 localhost dhcpd: Can't create PID file
/var/run/dhcpd.pid: Permission denied.
How can I allow it to work?
Thanks,
Antonio
--
After this breakthrough I also found out or not sure here?
is that iptables are forwarding packets to eth1
upon reading another page:
http://chwang.blogspot.com/2007/11/making-linux-fedora-core-8-as-gateway.html
it says iptables and has this part:
# Forward all packets from eth1 (internal network) to eth0 (the public
internet)
iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
# Forward packets that are part of existing and related connections from eth0
to eth1
iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j
ACCEPT
# Enable SNAT functionality on eth0. a.b.c.d are generally the ip of the eth0
iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -o eth0 -j SNAT --to-source a.
Then it recommends visiting the other page which was referenced before.
I will probably get to this machine tomorrow or on Monday. I hope that I can
get this working and with advice from the list I believe it can get done.
Regards,
Antonio
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
