Oh wow...I didn't expect that. The requirement to use the Firmware Selector comments should have raised curiosity.
I wonder why the OP did this to thier device.
I’m starting to lose track here.
I’ve not renamed anything. I’m not renaming anything since I can’t even access the device so cannot configure anything on it.
I have a DHCP server on the laptop and I have one on the LAN.
When I flashed my own build, it nabbed a DHCP IP from the laptop and from the LAN depending on which I had the router connected to but I think the flash didn’t work because even though it picked up an IP, I could not even ping the device.
Next, when I flashed it with the factory .img build, it comes back with 192.168.1.1 but no open ports and no, it’s not using DHCP at this point because it’s a factory build.
Now I don’t recall at this point if the factory build does have at least one DHCP interface but either way, the only usable IP is 192.168.1.1 but no open ports.
Ok... so then the device has no DHCP server running and no address without an upstream
DHCP server.
The router has nothing configured on it since I can’t access it and I don’t know if the factory build has a DHCP server on it for AP access for example but I assume it does. Also, no AP comes up after factory flashing it either. I mention this in case it should come up.
>Out of curiosity, why did you do this? What is your use-case for the B3000? Is it an AP only?
Why did I do what? The B3000 will be used as an AP eventually.
It's really not clear what you have done here...
You have two DHCP servers running? That's quite unusual and not recommended.
A default image should have ssh open. Something is wrong if it doesn't -- are you sure you flashed a true default image with no modifications? Where did it come from? How exactly did you flash it? How are you connecting to the device?
It must have a configuration, but it's not clear what you've done or where the image came from.
It should not come up. OpenWrt has wifi disabled by default.
Why did you set it as DHCP client? Yes, this can be done, but you've clearly done something that isn't working.
Ok... Good to know.
Here's what I would recommend:
-
use the B3000's recovery mechanism to install the GL-inet vendor firmware. Make sure that you can get into the user interface after that finishes.
-
Download and install the unmodified image from the firmware selector. Since the B3000 is currently only supported in snapshot, you'll download the sysupgrade image from here. Do not customize this at all. When you perform the upgrade, be sure that you do not keep settings since the vendor firmware's configuration files will be incompatible with official OpenWrt.
-
Once the flashing has completed, you should be able to connect to OpenWrt via the lan port (connected directly to your computer) at 192.168.1.1 -- only ssh will be available until you install LuCI.
Nope, I did not say I have two dhcp servers running on the same network.
I said I have a small DHCP server/service on the laptop which is not connected to the LAN and I have a pfsense firewall that has a DHCP server that servers all LAN devices.
The router I’m working on is connected to the laptop which is not connected to the LAN.
I’m not sure why this post is getting so complicated. It’s like some of you are hell bent on finding things I’ve done wrong :).
A default image should have ssh open.
Yes, exactly, which is why I’m posting about the problem. I flashed exactly the file I was given onto the router. No mods, no nothing special at all.
It came from the link I was given;
How are you connecting to the device?
As I said earlier, the router is connected to a laptop that is not connected to the LAN, it is stand alone and is what I always use to flash openwrt onto routers.
It must have a configuration, but it's not clear what you've done or where the image came from.
Again, I’ve not done anything special. I downloaded the file, put the router into recovery mode and flashed it. Nothing else and no open ports.
WiFi is disabled in factory build, got it.
Why did you set it as DHCP client? Yes, this can be done, but you've clearly done something that >isn't working.
I built my own build using Image Builder. Nothing special other than changing the network file to use DHCP instead of having the fixed 192.168.1.1. But that is a moot point because it didn’t work anyhow and I went back to the factory .img I downloaded at the link above.
use the B3000's recovery mechanism to install the GL-inet vendor firmware. Make sure
that you can get into the user interface after that finishes.
I can try that but I was told in another post to use the factory openwrt build, not the gl.inet which is what it was when I started.
Again, I do not customize anything, I’m flashing what I’m downloading, nothing more :).
I never keep settings when I flash.
Once the flashing has completed, you should be able to connect to OpenWrt via the lan port >(connected directly to your computer) at 192.168.1.1 -- only ssh will be available until you
install LuCI.
Yes, that’s the default method. When I receive a gl.inet router, it always has their fw on it and I connect to the WiFi then go to advanced and flash the openwrt fw.
I never install LuCI, I only use command line once I gain access.
I’ll find the gl.inet build then I’ll give this another try.
I think the reason this is so confusing is that you said things like this:
and this:
among many other things. We have been having trouble following which builds you've used and what the outcome of each has been....
We've also had trouble understanding how this is connected to the computer and/or the network.
You shouldn't have a DHCP server running on the interface that is being used to connect to the OpenWrt device.
We are and we aren't....
- we are: clearly something is not working properly and we are very confused about the conditions that have brought you to this point. We know that this should work without issue, but something you're doing is not working... we just can't figure out what since we don't have sufficient information about your process and setup.
- we aren't: we're not trying to blame you, just identify the problem. You're the only one who understands what has been flashed, how, and when. You're also the only one who knows how this device has been connected to a network/computer and what services are running in each place.
It is absolutely critical that you're working with what would be a vanilla config on a computer that is directly connected via ethernet to the lan port on the B3000. No DHCP servers on that computer, no wifi.... just one ethernet connection, dhcp client. Simple. You could use a live-USB boot of ubuntu for this purpose..... no extra services (and absolutely no DHCP servers).
The GL-inet image is here:
2 Likes
Sorry if my writing is not 100% clear, I am trying to provide what ever information you need. I’m not wanting you to have to guess. Yes, it should work without issue since I’ve flashed countless routers with openwrt. Every now and then, something like this does happen and only once I’ve exhausted everything I can think of do I ask for help.
You shouldn't have a DHCP server running on the interface that is being used to connect to the >OpenWrt device.
I don’t. I only enabled it when trying to find out if there was any kind of communications with the router. It’s disabled otherwise.
I flashed the gl.inet version. It did not ask me to save or not save settings.
After flashing, the usual gl.inet IP is 192.168.8.1 but in this case, it’s showing 192.168.30.1.
I am able to connect to the router using WiFi but that’s all.
There is no access again. Using nmap, there are no open ports.
Maybe I have a defective router here.
I mentioned 192.168.30.1. That now pings but there are no open ports.
I always believe I’m doing something wrong when these kinds of things happen but I’ve been posting every step that I take. This should be working right now.
It just took a while but now it’s normal, it’s up with 192.168.8.1 as it should be. The gl.inet build is now running.
I’ve gone to Advanced, luci gets installed and it’s now ready to be flashed again.
Ok... now, when you flash it:
- Use the sysupgrade image from the link I provided earlier (unmodified snapshot).
- If prompted (hopefully it will prompt), do not keep settings from the GL-inet config.
- Allow the flash to complete, then make sure your computer is connected via Ethernet to the lan port of the B3000. No other connections. Ensure your computer is not running a DHCP server and that the Ethernet port is set to be a DHCP client.
- Observe the DHCP issued address that you should get after the flashing is complete... it should be in the 192.168.1.0/24 network.
- ssh into your B3000 (
ssh root@192.168.1.1)
Just to confirm… I was told to use the factory image but you want me to use the sysupgrade one?
The upgrade process on the GUI is saying this;
Error: Mandatory section(s) missing from “/tmp/firmware.bin”. Abort… Image check failed.
The uploaded image file does not contain a supported format.
I selected the sysupgrade file I downloaded from above. Should I continue anyhow?
Oh, and, it keeps dropping me from wifi.
If it is giving you an error using the sysupgrade image, try the factory one. Do not force it.
1 Like
The default OpenWrt image has radio off by default.
Given this new information, I'm not sure it matters. To be clear, you're seeking assistance from the OpenWrt community regarding official images downloaded here, correct?
I'm not sure why we have constant uncertainty about which firmware you're using and how it's configured. That should be easy.
Your first post asked for a BIN file and is related to a past thread also discussing this (just to be clear). Follow the instructions for your device to eliminate confusion.
To be clear, I told @LarryPowel to install the GL-inet vendor firmware to get the device into a known working state. It seems to have worked (except that wifi was dropping,... that's not a good sign). But from there, the goal is to install official OpenWrt (snapshot since the device is not yet supported in a stable release build)... this is in progress AFAIK.
Because it's a different configuration (OpenWrt has WiFi disabled by default). 
(I assumed the OP successfully reflashed OpenWrt and lost WiFi due to default configuration, my bad.)
I think that the recovery mode used to install the gl-inet vendor firmware should have reset the configs to their default (specificallyy the default gl-inet configurations) to match the vendor firmware that was just installed (per my request/suggestion).
Yes, it likes the factory version and flashed it.
Now it pings 192.168.1.1 (laptop connected to LAN port on router) but no open ports.
Using nmap, there are no open ports.
Using ssh, I can actually reach it which tells me maybe the nmap tool is not working right but it won’t allow non password access. Usually, telnet is up to allow setting the root password but in this case, telnet is not up on the router.
Weird weird weird.
>(I assumed the OP successfully reflashed OpenWrt and lost WiFi due to default configuration,
my bad.)
The default OpenWrt image has radio off by default.
Yes, but it was the gl.inet firmware that was running when this was happening.I'm not sure why we have constant uncertainty about which firmware you're using and how it's >configured. That should be easy.
I’m not sure that everyone is unsure of this because I’ve mentioned it, shared the links explained eac step as I’ve done them :).
Based on this...
I would agree that nmap isn't working as expected.
What do you mean by this?
Telnet has not been installed on OpenWrt in maybe a decade now.
You should be able to ssh in with user root. there is no password. Make sure your ssh client is using the root user.
1 Like
I meant that in the past, telnet was enabled when the root password is not yet set.
In this case and as you said, it’s no longer done this way.
I did get in once I used ‘ssh root@192.168.1.1’ instead of ‘ssh 192.168.1.1’.
It seems all is good now.
I’m not 100% sure how things went bad since I’ve done so many things with this since the problem started but now I’m at a good starting point again.
Thank you all very much for all this help.
2 Likes