View Single Post
Old 12-27-2013, 03:20 AM   #14
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,084
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by zweiundachtzig View Post
I kind of fixed my problem a little bit... maybe yours too?

In some other forum I have read about DHCP issues and investigated a bit further.

The freshly booted Kobo got two different IPs for the same MAC addresses, which is kind of odd. I suppose it sends out two DHCP request in quick repetition. See attached screenshot from the router webpage. Also the 255 address is strange, because (depending on the subnet size) it should be for reserved for broadcasts (?)

Now, I have set the DHCP to always assign the same IP address to this MAC and rebooted the router to get rid of the current double allocation. Good thing is that it correctly receives one IP address now, bad thing is... it solve the problem only a little bit. After sleep mode the stupid "There was a problem ... please try again" message is still popping up. BUT, trying it again actually worked! Without a reboot.

Maybe other routers are a bit more fault tolerant against the double DHCP request? Or answer quicker to avoid a second request.

Credit where credit is due: This guy had the same idea already in 2011
http://www.lesen.net/forum/ebook-rea...ten/#post42126 (if you can read / google-translate german)
I would have to say that the firmware in your router has problems. Unless your router is very oddly configured, the address ending in the .255 octet is very likely to be the broadcast address for the address block and that address WOULD never be given out by any DHCP server even close to standards compliant.

One way to check if your router is misconfigured is to take a look at the netmask (PC, ipconfig from a command prompt, Mac or Linux, ifconfig from a command prompt). If it is 255.255.255.0, you are using a single class C block and the 192.168.xxx.255 address is the broadcast address.

Regards,
David
DNSB is offline   Reply With Quote