Oh, I see. So if bought new, it's not possible to know the hardware version without opening up the retail box? Thx!
I wouldn't buy a new C7, today.
I've replied earlier, but if you need/want more than one - https://www.ebay.com/sch/i.html?_nkw=linksys+e8452.
I apologize for missing our earlier recommendation. As an AP, how is the Linksys E8452 better than the Cudy WR3000? How is the E8452 better for use with the plan that I have outlined? The E8452 seems to be more expensive than the Cudy WR3000 so I want to know how I'm better off.
Thx!
it's cheaper ? ![]()
there's a reason I wrote "more than one" - it's a two pack.
I'm so sorry, I missed that! I'll look into that.
Meanwhile, I just want to enhance my understanding here. Technically speaking, as an access point for use with a BPI R4, how is the Linksys E8452 better than the Cudy WR3000?
like I said, it's cheaper (if you need two).
wifi wise it's about the same, routing wise the Cudy's better, it got a beefier SoC (CPU).
It's not necessarily cheaper unless I buy used. I live in Canada and the Linksys E8452 is about the same as a new Cudy WR3000. I have to look more into it.
Pricing aside, are you saying that the Cudy have superior specifications compared to the Linksys? Since I'll be using the BPI R4 as the router, then all I'll have to worry about is the WiFi aspect and if you say they're both the same, then pricing should be the sole determining factor, right?
Earlier I was talking about roaming (not sure if the terminology to use). For discussionās sake and trying to understand how this works, if I have a Cudy on different floors and as I walk from floor to floor, how do I ensure a seamless transfer from one access point to another? The APs will be connected via backhaul. I want to have one SSID that ill be using. Is it possible to configure OpenWRT to do that or it'll be automatic?
I went on xxxxxxzon.ca and was surprised to see so. wtf?
I don't know what to tell you, bro. ![]()
Where do I start?
Trying to cobble together a Wi-Fi network by turning a bunch of stand alone Wi-Fi Routers into Access Points is like gathering a bunch of buskers and sticking them into a Symphony Orchestra.
So this is a bad idea? If so, then how would you build a network?
16MB flash is plenty to use a router as a dumb AP. See my earlier post in this thread.
My chamber orchestra uses two stand alone Wi-Fi routers as AP's and plays great.
My home is similar to the OP's - several rooms are wired with Cat 5E to wall outlets that drops into a small central telecom box inside a closet. I added an electric outlet to the telecom box. I have a NanoPi R5C router and Netgear GS308T managed switch inside the telecom box, and a stand alone WiFi router on each floor of the home - a Reyee E5 and a Belkin RT3200 (same device as the Linksys E8450/E8452) - configured as dumb AP's. Every device runs OpenWrt.
My ISP service is half Gig DOCSIS 3.0. The R5C gateway handles SQM, adblock, DoH and dhcp for multiple vlans on the home network. The AP's provide a separate wireless interface for each vlan on 80MHz wide 5GHz WiFi6 and 20 GHz wide 2.4 GHz channels with 802.11r fast transfer configured for roaming. The "worst" performance in the home from the ISP to a 2x2 WiFi6 client a couple rooms away from the nearest AP is ~450 Mbps with good latency.
How do you ensure the seamless roaming inside your home?
How many AP's do you need? Figure that out before you go on a buying spree! One per floor works well in our two story home.
The Flint 2 you already have to use as an AP supports 802.11ax on both 5 GHz and 2.4 GHz. So does the Cudy WR3000. Used E8452/E8450 (single pack)/Belkin RT3200 WiFi routers are all identical hardware and make great AP's (I use one as such), but be aware they do not support 802.11ax on 2.4 GHz - only on 5 GHz.
Having 802.11ax support on 2.4 GHz across your network is not critical. Most need 2.4 GHz for IOT devices, and most of those cannot connect to an 802.11ax 2.4 GHz AP anyway, so you would need to dial 2.4 GHz down to 802.11n on the Flint 2 and any WR3000's anyway - at least on an IOT vlan SSID. It's just something to keep in mind for your hardware selection.
Something else to consider is internal versus external antennas. Vertically oriented higher gain external antennas do a little better job spreading the WiFi signal horizontally across a floor. Whereas lower gain internal antennas do a better job spreading the WiFi signal in a sphere around the AP. I use a Reyee E5 with external antennas as an AP on the larger sprawling ground floor of our home, and a Belkin RT3200 on the smaller second story floor. The Reyee provides better throughput at medium to long range distances, but don't take this as the RT3200 does not also perform well - it performs very well, just not quite as good as the Reyee E5.
Finally, I think it's already been mentioned in this thread, but OpenWrt supports Mediatek hardware better than Qualcommax targets. All else equal, I would stick with Mediatek targets.
First set up the same SSID name, same password and same wireless security encryption protocol on each AP for interfaces to be configured for roaming. Use different channels on each AP though. Second, under the OpenWrt LuCI wireless interface configuration Wlan roaming tab, check the "802.11 Fast Transition" box for the interface on each AP. Beyond that, the defaults will be good choices to start with. Save and apply.
Install a wireless signal strength app on your phone that shows you the channel and signal strength for each SSID. The channel will tell you which AP the SSID belongs too. In general, adjust the txpower of your AP's so that WiFi coverage between different AP's intersects around 65 dBm.
Clients decide which AP to use, so they play a part as well. You need to have realistic expectations on the "seemless" part.
The Linksys E8450 is a great option for basic/cheap WiFi router to use as an AP for $20.
I'd go for it. As I said, her in Germany I'd spend 5⬠more and get the one with more storage, but if you can't get your hands on that one, the WR3000 for an AP is nice, too. Just go for them.
I didn't see you write about it, but I'd make sure to have a central point for a central switch where every room and every AP branches out to.
Some people just daisy chain APs one after another, especially since those devices have 4 to 5 rj45 ports in total. One in from the router, one out to the next AP, leaves you with 3 other rj45 ports you can use for a computer or a PS3 or whatever. Sounds like a good idea at the first glance.
The thing is: There will come the time when your AP1 goes dark, either because of a config mishap or because it died. If you daisy-chain them, AP2 and AP3 and all wired devices loose connection to the router as well.
So if you're in the middle of some renovation or something, and have the chance to run wires the proper way, I'd spend some more money and give every AP its own distinct wire directly to the central switch.
This, of course, is not specific to OpenWRT but a general suggestion for networking.
Think about what you really want to achieve. As seamless for being able to take a wireless call (network via MS Teams or actual Wi-FI Calling on your mobile plan) while running around the house, switching from one AP to the other and have exactly 0 way of noticing it? Well, haven't achieved that myself with consumer grade stuff.
But just being able to walk around and being fine with a 50ms barely (but still) noticeable hick up in the conversation? Yea, just do 802.11r, FT over the air, 802.11k RRM, Neighbour Report and Beacon Report. Those are all settings you can enable in the UI and will work with just putting several APs side by side.
I've heard (not sure if true, since I didn't investigate myself) that some devices behave differently "sticky" when it comes to roaming, depending on if they assume they are in a personal or commercial environment. Personal environments tend to be less than ideal for roaming scenarios, commercial environments tend to be optimized for exactly that. The one thing I've heard (It's in one of OneMarcFiftys videos) is that some devices assume it's a personal environment if they see one or two APs sending the same SSID and assume it's a commercial environment if they see three APs sending the same SSID or more. So if you make sure your clients can detect at least 3 APs wherever they are, they should be more likely to switch from one to another just because they assume they are in a commercial environment.
I run a couple of Belkin RT3200 (Linksys E8450 but in white) and a couple of Cudy WR3000. I like the Cudy better, and so do most of my client devices.
That's the environment I have. When the house was rebuilt I put outlets in various locations around the house. I now have 3 APs in the house (living room, master bedroom, and in the unfinished 2nd floor).
I had to restore the factory firmware on the Netgear Nighthawk to get wifi support on it though (it's one of the APs now). I had found it in a scrap bin a few years back, just needed to get the antennas for it.
[Router] - [Layer 2 PoE Switch] - multiple - [Wall/Ceiling Mounted Wi-Fi 6 APs]
[Network Management]
I would use Ubiquiti as a reference for Switches and APs but NOT Routers.
Wow, thatās huge and Iām glad to ask you. Iām surprised the Linksys doesnāt support AX on 2.4 GHz.
Bro, I know and I want you to know that Iām not going to speculatively guess how many I need and blow my money on it. I do have the Beryl AX and Flint 2 to keep me busy in the meantime. Iām just asking these questions to sort of open my eyes a bit. Had I not asked, I wouldnāt have been inspired to do these things.
Yes, and thatās what Iāve read so far. The BPI R4, Cudy, and GL.iNet devices I have all have Mediatek chipsets, right? Great start then?