On 11/29/20 7:09 PM, Ed Ahlsen-Girard wrote:
> I've had a couple of panics:
>
> mtx(something) (address)
> locking against myself
>
>
> in the last
> couple of days. The most recent address was 0x821c63c8
>
> How do this get tracked down? No core files from anything in the
> applicable
Hi folks,
On 11/28/20 5:13 PM, Stuart Henderson wrote:
It is easy enough to add the filename, but adding that to the log
might suggest to users that things are setup to handle multiple pflogd
processes and that is not the case.
Various parts of the system would need changing in order to
I've had a couple of panics:
mtx(something) (address)
locking against myself
in the last
couple of days. The most recent address was 0x821c63c8
How do this get tracked down? No core files from anything in the
applicable time window. dmesg below signature.
--
Edward Ahlsen-Girard
Ft
Hi all,
I am trying to setup an OpenBSD 6.7 virtual machine under VMware ESXi 6.7 to
use as a filtering bridge between two virtual networks. I enabled promiscuous
mode for both virtual switches.
One network is the VMnet network, which is connected to the “outside world”.
“A” ——> “B” ——> “R”
Hello Heinrich,
it is not OpenBSD it is a Vmware issue ...
virtualnets / vswitches in ESXI are not proper switches... they forward
packets based on static mac- virtual port entries. (they do not do proper
mac learning)
you can set the vwswitch in the networking configuration section ... there
Some things I forgot:
All interfaces are UP
pf(4) ist disabled
bridge0 sees a bunch of lladdrs on em0 and one on em1, which is that of “A”
-Heinrich
> On 29. Nov 2020, at 22:29, Heinrich Rebehn wrote:
>
> Hi all,
>
> I am trying to setup an OpenBSD 6.7 virtual machine under VMware ESXi 6.7
Unfortunately, switching to vmx(4) did *not* do the trick
-Heinrich
> On 29. Nov 2020, at 22:38, Heinrich Rebehn wrote:
>
> Some things I forgot:
>
> All interfaces are UP
> pf(4) ist disabled
> bridge0 sees a bunch of lladdrs on em0 and one on em1, which is that of “A”
>
> -Heinrich
>
>
On Sat, 28 Nov 2020 at 11:14, Sebastian Benoit wrote:
> Hi,
>
>
>
> route add -label FOOBAR 172.16.1.0/24 172.16.2.5
> route show -label FOOBAR
>
> I am only aware of these mechanisms to set labels on routes added by
> routing daemons:
>
> bgpd (rtlabel keyword in filter "set")
>
On 2020-11-28, Gregory Edigarov wrote:
> #!/bin/sh
> rm -rf /usr/local/* /var/db/pkg/* /var/db/pkg/.* /etc/rc.d/*_daemon
There are only 3 packages with /etc/rc.d/*_daemon files.. also
you aren't putting /usr/local/lib/X11/app-defaults back how it should
be, and you miss creating the directory
Hi,
supo...@mdfsoftware.com.br wrote on Sun, Nov 29, 2020 at 01:40:18PM -0300:
> 0
> C Brazil
> P Ceará
> T FORTALEZA
> Z 60410442
> O MDFSoftware
> I Oliveira Filho, D. A.
> A Av. Eduardo Girão 355
> M supo...@mdfsoftware.com.br
> U http://www.mdfsoftware.com.br/
> B +55-85-9-89739017
> X
0
C Brazil
P Ceará
T FORTALEZA
Z 60410442
O MDFSoftware
I Oliveira Filho, D. A.
A Av. Eduardo Girão 355
M supo...@mdfsoftware.com.br
U http://www.mdfsoftware.com.br/
B +55-85-9-89739017
X +55-85-9-96110010
N Auditoria, Desenvolvimento, Suporte comercial para FreeBSD e
OpenBSD, gateways de
It turns out that my caring ISP really has a free firewall service
which is enabled by default.
I asked my ISP to disable it completely and now everything is OK.
Thank you!
29.11.2020 13:08, Stuart Henderson пишет:
On 2020-11-29, Родин Максим wrote:
The problem is that only port 80 seems to
On Sat, Nov 28, 2020, at 9:40 AM, Gregory Edigarov wrote:
>
>
> On 11/25/20 3:26 PM, Manuel Giraud wrote:
> > Hi,
> >
> > I'd like to upgrade (on -current) and, in the process, remove some cruft
> > accumulated over the years. I usually do sysupgrade and sysclean for
> > system.
> >
> > But for
It turns out that my caring ISP really has a free firewall service
which is enabled by default.
I asked my ISP to disable it completely and now everything is OK.
Thank you!
29.11.2020 14:30, Stuart Henderson пишет:
On 2020-11-29, Stuart Henderson wrote:
On 2020-11-29, Родин Максим wrote:
On 2020-11-29, Stuart Henderson wrote:
> On 2020-11-29, Родин Максим wrote:
>> The problem is that only port 80 seems to be open from the outside.
>> I used several online port scanners to check this.
>> All of them tell:
>> port 80 OPEN
>> port 443 CLOSED
>
> Could it be blocked by your ISP? Do
On 2020-11-28, Jan Stary wrote:
> If I'm reading you right, the rotation sends a SIGHUP to each
> of the pflogd processes; twice, in fact: after rotating each
> of the two files. Is that the case?
Yes, you have the same command for restarting pflogd on both
newsyslog.conf lines so it will send
Hi.
Just wondering if anyone else has seen any problems with tmux integration with
iterm2 on 6.8. I updated two i386 machines (alix 2c13) to 6.8 using
sysupgrade, and both of them seem to be unresponsive to tmux integration using
the latest version (3.4.2) of iterm2. In 6.7 and earlier, I’ve
On 2020-11-29, Родин Максим wrote:
> The problem is that only port 80 seems to be open from the outside.
> I used several online port scanners to check this.
> All of them tell:
> port 80 OPEN
> port 443 CLOSED
Could it be blocked by your ISP? Do you receive packets on your external
interface at
Hi,
I had made a program in 2014, but forgot whether I made it for FreeBSD or
OpenBSD. This program (found here: https://centroid.eu/public/ttldaemon.c.txt)
changes the default ttl in the system's network stack in order to read out
steganographically a christmas or new years message.
The
19 matches
Mail list logo
