9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Marco Feichtinger <marco@germteig.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] PXE tftpload: file does not exist
Date: Sat, 22 Jul 2023 08:21:04 +0200	[thread overview]
Message-ID: <3606FCBC-A925-4D16-8699-E6875461F712@germteig.com> (raw)
In-Reply-To: <06365091-97D7-4447-863D-84E952CA320B@germteig.com>

The error was caused by a misconfigured ndb.
Thanks to Frank D. Engel Jr., which gave me the hint in a separat email.

So I played around with my ndb files, and concluded,… that I don’t quit understand how the ndb works.
Given following basic ndb configuration:
; cat /lib/ndb/local

#  files comprising the database, use as many as you like, see ndb(6)

#  because the public demands the name localsource
ip= sys=localhost dom=localhost

#  main network for home.csr.germteig.com
ipnet=main ip= ipmask=

#  server subnetwork
ipnet=srv ip= ipmask=

        ip= ether=<mac address>

        ip= ether=<mac address>
        ip= ether=<mac address>

        ip= ether=<mac address>
        ip= ether=<mac address>

With that, the cpu server boots just fine.
It reads its config file under /cfg/pxe/ and loads the kernel.

Now if I change the ip address of that cpu server to following:
        ip= ether=<mac address>
        ip= ether=<mac address>

Then I get the error "tftpload: file does not exist”.
But why?


> On 17.07.2023, at 22:25, Marco Feichtinger <marco@germteig.com> wrote:
> yes, ip/dhcpd and ip/tftpd are running on the file server
> -marco
>> On 17.07.2023, at 20:47, Steve Simon <steve@quintile.net> wrote:
>> are you running the tftp server?
>>> On 17 Jul 2023, at 4:38 pm, Marco Feichtinger <marco@germteig.com> wrote:
>>> I have a standalone file server, and a separate standalone auth server.
>>> I tried to pxe boot a cpu server.
>>> It gets the /386/9boot to load fine, but then it seems, that it can’t retrieve the file /cfg/pxe/<mac address> from my file server.
>>> here is the screen output during bootup:
>>>      9boot gz…starting protected-mode loader at 0x900020
>>> Plan 9 from Bell Labs PXE boot loader
>>> cpu0: 1800MHz GenuineIntel Atom (cpuid: AX 0x106CA DX 0xBFEBFBFF)
>>> ELCR: CC80
>>> #l0: i82598: 10Gbps port 0XFE980000 irq 11: <mac address>
>>> #l0: i82598: 10Gbps port 0XFE980000 irq 10: <mac address>
>>> 498M memory: 498M kernel data, 0M user, 18M swap
>>> pxe on ether0 .
>>> <sysname> (!69): /cfg/pxe/<mac address> .T.T.T.T.T.T.T.T.T.Ttftpread1st: failed to connect to server (!69)
>>> failed.
>>> tftpload: file does not exist
>>> Which is strange, because I did create the file on my file server.
>>> It looks like following:
>>>      bootfile=ether0!/386/9pccpuf
>>>      nobootprompt=tcp
>>>      readparts=1
>>>      mouseport=2
>>>      monitor=vesa
>>>      vgasize=1024x768x8
>>>      user=bootes
>>>      sysname=<sysname>
>>> Does anyone know what might be the problem?
>>> Thanks.
>>> -marco

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8484142ec51acbb7-M1d39b26008b7a69293810d6e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2023-07-22  6:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 15:37 Marco Feichtinger
2023-07-17 18:47 ` Steve Simon
2023-07-17 20:25   ` Marco Feichtinger
2023-07-22  6:21     ` Marco Feichtinger [this message]
2023-07-22 23:12       ` vic.thacker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3606FCBC-A925-4D16-8699-E6875461F712@germteig.com \
    --to=marco@germteig.com \
    --cc=9fans@9fans.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).