Turris OS 3.9 is out with HaaS, Netmetr and PaKon

Dear Turris community

we just released Turris OS 3.9 and it contains a couple of cool new features and significant changes. If you decide to try the features out, please let us know how you like them:

  • Netmetr: the Netmetr project has been integrated into Foris as active bandwidth testing tool. To use the service just download the package “Internet connection speed measurement” an measure your bandwidth under the Updater tab in Foris. Out of technical reasons, we can measure speed only up to 200Mbps for now.
  • SSH Honeypot is migrating to HaaS (Honeypot as a Service). Statistics about attacks on your device have been moved to from Project Turris to project HaaS. To use the service, you need to register your e-mail, enable data collection and download the SSH Honeypot package in Foris. If you are already using our honeypots, you don’t need to register again and you can simply view the data about attacks on the HaaS project website when you sign in using your regular user name and password, which you used to sign into Project Turris. You can also register a different router than Turris according to the manual provided on the HaaS website.
  • PaKon: parental control/network monitoring is a new function, for now available as a CLI only preview.
  • Updater: moving and splitting configuration files. Files which have up to now been under /etc/updater/user.lua have been moved to /etc/updater/conf.d/user.lua
  • Foris: we made a few significant backend changes
  • Various package updates

Many greetings,

your Team Turris

2 Likes

Updated TO

##### Restart is needed #####
The system was updated, but some changes will take effect only after reboot. Please reboot the device.

The device will be restarted automatically on Thursday, December 14 at 03:30 AM.

##### News announcements #####
 • netmetr: active bandwidth testing tool
 • ssh-honeypot: migration to haas service
 • updater: moving and splitting configuration files
 • foris: big backend cleanup
 • pakon: parental control / network monitoring, CLI only preview
 • various package updates

