Помогите разобраться с настройкой транзитного сервера. У меня есть рабочий роутер (Zebra BGP) и AS который принемает инет и раздает в корпоративную сеть. Появился клиент со своей  AS. На него нужно подать инет. Настройки
транзит:
router bgp 12345
bgp router-id IP
bgp log-neighbor-changes
network a.a.a.a
network b.b.b.b
aggregate-address a.a.a.a as-set summary-only
aggregate-address b.b.b.b as-set summary-only
neighbor IP-World remote-as 55555
neighbor IP-World description SONIKA-WORLD
neighbor IP-World soft-reconfiguration inbound
neighbor IP-World route-map SONICO-WORLD-in in
neighbor IP-World route-map SONICO-WORLD-out out
neighbor IP-UA remote-as 555555
neighbor IP-UA description SONIKA-UAIX
neighbor IP-UA soft-reconfiguration inbound
neighbor IP-UA route-map SONICO-UAIX-in in
neighbor IP-UA route-map SONICO-UAIX-out out
neighbor c.c.c.c remote-as 77777  --------------------клиент
neighbor e.e.e.e remote-as 77777 --------------------клиент
!
!
ip prefix-list bogons description bogus nets
ip prefix-list bogons seq 15 permit 0.0.0.0/8 le 32
ip prefix-list bogons seq 20 permit 127.0.0.0/8 le 32
ip prefix-list bogons seq 30 permit 10.0.0.0/8 le 32
ip prefix-list bogons seq 35 permit 172.16.0.0/12 le 32
ip prefix-list bogons seq 40 permit 192.168.0.0/16 le 32
ip prefix-list bogons seq 45 permit 169.254.0.0/16 le 32
ip prefix-list bogons seq 50 permit 224.0.0.0/4 le 32
ip prefix-list bogons seq 55 permit 240.0.0.0/4 le 32
ip prefix-list default description default route
ip prefix-list default seq 10 permit 0.0.0.0/0
ip prefix-list our-CIDR-blocks seq 4 permit b.b.b.b le 32
ip prefix-list our-CIDR-blocks seq 5 permit a.a.a.a le 32
ip prefix-list our-CIDR-blocks seq 6 permit k.k.k.k le 32
ip prefix-list upstream-out seq 10 permit b.b.b.b
ip prefix-list upstream-out seq 20 permit a.a.a.a
ip prefix-list upstream-out seq 30 permit k.k.k.k
!
ip as-path access-list 1 permit _6451[2-9]_
ip as-path access-list 1 permit _645[2-9][0-9]_
ip as-path access-list 1 permit _64[6-9][0-9][0-9]_
ip as-path access-list 1 permit _65[0-9][0-9][0-9]_
!
route-map SONICO-WORLD-in deny 100
match as-path 1
!
route-map SONICO-WORLD-in deny 110
match ip address prefix-list bogons
!
route-map SONICO-WORLD-in deny 115
match ip address prefix-list default
!
route-map SONICO-WORLD-in deny 120
match ip address prefix-list our-CIDR-blocks
!
route-map SONICO-WORLD-in permit 200
set local-preference 100
!
route-map SONICO-WORLD-out permit 100
match ip address prefix-list upstream-out
!
route-map SONICO-WORLD-out deny 200
!
route-map SONICO-UAIX-in deny 100
match as-path 1
!
route-map SONICO-UAIX-in deny 110
match ip address prefix-list bogons
!
route-map SONICO-UAIX-in deny 115
match ip address prefix-list default
!
route-map SONICO-UAIX-in deny 120
match ip address prefix-list our-CIDR-blocks
!
route-map SONICO-UAIX-in permit 200
set local-preference 150
!
route-map SONICO-UAIX-out permit 100
match ip address prefix-list upstream-out
!
route-map SONICO-UAIX-out deny 200

КЛИЕНТ:

