CLOSED: Wireless in the network

[miksnake]

This doesn't seem like it should be a problem, but I just want to confirm before I make the leap to Amahi.

I've read that the Amahi server must be hardwired to work and does not support wireless. So, the way my configuration would work is as follows:

internet connection from ISP --> internet cable modem --> wireless router

I assume the Amahi server will be hard wired into the wireless router. All the other devices in the network connect wirelessly and they should all be able to see the Amahi server, have files, movies, music, etc. streamed to them wirelessly, etc.

That is correct, right?

Thanks.

[bigfoot65]

That is correct.

We just want to ensure that users understand that the Amahi server has to be hardwired. Wireless connectivity will still be supported via the router, but the DHCP lease and DNS will be handed out by the Amahi server.

[pucciclaudio]

it is not clear to me then how the dhcp and dns are handled by amahi

The amahi wiki, in the "Transitioning to using your Amahi server" section says to shut down the router dhcp, which I am not sure is a good advice because it will disconnect all the other devices int he house.

For instance, the server should be up and running (Fedora 21) but the amahi control panel on amaze.org/users still reports "waiting install". I can access the dashboard though (at 192.168.0.10).

The transitioning part is very obscure, where can I find more info?

[bigfoot65]

it is not clear to me then how the dhcp and dns are handled by amahi

Good point about this part. Those that have a basic knowledge of networking understand, but for those who this is new territory it's often baffling. Obviously we have not done our job explaining it. We will have to work on it.

says to shut down the router dhcp, which I am not sure is a good advice because it will disconnect all the other devices int he house.

When using Amahi for your DHCP and DNS server, all clients will get their DHCP lease from it. Currently the router does that piece, but once you disable it and let Amahi take over that role the clients just need to have their DHCP lease renewed.

the amahi control panel on amaze.org/users still reports "waiting install". I can access the dashboard though (at 192.168.0.10).

This may take a while for things to catch up. The status on amahi.org will not prevent you from using the server. It just means that it has not made the connection with your network. It will in time, so give it a bit.

[pucciclaudio]

Thanks for understanding.

RE the DHCP lease renew, does it work on android devices? Doesn't look like, it keeps saying "obtaining IP address" then "Saved" then back to "obtaining IP address" ...

[bigfoot65]

No problem.

For Android devices, you typically have to forget the wireless network, the select it again and should link up.

We are working on making the wiki guidance for Amahi 8 more intuitive for users. It's going to take some time, but getting there.

Is this Setup useful? Plan to go more in depth, but it's a start.

[pucciclaudio]

Thanks, forgetting the network and selecting again actually works.

I think it would be very useful to distinguish these various transition modalities from router to amaze DHCP in the wiki.

The webpage you linked looks useful. Only one point, http://hda does not work immediately after the install, maybe need to wait until the dashboard catches up. However, using the IP address of the server does work right away.

Best,
Ferdinando

[bigfoot65]

Feel free to add items to the wiki. Maybe we can come up with a tips page or something.

As for the access to the dashboard, we cover both scenarios in the transitioning to using your Amahi server wiki guidance. That should be sufficient.