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 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 wrote:
>>
>> H
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 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 Nov
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
wrote:
>What is this about
>
>I haven't sent anything to this list in a while.
>
>
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
Ah, seems that I were mistaken.
I needed to use /128 prefix for the addresses and it works now as expected.
On 05/09/2020 16.18, Ondrej Zajicek wrote:
> 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
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
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 prot
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 trie
I did that, but it did not change anything.
Still not binding.
> On 3. Sep 2020, at 18.34, Bernd Naumann 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 f
gt; to listen.
>
> From: Skyler Mäntysaari <mailto:s...@samip.fi>
> Reply: Skyler Mäntysaari <mailto:s...@samip.fi>
> Date: 3 September 2020 at 21:51:41
> To: Valery Lutoshkin <mailto:vpl...@gmail.com>
> Subject: Re: Unable to get Bird 2 to listen on the
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 neede
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"
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 u
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, S
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 pe
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
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
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
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äntys
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 wrote:
> Hi there,
>
> I’m fairly certain that my issue is something rather small, or stupid but
> I’m unable to get
Hi!
Try to activate “multihop" option in bgp config, sometmes it helps.
WBR,
Valery
From: Skyler Mäntysaari
Reply: Skyler Mäntysaari
Date: 3 September 2020 at 06:08:07
To: bird-users@network.cz
Subject: Unable to get Bird 2 to listen on the BGP socket
Hi there,
I’m fairly certain
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 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 o
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
23 matches
Mail list logo
