Amahi is not a Gateway?
Posted: Thu Aug 06, 2009 11:30 pm
I have been playing around with Amahi for a little bit and I'm in the process of reinstalling with the new version, but in the research over the last few weeks I've come to the conclusion that Amahi IS NOT a gateway as such.
I was having trouble getting the network computers to access the net once I switched to Amahi.
The way I setup everything, was:
the Amahi server computer was connected to the net via its Lan1 adapter card,
Lan2 Card was connected to an 8 port switch,
this was connected to the Wireless router, and the other 3 network computers I currently have!
Basically instead of sharing the router/Modem I disconnected the switch from that, and only left Amahi connected then connected the switch to the second Lan card. (I disabled the DNS etc from the modem router etc.)
Whenever I did this I lost internet connection for all computers, except the Amahi server system.
I could access Amahi, and local computers, but not the big wide world.
When looking at your connection diagram for the 50th time it finally twigged that all computers on the network are still connected directly to the internet via the "Home Router", the main Modem/Router/Wireless connection.
Previously using Centos I've set it up so the server is the only connection to the outside world. This is where the confusion sets in because I can't see how the system protects or isolates the LAN from the WAN etc.
This means that the AMAHI server doesn't HAVE to be on all the time for the rest of the network to have internet access, or talk to each other; BUT will need to be on to access ITS features.
Am I missing something or just confusing myself.
I'm new to Linux networking but have setup a couple of basic gateway servers using IPTables etc using Centos, and Ubuntu server, but this setup is different
, still looks like a good system, but DIFFERENT!
Is it possible to configure this as gateway server and still maintain the Amahi features. ?
When I've tried in the past I've lost access etc, generally when configering IP ranges (I think!)
I generally use 192.168.0.xxx for internal (ie Client PCs, printers etc.) and 192.168.1.xxx for external (ie Modem Router, Server etc)
I was having trouble getting the network computers to access the net once I switched to Amahi.
The way I setup everything, was:
the Amahi server computer was connected to the net via its Lan1 adapter card,
Lan2 Card was connected to an 8 port switch,
this was connected to the Wireless router, and the other 3 network computers I currently have!
Basically instead of sharing the router/Modem I disconnected the switch from that, and only left Amahi connected then connected the switch to the second Lan card. (I disabled the DNS etc from the modem router etc.)
Whenever I did this I lost internet connection for all computers, except the Amahi server system.
I could access Amahi, and local computers, but not the big wide world.
When looking at your connection diagram for the 50th time it finally twigged that all computers on the network are still connected directly to the internet via the "Home Router", the main Modem/Router/Wireless connection.
Previously using Centos I've set it up so the server is the only connection to the outside world. This is where the confusion sets in because I can't see how the system protects or isolates the LAN from the WAN etc.
This means that the AMAHI server doesn't HAVE to be on all the time for the rest of the network to have internet access, or talk to each other; BUT will need to be on to access ITS features.
Am I missing something or just confusing myself.
I'm new to Linux networking but have setup a couple of basic gateway servers using IPTables etc using Centos, and Ubuntu server, but this setup is different

Is it possible to configure this as gateway server and still maintain the Amahi features. ?
When I've tried in the past I've lost access etc, generally when configering IP ranges (I think!)
I generally use 192.168.0.xxx for internal (ie Client PCs, printers etc.) and 192.168.1.xxx for external (ie Modem Router, Server etc)