neighbor-changes

[iddq]

** Bug Report **

"connected" message received via API even if the neighbor is unreachable (No route to host)

up or connected message should be received after the BGP session established

exabgp/lib/exabgp/reactor/protocol.py

Line 111 in db41669

for connected in self.connection.establish():

exabgp/lib/exabgp/reactor/network/outgoing.py

Line 43 in db41669

return exc

[iddq]

plus, neighbor IP up message received only when the remote router is the connection initiator. you can easily reproduce it if you bind to other port than 179 and you can see the session will be negotiated but you won't receive any "up" message through API.

[thomas-mangin]

perhaps naming the function "establish" was not super wise. it is about establishing the TCP connection and not getting to the established state in BGP. connected is not established... :-)