Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: jimgoode on August 02, 2006, 05:07:02 PM

Title: Adding a Route
Post by: jimgoode on August 02, 2006, 05:07:02 PM

I am running SME with 2 NICS. My original local network is 192.168.0.0. I added a wireless router to my physical network which defaults to 192.168.1.0 and which is administered from a PC with 2 NICS.

The wireless router can ping the SME server and systems on both networks. The server, however, can't ping anything that isn't on the original network.

How do I add a route on the SME so that it can see the new network?

TIA,
Jim

Title: Adding a Route
Post by: gelcube on August 02, 2006, 05:22:22 PM

You should be able to change the IP address of the wireless router to match that of your LAN.  You can try to add the 192.168.1.0 network into the Local Networks panel in the server manager, but I'm not sure that'll work correctly.  You can try it, though.

Title: Re: Adding a Route
Post by: CharlieBrady on August 02, 2006, 05:33:47 PM

Quote from: "jimgoode"

How do I add a route on the SME so that it can see the new network?

localnetworks panel.

Title: Adding a Route
Post by: jimgoode on August 02, 2006, 05:57:48 PM

My biggest confusion is that the SME server does not see the router. Therefore, adding a local network does not work. I will try forcing the router to be a part of my original network.

Title: Adding a Route
Post by: gelcube on August 02, 2006, 06:13:17 PM

I think that would be the least complicated solution.

Title: Adding a Route
Post by: CharlieBrady on August 02, 2006, 08:06:49 PM

Quote from: "jimgoode"

My biggest confusion is that the SME server does not see the router.

What do you mean by "does not see"?

Quote

Therefore, adding a local network does not work.

Again, please define "does not work".

What you need is for the router's "WAN" address to be on the SME server's local network. Add the router's local network as an additional local network, using the router's "WAN" address as the router to that network. Done.

> The server, however, can't ping anything that isn't on the original network.

This will be because the "router" is operating as  a firewall, using NAT. If you can configure it as a pure router, ping will be able to traverse the router from WAN port to LAN.

Be sure to lock down wireless access to your router, otherwise passers by will be able to do evil things, such as send spam via your server.