-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
websockets on Freebsd 13.1 connects then immediately disconnects #2755
Comments
Would you care to try out the |
Roger, I'll give it a try this week.
…On Sat, 1 Apr 2023, 5:41 am Roger Light, ***@***.***> wrote:
Would you care to try out the develop branch? That removes the need for
libwebsockets, which simplifies things greatly and improves websockets
performance as well. It would be good to have some feedback on it from the
freebsd perspective.
—
Reply to this email directly, view it on GitHub
<#2755 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOOIJVMTMPOI2NZZ63VEDW3W67Z45ANCNFSM6AAAAAAU67JPWY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
develop branch doesn't compile on the latest FreeBSD-13.2 :
env:
|
Roger,
Finally back with time to work on this. Where can I download the
development branch. Specifically for FreeBSD since the websockets library
doesn't work on FreeBSD.
Rod
…On Sat, Apr 1, 2023 at 8:38 AM Rod Morgan ***@***.***> wrote:
Roger, I'll give it a try this week.
On Sat, 1 Apr 2023, 5:41 am Roger Light, ***@***.***> wrote:
> Would you care to try out the develop branch? That removes the need for
> libwebsockets, which simplifies things greatly and improves websockets
> performance as well. It would be good to have some feedback on it from the
> freebsd perspective.
>
> —
> Reply to this email directly, view it on GitHub
> <#2755 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AOOIJVMTMPOI2NZZ63VEDW3W67Z45ANCNFSM6AAAAAAU67JPWY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
@rodneygmorgan |
Seems like it's fixed in dev branch |
Mosquitto built from ports after tweaks to the libwebsockets port (added LWS_WITH_EXTERNAL_POLL LWS_CALLBACK_ADD_POLL_FD) to Makefile. Both ports build without errors. Issue confirmed with several clients. Once the client connects it immediately disconnects. It appears to happen in websockets.c in the callback_mqtt() function case statement for LWS_CALLBACK_CLOSED. I added a log_printf statement make this assumption. Here is the log file output:
1676606750: New client connected from 10.0.0.193:53052 as mqttjs_a375c484 (p2, c1, k60).
1676606750: Client gonna be disconnected because 'LWS_CALLBACK_CLOSED'.
1676606750: Client mqttjs_a375c484 closed its connection.
mosquitto works perfectly with MQTT protocol. I suspect this is caused by the libwebsockets port (which has no maintainer).
Any help/suggestion to diagnose the root cause is welcome.
The text was updated successfully, but these errors were encountered: