| To: | "'kuznet@xxxxxxxxxxxxx'" <kuznet@xxxxxxxxxxxxx> |
|---|---|
| Subject: | 回覆: ndisc_send_ns: always use link-local addr of the leaving device |
| From: | Moter Du <Moter_Du@xxxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 15 Feb 2001 09:39:25 +0800 |
| Cc: | netdev@xxxxxxxxxxx |
| Sender: | owner-netdev@xxxxxxxxxxx |
|
4.3. Neighbor Solicitation Message Format IP Fields: Source Address
7.2.2. Sending Neighbor Solicitations
Specifications are listed above for your reference. Note, in the illustration using [RUT] eth1 global-unicast address as Source Address of NS always violates the specification, because it's none of the addresses assigned to the outgoing interface (i.e., eth0). Any scope of addresses of [RUT] eth0 may be used as Source Address of NS. The patch uses link-local always and I see no improper at all. Could you show me more hints for "solicitation avoidance"? > Sincerely
-----原始郵件-----
Hello! > Without the patch, the following scenario illustrates how it violates
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
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:
BTW this is surely error, killing all the idea behind solicitation
Alexey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: MTU and 2.4.x kernel, Alan Cox |
|---|---|
| Next by Date: | TCP Algorithm, Ishtiaq Ahmed |
| Previous by Thread: | Re: MTU and 2.4.x kernel, Alan Cox |
| Next by Thread: | Re: 回覆: ndisc_send_ns: always use link-local, kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |