On Wed, May 20, 2020 at 02:30:31AM +0200, Ingo Schwarze wrote:
> Hi Kurt,
>
> Kurt Mosiejczuk wrote on Tue, May 19, 2020 at 07:49:56PM -0400:
> > On Mon, May 18, 2020 at 08:12:00PM +0200, Klemens Nanni wrote:
> >> On Mon, May 18, 2020 at 01:20:07PM -0400, Kurt Mosiejczuk wrote:
>
> >>> Learning
On Tue, May 19, 2020 at 11:36:23PM +0200, Patrick Wildt wrote:
> Hi,
>
> drahn@ was complaining to me that his cross-compiler wasn't defining
> __OpenBSD__ or __ELF__, and I think the fix is pretty simple. We're
> just missing a case in a switch-case.
>
> The .cpp file itself still compiles,
Generally packets are not transmitted by carp interfaces, but we have a
couple of things at work that mean we do send packets out on them.
Firstly, we have a dhcp relay implementation we run on carp interfaces,
and we sent dhcp replies fast enough to fill up the one slot on the
transmit queue and
2 Hi Vitaliy,
On Tue, May 19, 2020 at 12:11 PM Vitaliy Makkoveev
wrote:
> On Mon, May 04, 2020 at 10:03:40PM +0300, Sergey Ryazanov wrote:
> > Split checks from frame accepting with header removing in the common
> > PPP input function. This should fix packet capture on a PPP interfaces.
>
> Can
Hi Kurt,
Kurt Mosiejczuk wrote on Tue, May 19, 2020 at 07:49:56PM -0400:
> On Mon, May 18, 2020 at 08:12:00PM +0200, Klemens Nanni wrote:
>> On Mon, May 18, 2020 at 01:20:07PM -0400, Kurt Mosiejczuk wrote:
>>> Learning how LDOMs work on this T4-1 and we only create 8 devices
>>> (each /dev/ldom*
On Mon, May 18, 2020 at 08:12:00PM +0200, Klemens Nanni wrote:
> On Mon, May 18, 2020 at 01:20:07PM -0400, Kurt Mosiejczuk wrote:
> > Learning how LDOMs work on this T4-1 and we only create 8 devices
> > (each /dev/ldom* and /dev/ttyV*) by default. The now-commonly-available
> > T4-1 machines can
> On 20 May 2020, at 1:31 am, Miod Vallat wrote:
>
> There seems to be a logic error in tcpdump's print-gtp.c.
>
> The code is printing some values by passing a pointer to the array of
> strings, and the index within the array, and the routine uses
> sizeof(array) / sizeof(array[0]) to
On Mon, May 18, 2020 at 08:43:25PM +0200, Otto Moerbeek wrote:
> On Mon, May 18, 2020 at 06:27:04PM -, Miod Vallat wrote:
> > > Learning how LDOMs work on this T4-1 and we only create 8 devices
> > > (each /dev/ldom* and /dev/ttyV*) by default. The now-commonly-available
> > > T4-1 machines
> Date: Tue, 19 May 2020 23:36:23 +0200
> From: Patrick Wildt
>
> Hi,
>
> drahn@ was complaining to me that his cross-compiler wasn't defining
> __OpenBSD__ or __ELF__, and I think the fix is pretty simple. We're
> just missing a case in a switch-case.
>
> The .cpp file itself still compiles,
Stuart Henderson wrote:
> On 2020/05/19 14:23, Dirk Praet wrote:
> > A manual xorg config with the vesa driver brought X back to life, but not
> > until I set machdep.allowaperture=2 in /etc/sysctl.conf . Thanks for your
> > reply, Matthieu. I do hope 6.7 doesn't come with similar surprises,
On 2020/05/19 14:23, Dirk Praet wrote:
> A manual xorg config with the vesa driver brought X back to life, but not
> until I set machdep.allowaperture=2 in /etc/sysctl.conf . Thanks for your
> reply, Matthieu. I do hope 6.7 doesn't come with similar surprises, though
Run -current between
Hi Tom,
Thanks for offering.
I built a personal OpenBSD/socppc 6.5 release last year for my RB600A and
continue to use it. I tried building 6.6 but found compiling clang infeasible
on a platform with only 128MB of memory and PIO compact flash. I tried to
improve the swap experience by adding an
Hi,
drahn@ was complaining to me that his cross-compiler wasn't defining
__OpenBSD__ or __ELF__, and I think the fix is pretty simple. We're
just missing a case in a switch-case.
The .cpp file itself still compiles, but I haven't built a full clang
with it. Please give it a go and report back.
A manual xorg config with the vesa driver brought X back to life, but not
until I set machdep.allowaperture=2 in /etc/sysctl.conf . Thanks for your
reply, Matthieu. I do hope 6.7 doesn't come with similar surprises, though
--
Sent from:
So according to RFC2579 an octetstring can contain UTF-8 characters if
so described in the DISPLAY-HINT. One of the main consumers of this is
SnmpAdminString, which is used quite a lot.
Now that we trimmed a little fat from snmp's oid, I wanted to fill it
up again and implemented the bare
Hello Devs,
Thanks again for all your work on OpenBSD 6.7
just checking if any of you would need / want RB800s, as per mail below,
I also have 2x RB600s which at one stage did run OpenBSD PPC edition
if any dev want them contact me off list and Ill have them shipped to you
Thanks and stay safe
There seems to be a logic error in tcpdump's print-gtp.c.
The code is printing some values by passing a pointer to the array of
strings, and the index within the array, and the routine uses
sizeof(array) / sizeof(array[0]) to figure out the bound.
But since the caller is passing a pointer,
- OpenBSD 6.7 RELEASED -
May 19, 2020.
We are pleased to announce the official release of OpenBSD 6.7.
This is our 48th release. We remain proud of OpenBSD's record of more
I am OK with this diff. Also all pseudo interfaces except switch(4) do
the same.
On Mon, May 04, 2020 at 10:02:53PM +0300, Sergey Ryazanov wrote:
> Use bpf filter hook from the common interface structure. This simplifies
> the code by unifying it and prepare ppp(4) for pipex(4) support.
>
> Ok?
Hello Sergey.
I am not the developer, but I works in pipex(4) layer too. Also mpi@
wants I did rewiev for your diffs.
On Mon, May 04, 2020 at 10:03:40PM +0300, Sergey Ryazanov wrote:
> Split checks from frame accepting with header removing in the common
> PPP input function. This should fix
On Tue, May 19, 2020 at 08:48:17AM +1000, Jonathan Matthew wrote:
> So far I've completely ignored offloads in the ethernet drivers I've
> written, but on having a quick look at the documentation I found that
> mcx(4) checksum offload is extremely easy to use, and some simple testing
> suggests
On Mon, May 18, 2020 at 12:18:47PM +0200, Martijn van Duren wrote:
> Anyone feeling like trimming a little fat?
>
OK denis@
> On Fri, 2020-05-08 at 11:41 +0200, Martijn van Duren wrote:
> > Diff below removes fields from struct oid used by snmpd but not useful
> > for snmp(1). Minus 503LoC and
Anders Andersson wrote:
> On Tue, May 19, 2020 at 9:10 AM Peter J. Philipp wrote:
> >
> > Hi,
> >
> > Before I wrote this email I searched under marc.info and did a google
> > search,
> > but I didn't get a definitive answer. I found this under openbsd.org:
> >
> >
We have released OpenBGPD 6.7p0, which will be arriving in the
OpenBGPD directory of your local OpenBSD mirror soon.
This is the first stable release for the 6.7 version. It includes
the following changes:
* Add initial support for JSON output in bgpctl(8).
* Allow setting both IPv4 and
> Content-Type: text/plain; charset="utf-8"
> From:
> Date: Wed, 13 May 2020 23:36:57 -0700
Hi John,
> The process of using 40/50 row vga text modes is pretty cumbersome now:
>
> wsfontload -h 8 -e ibm /usr/share/misc/pcvtfonts/vt220l.808
> wsconscfg -dF 1
> wsconscfg -t 80x50 1
>
> I just
On Tue, May 19, 2020 at 12:19:12PM +0300, Vitaliy Makkoveev wrote:
> I am OK with this diff. Also all pseudo interfaces except switch(4) do
> the same.
Agreed. There is no need to be special here. This is OK claudio and I will
commit it later unless someone else wants to jump in first.
> On
I haven't used wsmoused in ages, but I tend to think ideas like (by default)
scaling to the font size have great merit.
There should be a debugging toggle (maybe) to get raw values.
It should work out-of-the-box preferably. ;)
> On 19/05/2020, at 11:19 AM, Alexandr Nedvedicky
> wrote:
>
> I'm not sure about outbound path. chksum offload on outbound side got killed
> back in 2016 (I think). All that logic behind dealing with various HW did not
> pay off. If PF is doing NAT it's far more simple and reliable if we
28 matches
Mail list logo
