On 3. Sep 2020, at 17.52, Valery Lutoshkin <vpluto@gmail.com> wrote:

Try it.
It is not about real multihop session, it is about how bird choose interfaces to listen.

From: Skyler Mäntysaari <sm@samip.fi>
Reply: Skyler Mäntysaari <sm@samip.fi>
Date: 3 September 2020 at 21:51:41
To: Valery Lutoshkin <vpluto@gmail.com>
Subject:  Re: Unable to get Bird 2 to listen on the BGP socket

They're directly connected,  so it's not a multihop session so no. 

On Thu, Sep 3, 2020, at 17:49, Valery Lutoshkin wrote:

Hi!

Have you tried to add option “multihop” in the BGP peer configuration? Usually it helps. 

Best regards.

Valery

From: Skyler Mäntysaari <sm@samip.fi>

Reply: Skyler Mäntysaari <sm@samip.fi>

Date: 3 September 2020 at 21:48:13

To: bird-users@network.cz <bird-users@network.cz>

Subject:  Re: Unable to get Bird 2 to listen on the BGP socket

Yes,  absolutely nothing appears to be binded according to netstat and nmap.

I only saw bird bind the control socket when debugging with strace.

The logs only has the "Waiting for fe80:10::1%wg1 to bocame my neighbor". 

The user is root,  and I can ping/nmap fine over the tunnel. 

On Thu, Sep 3, 2020, at 10:04, Alexander Zubkov wrote:

Hi,

So nothing in netstat? And what have you seen in strace? Maybe

something in logs?

On Thu, Sep 3, 2020 at 1:05 AM Skyler Mäntysaari <sm@samip.fi> wrote:

>

> Hi there,

>

> 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.

>

> 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.

>

> I did try to do strace and look for bind events, but couldn’t find any except for the control socket.

>

> My config can be seen here: https://dpaste.com/6P6NAUPNX & peer config: https://dpaste.com/HJ3SNL8RH

>