Setting up Amahi within a shared office network

[lou1z]

ummmmm......
without looking into it too much, your router 1 & 2 are on the same subnets
easiest solution would be to change the first routers subnet to something different eg 192.168.51.1/24

[moredruid]

correct, Amahi won't play nice on the other network as well
For your own range you can choose the ranges between 192.168.0 and 192.168.49 and again from 192.168.51 to 192.168.254
Or you can choose a completely different network on 10.0.0.x or 172.16.0.x

[Brimfulof]

Right, I think I've figured out what the problem is, but I need some help with the solution.

The HDA is telling the clients that the gateway is {router1}, rather than {router2}. How do I change the Gateway IP that is provided to clients by DHCP?

[Brimfulof]

Thanks Lou1z and moredruid, sorry I didn't see your responses before posting the comment above.

That makes sense about the subnets, should have thought of that, thanks. So, it's straightforward enough for me to change the settings on {router2}, but how do I change the settings in the {HDA} to tell it to provide the DHCP clients with the new info?

Thanks again for all your help with this.

[moredruid]

you'll need to create a new profile on the Amahi site IIRC

[Brimfulof]

OK, new problem.

I set {Router1} to 192.168.1.1 - as this is likely to be the setting of the router in the building
I set {Router2} to 192.168.50.1 - the original settings of {Router1} when I set up with Amahi

So now I can connect to the internet from both client and server, I can connect to http://hda/ from the client, but not from the server itself!

I can live with that I guess, but I'd like to understand why it's happening.

[Brimfulof]

OK, new problem.

I set {Router1} to 192.168.1.1 - as this is likely to be the setting of the router in the building
I set {Router2} to 192.168.50.1 - the original settings of {Router1} when I set up with Amahi

So now I can connect to the internet from both client and server, I can connect to http://hda/ from the client, but not from the server itself!

I can live with that I guess, but I'd like to understand why it's happening.

Ignore the above. I'm now in the new office and all is working well, probably just needed a full reboot.

Thanks for all your help.

[moredruid]

great to hear it works fine now