PDA

View Full Version : StarOS v1.13.3b10-3928 ready for testing


tony
12-12-2003, 10:19 PM
Changes between v1.13.3b9 and v1.13.3b10:
New: Hotspot update, which includes splash page support (enable in the hotspot menu). When enabled, end-users must view, and click a continue button on the splash page before gaining access to the network. This feature is available for Hotspot (web and auto-auth logins) as well as pptp and pppoe logins. The splash page (splash.htm) is can be edited via the hotspot menu.
Update: Radius Fallback CBQ attributes are now operational, and supported in pptp, pppoe and Hotspot logins.
Update: Atheros wireless updates.

To enable Atheros support, you can purchase an Atheros-enabled key from your reseller, or online via www.license-keys.com. All Server keys include the Atheros license. Do not generate a key that is locked to an Atheros card, as the key itself determines if the Atheros support is activated.

Atheros cards tested: D-Link DWL-AB520, DWL-AG520, DWL-G520, Proxim 8482-WD
To date, all Atheros-based cards tested by users have been supported in the later releases. Please let us know if your specific card is note being detected, or does not operate correctly.

OEM releases for this version are available.

Any and all comments are welcome.

DESKTOP SYSTEMS
Desktop Server Edition:
no iso for this edition
http://www.star-os.com/downloads/oem-vnc/strs-1.13.3b10-3928.bin
http://www.star-os.com/downloads/oem-vnc/strs-1.13.3b10-3928.raw

Desktop Router Edition:
http://www.star-os.com/downloads/oem-vnc/strr-1.13.3b10-3928.iso
http://www.star-os.com/downloads/oem-vnc/strr-1.13.3b10-3928.bin
http://www.star-os.com/downloads/oem-vnc/strr-1.13.3b10-3928.raw

SPECIAL PURPOSE SYSTEMS
Soekris & MODO Router Edition:
http://www.star-os.com/downloads/oem-vnc/strrs-1.13.3b10-3928.iso
http://www.star-os.com/downloads/oem-vnc/strrs-1.13.3b10-3928.bin
http://www.star-os.com/downloads/oem-vnc/strrs-1.13.3b10-3928.raw

WRAP Router Edition:
http://www.star-os.com/downloads/oem-vnc/strrw-1.13.3b10-3928.iso
http://www.star-os.com/downloads/oem-vnc/strrw-1.13.3b10-3928.bin
http://www.star-os.com/downloads/oem-vnc/strrw-1.13.3b10-3928.raw

Routerboard Router Edition:
http://www.star-os.com/downloads/oem-vnc/strrb-1.13.3b10-3928.iso
http://www.star-os.com/downloads/oem-vnc/strrb-1.13.3b10-3928.bin
http://www.star-os.com/downloads/oem-vnc/strrb-1.13.3b10-3928.raw

CPE SYSTEMS
SBC CPE Edition:
http://www.star-os.com/downloads/oem-vnc/cpe-1.13.3b10-3928.iso
http://www.star-os.com/downloads/oem-vnc/cpe-1.13.3b10-3928.bin
http://www.star-os.com/downloads/oem-vnc/cpe-1.13.3b10-3928.raw

Desktop CPE Edition:
http://www.star-os.com/downloads/oem-vnc/cpev-1.13.3b10-3928.iso
http://www.star-os.com/downloads/oem-vnc/cpev-1.13.3b10-3928.bin
http://www.star-os.com/downloads/oem-vnc/cpev-1.13.3b10-3928.raw

rasimoes
12-13-2003, 06:39 AM
Thank you for the CBQ Fallback feature... This will be very useful for me!

szern
12-13-2003, 08:37 AM
Changes between v1.13.3b9 and v1.13.3b10:
Update: Radius Fallback CBQ attributes are now operational, and supported in pptp, pppoe and Hotspot logins.
Can you please provide the new syntax for entering the 'Radius Fallback CBQ attributes?

Thanks!

georgew
12-13-2003, 08:46 AM
In the dictionary file I see:
# Rates to give PPPoE customers, can be used in Authentication replies. (in bits/s)
ATTRIBUTE VNC-PPPoE-CBQ-RX 1 integer
ATTRIBUTE VNC-PPPoE-CBQ-TX 2 integer

# Fallback support for each direction. (1 / 0)
ATTRIBUTE VNC-PPPoE-CBQ-RX-Fallback 3 integer
ATTRIBUTE VNC-PPPoE-CBQ-TX-Fallback 4 integer



And in the example user file I see:
# VNC-PPPoE-CBQ-TX = 64000,
# VNC-PPPoE-CBQ-RX = 115000



So I would guess:
...
VNC-PPPoE-CBQ-TX = 64000,
VNC-PPPoE-CBQ-RX = 115000,
VNC-PPPoE-CBQ-TX-Fallback = 1,
VNC-PPPoE-CBQ-RX-Fallback = 1

lonnie
12-13-2003, 08:50 AM
George, you are a super sleuth. Thanks.

szern
12-13-2003, 08:55 AM
*BAAAAaaaaa* I feel sheepish!
I looked in the 'radusers.txt' but it never occurred to me to look in the 'dictionary.vnc' file.

Thanks georgew :)

georgew
12-13-2003, 09:04 AM
Just FYI... Any time you get a product that says it supports radius, the first question in your mind should be "what attributes does this thing use, and how do I add them to my radius dictionary?" It's the file with all of the clues!

szern
12-13-2003, 09:13 AM
Will do just that..
Thanks again...

- Szern

Davader
12-13-2003, 12:21 PM
Can the RADIUS Web Interface be updated to now include these fallback features.

Installed b10 and used Web to create a new user.

Below is what is created, no Fallback info, or capability on the web interface to activate it.


# fullname: Test
test Auth-Type := Local, User-Password == "what"
VNC-PPPoE-CBQ-RX = 768000,
VNC-PPPoE-CBQ-TX = 256000

tony
12-13-2003, 02:08 PM
The next release will contain support for the fallback feature via the web tool.

datawork
12-15-2003, 03:27 AM
Server ISO hangs on boot at Loading Star-OS :cry: . P2-533 128mb Have retried download with same results. b3-9 is fine.

tony
12-15-2003, 07:49 AM
We'll look into this, thank you for the report.

Server ISO hangs on boot at Loading Star-OS :cry: . P2-533 128mb Have retried download with same results. b3-9 is fine.

datawork
12-15-2003, 11:14 AM
B3-10 Router ISO Works

tony
12-15-2003, 05:18 PM
I could not find anything out of the ordinary with the server ISO, however just to be sure all ISOs have been recreated and uploaded again.

Thanks!

dog
12-16-2003, 06:43 AM
Tried downloading the ISO again.

Server ISO hangs on boot at Loading Star-OS. Keyboard CAPS and SCROLL LEDs keeps flashing.

I'm using a Via C3 1Gig, 128MB RAM, 32MB DOM, with LiteOn LTD-163 DVD Drive.

tony
12-16-2003, 12:25 PM
Thank you. We have identified a problem with the server edition ISOs which include the symptom you are seeing.

In the short term, install using the Rotuer Edition, then upgrade to the Server via the .bin download.

Thanks!

dkii
12-21-2003, 02:20 PM
I'm having major lockup problems with a lightly loaded link with atheros(netgear wg311) on both ends. The link will just stop passing traffic. Both ends still show link/association with signals around -60 to -65. It seemed to be a little worse when the rate was set to auto. It's now set to 36mbps fixed. I've toyed with the ACK setting, with no effect. Link distance is appx 2 miles. It's been doing it every now and then(once-twice per week or so throughout the atheros testing. I upgraded to b10(from b9/b8), and now it's 3-4 times daily. I'll downgrade back to b9 and see if that helps any.

dkii
12-21-2003, 02:21 PM
btw, if I activate changes, the link starts passing traffic again.

bobbyc
12-24-2003, 06:08 PM
My link has been fairly stable... I think rain got in the connector this morning at one of the ends, so I am back on the 2.4ghz backhaul.

I did notice earlier that when I locked each end to 12mbps, it still was transferring much much higher speeds. Is only auto available at this time?
This is with AG520 cards.
Bob C

tony
12-24-2003, 10:34 PM
The data rate may be set to 12Mbps, however with the card optimizations available for the ar5212, the actual throughput at that rate may be higher than one would expect.

For example, with two AG cards connected at 11Mbps in 'b' mode, they can perform over 3,000KB/s actual throughput where one would normally expect 600-700KB/s.

bobbyc
12-24-2003, 11:19 PM
That is insane! Cool Tony thanks.... happy christmas up there in canada

tony
12-25-2003, 12:01 AM
Merry Christmas to you too!

bwbboot
12-27-2003, 03:24 PM
Have 2 StarOS Router Editions v1.13.3b10 running here.
1 box is running AP and 1 is running as a station.

AP settings are:

ESSID: wijssn01.wirelessijsselstein.nl
Channel: 1
Transmit Rate: auto
ACK: 0
Country Code: NL
TX Power override: 30
Network type: AP
Operating Mode: Auto (no turbo)

Station Settings are:

ESSID: wijssn01.wirelessijsselstein.nl
Channel: 1
Transmit Rate: auto
ACK: 0
Country Code: NL
TX Power override: 30
Network type: Station
Operating Mode: Auto

The station keeps scanning all the time, and does not stay associated.
I have tries static Operating Mode's, differend channels, static transmit rates, and all StarOS versions starting from B6 till current. All same behaviour.

I am using the Senao NL-3054PCI Aries.
http://www.senao.com.tw/english/product/product_wireless01_outdoor_1.asp?pgtl=Wireless&tp1 id=02&tp2id=03&proid=000067

Does someone has any ideas? Thanks in advance.
Bjorn.

Please find below a snippet of my syslog.

Dec 27 23:17:47 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 has associated
Dec 27 23:17:49 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 disassociation callback
Dec 27 23:17:49 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 deauthentication callback
Dec 27 23:17:49 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 authentication ind callback
Dec 27 23:17:49 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 has associated
Dec 27 23:17:50 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 disassociation callback
Dec 27 23:17:50 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 deauthentication callback
Dec 27 23:17:50 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 authentication ind callback
Dec 27 23:17:50 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 has associated
Dec 27 23:17:52 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 disassociation callback
Dec 27 23:17:52 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 deauthentication callback
Dec 27 23:17:52 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 authentication ind callback
Dec 27 23:17:52 wijssn01 kernel: wpci1: 00:02:6f:20:54:47 has associated

tony
12-27-2003, 03:57 PM
Ok, three things:
Set your channel correct for the mode you are using.. channel 1 is only valid for 802.11b (which is not selected, when auto is chosen).

Select a mode for the AP. do not keep it on auto. The client can remain on auto without problems.

Change your TX power to 20 for the best results.

Thanks!

bwbboot
12-27-2003, 04:07 PM
Ok, i left the station the same settings.

AP is currently using channel 4 (2427) TX=20 Mode=G

Same problems.

bwbboot
12-27-2003, 04:12 PM
I could give you an IP and login to verify if you like?

Bjorn.

tony
12-27-2003, 06:09 PM
What is the distance you are going? Try placing both ends with an ACK timing of 500 (or more) and see if that helps.

After you've tried this, you can email me the nessesary information to log into your systems.

Thanks!

bwbboot
12-28-2003, 03:19 AM
The distance is about 30 meters (90 feet)..

Bjorn

tony
12-28-2003, 12:01 PM
I looked at your system and the signal is awfully low for such a short distance. What antennas are you using? Can you make sure the pigtail connector has not been damaged when plugging into the card?

Thanks!

bobbyc
12-29-2003, 04:20 PM
Just some general signal/noise reporting bugs: AG520 AP to AG520 station:

1. Noise levels are always -102. Is the hilltop really that noise free?

2. The AP is set to 0 TX, and the station is set to 30TX
The AP association list reports -74/-74, but the client reports -81. So, my 1st guess would be that the AP is reporting the 'APs received signal' in the 'clients recieved signal' spot.

I would think that the AP should be reporting -74/-81

Overall I've been really happy with the .a portion of the driver! The only downtime we've had is for not properly waterproofing the antenna to LDF4 connector.
Bob C

tony
12-29-2003, 04:26 PM
The -102 is reported because the Atheros hardware does not report noise.

The -74/-74 readings represent the AP's receive signal on the left, and the AP's ACK RSSI signal on the right. The Atheros hardware is not capable of reporting the client-side signal levels as the Agere and Prism cards can. Implementing a special protocol to handle remote signal reporting would not be difficult, and will be considered at a later date.

bobbyc
12-29-2003, 05:37 PM
Well then everything is fine! Thanks :)

