Date: Wed, 14 Mar 2007 18:20:51 +0000 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: Gleb Smirnoff <glebius@FreeBSD.org>, "Bruce M. Simpson" <bms@FreeBSD.org>, freebsd-net@FreeBSD.org, Vladimir Ivanov <wawa@yandex-team.ru>, bug-followup@FreeBSD.org Subject: Re: kern/106722: [net] [patch] ifconfig may not connect an interface to known network Message-ID: <45F83D03.9020501@FreeBSD.org> In-Reply-To: <20070314161023.GF2713@cell.sick.ru> References: <20070314115916.GB2713@cell.sick.ru> <45F81C0D.2000608@FreeBSD.org> <20070314161023.GF2713@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Gleb Smirnoff wrote: > I was afraid that this would raise an argument on multipath routing. Let's > temporary do not speak about multipath but just decide what is the correct > way to remove conflicting routes when we are assigning an IP prefix to a > local interface? > My suggestion is to take the second approach you outlined but modify it slightly. That way, the conflict between the 'connected' FTE introduced by ifconfig'ing the interface and the pre-existing FTE for that network prefix, may be resolved in a manner which doesn't break current consumers of the routing code, and leaves the way open to do multipath later w/o problems. Regards, BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45F83D03.9020501>