lwIP - A Lightweight TCP/IP stack - Bugs: bug #41787, DHCP Discovery is invalid when an...
You are not allowed to post comments on this tracker with your current authentication level.
bug #41787: DHCP Discovery is invalid when an IP is set to thet netif.
Submitter: | Nick van IJzendoorn <dipswitch_> | ||
Submitted: | Thu 06 Mar 2014 08:40:21 AM UTC | ||
Category: | DHCP | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 1.4.0 |
Sun 06 Apr 2014 06:33:48 PM UTC, comment #3: |
Simon Goldschmidt <goldsimon> |
Fri 04 Apr 2014 08:02:26 PM UTC, comment #2: In section 4.1, it says:
|
Simon Goldschmidt <goldsimon> |
Fri 04 Apr 2014 07:59:45 PM UTC, comment #1: The DISCOVER packet does not seem invalid to me: the 'ciaddr' field is zero. Only the source address of the IP packet is != 0.0.0.0, I haven't found yet whether that's valid or not... |
Simon Goldschmidt <goldsimon> |
Thu 06 Mar 2014 08:40:21 AM UTC, original submission:
The DHCP client will send an invalid DHCP Discovery packet (according to RFC2131 the ciaddr MUST be zero in the DISCOVERY phase) when the IP of the netif is already set. For instance when you are switching from static IP to dynamic IP.
|
Nick van IJzendoorn <dipswitch_> |
Depends on the following items: None found
Items that depend on this one: None found
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 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-04-06 | goldsimon | Category | None | DHCP | |
Item Group | None | Faulty Behaviour | |||
Status | None | Fixed | |||
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2014-03-06 | dipswitch_ | Attached File | - | Added dhcp.patch, #30790 |
Powered by Savane 3.13-f8d8.
Corresponding source code
Fixed by sending discover, request and decline from 'any' even if netif has an address asigned.