> On 14 Oct 2016, at 16:17, Ted Unangst wrote:
>
> David Gwynne wrote:
>> this adds a pool backend for MCLGETI thats 2k+2 bytes in size, which
>> can be used on some very common nics that have annoying constraints
>> on their rx descriptors.
>>
>> this in turn simplifies the code in those drive
> Which acpi table should I attach?
Use sendbug(1). See also
http://www.openbsd.org/report.html#bugtypes
David Gwynne wrote:
> this adds a pool backend for MCLGETI thats 2k+2 bytes in size, which
> can be used on some very common nics that have annoying constraints
> on their rx descriptors.
>
> this in turn simplifies the code in those drivers and lets them
> always operate on ETHER_ALIGN boundaries
It is time to put the nasty comment from rl(4) into em(4) and ix(4).
Everybody knew how bad realtek was but thinks Intel nics are good. The
truth is that modern Intel nic are as bad as the cheepest and crapiest
10/100 Mbps Ethernet chips from the last millenium.
--
:wq Claudio
On Fri, Oct 14, 20
this adds a pool backend for MCLGETI thats 2k+2 bytes in size, which
can be used on some very common nics that have annoying constraints
on their rx descriptors.
this in turn simplifies the code in those drivers and lets them
always operate on ETHER_ALIGN boundaries.
the pool is cheap, pages will
Ted Unangst wrote:
> 16 bit IDs don't offer much security. This is well known. A trick to encode
> more bits into the query is to vary the case of the query name. It's case
> insensitive, but all known servers echo it back exactly, case preserving. Thus
> we can twiddle the query on the way out and
On Thu, Oct 06, 2016 at 10:36:48PM -0500, Matthew Martin wrote:
> There doesn't seem to be any reason for user to write out a config file
> with the defaults if none exists. I've never seen anything else in base
> do this, so kill it.
Ping. With man pages fixes this time.
- Matthew Martin
Index
16 bit IDs don't offer much security. This is well known. A trick to encode
more bits into the query is to vary the case of the query name. It's case
insensitive, but all known servers echo it back exactly, case preserving. Thus
we can twiddle the query on the way out and verify we get exactly the
On Thu, Oct 13, 2016 at 11:38:46PM +0100, Edd Barrett wrote:
> Hey,
>
> As we saw earlier on misc@, getting a vmm host on the internet when the
> host is using a wireless interface is not as straightforward as with
> wired interfaces.
>
> Specifically, a bridge won't work on a wireless interface,
Hello,
looks O.K. to me.
can you also do s/destinated/designated, when you are touching the
if_input_local() function already?
thanks and
regards
sasha
> ok?
>
> bluhm
>
> Index: net/if.c
> ===
> RCS file: /data/mirror/openbsd/cv
On 14 October 2016 at 00:38, Edd Barrett wrote:
> Hey,
>
> As we saw earlier on misc@, getting a vmm host on the internet when the
> host is using a wireless interface is not as straightforward as with
> wired interfaces.
>
> Specifically, a bridge won't work on a wireless interface, which in turn
> Am 14.10.2016 um 00:38 schrieb Edd Barrett :
>
> Hey,
>
> As we saw earlier on misc@, getting a vmm host on the internet when the
> host is using a wireless interface is not as straightforward as with
> wired interfaces.
>
> Specifically, a bridge won't work on a wireless interface, which in
Hi!
Thanks for looking into this. I've tried the patch and the "found GPIO
port" printf is not triggered because sc->sc_acpi->sc_hw_reduced is 0
for me.
Which acpi table should I attach?
Thanks,
Ilya
RSD PTR: Checksum=188, OEMID=ACRSYS, RsdtAddress=0x9aafe124
RSDT: Length=112, Revision=1, Ch
Hey,
As we saw earlier on misc@, getting a vmm host on the internet when the
host is using a wireless interface is not as straightforward as with
wired interfaces.
Specifically, a bridge won't work on a wireless interface, which in turn (I
think) means virtual switches don't work either (although
Currently rebound ignores packets with bad IDs. we should log them.
But while we're at it, we should do something a little sneakier. Leave the
socket open and listen for additional replies. Ordinarily that shouldn't
happen, but it can mean that somebody is trying to mess with us. A local
attacker
Quiet some sign warnings from the compiler. The common "st.st_size
> SIZE_MAX" check causes many of them. To avoid this we need to
cast st_size (which is off_t) to a large unsigned type. I think
uintmax_t makes the most sense for this.
- todd
Index: buf.c
=
On Fri, Jun 24, 2016 at 11:22:06AM +0200, Joris Vink wrote:
> On Fri, Jun 24, 2016 at 01:58:20PM +0800, Michael W. Bombardieri wrote:
> > If people are interested in opencvs diffs again, sharing a
> > rcsnum_free()->free()
> > clean-up item. Note that rcs(1) also has a version of rcsnum_free() wh
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
:32bi
Ivan Markin:
> Yes, you're absolutely right about purpose of this comment.
> This patch doesn't stop signify(1) from embedding a comment string
> before signature. It just makes it possible to verify signatures even if
> there is no 'untrusted comment: ' string in them.
Sorry that it is not clear
Hi,
m_resethdr() exists to clear information attached to a mbuf that
has been accumulated during processing. Especially pf(4) data is
removed. This feature used by pair(4) when a new input is started.
patrick@ has seen a mbuf going though lo(4) with an old inp attached.
I think this should be f
Hi Marc,
Marc Espie:
> It is slightly warped: it says "untrusted comment" because it's outside
> of the signed area and shouldn't be taken at face value, BUT if you have
> the right public key, AND manage to validate the signature with it, then
> it means that it *was* the right key, so in retrosp
The comments are a necessary feature these days, actually.
It is slightly warped: it says "untrusted comment" because it's outside
of the signed area and shouldn't be taken at face value, BUT if you have
the right public key, AND manage to validate the signature with it, then
it means that it *was
Hi,
Jan Stary wrote on Wed, Oct 12, 2016 at 10:36:12AM +0200:
> Why does logname(1) need to setlocale?
Because at some point in history, people thought doing as much work
as you can, even when it has no effect, brings you closer to
perfection (some may still labour in that vein).
Anyway, i just
Otto Moerbeek wrote:
> On Thu, Oct 13, 2016 at 08:20:52AM +0200, Otto Moerbeek wrote:
>
> > On Thu, Oct 13, 2016 at 08:01:22AM +0200, Otto Moerbeek wrote:
> >
> > > On Thu, Oct 13, 2016 at 12:15:34AM -0400, Ted Unangst wrote:
> > >
> > > > Theo de Raadt wrote:
> > > > > > On Wed, Oct 12, 2016 at
On Thu, Oct 13, 2016 at 08:20:52AM +0200, Otto Moerbeek wrote:
> On Thu, Oct 13, 2016 at 08:01:22AM +0200, Otto Moerbeek wrote:
>
> > On Thu, Oct 13, 2016 at 12:15:34AM -0400, Ted Unangst wrote:
> >
> > > Theo de Raadt wrote:
> > > > > On Wed, Oct 12, 2016 at 03:20:00PM +0200, Otto Moerbeek wrot
> The diff you sent simply ignores the issue which obviously can not be
> used in the tree.
The following diff starts working in the right direction, but there is
probably more to do in order to support machines like yours.
It would be interesting to see if that printf gets triggered though, so
p
On Mon, Oct 10, 2016 at 03:04:33PM -0700, Ilya Kaliman wrote:
> Hi tech,
>
> while trying the latest snapshot I've noticed that the following
> warning is printed to a console several times a second (this does not
> happen in 6.0):
>
> acpi0: WARNING EC not initialized
>
> The investigation show
> Do we want this? I don't know what else people use to look at,
> say, network packets in memory:
I like this and the diff is OK by me.
>
> ddb{3}> show mbuf $rax
> mbuf 0xff00dfa9d200
> m_type: 1 m_flags: 2
> m_next: 0xff00dfa9df00 m_nextpkt: 0x0
> m_data: 0xff00dfa9d2b
28 matches
Mail list logo