router bgp 77777
bgp router-id IP
bgp log-neighbor-changes
network k.k.k.k
aggregate-address k.k.k.k/24 as-set summary-only
neighbor d.d.d.d remote-as 12345
neighbor d.d.d.d description LUCKYNET-UAIX
neighbor d.d.d.d soft-reconfiguration inbound
neighbor d.d.d.d route-map LUCKYNET-UAIX-in in
neighbor d.d.d.d route-map LUCKYNET-UAIX-out out
neighbor t.t.t.t remote-as 12345
neighbor t.t.t.t description LUCKYNET-WORLD
neighbor t.t.t.t soft-reconfiguration inbound
neighbor t.t.t.t route-map LUCKYNET-WORLD-in in
neighbor t.t.t.t route-map LUCKYNET-WORLD-out out
!
!
ip prefix-list bogons description bogus nets
ip prefix-list bogons seq 15 permit 0.0.0.0/8 le 32
ip prefix-list bogons seq 20 permit 127.0.0.0/8 le 32
ip prefix-list bogons seq 30 permit 10.0.0.0/8 le 32
ip prefix-list bogons seq 35 permit 172.16.0.0/12 le 32
ip prefix-list bogons seq 40 permit 192.168.0.0/16 le 32
ip prefix-list bogons seq 45 permit 169.254.0.0/16 le 32
ip prefix-list bogons seq 50 permit 224.0.0.0/4 le 32
ip prefix-list bogons seq 55 permit 240.0.0.0/4 le 32
ip prefix-list default description default route
ip prefix-list default seq 10 permit 0.0.0.0/0
ip prefix-list our-CIDR-blocks seq 4 permit k.k.k.k le 32
ip prefix-list upstream-out seq 10 permit k.k.k.k
!
ip as-path access-list 1 permit _6451[2-9]_
ip as-path access-list 1 permit _645[2-9][0-9]_
ip as-path access-list 1 permit _64[6-9][0-9][0-9]_
ip as-path access-list 1 permit _65[0-9][0-9][0-9]_
!
route-map LUCKYNET-WORLD-in deny 100
match as-path 1
!
route-map LUCKYNET-WORLD-in deny 110
match ip address prefix-list bogons
!
route-map LUCKYNET-WORLD-in deny 115
match ip address prefix-list default
!
route-map LUCKYNET-WORLD-in deny 120
match ip address prefix-list our-CIDR-blocks
!
route-map LUCKYNET-WORLD-in permit 200
set local-preference 100
!
route-map LUCKYNET-WORLD-out permit 100
match ip address prefix-list upstream-out
!
route-map LUCKYNET-WORLD-out deny 200
!
route-map LUCKYNET-UAIX-in deny 100
match as-path 1
!
route-map LUCKYNET-UAIX-in deny 110
match ip address prefix-list bogons
!
route-map LUCKYNET-UAIX-in deny 115
match ip address prefix-list default
!
route-map LUCKYNET-UAIX-in deny 120
match ip address prefix-list our-CIDR-blocks
!
route-map LUCKYNET-UAIX-in permit 200
set local-preference 150
!
route-map LUCKYNET-UAIX-out permit 100
match ip address prefix-list upstream-out
!
route-map LUCKYNET-UAIX-out deny 200

С роутера клиента я пингую мир, а вот мир не видит сетку клиента и адреса не пингуются, хотя с сети провайдера я сервер клиента вижу. По ходу на сервере провайдера не правильно прописана конфа в сторону клиента. Мудрые люди подскажите где копать.

• настройка Zebra BGP,ivb, 13:44 , 12-Сен-11
  • настройка Zebra BGP,serj81, 13:59 , 12-Сен-11
    • настройка Zebra BGP,erera22, 12:43 , 13-Сен-11
      • настройка Zebra BGP,serj81, 12:19 , 14-Сен-11

Для  начала:

Сети клиента анонсируются по BGP ?
show ip bgp nei xxxx advertised-routes
аплинк получает ваши анонсы ?
надо узнать.
сеть клиента имеет объекты ROUTE в RIPE ?

> Для  начала:
> Сети клиента анонсируются по BGP ?
> show ip bgp nei xxxx advertised-routes
> аплинк получает ваши анонсы ?
> надо узнать.
> сеть клиента имеет объекты ROUTE в RIPE ?

на транзите show ip bgp nei

BGP neighbor is x.x.x.x, remote AS 77777, local AS 12345, external link
  BGP version 4, remote router ID y.y.y.y
  BGP state = Established, up for 02:30:44
  Last read 13:14:30, hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Route refresh: advertised and received(old & new)
    Address family IPv4 Unicast: advertised and received
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 14          5
    Notifications:          3          7
    Updates:           666619         11
    Keepalives:           342        324
    Route Refresh:          0          0
    Capability:             0          0
    Total:             666978        347
  Minimum time between advertisement runs is 30 seconds

For address family: IPv4 Unicast
  Community attribute sent to this neighbor(both)
  1 accepted prefixes

  Connections established 11; dropped 10
  Last reset 02:32:12, due to BGP Notification received
Local host: x.x.x.x, Local port: 179
Foreign host:  x1.x1.x1.x1, Foreign port: 64055
Nexthop: x.x.x.x
Nexthop global: ::
Nexthop local: ::
BGP connection: non shared network
Read thread: on  Write thread: off

мне кажется, что транзит не отправляет маршрут к клиенту, дальше следующему узлу, ведь я вижу сетку с сетитной.

Вы в ripe прописали роут-объекты? Внесли members, import, export в as-set?

> Вы в ripe прописали роут-объекты? Внесли members, import, export в as-set?

ситуация прояснилась, дело в том, что на сайте Ripe.net моя новая AS прописана не правильно, а именно export, import прописан не верно, ссылка не на ту AS.