Hi!
New version is ready, completely prepared by Santiago, good job. :-)
Version 1.2.2 (2010-04-10)
o Much better BSD kernel support (IPv6, alien routes, ...).
o Deep OSPF socket changes, fixes OSPFv2/v3 behavior on BSD.
o OSPFv2 in Linux now supports more non-stub IP prefixes
on one ph
Hello,
This is my first time so sorry if I have not done this right.
I have seen this problem before.
I have seen this in Linux when the BIOS synchronises its time with the OS.
The Linux OS could have been fine and have had a valid NTP source, but
periodically there is some form of synchronisat
On Apr 9, 2010, at 14:08 , Ondrej Zajicek wrote:
> On Fri, Apr 09, 2010 at 10:49:15AM +0200, Wolfgang Hennerbichler wrote:
>> Hm. Now this is strange indeed. I run linux 2.6.33.1 (amd64) - but it
>> is a virtualized host (with xen). Maybe it was xen's fault, but the logs
>> don't reveal much as y
On Fri, Apr 09, 2010 at 10:49:15AM +0200, Wolfgang Hennerbichler wrote:
> Hm. Now this is strange indeed. I run linux 2.6.33.1 (amd64) - but it
> is a virtualized host (with xen). Maybe it was xen's fault, but the logs
> don't reveal much as you see. Hm. this sucks.
If there is a virtualization i
On Apr 9, 2010, at 12:44 , Arnold Nipper wrote:
>
> Is this really a BIRD bug? I guess it is expected behaviour to drop a
> session if you _think_ you missed keepalives
Time Counters within a Daemon should NEVER be dependent on the system time, so
yes, I would consider this a bug of BIRD, but i
On 09.04.2010 10:22 Wolfgang Hennerbichler wrote
> Hi Ondrejs,
>
> I think I found another bug. For some mysterious reason our system time
> jumped forward (more than 30.000 seconds) on one of our route-servers. I
> don't know why this happened, but I suspect a broken ntp server could have
>
On Apr 9, 2010, at 10:49 , Ondrej Zajicek wrote:
> On Fri, Apr 09, 2010 at 10:22:05AM +0200, Wolfgang Hennerbichler wrote:
>> Hi Ondrejs,
>>
>> I think I found another bug. For some mysterious reason our system time
>> jumped forward (more than 30.000 seconds) on one of our route-servers. I
>
On Fri, Apr 09, 2010 at 10:22:05AM +0200, Wolfgang Hennerbichler wrote:
> Hi Ondrejs,
>
> I think I found another bug. For some mysterious reason our system time
> jumped forward (more than 30.000 seconds) on one of our route-servers. I
> don't know why this happened, but I suspect a broken ntp
On Apr 9, 2010, at 10:43 , Ondrej Zajicek wrote:
> On Fri, Apr 09, 2010 at 10:09:22AM +0200, Wolfgang Hennerbichler wrote:
>> Great news. Actually I think every cisco router threw up, JunOS didn't seem
>> to care (I think).
>> BTW: What happens if I do a bgp_community.delete ((1234,1234)) if th
On Fri, Apr 09, 2010 at 10:09:22AM +0200, Wolfgang Hennerbichler wrote:
> Great news. Actually I think every cisco router threw up, JunOS didn't seem
> to care (I think).
> BTW: What happens if I do a bgp_community.delete ((1234,1234)) if the
> community doesn't exist?
It does nothing (with th
Hi Ondrejs,
I think I found another bug. For some mysterious reason our system time jumped
forward (more than 30.000 seconds) on one of our route-servers. I don't know
why this happened, but I suspect a broken ntp server could have caused this.
Nevetheless, this was reason enough for BIRD to d
On Apr 9, 2010, at 10:08 , Ondrej Zajicek wrote:
> Hello.
Hi,
> Thank you for the bug report.
No problem.
> The RFC 1997 does not explicitly forbid
> empty community attribute and we assumed that it is valid. But if
> some Cisco routers don't like it reasonable to not generate such
> attrib
On Thu, Apr 08, 2010 at 02:44:11PM +0200, Wolfgang Hennerbichler wrote:
> Allright, reply to myself:
>
> This seems to be a bug in BIRD.
> What I actually added was a rule that certain communities should be deleted:
> if ((1120,1)) ~ bgp_community then bgp_community.delete((1120,1));
>
> this
13 matches
Mail list logo
