Amahi Forums

Hi all,

First of all, I use amahi from some weeks and it provide a real nice and easy to use "out of box" home sever. Many Thanks to all the team.
I don't know if this post has to be classified as an networking issue or as a suggestion.

My trouble is: I have got 2 seperated ip subnetwork: once for my wifi PCs and a second for my wire connected PCs.
It is not one subnet divided in 2 different ranges.
Both of theses subnet are connected to my firewall which provide DHCP and relay DNS to my provider and my HDA box.
My firewall allows connections in both way between both LAN.
My HDA box is on the wire connected LAN and all is working fine for this sub net (the DHCP server is turnned off) all of my boxes are able to connect normally.
But for the other LAN, I am unable to connect to the HDA web interface (except if I use the real ip instead of the named URL and of courses no webapps are working)

I found the root cause : the bind server is not set to allow my second LAN. The pragma "acl trusted" doesnt include my second LAN (just the tunnel LAN and the LAN my HDA belong to)
I tried to stop monit and bind, modify my named.conf and restart the services==> all was working in the way I want: both LAN are able to deal whith my HDA.

My trouble is that the named.conf is dynamically generated by the hdactl main script.

So I had a look to the hdactl script and found that the script is looking in the database to find which net has to be set in the named.conf file.

So my question is:
Is there a way to set 2 different net in this named.conf file.(I can try to modify the value in the "settings" table and add a second value but I m not sur it will work or If it is I m afraid of side effects)

Or is there a more convenient way to add this second net (an HDACTL_OPTIONS ?)
For the moment I use my workaround script which modify my "named.conf" file after the boot, but it is not the right way

Thanks in advance for your answers and suggestions

hi!

sorry for the late response to your message.

yes, we added this to enable DNS resolution to other networks, like VPN.

you are correct, it would be great if we could support with options in /etc/sysconfig/hdactl.

do you feel like you could submit a patch?
this seems fairly easy, but this feature does not get use by 99% of our users, and we have a lot of other requests.

the idea would be to add a variable SUPPORTED_LANS=<YOURLAN> in /etc/sysconfig/hdactl and then read that in hdactl.

in any case, please do file a feature request (under platform -> new issue -> feature)!

Hi Thanks for your reply,

I agree, for the moment, not a lot of people may use this feature.
It stay usefull for security purpose

For the patch, I will take some time to work on, and thanks for the link to the tracker.

Hope to be quickly able to provide this.

(waiting this improvement, this thread can now be closed)