| To: | Moter_Du@xxxxxxxxxxxxxxxxxxx (Moter Du) |
|---|---|
| Subject: | Re: ndisc_send_ns: always use link-local addr of the leaving device |
| From: | kuznet@xxxxxxxxxxxxx |
| Date: | Wed, 14 Feb 2001 19:34:19 +0300 (MSK) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <92C0C0AC8AE8D411864300105A835CBB50144A@xxxxxxxxxxxxxxxxxxxxx> from "Moter Du" at Feb 14, 1 02:15:01 pm |
| Sender: | owner-netdev@xxxxxxxxxxx |
Hello! > Without the patch, the following scenario illustrates how it violates > RFC2461 : Please, cite the place which is violated. (I'm sorry, lazy to search myself). > NS contains global-unicast address of eth1 of [RUT] as Source Address > (ERROR!!) I see no error. If it is global scope, it is on link by definition. But bug is really present: it could be link local for another link! > With the patch: > NS contains link-local address of eth0 of [RUT] as Source Address BTW this is surely error, killing all the idea behind solicitation avoidance. Alexey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | ndisc_send_ns: always use link-local addr of the leaving device, Moter Du |
|---|---|
| Next by Date: | Re: MTU and 2.4.x kernel, Alan Cox |
| Previous by Thread: | ndisc_send_ns: always use link-local addr of the leaving device, Moter Du |
| Next by Thread: | Re: MTU and 2.4.x kernel, Alan Cox |
| Indexes: | [Date] [Thread] [Top] [All Lists] |