BGP Error: No listening socket
Владислав Гришин
Vladislav.Grishin at vts24.ru
Sat Apr 10 08:38:22 CEST 2010
Hi!
I have been forced to change customisations of network interfaces on a
server with bird. After modification bird.conf I has checked up availability
of BGP neighbors. Everything is all right. ping ok. telnet <ip of bgp
neighbor> 179 - ok. After restart bird see error in/var/log/messges
May 12 10:03:01 border-t2 bird: Reconfiguring
May 12 10:03:01 border-t2 bird: Enabling protocol bgpfiord
May 12 10:03:01 border-t2 bird: Enabling protocol bgpabonent
May 12 10:03:01 border-t2 bird: Reconfigured
May 12 10:03:01 border-t2 bird: sk_open: bind: Cannot assign requested
address
May 12 10:03:01 border-t2 bird: BGP: Unable to open listening socket
May 12 10:03:01 border-t2 bird: sk_open: bind: Cannot assign requested
address
May 12 10:03:01 border-t2 bird: BGP: Unable to open listening socket
OSPF the protocol works perfectly. BGP no.
[root at border-t2 etc]# ping 93.191.9.205
PING 93.191.9.205 (93.191.9.205) 56(84) bytes of data.
64 bytes from 93.191.9.205: icmp_seq=1 ttl=64 time=0.799 ms
64 bytes from 93.191.9.205: icmp_seq=2 ttl=64 time=0.824 ms
64 bytes from 93.191.9.205: icmp_seq=3 ttl=64 time=0.836 ms
--- 93.191.9.205 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.799/0.819/0.836/0.036 ms
[root at border-t2 etc]#
bird> show protocols myospf
name proto table state since info
myospf OSPF master up 09:37 Running
bird>
bird> show protocols bgpabonent
name proto table state since info
bgpabonent BGP testable down 10:02 Error: No listening socket
bird>
bird> show protocols bgpfiord
name proto table state since info
bgpfiord BGP master down 10:02 Error: No listening socket
bird>
[root at border-t2 ~]# birdc
BIRD 1.2.3 ready.
bird> show interfaces
lo up (index=1)
MultiAccess AdminUp LinkUp Loopback Ignored MTU=16436
127.0.0.1/8 (Primary, broadcast 127.255.255.255, scope host)
eth0 DOWN (index=2)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
eth1 DOWN (index=3)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
eth2 up (index=4)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
10.16.1.73/24 (Primary, broadcast 10.16.1.255, scope site)
eth0.20 up (index=5)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
192.168.20.1/24 (Primary, broadcast 192.168.20.255, scope site)
eth0.701 up (index=6)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
93.191.9.206/30 (Primary, broadcast 93.191.9.207, opposite
93.191.9.205, scope univ) <-----FOR bgpfiord
eth1.10 up (index=8)
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
192.168.10.1/24 (Primary, broadcast 192.168.10.255, scope site)
eth1.550 up (index=9) <------FOR OSPF and bgpabonent
MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500
10.10.1.2/25 (Primary, broadcast 10.10.1.127, scope site)
sit0 DOWN (index=10)
MultiAccess AdminUp LinkDown MTU=1480
bird>
bird> show interfaces summary
interface state address
lo up 127.0.0.1/8
eth0 DOWN
eth1 DOWN
eth2 up 10.16.1.73/24
eth0.20 up 192.168.20.1/24
eth0.701 up 93.191.9.206/30 <--for bgpfiord
eth1.10 up 192.168.10.1/24
eth1.550 up 10.10.1.2/25 <--for bgpabonent and myospf
sit0 DOWN
bird>
I can not understand in any way that happens? What to check up?
Vladislav Grishin
More information about the Bird-users
mailing list