DHCP via Mac Address

I have a Cisco 831 router. I am handing out DHCP to my network via the router
ip dhcp pool HmPrivate
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 192.168.1.20
domain-name hmprivate.net
What I am trying to do is assign the same ip address to my laptop via DHCP by associating the mac address of the laptop to the DHCP ip address. This is easily done on a windows server.
I have not been able to figure it out on this router though. I have looked at the commands under the pool as well as in config mode. Nothing is jumping out at me.
Any assistance is greatly appreaciated!

Ok I powered up my laptop got an ip address from the rtr of 192.168.1.21. On the router i did a sh arp to get my hardware address of 0015.0025.60aa. I then created the new DHCP pool for the static entry. From my windows laptop i do an ipconfig / release then a ipconfig / renew. I keep getting the 192.168.1.21 address and not the 192.168.1.13 address that I want.
Am I missing something really simple here? Why wont the laptop grab the 192.168.1.13 address?
ip dhcp pool HmLaptop
host 192.168.1.13 255.255.255.0
hardware-address 0100.1500.2560.aa
default-router 192.168.1.1
dns-server 192.168.1.20
client-name dhopewell2
Here is a list of all DHCP pools on my router.
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.1 192.168.1.10
ip dhcp excluded-address 192.168.1.250 192.168.1.254
ip dhcp excluded-address 192.168.50.1 192.168.50.100
ip dhcp excluded-address 192.168.24.1 192.168.24.100
ip dhcp pool HmPrivate
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 192.168.1.20
ip dhcp pool HmWK
network 192.168.24.0 255.255.255.0
default-router 192.168.24.1
dns-server 10.0.101.12 10.0.101.13
option 150 ip 10.200.1.50 10.200.1.51
ip dhcp pool vlan10
network 192.168.50.0 255.255.255.0
default-router 192.168.1.1
dns-server 192.168.50.20
ip dhcp pool HmLaptop
host 192.168.1.13 255.255.255.0
hardware-address 0100.1500.2560.aa
default-router 192.168.1.1
dns-server 192.168.1.20
client-name dhopewell2

Similar Messages

Restricting access via MAC address?

Hello,
Could someone please tell me how to restrict access to my wireless network (and internet sharing) by only allowing computers with a certain MAC address to join?
I'm kinda stumbling around here
Thanks,
Jonny

