On Fri, Apr 21, 2023 at 11:21:11AM +0200, Claudio Jeker wrote:
> Flowspec added some new ext communities. They use new type (generic
> transitive types). Adjust the ext community code to handle these types as
> well. I need to cycle back to this but this gets us of the ground.
Both thi
Flowspec added some new ext communities. They use new type (generic
transitive types). Adjust the ext community code to handle these types as
well. I need to cycle back to this but this gets us of the ground.
--
:wq Claudio
Index: parse.y
On Mon, Jan 30, 2023 at 05:37:25PM +0100, Theo Buehler wrote:
> On Mon, Jan 30, 2023 at 03:29:49PM +0100, Claudio Jeker wrote:
> > Extended communities are annoying, especially the ASnum encodings are a
> > problem since the same extended community can be encoded in more than on
On Mon, Jan 30, 2023 at 03:29:49PM +0100, Claudio Jeker wrote:
> Extended communities are annoying, especially the ASnum encodings are a
> problem since the same extended community can be encoded in more than one
> way. This results in strange behaviour when used with local-as and/or
>
Extended communities are annoying, especially the ASnum encodings are a
problem since the same extended community can be encoded in more than one
way. This results in strange behaviour when used with local-as and/or
neighbor-as.
This diff changes the match function for any community with masks
On 2021/10/25 10:09, Martijn van Duren wrote:
> Thanks for the detailed analysis.
>
> diff below should fix it.
thanks, OK. I'm sure I tried that but maybe I missed the _ (SNMPV2 vs
SNMP_V2).
m with snmpd on mips64 but didn't see
> > them on amd64 and wondered if it was arch-specific, I had a go at
> > reproducing and see it very often on aarch64 and also sometimes on
> > amd64.
> >
> > Any setting of "trap receiver $ip snmpv2c community $community"
on aarch64 and also sometimes on
> amd64.
>
> Any setting of "trap receiver $ip snmpv2c community $community"
> triggers the problem:
>
> # for i in `jot 20`; do snmpd -nvf /etc/snmpd.conf; done
> trap receiver: missing community
> configuration ok
> con
trondd noticed a startup problem with snmpd on mips64 but didn't see
them on amd64 and wondered if it was arch-specific, I had a go at
reproducing and see it very often on aarch64 and also sometimes on
amd64.
Any setting of "trap receiver $ip snmpv2c community $community"
trigg
We moved away from the idea of default community in all of our snmp
tools. Let's give tcpdump the same treatment so that people don't
get the wrong idea.
OK?
martijn@
Index: print-snmp.c
===
RCS file: /cvs/src/usr.sb
Claudio Jeker(cje...@diehard.n-r-g.com) on 2021.05.12 19:49:08 +0200:
> RFC5492 is fairly explicit when a capability should be enabled on a
> session:
>
>A BGP speaker that supports a particular capability may use this
>capability with its peer after the speaker determines (as described
>
RFC5492 is fairly explicit when a capability should be enabled on a
session:
A BGP speaker that supports a particular capability may use this
capability with its peer after the speaker determines (as described
above) that the peer supports this capability. Simply put, a given
capabili
Moving to tech@
On 5/1/20 5:17 PM, Steven Surdock wrote:
> I see that snmpd.conf supports "read-write disabled", but this doesn't seem
> to _completely_ disable the private community. If I set "read-write
> disabled" I can still poll values using the 'pri
ities is a bit strange not all options are
> > possible. Here a list of possibilities:
> >
> > ext-community * * # delete any ext-community
> > ext-community ovs * # delete any ext-community of specified type
> > ext-community rt 1.2.3.4:*
> > ext-community rt local-a
diff allows the same use of '*' on ext-communities and also adds
> support for local-as and neighbor-as on some forms of ext-communities.
>
> Since the encoding of ext-communities is a bit strange not all options are
> possible. Here a list of possibilities:
>
> ext-
r local-as and neighbor-as on some forms of ext-communities.
Since the encoding of ext-communities is a bit strange not all options are
possible. Here a list of possibilities:
ext-community * * # delete any ext-community
ext-community ovs * # delete any ext-community of specified type
ext-co
Claudio Jeker(cje...@diehard.n-r-g.com) on 2018.12.12 14:19:36 +0100:
> Time to fold ext-communities into filter_community so that bgpd can match
> multiple ext-communities at the same time as well. Additionally this fixes
> parsing some of the ext-community types. Rather large diff agai
Time to fold ext-communities into filter_community so that bgpd can match
multiple ext-communities at the same time as well. Additionally this fixes
parsing some of the ext-community types. Rather large diff again so more
testing and review very welcome. After this more refactoring will be
t; > now share the same data structure for lookups and at the same time the
> > filters are extended to allow more then one community to match per rule
> > (currently the maximum is 3). I did leave extended communities outside for
> > now since this diff is already big enough bu
filters are extended to allow more then one community to match per rule
> (currently the maximum is 3). I did leave extended communities outside for
> now since this diff is already big enough but they will follow in a second
> step.
>
> So now filters like
> deny to any larg
This is a large diff that changes the way communities are stored in
filters and filter_sets. Both standard communities and large communities
now share the same data structure for lookups and at the same time the
filters are extended to allow more then one community to match per rule
(currently the
ok
Job Snijders(j...@instituut.net) on 2017.06.23 16:02:13 +0200:
> Dear team,
>
> This patch adds support for the "graceful shutdown" well-known
> community as described in draft-ietf-grow-bgp-gshut.
>
> An example implementation would be to add the f
OK
On 2017 Jun 23 (Fri) at 16:02:13 +0200 (+0200), Job Snijders wrote:
:Dear team,
:
:This patch adds support for the "graceful shutdown" well-known
:community as described in draft-ietf-grow-bgp-gshut.
:
:An example implementation would be to add the following to your
:bgpd.conf:
:
Dear team,
This patch adds support for the "graceful shutdown" well-known
community as described in draft-ietf-grow-bgp-gshut.
An example implementation would be to add the following to your
bgpd.conf:
match from any community GRACEFUL_SHUTDOWN set { localpref 0 }
Kind reg
yyerror("Bad ext-community value to big");
+ yyerror("Bad ext-community value too big");
return (-1);
}
c->data.ext_opaq = ullval;
@@ -3504,7 +3504,7 @@ merge_prefixspec(struct filter_prefix_l
> retrieving revision 1.307
> diff -u -p -r1.307 bgpd.h
> --- bgpd/bgpd.h 28 May 2017 20:14:15 - 1.307
> +++ bgpd/bgpd.h 30 May 2017 22:23:03 -
> @@ -760,18 +760,23 @@ struct filter_peers {
> #define EXT_COMMUNITY_IANA 0x80
> #define EXT_COMMUN
/* 2 octet AS specific */
-#define EXT_COMMUNITY_IPV4 1 /* IPv4 specific */
-#define EXT_COMMUNITY_FOUR_AS 2 /* 4 octet AS specific */
-#define EXT_COMMUNITY_OPAQUE 3 /* opaque ext community */
-/* sub types */
-#define EXT_COMMUNITY_ROUTE_TGT
forgot to look at bgpctl in my first reply, sry
Peter Hessler(phess...@openbsd.org) on 2016.10.13 17:34:28 +0200:
> On 2016 Oct 11 (Tue) at 00:00:53 +0200 (+0200), Peter Hessler wrote:
> :Here is an initial implementation of draft-ietf-idr-large-community for
> :OpenBGPD. I can co
Peter Hessler(phess...@openbsd.org) on 2016.10.13 17:34:28 +0200:
> On 2016 Oct 11 (Tue) at 00:00:53 +0200 (+0200), Peter Hessler wrote:
> :Here is an initial implementation of draft-ietf-idr-large-community for
> :OpenBGPD. I can connect and exchange routes with these attributes
&
On 2016 Oct 11 (Tue) at 00:00:53 +0200 (+0200), Peter Hessler wrote:
:Here is an initial implementation of draft-ietf-idr-large-community for
:OpenBGPD. I can connect and exchange routes with these attributes
:against exabgp.
:
:Normal communities are two 16bit numbers. With the addition of
Here is an initial implementation of draft-ietf-idr-large-community for
OpenBGPD. I can connect and exchange routes with these attributes
against exabgp.
Normal communities are two 16bit numbers. With the addition of
32bit ASNs, those will not work if you wish to control one of
them.
Large
Am 15.02.14 01:46, schrieb Brynet:
>OpenBSD is what part of the 'Linux System' exactly? :-)
Heh, "the Linux system"...
I'd assume what he meant was "we support Linux only, but we might also
support you if you help us support Linux".
Amusing.
ects developing or using Open
> Source and Linux-related technology by deterring patent aggression. We do
> this through a community that pledges not to assert patents against each
> other over this technology. This pledge covers over 2,100 Open Source
> packages. It is structured to
inux-related technology by deterring patent aggression. We do
> this through a community that pledges not to assert patents against each
> other over this technology. This pledge covers over 2,100 Open Source
> packages. It is structured to reduce risk on core operating system and
>
Hi,
vistit our community and post free ad.
http://escortsagency.ch
http://hostingwebtre.blogspot.com/, performante, veloce e sicuro.
For delete your account from this newsletter. black74...@gmail.com
35 matches
Mail list logo
