yeah the new u7 pro uses a fan. the deco series like BE 63/65 also use fans.
i think the Asus ZenWiFi BQ16 Pro doesn’t use a fan
Just an update
My Samsung S24 Ultra arrived. Already finished setting it up.
I was testing streaming wireless between it and the truenas ts-877. These were some of the media apps i tried
- jellyfin (using external mx player)
- navidrome (using substreamer)
- FX file explorer
- Comic screen
- netflix (tested 4k)
- immich
wireless ap was an old ubiquiti wifi5. The result is no lag it just worked.
My new wireless ap the eap-773 which is a wifi7 ap will arrive next week or so. I can then do some serious wireless performance test between the S24 Ultra and the truenas TS-877 using the docker hosted openspeedtest app locally hosted.
So in summary, with the new Samsung S24 Ultra, it can pretty much stream content from truenas ts-877 without issue. Heck, even my older phone model a realme could cope.
Anyway just wanted to share some real life usage when using the truenas with my new smartphone. It just works so many months on using truenas i’m quite happy i made the switch 
set it and forget it more or less. I haven’t been checking up on truenas lately these days since i was busy with other things. But it keeps chugging along and always available whenever i am streaming media content from it.
2 Likes
So my tplink eap-773 arrived yesterday. i already set it up and tested.
bad news is, apparently my client device the samsunf s24 ultra does have working wifi7. sus that it’s a firmware issue, because it has snapdragon so it should be wifi7 capable just that samsung did not enable it for my country no idea why.
But our neighbouring country for the same phone model has working wifi7 
So i only got wifi6e and 6GHz to work for now
ran more tests for the tplink eap-773 (wifi 7 access point for omada series)
It’s configured with band steering so it will switch between 6GHz and 5GHz depending on the signal so it can maintain a stable connection.
openspeedtest is hosted on the truenas using docker. For accurate results i used firefox browser to the lan ip for the openspeedtest from the S24 Ultra client device. So basically it’s testing wireless performance from the smartphone to the truenas for local network.
This is Wifi6 @ 6GHz within arms reach to the ap
This is 5GHz in a different room and separated between 2-3 walls
this is on the 2nd floor in a closed room. Also 5GHz
so coverage, range and connection stability is pretty good with just 1 single AP. 2 AP not required apparently. When i checked using wifiman for the signal strength, it was blue, green and yellow. There were some red but very vague/noticeable that i don’t think it counts. red means signal of -80 dBM
But was i got most often in the green was -30 to -60 dBM. And worse case was -60 to -78 dBM. So it barely even reached the -80 dBM where it will turn red. I did not notice any connection drops which is why i said it was stable. This was a big improvement from my previous Ubiquiti ap lite which was a wifi 5 ap.
For 4k netflix streaming you only need 25 mbps or something, which this clearly achieved. So you can do say streaming to netflix just fine. Or even if you wanna do plex or jellyfin streaming from your truenas over wifi should be fine as well.
But for the last 2 tests, it switched from 6GHz down to 5GHz.
Later when i went back to the arm’s reach position, it didn’t quickly switch back to 6GHz, it took a while before it did. I don’t know what setting to change to make it switch back quicker. But it did eventually switch back.
So this ap if you want 6GHz or wifi7, then you will need perhaps line of sight in same room for that. So for that you would need multiple aps 2 maybe 3 and set it up as mesh (which this omada series is able to do. But you cannot mix and match with deco or archer series which use different mesh technologies).
For the setup i am using omada controller self hosted on docker in truenas via jailmaker
Raidowl did a good walkthrough of the Omada setup which you may find helpful like i did
I could not get the AI wireless optimizer to work 
But everything else seemed to work.
Just could not get wifi7 to work, but that is probably a samsung issue.
This guy did manage to test wifi7 capability for the EAP-773
Wish i could test wifi7 for this but i can’t just yet
Would i recommend this wifi 7 ap to go with your truenas? Yes. But keep in mine it’s poe++ ap. I didn’t have a 10gbe port poe++ Because mine is poe++ with 2.5gbe ports. So i used a dc power adapter to power it just fine. So yeah if you wanna power via ethernet, just keep in mind the requirements are pretty high. Compared to say a ubiquiti U7 Pro which only needs poe+ to power it which is much easier to obtain vs poe++ equipment.
i got the same problem again.
192.168.0.24
so i was revisiting how i fixed this previously. hope it works.
the issue started after updating to the latest dragonfish truenas version. no issues before until that recent change. so something must have happened
was also looking for supplementary sources to try troubleshoot my docker networking issue
problem is 192.168.0.24:5001 is no longer working yet again.
I looked at the previous similar issue when this last happened, and the hint was to use the default jailmaker config. i tried that but same result. so i am at a loss.
the troubles started after the most recent truenas update. very weird.
managed to fix my docker 192… issue
did all the checks, and confirmations.
rolled back to a previous truenas.
redid the jailmaker config in case it got corrupted like last time. rebooted.
nothing worked, went to bed to sleep on it. woke up later checked and it worked… so weird.
anyway it works 
too bad i don’t know why it happened and how it resolved in the end.
but one thing i did find out, when i moved to eel to try and test, it broke jailmaker from loading. not sure but maybe it did not like my jailmaker config? but the end result, it couldn’t boot jailmaker for eel.
but stux in his youtube said it worked. so not sure.
even if i followed stux migrating out of jailmaker to truenas docker, it would then use the truenas ip for the docker wouldn’t it? i wanted to use a static ip different from truenas, but not sure how to do that if i did it that way.
with jailmaker i do know how to set the static ip.
so i’ll probably wait for eel to mature and see how it goes. right now i got a working config so i don’t want to mess that up again.
not fully sure, but maybe figured out why my docker lan ip was unstable.
checked my wifi was enabled same time as the wired connection. this is incorrect, as should either be connected via one or the other, not both simultaneously. i suspect some of the wonkyness was due to this. so i disconnected wifi, and disable/enable wired and it seemed stable after that.
will continue to monitor.
1 Like
when i tried to test electric eel last week, jailmaker wouldn’t load. i think the jailmaker config had issues?
any tips how people got jailmaker to work? do i have to create a new jail?
also since it didn’t work and it’s rc, i just opted to roll back.
was watching stux’s video on migration to truenas eel
it’s great that truenas offers integration for docker. i would have been fine with jailmaker because the networking worked with bridges. but if i switched to the truenas integrated method, my networking would have to be sorted out again.
i don’t want docker to use the same lan ip as truenas because i use nginx proxy manager which is the same port that truenas uses, so will be an issue.
only method i know around that is going back to using macvlans, and i only know how to do that via portainer which i no longer use.
but jailmaker is no longer actively maintained which is a shame 
the migrating from dragonfish to electric eel for jailmaker wasn’t working for me
to be fair, stux video is aimed at getting off jailmaker to switch to the native docker. whereas my goal is stay on jailmaker but on eel.
but when i tried, i ran into the jail refusing to run. so this is my mini guide what i did to get it to work, that i don’t think the youtube covered.
for truenas eel, it broke jailmaker (at least for me). I think this only affects those who were using nvidia graphics card for their jailmaker. So you may have to do changes in your config to get it to work.
so i opted to delete my docker jail and make it anew. because i felt starting from a clean slate i can eliminate potential issues far quickly rather than chase them all down 1 by 1.
what i learned is, i had to edit the jlmkr config file for my docker jail. specifically these lines
gpu_passthrough_nvidia=0
this needs to be set to 0. if u set it to 1, it won’t work. probably due to the changes in electric eel for integrating docker? not sure. Point is, it worked in dragonfish but not in eel. So had to make that change.
I also removed
--bind-ro=/usr/lib/x86_64-linux-gnu/nvidia/current
I’m not sure if leaving the bind is fine or not, but basically i removed it for now and figure it out later. main point is simply getting docker to work. most of my docker containers don’t care for graphics card.
recap. to start fresh, i removed my previous docker.
jlmkr remove docker
*my jail is named docker fyi
cd /mnt/xxxx/jailmaker
./jlmkr.py create --start --config /mnt/xxxxxx/jailmaker/config docker
*my config file is under the jailmaker folder. and the name of the jail is docker
basically what this does is, is to create the docker based on the config i just edited.
also because i removed my previous docker, i had to redo the networking in the docker jail.
i use a bridge setup so i had to first stop the jail
jlmkr stop docker
then i browse to the location of the file to edit (you can edit using nano instead if u prefer. i used winscp notepad++)
rootfs/etc/systemd/network
80-container-host0.network
i had previously backed up my settings, so i simply copied it over here and save.
once done, back in shell
jlmkr start docker
it will now load the changes i did.
then we need to reinstall back all our dockers…
keep in mind when i delete my jail, my docker data, configs, and all those files were not deleted. they were stored permanently in a separate dataset called docker.
if u check your jailmaker docker config, there is a list of binds pointing to the location where your docker files are located.
so, after the docker jailmaker is running, docker is active.
so in jlmkr shell docker
browse to where your docker stuff is located.
e.g. cd /mnt/docker
from there you can dir
then enter where your dockge compose file is located at. mine are all sorted under cd/mnt/docker/compose/dockge
once there i can then do this to install it
docker compose up -d
it will begin to download then install based on your docker compose. it was all configured long ago, so i did not have to change anything. though if dockge or any container docker compose has a change, you should do edits accordingly from time to time.
so anyway, in shell i do a docker ps
what this does is show me if i have any active running docker containers. sure enough dockge is now running.
then using dockge i can then deploy the rest of the containers.
few ways confirmed this worked
- jailmaker and the docker jail is active
- the dockge deployed is active
- in jailmaker when you list, it shows the ip for the jails. i setup mine using bridge
there is a last test, and it’s actually going to web browser, entering the ip for your container to access the web ui e.g.
http://192.168.0.24:5001
for dockge
unfortunately for me this did not work. i have a separate issue pertaining to networking that broke my dockers networking. still figuring that one out.
but for others, you can get your docker to work on jailmaker in electric eel. if you can share your success story that would be great.
keep in mind jailmaker is no longer actively maintained, so people may feel the need to just stick to native docker. stux made a great video for how to do that.
i’m just sticking to jailmaker for now which should be fine.
though i haven’t yet figured out how to fix the graphics card integration since moving to eel. but currently the graphics card should be accessible via the native docker support in eel. so that setup is more likely to have a better chance to get graphics to work for your docker if that is a requirement. not to say it wouldn’t with jailmaker for eel (i don’t know), but i haven’t figured it out yet. But what i do know is that it worked fine in dragonfish. So something changed in eel that make it no longer work for graphics card for the settings in the config file.
one thing about going from dragonfish to electric eel.
the dashboard is a mess. there is an easy fix. in dashboard edit the dashboard items, and select the pool and networks, and it will work fine.
there is also the pool where you can upgrade it. i did and it went without a hitch so far.
one other new thing i noticed in eel, was in the monitoring in truenas for netdata. now jailmaker is listed. so you can check how much cpu jailmaker is using. i don’t recall dragonfish having this sort of integration with netdata, or did it? anyway that’s nice.
I got this error
network proxy declared as external, but could not be found
in my docker compose it has this
networks:
- proxy
networks:
proxy:
external: true
any ideas how to fix this?
*update
i just changed to
networks: {}
works now.
also booted up nginxproxymanager, now the domain urls also working. will see how it does over the week, whether the old issues are still there or not. looking good so far.
tldr: i had to delete old jail and do it again from scratch. But that said, i did not lose data. I could recover my docker containers just fine after first installing dockge, then redeploy them all after minor fixes in the docker compose.
figured out why my docker container web uis couldnt be accessed.
its a very nub mistake.
basically my pfsense router was misconfigured.
the DHCP was 192.168.0.20 - 192.168.0.100
but my docker uses 192.168.0.24
which is bad because you dont want it to be within the dhcp range, unless u had reserved it prior (which i didn’t).
So the usual method was to have my docker ip fall into the same ip but outside the range
e.g. 192.168.0.19 meaning anything 0-19 would not be taken by any other devices using dhcp because it’s outside the dhcp range.
so i did not realize this as i kept using ips without noticing i had exceeded the safe zone and stepped into the dhcp range.
how i found out is, i went to pfsense and notice another device was occupying the same lan ip as what i was using for truenas jailmaker docker.
so this was why sometimes it worked, and other times it didn’t.
mystery solved.
so i merely changed 192.168.0.20 - 192.168.0.100
to 192.168.0.30 - 192.168.0.100
so now i got a bit more extra lee way 1-29
1 Like