staros on a private Ip network?

[Anonymous]

I have an internal network running on the private IP space 192.168.1.1-255 netmask 255.255.255.0 gateway 192.168.1.1 (to internet via nating to dynamic IP). We have a router box that nats from private to public IP at 192.168.1.1 and all other clients (wired and access points) plug through a 3Com Superstack II 1100 switch. Is it possible to set up a StarOS box so that it will be able to be plugged into a hub or switch on the local network and be accessable from wired and wireless clients alike? If so how would one do this?

We have tried setting up the StarOS box in AP mode with Wlan0=192.168.6.1 with the internal IP of 192.168.1.2 and our gateway to our internet backbone is 192.168.1.1 all on netmask 255.255.255.0. With this setup we seem to be able to ping everything (including wireless clients) from a wired station but only be able to hit 192.168.6.1 and 192.168.1.2 from a wireless one (IE...the StarOS boxes Wlan0 and Eth0).

If we try to ping from a wireless client, we can hit Wlan0 at 192.168.6.1 and the internal eth0 at 192.168.1.2 but nothing else on the network. All of the wired stations on our internal network are under the same IP space (IE...IP's=192.168.1.2-254 NM=255.255.255.0 GW=192.168.1.1)and have no problem hiting any wired or wireless client.

So, are we missing something that must have a route added? I thought that in the initial setup for AP mode with StarOS (as per the manuel), you setup the wireless adapter mode, setup the IP addresses, and in routing setup just the gateway (IE..no IP or netmask but just the gateway IP), and the system would automaticaly set the proper forwarding. Have we missed something or does StarOS not like private IP space? :?

[Anonymous]

Did you succeed in adding a route from the public IP interface to the 192.168.6.x (wireless) network in the FreeSCO box?

[Anonymous]

Yes, but it did not work. I even tried different subnets as well and no go. So now I have that box sitting off to the side and have a mikrotik box up and seem to be having the same problem. Makes me think that StarOS does not like Private non-routable IP's. Either that or I really am missing something right in front of my face. I even tried it through a Cisco 2600 siries router and no go. Guess I'll have to go dig my Cisco books out again and brush up on routing heh.

[Anonymous]

For clarification, this is what his network looks like:

internet
+
+
Cable modem <--
dhcp PUBLIC IP
+
+

FreeSCO router <- PC
192.168.1.1
+
+
Switch <-- connected: staros box, computers, other devices.
192.168.1.x <-- various clients all see internet
+
+
192.168.1.2 <-- ethernet nic
StarOS Box
Everything here cannot "see" the 'net.
192.168.6.1 <- PC card in AP mode
+
+
192.168.6.x < - Wireless clients.


My take: you can't route the 192.168.6.x IP's through the 192.168.1 network via the FreeSCO router box and StarOS box.

OR

There's just a route missing.

[tony]

In your setup, you will need a route on your FreeSCO.

For your FreeSCO router to be able to send a reply back to the StarOS AP clients, it will need a route for the subnet 192.168.6.0/24 that points to 192.168.1.2 as it's gateway.

If you cannot do this, you can always enable NAT on the StarOS box which will allow your associated clients to surf the net.

Thanks!

[Anonymous]

AKkk!!! I didn't even think about that heh!
Although I was able to add the route it still would not work so I set the Freesco box aside and now am working with a Mikrotik box. We shall see how well it adheers to the "standerd" route add commands.... :wink:

[tony]

Let me know how it works out.

Thanks!

[Anonymous]

Can you give an example of setting up the entire 192.168.6.0 subnet for nating to 192.168.1.1 (Freesco box)?

Also, how do you enable the script after you have written it and checked its syntax and saved it if the activate script is greyed out?

[Anonymous]

I sent an email explaining it in more detail. Can you please read it and get back to me on what to do? thanks.

[tony]

Can you give an example of setting up the entire 192.168.6.0 subnet for nating to 192.168.1.1 (Freesco box)?

Also, how do you enable the script after you have written it and checked its syntax and saved it if the activate script is greyed out?

The 'Activate Script' option is grey'd out because it has not been fully tested in this release yet, though it will be in the next release. For now, go to file->activate settings to apply your new script changes.

Thanks!

[tony]

I sent an email explaining it in more detail. Can you please read it and get back to me on what to do? thanks.

Thank you for the email. You should be back on track now.

Please let me know if you have any questions.

Thanks!