<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Yes, absolutely nothing appears to be binded according to netstat and nmap.<br></div><div><br></div><div>I only saw bird bind the control socket when debugging with strace.<br></div><div><br></div><div>The logs only has the "Waiting for fe80:10::1%wg1 to bocame my neighbor". <br></div><div><br></div><div>The user is root, and I can ping/nmap fine over the tunnel. </div><div><br></div><div>On Thu, Sep 3, 2020, at 10:04, Alexander Zubkov wrote:<br></div><blockquote type="cite" id="qt" style=""><div>Hi,<br></div><div><br></div><div>So nothing in netstat? And what have you seen in strace? Maybe<br></div><div>something in logs?<br></div><div><br></div><div>On Thu, Sep 3, 2020 at 1:05 AM Skyler Mäntysaari <<a href="mailto:sm@samip.fi">sm@samip.fi</a>> wrote:<br></div><div>><br></div><div>> Hi there,<br></div><div>><br></div><div>> I’m fairly certain that my issue is something rather small, or stupid but I’m unable to get Bird to listen on the 179 port.<br></div><div>><br></div><div>> The other side has direct in the protocol definition which is correct, and I tried this side with that as well but it only says “as213021_hel_node: Waiting for fe80:10::1%wg1 to become my neighbor” so I don’t really have more clues.<br></div><div>><br></div><div>> I did try to do strace and look for bind events, but couldn’t find any except for the control socket.<br></div><div>><br></div><div>> My config can be seen here: <a href="https://dpaste.com/6P6NAUPNX">https://dpaste.com/6P6NAUPNX</a> & peer config: <a href="https://dpaste.com/HJ3SNL8RH">https://dpaste.com/HJ3SNL8RH</a><br></div><div>><br></div><div><br></div></blockquote></body></html>