The accross the route problem could probably be fixed by making the MAC
match the last 4 bit sets of your REAL MAC. I did this at home and it worked
there.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
> -----Original Message-----
> From: Darb [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 06, 2001 8:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Win4Lin-users] Win4Lin 3.0 -- DHCP client broken
>
>
> 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
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
