Step by step - HOW TO SETUP V2 AP

[rafamous]

#OK. I'm putting up a new pop and would like to do it right.

#This is simply a StarOS box with a wireless card and an omni.

#Would someone please check my work here.

#Using as much of the default settings in StarOS as I can.

#I have a public IP connection to the internet of 204.2XX.XX.33

#Login using putty you can download it here. Get putty.exe.
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Grab a crossover cable and plug from your computer to the staros board.
If you don't have a crossover put a hub/switch in bewteen.
Set your computer to the IP of 192.168.1.2
Open putty
In the box where it says hostname/IP type 192.168.1.1
click open
user name:admin
password:1234

# Add the default gateway
Click on routing
click on static routes
edit/change the default route to 204.2XX.XX.33
click make default route and click ok
close the popup by clicking on the little green dot in the upper left of the popup.

# To avoid a conflict with your customers gateway we will edit this default setting.
Click on Interfaces
Click on ether1 (or wherever I am connecting to the outside internet to)
Click on IP assignments
double click on 192.168.1.1
change 192.168.1.1 to 192.168.1.2
OK and close the popup.

# Input the gateway for your customers
Click on interfaces
click on wlan1 (or wherever I put my wireless card to use for my Access Point)
Click on IP assignments
Click on create
Enter the IP of 192.168.1.1
OK and close the popup.

# Since all the default dhcp setting are what we are using we will just activate the dhcp server so it will hand out dhcp addresses.

# We want dhcp to run on every boot.
Click services
click dhcp server
click bootup settings
click load service on boot
click OK

# Activate the dhcp service
Click services
click dhcp server
click service activation
click start
click the little green dot on the upper left of the popup to close the popup.

# Now we will add our masq statement so the private IP's will make it through our public IP.
Click on advanced
click on scripts
click on nat and static nat
uncomment client = "ether1"
uncomment masq statement and change to - masq from 192.168.0.0/24 to dev $client

# now save and activate everything
click on advanced
click on scripts
click on activate scripts changes
click on file
click on activate changes
click on yes


Now this is as basic as you can get and it's probably full of mistakes. Please post with corrections and I will edit this until it is right. This will help me and any newbie get their new StarOS AP up and running.

[lonnie]

Thank you. What is your License Keys account username?

[rafamous]

Thank you. What is your License Keys account username?

Right on! Thanks Lonnie. Awesome!
If I knew how to do more I would. I'm hoping some of the advanced students might get in.

It takes some time but it's what's needed.

Thanks again.

[i20access]

#OK. I'm putting up a new pop and would like to do it right.

#This is simply a StarOS box with a wireless card and an omni.

#Would someone please check my work here.

#Using as much of the default settings in StarOS as I can.

#I have a public IP connection to the internet of 204.2XX.XX.33

#Login using putty you can download it here. Get putty.exe.
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Grab a crossover cable and plug from your computer to the staros board.
If you don't have a crossover put a hub/switch in bewteen.
Set your computer to the IP of 192.168.1.2
Open putty
In the box where it says hostname/IP type 192.168.1.1
click open
user name:admin
password:1234

*** I would suggest changing your password by doing:
click system
click change password
****

# Add the default gateway
Click on routing
click on static routes
edit/change the default route to 204.2XX.XX.33
click make default route and click ok
close the popup by clicking on the little green dot in the upper left of the popup.

# To avoid a conflict with your customers gateway we will edit this default setting.
Click on Interfaces
Click on ether1 (or wherever I am connecting to the outside internet to)
Click on IP assignments
double click on 192.168.1.1
change 192.168.1.1 to 192.168.1.2
*********************************************
I would think that the ip of ether1 needs to be in the same subnet as your default router. (i.e. 204.2XX.XX.34)
*********************************************

OK and close the popup.


# Input the gateway for your customers
Click on interfaces
click on wlan1 (or wherever I put my wireless card to use for my Access Point)
Click on IP assignments
Click on create
Enter the IP of 192.168.1.1
OK and close the popup.

# Since all the default dhcp setting are what we are using we will just activate the dhcp server so it will hand out dhcp addresses.

# We want dhcp to run on every boot.
Click services
click dhcp server
click bootup settings
click load service on boot
click OK

# Activate the dhcp service
Click services
click dhcp server
click service activation
click start
click the little green dot on the upper left of the popup to close the popup.

*********************************************
The above sets the default dns cache server to 192.168.1.1, so you would want to enable the dns server in star-os, this is done as follows:

click services
click dns server
click bootup settings
click load service on boot
click OK

As an alternative to using the ISC dhcp server under the services tab, one could do the following:

click on interfaces
click on wlan1 (or the interface you would like to hand out addresses to clients on)
click on dhcp auto-auth configuration
click on configuration
edit/change the default gateway to 192.168.1.1
leave the subnet mask as is
change the primary dns to 192.168.1.1
change the secondary dns to another caching dns server that you may have, or set it to 192.168.1.1 if you don't have another one available.
leave the lease duration as is, or change it to a longer time if you desire (this value is in seconds)
uncheck the "use radius" and "create hotspot session" boxes if you are not using them
change/edit the ip address range to begin at 192.168.1.2 and end at 192.168.1.254

# Activate the dhcp-auto auth service
click on interfaces
click on wlan1 (or the interface you would like to hand out addresses to clients on)
click interface features
click enable dhcp auto-auth

*********************************************

# Now we will add our masq statement so the private IP's will make it through our public IP.
Click on advanced
click on scripts
click on nat and static nat
uncomment client = "ether1"
uncomment masq statement and change to - masq from 192.168.0.0/24 to dev $client
*********************************************
Shouldn't this read "masq from 192.168.1.0/24 to dev $client" ?
*********************************************

# now save and activate everything
click on advanced
click on scripts
click on activate scripts changes
click on file
click on activate changes
click on yes


Now this is as basic as you can get and it's probably full of mistakes. Please post with corrections and I will edit this until it is right. This will help me and any newbie get their new StarOS AP up and running.

[rafamous]

Thanks for the corrections. Now I can go put this into action. Looking forward to seeing this working. I will give a report.

[rafamous]

The above script, with the corrections, is working beautifully.

So here is a working "How to - set up a basic AP with one public handing out dhcp".

oooh how sweet it is....

[jtellez]

hi guys,

I just got a Netkrom prewimax that comes with the StarOS... and almost no manual

I read a post in this forum for a fast deployment and didnt work for me

My scenario
ISP: - ADSL ISP w/2wire (wireless) modem/router in bridge mode, PPoE session is made by Linksys Router RV016 with IP 192.168.1.1, the StarOS IP has move from default 192.168.1.1 to 192.168.1.2

when I go to:

# Add the default gateway
Click on routing
click on static routes
edit/change the default route to 204.2XX.XX.33

...and want to declare 192.168.1.1 (the IP of the router conected to the ISP) in network adress it goes back to 0.0.0.0
I allready changed the AP adress to 192.168.1.2 and also tried by
intefases>ether1>interfase features>enable dchp client

so i tried static IP (192.168.1.2) and dinamic and nothing... AP client does not get IP

please help! harware supplier is not giving me enough manual...

[lonnie]

The default route is the device you connect with (192.168.1.1).

You have to configure dhcp and you will require a masq statement in order to handle the AP subnet.

[go.fast]

hi guys,

I just got a Netkrom prewimax that comes with the StarOS... and almost no manual



What is netkrom prewimax.

Is this something the star is working on?
what country are you i and what frequencies.

Thanks

George

[tony]

I would suspect it's this unit. Doesn't look that bad.
http://www.netkrom.com/prod_pre-wimax_multiband_radio.html

[go.fast]

Ok, so I checked it out.

Hmmm, I looked at their user manual.

Where does the "pre" wimax come into play?

Are they saying that atheros cm9's are prewimax and a software upgrade will make it wimax?

Or is it just marketing?

Where are you guys at concerning wimax?
As I understand it, there is no 5gig unlicensed wimax on the drawing boards yet, or at least being discussed at the interoperable phase by multiple manufacturers.

George

[lonnie]

We can achieve all of our objectives with Atheros cards "right now"TM. When WiMax is commercailly viable and we can get access to a software development kit that supports cards that are available in quantity, we will add them to our offering. Until then we have many projects to get ready that need a real solution that we can provide with the current state of the art for radios.

[go.fast]

Ok, I figured the the "PRE" Wimax was a marketing phrase.

I just wanted to hear it from you, seeing it's a star based system.

Thanks

George

[rafamous]

Does anyone have a tip on how to make the clients who obtain an IP via DHCP pingable at least from within the StarOS v2 AP?

Thanks.