dhcpd related issue
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
What shows tcpdump? -- Respectfully, Stanislav Putrya System administrator "RMK Kovsh" Ltd. IM: 328585847 mob. phone: +79525600664 email: root.vag...@gmail.com email: vagner_ri...@bk.ru ( ) ASCII ribbon campaign X - against HTML, vCards and / \ - proprietary attachments in e-mail ___ 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
I tried this one: # tcpdump -n -e -ttt -r /var/log/pflog port 67 reading from file /var/log/pflog, link-type PFLOG (OpenBSD pflog file) And it shows nothing. Do you have any other idea what should I try? From: Vagner To: FreeBSD questions Mail List Sent: Sat, October 31, 2009 5:09:52 PM Subject: Re: dhcpd related issue What shows tcpdump? -- Respectfully, Stanislav Putrya System administrator "RMK Kovsh" Ltd. IM: 328585847 mob. phone: +79525600664 email: root.vag...@gmail.com email: vagner_ri...@bk.ru ( ) ASCII ribbon campaign X - against HTML, vCards and / \ - proprietary attachments in e-mail ___ 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
You can analyze all the traffic going from the client to DHCP server. If this is of course really... -- Respectfully, Stanislav Putrya System administrator "RMK Kovsh" Ltd. IM: 328585847 mob. phone: +79525600664 email: root.vag...@gmail.com email: vagner_ri...@bk.ru ( ) ASCII ribbon campaign X - against HTML, vCards and / \ - proprietary attachments in e-mail ___ 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
Ok, I found this one on my Mac MacBook configd[13]: DHCP en1: INIT transmit failed I googled but yet I haven't found any good idea. From: Vagner To: FreeBSD questions Mail List Sent: Sat, October 31, 2009 7:03:54 PM Subject: Re: dhcpd related issue You can analyze all the traffic going from the client to DHCP server. If this is of course really... -- Respectfully, Stanislav Putrya System administrator "RMK Kovsh" Ltd. IM: 328585847 mob. phone: +79525600664 email: root.vag...@gmail.com email: vagner_ri...@bk.ru ( ) ASCII ribbon campaign X - against HTML, vCards and / \ - proprietary attachments in e-mail ___ 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
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"
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 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
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 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 1 Nov 2009 02:06-0800, Dánielisz László wrote:
> 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
DHCP uses UDP, telnet uses TCP, no wonder you're getting refused.
Do you have bpf (Berkeley packet filter) compiled in the kernel?
dhcpd relies on bpf. Just a thought, although dhcpd would probably
shut down if bpf is unavailable.
As others have suggested, please post the output from ifconfig rl1,
and from netstat -rnf inet.
> Than I disabled pf
> # pfctl -d
> No ALTQ support in kernel
> ALTQ related functions disabled
> pf disabled
Just another (silly) thought, does your pf setup allow UDP from
192.168.1.1:67 to *:68 over the rl1 interface?
> 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?
Did you restart dhcpd?
What's the output from fstat with respect to dhcpd?
The output should be something resembling:
dhcpddhcpd 18990 root / 2 drwxr-xr-x1024 r
dhcpddhcpd 18990 wd / 6 drwxr-xr-x1024 r
dhcpddhcpd 18990 text /usr 10505569 -rwxr-xr-x 595924 r
dhcpddhcpd 189900 /dev 14 crw-rw-rw-null rw
dhcpddhcpd 189901 /dev 14 crw-rw-rw-null rw
dhcpddhcpd 189902 /dev 14 crw-rw-rw-null rw
dhcpddhcpd 189903* local dgram c32224b4 <-> c32228bc
dhcpddhcpd 189904* internet raw icmp c32d8b2c
dhcpddhcpd 189905* internet dgram udp c3173974
dhcpddhcpd 189906 /var 70999 -rw-r--r-- 93335 w
dhcpddhcpd 189907 /dev 7 crw--- bpf rw
If you happen to have lsof installed, it should yield something like
this:
dhcpd 18990 1 dhcpd cwd VDIR 0,98 10246 /root
dhcpd 18990 1 dhcpd rtd VDIR 0,98 10242 /
dhcpd 18990 1 dhcpd txt VREG 0,106 595924 10505569
/usr/local/sbin/dhcpd
dhcpd 18990 1 dhcpd txt VREG 0,98 22013626684
/libexec/ld-elf.so.1
dhcpd 18990 1 dhcpd txt VREG 0,981143792 1327
/lib/libc.so.7
dhcpd 18990 1 dhcpd0u VCHR 0,140t0 14 /dev/null
dhcpd 18990 1 dhcpd1u VCHR 0,140t0 14 /dev/null
dhcpd 18990 1 dhcpd2u VCHR 0,140t0 14 /dev/null
dhcpd 18990 1 dhcpd3u unix 0xc31719a80t0
->0xc3171b44 (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=32768,SNDBUF=16384
SS=ISCONNECTED)
dhcpd 18990 1 dhcpd4u IPv4 0xc32d8b2c0t0 ICMP *:*
(QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=73728,SNDBUF=73728)
dhcpd 18990 1 dhcpd5u IPv4 0xc31750600t0 UDP *:bootps
(QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=262144,REUSEADDR,SNDBUF=73728)
dhcpd 18990 1 dhcpd6w VREG 0,104 9406170999 /var
(/dev/ufs/var)
dhcpd 18990 1 dhcpd7u VCHR0,7 0t267449857 /dev/bpf
HTH,
Trond.
>
> 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.
Re: dhcpd related issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 1 Nov 2009 12:30+0100, Trond Endrestøl wrote: > On Sun, 1 Nov 2009 02:06-0800, Dánielisz László wrote: > > > 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 > > DHCP uses UDP, telnet uses TCP, no wonder you're getting refused. > > Do you have bpf (Berkeley packet filter) compiled in the kernel? > dhcpd relies on bpf. Just a thought, although dhcpd would probably > shut down if bpf is unavailable. > > As others have suggested, please post the output from ifconfig rl1, > and from netstat -rnf inet. > > > Than I disabled pf > > # pfctl -d > > No ALTQ support in kernel > > ALTQ related functions disabled > > pf disabled > > Just another (silly) thought, does your pf setup allow UDP from > 192.168.1.1:67 to *:68 over the rl1 interface? Initially the DHCP client uses 0.0.0.0 as its IP address and broadcasts the DHCP requests to 255.255.255.255. I know you have disabled pf, but you should later allow the clients and dhcpd to send DHCP messages using the above addresses, i.e. dhcpd will broadcast back the offerings using its own IP-address as source (192.168.1.1 in your case) and the broadcast address 255.255.255.255 as destination. You should probably also allow for the use of 192.168.1.255 as broadcast address in your pf setup with respect to DHCP messages. More ranting on my part, Trond. > > 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? > > Did you restart dhcpd? > What's the output from fstat with respect to dhcpd? > > The output should be something resembling: > > dhcpddhcpd 18990 root / 2 drwxr-xr-x1024 r > dhcpddhcpd 18990 wd / 6 drwxr-xr-x1024 r > dhcpddhcpd 18990 text /usr 10505569 -rwxr-xr-x 595924 r > dhcpddhcpd 189900 /dev 14 crw-rw-rw-null rw > dhcpddhcpd 189901 /dev 14 crw-rw-rw-null rw > dhcpddhcpd 189902 /dev 14 crw-rw-rw-null rw > dhcpddhcpd 189903* local dgram c32224b4 <-> c32228bc > dhcpddhcpd 189904* internet raw icmp c32d8b2c > dhcpddhcpd 189905* internet dgram udp c3173974 > dhcpddhcpd 189906 /var 70999 -rw-r--r-- 93335 w > dhcpddhcpd 189907 /dev 7 crw--- bpf rw > > If you happen to have lsof installed, it should yield something like > this: > > dhcpd 18990 1 dhcpd cwd VDIR 0,98 10246 /root > dhcpd 18990 1 dhcpd rtd VDIR 0,98 10242 / > dhcpd 18990 1 dhcpd txt VREG 0,106 595924 10505569 > /usr/local/sbin/dhcpd > dhcpd 18990 1 dhcpd txt VREG 0,98 22013626684 > /libexec/ld-elf.so.1 > dhcpd 18990 1 dhcpd txt VREG 0,981143792 1327 > /lib/libc.so.7 > dhcpd 18990 1 dhcpd0u VCHR 0,140t0 14 > /dev/null > dhcpd 18990 1 dhcpd1u VCHR 0,140t0 14 > /dev/null > dhcpd 18990 1 dhcpd2u VCHR 0,140t0 14 > /dev/null > dhcpd 18990 1 dhcpd3u unix 0xc31719a80t0 > ->0xc3171b44 (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=32768,SNDBUF=16384 > SS=ISCONNECTED) > dhcpd 18990 1 dhcpd4u IPv4 0xc32d8b2c0t0 ICMP *:* > (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=73728,SNDBUF=73728) > dhcpd 18990 1 dhcpd5u IPv4 0xc31750600t0 UDP > *:bootps (QR=0 QS=0 > SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=262144,REUSEADDR,SNDBUF=73728) > dhcpd 18990 1 dhcpd6w VREG 0,104 94061 70999 /var > (/dev/ufs/var) > dhcpd 18990 1 dhcpd7u VCHR0,7 0t267449857 > /dev/bpf > > > HTH, > Trond. > > > > > 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. > >
Re: dhcpd related issue
The output of: # ifconfig rl1 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 And: # netstat -rnf inet Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default UGS 0 116905 tun0 link#4 UHS 00lo0 link#6 UHS 00 tun0 127.0.0.1 link#4 UH 0 327lo0 192.168.1.0/24 link#2 U 199038rl1 192.168.1.1link#4 UHS 00lo0 I'm usinf FreeBSD 8.0, right now I try to figure out how to check if bpf is comipled in the generic kernel; just to mention: # /usr/local/etc/rc.d/isc-dhcpd status dhcpd is running as pid 3716. From: Trond Endrestøl To: Dánielisz László Cc: freebsd-questions@freebsd.org Sent: Sun, November 1, 2009 12:30:52 PM Subject: Re: dhcpd related issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 1 Nov 2009 02:06-0800, Dánielisz László wrote: > 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 DHCP uses UDP, telnet uses TCP, no wonder you're getting refused. Do you have bpf (Berkeley packet filter) compiled in the kernel? dhcpd relies on bpf. Just a thought, although dhcpd would probably shut down if bpf is unavailable. As others have suggested, please post the output from ifconfig rl1, and from netstat -rnf inet. > Than I disabled pf > # pfctl -d > No ALTQ support in kernel > ALTQ related functions disabled > pf disabled Just another (silly) thought, does your pf setup allow UDP from 192.168.1.1:67 to *:68 over the rl1 interface? > 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? Did you restart dhcpd? What's the output from fstat with respect to dhcpd? The output should be something resembling: dhcpddhcpd 18990 root / 2 drwxr-xr-x1024 r dhcpddhcpd 18990 wd / 6 drwxr-xr-x1024 r dhcpddhcpd 18990 text /usr 10505569 -rwxr-xr-x 595924 r dhcpddhcpd 189900 /dev 14 crw-rw-rw-null rw dhcpddhcpd 189901 /dev 14 crw-rw-rw-null rw dhcpddhcpd 189902 /dev 14 crw-rw-rw-null rw dhcpddhcpd 189903* local dgram c32224b4 <-> c32228bc dhcpddhcpd 189904* internet raw icmp c32d8b2c dhcpddhcpd 189905* internet dgram udp c3173974 dhcpddhcpd 189906 /var 70999 -rw-r--r-- 93335 w dhcpddhcpd 189907 /dev 7 crw--- bpf rw If you happen to have lsof installed, it should yield something like this: dhcpd 18990 1 dhcpd cwd VDIR 0,98 10246 /root dhcpd 18990 1 dhcpd rtd VDIR 0,98 10242 / dhcpd 18990 1 dhcpd txt VREG 0,106 595924 10505569 /usr/local/sbin/dhcpd dhcpd 18990 1 dhcpd txt VREG 0,98 22013626684 /libexec/ld-elf.so.1 dhcpd 18990 1 dhcpd txt VREG 0,981143792 1327 /lib/libc.so.7 dhcpd 18990 1 dhcpd0u VCHR 0,140t0 14 /dev/null dhcpd 18990 1 dhcpd1u VCHR 0,140t0 14 /dev/null dhcpd 18990 1 dhcpd2u VCHR 0,140t0 14 /dev/null dhcpd 18990 1 dhcpd3u unix 0xc31719a80t0 ->0xc3171b44 (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=32768,SNDBUF=16384 SS=ISCONNECTED) dhcpd 18990 1 dhcpd4u IPv4 0xc32d8b2c0t0 ICMP *:* (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=73728,SNDBUF=73728) dhcpd 18990 1 dhcpd5u IPv4 0xc31750600t0 UDP *:bootps (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=262144,REUSEADDR,SNDBUF=73728) dhcpd 18990 1 dhcpd6w VREG 0,104 9406170999 /var (/dev/ufs/var) dhcpd 18990 1 dhcpd7u VCHR0,7 0t267449857 /dev/bpf HTH, Trond. > > 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 addres
Re: dhcpd related issue
Thank you Trond! True and I'll implement this to my pf.conf just first I want to make work this dhcpd :-) From: Trond Endrestøl To: Dánielisz László Cc: freebsd-questions@freebsd.org Sent: Sun, November 1, 2009 12:48:45 PM Subject: Re: dhcpd related issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 1 Nov 2009 12:30+0100, Trond Endrestøl wrote: > On Sun, 1 Nov 2009 02:06-0800, Dánielisz László wrote: > > > 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 > > DHCP uses UDP, telnet uses TCP, no wonder you're getting refused. > > Do you have bpf (Berkeley packet filter) compiled in the kernel? > dhcpd relies on bpf. Just a thought, although dhcpd would probably > shut down if bpf is unavailable. > > As others have suggested, please post the output from ifconfig rl1, > and from netstat -rnf inet. > > > Than I disabled pf > > # pfctl -d > > No ALTQ support in kernel > > ALTQ related functions disabled > > pf disabled > > Just another (silly) thought, does your pf setup allow UDP from > 192.168.1.1:67 to *:68 over the rl1 interface? Initially the DHCP client uses 0.0.0.0 as its IP address and broadcasts the DHCP requests to 255.255.255.255. I know you have disabled pf, but you should later allow the clients and dhcpd to send DHCP messages using the above addresses, i.e. dhcpd will broadcast back the offerings using its own IP-address as source (192.168.1.1 in your case) and the broadcast address 255.255.255.255 as destination. You should probably also allow for the use of 192.168.1.255 as broadcast address in your pf setup with respect to DHCP messages. More ranting on my part, Trond. > > 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? > > Did you restart dhcpd? > What's the output from fstat with respect to dhcpd? > > The output should be something resembling: > > dhcpddhcpd 18990 root / 2 drwxr-xr-x1024 r > dhcpddhcpd 18990 wd / 6 drwxr-xr-x1024 r > dhcpddhcpd 18990 text /usr 10505569 -rwxr-xr-x 595924 r > dhcpddhcpd 189900 /dev 14 crw-rw-rw-null rw > dhcpddhcpd 189901 /dev 14 crw-rw-rw-null rw > dhcpddhcpd 189902 /dev 14 crw-rw-rw-null rw > dhcpddhcpd 189903* local dgram c32224b4 <-> c32228bc > dhcpddhcpd 189904* internet raw icmp c32d8b2c > dhcpddhcpd 189905* internet dgram udp c3173974 > dhcpddhcpd 189906 /var 70999 -rw-r--r-- 93335 w > dhcpddhcpd 189907 /dev 7 crw--- bpf rw > > If you happen to have lsof installed, it should yield something like > this: > > dhcpd 18990 1 dhcpd cwd VDIR 0,98 10246 /root > dhcpd 18990 1 dhcpd rtd VDIR 0,98 10242 / > dhcpd 18990 1 dhcpd txt VREG 0,106 595924 10505569 > /usr/local/sbin/dhcpd > dhcpd 18990 1 dhcpd txt VREG 0,98 22013626684 > /libexec/ld-elf.so.1 > dhcpd 18990 1 dhcpd txt VREG 0,981143792 1327 > /lib/libc.so.7 > dhcpd 18990 1 dhcpd0u VCHR 0,140t0 14 > /dev/null > dhcpd 18990 1 dhcpd1u VCHR 0,140t0 14 > /dev/null > dhcpd 18990 1 dhcpd2u VCHR 0,140t0 14 > /dev/null > dhcpd 18990 1 dhcpd3u unix 0xc31719a80t0 > ->0xc3171b44 (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=32768,SNDBUF=16384 > SS=ISCONNECTED) > dhcpd 18990 1 dhcpd4u IPv4 0xc32d8b2c0t0 ICMP *:* > (QR=0 QS=0 SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=73728,SNDBUF=73728) > dhcpd 18990 1 dhcpd5u IPv4 0xc31750600t0 UDP > *:bootps (QR=0 QS=0 > SO=PQLEN=0,QLEN=0,QLIM=0,RCVBUF=262144,REUSEADDR,SNDBUF=73728) > dhcpd 18990 1 dhcpd6w VREG 0,104 9406170999 /var > (/dev/ufs/var) > dhcpd 18990 1 dhcpd7u VCHR0,7 0t267449857 > /dev/bpf > > > HTH, > Trond. > > > _
Re: dhcpd related issue <- solved
One of my friend brings the solution, it was reinstalling
ports/net/isc-dhcp31-server instead of ports/net/isc-dhcp30-server.
Now everything work fine!
$ sudo dhcping -v -h 00:23:6c:86:41:e3 -s 192.168.1.1
Got answer from: 192.168.1.1
# 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
20:54:15.403871 IP 192.168.1.202.68 > 192.168.1.1.67: BOOTP/DHCP, Request from
00:23:6c:86:41:e3, length 250
20:54:15.404320 IP 192.168.1.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply,
length 300
20:54:15.409016 IP 192.168.1.202.68 > 192.168.1.1.67: BOOTP/DHCP, Request from
00:23:6c:86:41:e3, length 244
20:55:19.960973 IP 192.168.1.202.68 > 192.168.1.1.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
20:55:19.963275 IP 192.168.1.1.67 > 192.168.1.202.68: BOOTP/DHCP, Reply, length
300
20:57:49.958270 IP 192.168.1.202.68 > 192.168.1.1.67: BOOTP/DHCP, Request from
00:23:6c:86:41:d9, length 300
20:57:49.960509 IP 192.168.1.1.67 > 192.168.1.202.68: BOOTP/DHCP, Reply, length
300
Thanks for all of you to your help!
Laci
From: Dánielisz László
To: Tim Judd
Cc: freebsd-questions@freebsd.org
Sent: Mon, November 2, 2009 8:49:15 PM
Subject: 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"
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"
>
__
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.
>
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ó > 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
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
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
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
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
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
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
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
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
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
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
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"
