I suppose establishing the state of your devices would be the first thing to check.
How do you know that ethernet ports are active? (I suppose some lights turn on somewhere?)
Are you connecting the switch to the correct ethernet port for the OnHub device? Remember, there are two ports, and you want to use the "LAN" port. (This will allow OnHub to act as a DHCP server to your laptop.)
What are the network interface configurations and routes on your laptop? If your interfaces are down, and/or routes not configured correctly, your packets may not be going towards the router.
Have you tried connecting a known-good device to your switch and contacting that with your laptop instead? This will establish whether the laptop side of your setup is working.
Have you verified that the switch connection is correct? (Is there something hosted on the switch, that you could ping instead?)
How do you know that ethernet ports are active? (I suppose some lights turn on somewhere?)
Yeah lights are on.
Are you connecting the switch to the correct ethernet port for the OnHub device? Remember, there are two ports, and you want to use the "LAN" port. (This will allow OnHub to act as a DHCP server to your laptop.)
Yes. I double checked this.
What are the network interface configurations and routes on your laptop? If your interfaces are down, and/or routes not configured correctly, your packets may not be going towards the router.
I tried default automatic DHCP., which works fine connected to my peplink router.
Have you tried connecting a known-good device to your switch and contacting that with your laptop instead? This will establish whether the laptop side of your setup is working.
I connected the switch into my main switch and the laptop works fine.
Have you verified that the switch connection is correct? (Is there something hosted on the switch, that you could ping instead?)
If I just hook the laptop to the switch and my switch to my main switch then I can ping some of my other devices on my main network.
Did you wipe the drive fully before writing the image to it? I've had the same issue before where I couldn't get any connection. When you write the image to the USB drive with dd add 'bs=1M' to the command. This has helped me in the past.
the lan interface in the <---> marked one
the other has a round kinda glob image that's internet
yes I would try the reset button on the usb
and the flash if you have installed openwrt b4
so a while after the red/green/blue leds show up
press the reset button
Yeah I have the ethernet cabled plugged into the right spot. I have never installed openwrt on this, but I am going to give the reset a try. You never know.
I got it working! I guess in my case, the magic sauce was resetting the onhub to factory defaults. Once I did that, everything worked as it should following the instructions.
I just successfully flashed my TP-LINK and wanted to chime in as I encountered.
I'm on Mac OS 14.1.2, MacBook Pro 2019 16"
At first I was getting the red/orange ring. I then tried the "ctrl+d" keyboard thing and the router would get stuck on a blinking purple ring.
I did some more researching and I found somewhere in this post someone mentioned using either "dd" or a program called Balena Etcher. Having tried "dd" a bunch of times and continuing to get to either the red/orange or to the blinking purple ring, I decided to give it a shot. I re-downloaded the image again and I also downloaded Balena Etcher. I put the image on my USB drive using Etcher and then went through the instructions again (without the keyboard), and that worked, I got the rainbow ring.
Not sure what etcher is doing right that "dd" isn't doing, I think maybe it has to do with getting the right "/etc/...." id. I maybe wasn't getting the right one? who knows. it works now so I'm done with this part. Now I just need to set things up for what I need it for.
I've had some problems on my fault while upgrading to 24 version then configuring my OnHub TP-Link, but want to talk all involved how well it's working and specially the reset button when you have troubles. I had this OnHub lost in some box, now it's serving me again with OpenWRT, it's amazing! Thank you all!
I have an Onhub TP Link AC 1900 router. Post Google's withdrawal of support, I installed OpenWRT. It is working fine through the USB boot route. Every time the power gets interrupted, I follow the sequence as instructed by openwrt to reboot the router. I have been postponing burning the firmware on to the router itself as I needed to study and understand how SSH works on my Windows 11 laptop. I finally did some basic research on SSH and tried to burn the firmware on to the router's memory so that I can do away with the USB reboot. I could carry out the first step and scp the file on to the \temp folder on the router using the following command -
You are right that the "" in the command line is redundant and is the cause of the error message. I had removed that and gave a contiguous command that worked. Now the firmware is installed on to the eMMC and the router boots up without the USB.
However, I have a new set of problems -
The router is not showing on the wifi search of my laptop, but connects through the lan cable. It is also connecting me to internet. I tried accessing the router through the IP address (192.168.1.1), so that I can switch on the radio signals through restore backup of an earlier config, it is not connecting.
I also tried to zero out the eMMC but since the firmware is already written on to it, the commands are not working. Perhaps I need to redo the entire process from scratch and zero out the eMMC before writing the firmware on to it.
Can you please confirm 1. if my thinking is right 2. if the two zero out commands are to be given separately or together in one line
Don’t zero the eMMC if it’s working (duh). Just read the wiki carefully. It’s easy to make mistakes. Start another thread on any other issues you have. You got the firmware installed. At this point, it’s easier to flash custom firmware and get it working the way you want.
You have to turn on the radio through the Luci, network, wireless interface, or edit /etc/config/wireless file and enable the radio by setting the flag to 1. It’s zero by default.