NATing to the virtual MAC address of an HSRP group problems...

Hello
I have a problem where I need to NAT various IP addresses, and need the NATd addresses to carry the virtual MAC address of the HSRP group on the onward travels..
By default, with the Cisco 871's I'm using, the packets are NATd, but carry the MAC address of the external interface.. not the virtual MAC address.
The problem is that when I failover to the standby 871, the packets will then have the MAC address of the standby (new active) 871. This causes problems because my next hop doesn't update its ARP tables (very infrequent updates).
The next hop will accept packets NATd by the standby (now live), but will continue to send reply (eg ICMP) to the live (now standby) because it hasn't updated its ARP table.
I know that I can create a NAT pool with the virtual IP address as the only member of the pool. Packets will then have the virtual MAC address, and the problem will be fixed, but if I need to NAT IP addresses to *different* NATd addresses, then I would have to create multiple HSRP groups, with different virtual IP's and MAC's, and then create multiple NAT pools...
If I can't get my next hop (which I have minimal control over) to refresh/update it's ARP table, then I will consider the multiple HSRP group config, but before I try that I would like to know whether I would be able to have multiple virtual IP's and MAC's on a single interface. Apparently there was a problem with the Catalyst 2500/4500 series where the same MAC address would be used for all HSRP groups, and you had to use burned-in MAC addresses for HSRP groups.. which wouldn't provide a solution in this case..
Any ideas on how to fix this would be greatly appreciated. BTW I have proxy-arp on external interface, and gratuitous arp.
My software version is:
Cisco IOS Software, C870 Software (C870-ADVSECURITYK9-M), Version 12.3(8)YI1, RELEASE SOFTWARE (fc1)
Synched to technology version 12.3(10.3)T2
Many thanks,
Michael Blake.

Hello Michael,
you might want to have a look at the documents below, describing two techniques developed for the problem of NAT in an HSRP environement:
NAT Stateful Failover of Network Address Translation.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftsnat.htm
NAT Static Mapping Support with HSRP for High Availability
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ftnthsrp.htm
Regards,
GP

