What is Reddit's opinion of
OpenWrt?
From 3.5 billion Reddit comments
100 reviews of this app found across Reddit:
Wow if only someone invented a router where the software code was truly open, didn't infringe on the GPL, was well coded and the devs weren't sketchy as fuck and named it say https://openwrt.org/
It depends by what metric you're after. Fastest CPU? Well you can put OpenWRT on a standard 64-bit PC, so I guess that
Fastest Wi-Fi is pretty much impossible to objectively measure, since it depends on so many factors. I guess if you want "newest". Wi-Fi 6 devices mostly aren't yet supported due to drivers lacking FOSS friendly chipsets
If you simply want the "well what do you use?" I have a WRT3200ACM/WRT32x
Copying files off my NAS to my laptop with an Intel AX200 chip I routinely get up to about 103MB/s over HTTP transfers
There's also nothing that says you can't block, filter or redirect the "smart TV's" requests to /dev/null (no where) via a home firewall or router.
Since most of these devices run Linux and the fact that it is legal to hack them, there are dozens of OpenWRT-like projects that remove this malware from the device.
It simply comes down to how much effort people want to spend bitching about it versus doing something about it.
You can get away with shit APs (just run local VPN if you think the encryption is worthless), but you do need a secure gateway. You can do it on the cheap too, just get a used thin client and put OpenWRT on it. Also as a bonus you can do advanced traffic shaping, which is still not even offered by commercial options.
That seems like a lot more money, time and effort than installing (the freshly re-unified) OpenWRT on something like a US$70 TP-Link AC2600 or US$25 AC1750.
If you know the details of the hardware (i.e. manufacturer and model), you can look in the downloads for a clean firmware that you can set up yourself in any way you want.
I'd personally go with a clean firmware, since you don't know what sort of backdoors the original vendor left on your router.
This is a test version of the software that will become 18.0.6.0. Once finalized, 18.06.0 will be the first stable version after the OpenWrt/LEDE project merger and the successor to the previous stable LEDE 17.01 and OpenWrt 15.05 major releases.
The 18.06 series will focus on support for network flow offloading and modernizing the Atheros AR71xx target.
- Adblock for your whole network (luci-app-adblock). Blocklists auto-update and there's no configuration required on any of the client devices. Plus, this gives you adblocking even on things like smart TVs, game consoles, set top boxes, etc.
- SQM to keep latency consistently low even under load, by reducing bufferbloat (luci-app-sqm; instructions here). It's easy to configure and of works better than doing manual QoS.
- When security flaws are found, the OpenWrt team releases firmware updates to fix them, for years and years after that router was first released. With manufacturer firmware, you're lucky to get any updates at all (they want you to buy a new product and give them more money). Consumer router manufacturers are notorious for cutting corners; in the rush to market and in the search for profit, manufacturers treat firmware security as an abysmal afterthought.
I think it's harder to find counter examples - basically every single router that has been around for few years would have had a few hardware revisions. Fairly popular TP-Link Archer C7 had 5 revisions large enough to require different firmware images - different WiFi chipsets, CPU frequencies, ROM sizes, USB port count etc.
It's not something that netgate necessarily includes, it's more like the openwrt community doesn't officially support this model (yet). It may get support later on, but usually most people looking to run openwrt stick to officially supported models.
You can see there are plenty of Netgear units that are supported here
OpenWrt can be loaded on many off the shelf routers (i wouldn't touch DD-WRT with a shitty stick).
I favour TP-Link devices as they're reasonably priced and decent quality. I currently run OpenWrt on a WDR4900 (main router) and WDR3600 (for increased wifi range).
I've got no real complaints with OpenWrt, it can do pretty much all the same things as pfSense (although not always through a GUI).
Fand CUPS eigentlich immer recht angenehm, gerade da man ihn bequem über das Webinterface konfigurieren kann.
Wenn du aber etwas radikal einfaches suchst, was selbst auf deinem OpenWRT Router mit minimalem Ressourcenverbrauch läuft, versuch's mal mit p910nd.
This is the second test version of the software that will become 18.0.6.0. Once finalized, 18.06.0 will be the first stable version after the OpenWrt/LEDE project merger and the successor to the previous stable LEDE 17.01 and OpenWrt 15.05 major releases.
The 18.06 series will focus on support for network flow offloading and modernizing the Atheros AR71xx target.
Edit: RC1 discussion thread.
I think the simple answer, is that it depends on your router. Most routers don't have the ability to act as essentially, wireless adapters, out of the box, because their firmware doesn't support it. DD-WRT and OpenWrt are two projects that create alternate router firmware that you can flash on to you router. Both of them are able to do what you want.
I've done exactly what you're describing using DD-WRT and it works great. If you aren't afraid to spend a couple hours, I would definitely recommend it as a solution. Try DD-WRT first though, as it's probably easier to get set up and to use.
Well, if you want to take care of your routers there's always openwrt.
And, honestly, it depends on country you live and how important would you be for three-characters authorities.
I agree and use OpenWRT when I can. DD WRT uses proprietary code from manufacturers for some routers, resulting in more features or better performance.
"Devices with Broadcom WiFi chipsets have limited OpenWrt supportability (due to limited FLOSS driver availability for Broadcom chips). Consider this when chosing a device to buy, or when deciding to flash OpenWrt on your device because it is listed as supported. See Broadcom WiFi for details."
https://openwrt.org/toh/hwdata/asus/asus_rt-ac68u
I'll take FLOSS over proprietary any day, but I have to do what I have to do to get the most out of my router.
You'll probably need a router than allows you to edit iptables rules; most consumer grade ones won't allow you to do this (unless flashed with openwrt or the like).
What you're after is dns hijacking. I use it on my mikrotik router to force all dns requests to my pihole. The openwrt guide is here:
I'd be honest with you. OpenWRT is terribly documented. It's a literal chaos for a newcomer where more often than not you have to go through the source code of scripts, libraries and daemons.
There is https://openwrt.org/docs/start which is seldom updated and does not cover cornercases, but might give you a clue for what you should look for.
I think the most important concepts that differentiate OpenWRT from other linux distros are uci (configuration framework) and ubus (IPC bus, similar to dbus).
>But I haven't seen a router that did not provide more than I ever need functionality in years.
You need cake, you just don't know you do.
Basically: do you have a Broadcom chip ? If yes then OpenWRT may not be optimal, because Broadcom open source drivers are utter shit.
Do you have a Qualcomm Atheros chip ? Then OpenWRT is superior
Using the method /u/draco42 provided to enable wifi on the device, I was able to do a sysupgrade to the current stable release of openwrt (17.01.4) for the TL-WR703N. This was done by wget'ing the latest sysupgrade package and installing via console/ssh. After a little trial and error getting the device back on my wifi, I was able to install the rtl-sdr packge though the openwrt web interface. While running rtl_test still resulted in "No supported tuner found", its nice to have the web interface and a clean OS. Keep in mind this wipes out any Tzumi packages used to tune TV with the phone app.
https://docs.opnsense.org/manual/how-tos/multiwan.html
[OpenWrt Wiki] mwan3 (Load balancing/failover with multiple WAN interfaces) - https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3
Multiple WAN Connections | pfSense Documentation - https://docs.netgate.com/pfsense/en/latest/multiwan/index.html
I have flashed OpenWRT onto my two AC Lites and it works very well - less buggy, more reliable and I trust the security of OpenWRT much more than UniFi.
https://openwrt.org/toh/ubiquiti/unifiac - maybe an option that saves you buying new hardware (or at least a temporary solution).
Explanation of fq_codel: http://www.bufferbloat.net/projects/codel/wiki
You need a linux-based router to run it, the easiest way I found to get it running was to buy a router that supports OpenWRT and set up the SQM packages.
Unfortunately there isn't really many other options for running it (as great as it is), most other home grade routers don't include it or have many good quality of service related options.
Puoi utilizzare un altro router o un router in cascata a quello TIM su cui installi OpenWRT e configurarci SQM. Anni fa' avevo un ADSL penosa del tipo 8Mbit in down e 1Mbit in up, e con SQM si riusciva a usare 3-4 dispositivi contemporaneamente senza troppi problemi
Openwrt is surely not dead! There's new releases every 2-3 months, the last one 21.02 RC4 being released just few days ago
Wifi 6 is probably still too new, and there's only a handful of devices with openwrt support:
https://openwrt.org/toh/views/toh_available_16128?dataflt%5BWLAN+5.0GHz*%7E%5D=ax
Anyway, I think wifi 5 is good enough for 99% of users, and openwrt supports around 270 wifi 5 devices. Surely a bunch of them are mainstream enough for you?
https://openwrt.org/toh/views/toh_available_16128?dataflt%5BWLAN+5.0GHz*%7E%5D=ac
A good resource on router information is the OpenWRT Wiki (in addition to Deviwiki).
It shows that WNDR3700v3 is the only one out of five WNDR3700 versions that has a Broadcom chipset (Tomato is only for Broadcom routers). Your v4 has an Atheros chipset (ruling out Tomato), and is supported by DD-WRT, OpenWRT and Gargoyle.
DD-WRT is a bit unstable. Gargoyle is an outdated, but beginner-friendly OpenWRT fork. For maximum features and modernity, OpenWRT is generally recommended. You can refer to the OpenWRT Wiki linked before for installation instructions (TFTP flashing OpenWRT directly is one way to go, or you could TFTP flash stock and then upload OpenWRT via stock WebUI).
As for OpenWRT's interface, the default LuCI is pretty popular and well-regarded. But you can install other interfaces on OpenWRT if you prefer.
I am guess the "why would you want to do this" is to give one device more bandwidth and another less? If so, I would simply advise against this and use SQM 100% of the time and not try to starve devices, SQM is smarter than you or I.
Use these settings to get per host isolation, which is sort of what you want just not a hard limit.
Thanks for your detailed answer. It's for a remote operated robot platform. Hardware is pretty much set at this point I and won't be able to change the dual modem router I have, that's why I was looking into more software-based solutions, but would surely look into the Peplinks if HW update would be possible later on.
Thanks for mentioning the Mwan3, I think I might already have that package installed into the router. Currently reading this guide: https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3
I'm willing to put a lot of time and effort into this, but would like to only work with open source solutions. Others have also mentioned SD-WAN so I'm exploring that option as well, not sure if quality-based routing is possible with the open source solutions I've found so far, though.
See my comment above. There’s free open source software for your router called OpenWrt which can ensure that all connections get a consistent 20ms ping no matter how heavily the network is used.
I think the only way to make it relatively private would be to run open source firmware on the camera. I don't think it exists for you model. here are some models that can run openwrt (open source router software) https://openwrt.org/start?do=search&id=start&q=camera
Other things to do, if you want to keep your camera: disable cloud connectivity, isolate the camera on your network, so it cannot access any other clients. It would be best to not connect it to the internet at all, but that does not work in your case, I fear.
No LEDE and OpenWRT merged again, but they're basing the new stuff mainly on what the LEDE guys made cause OpenWRT was kinda stagnant: https://openwrt.org/about
Same thing also happned with io.js which was a fork of node.js.
- Visit https://openwrt.org/ and its list of recommended devices -- in general, all that matters to OpenWRT is that one of the developers has one and keeps OpenWRT up to date for it, and that it has 8MB of flash memory and 64MB of RAM or more
- Buy one of the devices, choosing by factors that matter to you, e.g. how good is its Wi-Fi performance in tests, how many antennae does it have, does it support 802.11n or 802.11ac, how many Ethernet ports do you need on it, how much power does it draw, how long the power cable is, how much do you want to spend, etc. - whatever meets your needs. Personally I got a TL-WDR3600 a few years ago, but there were better routers available then and even better ones are out now.
- Configure your ISP's modem to be directly connected to a single computer rather than acting as a router / Wi-Fi hub. Follow your own ISP's guide on how to do that.
- Use the hardware guide of OpenWRT's website to get the correct "sysinstall" image for your hardware.
- Install OpenWRT
- Connect your modem to the "internet", "uplink" or "WAN" port of this new router you bought rather than your computer
- Enter the ISP settings you'd use on your computer into the "WAN" setup of OpenWRT
- Set up Wi-Fi networks to your liking on OpenWRT
Yes...ish. Its basically an embeded OS that you can tinker with. The OS image you're installing is essentially a snapshot; you've got to be careful not to break dependencies when you install software (sometimes, just upgrading a single package can cause issues).
That said, there are tons of packages available, and the system is fairly customizable. And, yes, you can install Apache, php7, and mysql... and with some work, you can get something like wordpress running... but, it'll have flakey dependancy problems, and the hardware (and lack of RAM) will make the whole experience a bit sub-par.
I do host an HTML5 speedtest app and a HTML5 file manager / video streamer app on my OpenWRT router... but they were both a pain in the arse to setup and required fiddling with code. But, I also have a USB-connected SSD that shares files via SMB, and a miniDLNA server to stream video to the SmartTVs that were both incredibly easy to setup.
So, my answer to your question is: it depends on what you want to do. For a lot of typical router/NAS activities, like sharing/streaming files or running an LDAP server, then yes. If you want to do something that's resource intensive, or very reliant on specific package support, then maybe you should look at adding a Raspberry Pi 4 to your network as a mini-server.
This device is fully supported via upstream OpenWRT: https://openwrt.org/toh/hwdata/gl.inet/gl.inet_gl-mt1300
This includes WiFi via the open source mt76 driver which works great. I had no issues updating mine using the builds linked above.
If you're asking for the --> best <-- way, I'd suggest using an access point and a cable. Because repeating uses loads of airtime, you're basically sending every message twice. So if it's busy where you live or of there are many wi-fis (neighbours etc) a repeater might work but you won't have fun with it. Using an access point eliminates the repeating of the message and instead transfers it to a LAN cable, where its a direct 1:1 connection, so there is no other network to disturb you.
I'd look for some white cable and put it along my ceiling or just put it in the wall, if possible. If this is your own house, the attic might also be a good option to play the cable. And for the access point: any openWRT-capable device will do. If you have the option to go through the wall, there are some capable outdoor APs, e.g. a UniFi AP-AC mesh. For setup there is a guide in the wiki: https://openwrt.org/docs/guide-user/network/wifi/dumbap
That would probably be the best way.
If laying a cable is not an option, a repeater might be your only solution, yes. I don't have any experience with your device, so I'm not sure if it's reliable. Just make sure your repeater has a good to very good signal to begin with, because it can't repeat what isn't there.
Hope this helps, although I'm not able to answer your question directly :)
Fun fact: this is actually totally not supposed to happen! Your router should be enforcing fairness, throttling the heavy downloads so network-light apps like games or VoIP can maintain consistent latency. Your ping in a game or in voice chat should be a consistent and steady ~20ms, no matter how heavily your network is being used by anything else.
OpenWrt is free open source software that you can install on nearly any router, and it allows you to enable smart queue management on your router. When SQM is enabled, your network speed tests will show slower speeds and large torrents will download slower. But while these downloads are happening the network will stay rock steady everywhere else, as your router makes sure everybody gets equal access to the network.
I installed OpenWrt two days ago and I’ve never looked back. 20ms ping for everyone, all the time.
It all boils down to identifying the features you need (VPN? QoS? VLANs? dual-WAN? network storage? etc.). Once that's done, I'd suggest checking the list of supported routers for OpenWRT and/or DD-WRT (website is currently down).
Without pouring over the openwrt-devel mailing list and the bug tracker, I don't really know in detail, but here's what I do know.
The 18.06 release page mentions "network flow offloading." I think that means hardware-accelerated NAT (Qualcomm Fast Path), which makes a big difference for Internet connections faster than 200Mbps. It's something that previously most routers could only get with their stock firmware.
That page also mentions "modernizing the Atheros AR71xx target." I'm not sure what that specifically means, but it's probably something like more up-to-date packages, such as maybe a newer kernel version, etc.
I also read that they don't recommend preserving settings when upgrading to 18.06 from OpenWrt 15.05.x or LEDE 17.01. Start fresh and reapply your changes manually, so that you can take advantage of new default settings. What those new defaults are exactly, I have no idea.
One change I'm noticing with RC2 is that some parts of Luci's Bootstrap theme look different. It's not a huge, fundamental change, but personally I think it's for the better.
For the real details, I'd say wait for the notes that accompany the full release.
> I'm guessing if you want the latest 802.11ac frequencies, you'd run the ac router as an access point (ideally with ddwrt firmware) while using the pfsense box as a router?
Yes, but ideally you'd be using OpenWrt on the router/AP (DD-WRT is less than ideal, and barely better than the manufacturer's firmware IMO. They also have similar issues to Ubiquiti with GPL compliance).
Very disappointing as i'd been leaning towards replacing my home network with their stuff after i finish with some other projects. I'll have to rethink that now.
GPL violations are also one of the reasons i recommend avoiding DD-WRT (the others being broken features and general crappiness) and going with the far superior OpenWrt (or TomatoUSB if OpenWrt doesn't work on your router model and it's a choice between DD-WRT, Tomato or manufacturer's firmware).
I guess my next network upgrade will probably end up being a small pfSense or OPNsense box with the APs running OpenWrt.
On the plus side if the broadcom hardware has Linux drivers already then you can probably flash your own version of OpenWRT to the router and be able to have full access to updates patches and features.
1- don't use quickset 2- factory reset the unit and use ether1 for WAN 3- Tinker from there 4- User Winbox not the webUI 5- Use the wiki and learn the platform
Most likely you used the quickset menu, or you just changed the address without changing the DHCP server/pool etc.
If you cba learning the platform then maybe throw openwrt on there.. not something I've played with so I couldn't advise
addrwatch is designed for this. It works by using ARP and NDP, so even if the host is firewalled, this can still detect them (on the same broadcast domain).
For CAKE you should probably look at OpenWRT: https://openwrt.org/docs/guide-user/installation/openwrt_x86
Otherwise, if you’re okay with fq_codel maybe check out OPNsense. I like it better than pfSense.
TO tie in what everyone else is saying:
Have a firewall
But wait, what is colloquially a router actually has a firewall built in
And this is where it gets weird.
If you use two "routers" (read: router, switch, wireless access point, firewall combos) you run into duplicate dhcp, dns, nat and other services. So you want to see if you can use one in access point mode or something, with all of these services disabled.
However, having two "routers" for extra wifi will mean having to have two ssids, give or take. You can avoid this by using alternative devices. Some "routers" can join nicely with wireless extenders.
Better yet, if you don't mind getting into some config work, get a real switch, firewall, and wireless access points, getting rid of the "router" entirely. This is, after all, homelab. :)
Also, you could see if your router can install openwrt. Which seems to have a good ap mode. https://openwrt.org/docs/guide-user/network/wifi/dumbap
I think the images can be downloaded from https://downloads.openwrt.org/releases/19.07.7/targets/x86/64/ (or the 21.02 release candidate)
Installation instructions can be found here: https://openwrt.org/docs/guide-user/installation/openwrt_x86
Worth giving both OpenWRT and PF/OPNsense a try, but I'd skip over pfsense and do opnsense after that recent wireguard fiasco.
That model is a modem as well as a router; therefore, it won't be supported (cable modem functionality wouldn't work). So trying to flash R6250 firmware wouldn't be very wise.
Netgear doesn't even provide firmware for it, as that's the responsibility of the ISP. So you're best off just using your C6250 as modem in bridged-only mode and connecting a separate (OpenWRT) router to it.
Popular suggestions for an OpenWRT router are Archer C7, x86 PC and Raspberry Pi 4. The Archer C7 also includes a good AP. But there are many more options out there.
P.S. OpenWRT and libreCMC are generally the best (except on Broadcom routers), FreshTomato is the best on certain Broadcom routers, DD-WRT is fine but not very stable, Gargoyle and ROOter are just old OpenWRT reskins so don't bother. Zeroshell is dead.
FreshTomato and Gargoyle are the most beginner-friendly; OpenWRT and libreCMC are the most advanced.
The TC4350 has the dreaded Puma 6 chipset which is known to have terrible ping issues. The TC4400 is a great modem with a Broadcom chipset that doesn't have those issues and is much more modern and performant. Try and see if that is available in your area, otherwise check the list of modems and see which ones don't use the Puma chip.
On top of that, once you have a solid modem, make sure to enable "SQM" (Smart Queue Management) on your router (it might have a different name depending on the router, and not all routers support it). This makes your router send out packets in a smarter way to avoid ping issue in the routers and server between you and the destination (you can google "bufferbloat" for more info). I usually recommend ditching your routers built in firmware and go for OpenWRT instead if possible. It has an easy to use SQM implementation (https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm).
Anything ath9k is fine. ath9k uses no firmware, the hardware is just a state machine and a crypto engine -- see the Minstrel Bleues whitepaper for more details on how it works.
You probably want an AR9462; it's dual-band 11an + 11n.
If you need a miniPCI card, go buy an Aruba AP105 and tear it down for its AR9220 + AR9223 dual-band-concurrent WLAN card, it's pretty insane.
> Block zoom
denying access to a service that is clearly being used by one of the roommates for legitimate reasons (work) is not a solution and the implications can be bad for you if things are not properly communicated in advance and documented. in addition, the roommate can connect to a vpn and you won't be able to block zoom addresses anymore because the router will only see the vpn addr connection.
talk with your roommates first and explain the situation. then, propose a few solutions. the most common solution for such cases is to segment your bandwidth evenly across roommates. you've not written anything about your network topology, so it's hard to help with the implementation. in openwrt devices, for example, you can create traffic shaping rules to distribute the bandwidth across IP addresses (if using a single lan for the house and static addresses) or pools (if using vlans for each roommate).
You'd need to follow the commit logs to Git for example; https://git.openwrt.org/?p=openwrt/openwrt.git;a=log.
Packages would be different, as OpenWRT tends to download the sources from the original source to compile in the cross-compile toolchain for OpenWRT.
That's the problem with snapshot builds. Eventually the kernel dependencies for repo packages leave you behind. Only way to upgrade the kernel is to re-flash your device with a fresh snapshot. From the wiki:
> snapshots are built daily, and that sets time limits to installing new packages with opkg. Due to kernel version checksums, you can only install “kmod” kernel modules and other kernel version dependent modules from the exactly same snapshot build. So, a few hours after flashing the firmware you may not be able to install new modules with opkg any more (as the next snapshot has been built into the download repo and has different checksums).
Using standard releases avoids this problem.
best info i can find is on a forum thread at https://forum.openwrt.org/t/tp-link-tl-wr820n-v2-eu/60161
tldr, 1mb flash/8mb ram (8/32mb minimum for openwrt install), the forum OP was trying to solder replacement chips but hasn't updated thread since july
edit: seems there versions with 4/64 so dutch's advice might pan out. opening it up to see what SoC it has would be a good start https://openwrt.org/toh/tp-link/tl-wr820n
Yes, if you have an OpenWRT router, or one of these routers on Amazon.
I personally haven't done this before, but it is possible!
Its a alternative firmware that can be put on many router models and allows for a lot more features.
http://www.linksysinfo.org/index.php?forums/tomato-firmware.33/
Also popular is OpenWRT: https://openwrt.org/
I've had no issues flashing different openwrt builds on their devices. Currently I have an AR150 with official openwrt, two x750's and a Mango V2 on ROOTER (openwrt fork with expanded modem support built-in). I can't specifically speak for the ar750s but I don't think you should have much issues with it.
Flashing these things with another firmware is pretty straightforward. Especially when reading the instructions on openwrt for this ar750s.
https://openwrt.org/docs/guide-user/virtualization/docker_host
You need OpenWRT 20.xx or higher.
- install docker-ce package for the commandline tools
- install luci-app-dockerman package to get a control panel for docker containers in Luci
The pfsense box is just handling firewall rules/ dhcp. The router is just in AP mode. My Modem connects to my pfsense box's WAN port, and the LAN port from the pfsense box connects to the WAN port of my router (where normally the modem would connect)
Yes,https://openwrt.org/supported_devices/432_warning
Openwrt is busybox/linux distro design for embedded system and Wi-Fi router .I have TP-Link TL-WR841N Wi-Fi router and I install openwrt successfully on it.It only had 4mb storage.
So your OpenWrt only has 100mb ports and not 1gb ports? So yes, only full speed when connected to your cable modem. I would use the settings guide to make OpenWrt an dumb AP. https://openwrt.org/docs/guide-user/network/wifi/dumbap Basically turn off DHCP and routing, change the LAN IP to something in the 192.168.0.0 range (not in the range your cable modem is handing out), and plug your OpenWrt into cable modem using Lan port rather than the WAN port.
That will put all your devices on the same side of the firewall (being your ISP modem/router), which will make your life easier. It will mean you are not using the firewall features OpenWrt, but just using it like and AP.
I am on a similar hunt, but OpenWRT Wiki warns against buying the TP-Link:
>This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version (18.06 or later) onto it! See <strong>4/32 warning</strong> for details.
Please make this clear and recommend what can be supported in the future.
​
I am looking for the ultra lowest cheapest (and possibly worst) AP that can be supported in the future, to be used just for Smart home devices.
If your DIR-615 is a supported revision and has a USB port, install OpenWRT. Then connect a USB 4G dongle to the router.
https://openwrt.org/toh/d-link/dir-615#supported_versions
Alternatively you can install OpenWRT (or maybe ROOter GoldenOrb firmware, should be easier to setup) on your Raspberry Pi. You’ll need a USB 2 Ethernet adapter. Then use your RPi as your router.
Worth remembering openwrt exists. Despite the name, it hasn't really been just for the classic linksys wrt devices for a long time, it provides open alternative firmware for a whole bunch of different brands and models. No idea of the actual overlap in this specific case and too lazy to check (I don't personally have a netgear router), but nowadays there's a reasonable chance openwrt (and/or various other router-specific firmware distros) will still support your device for a while even if the vendor drops support.
Right, so most dumb switches will just ignore the 802.1q headers and make all frame forwarding decisions using just the source and destination MAC addresses (and whatever CAM they have along with some hard coded logic) but some of these “dumb” switches actually use the same sort of configurable switch IC that’s used in most home router devices which can actually be configured via I2C or SPI to have a few basic “smart” switch features (mostly just VLANs).
That’s because many of those cheap routers just have a single (internal) Ethernet interface that’s connected from the internal CPU to the switch IC and use VLAN tags to separate the WAN and LAN ports rather than having an extra Ethernet MAC & PHY connected directly to the internal CPU.
There are some details here
That doesn’t mean that all cheap switches will use that sort of switch IC (presumably it’s still more expensive than a dumb store-and-forward model) but sometimes the economics of IC manufacturing means that chips that have extra features are put into cheap devices just so the IC manufacturers can use the same set of silicon across the range of products that they sell.
I recall reading someone who found a cheap, allegedly dumb switch that actually had an internal I2C interface that could be used for VLAN configuration but I can’t find the link for that right now.
PXE boot server with netboot image in usb drive mounted on startup. Comes handy when you need to boot into linux to remove virus/malware from Windows PC.
https://openwrt.org/docs/guide-user/services/tftp.pxe-server
>ath79 is the successor of ar71xx. It's modernization under the hood, with the main goal to bring the code into a form that is acceptable for Linux upstream, so that all (most) of the whole ar71xx supported devices can be handled by an upstream, unpatched Linux kernel.
https://openwrt.org/docs/techref/targets/ath79
HW offloading isn't related to the new ath79 target, but to the newer kernel versions (4.14+). So if 19.07 (or snapshot) of ar71xx should support it, too.
Anything that supports openwrt You have a very nice table of hardware where you can choose which one has the fastest processor, however i recommend you to have a nice openwrt router and a dedicated vpn server, otherwise performance will always be poor
>The routers, he said, have remote access enabled by default
Usually routers configuration access points are only accessible from the internal network by default, it is a huge security hole on its own right that this is accessible in the first place. But that's by design for their cloud smartphone app. ffs.
These web interfaces are notoriously insecure, they run on bare metal web services written in insecure languages by people who don't know what they are doing usually.
My advice, NEVER use the proprietary firmware of any router manufacturer, they can NEVER be trusted, consider them ALL to be compromised(!) instead use an open source firmware such as OpenWrt.
For newbies: Cake is a method of SQM (Smart Queue Management), which aims to reduce "Bufferbloat" (unexpected delay issues in your connection).
Official OpenWRT documentation on SQM and how to enable it on your router.
As a lurker on this sub this is my time to shine, what this sub really is about is OTT services providers, albeit you receive a TV signal is done via a public connection, video broadcasting thru Multicast on a closed network (such as a condo or a hotel or even a ISP can provide this kind of service) is what professional call IPTV, you need to use real equipment such as a UDP/RTP broadcaster and Level 2 switches, IGMP routing, etc... and of course a IPTV receiver such as a decoding box or directly on TV (I have a Samsung Program to test this I'm working on the webOS version)
Most of the providers listed on this sub are directly HTTP public connections (OTT) via a 3mu8 file where they make reference to .TS files, most of the real IPTV providers deliver only a list of URLs like this one rtp://@239.0.0.1:1234
now the question about the UDP to HTTP is not enabled on the app, is a daemon that need to be installed on a PC or router like udproxy, udproxy has support on openWRT check out if your router supports openWRT
https://openwrt.org/docs/guide-user/network/wan/udp_multicast
If you need more help please tell me.
This might not be such a great idea.
> With the release of OpenWrt 18.06, the old OpenWrt 15.05 release is marked end of life and will not get any support any more, not even for severe security problems. LEDE 17.01 will still get some security support for a limited time. We encourage everyone to upgrade to OpenWrt 18.06 to get the best support.
SQM essentially does that. Ask your friend to go to http://www.dslreports.com/speedtest on a wired connection (not WiFi) at a time when the Internet connection isn't being used for anything else (just for a couple of minutes), and have them tell you the download speed and upload speed. From there, you can set up SQM by following these instructions: https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm
It's really pretty easy.
You haven't mentioned which version you're using. The development snapshots don't incluse the web gui (luci), so if you're running those you'll definitely struggle to access the web gui.
One thing that newcomers have trouble understanding is that, in general, an operating system needs to be built for the hardware it runs on. If you come from a Windows background, then that means Intel compatible hardware and that's it, so the concept of different hardware (chipsets and CPUs) never really comes up.
In the small (embedded) devices world, there are tons of different hardware platforms. MIPS, ARM, TI, and hundreds more, plus different chipsets (Atheros, Broadcom, etc...). The operating system needs to be built for each of these and that's what that list is. The same OS, just different builds for different hardware.
For your model, the product page has the debug output and indicates that it is an Atheros 7 based system ("system type : Atheros AR7240 rev 2") and so the ar7 folder is the one you want.
You'll need to reference the product page to determine which hardware version of your router you have and that will tell you which image to use (most likely the tl-wr940 or tl-wr941 depending on the age of your router).
This guy did something similar with a TP-Link router for half the cost of the Mikrotik using OpenWrt.
It also has support for VPN with a button to toggle it on or off (so you can connect to the hotel's captive portal and authorise your router, then toggle the VPN on and redirect all your devices through a secure connection).
Factory reset requires the firmware to boot the device, when said device is bricked it's in the same position as a PC with no HD...except there's no BIOS on a router to act as a type of pre-boot environment.
​
Likely can still be saved if the motherboard has something like a JTAG connector and OP buys a USB to JTAG adapter. Info, towards bottom of page: https://openwrt.org/toh/tp-link/archer\_c6\_v2
Besides a GL-iNet router I also have two development models of this router, without an LTE connection. With that caveat, it works very well.
Flashing OpenWRT onto this is slightly tricky as there’s a firmware upload that is only in Chinese. But googling the characters tells you which option to pick and then you just upload your OpenWRT firmware image and go from there.
This router also has the only chip that OpenWRT supports hardware flow offloading:
https://openwrt.org/toh/recommended_routers#flow_offload_and_oem_throughput
VPN probably not in most cases. If you are only trying to prevent your ip from getting out there. It probably wont hurt. But most games and chat apps don't allow people to get an ip of someone you are talking/playing with. Server owners/admins will be able to see. But to answer your question. I think a vpn does make the stream safer in the cases that games are made unsafe.
And if I was playing in a tournament for money I would have a stream delay absolutely.
If you made real money from streaming/playing competitively online. I would get 2 separates ISPs and have a cheap backup connection and use WAN fallover to automatically allow stream to reconnect.
I use Unbound DNS + AdGuardHome on my OPNSense installation, and I think you can recreate something similar on OpenWRT: https://openwrt.org/docs/guide-user/services/dns/unbound https://openwrt.org/packages/pkgdata/adguardhome
So example DNS query > AGH on port 53 > Unbound DNS on port 5353 > query sent to root zone servers in the event of a cache-miss.
You have to make sure what version you are using. The reason is following that guide you found only works in 18.06.x and 19.07.x versions. The last version (21.02) changed the swconfig to DSA. So, if you wanna config vlans you need to follow DSA guide. I saw a response of your post in the forum. That’s the correct answer. I use 3 vlans for guest iot and private.
Read this guide. https://openwrt.org/docs/guide-user/network/dsa/dsa-mini-tutorial
Start at the Table of Hardware. This also takes you to the TP-Link Archer C7 AC1750 page.
I'll be updating mine soon.
If your talking about packages, then the advice given is correct.
However, there is no GUI function for finding out if there is an update to the OpenWRT firmware.
Current stable release info -
What Swedophone said is the way. You then set the default gateway in table 1 to the ip of the wireguard peer on the other end of the tunnel and voila. All traffic for those hosts in table 1 is now going via there.
Tutorial here: https://openwrt.org/docs/guide-user/network/routing/examples/pbr_iproute2
Make sure you set allowedips of the peer on the router to 0.0.0.0/0, but disable the automatic route creation and add a route for the wireguard peer on the other side yourself. You have to set 0.0.0.0/0 because otherwise it wouldn't allow traffic for all ips, but you don't want it to create a default route for the whole system.
And by setting a priority on the routing table lower than the local table your hosts can still talk to each other on the lan.
https://openwrt.org/docs/techref/odhcpd says "Router Discovery (RD) relay ... Supports rewriting of the announced DNS server addresses", but I haven't actually tried it.
You would need an OpenWrt router between the ISP router and LAN, but beware that things can get messy when you chain routers like that.
Then it's even less likely that the device will be ported.
There very likely already are comparable devices that are supported by OpenWrt because someone put in the work and ported them. I'd suggest that you look at the Table of hardware and find a device that fits your needs instead of finding a device and then asking if it is supported or might be in the future.
Because at the end of the day porting such a device is done for free, so people only do it if there is something in it for them. I for instance ported a device because I have it here anyway. I wouldn't have done so if I didn't own the device.
Don't worry, I'll google it for you <puts on google t-shirt>
https://openwrt.org/meta/infobox/upgrade_packages_warning
xD
dá uma lida aqui e veja se isso parece ser o que vc está procurando:
https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3
You can fairly easily flash custom firmware like OpenWrt on just about any router and there's a package called mwan3 that might work for your application. https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3
>How involved is the process?
Not much to be honest. Just need to boot into Uboot and load the image, which is a 5 minute job. Instructions are here.
>Is it reversible?
Reverting to stock firmware is the same process as above, but using the stock image instead.
>Any particular 'gotchas' to be aware of?
128MB NAND storage not available
Don't use Protected Management Frames nor WPA3 ... It causes the wifi driver to intermittently crash.
>Any notable increase (or decrease) in functionality in a particular area?
No GL.iNet Web UI. You only have Luci, but then Luci is a lot more powerful than the GL.iNet UI.
None of GL.iNet's special functions (preconfigured VPN profiles for different providers, speed limiter, physical side switch) are available. But this OpenWRT, so you can configure it yourself.
No goodcloud.
>Still able to use as a VPN client (or server)?
Works perfectly.
It seems that the first method described here https://openwrt.org/toh/xiaomi/mi_router_ac2100
just needs a ssh-client, which afaik Windows 10 now has as feature, or you could use PuTTY.
If you have to resort to the python PPPoE exploit I would recommend to borrow a PC with VT or use a raspberry, this would be harder to do on windows.
You'll have to install the package containing the kernel module that implements the driver for this card. A quick search indicates it may be this one here:
https://openwrt.org/packages/pkgdata/kmod-iwlwifi
From the command line run:
opkg update opkg install kmod-iwlwifi
There's a syntax for defining aliases (additional IP addresses for an interface) which is documented on the wiki:
https://openwrt.org/docs/guide-user/network/network_interface_alias
In terms of avoiding the DHCP range, just look at /etc/config/dhcp file, and pick an address that isn't in the range for the interface you are operating on.
TL;DR: If you don't want to wait on Starlink's official firmware, replace the starlink gateway with an OpenWRT-based device, install the "SQM" packages using the CAKE queue management algorithm, set reasonable speed limits for upload and download.
I've had this deployed on my WISP for some time, and CAKE alone was transformative in fixing bandwidth contention issues.
[https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm](Openwrt QoS/SQM Instructions) [https://www.friendlyarm.com/index.php?route=product/product&product_id=282](NanoPi R2S) - a cheap 2-port (1 WAN 1 LAN) router that can run OpenWRT [https://protectli.com/vault-4-port/](Protectli 4-port) - 4-port (any combo of WAN/LAN) x86 router that can run OpenWRT. Good if you want to connect to multiple ISPs.
Super simple I setup openwrt VMs frequently so the process is fresh in my mind.
Here's a written guide OpenWrt x86
The downloads for the images are in the same guide, it's pretty easy to miss if you scroll through the guide quickly without detailed reading. To be more exact ubder Download Images the "Go here" is the link that points towards the downloads page (I made it a link to it for your convenience).
From the Go here link you end up in OpenWrt's releases page. Pick the latest stable release which is 19.07.7. From clicking 19.07.7 you then click on targets, then you choose your platform (x86 in this case and it is at the bottom of the list), then you choose 64. Finally you can pick whichever image you would like to use (The guide linked above explains the pros/cons of each image). For ease of setup use the combined Images. Specifically the combined-squashfs if you want a way to factory reset things in case things go wrong sometime in the the future without having to reinstall through this same process again.
After you have your image of choice downloaded, just follow the guide and you should have a system up and running in less than an hour (or likely 20 minutes if you have some experience).
If your ONT is already working with the Netgear router, installing OpenWrt and then configuring SQM (Network -> SQM) will make a big difference.
You can find links to the R8000's OpenWrt firmware on its device page: https://openwrt.org/toh/netgear/r8000
Then find the SQM configuration steps at: https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm
If you check the developer threads on OpenWRT, you can see that OpenWRT can already be installed on the Xiaomi models. It works okay, and it will work better by the time they're officially supported (Wifi speeds are mediocre right now, but it works).
And yes, the mt76 driver the X5000R uses on OpenWRT supports MU-MIMO and Beamforming, so that works.
In the long term, the Xiaomi's will probably be a better buy. In the short term, the Totolink has better software support (but worse hardware).
As you can see here, you should expect OpenVPN to perform at 20Mbps on the X5000R. The Xiaomi's are ca. 100 Mbps.