OnHub (TPLink) OpenWrt Install - Connection Refused

Hi all,

First time OpenWRT user here doing my first install on a TPLink OnHub router.

I've followed the website's guide and everything seems to have gone well except for getting access to the device via ssh.

Current state is:

  • Device is powered
  • LED ring is multi-colored (rainbow / red green blue etc)
  • USB, flashed with balenaEtcher and the correct .bin file
  • Device is plugged into a network switch which indicates it is active
    • tracert from my Win11 cmd prompt actually shows OpenWRT in the listing:
>tracert 192.168.86.232

Tracing route to OpenWrt.lan [192.168.86.232]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  OpenWrt.lan [192.168.86.232]

Trace complete.

However when I attempt to ssh to this device, I simply get connection refused:

 ssh root@192.168.86.232
ssh: connect to host 192.168.86.232 port 22: Connection refused

SSH is occuring from a different device on the same network which can also see the IP.

Nmap ran and I think this shows why I can't connect, but I don't really know what to do about it:

# nmap -v 192.168.86.232
Starting Nmap 7.92 ( https://nmap.org ) at 2023-03-04 05:37 UTC
Initiating ARP Ping Scan at 05:37
Scanning 192.168.86.232 [1 port]
Completed ARP Ping Scan at 05:37, 0.05s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 05:37
Completed Parallel DNS resolution of 1 host. at 05:37, 0.00s elapsed
Initiating SYN Stealth Scan at 05:37
Scanning 192.168.86.232 [1000 ports]
Increasing send delay for 192.168.86.232 from 0 to 5 due to 22 out of 72 dropped probes since last increase.
Increasing send delay for 192.168.86.232 from 5 to 10 due to 11 out of 16 dropped probes since last increase.
Increasing send delay for 192.168.86.232 from 10 to 20 due to 11 out of 11 dropped probes since last increase.
Increasing send delay for 192.168.86.232 from 20 to 40 due to 11 out of 11 dropped probes since last increase.
Completed SYN Stealth Scan at 05:37, 38.47s elapsed (1000 total ports)
Nmap scan report for 192.168.86.232
Host is up (0.0013s latency).
All 1000 scanned ports on 192.168.86.232 are in ignored states.
Not shown: 1000 closed tcp ports (reset)
MAC Address: 18:A6:F7:E0:61:81 (Tp-link Technologies)

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 38.67 seconds
           Raw packets sent: 1085 (47.724KB) | Rcvd: 1001 (40.028KB)

Specifically the message:

All 1000 scanned ports on 192.168.86.232 are in ignored states.

Would love any help you can offer.


Just another edit:
I ran another nmap specifically against port 22:

# nmap -p 22 192.168.86.232
Starting Nmap 7.92 ( https://nmap.org ) at 2023-03-04 05:52 UTC
Nmap scan report for 192.168.86.232
Host is up (0.0015s latency).

PORT   STATE  SERVICE
22/tcp closed ssh
MAC Address: 18:A6:F7:E0:61:81 (Tp-link Technologies)

Nmap done: 1 IP address (1 host up) scanned in 0.20 seconds

OpenWRT usually uses 192.168.1.1 ... so ...

1 Like

I did see some examples where booting into dev mode on the OnHub made it reachable on 192.168.86.1 ...

But you're right the guide indicates 192.168.1.1.

Would this be something statically set inside the boot image that I won't be able to change until I've loaded it onto the device and can gain access?

If it is trying to listen on 192.168.1.1, is there any way to gain access to that subnet from my ...86.0/24 subnet?

a pc set to the defaut dhcp setting on it's lan port
will get an IP in the rage of 192.168.1.2 > 192.168.1.254
and you can the access to openwrt on 192.168.1.1

1 Like

Does that device not need to have a gateway on that subnet as well?

1 Like

by default like all routers it has a built in dhcp server it will give you pc it's ip & subnet mask
and give itself as the gateway & dhcp sever
as stated it's ip is 192.168.1.1 with subnet of 255.255.255.0 on in new format 192.168.1.1/24

there is a note as the onhub's are only in the master branch atm
Luci the web interface is not installed by default on shanpshots
you will have to do this via ssh unless you compile it in your seft

1 Like

Ok so currently I have the OnHub booted again back into rainbow LEDs and connected only to one device.

[Laptop] <---ethernet cable---> [OnHub]

I've tried:

Setting the network card to automatically obtain an IP

This gives me a very unusual IP address - 192.254.91.103
A Subnet mask of 255.255.0.0
A blank default gateway

Setting the network card to statically have ip 192.168.1.2

This shows as having the correct IP as you'd expect.
But still has a blank default gateway.

In both cases I am unable to ping 192.168.1.1
In the second case it seems obvious - I'm not on that subnet.

seems weird I have never seen 10.254.x.x/16 subnet
I'm guessing you tried the other port on the onhub
I do note they are not labelled very well

it takes a little while even after the RGB led's
did you repeatedly get 10.254.x.x/16 ?
I can't think of anything else to try atm

Thanks for your patience with me Lucky1,

So.. I've had some success.

As you pointed out there is another port. I had been plugged into the bottom port of the 2 ethernet ports (the one labelled with a globe icon).

I also reverted my laptop to use a static IP of 192.168.1.3

I have now been able to SSH into the device and get a prompt with the root user.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.