Messages

The safest way is to only add the single line "system_hosts_generate();"  to 
/usr/local/www/services_dnsmasq.php 

Around line 108.

Apparently the hosts file is not regenerated after apply.
Should be fixed with commit : https://github.com/opnsense/core/commit/c30080e503a20fbd379800374d29ec679e72fea0 

Thanks for the additions, I've copied your lines into the wiki page.

Cheers,

Ad

Hi,

Thanks for reporting this issue, I've corrected the code to execute the standard rc script for this process. The following release should include the corrected version.
(checked into github : https://github.com/opnsense/core/commit/2e506e47b497548bad04067fe3625a34f79aaa7b )

Apparently the old command line parameters where there to set the logging to the (current) defaults. (warning / syslog)

Cheers,

Ad

Great!

My plan was indeed to isolate our language files from the base system, to prevent overlap with the standard layout.

For now it's absolutely fine to implement everything into [core]/src/share/locale/, as soon as you have something we can pull in I will move them around to the new location and make it work.

Cheers,

Ad

Hi .ike,

The Volt template stuff is work in progress, if you want to have an idea of where this is heading you can look at the Proxy code which is under development.
- [/usr/local/]opnsense/mvc/app/models/OPNsense/Proxy/
- [/usr/local/]opnsense/mvc/app/controllers/OPNsense/Proxy/
- [/usr/local/]opnsense/mvc/app/views/OPNsense/Proxy/

I will post some notes on our wiki pages on how to enable the new code in the current environment, some develop information is already there.

For the location of the new locale files for opnsense I would like to suggest the following base location:

/usr/local/opnsense/locale/


But if this location turns out to be less practical, I will refactor the code to make it work later on. If you have some translation files for me, I will alter the path settings in the current codebase to make sure you can start easily.

Cheers,

Ad

Hi .ike,

At the moment we don't have any other mechanisms in place for translation as there where in pfSense, but for the new components we're planning for a similar approach using language files (and hook it into a Volt template tag / supply some helpers for the ajax parts).
For the time being we've chosen to remove the language files, because we're not sure how complete they are and we're unable to validate the contents our selves.

I guess that the language support still works for most parts when the translation files are placed inside the correct directory (gettext seems quite standard), but if that doesn't work I can look into it for you. It's very nice to hear that you want a Japanese version, so when I can help just let me know.

When you have patches for the project,  just put a pull request on github and we'll place it in our standard release.  (as long as we may include them under the 2 clause bsd licence).

It's no problem to have a Japanese forum, I will open one for you right away.

Cheers,

Ad

Hi,

There seems to be a small issue with saving the page, which by accident switches of the forwarder when you try to restart it. This is probably an issue with the form fields.

The host overrides themselves seem to be connected to the "DHCP Registration" feature, when you enable that the hosts should be loaded as well.

Cheers,

Ad

Hi,

We try to keep as close to the ports collection as possible, the active version in there is 3.4.9, so we will probably use that one.
If it turns out to be problematic in terms of performance we might use an older version, but measuring the performance in a default scenario is certainly a good idea.

Cheers,

Ad

Hi,

We are planning to implement a proxyserver for the 15.7 release, which will probably be implemented with squid.
You might be able to use reverse proxy features from squid, but I don't know for sure if that totally fits your needs.


Regards,

Ad

The rules for the forum are essentially the same as for the mailing list:
    before you post a question:
        search the forum and mailing list archives – spend at least 5 minutes searching!
        read the FAQ

    if a thread already exists for the topic that you wish to discuss, use it – don't start a new one!
        use the forum search to find similar threads

    make sure you choose the proper board for your topic
    when posting , give all details that could be relevant to your problem (configuration, log messages, etc.)
    treat other forum members as you wish to be treated
        stay polite

    In case the issue or question is resolved, we kindly ask the author to mark his thread with "[SOLVED]" so other
    people have insights into the status of the request or issue.

Posts in the non-international section should be in English.