From owner-freebsd-current@FreeBSD.ORG Mon Apr 10 04:03:08 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B60C916A400 for ; Mon, 10 Apr 2006 04:03:08 +0000 (UTC) (envelope-from dd@freebsd.org) Received: from charade.trit.org (charade.trit.org [65.19.139.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61DF743D46 for ; Mon, 10 Apr 2006 04:03:08 +0000 (GMT) (envelope-from dd@freebsd.org) Received: from maverick.trit.org (maverick.trit.org [IPv6:2001:4830:2381:2062:212:f0ff:fe4c:896a]) by charade.trit.org (Postfix) with ESMTP id 0AD501AF9A6; Mon, 10 Apr 2006 04:03:07 +0000 (UTC) Received: from maverick.trit.org (localhost [127.0.0.1]) by maverick.trit.org (8.13.6/8.13.4) with ESMTP id k3A437Zc003918; Mon, 10 Apr 2006 04:03:07 GMT (envelope-from dd@freebsd.org) Received: (from dima@localhost) by maverick.trit.org (8.13.6/8.13.4/Submit) id k3A437OF003917; Mon, 10 Apr 2006 04:03:07 GMT (envelope-from dd@freebsd.org) X-Authentication-Warning: maverick.trit.org: dima set sender to dd@freebsd.org using -f Date: Mon, 10 Apr 2006 04:03:07 +0000 From: Dima Dorfman To: Nik Message-ID: <20060410040306.GA1001@trit.org> References: <60ffc71f0604092047u4abfd62eg24a0af4b4e6a1d7@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <60ffc71f0604092047u4abfd62eg24a0af4b4e6a1d7@mail.gmail.com> X-PGP-Key: 69FAE582 (https://www.trit.org/~dima/dima.asc) X-PGP-Fingerprint: B340 8338 7DA3 4D61 7632 098E 0730 055B 69FA E582 User-Agent: Mutt/1.5.9i Cc: current@freebsd.org Subject: Re: BGP: can't connect to fd 10 : Can't assign requested address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 04:03:08 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Nik wrote: > 2 router is distribution and 2 router is core. I think to implement IBGP I > need to run bgp daemon in distribution router (please advise). You need to run iBGP on every router in the AS that needs to see BGP routes. Depending on what you're calling a "distribution" router, you might be able to get away with just using default routes. The main reason for running BGP on distribution or access routers is if you want those routers to make best-path decisions or if you have BGP-speaking customers. > 2006/04/10 11:12:32 BGP: can't connect to xx.xx.xx fd 10 : Can't assign > requested address >=20 > FYI, I try to run IBGP with loopback (lo0), here is my config's file in o= ne > of my router; >=20 > neighbor OCE-IBGP peer-group > neighbor OCE-IBGP remote-as 65478 > neighbor OCE-IBGP update-source lo0 Do you have a routable address configured on lo0? Even if you do, I suspect what's happening is that it's choosing 127.0.0.1, which can't reach the other router. Try this: neighbor OCE-IBGP update-source 1.2.3.4 where 1.2.3.4 is a /32 alias on lo0. Obviously all the other routers need to have host routes for that loopback addresses. The typical configuration is to carry those loopback routes in an IGP (like OSPF). --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFEOdj6BzAFW2n65YIRArO5AJ9wjti1Ga7ZIy+tG0/kYMlH68y5gACZAYi6 sVo/Jgz44R31J4XvXFXbiOI= =mtJ3 -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z--