Win 10 x64.

1. Open Mac Command Line
2. Eeupdate Linux

A guest Jun 24th, 2017 278 Never Not a member of Pastebin yet?. If you run EEUPDATE without any command line options, EEUPDATE will display. Based on the last 8 bytes of your Intel Network adapter's MAC Address. For example, if your MAC Address was '00AA11223344', EEUPDATE would create the.

I have an old software licence that is locked to a MAC address. If I create a VM, and use the Host to define the MAC address on the vNIC, then the software activates normally.

If I use the 'Network Address' feature of the vNIC settings to change the MAC, the software somehow figures out the NIC's real MAC and won't activate.

In the end, this solution needs to run on a real PC with a real NIC.

How do I change the MAC on a real NIC in such a way that the software can't read the real MAC. Or how do I install a fake NIC with the MAC address I need for the software to attach to?

(I've installed the MS Loopback Adapter, and set the MAC, but the sofware still finds the 'real' MAC on the adapter).

2 Answers

It sounds like your software is not actually changing the MAC address of the NIC, only the packets it sends. If and how you can change the MAC depends entirely on the model and firmware. Sometimes (not often)you can change onboard NIC mac addresses in BIOS.

If your current card/NIC cant be reprogrammed, you may be able to purchase a second cheapo card which can be flashed. The model might depend on your pc and available slots, but you want one which supports the 'clone mac' function.

Also, if your computer has a WIFI interface you may be able to use the clone mac function on that.

OK, found one of the tools. EEUPDATE is an Intel tool for OEMs to set MAC addresses on system build. I assume such a tool exists for most brands of cards. Tool is OEM only, so need to sign an agreement. Thanks folk!

Open Mac Command Line

Eeupdate Linux

Not the answer you're looking for? Browse other questions tagged networkingmacnetwork-adapter or ask your own question.

1. Contents
2. - RUNNING THE UTILITY
3. - BASIC USAGE GUIDELINES
4. - EEPROM/NVM VERIFICATION
5. - MAC ADDRESS FILE FORMAT
6. - EXAMPLES
7. - INSTALLATION
8. -LEGAL
9. EEUpdate is the EEPROM Update Utility. Allows manufacturing programming of
10. EEPROMs, in cases where EEPROM is not preprogrammed, or programmed
11. RUNNING THE UTILITY
12. Using the '/?' option will display a list of supported command line options.
13. NOTE: EEPROM checksums and CRCs are automatically updated with any
14. --------
15. EEUPDATE can be run with any of the following command line options:
16. /HELP or /?
17. Programs the EEPROM with only the MAC address from
18. EEPROM.
19. /ADAPTERRESET
20. *CAUTION* This will unload the driver for this device if present.
21. /ALL
22. Selects PCI bus of adapter to program. Must be used with the DEV
23. Forces the EEPROM checksum and CRCs to be updated.
24. /CB <offset> <bitmask>
25. Clears bits in the EEPROM, specified in <bitmask>.
26. /D <imagefile> or
27. Programs the EEPROM with the contents of <imagefile> without
28. Forces debug update to be used where applicable. Must be used with /D
29. or /DATA switch. This option is only for use in an emergency. Do not
30. Log debug messages into the debugfile.
31. /DEV=XX
32. Selects PCI device of the adapter to program. Must be used with the
33. 4 hex digit device id of card to program.
34. /DUMP
35. Displays the version of the EEPROM image.
36. /EXITCODES
37. Selects PCI function of the adapter to program. Must be used with both
38. the BUS and DEV parameters to specify an adapter.
39. /GUI [/HELP]
40. Brings up GUI mode. /HELP is optional and displays the GUI Help.
41. /IDFLASH
42. Dumps the contents of the INVM to the file <mac_address>_otp, where
43. Checks if data stored in the INVM is protected against write attempts.
44. /INVMLOCK [/FORCE]
45. Locks the data stored in the INVM against all future write attempts.
46. This option requires user confirmation. Using /FORCE when calling
47. INVMLOCK from a script will not display the confirmation and will not
48. Compares the free space in the INVM to the data contained in <config_file>.
49. Returns the free space that would remain if the <config_file> were applied.
50. /INVMUPDATE /FILE=<config_file>
51. Programs the INVM with the contents of <config_file>.
52. /INVMVERIFY /FILE=<config_file>
53. Compares the configuration data stored in the INVM with the configuration
54. defined in the <config_file> file. Returns the differences and displays
55. Displays the INVM version information. A value of '00.0-0' indicates an
56. empty or invalid version. 'Unsupported' indicates the device does not
57. Preserves some user data during an EEPROM upgrade. Preserved data includes
58. the device's Alternate MAC Address and PXE configuration words, however
59. Programs the EEPROM with only the MAC address of macaddr without changing
60. the rest of the EEPROM. /NUM is optional and applicable only to multi
61. Displays the adapter LAN MAC address.
62. /MAC_DUMP_FILE
63. Dumps the MAC address to a file usable by the /A command.
64. /NIC=XX
65. When programming an image for devices that support NVM protection,
66. prevents protection from being enabled. This switch must be used
67. with the /DATA command and has no effect on NVM devices that are
68. Displays the PCI information of the adapter.
69. /PF_MAC=macaddr /NUM=PF_num
70. Programs the dedicated MAC address of a specified Physical Function
71. This allows altering the mac addresses of inactive functions of a
72. Display MAC address of a selected Physical Function of the
73. specified NIC. This allows dumping MAC addresses of inactive functions
74. Programs the dedicated Port MAC address without changing the rest of the
75. EEPROM. /NUM is optional and applicable only to multi function adapters.
76. Display the adapter port MAC address. /NUM is optional and applicable only
77. to multi function adapters. Valid value range is 0 to 15.
78. /RW <word>
79. Programs the dedicated SAN MAC address with the MAC address from <addrfile>.
80. /SANMAC=macaddr
81. Programs the dedicated SAN MAC address without changing the rest of
82. Displays the dedicated MAC address for the SAN.
83. /SB <offset> <bitmask>
84. Programs the dedicated PCIe serial MAC address without changing the rest
85. Display the adapter PCIe serial MAC address.
86. /SUBDEVICE=<pci subsystem device ID>
87. 4 hex digit subsystem device id of card to program.
88. /TEST
89. Displays version and the diagnostic library information.
90. /WW <word> <value>
91. Verifies the eeprom image in eeprom to the target file
92. BASIC USAGE GUIDELINES
93. To display a list of installed adapters call EEUPDATE without any parameters
94. EEUPDATE will display a list of network adapters installed in the
95. [EEUPDATE ver 5.0.1.0] - Intel PCI NIC EEPROM Utility
96. Intel (R) Confidential and not for general distribution.
97. Warning: No Adapter Selected
98. NIC Bus Dev Fun Vendor-Device Branding string
99. 1 1 00 00 8086-1008 Intel(R) PRO/1000 XT Server Adapter
100. 2 1 08 00 8086-1039 Intel(R) PRO/100 VE Network Connection
101. To perform an operation on an installed network adapter you must specify
102. the '/NIC=' parameter. For example, to perform an EEPROM dump on NIC 3
103. Alternatively you may specify the '/BUS=' and '/DEV=' parameters instead of the
104. '/NIC=' parameter to specify which network adapter to select. For example
105. to program NIC 1 from the list above with the EEPROM image file 'image.eep'
106. EEPROM IMAGE FILE FORMAT
107. The <imagefile> parameter designates either a text file or a binary file. The
108. text file contains hexadecimal values with which to program the EEPROM. Each
109. value should consist of up to four hex digits separated by a space or newline.
110. The data contained in <imagefile> must be formatted the same as the EEPROM
111. imagefile produced by the '/dump' parameter. An imagefile produced by the
112. '/dump' parameter may be used to program the EEPROM. Comments may be added
113. to the EEPROM image file as long as they are preceded by a semicolon ';'.
114. Binary files are also accepted for NVM updates. A binary file can be either
115. NOTE: When programming the EEPROM using the '/DATA' parameter, EEupdate will
116. ignore the MAC Address (first 6 bytes), and EEPROM checksum (last 2 bytes).
117. However, the MAC Address and checksum locations in the EEPROM image file
118. EEPROM/NVM VERIFICATION
119. The EEPROM or NVM can be verified against an image file.
120. On devices that support EEPROM images, the following are verified:
121. - EEPROM version
122. - VendorID (if it exists).
123. On devices that support NVM images, all modules are verified except the Shadow
124. For the I210 adapter family, the Shadow RAM is verified except for the
125. - MAC address
126. - Flash Device Size
127. - PXE settings (Setup Options and Configuration Customization Options)
128. - OEM VPD area
129. INVM FILE FORMAT
130. The <config_file> is a text file that stores sets of configuration entries and their
131. values. These pairs are used to program the INVM with options such as MAC address,
132. LEDs configuration, device ID and WoL behavior. Values can be changed only if the
133. INVM has enough free locations available and write protection has not been applied.
134. File syntax:
135. <Record type> <Address> = <Data> <Reset type> <Comment>
136. Ordered section:
137. <Single record entry #1>
138. .
139. Ordered_Section_End
140. where:
141. WALD - autoload word record
142. PHYALD - PHY autoload record
143. 0x0000 - 0x07FF in WALD records definition
144. 0x00000 - 0x1F in PHYALD records definition
145. 0x0000 - 0xFFFF in WALD and PHYALD records definition
146. 0x00000000 - 0xFFFFFFFF in CSRALD records definition
147. <Reset type> - Describes the set of reset events for which the setting is applied:
148. PCIE_RST - PCIe asserted reset and all above
149. SW_RST - Host software asserted device reset and all above (must be set for PHYALD)
150. <Comment> - Alphanumeric comment (including space and tab) starting with ';'
151. -----------------------
152. The <addrfile> parameter designates a text file which contains MAC addresses
153. to be programmed to the NIC. This file should contain a list of one or more
154. legal MAC addresses, one per line. Each MAC address contains exactly 12
155. 000AC45D7801
156. A special 'count' syntax may also be used. When a decimal integer in square
157. brackets follows the mac address on the line, it is interpreted as a count of
158. The two examples above are the same. Both represent three consecutive MAC
159. Note: Every line in the address file must end with a carriage return.
160. When EEUPDATE is executed with the <addrfile>, it will sequentially program
161. each selected NIC with MAC addresses from the address file, starting with
162. the first entry. A file, EELOG.DAT, is generated with a record of which
163. MAC addresses were used and which remain available.
164. To program the remaining MAC addresses, EEUPDATE must be run again with the
165. EELOG.DAT specified for the <addrfile>. This is necessary because only
166. EELOG.DAT contains the information on which MAC addresses have been programmed
167. Alternatively, the EELOG.DAT file may be copied over to the previous address
168. file to eliminate the possibility of MAC Address reuse.
169. If EEUPDATE is run again using the same address file (without copying
170. EELOG.DAT), it will program MAC addresses starting back at the first entry
171. in the address file. Please use caution to always use the EELOG.DAT file in
172. order to not program two different NIC ports with the same MAC address.
173. Dual port adapters:
174. When programming the MAC address and EEPROM from a file on a dual port adapter,
175. the recommended method to only select the 1st port of the dual port adapter
176. for programming. The MAC address file should therefore contain only the 1st
177. port MAC addresses. This method is more efficient, as the EEPROM is only
178. These adapters require per port MAC address programming. Each port of the
179. adapter must be selected and the desired MAC address programmed on each port.
180. When programming the EEPROM image, only one port needs to be selected in
181. (See Example 9)
182. ---------
183. When <addrfile> is used as a source for MAC addresses, EEUPDATE generates
184. a file named EELOG.DAT which contains a record of which MAC addresses in
185. <addrfile> were used and which remain available. Those addresses used are
186. The file format for EELOG.DAT is readable as input for <addrfile> in
187. future invocations of EEUPDATE. As of EEUPDATE 3.27, the EELOG.DAT file
188. may be used as both input and output simultaneously.
189. --------
190. To update the EEPROM and MAC Address with the data stored in the files
191. imagefile.eep and addrfile.dat respectively, call EEUPDATE like this:
192. STEP1: EEUPDATE /NIC=1 /D imagefile.eep /A addrfile.dat
193. To update the MAC Address on the third Intel network adapter found in your
194. system without changing the rest of the EEPROM, call EEUPDATE like this:
195. STEP2: copy eelog.dat addrfile.dat
196. Example 3:
197. To update the EEPROM on all of the Intel network adapters with device
198. ID 2449, without changing the MAC address, call EEUPDATE like this:
199. To dump the EEPROM contents on all of the Intel network adapters in your
200. EEUPDATE /ALL /DUMP
201. Example 5:
202. To clear specific bit 1 in word 0xA in the EEPROM on all of the Intel
203. network adapters in your system with device ID 1038, call EEUPDATE like this:
204. To set bit 1 in word 0xA in the EEPROM on all of the Intel network
205. EEUPDATE /ALL /SB 0xA 0x2
206. Example 7:
207. To read word 0x9 from the EEPROM, call EEUPDATE like this:
208. To write word 0x9 to the EEPROM on the third Intel network adapter found
209. in your system, and update its checksum, call EEUPDATE like this:
210. To update the EEPROM and MAC Address for a dual-port adapter that requires
211. per port MAC address programming, call EEUPDATE like this:
212. STEP1: EEUPDATE /NIC=1 /D imagefile.eep /A eelog.dat
213. To update the MAC Address for a multi function per port adapter that
214. requires per function MAC address programming, call EEUPDATE like this:
215. or
216. -----
217. * If you run EEUPDATE without any command line options, EEUPDATE will display
218. a listing of all of the supported Intel Network adapters found in your system.
219. * When using the '/dump' command, EEUPDATE will automatically create a file and
220. name it, based on the last 8 bytes of your Intel Network adapter's MAC Address.
221. For example, if your MAC Address was '00AA11223344', EEUPDATE would create the
222. * Both <word> and <bitmask> parameters *must* be sent to eeupdate in hexadecimal.
223. * The EEPROM Checksums and CRCs are automatically updated when you clear/set a
224. bit or bits, and when you write a word to the EEPROM.
225. ERROR CODES:
226. EEUPDATE returns error codes to the command line. A description of each of these
227. codes can be found in the tool by running eeupdate /exitcodes.
228. Installation
229. The tools driver can be installed on all versions of Microsoft* Windows* since
230. Windows 7. To install the tools' drivers on Windows, run install.bat from the
231. Although the tools are not installed with install.bat, the driver that the tools
232. require is copied into the local machine Windows driver directory. To run the
233. tools, launch a Command Prompt window from the Windows Start Menu. Go to the
234. media and directory where the tools are located and run the tools. The readme
235. files for each tool are found in the same directory as the tools. These tools
236. can be manually installed on the local hard drive in any directory.
237. The tool uses its own driver file (not the same as the system network driver).
238. If the driver sys file already exists in the drivers directory, install.bat may
239. fail to copy. Using the /y switch with install.bat will override and copy the
240. driver file regardless. However, this can be dangerous if an older version of
241. the driver is being used by another application such as Intel(R) PROSet for Windows
242. Device Manager. If a driver is already present in the drivers directory, try
243. running the tool from the command prompt. If it runs, then the driver is fine.
244. The tool will not run if the driver version present does not match the driver
245. Note that for Windows 7 (and later), the user must have access to the
246. %systemroot%system32drivers directory. Only the administrator account has these
247. privileges. The user must be logged in as administrator or the tools must be
248. Note that on Windows, any device that is disabled in device manager will not be
249. accessible by tools due to no memory resources. You would get an error code 0xC86A800E.
250. To solve this problem, you can do one of the following:
251. 1) Re-enable the device in device manager. Never disable this device when using tools.
252. 2) Install an NDIS device driver for the device and make sure that it does not have
253. 3) Delete the device from device manager and restart the system. The install new
254. hardware wizard should appear on next reboot. Do not cancel this. Just move the
255. window aside and run the tool(s). Generally, you can click 'cancel' on the wizard
256. but there are some cases where Windows will disable the memory resources causing
257. INSTALLING THE TOOLS ON EFI
258. There is no installation required for EFI tools. The tools can simply be copied
259. from the appropriate directory to the drive that they will run from. The EFI2
260. binaries are for use with the UEFI Shell 2.X with the UEFI 2.3 HII protocol.
261. EFI2 tools will not run on the EFI Shell 1.X or if the UEFI 2.3 HII protocol is
262. Note that while EFI supports USB drives, there may be issues running tools from the USB
263. drive. Whether or not there are issues are BIOS specific. If issues are experienced,
264. INSTALLING THE TOOLS ON DOS
265. The tools support various DOS versions. There is no installation required for
266. DOS tools. The tools can simply be copied from the DOS directory on the CD to the drive
267. that they will run from. It is expected that the tools have a clean boot environment.
268. The tools will not run with memory managers and/or DOS networking drivers loaded.
269. The tools expect that they have full, unlimited control of the hardware. The tools
270. *WILL NOT* run properly if EMM386 is present. The tools run in protected mode, 32-bit
271. DOS. Therefore, they will not be compatible with any TSR programs.
272. In order to run tools on Linux*, a driver stub must be built and installed on
273. the system. This driver is not related to the network device driver that is
274. used to run the network during live traffic. It is a separate driver used
275. explicitly for tools. Due to the nature of Linux with the number of kernels
276. that can exist, we provide source for the driver module and an install script
277. The tools support Linux distributions based on kernels 2.6.x. Validation is done
278. randomly on popular distributions such as Red Hat* or Suse*. Configured
279. kernel source that matches the currently installed kernel is required. A working
280. GCC is also required. There are some versions of GCC that had a bug which did not
281. support unnamed structures. These versions of GCC are not supported. If you have
282. compilation errors, try updating your version of GCC. If you have linker errors
283. when installing the driver, you should update your kernel - download the latest
284. Note that some distributions such as recent Fedora core versions do not ship with Kernel
285. source. You must download, install, and configure the source in order to get the tools'
286. driver built on this OS. Installing the kernel source RPM does not solve the problem.
287. This is the installation procedure:
288. 1. Log in as root and create a temporary directory to build the Intel(R)
289. 2. Copy ‘install’ and ‘iqvlinux.tar.gz’ to the temporary directory.
290. There are 3 versions of Linux supported: Linux32 (x86), Linux64e (x64),
291. and Linux64 (Itanium). Copies of the above files exist in the appropriate
292. 3. CD to the temporary directory and run ‘./install.’ The driver has been
293. installed now, so the files in the temporary directory can be removed.
294. 4. Copy the tools that you want to use from the appropriate directory of the CD.
295. Iqvsolaris is a separate driver used explicitly for tools and is provided only in
296. binary form. Iqvsolaris driver and tools are provided for 2 different architectures:
297. In order to run tools on Solaris*, peform the following steps:
298. 1. Log in as root.
299. 2. Manually unload the network device driver.
300. 3. Copy the binary iqv driver to the local machine driver directory by
301. CUSTOMER SUPPORT
302. - Main Intel web support site: http://support.intel.com
303. - Network products information: http://www.intel.com/network
304. Copyright (C) 2002-2014, Intel Corporation. All rights reserved.
305. Intel Corporation assumes no responsibility for errors or omissions in this
306. document. Nor does Intel make any commitment to update the information
307. Intel is a trademark of Intel Corporation in the U.S. and/or other countries.
308. *Other names and brands may be claimed as the property of others.
309. This software is furnished under license and may only be used or copied
310. in accordance with the terms of the license. The information in this
311. manual is furnished for informational use only, is subject to change
312. without notice, and should not be construed as a commitment by Intel
313. Corporation. Intel Corporation assumes no responsibility or liability
314. for any errors or inaccuracies that may appear in this document or any
315. software that may be provided in association with this document. Except
316. as permitted by such license, no part of this document may be reproduced,
317. stored in a retrieval system, or transmitted in any form or by any means
318. without the express written consent of Intel Corporation.