For When You Can't Have The Real Thing
[ start | index | login ]
start > Panasonic > KX-HCM280A > Lease Rejected

Lease Rejected

Created by dave. Last edited by dave, 10 years and 28 days ago. Viewed 3,091 times. #8
[diff] [history] [edit] [rdf]
labels
attachments

Problem

The camera is not reachable via network. The camera starts up, accepts a dhcp lease, then rejects it 25 seconds later. This log segment is from the DHCP server (a CentOS 4.x OS, running the ISC dhcpd):

Jul  3 09:48:05 stargate dhcpd: DHCPDISCOVER from 00:80:f0:56:46:30 via eth0
Jul  3 09:48:06 stargate dhcpd: DHCPOFFER on 172.31.9.91 to 00:80:f0:56:46:30 via eth0
Jul  3 09:48:06 stargate dhcpd: DHCPREQUEST for 172.31.9.91 (172.31.0.1) from 00:80:f0:56:46:30 via eth0
Jul  3 09:48:06 stargate dhcpd: DHCPACK on 172.31.9.91 to 00:80:f0:56:46:30 via eth0
Jul  3 09:48:19 stargate dhcpd: DHCPRELEASE of 172.31.9.91 from 00:80:f0:56:46:30 via eth0 (not found)

The camera is pingable during the 25 seconds it holds onto the lease but does not respond to web queries. Once the release happens, it no longer responds to pings.

Changing the lease reservation does not fix the problem.

Chaning the lease reservation to a dynamic address (ie a random address from the pool) does not fix the problem. The only difference is when the address comes from a non-reservation, the DHCPRELEASE message says (found) instead of (not found).

Reseting to factory defaults via the hardware button does not clear the issue; in fact, after pressing the reset button, the camera's light flashes orange longer than the manual's advised period of 5 seconds; it appears to go for ever (I stopped waiting after 20 minutes and cycled the power).

I have four other KX-HCM280A cameras on the same network segment which are configured the same and are working properly. All the cameras were disconnected from the network and power for several months. This one is the only one which has failed to come back up. No relevant network changes happened during this period.

I also had a BL-C10 die the same way last year. I threw it away figuring it was a one-off failure. Now that I have a second one fail, I'm wondering if its systemic and/or if there's a way to fix.

About the (found) and (not found) messages

The (not found) and (found) are being generated by my dhcpd server. When you have a lease and the server is sent a DHCPRELEASE message, the dhcpd server looks to see if the lease is present to be released back into the pool of available addresses. If the lease is present, you get the (found) message. If the lease is a reservation, dhcpd doesn't record it, and so can't find it to release it (since there's no point in releasing a reserved IP; there's no functional difference) and you get (not found) instead.

So this has nothing to do with the camera being broken.

Commentary

This page is here as a reference for a Panasonic request I put in. The web form says "600 character maximum; be as specific as possible". My "specificity" requires more than 600 characters.

Also, I'm not in the US. I am in Ottawa, Canada. (In the unlikely event someone from Panasonic reads this.)

Panasonic Support Sucks

The US support team wanted me to call them and provided a 1-800 number, which of course doesn't work in Canada. They asked me to call the Canadian number. I tried four times over the space of a week at varying times of the day and got some variation of the "hold times are in excess of one hour, please try again some other time, <click>!" message.

Word From The Net

Someone emailed me with a note of what worked for him:

I used the reset button and connected to the default ip 192.168.0.253

Then set it to DHCP and I'm all set again, without releases.

The documentation claims this is what is supposed to happen. I tried this several times with mine against a variety of DHCP servers but it didn't work for me.

Got it working

There were some interesting developments.

I did some wireshark snoops of the wire while the camera was active and saw some odd behavior. The camera appeared to be taking a lease, then trying to switch to becoming the default router. Since the existing router didn't seem to like that much, the camera would give up and go sulk.

Tonight I put just the camera and one interface of my computer on a switch and watched it again. It did some kind of ipv6 discovery, then dhcp discovery, then tried again to be the default router from the previous attempts at getting it a lease.

However, once it was reset, it did respond to its default of 192.168.0.253. And from there I could assign it a static IP address.

no comments | post comment
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.

Useful:


snipsnap.org | Copyright 2000-2002 Matthias L. Jugel and Stephan J. Schmidt