Got it:
"A TLS server key and self-signed cert for 127.0.0.1 are also required;
see listen on in the RELAYS section for more details about certificate
locations."
eg:
openssl req -x509 -days 365 -newkey rsa:2048 \
-keyout /etc/ssl/private/127.0.0.1.key -out /etc/ssl/127.0.0.1.cr
Hi misc@
I am using the example for the TLS inspection from the relayd.conf(5) man
page:
# openssl req -x509 -days 365 -newkey rsa:2048 \
-keyout /etc/ssl/private/ca.key -out /etc/ssl/ca.crt
I set the PEM password to "password123"
then have the following relayd.con
On Mon, Apr 27, 2020 at 05:12:59PM +0200, Jan Stary wrote:
> Thanks for the clue, video0 at uvideo0 is detected again
> (dmesg below; NB: a different macbook with the same symptom).
>
note
you're now showing an amd64 kernel log
your first post all the logs were i386
so your analysis (one machine
On Mon, Apr 27, 2020 at 07:26:08PM +0100, Richard Chivers wrote:
> Hi,
>
> That makes a lot of sense thanks, and appears to have solved the problem,
> we had a route added through our loopback interface in production"
> "!/sbin/route add -reject default 127.0.0.1"
>
> Is that the best/general pra
Richard Chivers(r.chiv...@zengenti.com) on 2020.04.27 19:26:08 +0100:
> Hi,
>
> That makes a lot of sense thanks, and appears to have solved the problem,
> we had a route added through our loopback interface in production"
> "!/sbin/route add -reject default 127.0.0.1"
>
> Is that the best/genera
Hi,
That makes a lot of sense thanks, and appears to have solved the problem,
we had a route added through our loopback interface in production"
"!/sbin/route add -reject default 127.0.0.1"
Is that the best/general practise in general?
Cheers
Richard
On Mon, Apr 27, 2020 at 8:25 AM Claudio Jek
On Apr 27 10:55:15, sema...@online.fr wrote:
> On Mon, Apr 27, 2020 at 10:26:23AM +0200, Jan Stary wrote:
> > This is current/i386 on an old macbook (dmesgs below).
> > It runs fine except it no longer recognizes the video0 camera
> > ist used to. I am seeing the same on another macbook (amd64).
>
Try something like this in pf.conf:
pass in on hvn1 proto tcp from to (hvn1) port 22 reply-to
10.0.0.1@hvn1
The reason you have to do this is because you have the same router address on
hvn0 and hvn1 (10.0.0.1). Another option is to use route tables.
Let me know if you have any questions. I
what exactly are you trying to achieve, or: why not use azure firewall?
On 26.04.20 17:27, 4642 wrote:
> Hi, I have created a OpenBSD 6.6 VM in the Azures cloud that I plan to use as
> a Firewall, I had planned on using carp but I can't get it working in Azure
> so I think I can use an Internal
On Mon, Apr 27, 2020 at 10:26:23AM +0200, Jan Stary wrote:
> This is current/i386 on an old macbook (dmesgs below).
> It runs fine except it no longer recognizes the video0 camera
> ist used to. I am seeing the same on another macbook (amd64).
>
> [...]
>
> Looking at uvideo.c history, I naively s
This is current/i386 on an old macbook (dmesgs below).
It runs fine except it no longer recognizes the video0 camera
ist used to. I am seeing the same on another macbook (amd64).
uvideo-firmware-1.2.p3 is installed; in short, what is now
acpivideo0 at acpi0: GFX0
uvideo0 at uhub0 port 4 configura
On Sun, Apr 26, 2020 at 08:44:42PM +0100, Richard Chivers wrote:
> Not sure how I missed the clear information in the man page...
>
> "If set to default, a default route pointing to this router will be
> announced over OSPF"
>
> It seems I am just having an issue and it should work as I expected.
12 matches
Mail list logo