Arduino for STM32

A similar usage and its explanation can be found in
1. https://doc.ecoscentric.com/ref/lwip-ap ... -bind.html
2. https://www.nongnu.org/lwip/2_0_x/group__udp__raw.html
3. https://stackoverflow.com/questions/165 ... rogramming

I went through your explanations and based on them I understand that my computer (python) program that send's data to STM32 MUST bind to a specific address within its ethernet subnet mask i.e. any one of the 169.252.72.123/16 in my case. This is because there is no IP stack on the STM32 to read data ...

In the same wiki page "https://en.wikipedia.org/wiki/0.0.0.0" it is written
"In the context of servers, 0.0.0.0 can mean "all IPv4 addresses on the local machine". If a host has two IP addresses, 192.168.1.1 and 10.1.2.1, and a server running on the host is configured to listen on 0.0.0.0, it will ...

Actually if we check the file EthernetUdp.cpp in the STM32Ethernet library
(https://github.com/stm32duino/STM32Ethernet/blob/main/src/EthernetUdp.cpp) it has two functions like :
uint8_t EthernetUDP::begin(uint16_t port)
uint8_t EthernetUDP::begin(IPAddress ip, uint16_t port, bool multicast ...

Its a typo. It should be 155, not 555. Ive corrected it on the question itself.

PS: In the question I had wrongly input 169.252.72.555 which is not valid. Later after it was pointed it was not a valid ip address, i corrected my typo and made it 169.252.72.155 in the question itself,
The main ...

I have connected a STM32(NUCLEO-F767ZI) to my laptop via ethernet cable. The IP address of laptop ethernet is 169.252.72.123 with a subnet mask of 255.255.0.0.
When I bind my ethernet to 0.0.0.0 it must listen to all ip address in the subnet i.e. 169.252.72.123/16. i.e. when i send data from my ...