Similar Messages

  • Information on the Virtual IP Address of cluster resource group

    Hi,
    I would like to know how we can find a Virtual IP address of resource group. i.e. The IP address associated to the SUNW.LogicalHostname resource of the resource group.
    Is it always present in the output of the command 'ifconfig -a'?
    What is difference between IPMP and the Virtual IP Address of the resource groups? Can these IP Addresses be common / same?
    Thanks,
    Chaitanya

    Chaitanya,
    There seems to be a little confusion in your question so let me try and explain.
    Resource groups do not necessarily have to have a logical (virtual) IP address. They will only have a logical IP address if you configure on by adding a SUNW.LogicalHostname resource to the resource group. When you create that resource, you give it the hostname of the IP address you want it to control. This host name should be in the name service, i.e. /etc/hosts, NIS, DNS, LDAP.
    When you have added such a resource to a resource group (RG), bringing the RG online will result in the logical IP address being plumbed up on one of the NICs that form the IPMP group that host the relevant subnet. So, if you have two NICs (ce0, ce1) in an IPMP group that support the 129.156.10.x/24 subnet and you added a logical IP address 129.156.10.42 to RG foo-rg, then bringing foo-rg online will result in 129.156.10.42 being plumbed in on either ce0 or ce1. ifconfig -a will then show this in the output, usually as ce0:1 or ce0:2 or ce1:3, etc.
    An IPMP group is a Solaris feature that supports IP multi-pathing. It uses either ICMP probes or link detection to determine the health of a network interface. In the event that a NIC fails, the IP addresses that are hosted on that NIC are transferred to the remaining NIC. So, if your host has an IP of 129.156.10.41 plumbed on ce0 and it fails, it will be migrated to ce1.
    That's a very short description of a much more detailed topic. Please have a look at the relevant sections in the Solaris and Solaris Cluster documentation on docs.sun.com.
    Hope that helps,
    Tim
    ---

  • Configuring Virtual MAC Addresses on ASA

    Hello,
    I configure the virtual MAC address for a interface on ASA 5520, will enter the following command on the active unit:
       failover mac address Inside 0012.3456.789a 0023.4567.89ab
    The active MAC address is of the same as the Inside's burned-in MAC address of the active unit.
    Similarly, the standby MAC address is of the same as the Inside's burned-in MAC address of the standby unit.
    Do I get the effect of failover mac address command?
    Thank you for your cooperation in advance.

    Hi Bro
    That’s fine really. There’s nothing wrong if you’ve configured the active MAC address the same as the Inside's burned-in MAC address of the active unit.
    In an Active/Standby failover, the MAC addresses for the primary unit are always associated with the active IP addresses. If the secondary unit boots first and becomes active, it uses the burned-in MAC address for its interfaces. When the primary unit comes online, the secondary unit obtains the MAC addresses from the primary unit. The change can disrupt network traffic.
    You can configure virtual MAC addresses for each interface to ensure that the secondary unit uses the correct MAC addresses when it is the active unit, even if it comes online before the primary unit. If you do not specify virtual MAC addresses the failover pair uses the burned-in NIC addresses as the MAC addresses.
    P/S: If you think this comment is useful, please do rate them nicely :-)

  • Virtual MAC-Address on Solaris 10 update 9

    Hi,
    i'm installing Solaris 10 update 9 on UCS B-Series (B230 M2 or B440 M2) with M72KR-Q Adapter. We create the Service Profile with vNIC associated to vNIC Template. The vNIC Template use the MAC Pool Address configurated.
    When we run ifconfig -a on Solaris we can view only the original MAC-Address instead of Virtual MAC-Addres. Is this correct?
    Thanks in advance

    When you say the "original" MAC are you referring to the Hardware Default?
    Ensure your MAC pool has available addresses also.  You can also test unbinding the vNIC template from the Solaris service profile, and manually assigning a MAC address (watch for overlap) to the vNIC and see if that pushes to the solaris host.
    If that works, then you have a pool/template issue.  If not, we'll need to investigate further.
    Regards,
    Robert

  • Windows Network Load Balancing - Virtual MAC Address

    Hi All,
    I have environment that running 2 Exchange 2010 server with CASHT and join windows network load balancing as a node.
    My question is,
    If NLB service is restart, is it virtual MAC Address for NLB will change to new virtual MAC Address?
    Thanks for response,
    Best Regards,
    Henry Stefanus

    Hi Henry Stefanus,
    The NLB work mechanism will not change whether what higher application we used and I am not very familiar with Exchange NLB architecture, may the following KB and article
    may help you.
    When you use the unicast method, all cluster hosts share an identical unicast MAC address. Network Load Balancing overwrites the original MAC address of the cluster adapter
    with the unicast MAC address that is assigned to all the cluster hosts.
    When you use the multicast method, each cluster host retains the original MAC address of the adapter. In addition to the original MAC address of the adapter, the adapter is
    assigned a multicast MAC address, which is shared by all cluster hosts. The incoming client requests are sent to all cluster hosts by using the multicast MAC address.
    Selecting the Unicast or Multicast Method of Distributing Incoming Requests
    http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
    The related third party article:
    Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
    http://blog.morecoffeeany1.com/2010/03/19/building-nlb-exchange-2010-rtm-cas-ht-servers-hyper-v-%E2%80%93-part-1/
    I’m glad to be of help to you!
    *** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
    sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
    of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • ACE virtual mac address allocation

    We're running ACE SM and seeing all the VIP addresses, NAT addresses and alias addresses in the ARP table below  being assigned the same virtual MAC address. How then would a packet find the correct source/destination if all these MAC addresses are the same?
    IP ADDRESS      MAC-ADDRESS        Interface  Type      Encap  NextArp(s) Status
    ================================================================================
    204.107.54.1    00.24.f9.03.08.00  vlan810   GATEWAY    300    263 sec      up
    204.107.54.4    00.1e.13.3c.ab.80  vlan810   LEARNED    24     7631 sec     up
    204.107.54.5    00.1e.13.3c.a6.00  vlan810   LEARNED    331    8992 sec     up
    204.107.55.5    00.1f.ca.7b.70.23  vlan810   INTERFACE  LOCAL     _         up
    204.107.55.6    00.0b.fc.fe.1b.05  vlan810   ALIAS      LOCAL     _         up
    204.107.54.20   00.0b.fc.fe.1b.05  vlan810   VSERVER    LOCAL     _         up
    204.107.54.21   00.0b.fc.fe.1b.05  vlan810   VSERVER    LOCAL     _         up
    204.107.54.22   00.0b.fc.fe.1b.05  vlan810   VSERVER    LOCAL     _         up
    204.107.54.23   00.0b.fc.fe.1b.05  vlan810   VSERVER    LOCAL     _         up
    204.107.54.31   00.0b.fc.fe.1b.05  vlan810   VSERVER    LOCAL     _         up
    204.107.54.32   00.0b.fc.fe.1b.05  vlan810   VSERVER    LOCAL     _         up
    204.107.54.33   00.0b.fc.fe.1b.05  vlan810   VSERVER    LOCAL     _         up
    Thanks.

    ACE uses the concept of Virtual Mac Addresses , which are the addresses used for VIP addresses, NAT addresses (dynamic and static), and alias addresses These will all always use a MAC address in the following form 00.0b.fc.fe.1b.
    If you are using single ACE SM in a cat6k box, and you are seeing duplicate MAC, its normal. Cat6k Supervisor is L2 Adjacent with ACE, Any traffic received by Supervisor in VLAN 810 will be sent to ACE and then ACE will determine which VIP that packet is going to.
    Real Problem will come when you are using multiple ACE modules in Same Chassis or you are doing Chassis to Chassis ACE Redundancy. In such situation your Cat6k Switch will have duplicate MAC entries.
    To avoid this, you need to keep your Contexts in diffrent context groups in each Module i.e something like this
    ft group 5
      peer 1
      priority X
      associate-context default3
      inservice

  • How to specify in the ISE mac-address with its description?

    Hello :-)
    I want to implement ISE 1.2.
    We have a database of mac-addresses and their description (for example the phone with the Mac address, John).
    When connecting the phone John to a wifi network, WLC checks its mac-address in the database and allows access.
    How to specify in the ISE Mac address with its description?
    In the endpoint settings in ISE 1.2 there is no description field. We have ISE1.2.1.198, vWLC 8.0.100, AIR-LAP1131, MS AD (Win2003).
    How can I handle this situation? Any ideas?

    This link http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/user_guide/ise_user_guide/ise_man_network_devices.html about managing network devices(router,switch), not endpoints(phone, notebook).

  • How do i see the whole mac address for my iphone 5C?

    The Wi-Fi (MAC) address show in Setting>General>About only shows 4 pairs with ... after the 4th pair. How do I see the last two pairs? Touching the ... or anything else on the screen doesn't help.

    This is my friends iPhone and though I checked all of his settings I don't see anything turned on or checked that would make the fonts larger than normal.
    I checked this because my iPhone 6 doesn't have this problem.
    I was able to find a solution on another sight though. It was suggested that if the entire MAC address didn't show to just touch and hold the visible number until 'copy' shows. After copying the number just paste it into a text message field and the entire number then shows up. Viola!
    Its a shame that I had to spend so much time researching this to find it on a non-Apple sight to get this simple answer to a very frustrating glitch.

  • LAN and WAN share the same MAC address -- could this be a security issue?

    When I bought the AEBS(n), I was a bit surprised to see only one ethernet MAC address listed (on bottom of unit, or was it in config utility?), in addition to wireless MAC. My main router has two ethernet MACs.
    So last nite, I investigated. I confirmed my suspicion that both the WAN port and the LAN ports share the same MAC address! My setup has the AEBS WAN port plugged into my home LAN's main router, and a Linux machine plugged into a LAN port of the AEBS.
    View of AEBS WAN side (from main router at 192.168.1.1)
    ii# arp
    Seconds IP Address MAC Address
    734 66.130.224.1 001120A87AF5 -- ISP router
    789 192.168.1.21 0016CBC430A6 -- AEBS WAN port
    28 192.168.1.33 0010DC47DC53 -- home PC
    824 192.168.1.73 00065BB2F295 -- work PC
    View of AEBS LAN side (from a Linux box at 10.0.1.41)
    root@LKG7CAE25 # cat /proc/net/arp
    IP address HW type Flags HW address Mask Device
    10.0.1.1 0x1 0x2 00:16:CB:C4:30:A6 * eth0
    10.0.1.1 on the LAN side of AEBS and 192.168.1.21 on the WAN side of the AEBS both use the same MAC address, 00:16:CB:C4:30:A6.
    I tried to provoke some leakage between the two sides (for example with broadcast packets), but haven't been able to do it so yet. Perhaps the switch in front of the eth MAC has enough smarts to keep the two subnets separate? Still it sort of worries me, if I used the AEBS as my only router, that both WAN and LAN go thru the same ethernet MAC (same h/w). I browsed here but found no discussion on this.
    Comments anyone?

    .... This is why there are separate MAC addresses
    for ethernet and wireless, they are physically
    different networks. In the case of the WAN/LAN, both
    are ethernet-type networks but are physically
    distinct (this is the purpose of a router like the
    AEBS), so having the same MAC address on both sides
    won't cause any sort of collision nor should it be
    possible to leak across networks. MAC addresses can't
    be used for routing beyond the physical network.
    If it is indeed two different NICs sharing a single MAC, then indeed it is not an issue as you would never want to connect these two NICs together. But is it really two NICs?
    My worry is that these two subnets are on the same physical network, with some magic going on to keep them separate anyway. Do we have some picture of AEBS internals? Maybe that would answer the question...

  • Nexus 7k is going to be restarted if excute the claer mac address command

    Hi all,
    We are facing some issues in Nexus 7K.when we excute the clear mac address command,it is going to be restarted.
    Could you please suggest me what might be the reason ?
    Thanks & Best regards,
    Krishna Chintada

    I have no experience with Nexus but wondered if you could set the device to reload in 10 like in IOS and then clear the MAC address table.  If it didn't restart after clearing the MAC table you could do reload cancel.  Although the bigger issue still remains its probably a bug.

  • My WLan card and my Bluetooth have both the same MAC address?

    Hello dear Arch Forumers.
    I've recently purchased a brand new Sony VAIO SVF 14415. I installed Arch in Legacy BIOS mode (I didn't want to deal with the UEFI stuff and I don't use windows anyway, so I erased the complete disk and started from scratch) successfully without any glitches except for the wifi card (broadcom device) and the bluetooth device. For the wireless connection I installed the Broadcom-wl driver from AUR and worked fine, then I went after the bluetooth integration (I'm using KDE). I installed every package in the official repositories to make it work, I also enabled the systemd service for bluetooth management but no luck to get it to work...
    Then I tried with CLI tools to see if I could diagnose the problem and I noticed that both my bluetooth and wireless device have the same MAC address (see the image below).
    Even though I found something I still don't have a clue about how to proceed to make the bluetooth work. Can someone help me?
    Kind Regards!
    EDIT: I'm sorry, I just realized the last character is different in both mac addresses but the bluetooth still doesn't work.
    Last edited by Silex89 (2014-01-21 20:01:29)

    If the battery has been completely depleted on the Nano (not really a good idea) then it is going to take 15 to 30 minutes before your computer can see it. Same thing will happen with an iPod Touch.

  • How to I list the e-mail addresses in my contacts group? Mine seem to go to only the first address.

    How do I list the e-mail addresses in my contacts group? It seems to go only to the first address.

    Hi ozziejack123,
    Welcome to the Support Communities!
    The individual contacts are sorted first within the Contact application.  When you create a group in Contacts, the individual names in the group should keep the same sorting order.  Try resetting the name order for all contacts.
    Contacts (Mavericks): List contacts by first or last name
    http://support.apple.com/kb/PH15091
    Choose whether contacts’ first or last names are listed first, and whether they’re sorted by first or last name.
    Change the name order for all contacts
    Choose Contacts > Preferences, then click General.
    Select an option next to “Show first name.”
    Sort contacts
    Choose Contacts > Preferences, then click General.
    Use the Sort By menu to choose how to sort.
    I hope this information helps ....
    - Judy

  • How do i find the internet MAC address for my MBP?

    I am trying to get my MBP integrated into my home wireless network.  Need to enter MAC address.

    System Preferences > Network, select the connection type (probably Wifi). Advanced button > hardware tab.
    The MAC address is listed there.
    MAC address filtering is not actually adding any security to a wifi network, so you may want to turn that off - it is trivial to spoof a MAC address & they are visible to anyone in range. Use WPA2 with a good password if you can.

  • 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

  • How do you spoof the ethernet MAC address?

    I cant seem to get this to work...
    sudo ifconfig en0 lladdr 11:11:11:11:11:11
    ...the mac address never changes
    Message was edited by: navilon

    Threads seem to say you cant do it because of the hardware, but when I boot into windows i can do it just fine.
    any thoughts?

Maybe you are looking for