Hang with UDP multicast

[Petro Karashchenko]

Hello NuttX developers,

Recently I fixed a latency issue related to Ethernet transmission with
SAMv7. Now I'm moving forward and meeting the next issue:
I'm having a nuttx based board installed in the industrial Ethernet network
environment. By "industrial Ethernet network environment" I mean that there
are few switches and few PLCs in the network successfully communicating
with each other and I plug my device into existing infrastructure. The
network stack on the device has both TCP and UDP enabled and buffered mode
selected (I have a couple of TCP servers running and UDP server as well).
The device starts and operates well until other devices in the same network
start exchanging with UDP multicast messages. At that moment I can't access
my device over the network anymore.
I'm going to deep dive into this, but have a few questions:
- Maybe anybody used NuttX with UDP multicast?
- Is there a way to disable reception of UDP multicast messages and just
drop packets "on the floor"?
- Any guesses what can go wrong here?

Again the device is SAMv7 based, but I do not suspect driver issue here
(from the first glance seems not to be a driver issue). I will try to
replicate a similar situation with ESP32 config by running a mock of my TCP
and UDP servers to check if this is a driver issue or not.

Best regards,
Petro

Re: File transfer

[Petro Karashchenko]

You can try searching for "CONFIG_NSH_ROMFSETC" and
"CONFIG_NSH_CUSTOMROMFS" options in the code tree.
I see that currently ESP32-C3 and SIM use it. Also I used the same with
custom board and it works pretty well.

нд, 10 вер. 2023 р. о 00:35 Gustavo Soares 
пише:

> Do you have any example of how it should be done?
> 
> De: Gregory Nutt 
> Enviado: sábado, 9 de setembro de 2023 13:51
> Para: dev@nuttx.apache.org 
> Assunto: Re: File transfer
>
> On 9/9/2023 9:43 AM, Gustavo Soares wrote:
> > So I have to create and mount a directory to my HTML file and tranfer it
> to this directory? Even if I have the HTML file embedded on compile?
> No transfer is necessary.  The ROMFS file system can be built into the
> code.
>