MAX BR1 LTE hw2 - what would be a expected/typical NMAP report?

Can someone point me to a source of information for expected results from a typical:

MAX BRE Model
Pepwave MAX BR1
Product Code
MAX-BR1-LTE-US
Hardware Revision
2

In particular I am verifying (since the product was obtained second hand) the NMAP output results of slow comprehensive scans

For firmware 8.0.0 - Which version of linux would be running?

It appears that DD_WRT comes up - is that a normal response via NMAP or is my Router OS replaced by DD-wrt firmware that is acting like a Pepwave interface from within the admin products web page config interface?

OS CPE: cpe:/o:linux:linux_kernel: . .**

OS details: ********** (Linux . .**)

Are these normal port results?
53/udp open domain (unknown banner: Version: recursive-main/22386077)
8008/tcp open http nginx

And who is the certificate authority of the default installed SSL certificate? Is it Comodo? and Previously before I upgraded to firmware 8.0.0 from 6.4.2 it was a GoDaddy certificate.
I believe I have captive portal off but this may just be showing the certificate installed even if its off:

ssl-cert: Subject: commonName=captive-portal.peplink.com

| Subject Alternative Name: DNS:captive-portal.peplink.com, DNS:www.captive-portal.peplink.com

| Issuer: commonName=COMODO RSA Domain Validation Secure Server CA/organizationName=COMODO CA Limited/stateOrProvinceName=Greater Manchester/countryName=GB

| Public Key type: rsa

| Public Key bits: 2048

| Signature Algorithm: sha256WithRSAEncryption

| Not valid before: 2014-11-18T00:00:00

| Not valid after: 2019-11-17T23:59:59

| MD5: 8 groups of 4 symbols

Second time I’ve seen this request I think. Still confused by it.

Are you worried someone sold a second hand device that is then somehow hacked / rooted and so you want to check its ‘nmap signature’ against someone else’s device?

1 Like

More leaning to:
hacked / rooted and so you want to check its ‘nmap signature’ against someone else’s device

Any word on this?

upgrade firmware to 8.0.1 and run a nmap scan again. Then we’ll see if anyone on here will furnish you with a scan from their device for comparison.