Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*source\s+address\s+selection\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*source\s+address\s+selection\s*$/: 18 ]

Total 18 documents matching your query.

1. Re: source address selection (score: 1): Author: Yuji Sekiya <sekiya@xxxxxxx>; Date: Mon, 10 Jan 2000 15:30:11 -0800; Hello Alexey, Sorry for my late response. Hmm... I apologize that you confused the issue due to my poor English :-p In brief, we want the mechanism of source address selection into IPv6 stack. If we; /archives/netdev/2000-01/msg00015.html (9,007 bytes)
2. source address selection (score: 1): Author: Takeshi Kusune / 楠根雄志 <kusune@xxxxxxxxxxxxxx>; Date: Thu, 16 Dec 1999 08:51:34 +0900; That's a nice early X'mas gift :), Thank you. BTW, I think that Linux's current IPv6 code is not enough to work with multi-addressed network, because of weakness in source address selection. I made; /archives/netdev/1999-12/msg00030.html (9,436 bytes)
3. Re: source address selection (score: 1): Author: xxxxxx>; Date: Thu, 16 Dec 1999 19:09:31 +0300 (MSK); The patch is good and correct, but the solution is bad. We may make this thing in IPv4 because function inet_select_addr() is not in data path; selected source addresses are stored in routing tables; /archives/netdev/1999-12/msg00035.html (9,069 bytes)
4. Re: source address selection (score: 1): Author: xxxxxx>; Date: Wed, 29 Dec 1999 18:38:03 +0900; Hi, Hmm... I think what you say is right. But IMHO, I think that source address selection is more useful in IPv6 environment than IPv4 environment. Because IPv6 allows us to assign some IPv6 addresse; /archives/netdev/1999-12/msg00078.html (9,796 bytes)
5. Re: source address selection (score: 1): Author: xxxxxx>; Date: Wed, 29 Dec 1999 10:54:49 +0100; Source address selection for IPv6 is very useful feature. I give one real example: I use zebra as routing daemons. My machine has 2 IPv6 address at eth1 (internal LAN). I must set both address as nei; /archives/netdev/1999-12/msg00079.html (10,810 bytes)
6. Re: source address selection (score: 1): Author: xxxxxx>; Date: Wed, 29 Dec 1999 18:56:02 +0300 (MSK); zebra, sets source address _itself_ without help from kernel. Actually, routing daemons _must_ not use any automatic selection at all. If Zebra really does not bind() its sockets, it is strongly bro; /archives/netdev/1999-12/msg00080.html (8,564 bytes)
7. Re: source address selection (score: 1): Author: xxxxxxx; Date: Wed, 29 Dec 1999 19:09:22 +0300 (MSK); I do not understand. IPv6 and IPv4 are absolutely identical here. In 2.5. Alexey; /archives/netdev/1999-12/msg00082.html (8,480 bytes)
8. Re: source address selection (score: 1): Author: xxxxxx>; Date: Fri, 31 Dec 1999 00:05:40 +0900; Hello Alexey, It's a good news ! Thanks for your interest in this problem. Until your implementation has come, we will use kusune's patch for source address selection. Regards. -- SEKIYA Yuji USC/ISI; /archives/netdev/1999-12/msg00087.html (9,276 bytes)
9. Re: source address selection (score: 1): Author: xxxxxxx; Date: Thu, 30 Dec 1999 18:40:51 +0300 (MSK); Grrrr, I am replying to myself.... Seems, I misread your reply and you misread that mail, which I replied. 8) The result is full misunderstanding. Please, explain. What is "source address selection"; /archives/netdev/1999-12/msg00089.html (8,690 bytes)
10. Re: source address selection (score: 1): Author: Yuji Sekiya <sekiya@xxxxxxx>; Date: Mon, 10 Jan 2000 15:30:11 -0800; Hello Alexey, Sorry for my late response. Hmm... I apologize that you confused the issue due to my poor English :-p In brief, we want the mechanism of source address selection into IPv6 stack. If we; /archives/netdev/2000-01/msg00072.html (9,171 bytes)
11. source address selection (score: 1): Author: Takeshi Kusune / <kusune@xxxxxxxxxxxxxx>; Date: Thu, 16 Dec 1999 08:51:34 +0900; Hi, Alex. That's a nice early X'mas gift :), Thank you. BTW, I think that Linux's current IPv6 code is not enough to work with multi-addressed network, because of weakness in source address selection; /archives/netdev/1999-12/msg00122.html (9,465 bytes)
12. Re: source address selection (score: 1): Author: kuznet@xxxxxxxxxxxxx; Date: Thu, 16 Dec 1999 19:09:31 +0300 (MSK); Hello! The patch is good and correct, but the solution is bad. We may make this thing in IPv4 because function inet_select_addr() is not in data path; selected source addresses are stored in routing; /archives/netdev/1999-12/msg00127.html (9,098 bytes)
13. Re: source address selection (score: 1): Author: Yuji Sekiya <sekiya@xxxxxxx>; Date: Wed, 29 Dec 1999 18:38:03 +0900; Hi, Hmm... I think what you say is right. But IMHO, I think that source address selection is more useful in IPv6 environment than IPv4 environment. Because IPv6 allows us to assign some IPv6 addresse; /archives/netdev/1999-12/msg00170.html (9,883 bytes)
14. Re: source address selection (score: 1): Author: Artur Frysiak <wiget@xxxxxxxxxxxxxxxxxx>; Date: Wed, 29 Dec 1999 10:54:49 +0100; Source address selection for IPv6 is very useful feature. I give one real example: I use zebra as routing daemons. My machine has 2 IPv6 address at eth1 (internal LAN). I must set both address as nei; /archives/netdev/1999-12/msg00171.html (10,954 bytes)
15. Re: source address selection (score: 1): Author: kuznet@xxxxxxxxxxxxx; Date: Wed, 29 Dec 1999 18:56:02 +0300 (MSK); Hello! zebra, sets source address _itself_ without help from kernel. Actually, routing daemons _must_ not use any automatic selection at all. If Zebra really does not bind() its sockets, it is strong; /archives/netdev/1999-12/msg00172.html (8,621 bytes)
16. Re: source address selection (score: 1): Author: kuznet@xxxxxxxxxxxxx; Date: Wed, 29 Dec 1999 19:09:22 +0300 (MSK); Hello! I do not understand. IPv6 and IPv4 are absolutely identical here. In 2.5. Alexey; /archives/netdev/1999-12/msg00174.html (8,502 bytes)
17. Re: source address selection (score: 1): Author: Yuji Sekiya <sekiya@xxxxxxx>; Date: Fri, 31 Dec 1999 00:05:40 +0900; Hello Alexey, It's a good news ! Thanks for your interest in this problem. Until your implementation has come, we will use kusune's patch for source address selection. Regards. -- SEKIYA Yuji USC/ISI; /archives/netdev/1999-12/msg00179.html (9,356 bytes)
18. Re: source address selection (score: 1): Author: kuznet@xxxxxxxxxxxxx; Date: Thu, 30 Dec 1999 18:40:51 +0300 (MSK); Hello! Grrrr, I am replying to myself.... Seems, I misread your reply and you misread that mail, which I replied. 8) The result is full misunderstanding. Please, explain. What is "source address sele; /archives/netdev/1999-12/msg00181.html (8,712 bytes)

Current List: 1 - 18
Page: [1]