StarOS 2.01.1 build 4590 released.

[tony]

Release notes: http://www.star-os.com/release-notes/2.01.1-4590.txt

Downloads available on http://www.star-os.com/

NOTE: read the release notes carefully, including the caveats before upgrading.

[tony]

OEM release will be available for download within 24 hours

[bobbyc]

Just updated myself to this release, and noticed PPTP client is still broken. Same problem carried over from the 2.00.3 beta series.
http://forums.star-os.com/viewtopic.php?t=2932&highlight=pptp+client
Bob C

[tony]

The pptp client has just been tested and seems to operate as expected. What errors are you encountering?

[bobbyc]

I will try again tonight, and have the sys adm look at the VPN server end of things.
All I did the other night is upgrade a customers' box from 2.00.2 to this release, and it never got a lease. Logged into it, and tried to force it to connect to PPTP, but it wouldn't. I'll email you a ip/psswd.
Bob C

[David L. Vrablic]

When I used 1.13.3 the "Gas guage" was pegged with this customer.
I am using a hotter antenna now and upgraded to build 4590 the readings have been Pegged at 70. (Now at 68 )
(PS: The green bar doesn't display even tho the numbers are there)

wpci1: prism 2.5 68 -53dbm -98dbm 11 2412 client

Was the max reading false before and this one more accurate or is this one pegged at 70?

[lonnie]

The prism and Orinoco drivers have not been touched for a long time. There must be another explanation.

[tkerns]

I have noticed in this build (do not know if it is in others), when I use the SSH and exit, the screen says to press any key to exit SSH, only a return works.

Also, I can not find where to "set" how long the association list shows inactive clients. In previous releases, this could be set when using an NL2511 in AP mode. I am using CM9's in AP mode with this build and do not see an option. The list seems to show inactive associating for a long time, one is approaching 24 hours.

Tim Kerns

[n2000]

I read "Reference Guide" ok... any HowTo guide for nnewbies like me. star-os for windows users will serve me best. If none, can somebody please post a simple HowTo here?

Thanks in advance.

[butchkemper]

I attempted to upgrade a micro ATX733 system that I got from VNC to V2.01.1 from V1.13.3. The system was rebooted after upgrading the software and it went into trial mode. I tried to reenter the unlock key but the key was was rejected as being invalid.

I installed a DOM containing V1.13.3, rebooted the system, and reentered the unlock key. The key was accepted.

I know the DOM containing V2.01.1 is good because installed it in the office spare system, entered the unlock key for the office spare system, and it went into normal mode. I have also used the same binary image to upgrade several other Micro ATX 733 systems with success.

The unlocak key that failed is:

FD7BNL-N7981S-ETHANR-4TOQ9E (BC:7D:55:DC:A0:8C)

Now I noticed that the first octet of the ethernet MAC address is not 00. Perhaps that is the problem. This is the built-in ethernet adapter and placing another ethernet card in the board is not an option because all the PCI slots are filled with radio cards.

Thanks for your help.

Butch

[rasimoes]

Tony/Lonnie, any good news about a new version that solve the OSPF problem present in current zebra CVS?

Thanks!

[lonnie]

Sorry guys, we are at the CES in Las Vegas. You're on your own until next Wednesday.

[rasimoes]

OK Lonnie, no problem... 8)

[bairdc]

Is there a problem with OSPF in the latest version of StarOS? I've been running OSPF on part of my network for about three months now, and it's worked great. I'm planning on moving the rest of the network to it shortly. One of the boxes where OSPF has been running is on 2.0.1.1-4950. As far as I can tell, it's working fine, but we're not yet running any critical traffic over this link. I did have some trouble initially getting this box to talk OSPF with a Cisco router, but that problem cleared up. I'm not sure what the problem ever was; it sort of cleared up on its own.

Anyway, aside from that, OSPF has been fine on our network. However, if there is a problem, I'd sure like to know about it before we move the rest of the network over to it!

Craig

[rasimoes]

Yes, look this thread:

http://forums.star-os.com/viewtopic.php?t=3534&highlight=zebra

Rodrigo

[rumen]

Is there SNMP MiB definition for StarOS?
Can i get signal strength/quality via SNMP?

[bairdc]

Yes, look this thread:
http://forums.star-os.com/viewtopic.php?t=3534&highlight=zebra


I don't think this is a problem with only the latest CVS version. According to phendry in the thread you referenced:

Interestingly though if I configure the wireless interfaces as non broadcast multi access and then specify the neighbor address the OSPF comes straight up. Looks to be related to multicasting across a wireless link as an NBMA interface will not send hellos in multicast packets but unicast to the neighbor address specified. Any ideas as to why? at what version was OSPF upgraded to latest CVS?

