Stuart,
> Yes the original code was in the original import from KAME. The code
> that actually *processed* these queries was removed in the commit I
> mentioned (so it seems your main concern is already dealt with), but
> I think the interfaces are still joined to the group so will receive
>
On 2018/10/03 12:36, Aham Brahmasmi wrote:
> Hi Stuart,
>
> Thank you for your response.
>
> > > 2) How to disable an interface from joining IPv6 Node Information
> > > multicast group (RFC 4620)?
> > > In sys/netinet6/in6.c, the function in6_update_ifa contains the
> > > following lines:
> > >
On Tue, 2 Oct 2018, John M wrote:
This may be a bit off-topic but the feature responsible for this is
'electric-indent-mode', which is enabled by default in 24.4 or later.
It is not enough to prevent indentation in Tcl mode.
(setq tcl-mode-map (make-sparse-keymap))
is not anymore
... is it just 750 for a License ?
If one were to donate a License ? would that work for the project ?
Thanks
Tom Smyth
On Wed, 3 Oct 2018 at 17:33, Todd C. Miller wrote:
>
> On Wed, 03 Oct 2018 10:20:45 +0200, Ingo Schwarze wrote:
>
> > Which is of course trivial to do - you write a script to
On Wed, 03 Oct 2018 17:42:16 +0100, Tom Smyth wrote:
> ... is it just 750 for a License ?
> If one were to donate a License ? would that work for the project ?
No, it would not. Their licensing model simply won't work for us.
Even if it did, it's not like we could run it natively on OpenBSD.
Hi Todd,
I was thinking ... it might be possible to examine
a copy of the code out of band on a different OS system ...
and deal with the bugs that are flagged
as part of the normal OpenBSD development process,
if the license is not permissible then I suppose my suggestion
was entirely academic
On Wed, 03 Oct 2018 18:07:00 +0100, Tom Smyth wrote:
> I was thinking ... it might be possible to examine
> a copy of the code out of band on a different OS system ...
> and deal with the bugs that are flagged
> as part of the normal OpenBSD development process,
It is possible to generate
Thanks, I just saw the previous discussion, from late 2017.
Do you know where we can follow the work that is being done? I would be more
than
happy to test early version.
On Wed, 03 Oct 2018 10:20:45 +0200, Ingo Schwarze wrote:
> Which is of course trivial to do - you write a script to do a
> checkout, run "sed -i", run the tool, collect the the results,
> and delete the checkout. So the harassment by the author is not
> even effective for his intended purpose.
Hello,
your forwarding performance will vary based on a few things...
at the minute Routing is MP safe... but if one of the lan ports
lets say em1 was in a bridge... then the forwarding is done
by a single core...
My testing on OpenBSD 6.3 showed speeds of 750/s - 800Mb/s
with default rules
On 2018-10-03, Benjamin Petit wrote:
> Before upgrading to CURRENT, I think routing with or without pf
> enabled was around 600Mbit/s, but I would need to reinstall to test
> again.
Snapshots are usually built with the "pool_debug" kernel option,
releases are built without it. This is good for
Hello, and thanks for your responses!
> My testing on OpenBSD 6.3 showed speeds of 750/s - 800Mb/s
> with default rules using x86-64 GENERIC (not i386)
Same setup as yours, and I definitely don't reach 750-800Mbits/s (550 at best)
When I transfer a big file from one network to another, I
My sysctl output:
kern.ostype=OpenBSD
kern.osrelease=6.4
kern.osrevision=201811
kern.version=OpenBSD 6.4 (GENERIC.MP) #342: Tue Oct 2 23:23:09 MDT
2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.M
P
kern.maxvnodes=22282
kern.maxproc=1310
kern.maxfiles=7030
Ok so I compared 6.3-release, 6.3-release+syspatches(=stable?) and the latest
snapshot from October 2.
I measured iperf3 throughput between A and B, like this:
PC A <---> APU2 <---> PC B
pf rules are the one shipped by default in 6.3:
gw# pfctl -sr
can you show us a copy of your sysctl output?
check if smt is disabled ... (Hyper Threading )
Im not sure if this would have an effect on the
APU2C2 ... but worth checking as it is a change
in behaviour between 6.3 and current AFIK
Thanks
Tom Smyth
On Thu, 4 Oct 2018 at 04:58, Benjamin Petit
Added my sysctl output in attachement (I never really used
distribution lists before...)
I don't think the APU2 uses HT, but I tried with sysctl hw.smt=1,
no difference in the iperf3 numbers.
On Thu, 2018-10-04 at 05:02 +0100, Tom Smyth wrote:
> can you show us a copy of your sysctl output?
>
>
Hi Tom,
> The book of PF by Peter M Hansteen is very good, and openBSD Specific
> Building Internet firewalls is good also ... Building internet
> firewalls book can
> be a bit verbose atimes... but it does go through things in detail...
Thank you for your recommendation. I apologize for my
Hi Ingo,
Thank you for your response.
> i mostly learn by reading reference manuals, standard documents,
> and source code.
I try to too, but with limited successes. So topology and other higher
order concepts are out of my competency area, and hence my question.
> I mentioned it to show that
Hi Stuart,
Thank you for your response.
> > 2) How to disable an interface from joining IPv6 Node Information
> > multicast group (RFC 4620)?
> > In sys/netinet6/in6.c, the function in6_update_ifa contains the
> > following lines:
> >
> > /*
> > * join node information group address
> > */
> >
Hi,
Aaron Mason wrote on Wed, Oct 03, 2018 at 09:07:40AM +1000:
> Apparently you've got to go through your source code
> and plug the product in every single non-header file.
Which is of course trivial to do - you write a script to do a
checkout, run "sed -i", run the tool, collect the the
20 matches
Mail list logo
