Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2 hours SoftRF dhcp lease when used with kobo #58

Closed
bambukouk opened this issue May 22, 2019 · 13 comments
Closed

2 hours SoftRF dhcp lease when used with kobo #58

bambukouk opened this issue May 22, 2019 · 13 comments
Labels

Comments

@bambukouk
Copy link

When using SoftRF with kobo, wi-fi disconnects exactly after 120 minutes, everytime, on at least two different models of kobo that I have tested.
It is being suggested that it is caused by short dhcp lease on SoftRF? and it could be solved by changing it on SoftRF?
I have seen it, both in flight, and when bench testing.

@lyusupov
Copy link
Owner

lyusupov commented May 22, 2019

Report is filed not in compliance with the template.

Resolution: invalid.

@bambukouk
Copy link
Author

I am sorry for getting it wrong.
I will have another go using the template (or should I re-open/edit this one?)

@lyusupov
Copy link
Owner

Re-open is fine.

@bambukouk
Copy link
Author

bambukouk commented May 25, 2019

Hardware:
Prime Mark II
hardware
kobo

Firmware version:
status

Firmware settings:
settings

Describe the bug (or ask a question):
When using SoftRF with kobo, wi-fi disconnects exactly after 120 minutes, everytime, on at least two different models of kobo that I have tested.
It is being suggested that it is caused by short dhcp lease on SoftRF? and it could be solved by changing it on SoftRF?
By default kobo don't have 'auto renew' of dhcp lease...
I have seen it, both in flight, and when bench testing.

To Reproduce:
Connect any kobo (I tried mini and Clara HD) to SoftRF

Expected behavior:
Wi-fi connection to remain on for at least 5 hrs or (more desirably) for the whole day?
At the moment it disconnects after 120 minutes and the only way to get it going again is to re-start kobo (this would cause the loss of all task info)

@bambukouk
Copy link
Author

Re-open is fine.

I don't know whether you meant to re-open as a new issue or re-open by adding comment to this one using correct template?
If I am wrong (yet again...) please let me know and I will do the necessary.

@lyusupov
Copy link
Owner

ticket-58

@bambukouk
Copy link
Author

bambukouk commented May 31, 2019

I must be particularly thick...
Can't see re-open anywhere?
Clipboard01
Sorry

later update:
did a bit of searching and... it appears that:

...you can re-open your own issues *if you closed them yourself...

so, since I didn't close it, I cannot reopen it
it's up to you I guess to re-open it?

@lyusupov
Copy link
Owner

lyusupov commented Jun 4, 2019

I've assigned this ticket onto you.
Try again.

@bambukouk
Copy link
Author

bambukouk commented Jun 4, 2019

I am afraid being made "asignee" doesn't make any difference...
the option to re-open is still not available to me.

Quick search on interweb shows that it seems to be common problem on Github.
I cannot reopen because you have closed it.
You cannot reopen because it isn't your own issue.

Sorry for creating this mess by not using the template...

I am happy to raise a new issue and cross-refer the two? leaving #58 closed and linked to a new one?

@bambukouk
Copy link
Author

Thank you!

@lyusupov
Copy link
Owner

lyusupov commented Jun 5, 2019

  1. Give me a reference on a RFC 2131 paragraph where it is specified that: 120 minutes lease time is a "bad value".

Instead, the standard gives an option for DHCP server (ESP32, in this case) to choose an appropriate value, then any DHCP client (Kobo, in your case) have to comply with.

'120 minutes' lease value is a part of Espressif SDK: https://github.com/espressif/esp-idf/blob/master/components/lwip/include/apps/dhcpserver/dhcpserver.h
and SoftRF has no control over it.
Moreover, I consider that this is a reasonable value, provided that ESP32 AP can serve very limited number of Wi-Fi clients. Greater lease time value may cause exhaust of spare IP addresses pretty soon, when DHCP clients do abrupt disconnect/reconnect sequence.

So, if you have your own strong arguments against 120 minutes - argue with Espressif SDK developers, not me.

  1. Give me a reference on a paragraph in my SoftRF GitHub page(s) where I say that Kobo is a good, approved client for Wi-Fi connection to a SoftRF unit.

By choosing a device, not mentioned as known good one, you are taking all the associated risks on your own.

Friendly reminder that SoftRF firmware comes free of charge and without even the implied warranty of FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

Ask customer service of a product you've paid for to make you feel happy.

So, if you are not satisfied with your TTGO T-Beam hardware (you should had to read this Disclamer before purchasing the board ) - work with your board seller.
If you are not satisfied with your Kobo compliance to the RFC 2131 DHCP standard - work with Rakuten customer service.

Resolution: invalid.

@lyusupov lyusupov closed this as completed Jun 5, 2019
@bambukouk
Copy link
Author

Thank you for detailed explanation and your help.

@TexasUK
Copy link

TexasUK commented Jun 5, 2019 via email

Repository owner locked as off-topic and limited conversation to collaborators Jun 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants