| To: | Andrey Savochkin <saw@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: UDP and Dest Unreachable, Port Unreachables |
| From: | Andi Kleen <ak@xxxxxx> |
| Date: | Tue, 20 Feb 2001 12:23:50 +0100 |
| Cc: | Richard Sharpe <sharpe@xxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <20010219162508.A22917@saw.sw.com.sg>; from saw@saw.sw.com.sg on Tue, Feb 20, 2001 at 01:26:26AM +0100 |
| References: | <3.0.6.32.20010219215602.00856770@203.16.214.248> <20010219162508.A22917@saw.sw.com.sg> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Tue, Feb 20, 2001 at 01:26:26AM +0100, Andrey Savochkin wrote: > On Mon, Feb 19, 2001 at 09:56:02PM +1000, Richard Sharpe wrote: > > I wonder what the actual semantics are for receiving UDP datagams? Will the > > kernel receive datagrams if a socket is open with the appropriate SIP, > > SPort, DIP, DPORT combination, or, does there have to be a read scheduled, > > either via a select, or an actual read? > > The datagrams should be received and queued regardless of whether some > process executed select or read. ... except when the socket buffer overflows, but even then it shouldn't send a ICMP. ICMP means that the socket is closed or was not bound to a matching address -Andi -- This is like TV. I don't like TV. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | typo ? in ip6_output(), KANDA Mitsuru / 神田 充 |
|---|---|
| Next by Date: | net packet queue scheduler, packet_type and proto handlers, Krzysztof Halasa |
| Previous by Thread: | Re: UDP and Dest Unreachable, Port Unreachables, Andrey Savochkin |
| Next by Thread: | usagi ipv6 and linux source, Jens-Ulrik Petersen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |