OMG, DO NOT use Chrome to try to flash DDWRT onto this router.
At first, I got to this lockout screen. Every valid address sent me here.
..then I just clicked wildly on it.. at random..
It brought me to some page to make a Linksys account to use their Smart Wifi auto setup thing.
Once on that account creation page, without making an account, I opened a new tab and tried to get into the router's stock firmware again. It finally let me sign in as admin admin and flash the router to DDWRT.
That worked.. sort of..
It put the base DDWRT onto the router, but I couldn't even give the network a name using the latest Google Chrome. After about ten seconds of using any screen in Chrome, the entire router will crash and become unresponsive.
-
..so, thankfully I do have a Firefox ESR installed. THAT worked like it was made to interface with DDWRT. I finally got to the firmware flash screen inside of the GUI and unlocked the full set of features.. that I'll probably never use.. lol..
I do like that it'll speedtest for you inside the GUI. That's really snazzy. It helped me set up the QOS more easily.
Happy you got it installed. Chrome is verified in multiple threads to be on the do-not-use list.
If you don't mind, could you please test connecting to an open wifi on this router when you have time. Do you get an IP address? There seems to be some discrepancy about this and we need more testing. If you live in a neighbourhood with lots of wifi interference this may be more difficult for security reasons. Just make a backup of your config and reset the router and the defaults should be good enough to test it. Just set the un/pw and you should be fine. Takes less than 5 minutes to test.
This includes you @yanek2412@gmail.com
Many thanks! _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
I'm going to buy another router. At least this is just $50 down the drain..
The router works as a plugged-in router.
Wireless doesn't work.
My phone says it's 'Saved / No Internet Access"
It also refuses to connect to my Blink doorbell.
I'm just too stressed out and short on time to waste more than four solid hours trying to get wireless to work.
All I wanted was a newer DDWRT-capable router than my 2009 one that just died. I didn't read this thread before I bought it, I read the https://wiki.dd-wrt.com/wiki/index.php/Supported_Devices that listed this as being supported. I don't know anything about what is new and what would be good to buy. There are like 28,000 routers on the market.
-
Can anyone recommend a ~$50 Linksys router, newer than 2009, that works with DDWRT and has a usable, fully functional build that works?
This is a newly adopted router. Patience is a virtue. Things will get fixed and you must realize this router has only just gotten support in the past two months. What did you expect? I bought this router to help test and eventually replace my main Gateway, an EA8500. I knew it wouldn't be all roses at first, but that's how it goes when you have a single developer supporting 350+ routers.
Does your wireless work okay with r56941? _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
..I just bought a router that I thought would work because it's on the list.
I need a router. I need a router now. Right now. This moment.
This one isn't ready right now.
Now I'm up four hours past my bed time trying to find a router on Amazon that works with DDWRT and then cross reference the forum so I can find out if it isn't actually functional, this moment.
We have been experiencing issues getting IP addresses on this router if the wifi has no password configured. If folks could try this and report back it would be very helpful. Also, if it doesn't work, try turning off Multicast to Unicast and see if that helps. This made no difference for me but was suggested by BS since it was recently defaulted to Enabled. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
Last edited by lexridge on Wed Jul 24, 2024 18:08; edited 1 time in total
r57447 has been very good on my MR7350. Wired performance thru the router out to the WAN 940 down / 940 up. Wired performance as a wireguard client is 800-875 down / 800-875 up - probably depending on how busy the wireguard server is (Mullvad). I'm using NSS-ECM.
Wifi 802.11ax is stable but only after I disabled all the features in the Roaming tab. Two issues with wifi:
1. my Macbook holds onto the 802.11ax radio even when the RSSI drops into the 80s and 90s, and there are other stronger 802.11ac radios nearby that it could switch to. It could be a "feature" of my MacBook (looks like my iPhone switches ok) but regardless, I have the "minimal signal for connection" at -80 on the 802.11ax radio, so the router should tell the MacBook to find another radio?
2. Wifi (802.11ax) performance from a wifi client talking over the wireguard oet1 tunnel is much lower compared to a wifi client talking over the standard wan eth4 interface. (I use PBR source routing in wireguard) It doesn't appear to be a wireguard performance problem since wireguard performance for a wired client is awesome. I think there is something with the handoff between WIFI and oet1 that's imposing a performance penalty.
Just my observations. Hope this helps. r57447 is very solid. Thank you devs for all the hard work here.
Joined: 21 Jan 2017 Posts: 1797 Location: Illinois Moderator
Posted: Thu Jul 25, 2024 13:24 Post subject:
AnTi90d wrote:
I mean no disrespect towards you guys..
..I just bought a router that I thought would work because it's on the list.
I need a router. I need a router now. Right now. This moment.
This one isn't ready right now.
Now I'm up four hours past my bed time trying to find a router on Amazon that works with DDWRT and then cross reference the forum so I can find out if it isn't actually functional, this moment.
Try Build 57564, things should be much more stable now.
For wifi- I suspect you are trying to connect to it after initial flashing via wifi, correct?
BS doesn't believe me that when there is no WiFi password set, you will experience no connection as you describe above.
At the moment, you have to configure the router via the ethernet cable to establish a WiFi PW and then you will be able to receive an IP lease from the router to make more changes via WiFi.
I am still working on figuring out the right set of logging to prove my point to BS about this issue.
Additionally, make sure to enable the WAN to use DHCP to get an IP from your cable modem, Fiber "modem", or DSL modem. Otherwise you will never get onto the internet.
At the moment, these are the two glaring issues I know of that likely are causing you grief. Otherwise this router should be solid.
I have not tested mine yet on the open internet as I need to keep my network up and running for another week and then I can plop in the MR7350 and see how it performs vs my R9000.
My dilemma is that the MR7350 is severely power limited to 23dBM on 5ghz and 19-20dBm on 2.4ghz. I need the extra power the R9000 has on its radios. It seems the better bet is the MR5500, that appears from a marketing perspective, to have better radio's in it to achieve the full 30dBM with its 2700sqft coverage claim vs 1700sqft on the MR7350.
I got this router for $12 on ebay so no complaints from me at the moment. I may even sell it and try the MR5500 instead to see if that has better radios indeed.
I might get to testing the MR7350 over the weekend if I have any spare time, but not likely. _________________ FORUM RULES
Update to my post above. r57447 is still my go-to release for the mr7350. I've been running r57564 for 3 hours this morning and will post in the r57564 release thread soon. Wired client and wireguard performance is good. However I can't get any wifi clients to connect to either radio. Here's an example of my MacBook Pro trying to connect. It pops up in the wireless status tab with a -108 signal strength before eventually disappearing. Other non-apple products can't connect either. I'm going to go back to r57447.
Joined: 21 Jan 2017 Posts: 1797 Location: Illinois Moderator
Posted: Thu Jul 25, 2024 16:10 Post subject:
pbphoto wrote:
Update to my post above. r57447 is still my go-to release for the mr7350. I've been running r57564 for 3 hours this morning and will post in the r57564 release thread soon. Wired client and wireguard performance is good. However I can't get any wifi clients to connect to either radio. Here's an example of my MacBook Pro trying to connect. It pops up in the wireless status tab with a -108 signal strength before eventually disappearing. Other non-apple products can't connect either. I'm going to go back to r57447.
Any chance you can run wireshark and see if you glean anything from it?
I have 0.0 bandwidth to do any testing at the moment due to a crazy project at work. Otherwise I wouldn't be asking.
But this now sounds like a magnification/further worsening from the issue I was telling BS about with no PW set and not being able to get an IP lease.
Clearly something is amiss... we'll get there soon enough. _________________ FORUM RULES
I am unable to get this build to even boot. We saw this before with an earlier release. The previous test release, r57555 however DOES boot:
Code:
## Booting kernel from Legacy Image at 44000000 ...
Image Name: DD-WRT V3.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4194175 Bytes = 4 MiB
Load Address: 42208000
Entry Point: 42208000
Verifying Checksum ... OK
Loading Kernel Image ... OK
FDT and ATAGS support not compiled in - hanging
### ERROR ### Please RESET the board ###
This was after a full reset. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
After tftp flashing back to r57447 onto both partitions, I was able to successfully update to r57564. Not sure wth happened there. I MAY have flashed the EA8500 firmware to it by mistake causing this error. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Okay, I am seeing some really odd things here. Only testing wireless on wlan0 (wlan1 disabled).
After very basic configuration with dhcp server on then unplug all cables except power
- My Pixel7a phone can get an IP address on the correct subnet: 192.168.1.166.
- My Samsung Galaxy Tab cannot get an IP.
Next, I plug the LAN cable back into LANPort1 which is connected via a switch to my main computer (and the rest of the network). The main computer has an IP alias of 192.168.1.15 so it's able to access the router webui. There are no VLANs configured on the router at this point.
- Phone gets an IP address but from a completely different subnet?! (192.168.254.x) What? HOW? It's getting its IP address from my Main network DHCP server, but how? The WAN is not even plugged in. I would guess the built-in DHCP server is the problem here. It cannot assign an address but passes on the advertisement from the main network dhcp server. Is this possible or likely?
- Tablet still cannot connect.
Create a VLAN and assign WLAN0 to this VLAN.
- Phone gets an IP address on the correct vlan subnet (10.2.0.x)
- Tablet gets an IP on the correct vlan subnet (10.2.0.x)
Connection is good and stays connected indefinitely. This is kinda leaning to the problem being the built in DHCP server and not the radio itself I think.
Connected to both WAN (192.168.254.67 and LAN (192.168.1.1) Router DHCP server should be issuing addresses on 192.168.1.x.
- Phone gets IP address again but from the main network (192.168.254.61).
Opinions? I am totally confused about this extremely odd behavior. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Joined: 21 Jan 2017 Posts: 1797 Location: Illinois Moderator
Posted: Thu Jul 25, 2024 18:45 Post subject:
lexridge wrote:
r57564
@msoengineer
Okay, I am seeing some really odd things here. Only testing wireless on wlan0 (wlan1 disabled).
After very basic configuration with dhcp server on then unplug all cables except power
- My Pixel7a phone can get an IP address on the correct subnet: 192.168.1.166.
- My Samsung Galaxy Tab cannot get an IP.
Next, I plug the LAN cable back into LANPort1 which is connected via a switch to my main computer (and the rest of the network). The main computer has an IP alias of 192.168.1.15 so it's able to access the router webui. There are no VLANs configured on the router at this point.
- Phone gets an IP address but from a completely different subnet?! (192.168.254.x) What? HOW? It's getting its IP address from my Main network DHCP server, but how? The WAN is not even plugged in. I would guess the built-in DHCP server is the problem here. It cannot assign an address but passes on the advertisement from the main network dhcp server. Is this possible or likely?
- Tablet still cannot connect.
Create a VLAN and assign WLAN0 to this VLAN.
- Phone gets an IP address on the correct vlan subnet (10.2.0.x)
- Tablet gets an IP on the correct vlan subnet (10.2.0.x)
Connection is good and stays connected indefinitely. This is kinda leaning to the problem being the built in DHCP server and not the radio itself I think.
Connected to both WAN (192.168.254.67 and LAN (192.168.1.1) Router DHCP server should be issuing addresses on 192.168.1.x.
- Phone gets IP address again but from the main network (192.168.254.61).
Opinions? I am totally confused about this extremely odd behavior.
I don't have the bandwidth right now to guess, but likely a double DHCP/Double NAT induced issue on your part connecting the MR7350 to your main network/router....
Some commits made to madwifi on the IPQ6018 series routers in 57574....so now we wait to flash whatever nightly build we get and test more. _________________ FORUM RULES