similar to: Tinc on PFSENSE box can join mesh, share keys, connect out, but doesn't reply to pings or connections

On Mon, Oct 23, 2017 at 6:38 PM, Darren Mobley <corpdecker at gmail.com> wrote: > I've tried IRC in #tinc and #pfsense on freenode for this, not luck yet, > figured I'd try the mailing list. > > A summary of my problem is here: > > https://www.reddit.com/r/PFSENSE/comments/789xus/tinc_vpn_can_do_everything_but_be_accessed/ > > If there are any details I can

Ok so how can I setup the SAMBA AD on the ZFS? I ma using this tutorial guide to do what I need it to do. Now, I do have the samba service being installed o a UFS formatted ZFS Volume. I know that without that, it won't work right. On Mon, Jul 3, 2017 at 12:52 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 3 Jul 2017 12:23:24 -0400 > phillip mobley via

WOW! OK! The light bulb above my head just came on. I added the script to the Subnet Up Script section, and now all the routes I need have been added in to the table for me. I did have to modify the line a little since I'm using pfSense (FreeBSD). I changed it to... route add "$SUBNET" -iface "$INTERFACE" ...I also used... route del "$SUBNET" -iface

But if Samba AD does not work on the ZFS filesystem, then why bundle it with the NAS4Free OS? What filesystems does the Samba AD support? On Thu, Jul 6, 2017 at 10:54 AM, Andrew Walker via samba < samba at lists.samba.org> wrote: > Yes. I imagine that's why Andrew Bartlett commented: "There may be some > good news in the future, as I've had one of the developers at

Hello all, I am looking to setup a Samba AD on my NAS. I am currently using the latest version of NAS4Free which has Samba bundled into it already. However, I am getting a very nasty error when I go in to setup the samba service: Initializing... Looking up IPv4 addresses Looking up IPv6 addresses No IPv6 address will be assigned Setting up share.ldb Setting up secrets.ldb Setting up the

On Wed, Aug 29, 2018 at 12:46 PM, Corey Boyle <coreybrett at gmail.com> wrote: > Do you know if the "VPN Netmask" option is specific to the pfSense > implementation, or does it correspond to a tinc config item? In Tinc, I believe each host has it's own Subnet, and that each such Subnet has whatever netmask it has. I believe there is no "VPN(-wide) Netmask" in

https://bugs.freedesktop.org/show_bug.cgi?id=104291 Bug ID: 104291 Summary: Virgl broken on current mesa (17.4+), with nouveau/nv50 as host Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi everyone. I'm wondering whether a setup like the one described below would be possible with Tinc: nodeA1 nodeB3 | | (Network A) --- [GWA] --- (Internet) --- [GWB] --- (Network B) | | nodeA2

http://www.open-mesh.org/ Idea #1: is BATMAN worth considering using as part of the layer 2 routing in Tinc? Idea #2: would it be possible to embed BATMAN as an option to avoid having to use Quagga for routing v6 subnets? -------------- next part -------------- An HTML attachment was scrubbed... URL:

> My idea is to register the same DNS name with as many IP addresses as i have 'servers' and may be some 'clients' with public IPs. The point is, a single DNS name will have all servers behind it, so the benefits are: You even need extra hosts files for every server, so why make it complicated? Other idea: Create 3 internet tinc server names in dns and 3 host files. Use as

On 4 June 2015 at 22:36, Johannes Ernst <johannes.ernst at gmail.com> wrote: > It seems to me that if Node B is supposed to be able to send stuff directly to Node C (instead of Node A), Node B needs to know where Node C is. Does this mean that each Node has to have a complete network map? This seems to become very unwieldy with larger deployments. Yes, each node knows about the entire

tinc uses direct UDP communication for performance, not reliability. If you want to establish more metaconnections for increased reliability, you can use AutoConnect (though it probably won't work across NATs). A better solution is to use two central nodes (instead of one) for redundancy. On 11 June 2015 at 18:59, Daniel J. Grinkevich <danielgrinkevich at gmail.com> wrote: > If we

Hi, if we are to configure Tinc just like a traditional server-client VPN, what would be the options to set in the configuration file to achieve that. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20160501/b5d5935f/attachment.html>

I've been slowly reviewing our KCC patch series by Douglas and Garming into Samba git master over the past few days, and I expect that to be fully merged shortly. The purpose of this work is to change Samba from full-mesh replication to respecting site boundaries, and so trying to reduce WAN replication traffic. However, I need the help of Samba administrators to ensure this work is ready

Hello, I tried to plot some 3d-plots with the 'mesh' function, but I allways get the message 'Fehler: konnte Funktion "mash" nicht finden' in english this means 'error: can't find the function "mesh"'. Do I need another package? I didn't found anything in the web this afternoon, only descriptions how to use the function. I looked up a lot of

Hello, tinc experts! I have a question that I have not been able to find an answer to after reading the manual and examples and I was hoping someone could help me. So, let's say I have an elastic number of hosts all in rfc-1918 space that need to talk to each other. And lets also say that I do not trust the network they are on. Is there a way I can configure tinc on all N hosts to use the

Hi I have a Tinc cluster of about 100 nodes, and they are all running tinc 1.1pre14. I'd like to upgrade to tinc 1.1pre15. Is there a suggested mechanism to do this while keeping the cluster up? For instance can I simply automate the installation of tinc 1.1pre15 on each node and reload the existing configuration using 'tinc reload' Will the temporary state of having a mix set of

Hi. I read that one feature of tink vpn solution is the Automatic Full Mesh Routing support that is defined as: "regardless of how you set up the tinc daemons to connect to each other, VPN traffic is always (if possible) sent directly to the destination, without going through intermediate" hops. What this means? I don't understand how this work. Can you please give me some

I admit that I am not familiar with Tinc very well but see that Tinc is running their current vpn connections. We have a scenario that has 20 different sites currently and successfully using tinc on openwrt but I am having issues adding an additional site as it will not communicate with the rest. I am not the one that originally setup the system but that person is no longer available. I have

Is there some information somewhere that explains just how exactly the ?full mesh routing? works? It seems to me that if Node B is supposed to be able to send stuff directly to Node C (instead of Node A), Node B needs to know where Node C is. Does this mean that each Node has to have a complete network map? This seems to become very unwieldy with larger deployments. How far does tinc reasonably