Re: Need help with OpenBGPd Configuration

2005-12-08 Thread Kirk Ismay

Jason Ackley wrote:

 Do you have a valid route entry in your kernel routing tables point to 
 the 64.114.173.22  via 207.194.161.134? 

 The 'set nexthop' is used for modifying the BGP attributes, it does not 
in any way indicate which way the openbgpd host should use to get to the 
peer address.. This is not required in your configuration most likely.


I hate to say it, but you may also want to look at upgraded to openbsd 
3.8 with the latest openbgpd, as it is an area that has seen rapid 
development.


You don't want to deploy mission-critical router and then be stuck running 
older software on it..




I have it working now. I had to restart the bgpd, my 'set nexthop 
statement' confused my system into thinking that the intermediate router 
 was my BGP neighbor.


Thanks for the advice.

--
Sincerely,
Kirk Ismay
System Administrator

--
Net Idea
201-625 Front Street Nelson, BC V1L 4B6
P:250-352-3512 | F:250-352-9780 | TF:888-246-4222

10 Years of Service Excellence!

Visit us online at:
www.netidea.com | www.netidea.biz



Re: Need help with OpenBGPd Configuration

2005-12-08 Thread Claudio Jeker
On Thu, Dec 08, 2005 at 09:12:52AM -0800, Kirk Ismay wrote:
> Hi all,
> 
> I'm trying to set up a multihomed network using OpenBGPd on OpenBSD 3.6. 
>  I've got a BGP session up with my first ISP which works fine. Now I am 
> trying to set up BGP with my second ISP, which needs a multihop 
> configuration. I have not been able to get it working on my own, and was 
> unable to find any example configurations on this matter for OpenBGPd.
> 

Why 3.6? 3.8 is out and there where many many many changes and bugfixes in
OpenBGPD in that year.

> My only BGP experience so far is with OpenBGP, so I'm quite new at this.
> 
> They asked me to set up the following (they of course assume I have a 
> cisco):
> 
> router bgp 33714
>  neighbor 64.114.173.22 remote-as 852
>  neighbor 64.114.173.22 ebgp-multihop 2
> 
> I translated that as:
> 
> peer1="64.114.173.22"
> neighbor $peer1 {
> remote-as   852
> descr   ISP2
> announceself
> multihop 2
> #set nexthop 207.194.161.134
> }
> 

Looks OK. Have you tried to increase the multihop value?

> 207.194.161.134 is the router in between me and 64.114.173.22 - I've 
> tried with and without "set nexthop 207.194.161.134".  We've also tried 
> with and without md5 passwords.
> 

set nexthop does not what you think it will do. It will just overwrite all
nexthops coming from this peer. Without a running session set nexthop will
not change anything.

> I can also provide tcpdump log if it will help.
> 

Can you ping the other router?
Is the traceroute output looking sane? (like only 2 hops to the
destination)
Any specific log messages about that neighbor in /var/log/daemon?
Also check with "netstat -an | grep 179" that bgpd is listening on the
right address.
Finally that plus the tcpdump would be enough information to tell you
where the problem is.

-- 
:wq Claudio



Re: Need help with OpenBGPd Configuration

2005-12-08 Thread Stuart Henderson

--On 08 December 2005 09:12 -0800, Kirk Ismay wrote:


I'm trying to set up a multihomed network using OpenBGPd on OpenBSD
3.6.


Upgrading to 3.8, -stable or -current would be a *very* good idea. 
OpenBGPd was very new at 3.6.



and was unable to find any example configurations on this matter for
OpenBGPd.






Need help with OpenBGPd Configuration

2005-12-08 Thread Kirk Ismay

Hi all,

I'm trying to set up a multihomed network using OpenBGPd on OpenBSD 3.6. 
 I've got a BGP session up with my first ISP which works fine. Now I am 
trying to set up BGP with my second ISP, which needs a multihop 
configuration. I have not been able to get it working on my own, and was 
unable to find any example configurations on this matter for OpenBGPd.


My only BGP experience so far is with OpenBGP, so I'm quite new at this.

They asked me to set up the following (they of course assume I have a 
cisco):


router bgp 33714
 neighbor 64.114.173.22 remote-as 852
 neighbor 64.114.173.22 ebgp-multihop 2

I translated that as:

peer1="64.114.173.22"
neighbor $peer1 {
remote-as   852
descr   ISP2
announceself
multihop 2
#set nexthop 207.194.161.134
}

207.194.161.134 is the router in between me and 64.114.173.22 - I've 
tried with and without "set nexthop 207.194.161.134".  We've also tried 
with and without md5 passwords.


I can also provide tcpdump log if it will help.

Sincerely,
Kirk Ismay
System Administrator