Amahi Forums

What are the real hazards of permanently re-enableing Network Manager?

Is this possible?

I must admit, I am really only interested in Amahi as a front end for Samba/Greyhole, the fact that it tries to take over every aspect of my network is just a major annoyance for my setup, since I have DD-WRT on my router and it is alot more capable as a network manager (Why re-invent the wheel?)

By having it not use Network Manager + Static DHCP from my router, the server doesn't show up in local DNS lists and causes problems with finding the server at random intervals on my setup. It also causes problems with using the box as a VM host. Manually re-enableing the NetMan service and handing back the NIC to it through gnome configs, all this goes away, until I reboot the system. Some config somewhere restores it back the way that it was

I also must admit, I am a windows veteran/linux rookie and not completly familiar with.

Am I completely missing something?

I am not sure what the repercussions could be, but I tried it once. I was having strange issues and decided it was not worth changing from the default Amahi setup.

I believe there is also some guidance in the wiki regarding DD-WRT. There is also a router control option in Amahi that may include that as well.

Now, the situation you mention with VMs can be easily corrected if I understand it correctly. See the Reconfiguring the System section in the wik here:

http://wiki.amahi.org/index.php/Amahi_on_VirtualBox

I use VMs all the time and with this in place, have no issues. I access my server from VM, Windows 7, Vista, and XP clients. I have also been able to use hdaconnect and VPN into the network with no problems.

Hope this helps. If you choose to experiment, let us know how it goes. It is your server, so you can do anything you want. Keep in mind however when you modify these sorts of settings and it breaks the HDA, support may not be available.