I know :D
Already used this setup before some times.

But since around a week, I'm not able to use it.
As soon as I use this as a filter/import rule, everything will be filtered/nothing imported.

Is there any know bug with a current bird version?



--
Kind regards,
Tom Funken

Cyanlink Ltd.
132-134 Great Ancoats Street
Suite 33854, Advantage Business Centre
Manchester M4 6DE
Phone: +44 2036088360 | Email: t.funken@cyanlink.net
https://www.cyanlink.net

Cyanlink Ltd. is registered in England and Wales.
Registered number: 10896716

The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

On Mar 7 2018, at 3:27 pm, Ondrej Zajicek <santiago@crfreenet.org> wrote:

On Sun, Feb 25, 2018 at 08:40:54PM +0000, Tom Funken wrote:

Hey,

is there a way to define the gateway when export to the kernel table?
I've seen some others using "filter { gw = 10.0.0.0; accept; }" on the import. But, when I do it, it will filter all import routes and non of them will be accepted.

Hi

Not sure what is the problem. 'filter { gw = 10.0.0.0; accept; }' in
the export filter of the kernel protocol should set the gateway.

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