I completely reworked big parts of the tool, would be happy I you could test this!
The development server runs here: https://as-test.stephen304.com
The stable version stays here: https://chef.libremesh.org
5 Likes
which should i remove i only need
openvpn-mbedtls and luci
opkg
ip6tables
odhcp6c
base-files
mtd
fstools
libc
busybox
uclient-fetch
wpad-mini
uboot-envtools
kmod-gpio-button-hotplug
libgcc
odhcpd-ipv6only
logd
swconfig
iptables
firewall
kmod-ath9k
dnsmasq
dropbear
ppp
netifd
ppp-mod-pppoe
uci
luci
Hi, you can just keep the default packages and add extra packages as you like. I have to rework the user interface for that, if anyone has an idea, please let me know!
if i have to add another package it will rise more than 4mb.. my router is 4/32 wr940n(EU)v6
Don't try to run OpenVPN and routing on a 4/32 device. It wastes time and annoys the pig.
1 Like
You will have more options to free up space if you build your own image using the image builder and make menuconfig, but I don't think OpenVPN will fit in 4 MB no matter what you do.
https://openwrt.org/docs/guide-user/additional-software/saving_space
My travel router, a tiny Nexx WT1520, is one of those 4/32 devices-non-grata. It works fine with a custom-built image that includes OpenVPN and in turn leaves out LuCI, opkg and pppoe. Sure it is limited, very much so indeed. And no, I wouldn't recommend anyone to buy it now, especially if you want to be on the safe side for the future. But it currently does the job I want it to do.
Frankly, I'm rather annoyed with this recent trend in here that anything below optimum is not worth pursuing anymore. Why is it suddenly so wrong to recognize, work within, and push limitations? Isn't that how OpenWrt started out?
1 Like
openvpn-mbedtls si blocking sa SUN...user the other one hahahaha
lol guys dont help him ...you know why...his selling openwrt of big price in the phil.....
"Below optimum" is just fine. Below optimum would be 8/64 devices. 4/32 devices are barely supportable. Bring your own support.
The goal here is to manage the expectation of people buying equipment and expecting it to really work without custom compilation.
existing devices you can buy NEW today with 16/128 start at $20. There's nothing wrong with you supporting your own ancient hardware, but there's definitely something wrong with expecting volunteer forum supporters to spend several hours explaining to a new user why their ancient device needs custom builds, multiply by tens of times a month, when the answer to it is to buy $20 worth of hardware.
4 Likes
heres mine too and what is great with this one is
MY ROUTER IS SEALED SO NO ONE CANT GET INSIDE THE ROUTER only these can be SEEN
AND MANAGE
are you sure? even trx files can be unpack how could you say that yours cant be?
share your build here and lets see if it is really protected
Hi, I'd appreciate if you could keep the conversation somewhat friendly and related to the initial topic, thanks!
3 Likes
sorry about that he started it.. he is a flammer
1 Like
sorry for that...
1 Like
This is awesome project! Thanks @aparcar 
I just want to know that is it possible to add custom packages?
I want to add luci-wrtbwmon_v0.8.3_all.ipk, wrtbwmon_0.36_all.ipk
But unfortunately they are not in OpenWRT repos.
Does that still work for you on 18.1.x, It looks weird to me now
The answer to your question is no -- It will have to be added by the maintainer of that project.
Unless someone else forks it and adds it themselves I guess
Install packages from a website
Packages can be installed directly from a web adress, e.g. with following command.
opkg install http://www.yyy.com/zzzz/$package_name.ipk
So I tried adding urls, didn't work
Unknown package in request: **https://github.com/Kiougar/luci-wrtbwmon/releases/download/v0.8.3/luci-wrtbwmon_v0.8.3_all.ipk, https://github.com/pyrovski/wrtbwmon/releases/download/0.36/wrtbwmon_0.36_all.ipk**