Hi All! OpenWrt is really amazing! Thanks so much for all the developers do on this and thanks in advance!
Quick question, to keep moving forward with running OpenWrt.....
I was able to build a fresh OpenWrt image for G-iNet GL-MT300N-V2 and flash the router with fresh build/image from github specifically in accordance with https://openwrt.org/toh/gl.inet/gl.inet_gl-mt300n_v2. Yay! (Built with debian.)
I'm perfectly able to ssh into the box 192.168.1.1 and change the settings (e.g. enable new ssid, unhide ssid broadcast, add firewall rules, etc). There are no issues connecting to the GL box running OpenWrt via WiFi, either.
However, I'm still having issues connecting to LuCI via http://192.168.1.1/index.html?index and still having issues seeing any actual internet traffic flow through wifi router. It feels like a firewall issue, but thought to reach out to the pros after hours of trouble shooting. Perhaps Forwarding needs to be configured.
Any advise on which rabbit hole to go down next would be most appreciated! Thanks a ton in advance!
With a routed client the WAN IP (from the main router) needs to be in a different subnet range than the LAN IP. For example if they are both 192.168.1.X it can't route out to the Internet.
Thanks so much, MPA! This is very helpful!
RE#1 - Yes, great idea about stable version, thank you. I will try it after working more on fresh build. It would be great to showcase a fresh build to a few new learners in the field.
RE#2 - Is there a way to tell if LuCI is in build? It is in the config menu but wasn't sure we needed to set anything from links off openwrt.org/docs/guide-developer/start. If I recall correctly the browser simply indicates connection refused. (Aside, by the way, sorry in advance for any delay in response this week+. I had to pull my lab apart from a hard computer crash (wouldn't even boot) for a week+ but will be back when new device arrives/installed.)
Thanks so much, MK24!!! This is also very helpful!
RE# I'll check the IPs. The config of stock firmware worked fine (i.e. traffic flowed fine between ports). Then after fresh build traffic wasn't moving so figured maybe this setup is missing a config component with new firmware.
The device firewall rules are below (the plan is to lock it back down once it's up and running perhaps even after another rebuild):
Hi MPA! Thanks so much! I think you are correct! I'm getting a fail on both the opkg and netstat queries as seen below.
BusyBox v1.31.1 () built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r12089-5f4f269ce1
--------------------------------------------------
root@OpenWrt:~# opkg list-installed | egrep "luci|uhttpd"
root@OpenWrt:~# netstat -ltnp | egrep ':(80|443)\>'
root@OpenWrt:~# exit
The last command will open a menu.
If you want to build images for the “TL-WR841N v11” Wifi-Router, select:
“Target System” ⇒ “Atheros AR7xxx/AR9xxx”
“Subtarget” ⇒ “Devices with small flash”
“Target Profile” ⇒ “TP-LINK TL-WR841N/ND v11”
In the menu, select Exit and then Yes to save your settings. Now build the images. That may take some time:
make
Afterwards, the images can be found in ./bin/targets/ar71xx/generic/ - done.
The *-factory.bin images are for the first installation.
The *-sysupgrade.bin images are for the updating existing OpenWrt installations.
Perhaps more needs to be enabled/configured than the above for LuCi on GL-iNet?
