> I am trying a Nokia phone utility named WalkingHotSpot, which provides
 > wifi access to the phone 3G network. However, something prevents me
 > from getting a DHCP address. I have tried snoop and it shows a sequence
 > of DHCP DISCOVER and DHCP OFFER messages, but dhcpagent seems not to
 > like the offers. I have found the following in /var/adm/messages:
 > 
 > Feb 21 12:49:48 zoetekauwer mac: [ID 435574 kern.info] NOTICE: myk0 link up, 
 > 100 Mbps, full duplex
 > Feb 21 12:49:48 zoetekauwer in.routed[380]: [ID 749644 daemon.notice] myk0 
 > has a bad address 0.0.0.0
 > Feb 21 12:49:53 zoetekauwer /sbin/dhcpagent[1907]: [ID 142010 
 > daemon.warning] compute_points_v4: OFFER without lease time
 > Feb 21 12:51:53 zoetekauwer last message repeated 4 times
 > Feb 21 12:52:56 zoetekauwer /sbin/dhcpagent[1907]: [ID 142010 
 > daemon.warning] compute_points_v4: OFFER without lease time
 > Feb 21 12:58:17 zoetekauwer last message repeated 5 times
 > Feb 21 12:59:23 zoetekauwer /sbin/dhcpagent[1907]: [ID 142010 
 > daemon.warning] compute_points_v4: OFFER without lease time
 > Feb 21 13:04:44 zoetekauwer last message repeated 5 times
 > Feb 21 13:05:47 zoetekauwer /sbin/dhcpagent[1907]: [ID 142010 
 > daemon.warning] compute_points_v4: OFFER without lease time
 > Feb 21 13:12:12 zoetekauwer last message repeated 6 times
 > Feb 21 13:13:15 zoetekauwer /sbin/dhcpagent[1907]: [ID 142010 
 > daemon.warning] compute_points_v4: OFFER without lease time
 > Feb 21 13:15:21 zoetekauwer last message repeated 2 times
 > 
 > The fact is that it never replies to DHCP OFFER messages and never gets an 
 > IP address.

Right.  As above, it drops the OFFER because it's missing a lease time.  A
lease time is expressly required as per table 3 in RFC2131 and discussed
in the subsequent text.  I'd be interested to know what other clients use
for a lease time in this case (infinite?) as it is not specified in the
DHCP protocol.

 > 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.

--
meem
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to