StarV3 v1.3.23b build 2880 has been released.

[SpecialK]

Lonnie,

This brings up a question for me.

With other gear I have, I can jump into the AP and look at the subscriber list.
It shows me who they are, the signal strength, and also their firmware version.

Having the firmware version with the client name quickly shows me radios that did not or need to be upgraded and therefore maybe effecting the overall performance of the AP.

Is it possible in your managed mode abilities to get the firmware version from the CPE and display it in a list somewhere? I know that when I have an AP with 70 cpe on it, it is invaluable to have this feature. I know exactly which CPE to upgrade. And if there is trouble at the AP I know to check this first and make sure all CPE are on the same version.

[DrLove73]

Answer number one is: Current GUI is too small to display additional data, and GUI will not be changed until web version of the interface.

Answer number two: Special program is being made (StarGazer Senior) that will most likely have such functionality's. This manager is not due any time soon.

Answer number tree: You can always use "snmpwalk -v 2c -Ov -Oq -c public 192.168.212.100 1.3.6.1.2.1.1.1" command to extract version number for every unit on your network. With a little script you can quickly determen version for every unit, even use it for logging purposees.

[markscs]

One thing I noticed from the last version (22b) related to DHCP is that SMC wireless routers (or at least the "high power wireless router" model) broke after the DHCP changes. Plug the computer in directly, no problem, but the SMC could no longer get an address, there was some DHCP chit-chat in the logs on the SMC though. Fixed by simply changing the customers to PPPoE - only had two reported instances, but the second was yesterday so I thought I would mention it. Perhaps it is fixed in 23b, but I'll just leave the customers the way they are. Just pointing this out in case someone else notice and can report if this is no longer a problem in 23b.

[DrLove73]

ISC DHCP server is maintained by Internet Systems Consortium, who also maintain BIND and NTP servers, so I would say they are as close to Standards as it is possible. It is VERY likely that SMC behavior is their fault, so check for SMC firmware updates. If it worked so far, it could mean that ISC whent closer to standards, and SMC did not.

It could also mean that you did not follow correct ISC config procedure.

Lonnie, I can not, for the life in me, find your post with correct dhcp declaration.

Point in Lonnies how-to was, if I remember right, that you must declare EVERY existing subnet on that unit, even if you do not use it.

[tog]

Actually if I had to guess (which I have to because it wasn't stated) he's probably using dhcp auto-auth on a WAR1 or something which is the busybox udhcpd which is not completely perfect.

I don't know if Tony has poked at udhcpd at all, the version number is still the same as it has always been.

SMC routers' dhcp clients are pretty terrible... coupled with udhcpd not being completely perfect you could see problems.

I would not expect any problems with any dhcp client if you are using ISC dhcpd, though.

And of course there's the obligatory please try 23b, reporting on issues seen with 22b and earlier is still informational, but less helpful.

[ripv]

Originally Posted by DrLove73

ISC DHCP server is maintained by Internet Systems Consortium, who also maintain BIND and NTP servers, so I would say they are as close to Standards as it is possible. It is VERY likely that SMC behavior is their fault, so check for SMC firmware updates. If it worked so far, it could mean that ISC whent closer to standards, and SMC did not.

It could also mean that you did not follow correct ISC config procedure.

Lonnie, I can not, for the life in me, find your post with correct dhcp declaration.

Point in Lonnies how-to was, if I remember right, that you must declare EVERY existing subnet on that unit, even if you do not use it.

It used to be here - but now it seems the permissions have changed?
http://forums.star-os.com/showthread...8530#post58530

[tog]

Lonnie seems to have blocked off/hidden all the old beta threads which could be bothersome because we lose access to all the release notes history which sometimes contained tips and instructions for new features. If I could still get to them temporarily I could at least post that info on the wiki.

[lonnie]

I have moved them back but locked them. I do not want any discussion about older releases, since I am only concerned about the current release.

[markscs]

Originally Posted by tog

Actually if I had to guess (which I have to because it wasn't stated) he's probably using dhcp auto-auth on a WAR1 or something which is the busybox udhcpd which is not completely perfect.

I don't know if Tony has poked at udhcpd at all, the version number is still the same as it has always been.

SMC routers' dhcp clients are pretty terrible... coupled with udhcpd not being completely perfect you could see problems.

I would not expect any problems with any dhcp client if you are using ISC dhcpd, though.

And of course there's the obligatory please try 23b, reporting on issues seen with 22b and earlier is still informational, but less helpful.

I won't know as I've changed the SMC router users to PPPoE, just mentioning it in case someone else ran into it. And yes, I expect SMC's dhcp client is to blame as no other routers seem to have broken. We aren't using auto-auth, our clients are all pseudo-bridge devices. I'm not faulting Star-OS or ISC DHCPD just mentioning it in case any of you run into a similar situation.

[tog]

Originally Posted by lonnie

I have moved them back but locked them. I do not want any discussion about older releases, since I am only concerned about the current release.

Thanks, locking them but leaving them accessible to read seems optimal.