Hyperion complains MAC is invalid.

[Rakeshreddy11]

Hi, I am running Hyperion 4.0 on a Windows machine with:

0E20.2 LCS -n xxx.xxx.xxx.xxx -m 00-15-5D-25-E1-A3     masking the IP here

And I get this:

07:46:42.329 00001254 HHC04100I TunTap64.dll version 3.6.2.4906 initiated
07:46:42.693 00001254 HHC00901I 0:0E20 LCS: Interface tap0, type TAP opened

At the same time, I am trying to start another instance of Hyperion 4.5 with same device:

0E20.2  LCS     -n xxx.xxx.xxx.xxx -m 00-15-5D-25-E1-A3

But i get this:

23:45:15.792 00001E68 HHC04100I TunTap64.dll version 3.6.2.4906 initiated
23:45:15.915 00001E68 HHC00916E 0:0E20 LCS: Option MAC address value 00-15-5D-25-E1-A3 invalid
23:45:15.915 00001E68 HHC00007I Previous message from function 'ParseArgs' at ctc_lcs.c(3406)

Can't I start two instances of Hyperion at same time? Could someone help me what am I missing?

Thank you

[mcisho]

When a MAC address is specified in more recent versions of Hercules, Hercules requires that the locally assigned MAC address bit is on (0x02), and that the broadcast bit is off (0x01). Both bits are in the first byte of the MAC address. In your example you need to specify the locally assigned bit, i.e. 02-15-5D-25-E1-A3.

[Fish-Git]

Ian is correct.

Please see:

• https://sdl-hercules-390.github.io/html/hercconf.html#LCS

Note: The MAC address you specify for this option MUST have the 02 locally assigned MAC bit on in the first byte, must NOT have the 01 broadcast bit on in the first byte, and MUST be unique as seen by all other devices on your network segment. It should never, for example, be the same as the host adapter MAC address specified on the -n parameter.

HOWEVER...  I suspect the MAC address you are trying to assign to your virtual adapter might actually be the MAC address of your Windows host's real network adapter. Yes?

• https://maclookup.app/search/result?mac=00-15-5D

This is a common mistake.

To confirm, please post the output from ipconfig -all.

I suspect we will see that 00-15-5D-25-E1-A3 is actually the hardware (MAC) address of your Windows adapter.

More than likely you meant to use the -n option, not the -m option. This is a common mistake. The meaning of the two options are very different from one another. The first (-n) tells CTCI-WIN which host network adapter you want it to use to access your local network with, whereas the second (-m) tells it what MAC address you want CTCI-WIN to assign to your guest's virtual adapter.

Please try again using -n instead.

[Rakeshreddy11]

I suspect we will see that 00-15-5D-25-E1-A3 is actually the hardware (MAC) address of your Windows adapter.

I changed the option from -m to -n as you suggseted, which fixed the issue.

Thanks a lot.

[Fish-Git]

Closing issue.