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, etc..).
If anyone ever faces this problem and this to your `/etc/rc.conf`:
```
ipv6_static_routes="cjdns"
ipv6_route_cjdns="-net fc00::/7 fc4d:b57e:887e:5f2a:33e7:a215:2399:ea72"
cjdns_enable="YES"
```
and add this to the `interface` section of `router` at the end of the line:
```
"tunDevice": "tun0"
```
It should like this in the end:
```
"interface": {
// The type of interface (only TUNInterface is supported
for now)
"type": "TUNInterface",
// The type of tunfd (only "android" for now)
// If "android" here, the tunDevice should be used as the
pipe path
// to transfer the tun file description.
// "tunfd" : "android"
// The name of a persistent TUN device to use.
// This for starting cjdroute as its own user.
// *MOST USERS DON'T NEED THIS*
"tunDevice": "tun0"
},
```
and then restart your FreeBSD machine and cjdns should work !
On 1/27/20 6:53 PM, freneza wrote:
I am having major trouble getting cjdns working on FreeBSD.
I was capable of running it on Debian and Fedora without any trouble,
but FreeBSD has trouble with getting the network to route properly.
I tried the `pkg install cjdns` and running it from source, but both
don't work for me.
If someone could get cjdns to work, please create a guide. All generic
(usually Linux-targetted) cjdns guides didn't work for me.
I am sure my connectTo configuration (peering) is correct because I
use the same peers on Fedora and Debian without a hitch.
_______________________________________________
freebsd-security@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
