-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Re-adding PING after LWIP2 migration? #3863
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
Comments
For the record,
Are you indeed using it ? |
Personally, I'd love to get ping back, by whatever means. I'm curious what the downsides could be, though. I think @igrr was concerned, that it might be harder to support downstream, because it is not in the 'main' source tree anymore, like it used to be for 1.4? but i'm not sure what this means. Is 'lwIP-contrib' not part of the source distribution? Because I maintain an framework that sits on top of both cores (ESP8266 and ESP32) and abstracts away any differences, I'm especially thankful for APIs that are consistent across platforms. ;-) |
lwip-upstream-contrib PING api has changed and is not compatible with declarations in SDK.
and please report back whether it is working as before. |
I need ping badly. My ISP furnishes a very poor router in terms of versatility, performance and reliability. The best way to keep reliably connected that I have found is to PING the router every 6 min. If ping fails, I reset. Other more common methods like !connected often do not seem to detect that the router is no longer listening. |
@d-a-v: I followed your instructions and ping works the same as it used to do, which is great! but as soon as i start the mDNS responder, the firmware crashes.
this crash is new. |
@everslick thanks for testing ping.
|
@everslick waiting on feedback. |
lwip2 version in core release 2.4.0 has ping. |
Sure I can test ping. Just to be sure we are on the same page do you have example code you would like me. To run?
…Sent from my iPhone
On Jan 7, 2018, at 3:19 PM, david gauchard ***@***.***> wrote:
lwip2 version in core release 2.4.0 has ping.
@bill-orange @everslick can you confirm ping/lwip2 is working for you ?
@everslick please open a new issue if your mDNS bug still occurs with latest git and lwip2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@bill-orange You were saying
so I assumed you were using it in your own sketches and found it no more present in lwip2. |
No problem. I tested it with one of my own sketches. It works fine with I am maintaining connectivity with this:
pingTest is set for 15 min. WiFi On/Off uses this:
|
Thanks ! |
As previously discussed ping support was removed by migrating to LWIP2 (see: #3835).
Most people might not have noticed yet, as they are still on LWIP1. This issue is meant to gather opinions about re-adding support for it.
Should support for ping be re-added as it was, or would an external ESPing library, that might even work on ESP32, be a better solution?
Or is ping something only very few people care about anyway?
The text was updated successfully, but these errors were encountered: