Unable to get Bird 2 to listen on the BGP socket

[Skyler Mäntysaari]

I did that, but it did not change anything.
Still not binding.

> On 3. Sep 2020, at 18.34, Bernd Naumann <bena at spreadshirt.net> wrote:
> 
> I think its useless to fight over top- or bottom-posting here. Anyway:
> 
> Could it be that
> ```
> 	local fe80:10::2 as OWNAS;
> ```
> should rather be
> ```
> 	local fe80:10::2%wg1 as OWNAS;
> ```
> ?
> 
> Maybe Maria or one of the other bird maintainer can give an insight if this is even valid or needed when using IPv6 LLA.
> 
> Did you try to specify `interface`?
> 
> The documentation says:
> """
> interface string
> 
>    Define interface we should use for link-local BGP IPv6 sessions. Interface can also be specified as a part of neighbor address (e.g., neighbor fe80::1234%eth0 as 65000;). The option may also be used for non link-local sessions when it is necessary to explicitly specify an interface, but only for direct (not multihop) sessions.
> """
> 
> from which I assume, that the user needs either `%ifname` on `neighbor` _or_ `interface <if>`?
> 
> 
> 
> Off-topic, unrelated, and just my2cents: If wireguard would just support the auto-generation of LLA _and_ support Multicast we could all together just run OSPF (or any other IGP) on the tunnel-interface, handling the propagation of the router-ids and just use these for the `local` and `neighbor` stanza... (or do I miss something here?)
> 
> 
> On 03.09.20 16:48, Skyler Mäntysaari wrote:
>> The allowedIps shouldn't be the issue.  I can ping fine and even nmap.
>> Having the "direct" statement in the protocol defition does not change the behavior in any way.
>> P. S Please reply by writing up here and not below.
>> On Thu, Sep 3, 2020, at 14:49, Bernd Naumann wrote:
>>> On 03.09.20 00:57, Skyler Mäntysaari 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 <https://dpaste.com/6P6NAUPNX> & peer config: https://dpaste.com/HJ3SNL8RH <https://dpaste.com/HJ3SNL8RH>
>>>> 
>>>> 
>>> 
>>> Hi Skyler,
>>> 
>>> Do you have assigned "fe80:10::2" to `wg1`? (Just to make sure...) I
>>> think otherwise bird would not be able to bind to the address.
>>> And you have configured `AllowedIPs = 0.0.0.0/0, ::/0`?
>>> 
>>> Obvious question #2: You can ping6 the peer on fe80:10::1%wg1 ?
>>> 
>>> I would also enable "direct" for the peer, as you are directly connected
>>>   via the tunnel.
>>>