It would appear that what is broken is the vnet's ability to have a dhcp
server hosting from another subnet... This is the only thing I can find
in common between work and my home router... My home router gets
assigned an address via PPP, but I also have a routed subnet... and that
subnet isn't is no where near my PPP assigned IP... So the router is
configured to route to a virtual interface (shared on its eth0). So all
the machines that do work via dhcp say the dhcp server is the PPP
assigned address (208.49.7.250) and not the router's virtual interface
(207.227.237.209).
VMWare doesn't have this problem, nor do real windows, linux and
macintosh systems... Just vnet.
dhcproxy doesn't help either. It just makes windows assign all ip's to
0.0.0.0... Grrrr.
Guess I'm going to have to switch you hosting DHCP on my linux box...
both here *and* at work. Anyone know a way to set it up so I won't be
handing out IP's to everyone at work... only my win4lin session?
*Brandon
Darb wrote:
> It looks like Win98SE in win4lin makes its request... the router sees
> it and responds... but win4lin (and linux tcpdump) never see the
> response. Yet real systems on my lan work just fine with dhcp.
>
> Here's what I've got from tcpdump on the linux box... Following that,
> I have the dhcp logs from my Cisco 675 DSL router:
>
> tcpdump
> 16:08:19.267555 0.0.0.0.bootps > 255.255.255.255.bootps: (request)
> xid:0xf8684445 G:trident210.kplug.org ether 18:18:e3:ed:d2:0 [|bootp]
> 16:08:19.267544 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0xf8684445 [|bootp]
> 16:08:20.195942 trident210.kplug.org.32773 > ns1.tscnet.net.domain:
> 48188+ PTR? 213.237.227.207.in-addr.arpa. (46) (DF)
> 16:08:20.219728 ns1.tscnet.net.domain > trident210.kplug.org.32773:
> 48188* 1/2/2 (158) (DF)
> 16:08:22.045700 trident210.kplug.org.ipp > 207.227.237.215.ipp: udp
> 116 (DF)
> 16:08:22.265876 0.0.0.0.bootps > 255.255.255.255.bootps: (request)
> xid:0xf8684445 secs:34072 G:trident210.kplug.org ether
> 18:18:e3:ed:d2:0 [|bootp]
> 16:08:22.265866 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0xf8684445 secs:34072 [|bootp]
> 16:08:29.305738 0.0.0.0.bootps > 255.255.255.255.bootps: (request)
> xid:0xf8684445 secs:34072 G:trident210.kplug.org ether
> 18:18:e3:ed:d2:0 [|bootp]
> 16:08:29.305730 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0xf8684445 secs:34072 [|bootp]
> 16:08:45.325738 0.0.0.0.bootps > 255.255.255.255.bootps: (request)
> xid:0xf8684445 secs:34072 G:trident210.kplug.org ether
> 18:18:e3:ed:d2:0 [|bootp]
> 16:08:45.325729 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0xf8684445 secs:34072 [|bootp]
>
> Now for the router's DHCP logs:
>
> Receiving DHCP Discover message from client
> 014:04:18:38 DHCP Info Discover message has matching
> mac=ede31818 on list - delete
> 014:04:18:38 DHCP Info Could not find the requested IP
> address
> 014:04:18:38 DHCP Info Offering IP: 207.227.237.212
> 014:04:18:38 DHCP Info Sending DHCP offer message to client
> 014:04:18:38 DHCP Info The lease for pool 0 is 1080
> 014:04:18:43 DHCP Info Receiving DHCP Discover message
> from client
> 014:04:18:43 DHCP Info Discover message has matching
> mac=ede31818 on list - delete
> 014:04:18:43 DHCP Info Could not find the requested IP
> address
> 014:04:18:43 DHCP Info Offering IP: 207.227.237.212
> 014:04:18:43 DHCP Info Sending DHCP offer message to client
> 014:04:18:43 DHCP Info The lease for pool 0 is 1080
> 014:04:18:51 DHCP Info Receiving DHCP Discover message
> from client
> 014:04:18:51 DHCP Info Discover message has matching
> mac=ede31818 on list - delete
> 014:04:18:51 DHCP Info Could not find the requested IP
> address
> 014:04:18:51 DHCP Info Offering IP: 207.227.237.212
> 014:04:18:51 DHCP Info Sending DHCP offer message to client
> 014:04:18:51 DHCP Info The lease for pool 0 is 1080
> 014:04:19:07 DHCP Info Receiving DHCP Discover message
> from client
> 014:04:19:07 DHCP Info Discover message has matching
> mac=ede31818 on list - delete
> 014:04:19:07 DHCP Info Could not find the requested IP
> address
> 014:04:19:07 DHCP Info Offering IP: 207.227.237.212
> 014:04:19:07 DHCP Info Sending DHCP offer message to client
> 014:04:19:07 DHCP Info The lease for pool 0 is 1080
>
> Austin Gonyou wrote:
>
>> the 169.x.x.x addys are what MS just assigns itself if it doesn't see
>> the
>> a dhcp.
>>
>
>
> _______________________________________________
> 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
