I have neither of these enabled... And it works fine if the dhcp server
resides on the same subnet as the linux host. It's only broken for me
when dhcp served from across a route.
So no, sorry... it doesn't help. :(
*Brandon
Gonyou, Austin wrote:
> Yeah, that issue was fixed late Friday/early saturday. There are 2 things
> which can cause W4L not to do DHCP properly. They are:
>
> 1. Packet Socket: mmapped IO - Kernel option
> 2. Using IP Aliases, before W4L is started at boot.
>
> The affects for each are as follows:
>
> 1. Packet Socket - MAC address will be set incorrectly. You will have 18:18,
> but who knows what else.
> 2. IP Alias defined - Vnetd is unable to perform IP interception. grep
> intercept /var/log/messages to find out.
>
> Hope this helps.
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
