--- On Mon, 11/17/08, Tim <ignored_mailbox@xxxxxxxxxxxx> wrote:
> From: Tim <ignored_mailbox@xxxxxxxxxxxx>
> Subject: Re: Make a DHCP server using Fedora - Help
> To: olivares14031@xxxxxxxxx, "Community assistance, encouragement, and advice for using Fedora." <fedora-list@xxxxxxxxxx>
> 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
[root@localhost ~]# 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
lo Link 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)
[root@localhost ~]#
>
> 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: <info>
> address 192.168.1.23
> Nov 18 04:28:38 laptop NetworkManager: <info>
> prefix 24 (255.255.255.0)
> Nov 18 04:28:38 laptop NetworkManager: <info>
> gateway 192.168.1.254
> Nov 18 04:28:38 laptop NetworkManager: <info>
> hostname 'laptop-wireless'
> Nov 18 04:28:38 laptop NetworkManager: <info>
> nameserver '192.168.1.2'
> Nov 18 04:28:38 laptop NetworkManager: <info>
> domain 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>
> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
> Nov 18 04:28:38 laptop NetworkManager: <info>
> Activation (wlan0) Stage 5 of 5 (IP Configure Commit)
> started...
> Nov 18 04:28:38 laptop dhclient: bound to 192.168.1.23 --
> renewal in 265422 seconds.
> Nov 18 04:28:39 laptop NetworkManager: <info>
> (wlan0): device state change: 7 -> 8
> Nov 18 04:28:39 laptop NetworkManager: <info> Policy
> set (wlan0) as default device for routing and DNS.
> Nov 18 04:28:39 laptop NetworkManager: <info>
> Activation (wlan0) successful, device activated.
> Nov 18 04:28:39 laptop NetworkManager: <info>
> Activation (wlan0) Stage 5 of 5 (IP Configure Commit)
> complete.
> Nov 18 04:28:39 laptop ntpd[2302]: Listening on interface
> #5 wlan0, 192.168.1.23#123 Enabled
> Nov 18 04:28:39 laptop NetworkManagerDispatcher: ntpd is
> running, restart
>
> Secretly, I'm glad my modem/router doesn't support
> IPv6, so my whole
> system is IPv4. IPv6 would be yet another thing to learn
> about.
>
> --
> [tim@localhost ~]$ 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 do not have a router, I only have the two nics on the host machine and a little 8 port 10/100 Networking switch which I have connected the host machine from eth1 to it and it to the machines I try to make work.
Thank you for helping.
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
