down. get him down off the list for repetitive violation of mail lists
ethic.
On Mon, 4 Feb 2019 at 15:24, Mattia Milani
wrote:
> Up
>
> Il giorno dom 3 feb 2019, 11:11 Mattia Milani <
> mattia.mil...@studenti.unitn.it> ha scritto:
>
>> up
>>
>> Il giorno mer 30 gen 2019 alle ore 23:34 Mattia Mi
On Sun, 27 Jan 2019 at 02:14, Ondrej Zajicek wrote:
> On Sat, Jan 26, 2019 at 02:07:52PM +0700, Igor Podlesny wrote:
> > I have test lab -- two OSPF routers, Bird 1.6.4: A, B.
> >
> > 2 areas defined: 0.0.0.0, 0.0.0.1. Export "all".
> >
> > When rfc158
I can suggest changing it so: bird 2 would try to open new config
file, say, bird2.conf and only if there's no such a file, would fall
back to bird.conf.
--
End of message. Next message?
The docs say: "... secondary switch
On BSD systems, older versions of BIRD supported OSPFv2 only for the
primary IP address of an interface, other IP ranges on the interface
were handled as stub networks. Since v1.4.1, regular operation on
secondary IP addresses is supported, but disabled by defau
I have test lab -- two OSPF routers, Bird 1.6.4: A, B.
2 areas defined: 0.0.0.0, 0.0.0.1. Export "all".
When rfc1583compat is Off I observe default route gets propagated via
area 0.0.0.1 in despite its interfaces have higher costs than area
0.0.0.0's have.
Turning rfc1583compat On changes it to
First of all, protocols description are better kept in separate HTML
pages otherwise it's hard to find by some keywords that several
protocols have. It's really inconvenient to loose focus when you
search something related to OSPF and Find scrolls page to completely
different protocol.
Second: why
Whereas it's given in some default Bird configs, I couldn't find it in manual.
--
End of message. Next message?
(compared to native OSPF daemon.)
Test lab: just two routers with OSPF on both: A and B.
OpenBSD 6.4. Bird 1.6.4p1.
Router A has two default routes installed:
Routing tables
Internet:
DestinationGatewayFlags Refs Use Mtu Prio Iface
default192.168.69.36
I have an instance of Bird 1.6.4 on a freshly installed OpenBSD 6.4.
My study of its OSPF database shown (with birdc show ospf lsadb self)
that there were LSAs for broadcast routes that are indicated as ones
having "UHb" in netstat -rn output. I suspect they're added by
"protocol direct", but didn
On Thu, 17 Jan 2019 at 02:31, Igor Podlesny wrote:
>
> On Thu, 17 Jan 2019 at 02:25, Ondrej Zajicek wrote:
> > On Thu, Jan 17, 2019 at 12:38:11AM +0700, Igor Podlesny wrote:
> > > Or would the second "config timeout" commit version 2 instead and when
> > >
On Thu, 17 Jan 2019 at 02:25, Ondrej Zajicek wrote:
> On Thu, Jan 17, 2019 at 12:38:11AM +0700, Igor Podlesny wrote:
> > Or would the second "config timeout" commit version 2 instead and when
> > timeout is reached would rollback from version 3 (which is equal by
>
On Thu, 17 Jan 2019 at 01:35, Maria Jan Matějka wrote:
> On January 16, 2019 5:34:36 PM GMT+01:00, Igor Podlesny
> wrote:
>>
>> -- Is it possible to get link status (up/down? anything else?) of an
>> interface (specified by interface name or other reference way if
>
IOW, let's say we have config version 1.
Then if config has been changed (become version 2) and temporarily applied with
config timeout 10
and then before it's been rolled back (assuming control still isn't
lost of course), entered
config timeout 30
would it be effectively the same as i
-- Is it possible to get link status (up/down? anything else?) of an
interface (specified by interface name or other reference way if
there're any) for further use in routes' preferences/metrics
calculations?
Hi :)
--
End of message. Next message?
14 matches
Mail list logo