Project

General

Profile

Actions

Bug #7440

closed

Tinc package WEB GUI not picking up changes made on filesystem

Added by Stephen Walker-Weinshenker over 8 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
04/01/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

I have been setting up a tinc VPN using a pfsense firewall/router as one of the nodes and everything is working fine, except that manual changes to config or host files are not reflected properly on the page VPN>Tinc> Hosts. I wound up scping most of my existing host files directly to the box rather than configuring hosts through the web gui as I already had them available on another host.

However only the first and only host that I configured directly through the web gui shows up there, even though there are three host files in /usr/local/etc/tinc/hosts.

This is more of an annoyance than a bug but I figured I would bring it to the attention of the appropriate people.

Tinc version 1.0.29
Tinc package version 1.0.28_4
PFSense version: 2.3.3-Release-P1

Actions #1

Updated by Jim Pingle over 8 years ago

  • Status changed from New to Rejected
  • Affected Version deleted (2.3.3_1)
  • Affected Architecture added
  • Affected Architecture deleted (amd64)

That's not how it's meant to work. All settings must go into the GUI, and the filesystem contents are written out from the configuration made in the GUI.

Actions #2

Updated by Stephen Walker-Weinshenker over 8 years ago

I understand that this is not the approved way to do things, but now that I have done it, is there any way to get the hosts to show up properly? It seems silly that the Web GUI would not properly reflect changes made via ssh

Actions #3

Updated by Jim Pingle over 8 years ago

Put the settings in the GUI. That's how every part of pfSense works. Manual changes to files will always be overwritten by whatever is actually in the configuration made in the GUI.

The code in pfSense knows how to translate the settings from config.xml into the format that various daemons want. It doesn't go the other way.

Actions #4

Updated by Stephen Walker-Weinshenker over 8 years ago

Ok. Thank you. I can understand it would be difficult to write a parser for these config files, especially since they accept options in any order. I will try and duplicate the config files in the GUI and hopefully don't mess things up too badly.

Actions

Also available in: Atom PDF