Jump to content
Калькуляторы

странность с dhcp relay

В логе имею вот это :

Feb  2 18:09:18 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via eth0
Feb  2 18:09:18 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via eth0
Feb  2 18:09:21 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via eth0
Feb  2 18:09:21 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via eth0
Feb  2 18:09:23 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via eth0
Feb  2 18:09:23 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via eth0
Feb  2 18:09:25 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:09:25 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:09:44 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:09:44 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:09:47 ibm dhcpd: DHCPREQUEST for 172.17.12.63 from 00:26:18:f1:45:bf via eth0
Feb  2 18:09:47 ibm dhcpd: DHCPACK on 172.17.12.63 to 00:26:18:f1:45:bf (nastya-pc) via eth0
Feb  2 18:09:53 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:09:53 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:09:58 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:09:58 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:10:00 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:10:00 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:10:01 ibm dhcpd: DHCPREQUEST for 172.17.12.66 from d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:10:01 ibm dhcpd: DHCPACK on 172.17.12.66 to d4:bf:7f:05:4f:0f via 172.17.12.1
Feb  2 18:10:02 ibm dhcpd: DHCPDISCOVER from d4:bf:7f:05:4f:0f via 172.17.12.1

 

плюс в dhcpd.leases несколько раз:

 

lease 172.17.12.66 {
 starts 1 2015/02/02 15:09:11;
 ends 1 2015/02/02 15:14:11;
 cltt 1 2015/02/02 15:09:11;
 binding state active;
 next binding state free;
 rewind binding state free;
 hardware ethernet d4:bf:7f:05:4f:0f;
 uid "\001\324\277\177\005O\017";
}

 

В этом же vlan есть компьютеры которые получают адрес нормально.

Из за чего может быть такая ерунда ?

Share this post


Link to post
Share on other sites

Dhcp ответ не доходит до абонента.

Проверяйте линию, MTU и firewall.

Share this post


Link to post
Share on other sites

ответ доходит, адрес назначается....

 

Тогда дампите пакеты и изучаете, почему идут повторные запросы на получение адреса.

 

Вот тема форума с похожими проблемами.

Share this post


Link to post
Share on other sites

option dhcp-server-identifier ip-address;

 

вроде помогло. Спасибо !

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this