i just added a few WLan clients to my network, on some i see the "network" name, on some i didn't see them, is that a bug? In my opinion this should be available by the DHCP Lease?
I see this in a configuration where two SSIDs are advertised, one is bridged, and the client using the bridge gets DHCP from a source other than the ASG.
In other words, if the client gets DHCP from someone else, the IP address on the ASG's wireless clients shows as 0.0.0.0
Yes, that is what i would expect too if i had a external DNS, but in these Networks i only use the DHCP from my Astaro. And as you can see, there is one PC which has all informations presented ...
It should work when the ASG DHCP server is used, this _is_ strange.
Can you please check the output of
# cc get_dhcp_leases
executed as root on your ASG? This is what the DHCP server tells us, if the information isn't in there it was either not given to the DHCP server or the DHCP server "forgot" to save the information.
Cheers,
andreas
When a client device successfully connects to the wireless service, the ASG checks if there is a lease for that client (MAC address) present. If yes, we use the IP address for that lease, and the hostname which was submitted by the client during the DHCP request. If there was no hostname submitted, the DHCP server usually provides "[unknown]" as hostname.
If there is no lease on the ASG (which happens if you either use a different DHCP server, or use a static mapping) the IP is set to 0.0.0.0 and the hostname is set to the confd REF string.
Currently there is an issue with the leases: in some cases, the DHCP server has multiple lease entries for the same MAC address. In those cases, if one of those entries has the "[unknown]" host name, it can override a lease having a correct hostname. Workaround is to set the name manually in Wireless Clients, this always overrides data from the DHCP server.
There is another issue when creating a static mapping after you already have obtained a dynamic lease: since the static mapping can not be found on the ASG, but the dynamic mapping still exists (the DHCP server does not seem to purge them immediately), the wrong IP will be shown. So for static mappings, you currently have to always set the name manually.
Fixes for those things are already committed, but as this was done already two weeks ago I temporarily forgot that they are not fixed in the 7.506 release. [;)]
Cheers,
andreas
okay, so i don't have another dhcp in between [:)] The point with multiple entries in the DHCP i recognized over the weekend, and you can see this multiple entries on the WLan client page ... but what i didn't get is why it doesn't show an name and a ip address?
iven it doesn't show a name, it should show the ip address or not?
hmmm do you have the fixes available so i maybe could try it bevor a official update is available?
This name-guessing magic only works once, when the wireless client is seen for the first time, because the client is then added to the configuration daemon. Afterwards, the information saved in the configuration daemon always overrides the information provided by the DHCP. Therefore, once the string is shown as REF_Xxy, you'll have to manually set a name for the client.
The IP address is probably not shown because you have a static mapping for this MAC. The name and the IP are not in any relationship except that they are both taken from the DHCP. If you use the DHCP server on the ASG, the IP should work. If you use a static DHCP mapping, the IP should be shown once you've the latest fixes. If you use any other DHCP server, you won't see an IP here.
Currently, we're not planning to pre-release any fixes, but maybe we'll decide differently if we're having a huge load of fixes in a couple of days. [;)]