Hello. Could you tell me status RIP in bird. Is it still broken in Bird? Or it should works fine? I have a problem with rip_metric. -- Best regards, Anton Kiryushkin
Hello, Anton. The implementation of RIP from the master branch from Git should work fine. What version of Bird did you test and what problem did you have with rip metric? All Best, Pavel On 2016-01-03 00:18, Anton Kiryushkin wrote:
Hello.
Could you tell me status RIP in bird. Is it still broken in Bird? Or it should works fine?
I have a problem with rip_metric.
--
Best regards,Anton Kiryushkin
Hello, Pavel. I can't announce rip_metric from virtual interfaces via physical. Is it possible? As I understood, it's impossible.
Hello, Anton. On 2016-01-04 20:04, Anton Kiryushkin wrote:
Hello, Pavel.
I can't announce rip_metric from virtual interfaces via physical. Is it possible? As I understood, it's impossible.
Virtual interfaces aren't problem. Did you set the export filter to all? If I have virtual interfaces named ve1, ve2, ..., then the configuration below should work well: protocol rip { debug all; import all; # default is all export all; # default is none interface "ve*" { mode multicast; }; } Cheers, Pavel
What about metric for each virtual interface? I mean ve1 has metric 5, and ve2 has metric 2 ? How to export this setting? As I wrote before, from another side I saw metric from physical interface. My config is: protocol rip { debug all; import all; # default is all export all; # default is none interface "ve1" { mode multicast; metric 5; }; interface "ve2" { mode multicast; metric 2; }; interface "eth0" { mode multicast; metric 3; }; } 2016-01-05 11:12 GMT+03:00 Pavel Tvrdík <pavel.tvrdik@nic.cz>:
Hello, Anton.
On 2016-01-04 20:04, Anton Kiryushkin wrote:
Hello, Pavel.
I can't announce rip_metric from virtual interfaces via physical. Is it possible? As I understood, it's impossible.
Virtual interfaces aren't problem. Did you set the export filter to all?
If I have virtual interfaces named ve1, ve2, ..., then the configuration below should work well:
protocol rip { debug all; import all; # default is all export all; # default is none interface "ve*" { mode multicast; }; }
Cheers, Pavel
-- Best regards, Anton Kiryushkin
Hello. On 2016-01-05 11:56, Anton Kiryushkin wrote:
What about metric for each virtual interface? I mean ve1 has metric 5, and ve2 has metric 2 ? How to export this setting? As I wrote before, from another side I saw metric from physical interface. My config is:
protocol rip { debug all; import all; # default is all export all; # default is none interface "ve1" { mode multicast; metric 5; };
interface "ve2" { mode multicast; metric 2; };
interface "eth0" { mode multicast; metric 3; };}
Well, I think the virtual interfaces "ve1" and "ve2" have to use each other interfaces than the physical interface "eth0" to work like you want. Pavel
2016-01-05 11:12 GMT+03:00 Pavel Tvrdík <pavel.tvrdik@nic.cz>:
Hello, Anton.
On 2016-01-04 20:04, Anton Kiryushkin wrote:
Hello, Pavel.
I can't announce rip_metric from virtual interfaces via physical. Is it possible? As I understood, it's impossible.
Virtual interfaces aren't problem. Did you set the export filter to all?
If I have virtual interfaces named ve1, ve2, ..., then the configuration below should work well:
protocol rip { debug all; import all; # default is all export all; # default is none interface "ve*" { mode multicast; }; }
Cheers, Pavel
--
Best regards,Anton Kiryushkin
On Tue, Jan 05, 2016 at 01:56:01PM +0300, Anton Kiryushkin wrote:
What about metric for each virtual interface? I mean ve1 has metric 5, and ve2 has metric 2 ? How to export this setting? As I wrote before, from another side I saw metric from physical interface. My config is:
Hi Metrics in RIP are generally understood as in-metric (increased by receiver). Therefore, 'metric' option for an interface specifies an increase of metrics for routes received through that interface. It does not influence routes originated by the router itself, like locally reachable prefixes. You have to modify rip_metric in the export filter. -- 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."
Could you tell me how I can modify rip_metric in the export filter? Maybe some documentation exists? On your site and maillist community I found only metric for rip section. Not about export filter. Maybe you need write documentation about export filter possibility with practice examples? 2016-01-05 19:53 GMT+03:00 Ondrej Zajicek <santiago@crfreenet.org>:
On Tue, Jan 05, 2016 at 01:56:01PM +0300, Anton Kiryushkin wrote:
What about metric for each virtual interface? I mean ve1 has metric 5, and ve2 has metric 2 ? How to export this setting? As I wrote before, from another side I saw metric from physical interface. My config is:
Hi
Metrics in RIP are generally understood as in-metric (increased by receiver). Therefore, 'metric' option for an interface specifies an increase of metrics for routes received through that interface. It does not influence routes originated by the router itself, like locally reachable prefixes. You have to modify rip_metric in the export filter.
-- 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."
-- Best regards, Anton Kiryushkin
participants (3)
-
Anton Kiryushkin -
Ondrej Zajicek -
Pavel Tvrdík