View Full Version : StarOS 1.13.2 build 3790 released.
New in version 1.13.2:
New: PCI Atheros 5211 and 5212 802.11a/b/g support (Router and Server Editions). This includes support for the 5212 enhancements such as the Super-G 108Mbps mode.
New: Routerboard (www.routerboard.com) support
New: Web front-end for radius server, available on http port 10000 (server, adjust firewall on new installs to allow access to this port)
New: Keys can now be entered for Ethernet devices that are not present in the current system.
Update: eeZee client has been updated to better support DHCP-based users.
Update: Hotspot can now operate properly if all interfaces are bridged.
Update: WDS roaming updates.
Update: Proxy, DNS and Radius server menu and desktop items are now only shown on Server Editions.
Update: Hotspot and eezee client have been updated to support clients with any pre-configured proxy server settings. Integrated hotspot proxy supports both http and https protocols. Limitation: clients who use DHCP will not benefit from this feature, yet.
Update: Zebra routing engine (RIP, OSPF and BGP) have been updated to v0.94.
Update: New firmware for Hermes and Ruby cards
Update: Bridging code has been updated to work more like those in pre-1.13.x releases.
Update: SSH Server has been upgraded to OpenSSH v3.7.1
Update: DNS Server has been upgraded to ISC-BIND v9.2.3
Fixed: WRAP and Routerboards no longer have a 90 second bootup delay.
Fixed: wpci interfaces are now shown properly under the menus.
Fixed: PPPoE server now works as expected.
Fixed: Client (layer-3) bridging now functions as expected with PCI Wireless devices such as Prism 2.5, or Atheros.
Fixed: pppoe server was using an MTU size that was not fully compatible with some PPPoE dialers.
Fixed: Having the "Limit to one ip per mac address" eezee configuration option unchecked now works as expected.
Fixed: CBQ and Firewall rules for active hotspot sessions are now removed if the hotspot service is disabled.
Fixed: SSH keys are now auto-generated upon first boot of system. The key generation may take some time on SC520-bases SBC systems.
Fixed: Hotspot rates as specified in Radius are now consistent with those used by pppoe and pptp. Eg: 128Kbps rate is now entered as 128000 and not 16000.
Removed: tcpdump has been replaced with the above traffic monitor due to space constraints. (CPE Editions)
This release can be downloaded from http://www.star-os.com/
rasimoes
11-11-2003, 11:02 AM
Tony, this version corrects the WDS issue?
Thanks!
Yes, this version should clear up the WDS issues introduced in the later v1.13.2 betas.
radev
11-12-2003, 04:03 PM
I did try to install this release, but have 2 problems.
when my wireless senao card is inserted the system stops during booting at the point of installing the pcmcia controller (in the syslog i can find that he does see the cart and gives it a reset, after that it will crash so no new info is written..
the second problem (even with no card inserted) this release does not see the harddisk used for radius (system is on CF)
the only thing i can find diferent is the kernel which is gone BACK from 2.4.22 (which did work) to 2.4.20 with this problems (don't know is it is coused by this)
i am verry happy with the system, and hope for some extra features soon (cbq only WAN and fullspeed to LAN <--> WIFI)
(DMZ (WAN direct to Internet network modem) and DMZ for running web/mail server.)
at this moment i have a gateway, star-os, webserver, fileserver and workstation and i want to get rid of the gateway
greetz
Raymond
sure-data
11-12-2003, 04:08 PM
1:1 NAT will allow you to run your servers behind StarOs.
What kind of controler is your secondary HDD installed on?
Thanks!
radev
11-12-2003, 04:18 PM
I have a onboard controller on my VIA motherboard...
ATX733
it is installed as a slave on the primary controller but this is working in release 1.13.1 (3607)
Which version did you upgrade too? Can you provide me the downloaded file name?
Thanks!
radev
11-12-2003, 04:27 PM
the working is "strs-1.13.1-3607.bin"
the new one is "strs-1.13.2-3790.bin"
You mentioned you are using a CF to boot. Can you verify that your hard driver is 1) detected by the BIOS (can you see during bootup). 2) The CF is set to 'master' or 'master with slave' ?
Can you try moving the hdd to the secondary / master connector, does it have the same problem?
Thanks!
radev
11-12-2003, 04:53 PM
I can't try it. i don't have a IDE cable extra which fits the Motherboard.
some extra info
I did try also a USBkey (64Mb)
this one does work in the old release
in the new release this is also not availible (no HD is availible to prepair for radius in the new release)
Oxley
11-13-2003, 06:03 AM
I did try to install this release, but have 2 problems.
when my wireless senao card is inserted the system stops during booting at the point of installing the pcmcia controller (in the syslog i can find that he does see the cart and gives it a reset, after that it will crash so no new info is written..
the second problem (even with no card inserted) this release does not see the harddisk used for radius (system is on CF)
the only thing i can find diferent is the kernel which is gone BACK from 2.4.22 (which did work) to 2.4.20 with this problems (don't know is it is coused by this)
i am verry happy with the system, and hope for some extra features soon (cbq only WAN and fullspeed to LAN <--> WIFI)
(DMZ (WAN direct to Internet network modem) and DMZ for running web/mail server.)
at this moment i have a gateway, star-os, webserver, fileserver and workstation and i want to get rid of the gateway
greetz
Raymond
I had the same problem with the first version 1.13.x. I didn't installed it and went back to 1.12.6. Now I'm wory of the new version to upgrade from my desktop, because I have no access to the roof to correct it.
radev
11-13-2003, 06:12 AM
The only way to reboot when using a senao card is to remove it, and then you can flash it back to an older version, so yes it is a problem if you can't access the station....
maybe wait until the problem is fixed (proberbly when they are back to kernel 22 (i don't know what the reason whas of stepping back some kernel versions)
The reason for the step back was due to the fact that the v2.4.20 is a much more mature, and reliable kernel especially when it comes to bridging.
Hardware support is identical, and should not effect Wireless card support.
What kind of system are you trying to use your Senao card in?
radev
11-13-2003, 07:51 AM
I am using it in a VIA 377 (733) system with a PCI>PCMCIA controller
but a friend of mine had the same problem in a notebook he told me...
Does the problem occure with a non-senao wireless card, or only that one?
radev
11-13-2003, 07:58 AM
It does happen with more than one senao card (all of them) but when i remove it the rest of the system does boot.
when i insert my orinoco it works, but the range is not enough (thats why i use the senao long range)
It seems as though only the senao card is having problems which is interesting. Can you try replacing your pcmcia cardbus adapter another from a different brand?
What is the latest release that your Senao cards work in?
Thanks!
radev
11-13-2003, 08:10 AM
I have no replacement hardware, zo replacing the pcmcia controller is not possible
at this moment i am using the
Oct 1, 2003: StarOS&#8482; v1.13.1 build 3607 released.
which does work PERFECT
Nov 10, 2003: StarOS&#8482; v1.13.2 build 3790 released.
Which fails the SENAO (Prism 2.5 with newest firmware, the old firmware does not work on both systems)
What brand and chipset is your pcmcia controler ?
radev
11-13-2003, 09:51 AM
I don't know the official info, but i see a RICOH chip on it with the info
R5c475II
Thanks.
Does the senao card work if inserted after the system has already booted?
radev
11-13-2003, 10:13 AM
No, after i insert it it wil crash direct.
i turned the remote syslog on to see what happens, and the only thing i do see is that it sees the card, then it does a reset (of the card) and it is over.. total lock... only thing i can do is reset of turn the system off......
radev
11-13-2003, 10:25 AM
here is a pease from my syslog after the last entry (the reset) the system is crashed
Nov 12 22:18:21 10.0.0.111 kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Nov 12 22:18:21 10.0.0.111 cardmgr[893]: executing: 'modprobe agere_cs ignore_cis_vcc=1'
Nov 12 22:18:21 10.0.0.111 kernel: agere: Copyright(c) 2002, WebWorld Warehouse Ltd.
Nov 12 22:18:21 10.0.0.111 kernel: agere: Copyright(c) 2002 - 2003, Valemount Networks Corporation.
Nov 12 22:18:21 10.0.0.111 kernel: agere: 1.50 (Tony Toole <tony@valemount.com>)
Nov 12 22:18:21 10.0.0.111 kernel: cs: IO port probe 0x0100-0x02ff: clean.
Nov 12 22:18:21 10.0.0.111 kernel: cs: IO port probe 0x0800-0x08ff: clean.
Nov 12 22:18:21 10.0.0.111 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Nov 12 22:18:21 10.0.0.111 kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Nov 12 22:18:21 10.0.0.111 kernel: wpcm0: Reading card PDA records: 0x003f0000 - OK
Nov 12 22:18:21 10.0.0.111 kernel: wpcm0: NIC: id=0x800c v1.0.0
Nov 12 22:18:21 10.0.0.111 kernel: wpcm0: PRI: id=0x15 v1.1.1
Nov 12 22:18:21 10.0.0.111 kernel: wpcm0: STA: id=0x1f v1.7.4
Nov 12 22:18:21 10.0.0.111 kernel: wpcm0: Card is a prism 2.5 model 0x800C
Nov 12 22:18:21 10.0.0.111 kernel: wpcm0: Operating Temp: Commercial 0c <-> +40c
Nov 12 22:18:21 10.0.0.111 kernel: wpcm0: Hardware Address 00:02:6f:03:1d:99
Nov 12 22:18:22 10.0.0.111 kernel: wpcm0: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
Nov 12 22:18:22 10.0.0.111 cardmgr[893]: executing: './network start wpcm0'
Nov 12 22:18:24 10.0.0.111 kernel: wpcm0: Resetting wireless card.
bobbyc
11-13-2003, 10:54 AM
I upgraded a tower the other night to 1.13.2 3790 and it is using the lucent (TI) pcmcia-pci adapters with senao 2.5 200mw cards in them... no problem.
Bob C
radev
11-13-2003, 12:19 PM
i don't think but maybe has it something to do with the 2nd problem the HD which does not work work the new version...
i did look at the kernel.org site and did find a update in the .22 version from the VIA IDE.... I am using a VIA board so maybe the stepback has something to do with this
(i can't imagine a link to those problems, but they are both there...
Keep note that if there was a problem with the VIA IDE, you would not be able to boot the system. We've done quite a bit of testing and have not found anything out of the ordinary with VIA-based boards.
What class of VIA system are you using? Is it a K6, PIII, Athlon, etc.
Thanks!
nuclearcat
11-13-2003, 07:18 PM
Maybe good idea to include dmesg?
On it possible to see detection progress
radev
11-14-2003, 01:12 AM
I am using a VIA C3 system (during boot i see "via C3 1 Giga pro")
on the board itself i can't find a number...
radev
11-15-2003, 04:15 AM
I was browsing the site and found this
http://forums.star-os.com/viewtopic.php?t=417&start=0&postdays=0&postorder=a sc&highlight=
this is the system which i am using... only i don't have a DOM but a IDE<--> CF with a 32Mb CF inserted....
and a 800Mb Harddisk for radius (i want to use another CF for that but what is the minimum space i need)
Raymond
I have a 2 mile link using negear wg11's (atheros 5212). Throughput is decent (1.7MB tx, 600KB rx) One end is a celeron 400mhz, the other is a WRAP board.
I've noticed the signal fluctuates greatly, and once it goes down, it doesn't come back up (signal will go from say -69 to -70, but will never return to -69, untill I activate changes. It's gone as far as -82, once I activate changes, it will rise back to -69.(I just activated changes again, and a -79 went to a -66) I have the link set to 24mb/s fixed (should need -79db for this rate)
The celeron400 is the client, the WRAP is the AP. When running the test from the client(celeron), the rx is only ~600KB/s, but the tx is > 1700KB/s. Changing the speed setting doesn't really seem to affect the actual throughput(althout I haven't tried a speed under 24mb/s yet)
There's a few other things that I'm sure is on your to-do list, but I'll list em incase you miss any.
Last IP isn't updated(always reads 255.255.255.255) in the association list
Communication tallies are not updated(all read 0)
Signal readings in association list screen are not concurrent with signal readings on client side(2-3db lower on AP side)
I was going to mention the wireless monitor(just did), but it's probably greyed out for a reason.
The client IP detection has not been added quite yet, so the readings will show 255.255.255.255 for the time being.
The signal readings are averaged. The remote signal readings are from the cards ACK RSSI value which may not correspond 100% with the client end however it should be fairly close.
The Atheros hardware does not have communication tallies, however it does have it's own set of statistics that we may make available in the future.
The Wireless monitor is grayed out for the time being as the Atheros cards do not report signal readings in the manner it requires.
Thanks!