On Nov 21, 2014, at 3:29 AM, Dinesh Dutt wrote:
> I also agree that we should do this in a way that avoids affecting
> existing users and that this should be the default for new
> configurations. I don't know of a good way to address both issues
> offhand. Let me think some more and respond if I c
On Nov 21, 2014, at 1:31 PM, Lennart Sorensen
wrote:
> On Fri, Nov 21, 2014 at 06:43:04AM -0500, Alexis Rosen wrote:
>> So, here's a really bad solution, but if it gets the patch merged, then it
>> would be "good enough"...
>> [...]
>
> Most people
I have no dog in this fight (discussion), but I am curious... wasn't it decided
(more than a year ago IIRC) that the Quagga project would move to a merge-early
default behavior? I thought the criterion for merging was changed to,
approximately, "don't break stuff".
If so, that seems inconsisten
On Nov 26, 2014, at 3:36 AM, Vipin Kumar wrote:
> Please find a write-up for this feature, location of the code, and attached
> are some real outputs from the running code. Hope this will be useful to the
> members of the community interested in this feature.
This is great!
Have you had a chan
On Dec 2, 2014, at 3:31 PM, Greg Troxel wrote:
> + * platforms, and 8 bytes on others. bytes. NetBSD 6 changed the
You might want to fix that.
/a
___
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagg
[Oops, sorry, sending again with the correct From: address]
David, I think you're missing an important point: Quagga has a much greater
interest in being available on many platforms, than individual
platforms/distros have in making quagga available. To the extent that a larger
user base is desi
On Dec 5, 2014, at 4:20 AM, David Lamparter wrote:
> Ah, that argument I can actually understand. Ohwell.
>
> We need to make sure they're maintained, then - if they aren't, I still
> think they hurt more than they help :/. Ultimately, I guess Greg is
> spot on in arguing that the common, gener
On Dec 15, 2014, at 5:22 AM, Feng Lu wrote:
> (1) u_short instance
>
> The instance ID is defined as an unsigned short value. It seems enough
> for now, while I don't know whether it would be proper in the future
> or for some special reason.
>
> Is it more better to use u_int32_t?
>
> Or at le
On Jan 29, 2015, at 7:54 PM, David Lamparter
wrote:
> +@deffn Command {ip multicast rpf-lookup-mode @var{mode}} {}
> +@deffnx Command {no ip multicast rpf-lookup-mode [@var{mode}]} {}
> +
> +@var{mode} sets the method used to perform RPF lookups. Supported modes:
> +
> +@table @samp
> +@item uri
On May 7, 2015, at 6:45 AM, Juliusz Chroboczek
wrote:
>> Just to re-iterate again, everyone, including Juliusz, seems to be agreed
>> that Quagga is fully honouring all the licence conditions.
>
> I have no plans to sue anyone, if that's what you mean. However unethical
> their behaviour.
>
>
I don't use VRFs with Quagga. While I think it would be healthy for the
platform to have support, I don't need it myself, so I have no vested interest
in any particular outcome here.
On Jun 1, 2015, at 11:38 AM, Paul Jakma wrote:
> On Mon, 1 Jun 2015, David Lamparter wrote:
>> At least, I don't
On Aug 12, 2015, at 8:45 PM, Martin Winter
wrote:
> This includes some (basic) documentation on how to build from source and how
> to
> build a package for each of these distributions. All the Doc is currently in
> Markdown format (because the gut servers do a nice on-the-fly rendering)
>
> Wha
On Sep 10, 2015, at 9:36 AM, Paul Jakma wrote:
> On Thu, 10 Sep 2015, Donald Sharp wrote:
>> Paul -
>>
>> I don't get this. 'no neighbor activate' does nothing more than
>> temporarily turn the neighbor off, why would it remove some config? If I
>> wanted to remove the neighbor, I would do a 'n
On Sep 11, 2015, at 8:25 AM, Michael H Lambert wrote:
>> On 11 Sep 2015, at 06:34, Paul Jakma wrote:
>>
>> Yeah, be nice to have 1 way to delete the per-AFI/SAFI config, and another
>> to disable the neighbour in that AFI/SAFI, but keep config.
>>
>> What would be the sanest way to add such co
On Sep 11, 2015, at 3:37 PM, Lou Berger wrote:
> On 09/11/2015 02:35 PM, Alexis Rosen wrote:
>> On Sep 11, 2015, at 8:25 AM, Michael H Lambert wrote:
>>> For deleting the per-AFI/SAFI config, how about just
>>>
>>> no neighbor address-family
>>&g
On Sep 15, 2015, at 5:44 AM, Paul Jakma wrote:
> Well, what about requiring that where a command is modified and that command
> has documentation already, that the documentation is updated?
>
> Out-of-date and hence misleading documentation is perhaps more annoying than
> none.
Agreed. Potenti
On Oct 19, 2015, at 6:37 AM, Balaji G wrote:
> Quagga is a routing protocols suite. It does not have support for VRRP.
Maybe it would be better to say it doesn't include VRRP, than that it doesn't
support it. If you install a VRRP package, it will work fine with Quagga- at
least as much as any
On Oct 20, 2015, at 11:14 AM, Paul Jakma wrote:
> This is an old bit of documentation work gathering dust in my attic. I'd
> written it to try help OSPF admins better understand and debug their
> networks in the event of problems. I didn't finish it off, so never
> submitted it. Not sure if it's
On Nov 9, 2015, at 8:21 PM, Donald Sharp wrote:
> From: Dinesh G Dutt
>
> Currently, modifications to route maps do not affect already processed
> routes; they only affect new route updates. This patch addresses this
> limitation.
This is highly desirable, from one point of view, both as a sign
On Nov 10, 2015, at 9:13 AM, Daniel Walton wrote:
> Cisco IOS behaves the same way as quagga with the proposed patch...route-maps
> are applied automatically after a few seconds. Example:
I didn't realize that that had changed...
> While I appreciate the convenience it provides, I can also see
This looks great. Long past time for it. But I'm curious - have you profiled
the change in CPU and memory? I'm less concerned about CPU (obviously going to
be a big win) than memory. I'm happy to pay it for the CPU gain, just curious
about how expensive it will be.
/a
__
On Nov 24, 2015, at 9:06 AM, Vincent JARDIN wrote:
> On 24/11/2015 14:38, Paul Jakma wrote:
>> So the things we need to consider:
>>
>> - Existing CLI
>> - SNMP
>> - YANG
>> - OVSDB
>> -
> - bson/json
> - XML/binary XML configuration
> - ODL - Opendaylight
>
> We should not mix:
> a- transport
On Nov 25, 2015, at 8:29 AM, Paul Jakma wrote:
> On Tue, 24 Nov 2015, Alexis Rosen wrote:
>> I would be shocked if there was a consensus to move away from the current
>> CLI.
>
> Me too. ;)
>
> The idea is to be able to support other interfaces, and allow the
Anything that breaks the common case that millions (?) of fingers have on
automatic - "sho ip route xxx" - is going to seriously irritate many many
people.
/a
___
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/list
On Mar 1, 2016, at 6:55 PM, Alexander Turner wrote:
> Looking into starting a feature that prevents commands from being executed
> until a 'commit' command is issued in vtysh. Looking through the source code
> it would seem as if each daemon doesn't exactly facilitate this easily though
> I'm c
On Mar 2, 2016, at 6:43 PM, Alexander Turner wrote:
> So Vyatta is interesting though looking through the source code, it seems as
> if they've modified bash (I think for autocomplete functionality?) and
> written their own shell. Their commit function is hiding in here from what it
> seems.
I
On Mar 2, 2016, at 8:38 PM, Donald Sharp wrote:
> On a side note, extract.pl.in as far as I can tell only is used to auto
> generate the perl binary location. Is there a modern distribution that
> doesn't have perl in /usr/bin? Would people mind if I removed the
> extract.pl.in -> extract.pl
On Apr 22, 2016, at 11:45 AM, Donald Sharp wrote:
> Paul and I have been discussing this commit:
>
> https://github.com/donaldsharp/quagga/commit/4a77fb6cc78cacfd0c6cd0c35ba766f994a87e11
>
> Quagga behavior without this patch does not take into effect for already
> processed events. So if you
On May 16, 2016, at 10:03 AM, Devender wrote:
> I have Quagga/Zebra installed on Ubuntu 14-04 , I am able to connect to
> Quagga CLI using Telnet but SSH to CLI is not working. Do Quagga CLI supports
> SSH ?
No, it doesn't support either SSH or telnet. It's just sending text across a
network
On Oct 3, 2016, at 11:21 AM, Vincent JARDIN wrote:
> Le 03/10/2016 à 15:08, Paul Jakma a écrit :
>>
>> My inclination is to release as is. Document regressions. Try fix them
>> later.
> +1
ISTM the large majority of quagga users will not see any such documentation.
They'll build/install using t
On Oct 18, 2016, at 1:56 AM, Martin Winter
wrote:
> Security Advisory: Quagga Buffer Overflow in IPv6 RA handling
> =
>
> [...] The issue can be triggered on an IPv6 address where the Quagga
> daemon is reachable by a RA (Router Adverti
While I was at first concerned about wording, which I address first, I am also
concerned about the substance of the CVE, which I'll address at the end.
On Nov 15, 2016, at 6:00 PM, Martin Winter
wrote:
> On 14 Nov 2016, at 21:20, Alexis Rosen wrote:
>> On Oct 18, 2016, at 1
On Nov 16, 2016, at 10:05 AM, Paul Jakma wrote:
> On Tue, 15 Nov 2016, Alexis Rosen wrote:
>
>> As far as I can tell, this is an editing error of some sort, and in fact you
>> can NOT trigger the issue simply by having an IPv6 address reachable with an
>> ICMP.
>
On Nov 16, 2016, at 10:14 AM, Paul Jakma wrote:
> On Wed, 16 Nov 2016, Alexis Rosen wrote:
>> On Nov 15, 2016, at 6:00 PM, Martin Winter
>> wrote:
>>> On 14 Nov 2016, at 21:20, Alexis Rosen wrote:
>>>> On Oct 18, 2016, at 1:56 AM, Martin Winter
>>
On Jan 10, 2017, at 5:41 PM, Paul Jakma wrote:
> On Tue, 10 Jan 2017, Alexis Rosen wrote:
>> On Jan 10, 2017, at 10:47 AM, Paul Jakma wrote:
>>> On Tue, 10 Jan 2017, Alexis Rosen wrote:
>>>> This makes sense to me, and the RFC doesn't.
>>>
>>
On Apr 5, 2018, at 4:21 PM, Илья Шипицин wrote:
> Hello,
>
> please review attached patch
This patch seems obviously correct.
/a
___
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
On Jun 25, 2018, at 9:55 AM, Victor Sartori wrote:
> I found this patch on list archive and don't find this patch on quagga
> commits.
>
> I found a another message in list archives ''[quagga-dev 11920] BGP Dynamic
> Neighbor support', but I don't find anything about it too on git commits.
>
>
37 matches
Mail list logo
