Dhcp: медленное получение адреса клиентами

[pmn3]

FreeBSD 8, DHCP-3,0,7. Проблема: в том что клиентские машины с ос Windows Xp медленно получают адреса(минут 15-20),Windows 7 быстрее,максимум 1 минта. обе машины подключены к одному хаббу.

[ivan2ksusr]

и что пытались сделать? что получили? логи какие нибудь покажите? сеть какая? что всего 2 машинки?

[pmn3]

2 тестовые машины

[ivan2ksusr]

информативный ответ

[Shura]

Запускай на клиенте или на сервере снифер и смотри что там происходит на самом деле.

[pmn3]

Есть сеть 192,168,1,0. на машине с FreeBSD 2 сетевые карты sis0 - 192,168,1,101 и ed0 - 192,168,13,101. DHCP нужно на sis0.
в DHCP.conf
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.13.101;
range 192.168.13.20 192.168.13.30;
}

[Stonecold]

Есть сеть 192,168,1,0. на машине с FreeBSD 2 сетевые карты sis0 - 192,168,1,101 и ed0 - 192,168,13,101. DHCP нужно на sis0.
в DHCP.conf
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.13.101;
range 192.168.13.20 192.168.13.30;
}

а ничего, что у вас subnet 192.168.1.0/24, а выдавать вы собрались айпишники из другой сети, 13.20-30? и дефолт гейтвей тоже должен быть из той же сети, что и клиентский айпи, иначе как он до него достучится?

так что либо subnet все-таки 192.168.13.0 и вешать dhcpd на ed0, либо routers 192.168.1.101, range 192.168.1.xx 192.168.1.yy

[pmn3]

там опечатка,DHCP нужно не на sis0 а на ed0 и subnet 192.168.13.0 извините что ввёл в заблуждение

[Stonecold]

ну тогда действительно - нужно больше информации. Полный конфиг dhcpd; tcpdump на ed0 интерфейсе в момент запроса айпишников клиентскими машинами

[pmn3]

конфиг

# dhcpd.conf

#

# Sample configuration file for ISC dhcpd
#

# option definitions common to all supported networks...

default-lease-time 600;

max-lease-time 7200;

#authoritative;
#ddns-update-style ad-hoc;
ddns-update-style none;

log-facility local7;

subnet 192.168.13.0 netmask 255.255.13.0 {
option routers 192.168.13.101;
option subnet-mask 255.255.13.0;
range 192.168.13.20 192.168.13.30;
}

[Shura]

1. Раскомментируй строку
authoritative

2. Что за странная маска 255.255.13.0? Может должно быть 255.255.255.0?

[pmn3]

маску поставил 255,255,255,0