However, this is nothing new. This issue has been around for quite some time. This same phenomenon was discussed in several threads dating back to 2003. Here's one post talking about it:

http://forums.star-os.com/viewtopic.php?t=866

Basically, for some reason multicast breaks on wireless links. The work-around is quite simple: Set up OSPF on wireless links as non-broadcast, and then specify your neighbors.

Admittedly, it would be better if we didn't have to use work-arounds to get this done, but it's certainly not a show-stopper.

Craig

[rasimoes]

Craig,

I'm using the NBMA/neighbor specify in all my routers for a long time...i never had a problem with OSPF.

After upgraded to latest version, i've got a lot of trouble with OSPF... After hours of diagnostics, the ONLY solution is to downgrade all versions.

I really like the new features of latest version (specialy beacon), but unfortunatelly it doesn't work for me. :?

Rodrigo

[bairdc]

Interesting. On the part of my network where I'm running OSPF, I only have one StarOS box running 2.0.1.1-4950. Like I said, it seems to be fine, but I haven't really been paying close attention to it, since it's on a new network segment that is not yet being used. I'll have to watch it a little more closely. I have other StarOS boxes running OSPF without trouble, but they are all running earlier versions. I guess I'd better do some more testing before I do any more upgrades. Thanks for the input Rodrigo.

Craig

[rasimoes]

You're welcome! :)

[j0n]

Hi,

I've been trying to put in a rule pretty much like
# forward tcp to 1.2.3.4 8080 from 192.168.1.64/26 to any 80 out via $net

But its not being put into the iptables rules, other forward and drop rules are beint put in, but nothing is appearing in the Mangle chain.

I'm trying to set up a transparent proxy

What have I missed?

Regards
John

[tony]

Three things to check:
Does the script editor show an error when you press the syntax check button?
Did you remove the '#' in front of your forward line?
Did you disable connection tracking? It is required for NAT & forwarding.

The forward command will be listed under iptables as a DNAT statement.

[j0n]

No syntax error

No Hash

connection tracking, thats it.

Sorted thanks. I must be tired, cause I should have known to check that.

Have a most excellent weekend.

John

[butchkemper]

Is there an update/work around/fix to my problem where V2.01.1 failed to recoginize the unlock key that works with V1.13.3?


Butch

[tony]

Please send us a copy of your key and we'll look into why it has been deactivated.

Thanks!

[lonnie]

Is there an update/work around/fix to my problem where V2.01.1 failed to recoginize the unlock key that works with V1.13.3?


Butch

Are you sure you are not trying to use a CPE key with a Router image? The keys should be the same for Router and Server editions.

[butchkemper]

There is an earlier posting in this topic/thread that gives the key information.

I am positive that the key is a server key. The key is working in the server running V1.13.3 with the server editon of the software.

Please see the earlier posting in this topic/thread which gives more details on the problem. Also, I had sent several emails to network@valemount.com on the new year's weekend when this happened. I know someone got them because the extra keys I had generated while making sure I had a server key, were removed from license-keys.com as I had requested.

Thanks.

Butch

[lonnie]

The key sequence got changed along the way when we went ot combined licenses and our software detects that as an invalid MAC address. I had trouble when I originally generated it for, so we will have to patch the MAC checking for the next release.

[bobbyc]

I found a bug in the idle time display when using a atheros card. I'm using the CM9 card in 802.11g AP mode, with 802.11b clients associating. What I noticed is that the idle time jumps from 0 seconds to '49:17:02d' every few seconds. If there is no data passing over the link, then the idle time increases normally. I tested it with WEP on and OFF, as well as many other settings such as link distance, etc...

http://www.sonnet.com/bob/bug/wrongidletime.JPG

http://www.sonnet.com/bob/bug/correctidle.JPG

http://www.sonnet.com/bob/bug/uptime.JPG

See my uptime, much less than 49 days!!
Thanks,
Bob C

[lonnie]

We will check this out and get it fixed. It will not cause any problems except for the display.

[go.fast]

I found a bug in the idle time display when using a atheros card. I'm using the CM9 card in 802.11g AP mode, with 802.11b clients associating. What I noticed is that the idle time jumps from 0 seconds to '49:17:02d' every few seconds. If there is no data passing over the link, then the idle time increases normally. I tested it with WEP on and OFF, as well as many other settings such as link distance, etc...

See my uptime, much less than 49 days!!
Thanks,
Bob C

Ahhh, this is the reason that on a couple atheros ap's with just a couple customers, that I hardly ever see anyone connected.
Even though I've set the station removal time to 9999.
Good catch Bobc
George

[lonnie]

No the reason that people stay on the association screen is that we removed that code for the Atheros during the debug and development stage and just never put it back in.