BGP Error: No listening socket
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@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@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@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
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@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@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@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
On Sat, Apr 10, 2010 at 11:14:56AM +0400, ????????? ?????? wrote:
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. ... I can not understand in any way that happens? What to check up?
Do you use 'listen bgp address' config option? Is bird started with root privileges? Isn't there anything other listening on port 179 (can be checked by netstat -anp) ? BTW, your emails have bad date (Apr 10, 2010). -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Do you use 'listen bgp address' config option?
I tried two variants.
Is bird started with root privileges?
[root@border-t2 ~]# whoami root [root@border-t2 ~]# ps -aef | grep bird root 2877 1 0 12:01 ? 00:00:00 /usr/local/sbin/bird -c /etc/bird.conf root 2884 2671 0 12:01 pts/0 00:00:00 grep bird [root@border-t2 ~]#
Isn't there anything other listening on port 179 (can be checked by netstat -anp) ?
BIRD 1.2.3 ready. bird> down Shutdown requested Connection closed by server. [root@border-t2 ~]# netstat -anp | grep tcp tcp 0 0 :::22 :::* LISTEN 2545/sshd tcp 0 0 ::ffff:10.16.1.73:22 ::ffff:10.16.1.244:2389 ESTABLISHED 2805/2 tcp 0 52 ::ffff:10.16.1.73:22 ::ffff:10.16.1.244:2128 ESTABLISHED 2669/0 tcp 0 0 ::ffff:10.16.1.73:22 ::ffff:10.16.1.244:2379 ESTABLISHED 2699/1 [root@border-t2 ~]# [root@border-t2 ~]# netstat -anp | grep 179 [root@border-t2 ~]# -----Original Message----- From: owner-bird-users@atrey.karlin.mff.cuni.cz [mailto:owner-bird-users@atrey.karlin.mff.cuni.cz] On Behalf Of Ondrej Zajicek Sent: Saturday, July 10, 2010 11:58 AM To: Vladislav Grishin Cc: bird-users@trubka.network.cz Subject: Re: BGP Error: No listening socket On Sat, Apr 10, 2010 at 11:14:56AM +0400, ????????? ?????? wrote:
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. ... I can not understand in any way that happens? What to check up?
Do you use 'listen bgp address' config option? Is bird started with root privileges? Isn't there anything other listening on port 179 (can be checked by netstat -anp) ? BTW, your emails have bad date (Apr 10, 2010). -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Ondrej Zajicek -
Владислав Гришин