Re: dhcpd related issue - not giving up
Thank you for your advice, I tried to restart dhcpd a few times and I also
tried about 10+ dhcpd.conf-s.
Right now it's reinstalling the port.
From: Tim Judd
To: Dánielisz László
Cc: freebsd-questions@freebsd.org
Sent: Mon, November 2, 2009 5:16:58 PM
Subject: Re: dhcpd related issue - not giving up
On 11/2/09, Dánielisz László wrote:
> I tried about 10 conf, here is the actual one:
>
> # cat /usr/local/etc/dhcpd.conf
> authoritative;
> ddns-update-style none;
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> option routers 192.168.1.1;
>
>
> 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 looks awkward...
I don't recall ever seeing a pool inside a subnet declaration like this.
A subnet declaration can use all the declaration in your pool.
Pure curiousity, because I am not looking up the config syntax..
comment out (or delete) the pool { and } lines only. which bring the
statements to the subnet clause.
restart dhcpd, and retry
IIRC, pools are only useful if you have two pool definitions.
thanks... hope this works.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
On 11/2/09, Dánielisz László wrote:
> I tried about 10 conf, here is the actual one:
>
> # cat /usr/local/etc/dhcpd.conf
> authoritative;
> ddns-update-style none;
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> option routers 192.168.1.1;
>
>
> 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 looks awkward...
I don't recall ever seeing a pool inside a subnet declaration like this.
A subnet declaration can use all the declaration in your pool.
Pure curiousity, because I am not looking up the config syntax..
comment out (or delete) the pool { and } lines only. which bring the
statements to the subnet clause.
restart dhcpd, and retry
IIRC, pools are only useful if you have two pool definitions.
thanks... hope this works.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
In freebsd-questions Digest, Vol 283, Issue 2, Message: 4
On Mon, 2 Nov 2009 02:04:31 -0800 (PST)
Dánielisz László 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
> > dhcpddhcpd 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___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
I tried about 10 conf, here is the actual one:
# cat /usr/local/etc/dhcpd.conf
authoritative;
ddns-update-style none;
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
pool {
option domain-name-servers cns01.hdsnet.hu;
max-lease-time 300;
range 192.168.1.200 192.168.1.253;
allow unknown-clients;
}
}
From: Tim Judd
To: Dánielisz László
Cc: freebsd-questions@freebsd.org
Sent: Mon, November 2, 2009 6:03:51 AM
Subject: Re: dhcpd related issue - not giving up
On 11/1/09, Dánielisz László wrote:
> It's the only one on the network.
Doesn't mean that it will answer.
I saw your previous posts which has the authoritative declaration.
Authoritative (from my experience) means that if a client had
previously gotten an address, a non-authoritative server won't correct
the client's lease. Think of a roaming laptop or a PDA with wifi.
An authoritative server will say "No, that won't work", then the
client will release any knowledge of the previous IP, and search for
new dhcp servers.
Since you weren't getting leases when your firewall was disabled, I
would lean toward a misconfigured dhcpd.conf. I don't think I've seen
in the same post:
ifconfig rl1
cat /usr/local/etc/dhcpd.conf
Please provide these. Thanks.
>
> From: Tim Judd
> To: Dánielisz László
> Cc: freebsd-questions@freebsd.org
> Sent: Sun, November 1, 2009 5:41:58 PM
> Subject: Re: dhcpd related issue - not giving up
>
>
>
> is your dhcpd authoritative?
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
>
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
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 From: Liontaur To: freebsd-questions@freebsd.org Sent: Mon, November 2, 2009 3:24:10 AM Subject: Re: dhcpd related issue - not giving up 2009/11/1 Dánielisz László > I also though that maybe the rl NIC can be wrong, I will try another > branded NIC as soon as it will be possible, until than I looked for arp an > socksat right after dhcp request, these are my results: > 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 > > 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 > dhcpddhcpd 4747 7 udp4 *:67 *:* > > mac# arp -a > .pool.hdsnet.hu () at 4a:55:88:7c:44:4f on tap0 > ifscope [ethernet] > bsd (192.168.1.1) at 0:13:8f:86:2f:64 on en1 ifscope [ethernet] > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
On 11/1/09, Dánielisz László wrote: > It's the only one on the network. Doesn't mean that it will answer. I saw your previous posts which has the authoritative declaration. Authoritative (from my experience) means that if a client had previously gotten an address, a non-authoritative server won't correct the client's lease. Think of a roaming laptop or a PDA with wifi. An authoritative server will say "No, that won't work", then the client will release any knowledge of the previous IP, and search for new dhcp servers. Since you weren't getting leases when your firewall was disabled, I would lean toward a misconfigured dhcpd.conf. I don't think I've seen in the same post: ifconfig rl1 cat /usr/local/etc/dhcpd.conf Please provide these. Thanks. > > From: Tim Judd > To: Dánielisz László > Cc: freebsd-questions@freebsd.org > Sent: Sun, November 1, 2009 5:41:58 PM > Subject: Re: dhcpd related issue - not giving up > > > > is your dhcpd authoritative? > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
2009/11/1 Dánielisz László > I also though that maybe the rl NIC can be wrong, I will try another > branded NIC as soon as it will be possible, until than I looked for arp an > socksat right after dhcp request, these are my results: > 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 > > 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 > dhcpddhcpd 4747 7 udp4 *:67 *:* > > mac# arp -a > .pool.hdsnet.hu () at 4a:55:88:7c:44:4f on tap0 > ifscope [ethernet] > bsd (192.168.1.1) at 0:13:8f:86:2f:64 on en1 ifscope [ethernet] > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
I also though that maybe the rl NIC can be wrong, I will try another branded NIC as soon as it will be possible, until than I looked for arp an socksat right after dhcp request, these are my results: 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 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 # sockstat -4l | grep dhcp dhcpddhcpd 4747 7 udp4 *:67 *:* mac# arp -a .pool.hdsnet.hu () at 4a:55:88:7c:44:4f on tap0 ifscope [ethernet] bsd (192.168.1.1) at 0:13:8f:86:2f:64 on en1 ifscope [ethernet] From: Michael Powell To: freebsd-questions@freebsd.org Sent: Sun, November 1, 2009 6:29:04 PM Subject: Re: dhcpd related issue - not giving up Dánielisz László wrote: > I don't give it up, doing some tcpdump on my BSD I can see the dhcp > request reaches the machine, the dhcpd is running, but why doesn't gives > any IP? > > # 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 > 11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request > from 00:24:03:f1:bd:36, length 300 11:51:45.102260 IP 0.0.0.0.68 > > 255.255.255.255.67: BOOTP/DHCP, Request from 00:24:03:f1:bd:36, length 300 [snip] I only have a couple if ideas. First, is it possible to substitute some other non rl or re NIC for rl1? I seem to recall something about these cards having some sort of problem like this. This test would eliminate that idea. Also, right after a client machine requests a lease examine your arp tables on both machines. Maybe the dhcpd server is confused and sending the reply out the wrong interface? sockstat -4l can confirm which/what interface dhcpd is listening on, compare with arp results. Theoretically if dhcpd is bound to and listening on rl1 there shouldn't be any replies going out rl0. Check to eliminate. Wrt to a managed switch blocking ports, I think you probably ruled this out by connecting the machines to each other. Note that for GigE, or NICs that do MDI-X properly any cable will work. However, on many older 100baseTX cards this would need to be using a crossover cable to function correctly. You can also broaden your tcpdump to include arp traffic. When the output files become cumbersome to examine it's easier to look at them in Wireshark. I have a hunch if rl1 could be replaced with some old fxp or sk card lying around it might work. YMMV -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
Dánielisz László wrote: > I don't give it up, doing some tcpdump on my BSD I can see the dhcp > request reaches the machine, the dhcpd is running, but why doesn't gives > any IP? > > # 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 > 11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request > from 00:24:03:f1:bd:36, length 300 11:51:45.102260 IP 0.0.0.0.68 > > 255.255.255.255.67: BOOTP/DHCP, Request from 00:24:03:f1:bd:36, length 300 [snip] I only have a couple if ideas. First, is it possible to substitute some other non rl or re NIC for rl1? I seem to recall something about these cards having some sort of problem like this. This test would eliminate that idea. Also, right after a client machine requests a lease examine your arp tables on both machines. Maybe the dhcpd server is confused and sending the reply out the wrong interface? sockstat -4l can confirm which/what interface dhcpd is listening on, compare with arp results. Theoretically if dhcpd is bound to and listening on rl1 there shouldn't be any replies going out rl0. Check to eliminate. Wrt to a managed switch blocking ports, I think you probably ruled this out by connecting the machines to each other. Note that for GigE, or NICs that do MDI-X properly any cable will work. However, on many older 100baseTX cards this would need to be using a crossover cable to function correctly. You can also broaden your tcpdump to include arp traffic. When the output files become cumbersome to examine it's easier to look at them in Wireshark. I have a hunch if rl1 could be replaced with some old fxp or sk card lying around it might work. YMMV -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
It's the only one on the network. From: Tim Judd To: Dánielisz László Cc: freebsd-questions@freebsd.org Sent: Sun, November 1, 2009 5:41:58 PM Subject: Re: dhcpd related issue - not giving up is your dhcpd authoritative? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
is your dhcpd authoritative? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
Right now I'm using a layer 3 switch but I also tried with direct UTP connection between BSD-s rl1 port and MacBook's en0 port and I experience the same. From: krad To: Dánielisz László Cc: freebsd-questions@freebsd.org Sent: Sun, November 1, 2009 1:39:13 PM Subject: Re: dhcpd related issue - not giving up 2009/11/1 Dánielisz László Well, it says: > >rl1: flags=8943 metric 0 mtu >1500 >options=8 >>ether 00:13:8f:86:2f:64 >inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 >media: Ethernet autoselect (100baseTX ) >status: active > > > > From: krad > >To: Dánielisz László > >Cc: freebsd-questions@freebsd.org >Sent: Sun, November 1, 2009 12:09:30 PM >Subject: Re: dhcpd related issue - not giving up > > > > > >2009/11/1 Dánielisz László > >>> >>I don't give it up, doing some tcpdump on my BSD I can see the dhcp request >>reaches the machine, the dhcpd is running, but why doesn't gives any IP? >> >>>># 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 >>>>11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:24:03:f1:bd:36, length 300 >>>>11:51:45.102260 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:24:03:f1:bd:36, length 300 >>>>11:51:49.114960 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:24:03:f1:bd:36, length 300 >>>>11:51:57.150734 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:24:03:f1:bd:36, length 300 >>>>11:51:59.157311 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:24:03:f1:bd:36, length 300 >>>>11:52:03.160029 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:24:03:f1:bd:36, length 300 >>>>11:57:09.770520 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:23:6c:86:41:d9, length 300 >>>>11:57:11.941379 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:23:6c:86:41:d9, length 300 >>>>11:57:14.928398 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:23:6c:86:41:d9, length 300 >>>>11:57:16.378911 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:23:6c:86:41:d9, length 300 >>>>11:57:17.703219 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:23:6c:86:41:d9, length 300 >>>>11:57:18.839763 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >>>>from 00:23:6c:86:41:d9, length 300 >> >> >> >> >> >> >>>> >>>>From: Dánielisz László >>>>To: freebsd-questions@freebsd.org >>>>Sent: Sun, November 1, 2009 11:06:36 AM >>>>Subject: Re: dhcpd related issue >> >>>>I had one more idea: try nmap on my dhcp server, and port 67 does not seems >>>>to be opened, after I tried telneting in and my connection was refused: >> >>>>$ telnet 192.168.1.1 67 >>>>Trying 192.168.1.1... >>>>telnet: connect to address 192.168.1.1: Connection refused >>>>telnet: Unable to connect to remote host >> >>>>Than I disabled pf >>>># pfctl -d >>>>No ALTQ support in kernel >>>>ALTQ related functions disabled >>>>pf disabled >> >>>>Than I checked telnet/nmap again but still don't found any 67 port ever >>>>there. I checked again that the dhcpd is running, and its up: >>>># ps ax|grep dhcp >>>> 958 ?? Is 0:00.00 /usr/local/sbin/dhcpd -cf >>>> /usr/local/etc/dhcpd.conf -lf /var/db/dhcpd/dhcpd.lease >> >>>>Any idea? >> >> >> >> >>>> >>>>From: Dánielisz László >>>>To: patrick >>>>Cc: freebsd-questions@freebsd.org >>>>Sent: Sun, November 1, 2009 8:34:03 AM >>>>Subject: Re: dhcpd related issue >> >>>>It's the same, I still don't got any IP address. >> >> >> >> >>>> >>>>From: patrick >>>>To: Dánielisz László >>>>Cc: freebsd-questions@freebsd.org >>>>Sent:
Re: dhcpd related issue - not giving up
2009/11/1 Dánielisz László > Well, it says: > > rl1: flags=8943 metric 0 > mtu 1500 > options=8 > ether 00:13:8f:86:2f:64 > inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > > -- > *From:* krad > > *To:* Dánielisz László > *Cc:* freebsd-questions@freebsd.org > *Sent:* Sun, November 1, 2009 12:09:30 PM > *Subject:* Re: dhcpd related issue - not giving up > > > > 2009/11/1 Dánielisz László > >> I don't give it up, doing some tcpdump on my BSD I can see the dhcp >> request reaches the machine, the dhcpd is running, but why doesn't gives any >> IP? >> >> # 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 >> 11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:24:03:f1:bd:36, length 300 >> 11:51:45.102260 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:24:03:f1:bd:36, length 300 >> 11:51:49.114960 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:24:03:f1:bd:36, length 300 >> 11:51:57.150734 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:24:03:f1:bd:36, length 300 >> 11:51:59.157311 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:24:03:f1:bd:36, length 300 >> 11:52:03.160029 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:24:03:f1:bd:36, length 300 >> 11:57:09.770520 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:23:6c:86:41:d9, length 300 >> 11:57:11.941379 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:23:6c:86:41:d9, length 300 >> 11:57:14.928398 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:23:6c:86:41:d9, length 300 >> 11:57:16.378911 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:23:6c:86:41:d9, length 300 >> 11:57:17.703219 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:23:6c:86:41:d9, length 300 >> 11:57:18.839763 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request >> from 00:23:6c:86:41:d9, length 300 >> >> >> >> >> >> >> >> From: Dánielisz László >> To: freebsd-questions@freebsd.org >> Sent: Sun, November 1, 2009 11:06:36 AM >> Subject: Re: dhcpd related issue >> >> I had one more idea: try nmap on my dhcp server, and port 67 does not >> seems to be opened, after I tried telneting in and my connection was >> refused: >> >> $ telnet 192.168.1.1 67 >> Trying 192.168.1.1... >> telnet: connect to address 192.168.1.1: Connection refused >> telnet: Unable to connect to remote host >> >> Than I disabled pf >> # pfctl -d >> No ALTQ support in kernel >> ALTQ related functions disabled >> pf disabled >> >> Than I checked telnet/nmap again but still don't found any 67 port ever >> there. I checked again that the dhcpd is running, and its up: >> # ps ax|grep dhcp >> 958 ?? Is 0:00.00 /usr/local/sbin/dhcpd -cf >> /usr/local/etc/dhcpd.conf -lf /var/db/dhcpd/dhcpd.lease >> >> Any idea? >> >> >> >> >> >> From: Dánielisz László >> To: patrick >> Cc: freebsd-questions@freebsd.org >> Sent: Sun, November 1, 2009 8:34:03 AM >> Subject: Re: dhcpd related issue >> >> It's the same, I still don't got any IP address. >> >> >> >> >> >> From: patrick >> To: Dánielisz László >> Cc: freebsd-questions@freebsd.org >> Sent: Sun, November 1, 2009 6:38:31 AM >> Subject: Re: dhcpd related issue >> >> What happens if you disable pf temporarily? >> >> 2009/10/31 Dánielisz László : >> > Hello, >> > >> > I just configured my dhcpd but it gives no IP-s. >> > What had I done until now: >> > >> > 1. Installed isc-dhcp via ports >> > >> > 2. edited the /usr/local/etc/dhcpd.conf >> > >> > option domain-name "bsd"; >> > option domain-name-servers ; >> > option subnet-mask 255.255.255.0; >> > authoritative; >> > >> > default-lease-time 3600; >> > max-lease-time 86400; >> > ddns-update-style none; >> > >> > subne
Re: dhcpd related issue - not giving up
Well, it says:
rl1: flags=8943 metric 0 mtu
1500
options=8
ether 00:13:8f:86:2f:64
inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255
media: Ethernet autoselect (100baseTX )
status: active
From: krad
To: Dánielisz László
Cc: freebsd-questions@freebsd.org
Sent: Sun, November 1, 2009 12:09:30 PM
Subject: Re: dhcpd related issue - not giving up
2009/11/1 Dánielisz László
>I don't give it up, doing some tcpdump on my BSD I can see the dhcp request
>reaches the machine, the dhcpd is running, but why doesn't gives any IP?
>
>># 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
>>11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:24:03:f1:bd:36, length 300
>>11:51:45.102260 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:24:03:f1:bd:36, length 300
>>11:51:49.114960 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:24:03:f1:bd:36, length 300
>>11:51:57.150734 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:24:03:f1:bd:36, length 300
>>11:51:59.157311 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:24:03:f1:bd:36, length 300
>>11:52:03.160029 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:24:03:f1:bd:36, length 300
>>11:57:09.770520 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:23:6c:86:41:d9, length 300
>>11:57:11.941379 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:23:6c:86:41:d9, length 300
>>11:57:14.928398 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:23:6c:86:41:d9, length 300
>>11:57:16.378911 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:23:6c:86:41:d9, length 300
>>11:57:17.703219 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:23:6c:86:41:d9, length 300
>>11:57:18.839763 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
>>00:23:6c:86:41:d9, length 300
>
>
>
>
>
>
>>
>>From: Dánielisz László
>>To: freebsd-questions@freebsd.org
>>Sent: Sun, November 1, 2009 11:06:36 AM
>>Subject: Re: dhcpd related issue
>
>>I had one more idea: try nmap on my dhcp server, and port 67 does not seems
>>to be opened, after I tried telneting in and my connection was refused:
>
>>$ telnet 192.168.1.1 67
>>Trying 192.168.1.1...
>>telnet: connect to address 192.168.1.1: Connection refused
>>telnet: Unable to connect to remote host
>
>>Than I disabled pf
>># pfctl -d
>>No ALTQ support in kernel
>>ALTQ related functions disabled
>>pf disabled
>
>>Than I checked telnet/nmap again but still don't found any 67 port ever
>>there. I checked again that the dhcpd is running, and its up:
>># ps ax|grep dhcp
>> 958 ?? Is 0:00.00 /usr/local/sbin/dhcpd -cf /usr/local/etc/dhcpd.conf
>> -lf /var/db/dhcpd/dhcpd.lease
>
>>Any idea?
>
>
>
>
>>
>>From: Dánielisz László
>>To: patrick
>>Cc: freebsd-questions@freebsd.org
>>Sent: Sun, November 1, 2009 8:34:03 AM
>>Subject: Re: dhcpd related issue
>
>>It's the same, I still don't got any IP address.
>
>
>
>
>>
>>From: patrick
>>To: Dánielisz László
>>Cc: freebsd-questions@freebsd.org
>>Sent: Sun, November 1, 2009 6:38:31 AM
>>Subject: Re: dhcpd related issue
>
>>What happens if you disable pf temporarily?
>
>>2009/10/31 Dánielisz László :
>>> Hello,
>>>
>>> I just configured my dhcpd but it gives no IP-s.
>>> What had I done until now:
>>>
>>> 1. Installed isc-dhcp via ports
>>>
>>> 2. edited the /usr/local/etc/dhcpd.conf
>>>
>>> option domain-name "bsd";
>>> option domain-name-servers ;
>>> option subnet-mask 255.255.255.0;
>>> authoritative;
>>>
>>> default-lease-time 3600;
>>> max-lease-time 86400;
>>> ddns-update-style none;
>>>
>>> subnet 192.168.1.0 netmask 255.255.255.0 {
>>> range 192.168.1.129 192.168.1.250;
>>> option routers 192.168.1.1;
>>> }
>>>
>>> 3. Added the following ones to /etc/rc.conf
>>> ifconfig_rl1="inet 192.168.1.1 netmask 255.255.255.0"
>>> dhcpd_enable="Y
Re: dhcpd related issue - not giving up
2009/11/1 Dánielisz László
> I don't give it up, doing some tcpdump on my BSD I can see the dhcp request
> reaches the machine, the dhcpd is running, but why doesn't gives any IP?
>
> # 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
> 11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:24:03:f1:bd:36, length 300
> 11:51:45.102260 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:24:03:f1:bd:36, length 300
> 11:51:49.114960 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:24:03:f1:bd:36, length 300
> 11:51:57.150734 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:24:03:f1:bd:36, length 300
> 11:51:59.157311 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:24:03:f1:bd:36, length 300
> 11:52:03.160029 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:24:03:f1:bd:36, length 300
> 11:57:09.770520 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:23:6c:86:41:d9, length 300
> 11:57:11.941379 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:23:6c:86:41:d9, length 300
> 11:57:14.928398 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:23:6c:86:41:d9, length 300
> 11:57:16.378911 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:23:6c:86:41:d9, length 300
> 11:57:17.703219 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:23:6c:86:41:d9, length 300
> 11:57:18.839763 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
> from 00:23:6c:86:41:d9, length 300
>
>
>
>
>
>
>
> From: Dánielisz László
> To: freebsd-questions@freebsd.org
> Sent: Sun, November 1, 2009 11:06:36 AM
> Subject: Re: dhcpd related issue
>
> I had one more idea: try nmap on my dhcp server, and port 67 does not seems
> to be opened, after I tried telneting in and my connection was refused:
>
> $ telnet 192.168.1.1 67
> Trying 192.168.1.1...
> telnet: connect to address 192.168.1.1: Connection refused
> telnet: Unable to connect to remote host
>
> Than I disabled pf
> # pfctl -d
> No ALTQ support in kernel
> ALTQ related functions disabled
> pf disabled
>
> Than I checked telnet/nmap again but still don't found any 67 port ever
> there. I checked again that the dhcpd is running, and its up:
> # ps ax|grep dhcp
> 958 ?? Is 0:00.00 /usr/local/sbin/dhcpd -cf
> /usr/local/etc/dhcpd.conf -lf /var/db/dhcpd/dhcpd.lease
>
> Any idea?
>
>
>
>
>
> From: Dánielisz László
> To: patrick
> Cc: freebsd-questions@freebsd.org
> Sent: Sun, November 1, 2009 8:34:03 AM
> Subject: Re: dhcpd related issue
>
> It's the same, I still don't got any IP address.
>
>
>
>
>
> From: patrick
> To: Dánielisz László
> Cc: freebsd-questions@freebsd.org
> Sent: Sun, November 1, 2009 6:38:31 AM
> Subject: Re: dhcpd related issue
>
> What happens if you disable pf temporarily?
>
> 2009/10/31 Dánielisz László :
> > Hello,
> >
> > I just configured my dhcpd but it gives no IP-s.
> > What had I done until now:
> >
> > 1. Installed isc-dhcp via ports
> >
> > 2. edited the /usr/local/etc/dhcpd.conf
> >
> > option domain-name "bsd";
> > option domain-name-servers ;
> > option subnet-mask 255.255.255.0;
> > authoritative;
> >
> > default-lease-time 3600;
> > max-lease-time 86400;
> > ddns-update-style none;
> >
> > subnet 192.168.1.0 netmask 255.255.255.0 {
> > range 192.168.1.129 192.168.1.250;
> > option routers 192.168.1.1;
> > }
> >
> > 3. Added the following ones to /etc/rc.conf
> > ifconfig_rl1="inet 192.168.1.1 netmask 255.255.255.0"
> > dhcpd_enable="YES"
> > dhcpd_conf="/usr/local/etc/dhcpd.conf"
> > dhcpd_ifaces="rl1"
> >
> >
> > 4. Opened the adequate port in pf
> > pass in log on rl1 inet proto tcp from 192.168.1.0/24 to 192.168.1.1
> port = bootps flags S/SA keep state
> > pass in log on rl1 inet proto udp from 192.168.1.0/24 to 192.168.1.1
> port = bootps keep state
> >
> > 5.. When I start de daemon:
> > # /usr/local/etc/rc.d/isc-dhcpd start
> > Starting dhcpd.
> > Internet Systems Consortium DHCP Server V3.0.7
> > Copyright 2004-2008 Internet Systems Consortium.
> > All rights reserved.
> > For info, please visit http://www.isc.org/sw/dhcp/
> > Wrote 0 leases to leases file.
> > Listening on Socket/rl1/192.168.1/24
> > Sending on Socket/rl1/192.168.1/24
> >
> > Everythings looks to be ok there but on the client (I tried OS-X and
> Nokia symbian) I can not obtain the IP address, do you have any idea what
> should I check?
> >
> >
> > Thanks!
> > Laci
> >
> >
> >
> > ___
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
> >
> __
Re: dhcpd related issue - not giving up
I don't give it up, doing some tcpdump on my BSD I can see the dhcp request
reaches the machine, the dhcpd is running, but why doesn't gives any IP?
# 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
11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:24:03:f1:bd:36, length 300
11:51:45.102260 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:24:03:f1:bd:36, length 300
11:51:49.114960 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:24:03:f1:bd:36, length 300
11:51:57.150734 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:24:03:f1:bd:36, length 300
11:51:59.157311 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:24:03:f1:bd:36, length 300
11:52:03.160029 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:24:03:f1:bd:36, length 300
11:57:09.770520 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
11:57:11.941379 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
11:57:14.928398 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
11:57:16.378911 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
11:57:17.703219 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
11:57:18.839763 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
From: Dánielisz László
To: freebsd-questions@freebsd.org
Sent: Sun, November 1, 2009 11:06:36 AM
Subject: Re: dhcpd related issue
I had one more idea: try nmap on my dhcp server, and port 67 does not seems to
be opened, after I tried telneting in and my connection was refused:
$ telnet 192.168.1.1 67
Trying 192.168.1.1...
telnet: connect to address 192.168.1.1: Connection refused
telnet: Unable to connect to remote host
Than I disabled pf
# pfctl -d
No ALTQ support in kernel
ALTQ related functions disabled
pf disabled
Than I checked telnet/nmap again but still don't found any 67 port ever there.
I checked again that the dhcpd is running, and its up:
# ps ax|grep dhcp
958 ?? Is 0:00.00 /usr/local/sbin/dhcpd -cf /usr/local/etc/dhcpd.conf
-lf /var/db/dhcpd/dhcpd.lease
Any idea?
From: Dánielisz László
To: patrick
Cc: freebsd-questions@freebsd.org
Sent: Sun, November 1, 2009 8:34:03 AM
Subject: Re: dhcpd related issue
It's the same, I still don't got any IP address.
From: patrick
To: Dánielisz László
Cc: freebsd-questions@freebsd.org
Sent: Sun, November 1, 2009 6:38:31 AM
Subject: Re: dhcpd related issue
What happens if you disable pf temporarily?
2009/10/31 Dánielisz László :
> Hello,
>
> I just configured my dhcpd but it gives no IP-s.
> What had I done until now:
>
> 1. Installed isc-dhcp via ports
>
> 2. edited the /usr/local/etc/dhcpd.conf
>
> option domain-name "bsd";
> option domain-name-servers ;
> option subnet-mask 255.255.255.0;
> authoritative;
>
> default-lease-time 3600;
> max-lease-time 86400;
> ddns-update-style none;
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> range 192.168.1.129 192.168.1.250;
> option routers 192.168.1.1;
> }
>
> 3. Added the following ones to /etc/rc.conf
> ifconfig_rl1="inet 192.168.1.1 netmask 255.255.255.0"
> dhcpd_enable="YES"
> dhcpd_conf="/usr/local/etc/dhcpd.conf"
> dhcpd_ifaces="rl1"
>
>
> 4. Opened the adequate port in pf
> pass in log on rl1 inet proto tcp from 192.168.1.0/24 to 192.168.1.1 port =
> bootps flags S/SA keep state
> pass in log on rl1 inet proto udp from 192.168.1.0/24 to 192.168.1.1 port =
> bootps keep state
>
> 5.. When I start de daemon:
> # /usr/local/etc/rc.d/isc-dhcpd start
> Starting dhcpd.
> Internet Systems Consortium DHCP Server V3.0.7
> Copyright 2004-2008 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
> Wrote 0 leases to leases file.
> Listening on Socket/rl1/192.168.1/24
> Sending on Socket/rl1/192.168.1/24
>
> Everythings looks to be ok there but on the client (I tried OS-X and Nokia
> symbian) I can not obtain the IP address, do you have any idea what should I
> check?
>
>
> Thanks!
> Laci
>
>
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org
