• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1312
  • Last Modified:

dhcpd problem (DHCPACK) OpenBSD 4.4

Hi!

I have been struggling with this very weird behaviour of DHCPd server on OpenBSD 4.4 for some low-price routers such as EUSSO, Edimax, D-Link.
DHCPd server log output seems OK (see below), but still those low-price routers get only IP address and mask, but no gateway IP adress, nor DNS IP configuration from DHCPd server. Meanwhile there is no problems with getting (FULL) IP configuration for MikroTik, OvisLink, Ubiquiti routers and even MS Windows DHCP client from OpenBSD 4.4 DHCPd server! :)

I have used the same configuration on OpenBSD 4.2 and there is no problem, but cannot get it work on OpenBSD 4.4. Why is that? What could have changed in DHCPd server since 4.2 relase?

Some of mine OpenBSD 4.4 router information below.

Thank you for your input,
Janis.
# uname -a
OpenBSD xxx.xxx.xxx.lv 4.4 GENERIC#0 i386
 
# ifconfig vlan51
vlan51: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:1b:21:1e:2b:46
        description: vlan51
        vlan: 51 priority: 0 parent interface: em1
        groups: vlan
        inet6 fe80::21b:21ff:fe1e:2b46%vlan51 prefixlen 64 scopeid 0x5
        inet 192.168.51.254 netmask 0xffffff00 broadcast 192.168.51.255
 
# cat /etc/dhcpd.conf
 
deny unknown-clients;
 
option  domain-name "oic.lv";
option  domain-name-servers 195.13.171.6, 195.13.160.52;
default-lease-time 3600;
max-lease-time 3600;
 
subnet 192.168.51.0 netmask 255.255.255.0
{
    option routers  192.168.51.254;
    host 3232248579 { hardware ethernet 00:50:18:48:CB:3D; fixed-address 192.168.51.3; }
}
 
# dhcpd -d vlan51
DHCPDISCOVER from 00:50:18:48:cb:3d via vlan51
DHCPOFFER on 192.168.51.3 to 00:50:18:48:cb:3d via vlan51
DHCPREQUEST for 192.168.51.3 from 00:50:18:48:cb:3d via vlan51
DHCPACK on 192.168.51.3 to 00:50:18:48:cb:3d via vlan51
DHCPRELEASE of 192.168.51.3 from 00:50:18:48:cb:3d via vlan51 (not found)
DHCPRELEASE of 192.168.51.3 from 00:50:18:48:cb:3d via vlan51 for nonexistent lease
DHCPDISCOVER from 00:50:18:48:cb:3d via vlan51
DHCPOFFER on 192.168.51.3 to 00:50:18:48:cb:3d via vlan51
DHCPREQUEST for 192.168.51.3 from 00:50:18:48:cb:3d via vlan51
DHCPACK on 192.168.51.3 to 00:50:18:48:cb:3d via vlan51
 
# tcpdump -enivlan51 -Xvvs9999 port 67 or port 68
tcpdump: listening on vlan51, link-type EN10MB
 
{executing RENEW from EUSSO router}
 
23:57:14.767368 00:50:18:48:cb:3d ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] xid:0x21113082 secs:63695 vend-rfc1048 DHCP:DISCOVER CID:1.0.80.24.72.203.61 RQ:192.168.51.3 HN:"Suezou^@" VC:77.83.70.84.32.57.56 PR:SM+DN+DG+NS+WNS+WNT+WSC+VO+77 (ttl 64, id 38163, len 328)
  0000: 4500 0148 9513 0000 4011 e492 0000 0000  E..H....@.ä.....
  0010: ffff ffff 0044 0043 0134 c90f 0101 0600  ????.D.C.4É.....
  0020: 2111 3082 f8cf 0000 0000 0000 0000 0000  !.0.u;L,..........
  0030: 0000 0000 0000 0000 0050 1848 cb3d 0000  .........P.HE.=..
  0040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00b0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00c0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00f0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0100: 0000 0000 0000 0000 6382 5363 3501 013d  ........c.Sc5..=
  0110: 0701 0050 1848 cb3d 3204 c0a8 3303 0c07  ...P.HE.=2.A;Ø3...
  0120: 5375 657a 6f75 003c 074d 5346 5420 3938  Suezou.<.MSFT 98
  0130: 3709 010f 0306 2c2e 2f2b 4dff 0000 0000  7.....,./+M?....
  0140: 0000 0000 0000 0000                      ........
 
