buglwIP - A Lightweight TCP/IP stack - Bugs: bug #59966, After several hours of working,...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #59966: After several hours of working, need router reset to be able to send mqtt msg bigger than 1460 bytes

Submitter:  Dejan <dejandigitex>
Submitted:  Fri 29 Jan 2021 09:56:54 AM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  Faulty Behaviour Status:  Invalid
Privacy:  Public Assigned to:  goldsimon
Open/Closed:  Closed Planned Release:  None
lwIP version:  2.1.0

Fri 29 Jan 2021 10:05:12 AM UTC, comment #1: 

This is not an lwIP bug report. Please continue a discussion on the mailing list. I'll send it there and answer there.

-> closing as invalid

Simon Goldschmidt <goldsimon>
Group administrator
Fri 29 Jan 2021 09:56:54 AM UTC, original submission:  

Hi,

We are company producing seismic sensors based on STM32H7 mcu's running lwip and we use mqtt to connect to our own cloud server. On starrup devices send a series of short messages and then after this usual handshake with the server they start streaming bigger packets of sensor data on a specific mqtt topic. The message size is usually from 4KB up to 32 KB sent each second. Everything seems to work fine until after several hours (usually 12 to 24 hrs), we find that we need to restart the main router, otherwise the streaming of mentioned packets will be blocked from the router to the server. However the device is still able to send tcp mqtt packets that fit in one TCP frame. Once the TCP message is to be fragmented in more than one frame (is bigger than 1460 buyes) the router will not let it through untill we reset it and we get another day of a working device.

This behaviour is our several months nightmare and we cannot wrap our heads arroud it...

If any of you experts have an idea what could be the problem please reply.

We tried:
New server/ broker, different port numbers, different MCU series.

Can it be that our low level protocol for TCP is doing something wrong so the router remembers this device mac address and wont let it send fragmented msgs?

The last thing we tried is to change the MAC address of the device during the blockage mode and then communication went through until several hours later to fall in the same state.

Please throw any ideas you have in mind we need to deliver this product soon but its obviously no good as it is.

Dejan <dejandigitex>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by goldsimon (Posted a comment)
  • -email is unavailable- added by dejandigitex (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-01-29 goldsimon StatusNone Invalid
        Assigned toNone goldsimon
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-bb6a.
    Corresponding source code