Date: Tue, 3 Nov 2009 00:25:51 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: =?ISO-8859-1?Q?D=E1nielisz_L=E1szl=F3?= <laszlo_danielisz@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: dhcpd related issue - not giving up Message-ID: <20091102234435.O35366@sola.nimnet.asn.au> In-Reply-To: <20091102120022.939F910657E4@hub.freebsd.org> References: <20091102120022.939F910657E4@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--0-1817170976-1257168351=:35366
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
In freebsd-questions Digest, Vol 283, Issue 2, Message: 4
On Mon, 2 Nov 2009 02:04:31 -0800 (PST)
Dánielisz László <laszlo_danielisz@yahoo.com> wrote:
> Sorry, I misspell it, (192.168.1.1) at 00:13:8f:86:2f:64 on rl1
> permanent [ethernet] <- actually this is my rl1 interface on BSD
Ok. Chomping heavily .. I've just reviewed this thread through four
digests, rather a top-posting, multi-tail-quoting mess. Please trim
quotes to the necessary then add your response; we've seen the rest.
> > mac# $ dhcping -h 00:23:32:dc:72:19 -s 192.168.1.1
> > no answer
> >
> > bsd# tcpdump -i rl1 -n port 67 or port 68
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> > listening on rl1, link-type EN10MB (Ethernet), capture size 96 bytes
> > 19:14:38.604545 IP 192.168.1.234.68 > 192.168.1.1.67: BOOTP/DHCP, Request
> > from 00:23:32:dc:72:19, length 250
> > 19:24:06.600131 IP 192.168.1.234.68 > 192.168.1.1.67: BOOTP/DHCP, Request
> > from 00:23:32:dc:72:19, length 250
You could perhaps usefully add 'or arp' to that tcpdump.
Like your earlier tcpdump; the Mac's asking and 192.168.1.1 is not
responding. I don't think anyone's asked yet what you get from:
# netstat -finet -an | grep 67
ie, is dhcpd really listening? something like ..
udp4 0 0 192.168.1.1.67 *.*
If not, there's your problem .. if so, looks like your firewall might be
blocking those packets from reaching 192.168.1.1 (OR its responses back)
If dhcpd is running, even if it's misconfigured, I'd expect to see some
response if it's receiving requests.
> > bsd# arp -a
> > ? (192.168.1.234) at 00:23:6c:86:41:d9 on rl1 [ethernet] <- this is my
> > MacBook
> > ? (192.168.1.1) at 00:13:8f:86:2f:64 on rl1 permanent [ethernet] <- this is
> > the layer 3 switch
> >
>
> So your switch and your rl1 interface have the same IP? That can't be good,
> can't see why it would affect things when the switch isn't in action though.
>
> # sockstat -4l | grep dhcp
> > dhcpd dhcpd 4747 7 udp4 *:67 *:*
Yeah sockstat's always useful too; both it and netstat -a will show udp
port 67 listening if dhcpd's running (right).
>From a later message ..
> pool {
> option domain-name-servers cns01.hdsnet.hu;
> max-lease-time 300;
> range 192.168.1.200 192.168.1.253;
> allow unknown-clients;
> }
> }
.. it seems from the arp -a above that the Mac already has 192.168.1.234
which is within that range? However, concentrate on getting as far as
seeing return responses from dhcpd on port 67 to clients with tcpdump,
with your firewall momentarily disabled if need be ..
HTH, Ian
--0-1817170976-1257168351=:35366--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091102234435.O35366>