Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*primary\s+and\s+secondary\s+ip\s+addresses\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*primary\s+and\s+secondary\s+ip\s+addresses\s*$/: 64 ]

Total 64 documents matching your query.

1. Re: primary and secondary ip addresses (score: 1): Author: xx>; Date: Sun, 8 May 2005 15:31:15 +0300; I'm using it for some weeks in production and haven't noticed any issues either. Would be really good to see it kernel. regards, -- Hasso Tepper Elion Enterprises Ltd. WAN administrator; /archives/netdev/2005-05/msg00369.html (9,007 bytes)
2. Re: primary and secondary ip addresses (score: 1): Author: forge@xxxxxxxxxxxxx>; Date: Thu, 26 May 2005 20:11:18 +0200; David, would you consider applying that patch to mainline? I think there was concensus on this solution, and it has now received some amount of testing by Hasso and me. Thanks! -- - Harald Welte <laf; /archives/netdev/2005-05/msg01037.html (10,018 bytes)
3. Re: primary and secondary ip addresses (score: 1): Author: anium2003@xxxxxxxxx>; Date: Thu, 26 May 2005 20:21:46 +0200; * Harald Welte <20050526181118.GK13114@xxxxxxxxxxxxxxxxxxxxxxx> 2005-05-26 20:11 I agree, I've been running this patch for 3 weeks now without any problems. Two comments below. promote can only be !=; /archives/netdev/2005-05/msg01038.html (9,064 bytes)
4. Re: primary and secondary ip addresses (score: 1): Author: xxxxx>; Date: Thu, 26 May 2005 14:58:07 -0700 (PDT); Since it retains the default behavior by default, this change seems fine. I've added it to my tree, thanks.; /archives/netdev/2005-05/msg01070.html (8,090 bytes)
5. Re: primary and secondary ip addresses (score: 1): Author: Harald Welte <laforge@xxxxxxxxxxxx>; Date: Tue, 12 Apr 2005 12:54:42 +0200; Due to a customer having again trouble with this issue, I was forced to actually spend some time testing it (and merging it to a current kernel). At least in my simple tests, it worked like a charm :; /archives/netdev/2005-04/msg00498.html (10,292 bytes)
6. ness in dst_release (score: 1): Author: xxxxxxxxxxxxxx>; Date: Thu, 16 Dec 2004 10:28:32 +0100; ness in dst_release" messages started again. Kernel 2.6.10-rc3-bk2. The first message is below. Arnaldo and Yoshifuji should have already have access to this m; /archives/netdev/2004-12/msg00429.html (10,722 bytes)
7. ondary ip addresses (score: 1): Author: @xxxxxxxxx>; Date: Thu, 16 Dec 2004 11:53:51 +0200; ce november] agreed. ... and why does removing the primary address remove all secondary addresses. This makes it complicated if you have one interface with mul; /archives/netdev/2004-12/msg00430.html (11,843 bytes)
8. ondary ip addresses (score: 1): Author: ge@xxxxxxxxxxxx>; Date: Thu, 16 Dec 2004 11:07:11 +0100 (CET); ss is primary? This reminds me related issue ... Actually there is concept in Junos software I'd love to see in Linux as well. There is "preferred address" and; /archives/netdev/2004-12/msg00431.html (10,647 bytes)
9. ondary ip addresses (score: 1): Author: xxxxxxx>; Date: Thu, 16 Dec 2004 13:02:42 +0200; : And why I can't even choose which address is primary? It is the first you add in a subnet. Primary == Configure this address to be the primary address of the; /archives/netdev/2004-12/msg00432.html (11,473 bytes)
10. eping/timing rework (score: 1): Author: xxxx>; Date: Thu, 16 Dec 2004 17:02:59 +0100 (CET); on had some untested areas (and still has) so it was thought for 2.7 but it's been waiting for more than a year. Do we know anything about 2.7 plans now? BTW B; /archives/netdev/2004-12/msg00436.html (9,940 bytes)
11. ondary ip addresses (score: 1): Author: xxxxxxx>; Date: Thu, 16 Dec 2004 16:48:31 +0000 (UTC); No. There is only one primary address per interface and it is used if destination address doesn't indicate which source address to use. In the linux world you; /archives/netdev/2004-12/msg00437.html (11,070 bytes)
12. user data in kernel (score: 1): Author: <tom@xxxxxxxxxxxxx>; Date: Fri, 17 Dec 2004 10:10:29 -0500; caus; /archives/netdev/2004-12/msg00446.html (13,425 bytes)
13. ondary ip addresses (score: 1): Author: xxxxx>; Date: Fri, 17 Dec 2004 16:27:24 +0100 (CET); s would make things much easier. On top of this, when I change the primary IP, it takes about 500ms to see the change applied which is critical for real time a; /archives/netdev/2004-12/msg00447.html (11,305 bytes)
14. user data in kernel (score: 1): Author: is@xxxxxxxxxx>; Date: Fri, 17 Dec 2004 10:58:10 -0500; Patrick McHardy wrote: James Morris wrote: This at least needs CAP_NET_ADMIN. It is already checked in do_ip6t_set_ctl(). Otherwise anyone could replace iptab; /archives/netdev/2004-12/msg00450.html (12,120 bytes)
15. user data in kernel (score: 1): Author: xxxxxxxxxxxx>; Date: Fri, 17 Dec 2004 17:39:47 +0100 (CET); /archives/netdev/2004-12/msg00453.html (11,824 bytes)
16. ondary ip addresses (score: 1): Author: xxxxxxx>; Date: Fri, 17 Dec 2004 12:17:48 -0500; te: This does not help, since if I want to use my secondary IP address instead of my primary, I cannot delete the primary otherwise all of my secondary IPs are; /archives/netdev/2004-12/msg00454.html (11,723 bytes)
17. ondary ip addresses (score: 1): Author: xxxxx>; Date: Fri, 17 Dec 2004 20:03:22 +0200; you add in a subnet becomes a primary, any additional IPs you add in the same subnet becomes secondary. You can have any number of primary IPs with each any nu; /archives/netdev/2004-12/msg00455.html (10,917 bytes)
18. ondary ip addresses (score: 1): Author: xxxxxxxxxxxxxxx>; Date: Fri, 17 Dec 2004 12:37:02 -0600 (CST); no support for it in most of user space software. None of the routing protocols suites support it etc. -- Hasso Tepper Elion Enterprises Ltd. WAN administrator; /archives/netdev/2004-12/msg00456.html (12,010 bytes)
19. user data in kernel (score: 1): Author: xxxxxxxxxxxxx>; Date: Fri, 17 Dec 2004 20:53:27 +0200; ll Davidsen wrote: James Morris wrote: On Fri, 17 Dec 2004, Patrick McHardy wrote: James Morris wrote: This at least needs CAP_NET_ADMIN. It is already checked; /archives/netdev/2004-12/msg00458.html (12,556 bytes)
20. user data in kernel (score: 1): Author: o@xxxxxxxxx>; Date: Fri, 17 Dec 2004 20:17:07 +0100 (CET); lity to do anything bad :-) Are you saying that processes with capability don't make mistakes? This isn't a bug related to untrusted users doing privileged ope; /archives/netdev/2004-12/msg00460.html (11,850 bytes)

Current List: 1 - 20
Page: [1] [2] [3] [4]