<somedudenameddud>
hi I'm having some trouble with the latest build and SELinux, the following AVC is what I'm seeing, wondering if anyone could help me out. avc: "avc: denied { write } for pid=2405 comm="fw3" name="net" dev="proc" ino=2722 scontext=u:r:sys.subj tcontext=u:r:sys.subj tclass=dir permissive=0"
dorf_ has joined #openwrt-devel
dorf has quit [Ping timeout: 260 seconds]
hbug has quit [Ping timeout: 268 seconds]
<somedudenameddud>
it occurs 3 times on boot
<somedudenameddud>
with different pid's each time same comm"="fw3"
<somedudenameddud>
im trying to figure out if this is a false positive or something which should actually be blocked.
zjason has quit [Ping timeout: 240 seconds]
<somedudenameddud>
looks like port 80 on lan is blocked, maybe the file which fw3 is trying to write is responsible for opening port 80
<owrt-snap-builds>
build #780 of ath79/nand is complete: Failure [failed tools] Build details are at http://buildbot.openwrt.org/master/images/builders/ath79%2Fnand/builds/780 blamelist: Martin Kennedy <hurricos@gmail.com>, Yanase Yuki <dev@zpc.sakura.ne.jp>, Paul Spooren <mail@aparcar.org>, Sungbo Eo <mans0n@gorani.run>, Adrian Schmutzler <freifunk@adrianschmutzler.de>,
<owrt-snap-builds>
Ewan Parker <ewan@ewan.cc>, David Bentham <db260179@gmail.com>, Alexey Kunitskiy <alexey.kv@gmail.com>, Thomas Beckler <thomas.beckler@hotmail.com>, Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
<aparcar[m]>
mangix: do you understand why the bots fail?
gromero__ has joined #openwrt-devel
gromero_ has quit [Ping timeout: 272 seconds]
<mangix>
aparcar[m]: not trolling
<aparcar[m]>
mangix: more secure access to resources on the device, grift is the expert
nslu2-log has quit [Remote host closed the connection]
nslu2-log__ has quit [Remote host closed the connection]
nslu2-log has joined #openwrt-devel
nslu2-log_ has joined #openwrt-devel
blb4393 has joined #openwrt-devel
poljar has joined #openwrt-devel
poljar1 has quit [Ping timeout: 256 seconds]
feriman has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
Tapper has joined #openwrt-devel
<grift>
aparcar[m]: maybe you should update your blog port with updated instructions?
<grift>
finally had someone trying it and actually stumbling upon a interesting bug but was asleep and now he is gone leaving me wondering what the issue was
<grift>
might have been a device specific issue
rmilecki has joined #openwrt-devel
danitool has joined #openwrt-devel
<aparcar[m]>
grift: I'll give it more testing and update the post or write a follow up
<aparcar[m]>
do you have more pointers to include? Please write an email to me I'm about to leave
<grift>
ok yes, instructions where to report issues and get help and what info to provide
blb4393 has quit [Quit: ChatZilla 0.9.93 [Waterfox 56.3/MOZ_BUILDID]]
dangole has quit [Remote host closed the connection]
<Borromini>
nbd: my bisect points me to 8dc5d4a0, but that's a tiny MT7915 commit, so i don't think that's it. all other commits tested have had more than 10h uptime, and no errors. 8dc5d4a0 showed errors after ~6h up. i have collected logread output if you'd like, with ieee80211/mt76 debugging on
<karlp>
philipp64: sort of, not often I can behlpeful though?
dedeckeh has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
<philipp64>
karlp: the strongswan reviews are languishing so I broke the PR's into single commits so that some of them might make progress instead... I've added you as a reviewer to a couple of them...
<karlp>
I can't do muhc more than trivial style stuff.
blb4393 has quit [Quit: ChatZilla 0.9.93 [Waterfox 56.3/MOZ_BUILDID]]
<hurricos>
oh dear, I'm being blamed.
koniu has quit [Remote host closed the connection]
vrpatil has joined #openwrt-devel
koniu has joined #openwrt-devel
<philipp64>
karlp: trivial it is.
<vrpatil>
hello, trying to install mwan3 on development version of opwenwrt(Im porting Archer A6 v3), but it always complain Kernel version mismatch, stating I have to migrate to new version of Kernel. But I was already on quite recent version(1/2 commits behind). Doesn any one know hwo to resolve this issue?
<PaulFertser>
vrpatil: when you're installing any kmods you need the kmod files that were compiled along with the kernel you're running.
<vrpatil>
ok. So the dependency needs to specified explicitly in Architecture specific board file or Kernel config?
<PaulFertser>
vrpatil: look at what mwan3 is trying to install. It's some kmod, so you need the kmod you compiled yourself. Just that, install it before retrying to install mwan3.
<vrpatil>
ok thanks
<PaulFertser>
Most probably it's already compiled if you didn't mess with the kernel and openwrt configs too much.
dangole has joined #openwrt-devel
dorf has quit [Remote host closed the connection]
dorf has joined #openwrt-devel
<Borromini>
vrpatil: you need to compile everything in one go. at least, when it concerns kernel modules and the matching kernel.
<Borromini>
can't build A, flash A, then notice you need another kmod, recompile (b) with said kmod, try to install said kmod. you need to flash b to install said kmod (if you didn't compile it in)
<Borromini>
the moment you change kernel stuff, the checksum changes, and opkg will refuse the packages
dorf has quit [Ping timeout: 240 seconds]
dorf has joined #openwrt-devel
adrianschmutzler has joined #openwrt-devel
<Grommish>
adrianschmutzler: Did you find any issues with using the append-metadata?
lipnitsk has joined #openwrt-devel
feriman has joined #openwrt-devel
<nick[m]1>
can someone confirm that hostapd_cli -i wlan0 all_sta is not working?
<nick[m]1>
or it is just my own setup
<adrianschmutzler>
Grommish: Well, this thing started because I gave SUPPORTED_DEVICES a non-zero default value
<adrianschmutzler>
because x86 target uses append-metadata for signing images, and it then broke because append-metadata was actually adding metadata
<adrianschmutzler>
so, I looked for other cases where this was used
<adrianschmutzler>
and in your case, I don't understand why it is needed, since upgrade should be verified differently.