<schmars[m]>
are 802.11s (mode=mesh) devices supposed to be ignored by hostapd?
slh has joined #openwrt-devel
slh64 has joined #openwrt-devel
jschwart_ has quit [Ping timeout: 480 seconds]
jschwart has joined #openwrt-devel
minimal has quit [Quit: Leaving]
philipp64 has joined #openwrt-devel
philipp64 has quit []
Tapper has joined #openwrt-devel
<olmari>
schmars: I'm no dev at all.. but I do remember mesh and other "advanced" stuff needs full(er) hostapd/wpad set
<olmari>
what comes in owrt usually per default is quite sllimed down to save space... caters for most common usecases aka AP with WPA2-PSK (dunno how is WPA3-SAE nowadays as defaults)
<rsalvaterra>
Mangix: I hadn't sent those precisely for those reasons. The second one not for being suspicious, but because I haven't tested all ath9k hardware families (case in point, AR5008; I have a card to test, but not a computer with the PCI slot it requires :P).
<rsalvaterra>
This was quite surprising. I had no idea b43 could also provide a hwrng, if it weren't for this conversation. I believe CONFIG_B43_HWRNG should be user-visible.
jlsalvador2 has joined #openwrt-devel
* slh
05:00.0 Network controller [0280]: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] [168c:0023] (rev 01) albeit in a Debian (client/ workstation-)system and not really much time/ nor rng specific knowledge to evaluate the quality of it
<slh>
I haven't actually used that card forever, it's sitting in a workstation with two 1000BASE-T ethernet cards and doesn't really need/ use wireless
rua has joined #openwrt-devel
<slh>
ar5008 has never been really reliable, pretty similar silicon to ar9102/ ar9103, early draft-n ...stuff
<Tapper>
what is the path for vvlm on ubuntu?
<Tapper>
sorry llvm
<Tapper>
I am asking for the host llvm toolchane path
<slh>
binary should be in the search path (as in /usr/bin/clang-13), but there's probably also /usr/lib/llvm-13/bin/ <-- extrapolating from Debian/unstable and clang-13
<hauke>
mrkiko: is openwrt with VDSL working on the FritzBox 7530?
<tmn505>
Grommish: I see that dwfreed provided solution. Keep in mind that GitHub archive links provide cached files, so if the tarball gets deleted and recreated or system serving it gets updated, the checksum will change. For elaborate description https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745. I remember that being the case at least two times.
<Grommish>
tmn505: *nod* I was reading about issues in 2017 regarding it whe github updated their backend. I ended up just going the clone route and callng it a day. In the end, it saves more on-disk footprint by being able to use tar.xz vs .tgz or .zip
<Grommish>
Even thogh it's a huge upfront data expense
<Grommish>
tmn505: I appreciate the followup from you though!
<Grommish>
If they don't provide a release tarball, I'm not sure there is anyway around it.
<tmn505>
yeah, at least they could set up simple action to upload the tarball to releases.
<Grommish>
Well, worse is they date their branches like they freeze them, but then push upstream pulls without a new date :) Luckily, it happened when it did and not after which would have broken it across the board
<tmn505>
that is why I trigger myself the action on one of my repos, so it gets done when necessary
rua has quit [Ping timeout: 480 seconds]
Tapper has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
<schmars[m]>
is hostapd only started for devices that have encryption configured? trying to figure out why my plaintext mesh device doesn't show up in hostapd