OK, that's what I thought. Since I might end up wanting to reboot every night, I wanted to avoid touching /etc, to avoid wear.
Which hardware version do you have?
Mine didn't die or anything, but I noticed that ping from my laptop dropped sporadically, and it stopped dropping after I rebooted it. So I thought rebooting was a good thing. But it's about 3 years ago that I tested. And my laptop is very old. (Macbook pro mid 2012) Maybe EAP wasn't at fault.
Does it hurt to reboot EAP every day?
3.1
Does that computer actually have any meaningful wifi standard to use that isn’t obsolete?
Probably not, but why reboot the router if you feel you want to reboot the AP? Put a 24h-timer on the POE injector=no problems, no headache whatsoever with any configs anywhere, no scripts, no ntp sync problems, no unexpected reboot loops or nothing, a stupid timer simply just work as expected 365days a year.
OK, mines are 3.0. I guess not much difference.
With my laptop, I can use 2G and 5G. I thought that's good:) But I tested with https://test.vsee.com/network/index.html I was shocked to see how poorly mine did, comparing with a newer laptop, using the same AP.
As for EAP, I just went off the topic, my main issue was the router. I mentioned my EAPs only to give an example of the statement by @_bernd talking about mysterious bugs being prevented by regular reboots. But EAP reboot is taken care of by the controller, and they aren't even connected to the router I was talking about.
That is only the frequency, it has not that much to do with bandwith, pretty much nothing in reality more than 2,4 is very very very obsolete roundradio and is useless for everything called speed.
5G can do all fancy stuff that can result in speed.
The bandwidth is what the frequency is actually used as.
So what speed you get is only about what wifi standard the hardware support, not what frequency it use since I assume it is 5G if there is any point of measuring the speed.
I wasn't talking about bandwidth. If I do a simple speed test, my laptop is pretty OK (I get as much as the access point can provide). This page https://test.vsee.com/network/index.html does stability test during a video conference. With my laptop, the graph goes very wiggly, whereas with a newer laptop, it's straight horizontal. Both stay between good and excellent, though.
I mentioned about 2G and 5G because you asked about supported wifi standard. Isn't "standards" things like 802.11, with supported frequencies?
Nope. There are AX devices with only 2.4GHz radio
https://www.intel.com/content/www/us/en/gaming/resources/wifi-6.html
I let Intel explain.
But your laptop if it is from 2012 can never have better wifi standard functions than 802.11n or wifi4.
While the EAP245 is wifi5 or 802.11ac (wave2).
Todays general market standard is wifi6/6E, to be replaced on the general market by wifi7 in a more or less short future.
Hi
you could use something like this in reboot script
DT=$(($(date +"%s")+70)); touch -a -m -d "$(date -d @${DT} +%Y%m%d%H%M)" /etc/banner
/sbin/reboot
it will
Interesting, I didn't know it!
Yes, right, my laptop can do 802.11n. Since my internet contract is 100Mbs and I have no large LAN traffic, it's enough for me, but I guess it's not so reliable in diagnosing something. I'm glad to know that EAP245s are generally reliable things. I was a bit worried that perhaps I made a mistake using them.
That was my first plan, but then, in case I might end up rebooting every night, I wanted to find a way not to write to /etc, to avoid wear. That's why I came up with the idea of using uptime.
The idea is to make iot en masse possible all under a single ssid. But that also requires that iot actually have wifi6 or newer, and that will take time since iot usually seems to like wifi4 at best and that without 5G.
I set up reboot at 3am last night and went to bed. It worked without bootloop!! In the end, I did this way:
uptime="$(cut -d' ' -f1 /proc/uptime | cut -d. -f1)"
if [ $uptime -ge 3600 ] ; then
ntpd -n -q -p 1.openwrt.pool.ntp.org
if [ $? -eq 0 ];then
Thanks a lot for your infos!
Now, the jobs I set upon booting did not work:
@reboot /etc/config/bin/restoreStats.sh
@reboot echo "Subject: ERX rebooted." | msmtp xx@gmail.com
I suppose I should put something like sleep 180 & before the commands? (assuming that the router should be fully up and running within 3 min) Note that the restorestats.sh includes a line like
sshfs maria@192.168.1.30:/media/maria/usb4gb/erx-tmp /root/copy-tmp
I guess it didn't work because the network wasn't up and running...
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.