Hi,
I've read that its recommended to run amahi as the DHCP server instead of the router. However I was wondering what part of amahi (or apps?) actually requires this?
I've just switched my router back to being the DHCP server, and as far as i can see i still have access to my Amahi dashboard, still can navigate to my shares in windows explorer, my laptop still backs up to the \\backups share... so was wanting to know why i should make the hda the dhcp server, instead of the router?
cheers
v
DHCP server
Re: DHCP server
What are you using for your internal Amahi domain name?
Whatever it is, this has to be your default domain for your browser to append to http://hda. You CAN do this with your router's DHCP.
How are you accessing your Amahi shares? What are you using for your SAMBA domain? This is information passed to the client via DHCP, but direct access can get you there without it.
Basically, Amahi's DHCP makes some things easier for the clients. If Amahi ever evolves to a Win2000 style domain controller, then the dynamic DNS/DHCP functions it performs will be mandatory. It's current PDC function does not require this. If we add WINS support in Amahi 5 or 6, and you are supporting multiple subnets, you will need smarter DHCP, but then you are getting into SMB environment, not home or SOHO.
Whatever it is, this has to be your default domain for your browser to append to http://hda. You CAN do this with your router's DHCP.
How are you accessing your Amahi shares? What are you using for your SAMBA domain? This is information passed to the client via DHCP, but direct access can get you there without it.
Basically, Amahi's DHCP makes some things easier for the clients. If Amahi ever evolves to a Win2000 style domain controller, then the dynamic DNS/DHCP functions it performs will be mandatory. It's current PDC function does not require this. If we add WINS support in Amahi 5 or 6, and you are supporting multiple subnets, you will need smarter DHCP, but then you are getting into SMB environment, not home or SOHO.
Re: DHCP server
it's not required. here are the tradeoffs: http://www.amahi.org/faq#is-dhcp-server-requiredHi,
I've read that its recommended to run amahi as the DHCP server instead of the router. However I was wondering what part of amahi (or apps?) actually requires this?
I've just switched my router back to being the DHCP server, and as far as i can see i still have access to my Amahi dashboard, still can navigate to my shares in windows explorer, my laptop still backs up to the \\backups share... so was wanting to know why i should make the hda the dhcp server, instead of the router?
cheers
v
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: DHCP server
Hmm, what is involved in this? Do you know?If Amahi ever evolves to a Win2000 style domain controller, then the dynamic DNS/DHCP functions it performs will be mandatory. It's current PDC function does not require this. If we add WINS support in Amahi 5 or 6, and you are supporting multiple subnets, you will need smarter DHCP, but then you are getting into SMB environment, not home or SOHO.
Someone mentioned that DHCP changes are needed for wider PDC support, but it's not clear what is needed.
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 8GB RAM, 1TBx2+3TBx1
Re: DHCP server
I know **SOME** of it. We will pick this up on the developers forum. Part of step 2...Hmm, what is involved in this? Do you know?If Amahi ever evolves to a Win2000 style domain controller, then the dynamic DNS/DHCP functions it performs will be mandatory. It's current PDC function does not require this. If we add WINS support in Amahi 5 or 6, and you are supporting multiple subnets, you will need smarter DHCP, but then you are getting into SMB environment, not home or SOHO.
Someone mentioned that DHCP changes are needed for wider PDC support, but it's not clear what is needed.
Who is online
Users browsing this forum: No registered users and 10 guests