Unable to get Bird 2 to listen on the BGP socket
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, 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
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
Hi! Try to activate “multihop" option in bgp config, sometmes it helps. WBR, Valery From: Skyler Mäntysaari <sm@samip.fi> Reply: Skyler Mäntysaari <sm@samip.fi> Date: 3 September 2020 at 06:08:07 To: bird-users@network.cz <bird-users@network.cz> Subject: Unable to get Bird 2 to listen on the BGP socket 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
Does your configuration have any BGP peers? I've noticed that BIRD doesn't start listening until there is at least one BGP peer. On Thu, Sep 3, 2020 at 12:12 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
If you had taken the time to read the posted links, you would see that it has peers, using Link-Local addresses. On Thu, Sep 3, 2020, at 11:17, Neil Jerram wrote:
Does your configuration have any BGP peers? I've noticed that BIRD doesn't start listening until there is at least one BGP peer.
On Thu, Sep 3, 2020 at 12:12 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
I did look at https://dpaste.com/6P6NAUPNX, and saw that it had a template but no actual peers. I misinterpreted "& peer config: https://dpaste.com/HJ3SNL8RH" as being the config for the BIRD at the other end of the peering, and so didn't check that, as you say. Anyway, your response is rather unkind, to someone who was trying to help you. On Thu, Sep 3, 2020 at 3:43 PM Skyler Mäntysaari <sm@samip.fi> wrote:
If you had taken the time to read the posted links, you would see that it has peers, using Link-Local addresses.
On Thu, Sep 3, 2020, at 11:17, Neil Jerram wrote:
Does your configuration have any BGP peers? I've noticed that BIRD doesn't start listening until there is at least one BGP peer.
On Thu, Sep 3, 2020 at 12:12 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
I'm sorry if that message can be taken like that, as that was not my intention. On Thu, Sep 3, 2020, at 18:20, Neil Jerram wrote:
I did look at https://dpaste.com/6P6NAUPNX, and saw that it had a template but no actual peers. I misinterpreted "& peer config: https://dpaste.com/HJ3SNL8RH" as being the config for the BIRD at the other end of the peering, and so didn't check that, as you say.
Anyway, your response is rather unkind, to someone who was trying to help you.
On Thu, Sep 3, 2020 at 3:43 PM Skyler Mäntysaari <sm@samip.fi> wrote:
__ If you had taken the time to read the posted links, you would see that it has peers, using Link-Local addresses.
On Thu, Sep 3, 2020, at 11:17, Neil Jerram wrote:
Does your configuration have any BGP peers? I've noticed that BIRD doesn't start listening until there is at least one BGP peer.
On Thu, Sep 3, 2020 at 12:12 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
What user runs BIRD? 179 is lesser than 1024 so only root can bind to it. BIRD doesn't even attempt if it is not root. On linux, BIRD can drop all privileges except for privileged port binding almost immediately after startup; see bird -h for more info. Maria On 9/3/20 12:57 AM, 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 & peer config: https://dpaste.com/HJ3SNL8RH
Hi, On 9/3/20 10:43 AM, Maria Matejka wrote:
What user runs BIRD? 179 is lesser than 1024 so only root can bind to it. BIRD doesn't even attempt if it is not root. On linux, BIRD can drop all privileges except for privileged port binding almost immediately after startup; see bird -h for more info.
At least on debian, perhaps it was patched, bird will still try to open the port, even if not running as root. This way I can start bird under the bird user and bird group and give it the capability CAP_NET_BIND_SERVICE to allow it to bind to port 179. -- bauen1 https://dn42.bauen1.xyz/
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. Good luck and have fun with dn42! Bernd
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.
Good luck and have fun with dn42!
Bernd
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.
I did that, but it did not change anything. Still not binding.
On 3. Sep 2020, at 18.34, Bernd Naumann <bena@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.
On Thu, Sep 03, 2020 at 01:57:57AM +0300, 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.
Hi Based on the log it seems that the BGP protocol does not start because it does not detect availability of neighbor IP address. What is the output of 'show interfaces' and 'show protocols' command? What is your BIRD version? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hi, My bird version is 2.0.7, running on aarch64 with 5.7.16 kernel using raspberrypi kernel tree for BCM2711. The exact same behavior happens if the source is built from the bird ebuild in the Gentoo portage tree, or directly from source. show interfaces: https://dpaste.com/GRHNJS2D3 show protocols: https://dpaste.com/BP7HE5NHK Related Gentoo bug, that I submitted: https://bugs.gentoo.org/7402 <https://bugs.gentoo.org/740252> On Fri, Sep 4, 2020, at 18:48, Ondrej Zajicek wrote:
On Thu, Sep 03, 2020 at 01:57:57AM +0300, 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.
Hi
Based on the log it seems that the BGP protocol does not start because it does not detect availability of neighbor IP address.
What is the output of 'show interfaces' and 'show protocols' command?
What is your BIRD version?
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On Sat, Sep 05, 2020 at 02:29:34PM +0300, Skyler Mäntysaari wrote:
Hi,
My bird version is 2.0.7, running on aarch64 with 5.7.16 kernel using raspberrypi kernel tree for BCM2711. The exact same behavior happens if the source is built from the bird ebuild in the Gentoo portage tree, or directly from source.
show interfaces: https://dpaste.com/GRHNJS2D3
Hi Seems to me like misconfiguration: wg1 up (index=7) PtP Multicast AdminUp LinkUp MTU=1340 fe80:10::2/127 (Preferred, opposite fe80:10::3, scope link) as213021_hel_node: Waiting for fe80:10::1%wg1 to become my neighbor You have fe80:10::2/127 prefix on wg1, which contains fe80:10::2 and fe80:10::3, but waiting for fe80:10::1, which is outside of the range (it would be in fe80:10::0/127 network). -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
What is this about???? I haven't sent anything to this list in a while. ================================================== Your membership in the mailing list Bird-users has been disabled due to excessive bounces The last bounce received from you was dated 22-Nov-2020. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. ================================================== Sent from my Verizon Wireless 4G LTE Droid Turbo 2. On Fri, Sep 4, 2020 at 10:52 AM Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Thu, Sep 03, 2020 at 01:57:57AM +0300, 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.
Hi
Based on the log it seems that the BGP protocol does not start because it does not detect availability of neighbor IP address.
What is the output of 'show interfaces' and 'show protocols' command?
What is your BIRD version?
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hello! This means that you were refusing messages from the list for some amount of time. You may want to check your mailserver. Maria On November 22, 2020 7:38:10 PM GMT+01:00, Jason Kopacko <jason@kopacko.com> wrote:
What is this about????
I haven't sent anything to this list in a while.
================================================== Your membership in the mailing list Bird-users has been disabled due to excessive bounces The last bounce received from you was dated 22-Nov-2020. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. ==================================================
Sent from my Verizon Wireless 4G LTE Droid Turbo 2.
On Fri, Sep 4, 2020 at 10:52 AM Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Thu, Sep 03, 2020 at 01:57:57AM +0300, 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.
Hi
Based on the log it seems that the BGP protocol does not start because it does not detect availability of neighbor IP address.
What is the output of 'show interfaces' and 'show protocols' command?
What is your BIRD version?
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
I mean the mail server is Gmail. Sent from my Verizon Wireless 4G LTE Droid Turbo 2. On Sun, Nov 22, 2020 at 1:51 PM Maria Matějka <maria.matejka@nic.cz> wrote:
Hello!
This means that you were refusing messages from the list for some amount of time. You may want to check your mailserver.
Maria
On November 22, 2020 7:38:10 PM GMT+01:00, Jason Kopacko < jason@kopacko.com> wrote:
What is this about????
I haven't sent anything to this list in a while.
================================================== Your membership in the mailing list Bird-users has been disabled due to excessive bounces The last bounce received from you was dated 22-Nov-2020. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. ==================================================
Sent from my Verizon Wireless 4G LTE Droid Turbo 2.
On Fri, Sep 4, 2020 at 10:52 AM Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Thu, Sep 03, 2020 at 01:57:57AM +0300, 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.
Hi
Based on the log it seems that the BGP protocol does not start because it does not detect availability of neighbor IP address.
What is the output of 'show interfaces' and 'show protocols' command?
What is your BIRD version?
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
I have also received the same message with gmail yesterday. And also was surprised. On Sun, Nov 22, 2020 at 9:51 PM Jason Kopacko <jason@kopacko.com> wrote:
I mean the mail server is Gmail.
Sent from my Verizon Wireless 4G LTE Droid Turbo 2.
On Sun, Nov 22, 2020 at 1:51 PM Maria Matějka <maria.matejka@nic.cz> wrote:
Hello!
This means that you were refusing messages from the list for some amount of time. You may want to check your mailserver.
Maria
On November 22, 2020 7:38:10 PM GMT+01:00, Jason Kopacko <jason@kopacko.com> wrote:
What is this about????
I haven't sent anything to this list in a while.
================================================== Your membership in the mailing list Bird-users has been disabled due to excessive bounces The last bounce received from you was dated 22-Nov-2020. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. ==================================================
Sent from my Verizon Wireless 4G LTE Droid Turbo 2.
On Fri, Sep 4, 2020 at 10:52 AM Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Thu, Sep 03, 2020 at 01:57:57AM +0300, 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.
Hi
Based on the log it seems that the BGP protocol does not start because it does not detect availability of neighbor IP address.
What is the output of 'show interfaces' and 'show protocols' command?
What is your BIRD version?
-- Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
participants (10)
-
Alexander Zubkov -
bauen1 -
Bernd Naumann -
Jason Kopacko -
Maria Matejka -
Maria Matějka
-
Neil Jerram -
Ondrej Zajicek -
Skyler Mäntysaari -
Валерий Н. Лутошкин