Аналогичная ситуация:
Хочу присоединиться к некому провайдеру по BGP4, личный номер AS и пул адресов уже купили. возникли проблемы на стыковке quagga и cisco
cat /etc/quagga/daemons
# This file tells the quagga package which daemons to start.
#
# Entries are in the format: <daemon>=(yes|no|priority)
# 0, "no" = disabled
# 1, "yes" = highest priority
# 2 .. 10 = lower priorities
# Read /usr/share/doc/quagga/README.Debian for details.
#
# Sample configurations for these daemons can be found in
# /usr/share/doc/quagga/examples/.
#
# ATTENTION:
#
# When activation a daemon at the first time, a config file, even if it is
# empty, has to be present *and* be owned by the user and group "quagga", else
# the daemon will not be started by /etc/init.d/quagga. The permissions should
# be u=rw,g=r,o=.
# When using "vtysh" such a config file is also needed. It should be owned by
# group "quaggavty" and set to ug=rw,o= though. Check /etc/pam.d/quagga, too.
#
zebra=yes
bgpd=yes
ospfd=no
ospf6d=no
ripd=no
ripngd=no
isisd=no
cat /etc/quagga/zebra.conf
!
! Zebra configuration saved from vty
! 2010/10/08 17:18:57
!
hostname zebra
password test
enable password test
!
log file /var/log/quagga/zebra.log
!
interface eth0
interface eth1
!
ip forwarding
!
line vty
cat /etc/quagga/bgpd.conf
!
! Zebra configuration saved from vty
! 2010/10/09 14:32:09
!
hostname bgpd
password test
enable password test
log file /var/log/quagga/bgpd.log
!
router bgp 1234
bgp router-id 1.1.1.4
network 11.11.11.0/23
neighbor 1.1.1.1 remote-as 1235
!
line vty
!
cat /etc/quagga/debian.conf
#
# If this option is set the /etc/init.d/quagga script automatically loads
# the config via "vtysh -b" when the servers are started.
# Check /etc/pam.d/quagga if you intend to use "vtysh"!
#
vtysh_enable=yes
zebra_options=" --daemon -A 127.0.0.1"
bgpd_options=" --daemon -A 127.0.0.1"
ospfd_options=" --daemon -A 127.0.0.1"
ospf6d_options="--daemon -A ::1"
ripd_options=" --daemon -A 127.0.0.1"
ripngd_options="--daemon -A ::1"
isisd_options=" --daemon -A 127.0.0.1"
AS провайдера: 1235
neighbor провайдера: 1.1.1.1
мой AS: 1324
на моём шлюзе 2 интерфейса:
eth0 в сторону провайдера: ip 1.1.1.4
eth1 в локалку: ip 11.11.11.1
telnet 0 bgpd
bgpd> show bgp neighbors
BGP neighbor is 1.1.1.1, remote AS 1235, local AS 1234, external link
BGP version 4, remote router ID 0.0.0.0
BGP state = OpenSent
Last read 00:27:49, hold time is 180, keepalive interval is 60 seconds
Message statistics:
Inq depth is 0
Outq depth is 0
Sent Rcvd
Opens: 7 0
Notifications: 6 0
Updates: 0 0
Keepalives: 0 0
Route Refresh: 0 0
Capability: 0 0
Total: 13 0
Minimum time between advertisement runs is 30 seconds
For address family: IPv4 Unicast
Community attribute sent to this neighbor(both)
0 accepted prefixes
Connections established 0; dropped 0
Last reset never
Local host: 1.1.1.4, Local port: 42869
Foreign host: 1.1.1.1, Foreign port: 179
Nexthop: 1.1.1.4
Nexthop global: fe80::3a5b:69ff:fe0d:f474
Nexthop local: ::
BGP connection: non shared network
Read thread: on Write thread: off
cat /var/log/quagga/bgpd.log
BGP: 1.1.1.1 sending NOTIFICATION 4/0 (Hold Timer Expired) 0 bytes
BGP: 1.1.1.1 send message type 3, length (incl. header) 21
BGP: 1.1.1.1 went from OpenSent to Idle
BGP: 1.1.1.1 went from Idle to Connect
BGP: 1.1.1.1 open active, local address 1.1.1.4
BGP: 1.1.1.1 sending OPEN, version 4, my as 1234, holdtime 180, id 1.1.1.4
BGP: 1.1.1.1 send message type 1, length (incl. header) 53
BGP: 1.1.1.1 went from Connect to OpenSent
получается quagga посылает пакеты Cisco, а Cisco молчит...
Какие быдут мысли?
Пользователь решил продолжить мысль 12 Октября 2010, 12:12:18:
проблема снята, оказалось затык был в оборудовании провайдера, т.е. где-то на промежутке пакеты резались
Тема: Настройка BGP (Прочитано 5227 раз)