Sorry if I wasn't being specific enough...
I have my eMac set up as a Software Base Station, which streams internet & Airtunes to an Airport Express. I have it set up this way, because my ADSL modem is connected via USB (so it's a bit of a workaround). As a result, I have Internet Sharing switched on, so I can access it from all my other macs.
What I want to do is to stop other people from accessing my eMac's internet connection. If I set up a WEP password for Internet Sharing, I lose my Airtunes facility... so I was thinking another way might be to restrict access to the connection via MAC address. I only want my other airport card-equipped macs to access the internet connection and network generally.
Surely it's possible?

Restrict printing via MAC address

I am currently using Mac OS 10.2 server and now we are considering upgrading to 10.4 because of better printer servers. We don't current use the server software for printer serves. We would like to have the ability to restrict printing to the printer via the computers MAC address. Is this possible via server 10.4?
Thanks in advance
Jason
PowerG4 dual G4 - 400mhz Mac OS X (10.2.x) OS 10.2 server

You could use the firewall to block certain IP addresses from printing.
You can ensure certain computers receive consistent IP adddresses via DHCP using Server Admin > DHCP > Settings > Static Maps which depends on MAC addresses.
hth,
b.

How to assign static ip via mac address on LINKSYS WRT54G2

? how do i assign an ip per mac address with this router? i can't seem to find the option and its becoming a real pain
on my buffalo router i can paste a mac address and assign and ip for each mac on my network

The feature that you are looking for is called "DHCP reservation". This feature is not available on the WRT54G2. Several of the newer Linksys wireless n routers support this feature.
You can assign your computer a fixed (static) LAN IP address, however, you will need to do it manually. Linksys has some very specific rules about assigning fixed LAN IP addresses. Be sure to follow them carefully.
Rules for using fixed LAN IP addresses on Linksys routers:
With Linksys routers, a fixed (static) LAN IP addresses must be assigned in the device that is using the address. So you need to enter the fixed address in the computer or printer, not in the router.
When using a Linksys router, any fixed LAN IP address must be outside the DHCP server range (typically 192.168.1.100 thru 192.168.1.149), and it cannot end in 0, 1, or 255.
Therefore any fixed LAN IP address would normally need to be in the range of
192.168.1.2 thru 192.168.1.99 or
192.168.1.150 thru 192.168.1.254
assuming you are still using the default DHCP server range.
Also, in the computer, when you set up a static LAN IP address, you would need to set the "Subnet mask" to 255.255.255.0 and the "Default Gateway" to 192.168.1.1 and "DNS server" to 192.168.1.1
It is also important that no two devices on your network be set to the same static LAN IP address.

Filtering and Monitoring via Mac-Address

Hi everyone.
Is it possible to filter and monitor a user's device via it's mac-add?
For example, I want to filter facebook and youtube in our company. I also want to have a status report regarding which mac-addresses are attempting to go into the sites that I have blocked.
Is this feasible?
Thanks in advance.

A lot depends on what systems you have and are using; but generally not directly (assuming basic systems and tools). You'd have to correlate logs and arp tables etc.
Advanced solutions such as ISE can do this but that's a much bigger discussion.

Wireless connects via MAC address, but not with essid.

I have an eee 901 using the zeneee901 kernel. I got wireless to work out of the box to an extent. This will probably be easier to exlain just posting the commands.
ifconfig ra0 up
iwlist ra0 scan
iwconfig ra0 essid *essid here*
dhcpcd ra0
TIMEOUT GOES HERE
iwconfig ra0 ap MACADDRESS
dhcpcd ra0
Connected!
This wouldn't be so bad except I can'tuse Wicd. This was happening way before I installed Wicd btw.
What's the deal?

R00KIE wrote:The way you do it I don't know, but in wicd you can select an option to associate by essid instead of mac address and it works fine for me.
Someone else might be able to answer your question. Maybe you can consider using another network connection manager, would makes things easier. Although knowing why it doesn't work is also good
That's good, but I can't find that option. Where is it?

How to look up a wireless client via MAC address

One of my AirPort Expresses shows a wireless client whose MAC address I don't recognize. Is there some utility that will show me info (manufacturer, etc) of a wireless MAC address?
Also, under what conditions would one choose to set up the Wireless Mode of an AirPort Express (Extreme) to "Extend a wireless network" and when would you choose "Participate in a WDS network"? The help files don't explain this stuff very well.

If the "g" Express is set to "join", it does not extend the wireless signal, it receives the wireless signal as if it were a computer. The idea behind "join" was to provide a means for users to stream AirTunes to a remote location with an amplifier and speakers.
If you are not using it to stream AirTunes, there's really no reason to have it powered on. As you have probably discovered, the ethernet port on the "g" Express is not active.
You'll need to recheck some settings on your main base station, the Extreme to make sure that it is setup correctly. Open AirPort Utility, click Manual Setup and click the Wireless tab below the icons. Just make sure that there is a check mark next to "Allow this network to be extended". Update to save any changes.
The "n" Express should be configured using AirPort Utility, Manual Setup, Wireless tab. Check that your Wireless Mode is "extend a wireless network" and make sure there is a check mark next to "allow wireless clients".
As you have discovered, the ethernet port is also active on the "n" Express when you have it set to "extend" and it will also stream AirTunes. Great features on the "n" Express.
You might think about adding another "n" Express to extend to another area.
Ethernet is always the best choice for speed and stability if you are able to hide the wire through the house. If it's not feasible to run an ethernet cable, take a look at ethernet powerline adapters.
You would use a pair, one device at the Extreme end and one at the other end where you want the signal to go. These devices use the home wiring to transport an ethernet signal and they work very well. Not quite as good as straight ethernet, but close and far better than wireless overall.
I bought a pair from DirecTV to setup the On Demand service because I didn't want to crawl through a hot attic to run an ethernet cable from my office router to the DVR. Much faster than wireless...and I previously had a very good wireless connection between my Time Capsule and the Express I was using to extend.
Hope you get things figured out soon.

Connecting via MAC address?

Guys,
For some strange reason, one of our suppliers needs to install a device (Nortel Meridian media card) which cannot have an IP address configured on it.
The supplier engineer swears blind that on other sites, he can connect to this device just by using MAC address.
Is there a way to communicate with this device just using destination MAC address? I have scoured the internet with no luck so far.
We have Catalyst 4507Rs with 12.2.20 IOS.
Any help greatly appreciated.

Hi,
If it cannot be configured with an IP address, what network layer protocol does it use, if any? You can certainly communicate with it, assuming that the application being used to communicate with this device uses the same upper layer protocols. As long as the ethernet headers are compliant, the switches will forward them based on what is in the mac-address-table.
HTH,
Bobby
*Please rate helpful posts.

DHCP to send different Gateways based on MAC-Addresses

Hello,
I would like to use the built-in DHCP server to send out different Gateways based on the clients' MAC-Addresses.
I have already managed to assign "static" IP-Adresses using the DHCP server to specific MAC-Adresses.
Is this possible or do I need additional software ?
thanks for your help

The basic IP networking construct here is the IP subnet (and the subnet mask); that's how you set up groups of related network hosts in an IP network. Hosts within a subnet tend to have the same DNS and gateway router and related pieces configured, and one DHCP server and such. (That's not strictly necessary, but...)
Launch Server Admin, select the DHCP service, set up subnets via the DHCP service by subnet mask, and establish DNS and default router settings there for each of the subnets.
Then set up static maps for the MAC address(es) associated with the hosts, and drop the static IP addresses into the particular subnet you want the host associated with.
You will want to leave room in the subnet for both the DHCP allocations (if any) and for the static hosts mapped into the subnet via MAC address.
There well may be a better way here, but this will get you where you want. (And the Network Services Administration manual - which you'll need to read - does seem a bit confusing around this particular sequence.)
nb: I don't have a "scratch" Leopard Server configuration handy to test and confirm this sequence.
nb: Xserve boxes require a little extra thought, given each Xserve box tends to have four MAC addresses.

Mac Address restriction

Hi there,
I have a express acting as a access point to my network for wireless devices, just wondering if anyone know if it is possible to restrict access via MAC address within the express station? This is a last attempt by me for some security as I can't get encryption to work with all devices. Any help will be good, thanks
Thanks
Connor

You can, however in my opinion it only adds a superficial level of security which can be easily broken.
Airport Admin Utility -> Configure > Access Control Tab.
It use to be useful, but MAC address access control is really no longer a real option when it comes to wireless security.
The problem arises as the MAC addresses are sent unencrypted and therefore can be picked up and read by a determined hacker.
Not only that with many ethernet devices you can now very easily change the MAC address to a different one, so making it very easy to spoof the Mac address and fool a wireless base station into believing that you are an authenticated client.
What security are you trying to configure?
WEP or WPA?
iFelix

WRT54GS: without Windows, force a given MAC address to always get the same IP address via DHCP?

I have just now set up my WRT54GS to manage my home wireless network, and it works great. I just have one question that I haven't been able to find an answer for (forgive me if I have overlooked an obvious source of information).
I have set up the WRT54GS to be a DHCP server, and it assigns addresses in an ad hoc manner to all the devices that connect to it. In general, this is what I want, but in one case, I want a certain host to always get the same IP address, for example, 192.168.1.10.
You should know that I have no Windows machines on my network. Everything is either running Linux, MacOSX, or Symbian (on a Nokia N95 handheld). Therefore, I can't set up a static IP for my device using the software supplied on the CD that comes with my router, as that software only runs under Windows.
Using a different manufacturer's router, I am able to accomplish this by telling the DHCP software on that router to always assign 192.168.1.10 to the host who connects with a certain MAC address. I can then use this mechanism to force my specific host to always get this desired IP address. However, I haven't been able to find any way to do that with the WRT54GS without the software on the Windows-based CD. Is it possible at all? If I can indeed do this without that Windows software, could someone point me to some docs which explain how to accomplish this?
... or is there perhaps a different way to cause this to happen, perhaps by means of some sort of DHCP client ID?
Thank you very much in advance for any pointers you can give me.
Message Edited by HippoMan on 10-16-2007 05:27 PM
Take a hippopotamus to lunch today.

Forget about the CD. There is nothing on the CD which you don't configure better through the router web interface at http://192.168.1.1/ You don't need the CD. Never. I have never used the CD to configure any of my routers. The program on the CD is just a software which helps you with the initial configuration of the router. It is just a software which pretty much contacts the web interface in the background and sends some settings changes there. You can do everything yourself directly. Then you know what you change.
You have to configure the static IP address on the computer and on the computer only, e.g. on your Mac use Static IP instead of DHCP in the network preferences. Enter the IP address you want to use for the computer, the subnet mask, gateway address and DNS server(s). That's it. The router is not involved in any of this.
You just have to make sure that you use an IP address inside the LAN of the router. By default, Linksys routers use the IP address 192.168.1.1 on the LAN side for the the router. The subnet mask is 255.255.255.0. The IP address together with the subnet mask says that all IP addresses 192.168.1.0-255 are considered part of the LAN. Everything else is outside and needs to be routed to the router and from there into the internet. (If you want to know how the subnet mask works exactly read the wikipedia article on it or search for "subnet calculator" or similar in the internet)
Thus, if you connect a computer to your LAN and set a static IP address on the computer it should be inside this IP address subnet/range in order to have internet and LAN access on the computer. It does not matter which address you use as long as it is inside the IP subnet. The DHCP server on the router automatically assign a correct IP address inside the IP subnet and also automatically assigns the correct gateway address (its own address = the address to which everything should be sent which does not belong into the LAN, i.e. the internet traffic) and the DNS server. With static IP you have to assign those values yourself.
But again, there is no Windows computer or CD involved to do that nor is there any configuration on the router required to set the static IP address on the Mac. The IP address you set must simply match your LAN IP which is basically defined through the settings on the router as you want to have internet and thus need access to the router and its address 192.168.1.1.
Some routers allow you define fixed IP addresses for specific devices in the DHCP server of the router. With that function you can set a fixed IP address on the router. The computer can remain on DHCP. It will always get the IP address you have configured in the list on the router through the DHCP server. However, your Linksys router does not have this option. If any device inside your LAN is supposed to receive the same IP address at any time you have to configure that on the device only.
If you have not changed the default LAN IP address, subnet mask and DHCP server settings on the router, the router has 192.168.1.1, subnet mask 255.255.255.0 and the DHCP server uses 192.168.1.100-149 for dynamic assignments. To avoid potential address conflicts you should not use any static IP addresses inside the DHCP server address pool. This leaves you with IP addresses 192.168.1.2-99 and 150-254 as static IP addresses inside your LAN. You can pick any address you like as long as any device with a static IP address has a unique IP address inside your LAN.
Assign the subnet mask 255.255.255.0 on the computer and set the default gateway to 192.168.1.1. The DNS servers are a little bit more complicated. Generally it is better and faster if you use the DNS servers of your ISP. You can, however, also use the IP address of the router 192.168.1.1 as DNS server. The router will then operate as DNS proxy, i.e. it contacts the DNS servers of your ISP for any request from your computer.
If you want to use the DNS servers of your ISP, click on the Status tab in the router web interface. It shows you the current settings of the router on the internet port. It should show you multiple entries for DNS servers. Choose those DNS server IP addresses in the computer.
If you don't want to go through the hassle with the direct access to the DNS servers of your ISP, simple use 192.168.1.1 as only DNS server on the computer.
There are all settings you have to make on your Mac or other computers to assign a static IP address. As long as the IP address is inside 192.168.1.* it belongs to the LAN and has internet access through the router (as long as the default gateway address is 192.168.1.1 of course).
Firmware is loaded either through the web interface of the router, usually somewhere on the Administration tab or with tftp. Both ways work fine on any Mac or Linux box.

WRT160N mac address to use for dhcp reservation

I have to reserve this one router's MAC address in the main router for the building. Both routers in question are WRT160Ns. The router I have to reserve's MAC address ends in 5A (on the bottom of the router, and in the ARP table when connected via wifi), but it's 5B that is listed in the DHCP resrvation table for the main router. Why is this? What should I do? I am trying to reserve it in order to keep the nettalk voIP adaptor connected to the network.

How about if you access the setup page of the 2nd router then go to the status and check the local mac address under the local network subtab. From there you will be able to compare if you have the right mac address.

I want to reserve a static IP address on my Airport extreme. What is the difference between reserving by MAC Address and DHCP Client ID?

I want to understand the differences in the way you can reserve a static address for a device on the network. I had previously set the device itself to an address and then reserved it with DHCP Client ID, which I thought was just the devices static addresss. I'm not sure if this was in fact correct or just happend to work. I know what a MAC address is, but I'm not really sure what the DHCP Client ID is. So it would be great if someone could clarify it, and the difference between reserving address by MAC Address or DHCP Client ID.

A MAC address is a unique identification consisting of letters and numbers in a form that looks like this:
xx:xx:xx:xx:xx:xx
Every network device has a MAC address, which can be found on a label on the bottom or back of the device. Apple calls this the Ethernet ID.
A DHCP Client ID is an optional name that you can assign to a device. For example, on your Mac....
Open System Preferences (gear icon on the dock)
Open Network
Click on Ethernet
Click Advanced at the lower right
You may be able to edit the DHCP Client ID here....for example.....you could enter MJ500's MacBook in the space provided. That would be the Client ID of your Mac.

DHCP Server with the strange MAC address at the same time. This MAC address is HEX IP address!

Server version: Windows server 2008 R2 Ent.
Structure of DHCP scopes: Two DHCP server 50% to 50% all allocation for per scopes.
Question: Sometimes the DHCP server
allocate the IP address at the same time to the a strange MAC address per IP address, the type is "DHCP/BOOT", it cause DHCP scopes out of space at some time point. We need clear up them manually.
I found strange MAC address in HEX is the IP address which the server allocated.
Someone meet the issues before, any solution for this ?
Thanks !
Client IP Address
Name
Lease Expiration
Type
Unique ID
10.199.190.0
10.199.190.0
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e3000
10.199.190.46
10.199.190.46
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e343600
10.199.190.59
10.199.190.59
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e353900
10.199.190.69
10.199.190.69
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e363900
10.199.190.74
10.199.190.74
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e373400
10.199.190.90
10.199.190.90
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e393000
10.199.190.101
10.199.190.101
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31303100
10.199.190.104
10.199.190.104
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31303400
10.199.190.110
10.199.190.110
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31313000
10.199.190.114
10.199.190.114
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31313400
10.199.190.117
10.199.190.117
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31313700
10.199.190.121
10.199.190.121
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31323100
10.199.190.138
10.199.190.138
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31333800
10.199.190.144
10.199.190.144
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31343400
10.199.190.153
10.199.190.153
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31353300
10.199.190.156
10.199.190.156
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31353600
10.199.190.157
10.199.190.157
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31353700
10.199.190.163
10.199.190.163
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363300
10.199.190.165
10.199.190.165
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363500
10.199.190.168
10.199.190.168
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363800
10.199.190.169
10.199.190.169
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363900
10.199.190.174
10.199.190.174
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31373400
10.199.190.177
10.199.190.177
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31373700
10.199.190.184
10.199.190.184
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31383400
10.199.190.188
10.199.190.188
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31383800
10.199.190.189
10.199.190.189
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31383900
10.199.190.192
10.199.190.192
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31393200
10.199.190.197
10.199.190.197
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31393700
10.199.190.201
10.199.190.201
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32303100
10.199.190.202
10.199.190.202
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32303200
10.199.190.209
10.199.190.209
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32303900
10.199.190.210
10.199.190.210
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313000
10.199.190.211
10.199.190.211
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313100
10.199.190.212
10.199.190.212
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313200
10.199.190.213
10.199.190.213
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313300
10.199.190.216
10.199.190.216
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313600
10.199.190.219
10.199.190.219
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313900
10.199.190.222
10.199.190.222
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323200
10.199.190.225
10.199.190.225
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323500
10.199.190.226
10.199.190.226
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323600
10.199.190.229
10.199.190.229
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323900
10.199.190.233
10.199.190.233
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32333300
10.199.190.235
10.199.190.235
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32333500
10.199.190.238
10.199.190.238
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32333800
10.199.190.240
10.199.190.240
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343000
10.199.190.242
10.199.190.242
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343200
10.199.190.243
10.199.190.243
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343300
10.199.190.246
10.199.190.246
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343600
10.199.190.249
10.199.190.249
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343900
10.199.190.251
10.199.190.251
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32353100
10.199.190.252
10.199.190.252
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32353200
10.199.190.255
10.199.190.255
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32353500
10.199.191.1
10.199.191.1
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3100
10.199.191.2
10.199.191.2
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3200
10.199.191.5
10.199.191.5
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3500
10.199.191.6
10.199.191.6
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3600
10.199.191.8
10.199.191.8
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3800
10.199.191.13
10.199.191.13
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313300
10.199.191.14
10.199.191.14
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313400
10.199.191.15
10.199.191.15
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313500
10.199.191.16
10.199.191.16
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313600
10.199.191.17
10.199.191.17
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313700
10.199.191.18
10.199.191.18
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313800
10.199.191.19
10.199.191.19
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313900
10.199.191.20
10.199.191.20
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323000
10.199.191.21
10.199.191.21
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323100
10.199.191.22
10.199.191.22
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323200
10.199.191.23
10.199.191.23
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323300
10.199.191.24
10.199.191.24
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323400
10.199.191.27
10.199.191.27
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323700
10.199.191.29
10.199.191.29
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323900
10.199.191.30
10.199.191.30
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333000
10.199.191.31
10.199.191.31
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333100
10.199.191.32
10.199.191.32
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333200
10.199.191.33
10.199.191.33
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333300
10.199.191.34
10.199.191.34
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333400
10.199.191.37
10.199.191.37
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333700
10.199.191.38
10.199.191.38
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333800
10.199.191.39
10.199.191.39
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333900
10.199.191.42
10.199.191.42
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e343200
10.199.191.44
10.199.191.44
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e343400
10.199.191.49
10.199.191.49
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e343900
10.199.191.52
10.199.191.52
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e353200
10.199.191.54
10.199.191.54
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e353400
10.199.191.56
10.199.191.56
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e353600
10.199.191.61
10.199.191.61
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363100
10.199.191.62
10.199.191.62
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363200
10.199.191.64
10.199.191.64
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363400
10.199.191.65
10.199.191.65
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363500
10.199.191.66
10.199.191.66
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363600
10.199.191.70
10.199.191.70
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373000
10.199.191.72
10.199.191.72
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373200
10.199.191.73
10.199.191.73
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373300
10.199.191.79
10.199.191.79
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373900
10.199.191.80
10.199.191.80
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383000
10.199.191.81
10.199.191.81
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383100
10.199.191.82
10.199.191.82
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383200
10.199.191.83
10.199.191.83
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383300
10.199.191.84
10.199.191.84
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383400
10.199.191.86
10.199.191.86
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383600
10.199.191.90
10.199.191.90
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393000
10.199.191.91
10.199.191.91
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393100
10.199.191.92
10.199.191.92
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393200
10.199.191.93
10.199.191.93
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393300
10.199.191.97
10.199.191.97
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393700
10.199.191.98
10.199.191.98
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393800
10.199.191.99
10.199.191.99
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393900
10.199.191.101
10.199.191.101
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303100
10.199.191.102
10.199.191.102
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303200
10.199.191.105
10.199.191.105
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303500
10.199.191.106
10.199.191.106
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303600
10.199.191.108
10.199.191.108
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303800
10.199.191.112
10.199.191.112
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313200
10.199.191.115
10.199.191.115
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313500
10.199.191.116
10.199.191.116
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313600
10.199.191.117
10.199.191.117
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313700
10.199.191.119
10.199.191.119
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313900
10.199.191.120
10.199.191.120
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31323000
10.199.191.121
10.199.191.121
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31323100
10.199.191.125
10.199.191.125
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31323500
10.199.191.133
10.199.191.133
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31333300
10.199.191.146
10.199.191.146
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31343600
10.199.191.158
10.199.191.158
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31353800
10.199.191.162
10.199.191.162
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31363200

Hi,
According your description, this may be caused by virus or malicious client.
Please try to perform a network capture on your DHCP server. Then find the device which send these malicious discover messages.
To download Network Monitor, please click the link below,
http://www.microsoft.com/en-hk/download/details.aspx?id=4865
To prevent this issue, you may implement NAP Enforcement for DHCP.
Here is a checklist of configuring NAP Enforcement for DHCP,
Checklist: Configure NAP Enforcement for DHCP
http://technet.microsoft.com/en-us/library/cc772356(v=WS.10).aspx
Hope this helps.
Steven Lee
TechNet Community Support

Using DHCP and assigning to hardware MAC-address

Hi,
Is it possible for the DHCP functionality of the Airport Extreme Base to manually assign an IP-address to the MAC-address of a computer on the network?
This is a feature that I am missing a lot.
Thanks.

mbp, Welcome to the discussion area!
Is it possible for the DHCP functionality of the Airport Extreme Base to manually assign an IP-address to the MAC-address of a computer on the network?
No, this is not a feature available from an AirPort Extreme base station (AEBS).

DHCP via Mac Address

Similar Messages

Maybe you are looking for