I have bitcoind serving cfilters to an LND node on my local network on separate machines. Both have `192.168.1.x` IP addresses and they connect fine using neutrino. However, the LND node does not appear in the `bitcoin-cli -netinfo` table.

The reason is because if you look at the `getpeerinfo` response:

```
{
  "id": 11728,
  "addr": "192.168.1.153:64367",
  "addrbind": "192.168.1.13:8333",
  "addrlocal": "192.168.1.13:8333",
  "network": "not_publicly_routable",
  "services": "0000000000000048",
  "servicesnames": [
    "WITNESS",
    "COMPACT_FILTERS"
  ],
...
```

...so bitcoin-cli ignores the peer here:

https://github.com/bitcoin/bitcoin/blob/9c47eb450346937b3d7ee21b9e669b5c91a7ed6c/src/bitcoin-cli.cpp#L477-L479

...expecting one of these strings only:

https://github.com/bitcoin/bitcoin/blob/9c47eb450346937b3d7ee21b9e669b5c91a7ed6c/src/bitcoin-cli.cpp#L58

I'm happy to fix / add this myself unless there's a reason? Maybe instead of skipping the peer we can just add an "unknown network" category, or "other" ...?

cc: @jonatack 
int status{0};
    int error{-1};
    std::string body;
};
static std::string http_errorstring(int code)
{
    switch(code) {
    case EVREQ_HTTP_TIMEOUT:
        return "timeout reached";
    case EVREQ_HTTP_EOF:
        return "EOF reached";
    case EVREQ_HTTP_INVALID_HEADER:
        return "error while reading header, or invalid header";
    case EVREQ_HTTP_BUFFER_ERROR:
        return "error encountered while reading or writing";
    case EVREQ_HTTP_REQUEST_CANCEL:
        return "request was canceled";
    case EVREQ_HTTP_DATA_TOO_LONG:
        return "response body is larger than allowed";
    default:
        return "unknown";
    }
}
static void http_request_done(struct evhttp_request *req, void *ctx)