so I am stuck but yes it would be the long and correct way - thank you for reminding me
finishing the patch ..
should be done soon
As long the the nice pear liqueur is not too harmful to my coding :wink2:
documentation for the MD5 and new per peer “listen” which allows to set per peer MD5
@sanjmonkey can I please have your full name for the changelog ?
done
22:06:11.174545 IP <x.x.x.x>.40356 > <y.y.y.y>.179: Flags [S], seq 3786399209, win 29200, options [nop,nop,md5valid,mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
on the receiving exabgp you need to add
“listen <port>"
sorry
like you would do for passive
or hold-time
MD5 is a per peer setting
previously the only way to listen was via the global option exabgp.tcp.bind
it is not the case anymore
hence why the patch took a few hours
passive side is listening as it should
so without using the global listening option a passive neighbour is as good as unconfigured
listen <port> accept incoming connection
so both options are orthogonals
you can have passive, passive + listen, listen
hum .. not sure why it does not work for you ...
I need to add an “active” or “port” option to set out on what port the peer will connect out ..
when I tried I only tested 1790 ( to not have to use root )