Hey,
is it possible that OpenVPN can not handle TAP on -current (12) any
more?
I tried it with Linux -> FreeBSD and FreeBSD -> FreeBSD with the same
result. On the server, the pings for example arrived at unknown
ethernet packets or sth. He was still trying to learn new MAC addrs.
I am suspecting
On 7/29/18 10:43 AM, blubee blubeeme wrote:
Has anyone else noticed that svn is getting this type of error trying to
run svn: svn: E65: Error running context: No route to host
This is likely due to network problems, not the subversion server itself.
Yuri
___
Hi,
settings in BIOS:
- power-off system if watchdog is not taken care of 10 minutes after power-on
What I have with r336564 is: watchdogd is started during boot and
system runs fine.
What I have with r336767 is: watchdogd is started but system powers
off after 10 minutes.
What I have with
Has anyone else noticed that svn is getting this type of error trying to
run svn: svn: E65: Error running context: No route to host
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sun, 29 Jul 2018 08:58:47 -0400
Michael Butler schrieb:
> This started a few days ago .. no apparent ill effect but still annoying ..
>
> *** Creating the temporary root environment in /var/tmp/temproot
> *** /var/tmp/temproot ready for use
>
This started a few days ago .. no apparent ill effect but still annoying ..
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sun, 29 Jul 2018 15:17:53 +0400
Roman Bogorodskiy schrieb:
> O. Hartmann wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Am Sun, 29 Jul 2018 12:09:58 +0400
> > Roman Bogorodskiy schrieb:
> >
> > > O. Hartmann w
O. Hartmann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Sun, 29 Jul 2018 12:09:58 +0400
> Roman Bogorodskiy schrieb:
>
> > O. Hartmann wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA512
> > >
> > > Am Sat, 28 Jul 2018 11:29:40 +0400
> > > Roman Bo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sun, 29 Jul 2018 12:09:58 +0400
Roman Bogorodskiy schrieb:
> O. Hartmann wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Am Sat, 28 Jul 2018 11:29:40 +0400
> > Roman Bogorodskiy schrieb:
> >
> > > Hi,
> > >
> >
O. Hartmann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Sat, 28 Jul 2018 11:29:40 +0400
> Roman Bogorodskiy schrieb:
>
> > Hi,
> >
> > I have a test box that's updated to -CURRENT usually once in a week or
> > two. This box boots using UEFI. After a regular update about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sat, 28 Jul 2018 11:29:40 +0400
Roman Bogorodskiy schrieb:
> Hi,
>
> I have a test box that's updated to -CURRENT usually once in a week or
> two. This box boots using UEFI. After a regular update about two weeks
> ago it started to panic on bo
Roman Bogorodskiy wrote:
> Hi,
>
> I have a test box that's updated to -CURRENT usually once in a week or
> two. This box boots using UEFI. After a regular update about two weeks
> ago it started to panic on boot frequently (not UEFI related), but I
> could not get a crash dump because my swap
12 matches
Mail list logo