dkii
12-29-2003, 07:01 PM
what is ACK RSSI ?

lonnie
12-29-2003, 08:17 PM
Let's analyze this: ACK is a reply, RSSI is a signal level so it must be the RSSI of the last ACK :D :D :twisted: :D :D :D

dkii
12-30-2003, 08:57 PM
I'm still confused.. oh well maybe it's better that way I'm not dangerous :D

tony
12-30-2003, 09:00 PM
This is the signal strength from the last ACK received by the station. If this value does not update, or stays at -102 that could mean the remote end is either note receiving anything from you, or the distance is too great and requires one to adjust the ack value.

dkii
12-30-2003, 09:04 PM
okie that's a little better.. thanks and have a great vacation

bobbyc
12-31-2003, 02:13 AM
I have a tower we put the beta on to test the 5.3 This tower has 4 other older wireless cards. It seems that since we loaded the latest beta on, when we change the channels on the older wireless cards, the clients do not re-associate all the time. Even rebooting the tower will not get all clients to associate. I have to put the card back on the channel it was originally on.
This is most likely a new noise issue; I just haven't had the time to track it down. I was thinking maybe the new dual card is doing something wierd to the spectrum up there (even though I'm using only 5.3ghz)
Channel 11 is pretty much useless right now.
This is all happening at the same time that the tower company moved our equipment higher up the tower so that a new cellular company could mount their sectors in our previous tower location :(

lonnie
12-31-2003, 09:12 AM
Cellular at 200W or your 5.3 at 50 mW. Which do you think has the most ability to create interference? Simply shut the 5.3 system down and I bet your interference stays. Also cell guys quite often use 2.4 for their backhauls and they like to punch through everything else (amps and big antennas).

bobbyc
12-31-2003, 10:42 AM
Hi Lonnie,
Yeah I don't think it is the atheros card afterall. There is just so much weirdness going on right now on this tower. Late last night I tried to find a channel order that would work. One of my sectors I put on channel 4 and it was behaving the same way as channel 11 where none of my clients would re-associate.
Just to be safe, we are going to downgrade, and then if the problems still show up we'll start swapping radios; and then probably change to horizontal polarity. Each AP has 20 or so customers so it will be fun.
The cellular brought in their own wired backhaul; I made sure they weren't going to be using 2.4ghz backhaul before we moved for them.
Thanks!
Bob C

CompuTron
01-04-2004, 05:28 PM
Has anyone had issues booting from the CD image of this beta? I'm burning to a CD-RW and when the "Welcome to StarOS: loaded, now booting." message appears, my Caps Lock and Scroll Lock LEDs flash and the system goes no further.

I've erased the CDRW several times completely and the version from the stable download page works fine.

I've tried installing this on 2 different legacy motherboards so it has to be in the image. I've downloaded the image several times just in case it had an error in the transfer.

I don't think it is a problem in reading the CDRW with these legacy CD-ROMS because it is reading "some" of the CD.

Any ideas would be great.

Travis

nuclearcat
01-04-2004, 08:27 PM
Thats means kernel paniced....

CompuTron
01-04-2004, 09:09 PM
Thats means kernel paniced....

Man...I must have the whimpiest kernel known to mankind. :wink:

lonnie
01-04-2004, 11:24 PM
There is a problem we are working out with the server image, but router is fine. Which image are you using?

CompuTron
01-05-2004, 07:50 AM
It was the server ISO image. Typically, I'd just upgrade from a lower image but my GigE NIC that the license is tied to hangs the POST of these older motherboards.

Travis

tony
01-05-2004, 08:02 AM
The server ISOs are not supported in the latest release. Solution is to download the Router ISO, install it then upgrade to the Server via the .bin file.

Thanks!

jbland
01-06-2004, 07:44 PM
I think this is a bug but not 100% sure. The atheros cards stop communicating with each other after about 2 hours with or without load. I tried using the watchdog timer but the unit reboots every 3-5 minutes, so this may not be functioning properly as well and got a bit annoying.

With the watchdog timer I'll set this on 2 different machines and it seems to do the same thing regardless. I am pinging across the wireless link and have not tried pinging the wired side, but techincally that's pointless because I really want to know if the link is up and not if my switch is working.

I don't have to reboot the machines to make the link come alive again, all I do is click activate changes and all is well for about 2 or so hours.