##### Update notifications #####
The updater requests an autorisation of its planned actions. You can grant it in the Foris administrative interface.
 • Install adblock 1.3.3-1
 • Install luci-app-adblock git-17.212.24321-49c3edd-1

 • Installed version 8 of package userlists
 • Installed version 2015-08-19-b6618ffab8ed4981c57f53929276559698541462 of package procd-nand
 • Installed version 2015-05-29-f361bfa5fcb2daadf3b160583ce665024f8d108e of package libubus
 • Installed version 2015-05-29-f361bfa5fcb2daadf3b160583ce665024f8d108e of package ubusd
 • Installed version 2015-09-15-1 of package libblobmsg-json
 • Installed version 2015-05-29-f361bfa5fcb2daadf3b160583ce665024f8d108e of package ubus
 • Installed version 2015-09-15-1 of package libjson-script
 • Installed version 2015-08-19-b6618ffab8ed4981c57f53929276559698541462 of package procd
 • Installed version 2015-09-15-1 of package jshn
 • Installed version 188-r47055 of package base-files
 • Installed version 1.25.1-6 of package busybox
 • Installed version 4.4.103-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kernel
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-ipt
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-conntrack
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-nat
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-nathelper
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nls-base
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-core
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-uhci
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb3
 • Installed version 4.4.103+2017-01-31-4-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-cfg80211
 • Installed version 4.4.103+2017-01-31-4-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-mac80211
 • Installed version 4.4.103+2017-01-31-4-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ath
 • Installed version 4.4.103+2017-01-31-4-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ath10k
 • Installed version 4.4.103+2017-01-31-4-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ath9k-common
 • Installed version 4.4.103+2017-01-31-4-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ath9k
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-libphy
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-swconfig
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-switch-mvsw61xx
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-i2c-core
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-i2c-mv64xxx
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-serial
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-serial-wwan
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-serial-qualcomm
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-hwmon-core
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-thermal
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-thermal-armada
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-mmc
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-mvsdio
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-wdt-orion
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-default-on
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-gpio
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-heartbeat
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-morse
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-netdev
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ipt-core
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-netfilter
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-oneshot
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-timer
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-transient
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ledtrig-usbdev
 • Installed version 2.6.2-1 of package knot-libzscanner
 • Installed version 2.6.2-1 of package knot-libs
 • Installed version 1.5.0-3 of package knot-resolver
 • Installed version 1.6.7-0 of package libunbound
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ipt-nat
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ipt-conntrack
 • Installed version 1.6.1-1 of package libxtables
 • Installed version 1.6.1-1 of package libip6tc
 • Installed version 1.6.1-1 of package libip4tc
 • Installed version 2017-05-18 of package firewall
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-llc
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-stp
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-bridge
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ebtables
 • Installed version 1.3 of package switch-branch
 • Installed version 1.0.2m-1 of package openssl-util
 • Installed version 7.57.0-1 of package curl
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-lib-crc-ccitt
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-slhc
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ppp
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-pppox
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-pppoe
 • Installed version 60.0.3-1 of package updater-ng-localrepo
 • Installed version 60.0.3-1 of package updater-ng-opkg
 • Installed version 4.0.0-5 of package ip-full
 • Installed version 1.6.1-1 of package iptables
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-conntrack6
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-ipt6
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ip6tables
 • Installed version 1.6.1-1 of package ip6tables
 • Installed version 9.10.6-1 of package bind-libs
 • Installed version 9.10.6-1 of package bind-client
 • Installed version 9.10.6-1 of package bind-dig
 • Installed version 1.3-1 of package schnapps
 • Installed version 1.1.31-1 of package libxslt
 • Installed version 159-1 of package nuci
 • Installed version 159-1 of package nuci-nethist
 • Installed version 3.9 of package turris-version
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nfnetlink
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-conntrack-netlink
 • Installed version 1.4.45-6 of package lighttpd
 • Installed version 1.4.45-6 of package lighttpd-mod-setenv
 • Installed version 2015-05-29-f361bfa5fcb2daadf3b160583ce665024f8d108e of package libubus-lua
 • Installed version 1.4.45-6 of package lighttpd-mod-cgi
 • Installed version 1.4.45-6 of package lighttpd-mod-alias
 • Installed version 1.06-0 of package sshpass
 • Installed version 2 of package server-uplink
 • Installed version 1.10.0-1 of package python-six
 • Installed version 3200100-1 of package libsqlite3
 • Installed version 22.0.5-1 of package python-setuptools
 • Installed version 1.0.16-1 of package python-ipaddress
 • Installed version 2.1-1 of package python-idna
 • Installed version 1.1.2-1 of package python-enum34
 • Installed version 3.8-3 of package python-ply
 • Installed version 2.14-3 of package python-pycparser
 • Installed version 1.5.2-2 of package python-cffi
 • Installed version 1.3.1-1 of package python-cryptography
 • Installed version 16.0.0-1 of package python-pyopenssl
 • Installed version 0.0.8-1 of package python-pyasn1-modules
 • Installed version 15.2.0-1 of package python-attrs
 • Installed version 16.0.0-1 of package python-service-identity
 • Installed version 4.1.3-1 of package zope-interface
 • Installed version 16.0.0-1 of package twisted
 • Installed version 1.2-5 of package haas-proxy
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-tun
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-atm
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-pppoa
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-crypto-pcompress
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-crypto-hash
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-crypto-null
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-crypto-aead
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-crypto-manager
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-crypto-ecb
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-crypto-sha1
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-mppe
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-iptunnel
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-gre
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-iptunnel6
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ip6-tunnel
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-iptunnel4
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-sit
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-lib-textsearch
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-nathelper-extra
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-mii
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-net
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-net-cdc-ether
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-net-rndis
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-wdm
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-net-qmi-wwan
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-usb-serial-option
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nfnetlink-log
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ipt-nflog
 • Installed version 1.6.1-1 of package iptables-mod-nflog
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nfnetlink-nfacct
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ipt-ipset
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-nf-nat6
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ipt-nat6
 • Installed version 1.6.1-1 of package ip6tables-mod-nat
 • Installed version 4.4.103+1-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-ipt-tproxy
 • Installed version 1.6.1-1 of package iptables-mod-tproxy
 • Installed version 1.18-3 of package wget
 • Installed version 4.4.103+2016-12-19-70c8eb766d5afcf3cf187594b7cd776da92bee3c-1-1e4a549d177ab3da12b2052fba6a4dd5-1 of package kmod-sched-cake
 • Removed package mitmproxy
 • Removed package python-twisted
 • Removed package pyopenssl
 • Removed package foris-diagnostics-plugin
 • Removed package foris
 • Removed package python-beaker
 • Removed package python-ncclient
 • Removed package lighttpd-mod-fastcgi
 • Removed package lighttpd-mod-redirect
 • Removed package l10n_supported
 • Removed package sqm-scripts
 • Removed package kmod-ifb
 • Removed package iptables-mod-ipopt
 • Removed package kmod-ipt-ipopt
 • Removed package nuci-diagnostics
 • Removed package ip
 • Removed package turris-diagnostics
 • Removed package kmod-sched
 • Removed package iptables-mod-conntrack-extra
 • Removed package kmod-ipt-conntrack-extra
 • Removed package tc
 • Removed package kmod-sched-core
 • Removed package python-bottle-i18n
 • Removed package python-bottle
 • Removed package python-flup

but after update lighttpd seemed to be not working. /etc/init.d/lighttpd start worked, but when trying to access https://my.subdomain.tl:port/ I get a

Any suggestions on that?

edit: doing a restart lighttpd is again disabled, but a /etc/init.d/lighttpd enable did the job and now it’s enabled by default again.

edit2: looking into the list of removed packages it seems foris has been uninstalled. Why? How should I approve updates in future without foris? That seems weird…

What is in your’s updater configuration? I suspect that you are uninstalling something foris needs and because of that foris was just removed. Just send me an output of /usr/share/diagnostics/diagnostics.sh updater (you can get file by appending | tee updater.log and then you can send me that file).

Use https://my.subdomain.tl:port/ and you will be forwarded to https://my.subdomain.tl:port/foris/config/.

Simple configuration TO - SFSG - seems all OK :wink:

my user.lua contains a

Uninstall("lighttpd-https-cert", { priority = 60 })

Might this be the problem? As I do not want to use standard ports (port 443 and 80 are used by other servers) and don’t want my config to be massacred on any update you advised me to do so (in another thread quite some time ago).
But as foris worked pretty well in the past (it passed several updates without lighttpd-https-cert) I maybe wrong.

Unfortunately I do not have a folder ./diagnostics in /usr/share/ (looking into the removed package this comes not unexpected…) :frowning:
What about the other packages - which are removed by purpose and which unintentionally?

Yes, that’s it. As websocket servers for foris depends on it (probably because foris forces https access on websockets, but I am not sure. Colleague managing foris would know). Well in that case I don’t have probably solution for you. It seems to me that at the moment foris needs this package to ensure that you have lighttps running on port 443. But probably you can create your own package replacing this one.

Simplified what does it means is that you need that package and without it you have no foris and with that the router is so way out of base state that we won’t support it on software side.

That’s bad news - I cannot use 443 as this points to my homepage (which is else not accessible from company network). And in addition to that 443 needs in certain timewindows to be opened to let’s encrypt acme for certificate renewal.

Sorry, but that is not acceptable! Please solve that issue that has been created with this update! This will break several configurations - I don’t think I’m the only one using other webservers than TO’s lighttpd…

I will ask my colleague why this dependency is there. But wait you are hosting something directly on Turris lighttpd? Something that is in prod? Are you crazy? At least run another lighttpd instance. Don’t take me wrong, running website on Turris is completely fine but you are really doing it wrong. What I would do is that I would have my web server running in lxc or as another instance on router and then I would have firewall rules to nat specific ports to specific internal ports. This way you could swap ports from outside to inside with ease and I would do that specially if you have that lighttpd sticking to wan. Separation man separation…

No, I run my servers on a completely separate much more powerful machine :wink:

You’re right, that separation is possible - but hopefully not necessary (as it was not necessary in the past). I hope your colleague manages to sort out that issue.

After update I have a problem with local package.

inconsistent: Requested package meteo that is not available.

I tried to reinstall, but with no luck.
On the other hand, adblock installed in the same way works ok.
Both packages are in /usr/share/updater/localrepo/auto
Any hint?

In that case only explanation I see of your setup is that you are trying to use external ip and resolver for both wan and lan traffic. That is not good either. Common practice would be to setup nat from wan for given port and for lan having static hint in resolver to resolver your domain to your “more powerful machine”'s lan ip. This way you realy don’t have to move lighttpd at all. And it’s more versatile if you ever want to expand your setup.

I’ve noticed that the new version of the updater “rolls back” packages with a newer version to what is available in the feeds. Case in point: I build wireguard myself because the version in the repository is older, however this morning I noticed that it had been rolled back (I had it installed previously after the 3.9 update):

Installed version 0.0.20171017-1 of package wireguard

The one I built is 0.0.20171127-1. Is there a way to tell updater to ignore that? (if it’s not safe, I’ll just set up a cron job that updates the versions).

@Cabal, @einar, these seems to be a bug in localrepo probably. Can you please list what is in your localrepo using command localrepo list? Also can you please try to add that missing package to localrepo if it is missing from there using localrepo add file.ipk (where file.ipk is of course a path to your package).

1 Like

Local repo looks:

root@turris:~# localrepo list
auto:
  adblock: 3.0.3-1
  luci-app-adblock: git-17.302.29094-87ec343-1
  meteo: 0-1

But after adding ipk:

root@turris:~# localrepo list
auto:
  adblock: 3.0.3-1
  luci-app-adblock: git-17.302.29094-87ec343-1
  meteo: 0-1
user:
  meteo: 0-1

And now updater works!

I didn’t use “localrepo”, just a plain opkg install. I guess this is why it did not work. Thanks for the tip on localrepo, will do that!

FTR, this is how it looks after adding all that I needed:

auto:
  adblock: 3.1.0-1
  luci-app-adblock: git-17.309.31241-676ce11-1
  wireguard: 0.0.20171127-1
  kmod-wireguard: 4.4.103+0.0.20171127-1-1e4a549d177ab3da12b2052fba6a4dd5-1
  wireguard-tools: 0.0.20171127-1
user:
  adblock: 3.1.0-1
  luci-app-adblock: git-17.309.31241-676ce11-1
  wireguard: 0.0.20171127-1
  kmod-wireguard: 4.4.103+0.0.20171127-1-1e4a549d177ab3da12b2052fba6a4dd5-1
  wireguard-tools: 0.0.20171127-1

I’ll report back in case they are rolled back.

opkg is wrapper script that is using localrepo in background. There is a bug in localrepo that is causing repository auto to not be added to updater configuration. Fix should be in 3.9.1.

@cabal and @einar thank you with helping me to found out where is a problem.

Thanks, i have the same problem. Every time updater runs in the background it pushes the old (not working) adblock packages over the manually installed ones. I hope for a quick release of 3.9.1 =)

Just to state another problem: 5 GHz wireless went away after update to 3.9 :frowning: Fortunately reboot helped (hint from forum), but I’m in doubt what will happen next time.

1 Like

Is there anyway we can submit our additions to /usr/share/pakon-light/domains_replace/ to be included with the official domains_replace file?