Re: Make a DHCP server using Fedora - Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



--- On Wed, 11/19/08, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:

> From: Antonio Olivares <olivares14031@xxxxxxxxx>
> Subject: Re: Make a DHCP server using Fedora - Help
> To: fedora-list@xxxxxxxxxx, vmarko@xxxxxxxxxxxx
> Date: Wednesday, November 19, 2008, 5:24 AM
> --- On Tue, 11/18/08, Marko Vojinovic
> <vvmarko@xxxxxxxx> wrote:
> 
> > From: Marko Vojinovic <vvmarko@xxxxxxxx>
> > Subject: Re: Make a DHCP server using Fedora - Help
> > To: fedora-list@xxxxxxxxxx
> > Cc: olivares14031@xxxxxxxxx
> > 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: 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.  

Regards,

Antonio 


      

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux