OFW doesn't ask for enough DHCP options

[wmb@…]

For complete network access, OFW needs router and nameserver responses from the DHCP server. Many DHCP servers supply that information in every response, but some only supply the options that the DHCP discover packet explicitly asks for. OFW Q2E17 and earlier don't ask for any options explicitly, so it doesn't get the required information from the explicit-response servers.

[wmb@…]

Fixed by svn 933. The fix will appear in q2e18. A test build with the fix is in http://dev.laptop.org/~wmb/q2e17d.rom

[mikus]

Replying to wmb@firmworks.com:

For complete network access, ...

I'm not sure what "complete network access" means, but of course there will be situations where the XO is under a tree by itself, with NO network access.

Further, I expect there might be other users with setups like mine - if I can figure out how, I will run with static network addresses - *without* any DHCP server. Also, even today for OFW to get responses from the (temporary) DHCP server I have on my LAN will not enable it to access the outside world (i.e., the internet) -- since my connection passes through a proxy that the DHCP server never reports.

[cscott]

Please test build 761 resulting from build-repo commit 66520e40.

[wmb@…]

The fixed version has been released.