23:57:14.767632 00:1b:21:1e:2b:46 00:50:18:48:cb:3d 0800 344: 192.168.51.254.67 > 192.168.51.3.68: [udp sum ok] xid:0x21113082 secs:63695 Y:192.168.51.3 S:192.168.51.254 vend-rfc1048 OO:0 DHCP:OFFER SID:192.168.51.254 LT:3600 SM:255.255.255.0 DN:"oic.lv" DG:192.168.51.254 NS:195.13.171.6,195.13.160.52 RN:1800 RB:3150 [tos 0x10] (ttl 16, id 0, len 330)
  0000: 4510 014a 0000 0000 1011 c141 c0a8 33fe  E..J......I;AA;Ø3~
  0010: c0a8 3303 0043 0044 0136 e6ce 0201 0600  A;Ø3..C.D.6e;I-....
  0020: 2111 3082 f8cf 0000 0000 0000 c0a8 3303  !.0.u;L,......A;Ø3.
  0030: c0a8 33fe 0000 0000 0050 1848 cb3d 0000  A;Ø3~.....P.HE.=..
  0040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00b0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00c0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00f0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0100: 0000 0000 0000 0000 6382 5363 3401 0035  ........c.Sc4..5
  0110: 0102 3604 c0a8 33fe 3304 0000 0e10 0104  ..6.A;Ø3~3.......
  0120: ffff ff00 0f06 6f69 632e 6c76 0003 04c0  ???...oic.lv...A;
  0130: a833 fe06 08c3 0dab 06c3 0da0 343a 0400  Ø3~..C'.«.C'. 4:..
  0140: 0007 083b 0400 000c 4eff                 ...;....N?
 
23:57:14.769245 00:50:18:48:cb:3d ff:ff:ff:ff:ff:ff 0800 348: 0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] xid:0x21113082 secs:63695 vend-rfc1048 DHCP:REQUEST CID:1.0.80.24.72.203.61 RQ:192.168.51.3 SID:192.168.51.254 HN:"Suezou^@" T81:0,83,30053,31343,29952 VC:77.83.70.84.32.57.56 PR:SM+DN+DG+NS+WNS+WNT+WSC+VO+77 (ttl 64, id 38675, len 334)
  0000: 4500 014e 9713 0000 4011 e28c 0000 0000  E..N....@.a-.....
  0010: ffff ffff 0044 0043 013a 69a2 0101 0600  ????.D.C.:i¢....
  0020: 2111 3082 f8cf 0000 0000 0000 0000 0000  !.0.u;L,..........
  0030: 0000 0000 0000 0000 0050 1848 cb3d 0000  .........P.HE.=..
  0040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00b0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00c0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00f0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0100: 0000 0000 0000 0000 6382 5363 3501 033d  ........c.Sc5..=
  0110: 0701 0050 1848 cb3d 3204 c0a8 3303 3604  ...P.HE.=2.A;Ø3.6.
  0120: c0a8 33fe 0c07 5375 657a 6f75 0051 0a00  A;Ø3~..Suezou.Q..
  0130: 0000 5375 657a 6f75 003c 074d 5346 5420  ..Suezou.<.MSFT
  0140: 3938 3709 010f 0306 2c2e 2f2b 4dff       987.....,./+M?
 
