tasklwIP - A Lightweight TCP/IP stack - Tasks: task #10241, AutoIP: don't break existing...

 
 

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

task #10241: AutoIP: don't break existing connections when assiging routable address

Submitter:  Simon Goldschmidt <goldsimon>
Submitted:  Sat 06 Mar 2010 09:12:41 AM UTC
   
 
Category:  None Should Start On:  Sat 06 Mar 2010 12:00:00 AM UTC
Should be Finished on:  Sat 06 Mar 2010 12:00:00 AM UTC Priority:  5 - Normal
Status:  Done Privacy:  Public
Assigned to:  goldsimon Percent Complete:  100%
Open/Closed:  Closed Planned Release:  None
Effort:  0.00

Mon 08 Mar 2010 06:24:58 PM UTC, comment #3: 

Done:
- netif_set_ipaddr doesn't abort existing connections when pcb->local_ip is a LLA
- ip_input compares for netif->autoip->llipaddr, too

Simon Goldschmidt <goldsimon>
Group administrator
Mon 08 Mar 2010 02:06:48 PM UTC, comment #2: 


>Now, are we compliant or not? I hope we are (aside from this task...


Aside from this task I can't say. The contributor should  be able to tell us.  I'll review it as time permits.

Being compliant will be required for the new ZeroConf tasks that were recently added.

Bill Auerbach <billauerbach>
Sat 06 Mar 2010 10:14:23 AM UTC, comment #1: 


> Since we support LLA (compliant or not)


Now, are we compliant or not? I hope we are (aside from this task - I've just fixed some tiny issues I noticed while reading RFC3927), but if you find anything that's not RFC-compliant, please don't hesitate to discuss it here or on lwip-devel!

> don't we now fall under RFC3927's DHCP provisions when LLA is
> enabled?


Well, RFC3927 explicitly states that there is no such thing. Excerpt from RFC3927 ch. 2.11:
"A device that implements both IPv4 Link-Local and a DHCPv4 client
should not alter the behavior of the DHCPv4 client to accommodate
IPv4 Link-Local configuration."

However, if there were, we would have to follow it, no matter if LLA is enabled or not.

Simon Goldschmidt <goldsimon>
Group administrator
Sat 06 Mar 2010 09:12:41 AM UTC, original submission:  

Discussion continued from bug #29072, which was a bit off-topic there...

RFC3927 (chapter 1.9) recommends to let existing connections continue to work when changing a netif's address from a link-local address to a DHCP- or static address.

While we currently suspect this won't work, we will have to check it before deciding whether to implement this or not.

Simon Goldschmidt <goldsimon>
Group administrator

 

(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 billauerbach (Posted a comment)
  • -email is unavailable- added by goldsimon (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
    2010-03-08 goldsimon StatusNone Done
        Percent Complete0% 100%
        Assigned toNone goldsimon
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code