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
syst
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 (
https://github.com/ltsp/
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 a
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 Bhur
> 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.
The
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 O
On Mon, 25 Oct, 2021, 01:24 Matthias May via Dnsmasq-discuss, <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:
In your case you are using an IP address as hostname which is not a valid
host
the problem here is the client looks to be misconfigured if it is telling
the server its name is an I
On Mon, 25 Oct, 2021, 01:24 Matthias May via Dnsmasq-discuss, <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:
> On 21/10/2021 13:05, Shrenik Bhura wrote:
> > May be the code that logs this line needs to be checked if it is just
> printing part of the complete hostname i.e. IP
> > address.
> >
>
On 10/21/21 7:05 AM, Shrenik Bhura wrote:
DHCP Request
> Server-ID (54), length 4: 192.168.67.1
> Requested-IP (50), length 4: 192.168.67.53
> Hostname (12), length 13: "192.168.67.53"
Client says "My hostname is '192.168.67.53'"
[...]
On 21/10/2021 13:05, Shrenik Bhura wrote:
> May be the code that logs this line needs to be checked if it is just
> printing part of the complete hostname i.e. IP
> address.
>
Hi Shrenik
The code is doing what it is supposed to do.
Please take a look at the definition of a hostname and what ma
On Thu, 21 Oct 2021 at 03:04, Geert Stappers via Dnsmasq-discuss <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:
> On Wed, Oct 20, 2021 at 10:56:02PM +0200, Geert Stappers wrote:
> > On Wed, Oct 20, 2021 at 02:48:27PM +0530, Shrenik Bhura wrote:
> > > On Wed, 20 Oct, 2021, 11:21 Geert Stappers w
On Wed, Oct 20, 2021 at 10:56:02PM +0200, Geert Stappers wrote:
> On Wed, Oct 20, 2021 at 02:48:27PM +0530, Shrenik Bhura wrote:
> > On Wed, 20 Oct, 2021, 11:21 Geert Stappers wrote:
> > > On Wed, Oct 20, 2021 at 07:50:58AM +0530, Shrenik Bhura wrote:
> > > > There isn't anything specific in the co
On Wed, Oct 20, 2021 at 02:48:27PM +0530, Shrenik Bhura wrote:
> On Wed, 20 Oct, 2021, 11:21 Geert Stappers wrote:
> > On Wed, Oct 20, 2021 at 07:50:58AM +0530, Shrenik Bhura wrote:
> > >
> > > Hi Dominik,
> >
> > Hello Archive visitor,
> > Hello Mailinglist subscriber,
> >
> >
> > > There isn't an
On Wed, 20 Oct, 2021, 11:21 Geert Stappers via Dnsmasq-discuss, <
dnsmasq-discuss@lists.thekelleys.org.uk> wrote:
> On Wed, Oct 20, 2021 at 07:50:58AM +0530, Shrenik Bhura wrote:
> > On Tue, 19 Oct 2021 at 21:01, Dominik Derigs wrote:
> >
> > > Hey Shrenik,
> > >
> > > On Tue, 2021-10-19 at 17:20
On Wed, Oct 20, 2021 at 07:50:58AM +0530, Shrenik Bhura wrote:
> On Tue, 19 Oct 2021 at 21:01, Dominik Derigs wrote:
>
> > Hey Shrenik,
> >
> > On Tue, 2021-10-19 at 17:20 +0530, Shrenik Bhura wrote:
> > > Option 12 hostname sent to RPi is the first octet of the IP
> > > address. This seems incor
Hi Dominik,
There isn't anything specific in the configuration that serves the
hostname. I am aware of this feature and when defined it works as desired.
But when nothing is explicitly defined to serve hostnames, it is defaulting
to 192 as visible in the logs, and only in the case of an RPi.
When
Hey Shrenik,
On Tue, 2021-10-19 at 17:20 +0530, Shrenik Bhura wrote:
> Option 12 hostname sent to RPi is the first octet of the IP
> address. This seems incorrect.
This can very well be desired behavior (if the hostname is set to
"192"). Can you quote your configuration and related files (e.g.
i
Option 12 hostname sent to RPi is the first octet of the IP address. This
seems incorrect.
For example, if the IP address is 192.168.67.53, the value visible in the
logs is -
*Oct 19 16:38:49 server dnsmasq-dhcp[14224]: 1870967312 sent size: 3
option: 12 hostname 192*
and so is in the value in /
19 matches
Mail list logo
