endian problems on FreeBSD?

[Guus Sliepen]

On Mon, Mar 09, 2015 at 09:52:51PM -0400, Brett Wynkoop wrote:

> This seems the most probable from the various tests and key changes and
> so forth that I have done.  Yes I went through everything else you
> mention in the FAQ and your last email.

Ok. Can you try copying the tinc configuration from the Beaglebone to an
x86 machine, including the public and private keys, and run tinc on the
latter? If it then runs fine, then there is indeed a problem with tinc
on ARM FreeBSD, if not then the problem is with the private and/or
public key.

> Here is my tinc.conf
> 
> [wynkoop at beaglebone /usr/local/etc/tinc/wdl]$ more tinc.conf
> Name = beaglebone
> AddressFamily = ipv4
> INTERFACE = tun0
> DEVICE = /dev/tun0

That looks OK.

> [wynkoop at beaglebone /usr/local/etc/tinc/wdl]$ more tinc-up
> #!/bin/sh
> /sbin/ifconfig $INTERFACE 192.168.254.113   netmask 255.255.255.0
> /sbin/route add -net 192.168.254.0 192.168.254.113
> 
> Which is the same, except addresses as on my other FreeBSD boxes and
> they do not toss the route error.

The route command is redundant, since the ifconfig command would
already have added a route for 192.168.254.0/24 to the routing table. I
think that explains the error message you get.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150310/13a440d5/attachment.sig>