I like how you are assigning the MAC addresses... makes much more sense
than VMWares truly random within a range method. Only thing I could
think of that would be better is to use the linux hosts own ethernet MAC
as the basis for extrapolating your own. That way it wouldn't change if
the Linux host getting dynamic IP's. Just a thought.
I sent Mike Badger ifconfig's, netstat -rn's, and etherea logs of
win4lin compared to a real windows system... did you get those?
*Brandon
P.S. I love that you are letting us help by givin ya'll information. :)
Brian Keegan wrote:
> Brandon
>
> VNET generates a dynamic MAC address based on the IP address of the host
> Linux system. By default, all VNET MAC addresses start with 18:18
> followed by the least significant 3 bytes of the host system's IP
> address followed by 00.
>
> So, if the host system IP address is 207.227.237.210, the Win4Lin VNET
> MAC address will be 18:18:e3:ed:d2:00.
>
> This way of allocating dynamic MAC addresses offers the best chance of
> assuring uniqueness in a network of Win4Lin clients, and also provides
> NeTraverse with a mechanism for assigning a range of MAC addresses to
> multiple Win4Lin sessions running on the same system (cf. the NeTraverse
> Server product).
>
> Now to the question of specifying a static MAC address. Yes, this is
> possible. There are parameters in /etc/default/merge that define the
> range of MAC addresses that Win4Lin will use. If that range starts and
> ends on the same address, that effectively defines a static MAC address
> to be used by your Win4Lin session. The parameters you need to change
> are:
>
> MERGE_VNET_MACRANGE_START
> MERGE_VNET MACRANGE_END
>
> Only the least significant 4 bytes of the MAC address can be specified;
> the most significant 2 bytes are always set to 18:18. The value needs to
> be specific as 8 hexadecimal digits so, for example, if you want your
> MAC address to be 18:18:01:23:ab:cd, then you need to set the MAC
> address range parameters as follows:
>
> MERGE_VNET_MACRANGE_START=0123abcd
> MERGE_VNET MACRANGE_END=0123abcd
>
> Make these changes, reboot the system and you now have a static MAC
> address allocated to your Win4Lin session.
>
> By the way, there are two other /etc/default/merge parameters that will
> be of interest to anyone using VNET (or not, as the case may be).
>
> Setting MERGE_VNETWORK=off will disable VNET totally. This is useful to
> anyone who absolutely never wants to use VNET and hates the thought of
> VNET modules and a daemon hanging around their system with no work to
> do.
>
> Setting MERGE_VNET_IFNAME=<interface name, e.g. eth1> can be used on a
> system with multiple network interfaces to force VNET to use a specified
> interface, rather than simply adopt the first interface as viewed in the
> output of "ifconfig -a".
>
> And, yes, we need to get this documented.
>
> Best regards,
>
> Brian
>
> Darb wrote:
>
>> So the next question would be... Is a Win4Lin install using a static
>> MAC address or a dynamic one? Vmware uses a dynamic one by default, but
>> they document how to set it to a static address.
>>
>> Netraverse, can you offer me a clue on that?
>>
>> *Brandon
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
