View Full Version : StarV3 v1.1.13 build 2080 has been released.
The new release is available for download.
Please visit www.star-os.com/downloads (http://www.star-os.com/downloads) for the release notes.
Thanks for providing the firmware unzipped, it must take some effort to set all that up all nice and pretty for us. I like being able to simply grab the new .pkg file rather than having to download a huge 30+MB zip.
With the size of some of the archives, we felt it would be wise to start providing the firmware in an unpacked form. Makes it much easier to download the parts you need.
kbldawg
03-21-2007, 05:24 PM
Much bettaaah!
David L. Vrablic
03-22-2007, 06:45 AM
What is the difference between the -2 and the -4 versions?
First time I have noticed that.
Those are used for fresh installs (jtag for example). The -4 is a WAR-4, and -2 is a WAR-2.
All you need is the .pkg file under the Upgrade section.
rbolduc
03-22-2007, 10:30 AM
Smaller is bettah !!! ;)
naamah
03-25-2007, 04:04 AM
not work connection table size :(
lonnie
03-25-2007, 12:07 PM
Sorry, but your post does not tell us anything to enable us to troubleshoot your issue. Connection tracking table size does work in the systems we have used it. What symptoms lead you to think it does not?
not work connection table size :(
tkerns
03-25-2007, 05:24 PM
I replaced two V2 WRAP's with a WAR-4. I'm using a CM9 for the backhaul and 2 WLM54G's for the 2 AP's. I uploaded this release to the WAR. I have noticed that the log is full of clients dis-associating and re-associating. It look like the time is about every 5 minutes. I have another WAR with CM9's only running ver 1.1.10 build 1734 and I do not see the same thing. Is this new to this release or is it only related to running "b" mode and the WLM54G's?
Idle clients are disconnected once every 5 minutes, which accounts for the log entries. This is not new to V3, however on busy APs it can overwhelm the logs.
If it bothers you, use the ping watchdog on the clients.
tkerns
03-25-2007, 07:33 PM
ping watch dog is not an option....
These are still a mix of CB3's and WRAP's. I guess I can expect to see all go to "n" on the associations? Then I will load 1.1.5b build 1659 as this is the only V3 I have found to support this configuration. Later 1.2 V3's seem to have performance issues, at least every time I have attempted to use one..
naamah
03-26-2007, 03:26 PM
it's PC and since i enable connection tracking setup i get 30 % packet lost on router in logs i get "connection table full" even though i set option "connection table size" - high
sory my english wery weak :(
Sorry, but your post does not tell us anything to enable us to troubleshoot your issue. Connection tracking table size does work in the systems we have used it. What symptoms lead you to think it does not?
tkerns
03-26-2007, 04:57 PM
I have one StarOS router that I had to keep raising the table size to 65536 which amounts to a table size of 22.4 meg. It all depends on the number of clients being Nat'd and also the number of clients running VPN's.
edit: Also, have you done a "reboot" after changing the table size. I believe an activate will not reset the table, and I had to do a reboot.
Per Tony, you don't have to reboot. Changes take effect immediately after changing.
lonnie
03-26-2007, 09:37 PM
I suspect that your system is being scanned, probed or attacked. A user running p2p software can also cause issues since a p2p user will get thousands of connection attempts. Since connections take a lot of time to expire it can deplete any system.
Rather than raising the limits to the point you exhaust ram or slow the system down, you have to use Beacon to find the user or users who are allowing and creating so many connections. Once you do find them you have to speak with them and get them to limit the number of connections they will accept.
it's PC and since i enable connection tracking setup i get 30 % packet lost on router in logs i get "connection table full" even though i set option "connection table size" - high
sory my english wery weak :(
After doing some investigation, the connection tracking table size adjusting does not alway take effect on reboots (though it does via the SSH interface). This has been corrected for the next release.
soulmata
03-28-2007, 02:44 PM
ping watch dog is not an option....
These are still a mix of CB3's and WRAP's. I guess I can expect to see all go to "n" on the associations? Then I will load 1.1.5b build 1659 as this is the only V3 I have found to support this configuration. Later 1.2 V3's seem to have performance issues, at least every time I have attempted to use one..
If you have the capacity, host monitoring is really a good idea. We use it in lieu of ping watchdogs on every client (which are of limited use anyway, though all CPEs still have it configured). In particular, I love nagios. I use it to monitor and track performance and status for every customer we have. You can easily configure it to probe every client every few seconds.
go.fast
03-28-2007, 03:51 PM
In particular, I love nagios. I use it to monitor and track performance and status for every customer we have. You can easily configure it to probe every client every few seconds.
Me too!
https://addons.mozilla.org/en-US/firefox/addon/3607
Even have an add on for my browser.
kbldawg
03-28-2007, 04:33 PM
Works great with ubuntu too!
bobbyc
03-29-2007, 11:46 AM
I understand why the SSH is omitted from the WAR1 (size constraints?), but was it meant to be omitted from the WAR 2/4 release? Or was it a "oops"?
Thanks,
Bob C
butchkemper
03-29-2007, 11:57 AM
The ssh client has been moved to the command shell.
Once in the command shell, drop to the prompt (type 'sh'), and you will have ssh and telnet at hand.
The quote came from Tony in an earlier thread about V3 1.1.12 - http://forums.star-os.com/showthread.php?t=6421.
Butch
mrmike
04-03-2007, 07:07 PM
It might be insignificant to some, but I do miss the numbers; you know the 'alt i 3 2 1' for configuration. I hate the mouse, plus it easier when I'm on the phone with my installers.
There are still shortcut keys.. I don't understand?
You can still do everything with the keyboard, no mouse required.
Beebe
04-04-2007, 12:21 PM
I'm having trouble with CBQ on v1.1.13 on the compex CPE boards.
client = ether1
net = wpci1
qshape joe-user 100 bw 1200k 600k 12.198.208.0/24 on $client
results in a wide open connection.
Is this a known issue?
Thanks,
Roger
CBQ is working as expected for me on the WAR-1 platform. I have a few of them deployed with CBQ rules pretty much just like yours (limiting private /24 subnets with one qshape rule) and they are functioning normally.
I haven't tested how accurately the bandwidth is limited from the perspective of a client, I just know that the rule(s) are being hit and counting up traffic as expected.
What does your cbq traffic report show?
Beebe
04-04-2007, 02:58 PM
It shows
bi-pipe 100 ( 146.48K / 73.24K): rx: 0B, 0.00B/sec tx: 0B,
Yeah so your rule isn't being hit. There is likely something wrong with it.
The IPs actively in use for Internet connectivity on ether1 are 12.198.208.0/24 ?
Beebe
04-04-2007, 03:15 PM
This particular customer is using the IP 12.198.208.106 which was obtained via dhcp from our AP to his linksys router.
I'm using the WAR1 configured as a transparent bridge (bridge group 9 on both interfaces). Are yours configured that way?
Thanks,
Roger
Ah, no. I don't use WDS. My qshape rule is shaping IPs that are directly on ether1, no bridging involved.
qshape and cbq rules do not work as expected when there is bridging involved. This is not unique to the WAR-1, this goes for all StarV3 versions and editions. You may be able to make some CBQ work by using normal cbq shape rules instead of qshape and doing something along the lines of:
pipe 100 bw 1200k
pipe 101 bw 500k
shape all to pipe 100 from any to 12.198.208.0/24 in via $net
shape all to pipe 101 from 12.198.208.0/24 to any out via $net
Try that and see if it works for you.
Also, I would suggest avoiding WDS, it is not viable for a PtMP customer-bearing AP.
Beebe
04-04-2007, 03:31 PM
I'm planning to switch to pseudo bridging when it becomes available. I've not had a problem in the past with my shaping rules. I'll try what you suggested.
Thanks,
Roger
jazbill
04-11-2007, 07:23 AM
I'm having a bit of trouble with the ping utility in the latest version of staros (1.1.13 build 2080) on WAR 1 boards.
Why does the ping utility only ping 1 time instead of continuously until the user ends the thread?
Thanks
Thank you for pointing it out. In the short term, the ping utility under "system->system console" should work without problems.
I'm having a bit of trouble with the ping utility in the latest version of staros (1.1.13 build 2080) on WAR 1 boards.
Why does the ping utility only ping 1 time instead of continuously until the user ends the thread?
Thanks
kbldawg
04-11-2007, 04:35 PM
I noticed that the other day too, but forgot to mention it.
I also noticed that when I tried to change the ether1 auto negotiate settings (WAR1) it gave me an error message... "Unsupported by Ethernet"
Since the WAR-1 works as a managed switch (two ports), the Auto-negothation options are not available.
gunther_01
04-30-2007, 09:05 PM
Interesting tid bit. Using this version (2080) on a WRAP 2 port mpci/2 port ethernet AP box.
I had my ISP add some reverse DNS to my IP's. After that change I had to reboot the AP (it fixed it anyway) in order for the clients on that AP to get DNS resolution (ap is used for DNS cache). Not sure if it's a bug or just normal. Thought I would post it anyway.
lonnie
04-30-2007, 09:38 PM
You could also have stopped and started the DNS. It was caching and needed a flush.
calidadwireless
05-08-2007, 12:07 PM
i have a AP11-2 board supported by Star-os. It is currently working at my main backhul/AP broadcasting to over 150 clients. This system is working great however i find at times it will hang, clients would call and complain of good signal but cannot get and IP, when i reset the AP, everyone can get back online, now this happen at maximum usage and also with abt 5 subscribers at times. I want to upgrade to the lastest board using the 23dm mini pci card quad board. Does anyone have any bad experience using the lastest board. I want to used the new board at my main base station to provide service to over 1500 subscribers. What advise can i get here? Looking forward for some positive ideas, i like star-os solutions.
go.fast
05-08-2007, 12:25 PM
I would go with the new metro board regardless of 1 card or more.
calidadwireless
05-09-2007, 08:46 AM
Does anyone know alot about the metro quad board? What are the pros and cons lets hear it! if we all work together we going to turn this world to complete wireless..:D
lonnie
05-09-2007, 08:53 AM
What do you need to know? It takes 4 cards (high power if you choose), it has awesome power handling and protection and will be available soon in a 24V model.
calidadwireless
05-09-2007, 06:03 PM
I just want to know more before i make any desicions... so far i am happy with the response... would just welcome more if someone have more to say. I've just install a second AP11-2 today and and i enable the WAP feature on it, just a great piece of equipment to have on small network.
calidadwireless
05-18-2007, 09:14 AM
Any one ever used the service on the Wrap v2 WPA CLIENT. i would like to used it but i and not sure how would i be able to set a configuration or to enable such service so that a WPA can work with mobile phones.
lonnie
05-18-2007, 10:37 AM
There has been much discussion about WPA so a search of the Forums will give some reading material.
You would be better off waiting for the upcoming V3 release and WPA support for the WRAP and WAR boards.
DrLove73
05-28-2007, 09:39 AM
Will support for starutil be in the next release, and can you publish one release as soon as starutil support is ready (on top of 1.1.13 build 2080)?
This is only feature I NEED for the moment.
I'm to upgrade couple of PC V2 WiFi routers, and I have monitoring/script saving system based on starutil. I upgraded my main WiFI router, and now can not even save cbq script, not to mention Association lists (batch files used to save them every 10 minutes for posterity)
Support for individual scripts will be added to the upcoming 1.3.0 release. An updated 1.1.x release will be made afterwords with the same starutil updates, and a few general fixes.
mimbach
06-06-2007, 09:40 AM
Lonnie or Tony,
I know you dont like to give dates on upcoming releases. So are we getting close to the new release or are we weeks out still?
Cannot give ETAs on the 1.3.x release.
The 1.1.14 interim release should be ready within a week if all goes well.
dc2005
06-06-2007, 03:45 PM
Any chance we could get some wireless interface stats in one of the upcoming releases? I know from reading other posts that this is planned once the new driver is ready but is there any possibility of including some basic stats sooner, in particular the signal strength(s). We could really do with this to monitor some of our longer backhaul links to see how much fade we're getting etc. It doesn't even have to be full-blown snmp support, if this makes it any easier, maybe it could be done using starutil and a suitable script?
lonnie
06-06-2007, 03:53 PM
I'm not sure what you want me to say here, well, actually I know exactly what you want me to say. If I do say that we have such a thing planned and it has to be left out at the last minute for some issue then you'll be angry and and will have been making plans to use it and the Forums will get loud with people saying we messed them up.
So, what I will say, is that we are working on it and the intention is to release it soon. No date is promised. No feature set is promised. We will get as much and as soon as we are able.
Any chance we could get some wireless interface stats in one of the upcoming releases? I know from reading other posts that this is planned once the new driver is ready but is there any possibility of including some basic stats sooner, in particular the signal strength(s). We could really do with this to monitor some of our longer backhaul links to see how much fade we're getting etc. It doesn't even have to be full-blown snmp support, if this makes it any easier, maybe it could be done using starutil and a suitable script?
DrLove73
06-13-2007, 10:50 AM
Any chance we could get some wireless interface stats in one of the upcoming releases? I know from reading other posts that this is planned once the new driver is ready but is there any possibility of including some basic stats sooner, in particular the signal strength(s). We could really do with this to monitor some of our longer backhaul links to see how much fade we're getting etc. It doesn't even have to be full-blown snmp support, if this makes it any easier, maybe it could be done using starutil and a suitable script?
dc2005: Starutil support (at least for individual scripts) SHOULD arive in next interim release that COULD came in next week or so. MY opinion is that starutil support for Associations and Link-stats will also came with that release. That way they will get us of their backs for now about monitoring and script control, and be able to carefully and without (excessive) stress work on further development. So bear with the rest of us a while longer and dont preassure them, calvary is on the way :cool:.
gaf@bluerivernet.com
06-28-2007, 08:03 AM
On V2, I have been able to block customers by coding:
deny all from "IP" to any
Where "IP" is the ip of the client I wish to block...On 2080 it does not seem to work. Is this a known issue? Has the syntax changed?
Thanks, Greg
lonnie
06-28-2007, 08:37 AM
The syntax should be the same. Does it create a rule (check the reports).
gaf@bluerivernet.com
06-28-2007, 09:54 AM
Under System Reports, Firewall Chains, there are none....
Greg
If you enable connection tracking (it must be disabled), your firewall should work as expected.
gaf@bluerivernet.com
06-28-2007, 10:22 AM
;) Thank u. That indeed fixed it.
Will connection tracking enabled always be a pre-req for firewall?
Greg
Yes, it is needed for firewall support in V3 (can be disabled for a network performance boost if firewall and NAT is not being used).
gaf@bluerivernet.com
06-28-2007, 10:33 AM
Understood...Thanks again!
Greg
butchkemper
06-28-2007, 02:16 PM
In V2, connection tracking was not required for the firewall rules.
In V3, connection tracking is required for the firewall rules.
Is it possible to change V3 to have a restricted set of the firewall rules function without requiring connection tracking?
I ask because I need to limit access to back haul radios - War2 units, and I can not have connection tracking enabled because of dropped packets.
If making this change is a possibility, please consider it for an upcoming release.
Thanks.
Butch
In V2, connection tracking was not required for the firewall rules.
In V3, connection tracking is required for the firewall rules.
Is it possible to change V3 to have a restricted set of the firewall rules function without requiring connection tracking?
I ask because I need to limit access to back haul radios - War2 units, and I can not have connection tracking enabled because of dropped packets.
If making this change is a possibility, please consider it for an upcoming release.
Thanks.
Butch
I have suggested some optimization of connection tracking before since it should be possible to run minimal rules without it. The dropped packets can be minimized by increasing the connection table size.
mimbach
07-06-2007, 11:52 AM
I have 2 older war2's. the have fair load on them and alot of routes. Sometimes when I go to add / remove a route and activate changes they lock up hard and have to be physically power cycled to get them back up.
The only ones of all are wars are these old ones.
Ideas?
1) Check their power supplies, are they adequate?
2) Possibly replace the boards, there's likely a hardware problem
mimbach
07-06-2007, 03:15 PM
I replaced both power supplies. Infact the one side is being fed from a bank of batteries with dual charge controllers.
These are the old war2's that you can power them from both ethernet ports.
Mimbach
mimbach
07-07-2007, 11:06 AM
we replaced the war with a new one and have not seen a lockup yet.
If I spawned 4 ssh sessions and told it to reboot it would just die. Under heavy load just connecting to it would cause it to lock up.
The only way to recover even with ping watchdog etc enabled is to physically drive up the mountain and power cycle the radio.
This was also tested on the latest beta also with the old war2 board.
Mimbach