Peter Memishian writes: > > I suspect that there is something non-standard or at least non-strict > > in the DHCP implementation of WalkingHotSpot, because I have tried the > > exact same configuration with JoikuSpot, another software for Nokia > > phones that does exactly the same thing and it worked out of the box. > > Question is, can I do something configuration-wise to fix this? > > No, but it would be straightforward to tweak the client source code to > fall back on e.g. an infinite lease in this case. Whether this is a > reasonable behavior in general is debatable.
I'd suggest falling back to some arbitrary time period instead -- perhaps an hour or a day, and with a tunable if someone _really_ cares. With an arbitrary time period, we would at least end up requerying the server periodically to make sure we still have the lease. With an "infinite" lease, we won't do that, and would have to fall back on duplicate detection to discover mistakes. I wouldn't make the default arbitrary period "too short." It's likely that a DHCP server that flubs this part of the spec does other weird things, such as handing out a different IP address every time you ask. Getting renumbered once a day or so isn't too horrible for most applications. Having it happen every few minutes would be "bad." (Honestly, it's always bugged me that the DHCP spec is draconian about this "mandatory option." It violates at least the spirit of being liberal about what you accept.) -- James Carlson, Solaris Networking <[email protected]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
