Thnx for your fast reply. It works very well and saved us a lot of configuration time! By the way do you know why this isn't nescesary by using Quagga? (A little bit off topic, but I am just wondering).
Henning Brauer wrote: > > * Tom Martin <openb...@lekl.nl> [2009-05-06 15:41]: >> May 6 17:00:01 openBSD4-5 bgpd[5747]: neighbor 192.168.113.100 (test.4): >> received notification: error in UPDATE message, AS-Path unacceptable >> >> At the client side we see a fatal error: >> >> Apr 6 17:00:05 bsd bgpd[24969]: neighbor 192.168.113.1 (test): state >> change >> Established -> Idle, reason: Fatal error >> >> When we use quagga as client the session is doing fine on both sides, >> even >> with community filters. When we are using OpenBGPD we keep facing this >> message until we are removing the following line: transparent-as yes. Is >> this a comment problem, or is this a bad configuration of us? > > bad config on the client side - must use > enforce neighbor-as no > > OpenBGPD enforces that AS Pathes from a neighbor begin with his AS by > default. If the neighbor is a transparent route-server, that is - of > course - not the case. > > -- > Henning Brauer, h...@bsws.de, henn...@openbsd.org > BS Web Services, http://bsws.de > Full-Service ISP - Secure Hosting, Mail and DNS Services > Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam > > > -- View this message in context: http://n2.nabble.com/OpenBGPD-transparent-as-issue-tp2815387p2816439.html Sent from the OpenBSD Misc mailing list archive at Nabble.com.
