On Thu, Jan 14, 2021 at 04:28:42PM +0100, Claudio Jeker wrote:
> This diff adds 'reject as-set yes' as an option to filter out AS paths
> with AS_SET segement elements. In bgpctl they show up with {} elements,
> e.g. 174 6762 24835 { 36893 }.
>
> This diff uses the soft-error path from RFC7606 and
On Thu, Jan 14, 2021 at 08:22:45PM +0100, Denis Fondras wrote:
> Le Tue, Jan 12, 2021 at 10:06:46AM +0100, Claudio Jeker a écrit :
> > On Tue, Jan 05, 2021 at 11:17:22AM +0100, Claudio Jeker wrote:
> > > While changing log_addr() I noticed that struct bgpd_addr could benefit
> > > from changing the
Hi,
I spotted a typo in www/68.html and this patch will fix it.
Index: 68.html
===
RCS file: /cvs/www/68.html,v
retrieving revision 1.85
diff -u -r1.85 68.html
--- 68.html 3 Jan 2021 14:19:20 - 1.85
+++ 68.html 14 J
Hi,
The following patches will update the hardware note file and loongson.html
with the corrent screen resolution and model details for Loongson
Lynloong.
Index: distrib/notes/loongson/hardware
===
RCS file: /cvs/src/distrib/notes/
Hi,
The following patch will update the link for PMON on loongson.html. The
existing site for PMON seems to be abandoned now and development of pmon
on loongson continues in Loongnix's git repository.
Index: loongson.html
===
RCS f
So I recently read most of the source for config (only stuff needed
for kernel compilation), and I'm certainly no expert, but I have a few
suggestions.
The first is that pathnames in gram.y should probably use right
recursion, correct? Unless you want to be limited to pathname lists
of length two.
bpf should be showing what will be or has been on the wire, which is
what the ether_vtag in the mbuf has. the prio is either about to be
decoded from the tag on the wya into the stack, or has been encoded by
vlan(4) on the way out of the stack.
ok?
Index: bpf.c
===
On Wed, Jan 13, 2021 at 9:38 PM Scott Cheloha
wrote:
snip
> Do we need to properly set stathz for each platform in *this* diff?
> Or can it wait?
>
> I was hoping to do a sweep of the tree in a later patch and ensure
> that stathz is non-zero everywhere and simultaneously remove code like
> this:
Le Thu, Jan 14, 2021 at 02:20:26PM +0100, Claudio Jeker a écrit :
> The aspath_neighbor function returns the first AS of a path. Now if the
> first element is an AS_SET then this does not really make sense.
> RFC4271 has this bit in section 9.1.2.2
>
> Similarly, neighborAS(n) is a functi
Le Tue, Jan 12, 2021 at 10:06:46AM +0100, Claudio Jeker a écrit :
> On Tue, Jan 05, 2021 at 11:17:22AM +0100, Claudio Jeker wrote:
> > While changing log_addr() I noticed that struct bgpd_addr could benefit
> > from changing the encoding of AID_VPN_IPv4 and AID_VPN_IPv6 addrs.
> > Instead of having
On Thu, Jan 07, 2021 at 11:15:42AM -0600, Scott Cheloha wrote:
> Hi,
>
> I want to isolate statclock() from hardclock(9). This will simplify
> the logic in my WIP dynamic clock interrupt framework.
>
> Currently, if stathz is zero, we call statclock() from within
> hardclock(9). It looks like t
This diff adds 'reject as-set yes' as an option to filter out AS paths
with AS_SET segement elements. In bgpctl they show up with {} elements,
e.g. 174 6762 24835 { 36893 }.
This diff uses the soft-error path from RFC7606 and because of this
prefixes that have such an AS_SET segment will be remove
On 14/01/21 14:50 +0100, Theo Buehler wrote:
> On Thu, Jan 14, 2021 at 02:37:20PM +0100, Robert Nagy wrote:
> > On 14/01/21 14:27 +0100, Robert Nagy wrote:
> > > On 14/01/21 14:20 +0100, Theo Buehler wrote:
> > > > On Thu, Jan 14, 2021 at 01:32:41PM +0100, Matthieu Herrb wrote:
> > > > > Hi,
> > >
On Thu, Jan 14, 2021 at 02:37:20PM +0100, Robert Nagy wrote:
> On 14/01/21 14:27 +0100, Robert Nagy wrote:
> > On 14/01/21 14:20 +0100, Theo Buehler wrote:
> > > On Thu, Jan 14, 2021 at 01:32:41PM +0100, Matthieu Herrb wrote:
> > > > Hi,
> > > >
> > > > I'm trying to debug strange beahaviour chang
On 14/01/21 14:27 +0100, Robert Nagy wrote:
> On 14/01/21 14:20 +0100, Theo Buehler wrote:
> > On Thu, Jan 14, 2021 at 01:32:41PM +0100, Matthieu Herrb wrote:
> > > Hi,
> > >
> > > I'm trying to debug strange beahaviour changes with certificates on a
> > > systemc after upgrading it from 6.7 to 6.
On 14/01/21 14:20 +0100, Theo Buehler wrote:
> On Thu, Jan 14, 2021 at 01:32:41PM +0100, Matthieu Herrb wrote:
> > Hi,
> >
> > I'm trying to debug strange beahaviour changes with certificates on a
> > systemc after upgrading it from 6.7 to 6.8...
> >
> > On 6.7, If I run :
> >
> > openssl s_serv
On Thu, Jan 14, 2021 at 02:20:38PM +0100, Theo Buehler wrote:
> On Thu, Jan 14, 2021 at 01:32:41PM +0100, Matthieu Herrb wrote:
> > Hi,
> >
> > I'm trying to debug strange beahaviour changes with certificates on a
> > systemc after upgrading it from 6.7 to 6.8...
> >
> > On 6.7, If I run :
> >
>
On Thu, Jan 14, 2021 at 01:32:41PM +0100, Matthieu Herrb wrote:
> Hi,
>
> I'm trying to debug strange beahaviour changes with certificates on a
> systemc after upgrading it from 6.7 to 6.8...
>
> On 6.7, If I run :
>
> openssl s_server -cert mycert.pem -key mykey.pem -CAfile CA.pem
>
> then ope
The aspath_neighbor function returns the first AS of a path. Now if the
first element is an AS_SET then this does not really make sense.
RFC4271 has this bit in section 9.1.2.2
Similarly, neighborAS(n) is a function that returns the
neighbor AS from which the route was received.
Hi,
I'm trying to debug strange beahaviour changes with certificates on a
systemc after upgrading it from 6.7 to 6.8...
On 6.7, If I run :
openssl s_server -cert mycert.pem -key mykey.pem -CAfile CA.pem
then openssl s_client -showcerts -connect localhost:4433
returns the full certificate chain
Currently bgpd does not properly handle strict med route decisions.
The problem is that the strict MED check only matters for aspaths with the
same neighbor as. The route decision process currently stops as soon as
the current prefix is better then the one checked in the list of prefixes.
Now in so
> My understanding is that HZ=100 was a practical choice because the
> machines of the day could not reliably drive a faster clock interrupt.
The VAX architecture defines a 100Hz timer, which is the only timer you
can be sure will be available to the kernel. A few of the later models
(VAXstation 4
> Date: Wed, 13 Jan 2021 21:39:37 -0600
> From: Scott Cheloha
>
> On Fri, Jan 08, 2021 at 08:21:14PM +0100, Florian Obser wrote:
> >
> > My x1 gen 2 seems to have a TPM 1.2 chip. Or can emulate one?
> > The bios is confusing. I had it disabled until now.
> > It seems to be able to suspend/resume
23 matches
Mail list logo
