I am replying to myself..
I have fixed this problem by adding a stating route. Turns out cjdns
FreeBSD doesn't add a proper route when being run from FreeBSD. In
addition you had to statically select the interface name or else it will
just increment whenever you restart cjdns (tun0, tun1, tun2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
=
FreeBSD-SA-20:01.libfetch Security Advisory
The FreeBSD Project
Topic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
=
FreeBSD-SA-20:02.ipsec Security Advisory
The FreeBSD Project
Topic:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
=
FreeBSD-SA-20:03.thrmiscSecurity Advisory
The FreeBSD Project
Topic:
Is the @freebsdsecurity Twitter handle managed by the security team? (If
so, looks like it's been fallow since 2016?)
If not, is there an equivalent Twitter account that is official?
--
Royce
___
freebsd-security@freebsd.org mailing list
https://lists.
On 29/01/2020 7:51 am, Royce Williams wrote:
Is the @freebsdsecurity Twitter handle managed by the security team? (If
so, looks like it's been fallow since 2016?)
If not, is there an equivalent Twitter account that is official?
Hi Royce,
I run @FreeBSDHelp, tweet about FreeBSD security relat