Hi Miod,
Thanks for helping. With this patch unfortunatly I still get a trap 2 on
my small unifi security gateway which I pulled out again to test your patch.
--->
cnmac0: 192.168.177.35 lease accepted from 192.168.177.1 (24:a4:3c:06:9f:16)
pppoe0: received unexpected PADO
pppoe0: host uniqu
On Wed, Oct 23, 2019 at 02:40:53PM +0200, Otto Moerbeek wrote:
> Hi,
>
> The patch below add opportunistic DoT to unwind. Some background
> info:
>
> The purpose of unwind is to provide secure DNS services even when
> the available nameservers are broken or filtered like in many hotels.
> To do
On Thu, Oct 24, 2019 at 12:19:05AM +0200, Klemens Nanni wrote:
> On Thu, Oct 24, 2019 at 12:10:09AM +0200, Klemens Nanni wrote:
> > Someone on IRC (I forgot the name, sorry) mentioned that the
> > `adaptive.end' and `adaptive.end' timeout variables had their documented
> > default values swapped.
>
Hello tech@,
Here is the patch discussed in the previous email. This part covers
the handlers and changes in the header file.
@@ -5480,6 +5830,32 @@ svm_handle_inout(struct vcpu *vcpu)
}
/*
+ * svm_handle_mmio
+ *
+ * Exit handler for memory accesses to PCI MMIO region.
+ */
+int
+svm_handle_m
Hello tech@,
Here is the patch discussed in the previous email. This covers emulation part.
@@ -5378,6 +5441,293 @@ vmm_get_guest_cpu_mode(struct vcpu *vcpu
}
/*
+ * get_vcpu_regs_id
+ *
+ * an utility for parse_instruction():
+ * get a VCPU_REGS id from instruction bytes.
+ */
+int
+get_
Hello tech@,
Here is the patch discussed in the previous email. This part mainly
covers changes in the declaration part and fault handlers.
Index: sys/arch/amd64/amd64/vmm.c
===
RCS file: /cvs/src/sys/arch/amd64/amd64/vmm.c,v
retrie
Hello tech@,
I introduce an MMIO handler in vmm(4) as an attempt to make a
scaffolding for full-featured MMIO handler which requires more effort.
I will send a few emails with patches after this one. First of all, I
show the overview.
As I sent you earlier in emails about a question on vmclear()
Hello,
I like to swap the order, so adaptive.start goes first.
Though I'm not sure the default value for adaptive.start
is 5, I think it's 6. Or do I miss something?
> -.It Cm adaptive.start Pq 12 states by default
> +.It Cm adaptive.start Pq 5 states by default
On Thu, Oct 24, 2019 at 12:10:09AM +0200, Klemens Nanni wrote:
> Someone on IRC (I forgot the name, sorry) mentioned that the
> `adaptive.end' and `adaptive.end' timeout variables had their documented
> default values swapped.
>
> Obviously, start must be lower than end; I took the chance and als
On Wed, Oct 23, 2019 at 11:56:13PM +0200, Klemens Nanni wrote:
> I did not bother comparing host and IP because it quickly breaks for
> unshortened IPv6 addresses, e.g.
>
> $ ./obj/nc -w1 -v 2001:0db8::1 22
> nc: connect to 2001:0db8::1 (2001:db8::1) port 22 (tcp) failed:
> Operation
Someone on IRC (I forgot the name, sorry) mentioned that the
`adaptive.end' and `adaptive.end' timeout variables had their documented
default values swapped.
Obviously, start must be lower than end; I took the chance and also
moved the start list element above the end one, as this reflects the
in
Safe enough from my perspective.
Back in the days of YP-over-network that kind of thing was nasty,
but we only do service discovery on-system now
Klemens Nanni wrote:
> nc(1) still resolves service names if `-n' is given, only hostnames are
> effected.
>
> Instead of changing the code, which d
nc(1) still resolves service names if `-n' is given, only hostnames are
effected.
Instead of changing the code, which does behave like other tools such as
pfctl(8), fix the manual by simply using pfctl's `-N' wording.
OK?
Index: nc.1
==
On Wed, Oct 23, 2019 at 09:11:47PM +, Job Snijders wrote:
> Scratching a small itch: telnet(1) nicely prints what IP addresses it is
> attempting to connect to, I'd like 'nc -v' to do the same, see below:
Yes, please; I had an almost identical diff but shelved it for later.
Also thought about
Looks great to me.
Alexander Bluhm wrote:
> On Thu, Oct 17, 2019 at 04:23:32PM +0200, Alexander Bluhm wrote:
> > There are more warnings, but the diff is long enough already.
>
> Here is the next part to fix ifconfig warnings. The global variable
> "name" is the interface name. Sometimes it i
Similar behaviour seems more sensible to me.
The messaging is really verbose, but it remains largely compatible
with the original netcat and we haven't chosen to deviate from
that yet I guess.
Job Snijders wrote:
> Dear all,
>
> Scratching a small itch: telnet(1) nicely prints what IP addresse
Dear all,
Scratching a small itch: telnet(1) nicely prints what IP addresses it is
attempting to connect to, I'd like 'nc -v' to do the same, see below:
$ nc -v localhost 23
nc: connect to localhost (127.0.0.1) port 23 (tcp) failed: Connection refused
nc: connect to localhost (::1) port 23 (tcp)
On Thu, Oct 17, 2019 at 04:23:32PM +0200, Alexander Bluhm wrote:
> There are more warnings, but the diff is long enough already.
Here is the next part to fix ifconfig warnings. The global variable
"name" is the interface name. Sometimes it is passed as parameter,
sometimes it is accessed directl
> Try changing all the final 0 in sppp_auth_send() to 0UL and this ought
> to work. This function needs __attribute__((__sentinel__)) as well to
> prevent such mistakes from occurring again.
The sentinel attribute wants a pointer, not a zero size_t,
unfortunately.
Please try this diff.
Index:
> The system has a trap 2, which I looked up as:
>
> #define T_TLB_LD_MISS 2 /* TLB miss on load or ifetch */
>
> what happens before this patch, I think, is that there is a varargs size_t
> (which is size 8 in mips64), that gets promoted (I think) in varargs to int
> (which wou
On Wed, Oct 23, 2019 at 02:40:53PM +0200, Otto Moerbeek wrote:
> [1] https://doh.powerdns.org/doh/privacy.html
Should be https://powerdns.org/doh/privacy.html
Hi,
The patch below add opportunistic DoT to unwind. Some background
info:
The purpose of unwind is to provide secure DNS services even when
the available nameservers are broken or filtered like in many hotels.
To do that, it prefers DNSSEC whenever possible and changes to do
resolving by itself
Hi Janne,
I think the way this patch is, it's ghetto, I don't even know if OpenBSD
wants to take it on, hence I sent it as a hint. What really would be cool is
to find out why exactly the trap 2 happens, because the pppoe code works on
a lot of other archs.
My effort is selfish because I want my
Den ons 23 okt. 2019 kl 09:15 skrev Peter J. Philipp :
> Hi Holger & Tech,
>
> I have made my octeon router work again and I have a patch.
>
>
Truncated it a lot, leaving the things I reacted on:
> - sppp_auth_send(&chap, sp, CHAP_RESPONSE, h->ident,
> -
On Wed, Oct 23, 2019 at 11:18:11AM +0200, Martin Pieuchot wrote:
> On 23/10/19(Wed) 08:43, Peter J. Philipp wrote:
> > Hi Holger & Tech,
>
> Hello Peter,
>
> > I have made my octeon router work again and I have a patch. But I'm not an
> > openbsd developer, nor is this patch official in any way.
On 23/10/19(Wed) 08:43, Peter J. Philipp wrote:
> Hi Holger & Tech,
Hello Peter,
> I have made my octeon router work again and I have a patch. But I'm not an
> openbsd developer, nor is this patch official in any way.
Could you explain in words what is the issue? Why does your diff
prevent it
On Wed, Oct 23, 2019 at 08:47:25AM +0200, Theo Buehler wrote:
> On Wed, Oct 23, 2019 at 08:04:26AM +0200, Claudio Jeker wrote:
> > On Wed, Oct 16, 2019 at 10:47:25PM +0200, Claudio Jeker wrote:
> > > On Wed, Oct 16, 2019 at 07:26:25AM -0300, Alexandre Hamada wrote:
> > > > Hi Tech,
> > > > I would
27 matches
Mail list logo
