Hi Claudio & Co.,

I am running 4.3-current. I am using a very basic bgpd config file that worked for 4.2 very well. Unfortunatelly, with -current my router does not want to announce our prefix anymore.

Any ideas?

Thanks,
- Christian

Details: (my as: 303, transit: 304)

I am able to receive prefixes from my transit provider.
bgpctl shows the following (77.X.Y.0/21 being our prefix):

# bgpctl show rib 77.X.Y.0
flags: * = Valid, > = Selected, I = via IBGP, A = Announced
origin: i = IGP, e = EGP, ? = Incomplete

flags destination         gateway          lpref   med aspath origin
      77.X.Y.0/21       A.B.C.D 105     0 304 [SOMEAS] 303 i
I*    77.X.Y.0/21       77.X.Y.2           100     0 i
AI    77.X.Y.0/21       0.0.0.0            100     0 i

So there are two funny things:

- I get my own prefix (announced by our other router, 77.X.Y.2) via the transit provider.
- The line with my announced prefix ("AI") is missing the "*".

2# bgpctl network show
flags: S = Static
flags destination
*     77.X.Y.0/21

/etc/bgpd.conf:

AS 303

router-id 77.X.Z.3

network 77.X.Y.0/21

group "Peering XXXXXXXXXXX" {

        remote-as 304

        neighbor A.B.C.D {
                tcp md5sig password "xxxxxxx"
                announce self
                set localpref 105
        }
}

group IBPG {

group IBPG {

        remote-as 303

        neighbor 77.X.Y.2 {
                tcp md5sig password "xxxxxxxxx"
        }

    [...some other internal IBGP sessions...]
}

deny from any

allow quick from group IBPG
allow from any inet prefixlen 8 - 24
allow from any prefix 0.0.0.0/0

# filter bogus networks
deny from any prefix 10.0.0.0/8 prefixlen >= 8
deny from any prefix 172.16.0.0/12 prefixlen >= 12
deny from any prefix 192.168.0.0/16 prefixlen >= 16
deny from any prefix 169.254.0.0/16 prefixlen >= 16
deny from any prefix 192.0.2.0/24 prefixlen >= 24
deny from any prefix 224.0.0.0/4 prefixlen >= 4
deny from any prefix 240.0.0.0/4 prefixlen >= 4

Reply via email to