08:42:50.362168 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:50.600088 IP 192.168.1.44.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
08:42:50.600191 IP 192.168.1.44.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
08:42:50.682262 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:50.683206 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:50.684628 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:50.685111 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:50.687453 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:51.114562 ARP, Request who-has 93.184.71.16 tell 192.168.1.107, length 46
08:42:51.350262 IP 192.168.1.44.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
08:42:51.350312 IP 192.168.1.44.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): REGISTRATION; REQUEST; BROADCAST
08:42:51.356247 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:51.357409 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:51.359724 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:51.360608 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:51.363454 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:51.682410 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:51.683533 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:51.684968 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:51.685778 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:51.688106 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:51.782102 STP 802.1d, Config, Flags [none], bridge-id 8000.02:21:91:0c:8b:a3.8000, length 43
08:42:52.100559 IP 192.168.1.44.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:52.100954 IP 192.168.1.44.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:52.170062 IP 192.168.13.29.4892 > 192.168.1.2.3128: Flags [S], seq 3828216028, win 65535, options [mss 1460,nop,wscale 1,nop,nop,sackOK], length 0
08:42:52.368642 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:52.369795 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:52.372084 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:52.372709 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:52.375023 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:52.682159 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:52.683095 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:52.684519 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:52.685365 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:52.687336 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:52.693882 IP 192.168.1.44.iad1 > 239.255.255.250.1900: UDP, length 133
08:42:52.900179 IP 192.168.1.154.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:53.369276 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:53.370259 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:53.413652 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:53.414308 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:53.416808 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:53.600168 IP 192.168.1.44.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:53.682043 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:53.683166 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:53.684633 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:53.685478 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:53.687477 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:53.782042 STP 802.1d, Config, Flags [none], bridge-id 8000.02:21:91:0c:8b:a3.8000, length 43
08:42:53.893700 EAPOL start (1) v2, len 0
08:42:54.414862 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:54.415840 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:54.418341 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:54.418977 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:54.422384 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:54.682154 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:54.683270 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:54.684693 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:54.685530 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:54.687333 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:55.100089 IP 192.168.1.44.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:55.133791 ARP, Request who-has 93.184.71.16 tell 192.168.1.107, length 46
08:42:55.160163 IP 192.168.13.29.4892 > 192.168.1.2.3128: Flags [S], seq 3828216028, win 65535, options [mss 1460,nop,wscale 1,nop,nop,sackOK], length 0
08:42:55.415901 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:55.417057 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:55.419354 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:55.420172 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:55.422748 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:55.681902 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:55.682837 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:55.684260 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:55.685328 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:55.687641 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:55.781943 STP 802.1d, Config, Flags [none], bridge-id 8000.02:21:91:0c:8b:a3.8000, length 43
08:42:56.124482 ARP, Request who-has 93.184.71.16 tell 192.168.1.107, length 46
08:42:56.415453 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:56.416605 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:56.418786 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:56.419617 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:56.421484 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:56.600200 IP 192.168.1.44.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:56.682025 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:56.682960 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:56.684623 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:56.685477 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:56.687813 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:57.124243 ARP, Request who-has 93.184.71.16 tell 192.168.1.107, length 46
08:42:57.415581 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:57.416939 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:57.419207 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:57.419845 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:57.422119 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:57.682104 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:57.683053 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:57.684480 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:57.685316 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:57.687630 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:57.781872 STP 802.1d, Config, Flags [none], bridge-id 8000.02:21:91:0c:8b:a3.8000, length 43
08:42:58.099985 IP 192.168.1.44.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:58.415329 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 300
08:42:58.416484 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:58.418832 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:d3:6f:9d (oui Unknown), length 320
08:42:58.419642 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:58.422206 IP 192.168.13.101.bootps > 192.168.13.25.bootpc: BOOTP/DHCP, Reply, length 300
08:42:58.681731 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 300
08:42:58.682861 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:58.684299 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:15:f2:eb:b0:3e (oui Unknown), length 313
08:42:58.685149 IP 192.168.1.4.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
08:42:58.688298 IP 192.168.13.101.bootps > 192.168.13.26.bootpc: BOOTP/DHCP, Reply, length 300
08:42:58.863017 IP 192.168.1.204.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
08:42:59.099936 IP 192.168.1.44.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)

[Mydvane]

что это?

[pmn3]

tcpdump на ed0 интерфейсе в момент запроса айпишников клиентскими машинами

[Mydvane]

таки без параметров запускали?

[pmn3]

какие параметры нужно?

[Shura]

Ну ответы клиентам идут, а вот почему компы их не понимают - хз. Ставь Wireshark, снимай трафик в нормальном формате pcap и прикрепляй сюда.

[pmn3]

то что обе сетевухи в один хаб воткнуты может как то влиять?

[Shura]

Да, может. По крайней мере настрой так, чтобы dhcp сервер только с одного интерфейса отвечал.

[pmn3]

так и настроил.непойму в чем дело,если делаю чтоб ип по первой сети раздавлись в диапазоне 1,10-1,100 то все отлично работает,в 13 подсети нихрена неработает