So with no great surprise to my wife, my 1st image build bricked the device and it seems the pins are labeled slightly different to the eap245 I'll get a multimeter out later and test unless someone can help me out
Ok so I'll open a new thread I guess might be a better source for others
What are the sleep times supposed to do in a setup script?
My biggest setup script for my devices have about 900 lines of UCI code, but I have no delays in it.
Maybe for more manual hardcoded hacking with sed, echo, cat config file replace and restarting services manually. With uci a interface may only comes up after the commit message and some delay. Maybe in or between that period you have other wishes certificate/authentication before other parts of the uci config may succeed?
A commit only writes your changes from the ram to the actual config file.
To load it in a interface or something else you need to run a restart or reload operation.
But the whole idea with !# script is that they run the code as if you did it yourself but without delay so every command must be done before it moves on or it gives a error message.
You can even make commands in the script like opkg update and on next line opkg install <something> and the script will nicely wait while the device is downloading the package list and then it will install ”something”.
Well since you recently saved your brick, try to avoid a new one and just build a default image with the online image builder having the default packages but only the following test commands in the script to see if/how the script may work. As in if it needs extra shebang/exit0 stuff.
echo "just a simple echo test" > /etc/echotest.txt
mkdir /etc/blablabla
touch /etc/blablabla/testfile
date > /etc/blablabla/datescript.txt
date >> /etc/echotest.txt #puts date at the last line in file
Than step by step try to add your new default config with uci commands (verified before in a clean image using ssh) in this custom script.
You might also try to remove all packages you don't like from the current default image and see if that still boots, than later adjust the package list for the online image builder.
Thanks Walter I was planning on saving the UCI commands but as I was setting up I enabled one of the WiFi controllers and that saved everything..... I just went with the generic build as you said and just followed the dumb ap guide.
Next I seem to have bricked the Comfast I got also
So after a week of bricking routers(only one device is dead dead and needs a EEprom re-program) I think I'm finally at the point I can start building custom images.
I actually managed to create a text file this morning of the UCI commands, so to be sure.
Factory reset the device and SSH into it,
Copy and paste the text file in and see if it works,
All going well then build a custom image with the text file copied into the command list( do I need to add anything else or just;
UCI command blablah
UCI command blah blah
)?
Sorry I meant the custom builder first boot custom script.
Does the front-end image builder need something like that? I was told to just copy what the config changes were from the top right of the Luci interface run them in a clean build via SSH if they work then add them to the online custom builder frontend
Yes!
The other tip was only the easiest way to get the actual UCI code for your settings, but that is still a good tip.
But instead of working full time bricking routers with trial and error you maybe should read some parts of the user guide and developers guide?
Sorry ADHD is a real pita I try to read as much as I can but my underlying knowledge is pretty basic so as soon as I start reading things I don't understand my mind switches off and I get frustrated. Speaking to people works better and i can verify things I don't understand that way.
I've probably watched every vlan video on YouTube and still haven't got any running at home.
I lock myself out of my network on a daily basis I would guess I locked myself out of my managed switch 3 or 4 times just this morning trying to set up 802.11q on it
Switches can be tricky! Sometimes console cable is needed to set up VLAN and DHCP client mode since some configurations gives a catch 22 problem.
Tell me about it!
I have 2 old l2 switches a tplink and a SMC poe they use different terminology on both. I was trying to set up both but now I'm using the Poe as my feed for most of my access points so I'm not touching it and just playing with the tplink in an effort not to lock myself or mainly my partner out of our WiFi as she needs it for work.
All the gear, no idea is pretty much an apt description of me.
Still not sure about the Custom script to run on first boot (optional) requirements of the a.s.u. imagebuilder is it shell based or only a uci parser, could you clarify?
I'm talking about the ASU.aparcar now not the Linux ASU I'm not intelligent enough to get that working.