Daniel Bye wrote:
On Fri, Oct 24, 2008 at 11:43:32AM +0200, Svein Halvor Halvorsen wrote:
Hi,
I'm not sure if this is an issue with my dhcp server or the client, but
since I seem to get troubles with two different clients, I'm thinking it
might be the server:
I've got a FreeBSD 7.0-p4 machine running isc-dhcp3-server-3.0.5_2
serving my home network. When my Linux (Archlinux) client request
a lease, this happens:
[EMAIL PROTECTED]:~]$ dhcpcd -n eth0
eth0: dhcpcd 4.0.2 starting
eth0: broadcasting for a lease
eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball'
eth0: checking 10.0.0.176 is available on attached networks
... and then it times out, and does not configure the network. This
makes me think that there may be a client issue, since the DCHP server
does indeed offer an address. But I also have troubles with a Mac OS X
client (although it's a little more vague about the errors).
If the server is handing out /24 network prefixes, then once your clients
bind the offered address in 10.0.0/24, they can no longer communicate with
the server in 10.0.1/24.
You can
a) give the DHCP server an alias IP address in 10.0.0/24 on the
appropriate interface
b) change the network prefix to 16 bits, so that 10.0.0 and 10.0.1
(and ALL other addresses with the prefix 10.0) are in the same
logical network space
c) renumber your DHCP pool
The dhcp server has netmask /23, and are also handing out this netmask
to clients.
I have lots of clients running FreeBSD, Windows and OS X not
complaining. I do however, have one OS X client that's been constantly
complaining, and recently also an Archlinux machine. It used to work on
the Linux client up until recently.
It might be the client, in which case I should probably ask some
Lunux-folks, but since one of the apples also have a problem, I thought
I might be the server.
Can I diagnose this any further?
sv.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
