Hacker News new | ask | show | jobs
by m463 1919 days ago
I started years ago with openwrt.

First I tried the tp-link TL-WDR4300, which was very well supported at the time.

I then moved to the tp-link Archer C7.

Along the way I went from a "regular install" of openwrt, to build the LEDE fork myself, then back to building openwrt.

It's actually quite straightforward after you get over the hump.

    $ git clone https://git.openwrt.org/openwrt/openwrt.git
    $ cd openwrt
    $ ./scripts/feeds update -a
    $ ./scripts/feeds install -a
    $ make menuconfig
    $ make -j $(nproc)
I got away from the GUI and now do most configuration via the config files in /etc/config.

my current router is a wrt-1900acs, which took a while to get stable. I sit it on the shelf for a good year.

Because I learned how to build openwrt, I also have two mikrotik rb3011uias-rm 10x gbe switches. I wish the touchscreen worked.

It's not in the main tree but I followed this thread:

https://forum.openwrt.org/t/support-for-mikrotik-rb3011uias-...

It's a community build, but it is stable and works well.

If you want to play with openwrt, it's a little saner to have two routers. Have one that works, and one that you can break without having to stay up all night to get online.

1 comments

> If you want to play with openwrt, it's a little saner to have two routers. Have one that works, and one that you can break without having to stay up all night to get online.

There is a learning curve when using openwrt. When my girlfriend demanded that I stop effing up the wifi at some point. That's when I decided to get a second router to test new and complex configurations.