tony
06-30-2007, 10:30 AM
The BETA has been released, and is available on http://files.star-os.com/
While the change log is not complete at the moment, there are some changes listed on this thread http://forums.star-os.com/showthread.php?t=6714, and previous BETA postings (1.2.1b and newer)
Please do not upgrade your system unless you have access to it via the ethernet, in case you need to downgrade.
Please post your results as there are bound to be a few issues left to iron out before we remove the BETA status.
Changes since v1.2.3b build 2333
*) HotSpot / Captive Portal support is now available for all platforms excluding the WAR-1. (see HotSpot notes below)
*) IPs would sometimes linger around after a VDS interface was removed or disabled, specifically if the VDS was part of a bridge group.
*) IE country now support 5.8 frequencies 5.745 - 5.825
*) Improved support for AR5006XS chipsets while using Cloaking. Cards based on this chip include the WLM54AG / WLM54AG23.
*) Improved Cloaking support for 11g modes.
*) "802.11g only" mode no longer offers 802.11b / ERP protection (more robust)
*) "802.11g only" now uses pure OFDM rates. 802.11b CCK rates are now only offered in the 802.11b/g mode.
*) 6 and 9 OFDM rates can now be selected in the "802.11g only" mode.
*) 802.11g cloaking now offers the same improvements as the "802.11g only" mode listed above.
*) When specifying a specific rate, it is no longer a fixed rate but rather a MAX rate. When the signal threshold decreases, the rate will go lower to compensate, but will never increase beyond the rate specified. This feature greatly complements our new rate control, providing for a very robust network.
There are a few known incompatibilities and/or problems with this releases:
*) OLSR service does not restart on activate changes. (resolved for next release)
*) OLSR service may randomly quit. (resolved for next release)
Some operational differences include (mainly related to regulatory requirements):
*) Atheros channel and country code list no longer contains an 'All Channel' setting (## and #!).
*) U1 country code (US + FCC3) no longer contains the FCC3 channels, however country UZ can be used in it's place for systems that require them.
*) Due to the nature of our unique rate control, the rate specified is now a MAX rate, and not a FIXED rate.
For best operation, please ensure your client and AP use the same country code.
For those wanting to try the live upgrade feature via starutil, simply add the -a (apply) flag to the command line when uploading the firmware.
This requires that your system is using build 2321 or newer, and starutil 1.16.
HotSpot notes:
The HotSpot offered is vastly different from the version offered in V2.
To configure the HotSpot, there is a new 'hotspot' pull-down menu entry. The configuration script should be self explanitory.
The website users log into is now hosted on your own webserver, and not on the StarV3 box itself. We have offered a login webpage template on our files website, though any ChilliSpot login portal will work just as well.
While in the SSH interface, you can press ALT-H to view the on-line hotspot users. If there is a star (*) next to the IP address, that means the user has authenticated. The rest of the screen should be explanatory.
The hotspot user manipulation support via utilistar is also supported.
Sample HotSpot configuration steps:
Remove all IPs from wpci1 (this will be the AP the users log into)
Make sure your DNS server listed in "advanced->dns server list" is valid, as the hotspot service will require it.
Update RIP and OSPF (if used) to only advertise the Ethernet interface, as to not propagate the hotspot's private IP range.
Enter the HotSpot configuration script and enter the following commands:
hotspot enabled
interface wpci1
radius 1.2.3.4 <-- change to your radius server
radius_secret MySecret <-- change
login_server http://my-auth.server.com/ <-- change to the url where you installed the login script.
login_server_secret 5d8cp1fr9ua <-- change to match the one specified in your login script
dhcp_network 192.168.57.0/24
dhcp_dns 1.2.3.4 <-- change to your DNS server
Enter this in your NAT script: masq from 192.168.57.0/24 to dev ether1
Activate Changes, and you are done.If you use the default domain (hotspot.star-os.com), and default IP range of 192.168.57.0/24, then your customers can use the "exit" keyword in the Internet Explorer address bar to go to the logout page, if the popup window is closed. You can setup similar keywords for your own network if you do not use the default settings.
Notes regarding the Login script:
This is the web-based login prompt your HotSpot users will see when they try to access the Internet.
The system requirements needed for the Login script is a webserver and a stock install of PHP. (Perl login scripts are also available).
The only purpose of the login script is to collect a username and password from the user, and forward it back to the V3 hotspot system for authentication and can be hosted anywhere.
While the change log is not complete at the moment, there are some changes listed on this thread http://forums.star-os.com/showthread.php?t=6714, and previous BETA postings (1.2.1b and newer)
Please do not upgrade your system unless you have access to it via the ethernet, in case you need to downgrade.
Please post your results as there are bound to be a few issues left to iron out before we remove the BETA status.
Changes since v1.2.3b build 2333
*) HotSpot / Captive Portal support is now available for all platforms excluding the WAR-1. (see HotSpot notes below)
*) IPs would sometimes linger around after a VDS interface was removed or disabled, specifically if the VDS was part of a bridge group.
*) IE country now support 5.8 frequencies 5.745 - 5.825
*) Improved support for AR5006XS chipsets while using Cloaking. Cards based on this chip include the WLM54AG / WLM54AG23.
*) Improved Cloaking support for 11g modes.
*) "802.11g only" mode no longer offers 802.11b / ERP protection (more robust)
*) "802.11g only" now uses pure OFDM rates. 802.11b CCK rates are now only offered in the 802.11b/g mode.
*) 6 and 9 OFDM rates can now be selected in the "802.11g only" mode.
*) 802.11g cloaking now offers the same improvements as the "802.11g only" mode listed above.
*) When specifying a specific rate, it is no longer a fixed rate but rather a MAX rate. When the signal threshold decreases, the rate will go lower to compensate, but will never increase beyond the rate specified. This feature greatly complements our new rate control, providing for a very robust network.
There are a few known incompatibilities and/or problems with this releases:
*) OLSR service does not restart on activate changes. (resolved for next release)
*) OLSR service may randomly quit. (resolved for next release)
Some operational differences include (mainly related to regulatory requirements):
*) Atheros channel and country code list no longer contains an 'All Channel' setting (## and #!).
*) U1 country code (US + FCC3) no longer contains the FCC3 channels, however country UZ can be used in it's place for systems that require them.
*) Due to the nature of our unique rate control, the rate specified is now a MAX rate, and not a FIXED rate.
For best operation, please ensure your client and AP use the same country code.
For those wanting to try the live upgrade feature via starutil, simply add the -a (apply) flag to the command line when uploading the firmware.
This requires that your system is using build 2321 or newer, and starutil 1.16.
HotSpot notes:
The HotSpot offered is vastly different from the version offered in V2.
To configure the HotSpot, there is a new 'hotspot' pull-down menu entry. The configuration script should be self explanitory.
The website users log into is now hosted on your own webserver, and not on the StarV3 box itself. We have offered a login webpage template on our files website, though any ChilliSpot login portal will work just as well.
While in the SSH interface, you can press ALT-H to view the on-line hotspot users. If there is a star (*) next to the IP address, that means the user has authenticated. The rest of the screen should be explanatory.
The hotspot user manipulation support via utilistar is also supported.
Sample HotSpot configuration steps:
Remove all IPs from wpci1 (this will be the AP the users log into)
Make sure your DNS server listed in "advanced->dns server list" is valid, as the hotspot service will require it.
Update RIP and OSPF (if used) to only advertise the Ethernet interface, as to not propagate the hotspot's private IP range.
Enter the HotSpot configuration script and enter the following commands:
hotspot enabled
interface wpci1
radius 1.2.3.4 <-- change to your radius server
radius_secret MySecret <-- change
login_server http://my-auth.server.com/ <-- change to the url where you installed the login script.
login_server_secret 5d8cp1fr9ua <-- change to match the one specified in your login script
dhcp_network 192.168.57.0/24
dhcp_dns 1.2.3.4 <-- change to your DNS server
Enter this in your NAT script: masq from 192.168.57.0/24 to dev ether1
Activate Changes, and you are done.If you use the default domain (hotspot.star-os.com), and default IP range of 192.168.57.0/24, then your customers can use the "exit" keyword in the Internet Explorer address bar to go to the logout page, if the popup window is closed. You can setup similar keywords for your own network if you do not use the default settings.
Notes regarding the Login script:
This is the web-based login prompt your HotSpot users will see when they try to access the Internet.
The system requirements needed for the Login script is a webserver and a stock install of PHP. (Perl login scripts are also available).
The only purpose of the login script is to collect a username and password from the user, and forward it back to the V3 hotspot system for authentication and can be hosted anywhere.