--- 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
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
