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.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
> -----Original Message-----
> From: Darb [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 05, 2001 9:26 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Win4Lin-users] Win4Lin 3.0 -- DHCP client broken
>
>
> Any news on the vnet/dhcp front yet?
>
> Brandon Darbro wrote:
>
> > Both at work and at home the problem stems from the dhcp
> server being on
> > a different subnet then what we are on. The dhcp server is set to
> > server many subnets coming off a single router.
> >
> > If I run a dhcp server actually on the same subnet, it
> works. Grrrr.
> > VMware and real windows,linux and mac machines don't have
> this problem.
> >
> > I currently trying to script a way to get a dhcp address with either
> > dhcpcd or dhclient in linux, then use the assigned IP to
> dynamicly make
> > a dhcpd config file and kick off a local dhcpd server
> offering only that
> > one IP to my win4lin mac address only. Let you know how that goes.
> >
> > *Brandon
> >
> >> On Thu, 31 May 2001, Austin Gonyou wrote:
> >>
> >>> I got tcpdump info. Here it is:
> >>> 00:15:44.545091 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> >>> xid:0x1e77e51b [|bootp]
> >>> 00:15:48.554218 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> >>> xid:0x1e77e51b secs:18822 [|bootp]
> >>> 00:15:55.564209 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> >>> xid:0x1e77e51b secs:18822 [|bootp]
> >>> 00:16:11.604209 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> >>> xid:0x1e77e51b secs:18822 [|bootp]
> >>>
> >>> As you can see, requests are made, but no replies. This
> was ALL I got.
> >>> I'll attempt this at work and see what happens. For now,
> it's pretty
> >>
> > much
> >
> >>> useless. It can't even ping itself if I assign an IP to
> it! I can't even
> >>> ping 127.0.0.1. I get request timed out. HEEEEELLLLLPP.
> Btw, does it
> >>> matter if I have a temp key or not?
> >>
> >> Let me know how it goes. This is kind of mystifying. I
> have a gnatbox
> >> firewall, running DHCP server. My win4lin session (just
> installed),
> >> grabs an IP fine. Odd...
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
