QNET - problem with hostnames containing dots

Dear QSSL team,

we (better: one of our customers) found, that dots in the hostname
cause problems: the node is no longer accessible via QNET.

The dot was entered in the ‘ID’ field of the DHCP configuration of the
‘phlip’ utility.

The hostname is shown under /net but it is not accessible.

This applies to V6.2.1 and 6.30beta (therefore X-post to
q.p.beta.630).



Mit freundlichen Grüßen aus Krefeld,
With best regards from Krefeld,

MBS GmbH
Karsten Hoffmann


MBS GmbH E-Mail: karsten.hoffmann@mbs-software.de
Römerstraße 15 Tel: +49 / 2151 / 72 94-38
D-47809 Krefeld Fax: +49 / 2151 / 72 94-50
http://www.mbs-software.de Mobil: +49 / 172 / 38 12 373

Karsten P. Hoffmann <karsten.hoffmann@mbs-software.de> wrote:

Dear QSSL team,

we (better: one of our customers) found, that dots in the hostname
cause problems: the node is no longer accessible via QNET.

Can you give more details? If you mean a hostname of “my.node” which
would be in a domain of “qnx.com”, to give a fqn of “my.node.qnx.com”,
I would definitely expect this to fail. The dot is a seperator, so I
don’t think it would be a valid character within a name.

But, if you mean “mynode” in “qnx.com”, giving “mynode.qnx.com” as
the fqn, and that failing, it is a problem.

-David

The dot was entered in the ‘ID’ field of the DHCP configuration of the
‘phlip’ utility.

The hostname is shown under /net but it is not accessible.

This applies to V6.2.1 and 6.30beta (therefore X-post to
q.p.beta.630).



Mit freundlichen Grüßen aus Krefeld,
With best regards from Krefeld,

MBS GmbH
Karsten Hoffmann


MBS GmbH E-Mail: > karsten.hoffmann@mbs-software.de
Römerstraße 15 Tel: +49 / 2151 / 72 94-38
D-47809 Krefeld Fax: +49 / 2151 / 72 94-50
http://www.mbs-software.de > Mobil: +49 / 172 / 38 12 373


David Gibbs
dagibbs@qnx.com

David Gibbs wrote:

Karsten P. Hoffmann <> karsten.hoffmann@mbs-software.de> > wrote:
Dear QSSL team,

we (better: one of our customers) found, that dots in the hostname
cause problems: the node is no longer accessible via QNET.

Can you give more details? If you mean a hostname of “my.node” which
would be in a domain of “qnx.com”, to give a fqn of “my.node.qnx.com”,
I would definitely expect this to fail. The dot is a seperator, so I
don’t think it would be a valid character within a name.

Sorry for being unclear!

I mean: the customer entered something like ‘my.node’ in the ‘ID’
field of phlip’s DHCP configuration screen. Then the fq hostname became
‘my.node.internal’ and networking fails.

From my point of view, phlip should reject dots (and other invalid
characters) in the ID or hostname fields …

\

Karsten P. Hoffmann <karsten.p.hoffmann@web.de>
“I love deadlines. I especially like the whooshing sound
they make as they go flying by.”
[In memoriam Douglas Adams, 1952-2001]

Karsten P. Hoffmann <karsten.p.hoffmann@web.de> wrote:

David Gibbs wrote:
Karsten P. Hoffmann <> karsten.hoffmann@mbs-software.de> > wrote:
Dear QSSL team,

we (better: one of our customers) found, that dots in the hostname
cause problems: the node is no longer accessible via QNET.

Can you give more details? If you mean a hostname of “my.node” which
would be in a domain of “qnx.com”, to give a fqn of “my.node.qnx.com”,
I would definitely expect this to fail. The dot is a seperator, so I
don’t think it would be a valid character within a name.

Sorry for being unclear!

I mean: the customer entered something like ‘my.node’ in the ‘ID’
field of phlip’s DHCP configuration screen. Then the fq hostname became
‘my.node.internal’ and networking fails.

From my point of view, phlip should reject dots (and other invalid
characters) in the ID or hostname fields …

Ah, yes. That is probably a good thing for phlip to do.

I will PR this against phlip.

PR 19895.

-David

David Gibbs
dagibbs@qnx.com