![]() They may release after their DHCP lease time expires. and you will get a ton of BAD_ADDRESSES in the database signifying that the IP address you have in the SCOPE is already in use. If you have a small amount of devices and a large DHCP scope, set lease time higher amount (3 days, 5 days etc). If you have many devices with a small DHCP scope, set the lease time less (4hrs, 8hrs etc). People now have cell phones and they will take your whole scope up in a second. That way each day the old devices release so new ones can get IP's. so it doesn't get full or release IP's too soon. in a few days the whole SCOPE will be full. if 30 different devices request DHCP each day. and it will stay in the DHCP database as USED. That means a machine will take that IP address for 8 or 30 days. What is your DHCP lease time? Is it a long lease time or a short lease time? it is just a simple rule of thumb so don't kill me here people. This caused problems with system identification when the mac address is used for identification.ĭHCP can be adjusted a few ways. Something comes to mind is that windows has/had a "security" feature where it would create a random mac addresses for its network adapters. So what do you really mean when you say " bunch of bad addresses" what's bad about them? Can you give an example of what bad is? The Discover and Request packets are from the client computer and the Offer and Ack/Nak is from the dhcp server. DHCP option 53 is the message type (Discover, Offer, Request, Ack/Nak or DORA).įor wireshark you either want a capture filter of "port 67 or port 68" OR if you capture everything you want a display filter of "bootp" to just display the DHCP (DORA) process. Isī = 5 suppose to show all the dhcp devices? I think is suppose to filter DHCP but in wireshark display, I only see 3 values instead of 100 DHCP devices. Virtual-Fixer wrote: I setup wireshark with filter DHCP = 53 (found in another forum).
0 Comments
Leave a Reply. |