buglwIP - A Lightweight TCP/IP stack - Bugs: bug #53301, UDP Broadcast reception not...

 
 

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

bug #53301: UDP Broadcast reception not interface-specific

Submitter:  Michael Steinberg <michsteinb>
Submitted:  Thu 08 Mar 2018 08:28:30 AM UTC
   
 
Category:  UDP Severity:  3 - Normal
Item Group:  Faulty Behaviour Status:  Fixed
Privacy:  Public Assigned to:  goldsimon
Open/Closed:  Closed Planned Release:  2.1.0
lwIP version:  2.0.3

Wed 13 Jun 2018 08:01:44 PM UTC, comment #2: 

Should be fixed, thanks for reporting!

Simon Goldschmidt <goldsimon>
Group administrator
Fri 20 Apr 2018 07:16:36 AM UTC, comment #1: 

Could udp_bind_netif() solve your problem?

Dirk Ziegelmeier <dziegel>
Group administrator
Thu 08 Mar 2018 08:28:30 AM UTC, original submission:  

Following setup (using RAW API):
2 Interfaces bound to IP1 and IP2 respectively.
2 UDP PCBs bound to IP1 and IP2 respectively (same port), but not "connected"; broadcast option set for both.

Outcome:
The PCB created last receives all broadcasts on the configured port, even though they may have arrived on the interface with the matching IP of the other PCB.

Depending on the design/specification this might be a bug or a limitation.

Possible relief:
Priorize PCBs bound to a specific IP address over ones bound to ipaddrany when determining the destination PCB upon UDP broadcast reception and have them match the configured interface address.

Michael Steinberg <michsteinb>

 

(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 (Updated the item)
  • -email is unavailable- added by dziegel (Posted a comment)
  • -email is unavailable- added by michsteinb (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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-06-13 goldsimon StatusNone Fixed
        Assigned toNone goldsimon
        Open/ClosedOpen Closed
    2018-06-13 goldsimon Planned ReleaseNone 2.1.0

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code