net: ipv4: udp: broadcast delivery not supported #11617
Assignees
Labels
area: Conformance
Conformance tests
area: Networking
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Comments
galak
added
bug
|
Works for me, perhaps this was already fixed or there was some issue during testing. Anyway, attached is a capture of an UDP packet with broadcast destination address and it was handled by zephyr just fine. |
|
New pcap, with correct Zephyr MAC address. |
jukkar
added a commit
to jukkar/zephyr
that referenced
this issue
May 15, 2019
Make sure we are able to receive UDP packets with broadcast destination address. If CONFIG_NET_IPV4_ACCEPT_ZERO_BROADCAST is set, then check here also non-standard broadcast address that is described in RFC 1122 chapter 3.3.6. Fixes zephyrproject-rtos#11617 Signed-off-by: Jukka Rissanen <[email protected]>
backporting bot
pushed a commit
that referenced
this issue
May 20, 2019
Make sure we are able to receive UDP packets with broadcast destination address. If CONFIG_NET_IPV4_ACCEPT_ZERO_BROADCAST is set, then check here also non-standard broadcast address that is described in RFC 1122 chapter 3.3.6. Fixes #11617 Signed-off-by: Jukka Rissanen <[email protected]>
jukkar
added a commit
that referenced
this issue
May 20, 2019
Make sure we are able to receive UDP packets with broadcast destination address. If CONFIG_NET_IPV4_ACCEPT_ZERO_BROADCAST is set, then check here also non-standard broadcast address that is described in RFC 1122 chapter 3.3.6. Fixes #11617 Signed-off-by: Jukka Rissanen <[email protected]>
nashif
pushed a commit
to nashif/zephyr
that referenced
this issue
May 21, 2019
Make sure we are able to receive UDP packets with broadcast destination address. If CONFIG_NET_IPV4_ACCEPT_ZERO_BROADCAST is set, then check here also non-standard broadcast address that is described in RFC 1122 chapter 3.3.6. Fixes zephyrproject-rtos#11617 Signed-off-by: Jukka Rissanen <[email protected]>
nashif
pushed a commit
that referenced
this issue
May 21, 2019
Make sure we are able to receive UDP packets with broadcast destination address. If CONFIG_NET_IPV4_ACCEPT_ZERO_BROADCAST is set, then check here also non-standard broadcast address that is described in RFC 1122 chapter 3.3.6. Fixes #11617 Signed-off-by: Jukka Rissanen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Zephyr drops UDP packet with broadcast destination IP and unicast MAC. According to RFC 1122 4.1.1 this scenarion should be supported by UDP: "... to use communications services (e.g., multicast or broadcast delivery) not available from TCP."
ipv4-udp-bcast-dst.pcap.gz
The text was updated successfully, but these errors were encountered: