tasklwIP - A Lightweight TCP/IP stack - Tasks: task #7487, ICMP: associate incoming error...

 
 

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

task #7487: ICMP: associate incoming error messages with active pcbs

Submitter:  Simon Goldschmidt <goldsimon>
Submitted:  Wed 21 Nov 2007 07:02:49 PM UTC
   
 
Category:  None Should Start On:  Wed 21 Nov 2007 12:00:00 AM UTC
Should be Finished on:  Wed 21 Nov 2007 12:00:00 AM UTC Priority:  3 - Low
Status:  Cancelled Privacy:  Public
Assigned to:  None Percent Complete:  0%
Open/Closed:  Closed Planned Release:  None
Effort:  0.00

Sat 06 Mar 2010 11:59:18 AM UTC, comment #4: 

Won't do: not necessary. Please reopen if you feel different.

Simon Goldschmidt <goldsimon>
Group administrator
Thu 22 Nov 2007 08:22:23 AM UTC, comment #3: 


>I thought so, too. But then we'd also have to close bug #20155 as 'won't fix'!


Why? tcp_pcb->err() can handle an error without having such feature. Or I'm wrong?

>On the other hand, lwIP might have some troubles communicating over the internet without a mechanism like path MTU discovery, won't it?


There was problem before since DF flag was always set in IP header. But now, I can confirm that July CVS HEAD work (fine?) with TCP on the Internet. About last changes, I can tell you...

Frédéric Bernon <fbernon>
Group Member
Thu 22 Nov 2007 08:11:13 AM UTC, comment #2: 

I thought so, too. But then we'd also have to close bug #20155 as 'won't fix'!

On the other hand, lwIP might have some troubles communicating over the internet without a mechanism like path MTU discovery, won't it?

Simon Goldschmidt <goldsimon>
Group administrator
Wed 21 Nov 2007 07:23:02 PM UTC, comment #1: 

Stuff like this which is essentially optional would risk making lwIP less lightweight, so unless there's a really pressing need for it we should avoid it if we can.

Kieran Mansley <kieranm>
Group Member
Wed 21 Nov 2007 07:02:49 PM UTC, original submission:  

This is only an idea, maybe a lightweight stack doesn't really need it:

- destination unreachable and time exceeded messages could wake up a thread using select on a socket to wait for an error (see bug #20155 'select() with errorfd set')
- a kind of path MTU discovery could be implemented by lowering mss of tcp pcbs (when receiving destination unreachable, fragmentation needed, DF set)

anything more?

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 fbernon (Posted a comment)
  • -email is unavailable- added by kieranm (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 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-03-06 goldsimon StatusNone Cancelled
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code