user131406: Currently, I am following the recommendation of running a full node on my desktop with bitcoind; it has most of the blockchain downloaded (~680000 blocks) and is not pruned. Then I have two laptops that I will be running bitcoin-qt on that will only connect to my full node. Unfortunately, I am having trouble with bitcoind sending the index and blocks to the inbound connections from the bitcoin-qt laptops. My configuration files, node info, and peer info are included below. Thanks for your suggestions.
desktop bitcoind /etc/bitcoin.conf
rpcauth=root:******
rpcauth=_bitcoind:******
[main]
[test]
[signet]
[regtest]

laptop bitcoin-qt ~/.bitcoin/bitcoin.conf
connect=192.168.1.197:8333

desktop bitcoind daemon control script /etc/rc.d/bitcoind
#!/bin/ksh
#
# $OpenBSD: bitcoind.rc,v 1.2 2018/07/15 22:03:50 bentley Exp $

daemon="/usr/local/bin/bitcoind"
daemon_timeout="300"
daemon_user="_bitcoind"

datadir="/home/bitcoin"
conf="/etc/bitcoin.conf"
daemon_flags="-daemon -conf=$conf -datadir=${datadir}"

. /etc/rc.d/rc.subr

rc_reload=NO


rc_cmd $1

bitcoin-cli -getinfo to bitcoind on the desktop, it returns:
{
  "version": 210100,
  "blocks": 684628,
  "headers": 718323,
  "verificationprogress": 0.90065025371744,
  "timeoffset": -1,
  "connections": {
    "in": 2,
    "out": 1,
    "total": 3
  },
  "proxy": "",
  "difficulty": 25046487590083.27,
  "chain": "main",
  "relayfee": 0.00001000,
  "warnings": ""
}

When I run getpeerinfo in the bitcoin-qt console, I get:
[
  {
    "id": 0,
    "addr": "192.168.1.197:8333",
    "addrbind": "192.168.1.174:58377",
    "network": "not_publicly_routable",
    "services": "0000000000000409",
    "servicesnames": [
      "NETWORK",
      "WITNESS",
      "NETWORK_LIMITED"
    ],
    "relaytxes": true,
    "lastsend": 1642006419,
    "lastrecv": 1642006299,
    "last_transaction": 0,
    "last_block": 0,
    "bytessent": 693,
    "bytesrecv": 18317,
    "conntime": 1642005880,
    "timeoffset": 0,
    "pingtime": 0.002229,
    "minping": 0.001617,
    "pingwait": 6.439448,
    "version": 70016,
    "subver": "/Satoshi:0.21.1/",
    "inbound": false,
    "bip152_hb_to": false,
    "bip152_hb_from": false,
    "startingheight": 684595,
    "synced_headers": -1,
    "synced_blocks": -1,
    "inflight": [
    ],
    "addr_processed": 1003,
    "addr_rate_limited": 0,
    "permissions": [
    ],
    "minfeefilter": 0.09170997,
    "bytessent_per_msg": {
      "feefilter": 32,
      "getaddr": 24,
      "getheaders": 93,
      "ping": 160,
      "pong": 96,
      "sendaddrv2": 24,
      "sendcmpct": 66,
      "sendheaders": 24,
      "verack": 24,
      "version": 126,
      "wtxidrelay": 24
    },
    "bytesrecv_per_msg": {
      "addrv2": 17773,
      "feefilter": 32,
      "ping": 96,
      "pong": 128,
      "sendaddrv2": 24,
      "sendcmpct": 66,
      "sendheaders": 24,
      "verack": 24,
      "version": 126,
      "wtxidrelay": 24
    },
    "connection_type": "manual"
  }
]


user131406: It seems that the whole blockchain has to be synced before it will send the index and blocks to inbound requests.
Explained in this issue: https://github.com/bitcoin/bitcoin/issues/6971

131406: <p>Currently, I am following the recommendation of running a full node on my desktop with bitcoind; it has most of the blockchain downloaded (~680000 blocks) and is not pruned. Then I have two laptops that I will be running bitcoin-qt on that will only connect to my full node. Unfortunately, I am having trouble with bitcoind sending the index and blocks to the inbound connections from the bitcoin-qt laptops. My configuration files, node info, and peer info are included below. Thanks for your suggestions.</p>
<p>desktop bitcoind <code>/etc/bitcoin.conf</code></p>
<pre><code>rpcauth=root:******
rpcauth=_bitcoind:******
[main]
[test]
[signet]
[regtest]
</code></pre>
<p>laptop bitcoin-qt <code>~/.bitcoin/bitcoin.conf</code></p>
<pre><code>connect=192.168.1.197:8333
</code></pre>
<p>desktop bitcoind daemon control script <code>/etc/rc.d/bitcoind</code></p>
<pre><code>#!/bin/ksh
#
# $OpenBSD: bitcoind.rc,v 1.2 2018/07/15 22:03:50 bentley Exp $

