opsi-client mac address - wired to wireless

[bbain]

Hello All:

I've been using opsi to configure laptops at the school district I work for and it's been working great. Most of these are older laptops that don't have the ability to boot wirelessly so my process has been to bring each machine in, plug it into the network and reload the OS (Netboot product) and products. This is a huge time saver from the way we had previously been doing it.

I wanted to start testing the ability to push updates to the products out to the machines as they become available (such as updates to Firefox, Flash, etc.). However, it looks like the opsi config editor does not know how to communicate with the machines as soon as they are unplugged from the ethernet network and only on the wireless network. I'm assuming this is because the mac address is different now that they are connected wirelessly instead of wired.

Is there something I'm missing -- a configuration setting somewhere perchance? Something I can change? Do I need to re-install the clients once the initial reload of the laptops are finished (least ideal way of handling this)?

Any recommendations on this would be greatly appreciated.
In advance, many thanks!
Brent

[SisterOfMercy]

Configed only needs to know the new mac address when you are pushing installations, right? I think it would use the hostname/whatever and not only the mac address when starting up and running the login blocker.
Have you tested it and found out that it doesn't work?

[bbain]

I just verified this. I had a test machine sitting next to me:
I plugged it in to do the OS install, installed a couple of product packages but left some alone.
Then I unplugged the wired ethernet, verified it was on wirelessly.
Changed a product configuration requested action to "Setup"
Rebooted the machine. The login blocker popped up but it did not pick up any new software packages to install.

Right clicking on the package and choosing "Execute Now (on demand)" also times out.

Thoughts?
Brent

[dkoch]

Does the IP change when are connecting to the wireless network ?

If so try this setting in /etc/opsi/opsiconfd.conf

Code: Alles auswählen

        # If set to yes a client's ip address will be updated in the opsi database,
        # when the client connects to the service and authentication is successful.
        # Opsiconfd needs to be reloaded (SIGHUP) for changes to take effect.
        #
        # Default:
        #   update ip = no

        update ip = yes

[n.wenselowski]

Hello Brent,

you need to be able to reach the client from your server. This can be done either by IP or by FQDN.
Please have a look at the getting started, 3.4. Configure how the opsi-server gets the Client’s IP-Address.

The MAC is only needed to deploy an OS to your client. It is not needed for push installation.

Is the client on the wifi able to reach the opsi server?


With kind regards

Niko

[bbain]

Hello:

There were two settings mentioned in the documentation. It turned out, for our situation, the following seems to have solved the problem:
resolveHostAddress in hostcontrol.conf --> True (This had been set to false)
update ip in opsiconfd.conf --> yes (already set that way)

I had used the recommended setup (resolveHostAddress to False and update ip to yes). As soon as I switched things appear to have resolved themselves. One of the last steps performed is for the machine to join the domain. Once this is done, DNS is always up to date (as long as the laptops stay in contact with the domain controllers). Once I re-read the documentation it made sense. I hadn't re-read that since getting opsi up and running a couple months ago... focusing primarily on getting product scripts working.

I should probably go back and re-read the getting started documentation now that I have a better understanding of how it's working!
Thanks everyone.
Brent