23:57:14.769440 00:1b:21:1e:2b:46 00:50:18:48:cb:3d 0800 344: 192.168.51.254.67 > 192.168.51.3.68: [udp sum ok] xid:0x21113082 secs:63695 Y:192.168.51.3 S:192.168.51.254 vend-rfc1048 OO:0 DHCP:ACK SID:192.168.51.254 LT:3600 SM:255.255.255.0 DN:"oic.lv" DG:192.168.51.254 NS:195.13.171.6,195.13.160.52 RN:1800 RB:3150 [tos 0x10] (ttl 16, id 0, len 330)
  0000: 4510 014a 0000 0000 1011 c141 c0a8 33fe  E..J......I;AA;Ø3~
  0010: c0a8 3303 0043 0044 0136 e6cb 0201 0600  A;Ø3..C.D.6e;E.....
  0020: 2111 3082 f8cf 0000 0000 0000 c0a8 3303  !.0.u;L,......A;Ø3.
  0030: c0a8 33fe 0000 0000 0050 1848 cb3d 0000  A;Ø3~.....P.HE.=..
  0040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00b0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00c0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00f0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0100: 0000 0000 0000 0000 6382 5363 3401 0035  ........c.Sc4..5
  0110: 0105 3604 c0a8 33fe 3304 0000 0e10 0104  ..6.A;Ø3~3.......
  0120: ffff ff00 0f06 6f69 632e 6c76 0003 04c0  ???...oic.lv...A;
  0130: a833 fe06 08c3 0dab 06c3 0da0 343a 0400  Ø3~..C'.«.C'. 4:..
  0140: 0007 083b 0400 000c 4eff                 ...;....N?
 
{executing RELEASE from EUSSO router}
 
23:58:43.224359 00:50:18:48:cb:3d ff:ff:ff:ff:ff:ff 0800 342: 192.168.51.3.68 > 255.255.255.255.67: [udp sum ok] xid:0x744b7101 C:192.168.51.3 vend-rfc1048 DHCP:RELEASE SID:192.168.51.254 CID:1.0.80.24.72.203.61 (ttl 64, id 45331, len 328)
  0000: 4500 0148 b113 0000 4011 d4e6 c0a8 3303  E..H±...@.O-e;A;Ø3.
  0010: ffff ffff 0044 0043 0134 bd5d 0101 0600  ????.D.C.4½]....
  0020: 744b 7101 0000 0000 c0a8 3303 0000 0000  tKq.....A;Ø3.....
  0030: 0000 0000 0000 0000 0050 1848 cb3d 0000  .........P.HE.=..
  0040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00b0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00c0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  00f0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0100: 0000 0000 0000 0000 6382 5363 3501 0736  ........c.Sc5..6
  0110: 04c0 a833 fe3d 0701 0050 1848 cb3d ff00  .A;Ø3~=...P.HE.=?.
  0120: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0130: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  0140: 0000 0000 0000 0000                      ........

Open in new window

eusso-DHCPclient-problem.PNG
0
fr0x
Asked:
fr0x
1 Solution
 
kyleb84Commented:
Here's my DHCPD.CONF file, I use it for PXE booting, when the host gets the IP address DNS and the GW are provided as well.
#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#   see 'man 5 dhcpd.conf'
#
ddns-update-style interim;
 
subnet 192.168.126.0 netmask 255.255.254.0 {
        default-lease-time 3600;
        max-lease-time 4800;
        option routers 192.168.126.1;
        option domain-name-servers 192.168.126.30;
        option subnet-mask 255.255.254.0;
        option time-offset 10;
        #option next-server 192.168.126.254;
}
 
host lexlite {
        hardware ethernet 00:40:F4:B8:EC:63;
        fixed-address 192.168.126.252;
        option host-name "pxeclient";
        filename "pxelinux.0";
}
 
host neoware {
        hardware ethernet 00:E0:C5:59:2C:95;
        fixed-address 192.168.126.253;
        option host-name "mranderson";
        filename "pxelinux.0";
}

Open in new window

0
 
gheistCommented:
Do you really need max-lease-time set?
/var/log/daemon should say something
0
 
fr0xAuthor Commented:
Couldn't find solution, so I just took src and recompiled dhcpd from www.isc.org. This solved my problem.
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now