Re: [lwip-users] Help with LwIP Modem

Hi All, To close the loop on my original question maybe it can help another rookie like me. My goal was to set my ethernet device so that it will act as a cable, received packets from the netif, modulates them, send them over a cable, have another device demod, the exact same packet, and last

[lwip-users] Netconn write and non-blocking

Dear all, What is the best way to handle the following situation when using netconn in TCPIP mode and v2.0.0RC1. If I connect (with netconn_connect() ) to a device that's not available and netconn is blocking how long do I have to wait? Because it's unknown to me and it could take very long I

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

It's worth comparing the behavior of the netconn API.  Even though the netconn API is only available with NO_SYS = 0, it is still a user of the raw API like the applications mentioned in this email thread. lwip_netconn_do_writemore() calls tcp_write() until all segments have been put into

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

Again, it's probably not be the wrong approach, it's just what I've been told on this thread: https://lists.gnu.org/archive/html/lwip-users/2016-06/msg00055.html Since it worked for me at that moment, I just let it like that, and reading the responses here confirms that it's the correct approach

Re: [lwip-users] 0MQ, MQTT and RabbitMQ

Hi, I contributed the transport abstraction for the Packet libraries for MQTT and MQTT-SN in Paho for embedded. I've been working on the transport for MQTT-SN to use the lwIP RAW API, which seemed to be working, but I didn't submit them to Paho. I can post it if you or anyone else are willing

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

> > I think you might have missed reading the documentation: tcp_write enqueue > data, tcp_outout tries to send it. You always have to call both. > > I actually found the recommended call flow on wiki (Here: http://lwip.wikia.com/wiki/Raw/TCP ) after Mihai mentioned using tcp_output(). And yes, I

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

Confusion might arise from the examples in contrib, neither tcpecho_raw nor smtp do call tcp_output(). Not everyone seems to look at httpd... nor read the wiki, nor the docs... ___ lwip-users mailing list lwip-users@nongnu.org

[lwip-users] 0MQ, MQTT and RabbitMQ

Hello, Could anyone share their experience(s) of any integration of LWIP with OMQ, MQTT and RabbitMQ. Much obliged, Abdul Hakeem ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

I think you might have missed reading the documentation: tcp_write enqueue data, tcp_outout tries to send it. You always have to call both. Simon Gesendet mit AquaMail für Android http://www.aqua-mail.com Am 13. Juli 2016 2:35:59 nachm. schrieb Jakub Schmidtke : Maybe

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

> > Maybe your sys_now() or sys_jiffies() functions are too course? > They should have a resolution of approx. 1 msec. I am not even talking about observed delays. I am looking at the code, and based on that, those packets will be delayed by up to twice the value of TCP_TMR_INTERVAL in

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

Jakub Schmidtke wrote: > I am using lwip with NO_SYS=1, and I have noticed > that outgoing TCP packets are very delayed. > > It looks like between writing a packet (using tcp_write), > and the time it actually written to the interface it takes usually about > 200ms. Maybe your sys_now() or

Re: [lwip-users] lwIP delays outgoing TCP packets by up to 500ms

I've worked around this disabling Nagle Algorithm for each pcb and also calling tcp_output after every write. But somebody told me it was the wrong approach doing so, but it works for me so I don't know what to say. Mihai On Wed, Jul 13, 2016 at 3:20 AM, Jakub Schmidtke wrote: