On 10/27/21 12:15 PM, Geoff Back wrote:
You said, earlier on:
/"Nothing on the server is configured to set the same. The Raspberry Pi client
is netbooting, so nothing on the client side could be setting it."/
That's an invalid configuration. All Linux-based systems - in fact all POSIX
Hey Geoff,
I absolutely agree with your explanation.
So if dnsmasq is behaving the way it should and is not doing anything
special w.r.t. the RPis, then there is some other component in the Ubuntu
Mate 20.04 image that may be playing truant.
Quoting from the ltsp issue (
Hi Shrenik,
On 27/10/2021 16:38, Shrenik Bhura wrote:
> Hi Geoff,
>
> I don't expect it to at all set a hostname.
I think this sentence points to the very heart of your problem.
I have been following this thread in detail. Everything indicates that
the RPI device is getting an IP address set
Hi Geoff,
I don't expect it to at all set a hostname. But yet something involved in
the entire transaction is doing so i.e. setting the IP address as the
hostname and in doing so it is getting it all wrong.
Kindly read the thread to understand what's exactly going on.
Regards,
Shrenik
On Wed,
Hi Shrenik,
Looking at that configuration file I see nothing that specifies the host
name that the RPI device should initialise itself with. Where do you
expect it to obtain a hostname from, and what specific hostname are you
expecting to set?
Regards,
Geoff.
On 27/10/2021 14:06, Shrenik
> but my rpi machines received hostname set from dnsmasq. I used static
allocations only for my testing.
Try without setting any.
> Can you share at least relevant part of dnsmasq configuration?
Config file attached below.
> Does it have dhcp-host record for that machine?
No, it doesn't.
Hi,
I would try tomorrow, but my rpi machines received hostname set from
dnsmasq. I used static allocations only for my testing. Can you share at
least relevant part of dnsmasq configuration?
Does it have dhcp-host record for that machine?
On 10/25/21 16:00, Shrenik Bhura wrote:
>
> On Mon, 25
