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

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

Reply to this topic

Jaguar77   

Jaguar77
Posted · Report post

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

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

vlad11   

vlad11
Posted · Report post

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

 

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

 

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

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Followers 0
Go to topic listing Программное обеспечение, биллинг и *unix системы