If you like you can test my current build that I've compiled 2 weeks ago. It's pre-installed with bunch of packages I'm playing with (SQM, OpenVPN, WPA3, DDNS, dnscrypt-proxy2, Adblock etc.) but seems stable enough and I haven't noticed any issues with txpower or WiFi range in general. Though, there is no added support for external storage or usb.
I would like to thank @geminis3 for build instructions and all contributors for making this small router useful. Keep up good work and let's hope for stable branch in the future .
@Xarlith thanks for firmware. Awesome to have Adblock in my MikroTik.
Where is Adblock can be activated in config at the build step or this package can be installed manually (any deps for Adblock package)?
As long as snapshot's dependencies are still met you should be able to install it yourself with the package manager.
Additional packages were activated at build step just because dependencies in snapshots repository change constantly and I wanted a build that can be flashed and ready to go anytime in the future. No special kernel modules are required for adblock.
Thanks for the build. Been running this last few days and it seems pretty stable. I am using the 5Ghz radio in client mode for my WAN uplink. Speeds are actually much better that I was getting with router OS.
Also my first time trying openwrt. Getting the PXE installation to work was the hardest. But once installed, open wrt's webui is very intuitive.
Install Nemesis on your flash drive or HDD >>> https://pastebin.com/czT9QPx2
NOTE. File system that you will be clone openwrt must to be POSIX filesystem (like as ext2, ext4...) and to have a good supply of free space.
By default all changes will be saved on /mnt/sdb1 (look at option changes=/dev/sdb1 in /boot/syslinux/porteus.cfg) Warning! /mnt/sdb1 must to be POSIX filesystem (like as ext2, ext4...)
Boot up from your USB Flash drive or HDD
Nemesis via second menu - Xfce (changes)
Open terminal and run these commands:
su
toor
export FORCE_UNSAFE_CONFIGURE=1
env FORCE_UNSAFE_CONFIGURE=1
setup-pman
# where is /mnt/sdb1 is POSIX filesystem (like as ext2, ext4...)
cd /mnt/sdb1/
pacman -Syu
pacman -S bash bc bin86 binutils bzip2 cdrkit coreutils diffutils fastjar file-roller findutils firefox flex gawk gcc gettext git intltool libusb libxslt make ncurses openssl patch perl-extutils-makemaker pkgconf python3 rsync sharutils time unzip util-linux wget zlib
git clone https://github.com/openwrt/openwrt.git
cd openwrt
git remote add foobar https://github.com/f00b4r0/openwrt.git
git fetch foobar
git config --global user.email "here-is-your@email.com"
git config --global user.name "here-is-your-nikname"
git merge foobar/hAP-ac2-cleanup
git rebase
./scripts/feeds update -a && ./scripts/feeds install -a
# copy your .config to openwrt/
# you can rename config.buildinfo from ready mikrotik hap-ac2 firmware to .config
# and copy this .config to openwrt/
# press Ctrl+H to see hidden files and folders
make menuconfig
make -j4 V=cs
# (where 4 is CPU core - look at your PC configuration)
# share your build of firmware for community.
#NOTE.
#Initial compilation takes like an hour but subsequent builds are fast, make sure to run each time you rebase (aka update local OpenWRT repo)
./scripts/feeds update -a && ./scripts/feeds install -a
make clean
Those LED-s are driven by the PHY-s directly, by default PHY only enables the gigabit ones and not 10/100 ones.
QCA fixes that up in U-boot usually but Mikrotik does it from userspace.
My hAP has been out of the case all of the time, so I did not notice it.
I have a PR for a proper PHY driver, so I might as well integrate this as well for these cases.
.