daemon=&quot;/usr/local/bin/bitcoind&quot;
daemon_timeout=&quot;300&quot;
daemon_user=&quot;_bitcoind&quot;

datadir=&quot;/home/bitcoin&quot;
conf=&quot;/etc/bitcoin.conf&quot;
daemon_flags=&quot;-daemon -conf=$conf -datadir=${datadir}&quot;

. /etc/rc.d/rc.subr

rc_reload=NO


rc_cmd $1
</code></pre>
<p><code>bitcoin-cli -getinfo</code> to bitcoind on the desktop, it returns:</p>
<pre><code>{
  &quot;version&quot;: 210100,
  &quot;blocks&quot;: 684628,
  &quot;headers&quot;: 718323,
  &quot;verificationprogress&quot;: 0.90065025371744,
  &quot;timeoffset&quot;: -1,
  &quot;connections&quot;: {
    &quot;in&quot;: 2,
    &quot;out&quot;: 1,
    &quot;total&quot;: 3
  },
  &quot;proxy&quot;: &quot;&quot;,
  &quot;difficulty&quot;: 25046487590083.27,
  &quot;chain&quot;: &quot;main&quot;,
  &quot;relayfee&quot;: 0.00001000,
  &quot;warnings&quot;: &quot;&quot;
}
</code></pre>
<p>When I run <code>getpeerinfo</code> in the bitcoin-qt console, I get:</p>
<pre><code>[
  {
    &quot;id&quot;: 0,
    &quot;addr&quot;: &quot;192.168.1.197:8333&quot;,
    &quot;addrbind&quot;: &quot;192.168.1.174:58377&quot;,
    &quot;network&quot;: &quot;not_publicly_routable&quot;,
    &quot;services&quot;: &quot;0000000000000409&quot;,
    &quot;servicesnames&quot;: [
      &quot;NETWORK&quot;,
      &quot;WITNESS&quot;,
      &quot;NETWORK_LIMITED&quot;
    ],
    &quot;relaytxes&quot;: true,
    &quot;lastsend&quot;: 1642006419,
    &quot;lastrecv&quot;: 1642006299,
    &quot;last_transaction&quot;: 0,
    &quot;last_block&quot;: 0,
    &quot;bytessent&quot;: 693,
    &quot;bytesrecv&quot;: 18317,
    &quot;conntime&quot;: 1642005880,
    &quot;timeoffset&quot;: 0,
    &quot;pingtime&quot;: 0.002229,
    &quot;minping&quot;: 0.001617,
    &quot;pingwait&quot;: 6.439448,
    &quot;version&quot;: 70016,
    &quot;subver&quot;: &quot;/Satoshi:0.21.1/&quot;,
    &quot;inbound&quot;: false,
    &quot;bip152_hb_to&quot;: false,
    &quot;bip152_hb_from&quot;: false,
    &quot;startingheight&quot;: 684595,
    &quot;synced_headers&quot;: -1,
    &quot;synced_blocks&quot;: -1,
    &quot;inflight&quot;: [
    ],
    &quot;addr_processed&quot;: 1003,
    &quot;addr_rate_limited&quot;: 0,
    &quot;permissions&quot;: [
    ],
    &quot;minfeefilter&quot;: 0.09170997,
    &quot;bytessent_per_msg&quot;: {
      &quot;feefilter&quot;: 32,
      &quot;getaddr&quot;: 24,
      &quot;getheaders&quot;: 93,
      &quot;ping&quot;: 160,
      &quot;pong&quot;: 96,
      &quot;sendaddrv2&quot;: 24,
      &quot;sendcmpct&quot;: 66,
      &quot;sendheaders&quot;: 24,
      &quot;verack&quot;: 24,
      &quot;version&quot;: 126,
      &quot;wtxidrelay&quot;: 24
    },
    &quot;bytesrecv_per_msg&quot;: {
      &quot;addrv2&quot;: 17773,
      &quot;feefilter&quot;: 32,
      &quot;ping&quot;: 96,
      &quot;pong&quot;: 128,
      &quot;sendaddrv2&quot;: 24,
      &quot;sendcmpct&quot;: 66,
      &quot;sendheaders&quot;: 24,
      &quot;verack&quot;: 24,
      &quot;version&quot;: 126,
      &quot;wtxidrelay&quot;: 24
    },
    &quot;connection_type&quot;: &quot;manual&quot;
  }
]
</code></pre>
 131406: <p>It seems that the whole blockchain has to be synced before it will send the index and blocks to inbound requests.</p>
<p>Explained in this issue: <a href="https://github.com/bitcoin/bitcoin/issues/6971" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/issues/6971</a></p>
