S
S
sazhyk2017-01-13 18:24:35
linux
sazhyk, 2017-01-13 18:24:35

Different configs for different Dnsmasq clients?

There is a server with debian 8 onboard. Acts as a gateway. The dhcp/dns/tftp is dnsmasq. Tftp is used for thin clients. Thin clients (old pieces of iron, read got a second life) are running Thinstation 2.2. Everything was fine, everything worked. There was a need to add a workplace, and here a problem arose. The old thinstation assembly did not have modules for the new client's video card. No problem. I decided (this question has been brewing for a long time) to update the image, to the latest, Thinstation 5.4. No sooner said than done. But. Now another problem has arisen - one of the old clients is very old, and the new thinstation did not have drivers for the old Ati Radeon R9250.
Now I am faced with a choice: either the old hardware and the old thinsration image, but without a new machine on the network, or a new image and a new machine, but without the old piece of iron, which is still coping with its task.
In this connection, the question arose: is it possible to write different dnsmasq configs for different clients, in which to give different files via tftp?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
K
Konstantin ™, 2017-01-13
@sazhyk

I won’t tell you the exact recipe, but I think that you need to dig towards determining the MAC address of the thin client and, depending on the MAC, give the desired image of version 2.2 or version 5.4.
Here is an example of uploading different loaders depending on the architecture of the client station.
I think you need to read more about the options:

pxe-service
dhcp-match
dhcp-boot

UPD: solution to the problem in the comments

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question