Page 1 of 1

[solved] WebGUI bind to LAGG

Posted: 06 Dec 2013 12:33
by spammeatwill
Hi,

I have setup the NAS4FREE box in a way that SAMBA is served through a link aggregation interface.
This interface happens to be in my main network, from which I need access to the WebGUI.
How can I bind the WebGUI on another interface?

Thanks!

Re: WebGUI bind to LAGG

Posted: 23 Dec 2013 16:17
by spammeatwill
Hi,

I still don't have a clue on how to do this. Maybe I am getting this wrong?

What I am trying to do is to have more link capacity for my SAMBA clients (main network) while having a dedicated storage/backup network:

Code: Select all

                                     +-------------------+
 main network   +----+-------+-------|re0+re1         em0|-------> to storage/backup network
                |    |       |       +-------------------+
             (C1) (C2) ... (Cn)
I figured that the LACP interface ports should be more usefull on the main network to distribute the load.

The problem is that LAN is on the em0... and I can't access management GUI from the main network.

Lighthttpd seems to bind only to em0 and in this case I need it to be on re0+re1 side.

Can this be done?

Re: WebGUI bind to LAGG

Posted: 23 Dec 2013 16:55
by spammeatwill
Well, I found a solution to this by editing the rc file for lighttpd... It is not an ideal solution, but at least it works.

Near the end, I have commented out the ipaddr variable and hardcoded 0.0.0.0 to bind on all interfaces:

Code: Select all

nasserver1: ~ # grep server.bind /etc/rc.d/lighttpd
server.bind = "0.0.0.0" #"${_ipaddr}"
Previously I tried to edit /var/etc/lighttpd.conf but soon realized that it is overwritten on every restart by the rc file above.

I would like to have a more permanent configurable solution for this.

Thanks.

Re: WebGUI bind to LAGG

Posted: 26 Dec 2013 12:37
by spammeatwill
Is there any way I could make this change permanent? Although it survives a lighttpd restart, it does not survive a reboot...

Edit:

It occurred to me that I could try and swap LAN and OPT1 interfaces, so that LAN is bound to lagg0 and OPT1 to em0. It works :)

Re: [solved] WebGUI bind to LAGG

Posted: 26 Dec 2013 22:26
by raulfg3
As you discover answer is to setup properly LAN and OPT1 in webgui.

http://wiki.nas4free.org/doku.php?id=do ... management


Webgui is allways bind to LAN.