Austin I'm not sure what you are trying to say here but it's wrong anyway. You can only specify the last (i.e. least significant) 4 bytes (that's 8 hex digits) of the MAC address using these parameters. The first two bytes are hard coded to be 1818 and must not be included. If you specify 5 bytes, as you have done here, the result, from the users perpective, are unpredictable. Best regards, Brian Austin Gonyou wrote: > MERGE_VNET_MACRANGE_START=1818183e44 > MERGE_VNET_MACRANGE_END=1818183e44 _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] https://lists.netraverse.com/mailman/listinfo/win4lin-users
- Re: [Win4Lin-users] Win4Lin 3... Darb
- Re: [Win4Lin-users] Win4Lin 3... Austin Gonyou
- Re: [Win4Lin-users] Win4Lin 3... Darb
- Re: [Win4Lin-users] Win4Lin 3... Dan Swartzendruber
- Re: [Win4Lin-users] Win4Lin 3... Mike Badger
- Re: [Win4Lin-users] Win4Lin 3... Austin Gonyou
- Re: [Win4Lin-users] Win4Lin 3... Brian Keegan
- Re: [Win4Lin-users] Win4Lin 3... Darb
- Re: [Win4Lin-users] Win4Lin 3... Mike Badger
- Re: [Win4Lin-users] Win4Lin 3... Austin Gonyou
- Re: [Win4Lin-users] Win4Lin 3... Brian Keegan
- Re: [Win4Lin-users] Win4Lin 3... Austin Gonyou
- Re: [Win4Lin-users] Win4Lin 3.0 -- DHCP cl... Darb
- Re: [Win4Lin-users] Win4Lin 3.0 -- DHCP client bro... Glen Boyd
- Re: [Win4Lin-users] Win4Lin 3.0 -- DHCP client broken? Paul Harvey
- Re: [Win4Lin-users] Win4Lin 3.0 -- DHCP client broken? Brandon Darbro
