<aparcar[m]>
Well github is a mirror so it has the very same refs
rsalvaterra1 has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 256 seconds]
rmilecki has joined #openwrt-devel
danitool has quit [Ping timeout: 256 seconds]
hbug__ has quit [Ping timeout: 268 seconds]
hbug__ has joined #openwrt-devel
black_ant has quit [Ping timeout: 264 seconds]
goliath has joined #openwrt-devel
ivanich has joined #openwrt-devel
bkallus has joined #openwrt-devel
<OutBackDingo>
aparcar[m]: mmmm not from what gitlab shows compared to openwrt
<bkallus>
I've been working on porting OpenWrt to the Actiontec MI424WR Rev. I (Avanta-based) and I think I'm pretty close. The kernel can't mount the rootfs. I'm assuming the file "root.squashfs" in the build directory is the rootfs. How do I tell the kernel to look there during the boot process?
<bkallus>
I'm a total novice, and I'm assuming I'm just missing something obvious. All I've done to get this far is tftp over a uImage that I built and run bootm.
valku has quit [Quit: valku]
_lore_ has quit [Ping timeout: 246 seconds]
dorf_ has quit [Remote host closed the connection]
dorf_ has joined #openwrt-devel
nitroshift has joined #openwrt-devel
ivanich has quit [Quit: Konversation terminated!]
ivanich has joined #openwrt-devel
nitroshift has quit [Remote host closed the connection]
<plntyk>
bkallus, afaik arm architectures have either: a bootenv entry with root= on internal flash, a bootscript (.scr) which overwrrites the previous entry - when booted from usb/external storage, or the kernel has an internal root= cmdline that is executed anyway and ignores the uboot option set before (on other arches like ath79 iirc this is done)
<plntyk>
so the path is likely incorrect - since "vendor" firmware and openwrt probably use different drivers meaning paths of rootfs change
<plntyk>
rootfs should be dumped/written via mtd / or other mechanics to a rootfs partition
nitroshift has joined #openwrt-devel
ProKn1fe has joined #openwrt-devel
_lore_ has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
ProKn1fe has quit [Quit: Connection closed]
bkallus has quit [Ping timeout: 256 seconds]
<aparcar[m]>
mangix why is ugps not in packages git?
<grift>
aparcar[m]: depdencency issue with busybox-selinux annoying?
<grift>
what exactly is annoying about it?
ivanich has quit [Remote host closed the connection]
_lore_ has quit [Read error: Connection reset by peer]
_lore_ has joined #openwrt-devel
<ynezz>
aparcar[m]: perhaps ugps could be considered a core package due to PKG_SOURCE_URL=$(PROJECT_GIT)/project/ugps.git which means developed and maintained in the main tree ? But then we should probably move cgio-io from packages to main tree as well :)
<aparcar[m]>
ynezz: I'd say because a packet is "created" within the OpenWrt project doesn't mean it has to be part of openwrt.git
<aparcar[m]>
what do you think about perf, iperf, iperf3 and ethtool?
<ynezz>
in case of cgi-io it should, it's network exposed service and installed by default in release builds
<ynezz>
so we're doing review of patches on the mailing list, but do package bumps in packages feed
<grift>
cgi-io itself isnt network exposed afaik?
<grift>
atleast my security policy dont not associate networking rules with it
dorf has joined #openwrt-devel
<grift>
i guess you mean indirectly via uhttpd or another webserver
<grift>
but then a lot if 'exposed' to the network
<aparcar[m]>
grift: I think cgi-io has a direct call to upload files
<grift>
i see, i guess i overlooked that
<aparcar[m]>
ynezz: you're right, which kind of means LuCI should be part of openwrt.git đ Let's move cgi-io over to openwrt.git and move the dev utils to packages
dorf_ has quit [Ping timeout: 246 seconds]
<grift>
i still needs to address upgrading firmware via luci ( and i guess that is what does the uploading)
<grift>
for that i would like to be able to tell sysupgrade to not reboot automatically directly
Rene__ has quit [Ping timeout: 264 seconds]
<grift>
ie put it in the back group and add a sleep call or something, or just dont automatically reboot at all
<aparcar[m]>
grift: the busybox-selinux issue is that if I select the general selinux option, the build fails because the build system is confused by busybox vs busybox-selinux. I'm assuming it's an openwrt issue but still
<ynezz>
aparcar[m]: AFAIK those packages are build in phase2 anyway
<ynezz>
phase1 only builds those for images
<aparcar[m]>
ynezz: I think you're right!
<aparcar[m]>
I'll just send patches and put them in cc
<aparcar[m]>
if they did not change their mins after your response (which never got a response?) I'll see where the discussion goes to
<ynezz>
aparcar[m]: btw you can't build perf with SDK, so it makes no sense to move it to packages.git
<aparcar[m]>
but iperf correct?
<ynezz>
if I need it I `opkg install` it anyway
<ynezz>
but I might have different workflow
<aparcar[m]>
agree
<ynezz>
grift: I wish there was something like uselinux (microselinux) which could be enabled and shipped by default by !SMALL_FLASH targets
<aparcar[m]>
uh grift do you know if someone works on busybox selinux api updates? afaik it's legacy right?
<mrkiko>
grift: hoping your effort goes well, I did read your mail.
<aparcar[m]>
nbd: are you okay with moving perf(3) over?
<ynezz>
you can't do that :p
<aparcar[m]>
at least it says you're the maintainer
dorf_ has joined #openwrt-devel
<aparcar[m]>
oh iperf
rsalvaterra1 has quit [Quit: Leaving.]
<aparcar[m]>
sry
rsalvaterra has joined #openwrt-devel
dorf has quit [Ping timeout: 246 seconds]
<aparcar[m]>
ynezz: did you have a look at the AUTORELEASE patch?
black_ant has joined #openwrt-devel
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
_whitelogger has joined #openwrt-devel
<grift>
more like 2% maybe
<grift>
but it would be nice if someone with perf experience would have a closer look
<olmari>
While I don't know anything about selinux toll, in general things are always need to put into scopes... for random consumer router and especially purely AP, gain for any of migitations or "security stuff" is diminishing... but if the thing is also made to serve DNS and generally more thing than just routing, especially to internet, then it can be beneficial to use such things, but deployers of those might already know
<olmari>
better
<grift>
i dont see it like that
<grift>
selinux enhances continuity of operations , and that *ca* be beneficial equally to all
<dorf_>
yeah, I think a baseline security level is always a good place to start.
<dorf_>
security shouldn't be opt-in.
<grift>
it was linus' idea to create LSM
<grift>
and that essentially made it so that people could use an excuse and say: well mac isnt enabled by default so must not be important
<grift>
but linus' just wanted people to be able to choose between implementations
<olmari>
Like said, I didn't specifically target selinux there.. And yes I also agree that at least per default things should be safe (whatever that entails), and generally I'd say openwrt build defaults relating are just nice (of those that are implemented)
<grift>
i really have a hard time understanding why people , especially industry workers, can't see the problem with traditional access control
<grift>
same with ip6 vs ip4
<grift>
this industry should be advocating and working actively to prefer ip6 over ip4
<olmari>
The fact that form of ipv6 natting "needed" to made into existence tells alot, kinda ;P
<grift>
i was looking into the busybox built settings the other day to disable the ntpd app, and there was an option ticked prefer ip4 for dns name resolving
<grift>
things like that should just prefer ip6 instead
Borromini has joined #openwrt-devel
T-Bone is now known as f00b4r0
<f00b4r0>
grift: probably stems from the fact that ip6 is anything but reliable is many places still...
xback has joined #openwrt-devel
<nitroshift>
grift, not all isp`s have ipv6 implemented yet
<grift>
its a preference option
<grift>
ie if theres ip6 then prefer that, if not the obviously it does not apply
<nitroshift>
grift, correct, but builds are catered for everyone ;)
hsp has quit [Ping timeout: 264 seconds]
jas4711 has quit [Remote host closed the connection]
<grift>
ok then lest turn the tables
<grift>
what if i only have an ip6 stack and not ip4?
<f00b4r0>
if there's no ip4 stack enabled in the system the prefer probably doesn't apply anyway since getaddrinfo() and friends won't consider ip4
<grift>
when it comes to selinux this is why i admire red hats leadership in this industry
<grift>
they actively take the industry in a direction
<olmari>
Issue where such option stems is likely that suprisingly many places/ISP/networks/things allures systems to thign there is ipv6 connectivity (to outside world, not just stack existing) and then much everything failing, being sluggish, etc
<f00b4r0>
*nod*
<grift>
if thats true and if it just apply to getaddrinfo() then the sluggishness will currently probably be the issue for the people using ip6 only with this setting
<grift>
becaise it will try ip4 first, determines theres no connectivity, then try ip6 (or whatever)
<f00b4r0>
no. If there's no ip4 stack, getaddrinfo() doesn't "try" ip4
<grift>
anyways, its not my field of expertise i just found it ironic
<grift>
yes but openwrt build with ip4 stack?
<grift>
you said it yourself:
<grift>
09:54 < nitroshift> grift, correct, but builds are catered for everyone ;)
<grift>
last words. i might be wrong but the way i see if ip4 is favored over ip6
<grift>
it should be the other way around
<f00b4r0>
if both are available yes
<f00b4r0>
as I mentioned before, it's (unfortunately) still not rare that when both stacks are present, ip6 is less reliable. Not to mention the case where ip6 is a tunnel into ip4, in which case the performance penalty is very high.
<olmari>
Usually default state is not to favour anything but the answer that is got first (aka does not matter is it v4 or v6), obviously where both stacks are enabled and in use
hsp has joined #openwrt-devel
Piraty has quit [Ping timeout: 256 seconds]
<grift>
but asides from that compare (in some way's) the ip4->ip6 transition to the dac->mac transition
<grift>
thats why modernisation is happening so slowly
Piraty has joined #openwrt-devel
dedeckeh has quit [Quit: Ping timeout (120 seconds)]
damex has quit [Quit: No Ping reply in 180 seconds.]
damex has joined #openwrt-devel
decke has joined #openwrt-devel
ivanich has joined #openwrt-devel
Tapper has joined #openwrt-devel
grift has quit [Quit: Bye]
dedeckeh has joined #openwrt-devel
grift has joined #openwrt-devel
<ynezz>
it happens slowly, because people don't care enough
<ynezz>
this stuff needs to be made mandatory from goverment, otherwise it's optional and nobody cares
<karlp>
for many of us, the gains are extremelt hard to quantify, and the costs are real and measurable. (applies to both v6 and selinux)
<ynezz>
I mean, IIRC we've ipv6 mandatory since 2016 for new goverment services, but for example they've just launched new reservation system for covid-19 vaccination and it's ipv4 only
<aparcar[m]>
isn't it like climate change were you postpone the problem due to missing direct impact and next thing you know 30 mio routers are part of a botnet causing aws downtimes?
<ynezz>
so I keep saying, I don't care about ipv6 that mich and just wait for ipv7 :p
<ynezz>
s/mich/much/
Acinonyx_ has joined #openwrt-devel
<Tapper>
Security notice - Site break-in on 16-Jan-2021
<Tapper>
Around 0400 GMT on 16 Jan 2021, an administrator account on the OpenWrt forum (https://forum.openwrt.org) was breached. It is not known how the account was accessed: the account had a good password, but did not have two-factor authentication enabled.
<Tapper>
The intruder was able to download a copy of the user list that contains email addresses, handles, and other statistical information about the users of the forum. Although we do not believe the intruder could download the database, from an abundance of caution, we are following the advice of the Discourse community and have reset all passwords on the Forum, and flushed any API keys.
<aparcar[m]>
Tapper: are you Ted?
Acinonyx has quit [Ping timeout: 246 seconds]
<Tapper>
no mate.
<Tapper>
From the forums.
<aparcar[m]>
I see, Hi
<Tapper>
That is what pops up befor you logno
<Tapper>
login now
<ldir>
Do we know who's account was breached? Privately if need be
<stintel>
not mine, I don't have admin access and use U2F :)
<ldir>
I haven't been told it was mine but then I don't have admin either AFAIK
* Borromini
didn't even know discourse supported 2FA
<Tapper>
ldir: What I would not do to go out with good people and have a beer or to.
rsalvaterra has quit [Ping timeout: 256 seconds]
<Tapper>
two*
<Tapper>
Bring on this vaccine!
<olmari>
stintel: Thanks, dropped noise there for importance of ed25519 ;P
<stintel>
:)
<olmari>
be it any use for anyone there.. not that noise here will help either :D
<ldir>
ynezz: I think I remember... the beer worked is all I'm saying. I seem to remember a walk to the train station to check routes to airports.
feriman has quit [Quit: WeeChat 3.0]
feriman has joined #openwrt-devel
misterhsp has joined #openwrt-devel
rsalvaterra1 has quit [Quit: Leaving.]
rsalvaterra has joined #openwrt-devel
rsalvaterra1 has joined #openwrt-devel
rsalvaterra1 has quit [Client Quit]
jas4711 has joined #openwrt-devel
rsalvaterra1 has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 256 seconds]
rsalvaterra1 has quit [Client Quit]
danitool has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
<mangix>
apparently I bought a bootlooping ER-X. what did I get myself into?
victhor has joined #openwrt-devel
<damex>
might be dead flash
<damex>
get serial and check what is going on
<damex>
you can try tftp recovery though
<mangix>
dead flash sounds no good. isn't it using NAND?
<lemmi>
they have some weird flash issue. needs serial and reflash and you should be good to go again
<lemmi>
some update caused this, can't remember what
<lemmi>
tons of those dead er-x turned up cheap on ebay for easy repair
<mangix>
...wow you just made my day
glyph has quit [Quit: End of line.]
<Borromini>
mangix: you got it to play with?
<Borromini>
er-x is mt7621 no
glyph has joined #openwrt-devel
* stintel
reads 24V PoE, closes browser tab
<mangix>
Borromini: lemmi explained
<mangix>
i have no mt7621 device right now anyway
<Borromini>
mangix: he explained what they suffer from, but not what your intentions were :)
<Borromini>
stintel: hehe
<mangix>
play with for now. I only bought it for the low price.
<Borromini>
:)
feriman has quit [Quit: WeeChat 3.0]
<mangix>
that would be the second device I have with SFP, which I can't even use
<Borromini>
:P
<Borromini>
i have my first PoE client devices on the way
<mangix>
looking at it again, it's pretty barebone
<lemmi>
mangix: but that means you have the er-x-sfp. basically the same part, but just to be accurate
<Borromini>
someone on the forums told me his GS1900-8HP seems unstable with PoE, at least his aruba AP fed by it seems to reboot after an hour
<mangix>
no sd card, usb, wifi, etc...
<stintel>
Borromini: I need 2 hands to count mine :P
<Borromini>
yeah it's just a tiny wired router
<lemmi>
and the sfp port only works on master, doesn't work with 19.x.y
<Borromini>
stintel: lol
<mangix>
oh of course
* Borromini
had PoE and SFP mixed up again
<mangix>
i would not even conaider running 19.07
<mangix>
too many reports of crashing ethernet driber
<mangix>
*driver
<lemmi>
and it's passive 24V PoE, so triple check if the other device supports that or if it is going to be cooked by it
<lemmi>
i have tons of these things working, and never experienced that crashing driver problem.
<mangix>
I think it's hardware dependent
<mangix>
that is, broken mt7621 re isions
<lemmi>
apparently it has something to do with pause-frames. but almost nothing uses that in my setups, so i might just have avoided this problem that way
<olmari>
For the interested, active poe first measures is there certain resistance between certain wires, indicating there is PoE capable device present on other end, then it gives some small power so device can get power up neccesary parts to actually communicate what kind of power it really needs :)
csrf has joined #openwrt-devel
<mangix>
nnot quite like type c :)
Xesxen has joined #openwrt-devel
Xesxen has quit [Changing host]
daregap has joined #openwrt-devel
kontaxis has quit [Ping timeout: 268 seconds]
KGB-0 has quit [Ping timeout: 272 seconds]
kontaxis has joined #openwrt-devel
fork has quit [Quit: Bye.]
fork has joined #openwrt-devel
protodave_ has joined #openwrt-devel
stintel has quit [Quit: reboot - kernel update]
stintel has joined #openwrt-devel
grift has quit [*.net *.split]
nitroshift has quit [*.net *.split]
Misanthropos has quit [*.net *.split]
th3g1z has quit [*.net *.split]
Acrisor has quit [*.net *.split]
fredrikhl has quit [*.net *.split]
DragoonAethis has quit [*.net *.split]
MatMaul has quit [*.net *.split]
nslu2-log has quit [*.net *.split]
lemmi has quit [*.net *.split]
protodave has quit [*.net *.split]
KGB-0 has joined #openwrt-devel
grift has joined #openwrt-devel
fredrikhl has joined #openwrt-devel
lemmi has joined #openwrt-devel
MatMaul has joined #openwrt-devel
Misanthropos has joined #openwrt-devel
Acrisor has joined #openwrt-devel
th3g1z has joined #openwrt-devel
nitroshift has joined #openwrt-devel
DragoonAethis has joined #openwrt-devel
nslu2-log has joined #openwrt-devel
voltagex has quit [Ping timeout: 258 seconds]
nick[m]2 has quit [Ping timeout: 240 seconds]
akira25[m] has quit [Ping timeout: 240 seconds]
t4h4[m] has quit [Ping timeout: 240 seconds]
pavlix has quit [Ping timeout: 268 seconds]
svanheule[m] has quit [Ping timeout: 258 seconds]
decke[m] has quit [Ping timeout: 258 seconds]
olmari has quit [Ping timeout: 258 seconds]
pgwipeout[m] has quit [Ping timeout: 258 seconds]
JuniorJPDJ has quit [Ping timeout: 244 seconds]
MatMaul has quit [Ping timeout: 246 seconds]
fblaese has quit [Ping timeout: 240 seconds]
aparcar[m] has quit [Ping timeout: 240 seconds]
agb[m] has quit [Ping timeout: 258 seconds]
grift has quit [Quit: Bye]
grift has joined #openwrt-devel
gromero has joined #openwrt-devel
nick[m]2 has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
dedeckeh has quit [Quit: Connection closed]
pavlix has joined #openwrt-devel
urjaman has quit [Read error: Connection reset by peer]
urjaman has joined #openwrt-devel
svanheule[m] has joined #openwrt-devel
decke[m] has joined #openwrt-devel
voltagex has joined #openwrt-devel
pgwipeout[m] has joined #openwrt-devel
akira25[m] has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
swegener has quit [Changing host]
swegener has joined #openwrt-devel
decke[m] has quit [Ping timeout: 258 seconds]
t4h4[m] has quit [Ping timeout: 240 seconds]
voltagex has quit [Ping timeout: 268 seconds]
pavlix has quit [Ping timeout: 244 seconds]
svanheule[m] has quit [Ping timeout: 246 seconds]
akira25[m] has quit [Ping timeout: 240 seconds]
nick[m]2 has quit [Ping timeout: 240 seconds]
pgwipeout[m] has quit [Ping timeout: 260 seconds]
samantaz__ has joined #openwrt-devel
samantaz_ has quit [Ping timeout: 260 seconds]
_lore_ has quit [Read error: Connection reset by peer]
_lore_ has joined #openwrt-devel
dedeckeh has quit [Quit: Ping timeout (120 seconds)]
<grift>
dorf_: also seems there was a BasicAuth option added to tinyproxy but /etc/init.d/tinyproxy does not support it
<grift>
its pretty neat service though, i have it proxy http transparently for my guest network, unfortunately https transparent proxying does not work, then i have it set to filter by default and just a whitelisted some domains
Borromini has quit [Read error: Connection reset by peer]
nitroshift has quit [Quit: Gone that way --->]
MichaelOF has joined #openwrt-devel
<dorf_>
grift: yeah, it's not bad is it? if you can make it more openwrt friendly, I'm sure it would be much appreciated :)
<dorf_>
polipo and privoxy should probably be retired.
<grift>
maybe squid as well
<dorf_>
yeah, squid could also be retired. that's super-bloat central.
<grift>
yes but squid has some unique caching functionality albeit useless on routers probably
victhor has quit [Remote host closed the connection]
__lore__ has quit [Read error: Connection reset by peer]
_lore_ has joined #openwrt-devel
<dorf_>
true, squid does do caching, but that's more the domain of an x86 server.
<dorf_>
(as is squid)
<dorf_>
I forgot tinyproxy already has a luci front end.
valku has joined #openwrt-devel
<grift>
nice
Borromini has joined #openwrt-devel
feriman has joined #openwrt-devel
dengqf6 has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
dengqf6 has joined #openwrt-devel
kakaka has quit [Remote host closed the connection]
kakaka has joined #openwrt-devel
stintel has quit [Quit: reboot another kernel update]
stintel has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
bkallus has joined #openwrt-devel
koala_ has joined #openwrt-devel
<dorf_>
grift: one thing that's less than optimal with tinyproxy is the divergent-from-upstream conf file.
f00b4r0 has quit [Quit: Quitte]
<dorf_>
I'm having a hard time configuring an upstream proxy to forward all requests, when it should be trivial. :|
<dorf_>
the luci app has an issue with entering '.' in the target host field, despite the help text underneath, and it should support * for all hosts or, failing that, an empty field should parse as "all hosts and domains".
<dorf_>
there's also no method in the ui to select the proxy type, which is not so hot.
<grift>
i havent tried that functionality yet
<grift>
neither luci integration not proxy chains
Tapper has quit [Ping timeout: 240 seconds]
<dorf_>
it has potential at least :)
dedeckeh has quit [Quit: Connection closed]
linzst_ has joined #openwrt-devel
ivanich_ has joined #openwrt-devel
ivanich has quit [Read error: Connection reset by peer]
<rsalvaterra>
nbd: Actually, it's all broadcast not getting through.
goliath has quit [Quit: SIGSEGV]
<aparcar[m]>
mangix: your autoconf patch is broken
<mangix>
unfortunate
<aparcar[m]>
mangix: very, mind sending a patch?
Borromini has joined #openwrt-devel
astylian has quit [Ping timeout: 246 seconds]
<aparcar[m]>
mangix: sorry you may got some spam from me
Namidairo has quit [Ping timeout: 260 seconds]
Namidairo has joined #openwrt-devel
<Hauke>
the at91 taregt is not compoling in 19.07 any more becasue someone deleted the git tags OpenWrt points to in the reposetory and we do not have a mirror hash.
blb4393 has quit [Quit: ChatZilla 0.9.93 [Waterfox 56.3/MOZ_BUILDID]]
<Hauke>
luckyly we haev it already on our mirrors and when using the same commit hash from a random fork on github I also get the same tar.gz
<karlp>
what repo?
<karlp>
I thought mchp wsa doing a fair job of looking after this stuff?
<Hauke>
I have a fix, so OpenWrt will work again, I will also send a mail to the poeple from microchip
dedeckeh has quit [Quit: Ping timeout (120 seconds)]
misterhsp has quit [Quit: WeeChat 3.1-dev]
astylian has joined #openwrt-devel
feriman has quit [Ping timeout: 265 seconds]
shibboleth has quit [Quit: shibboleth]
linzst_ is now known as linzst
Borromini has quit [Quit: Lost terminal]
ivanich has joined #openwrt-devel
aliceussr has joined #openwrt-devel
shibboleth has joined #openwrt-devel
<aliceussr>
Hello! Who know latest driver for Ralink rt2800 and rt2x00 with full speed WiFi?
<shibboleth>
you'll be limitied by usb2 anyway
<aliceussr>
shibboleth: You about my question?
<shibboleth>
yeah
<aliceussr>
shibboleth: Big thank for you!
aliceussr has left #openwrt-devel [#openwrt-devel]
<aparcar[m]>
Hauke: what a boring 50k commit ;)
Namidairo has quit [Ping timeout: 264 seconds]
EqUaTe has quit [Quit: Someone should have labelled the future as 'some assembly required'!]
<Hauke>
it looks like the github repos for u-boot-at91 and at91bootstrap are ok, just github didn't want to talk to us and there seams to be some problems when doing "make package/at91bootstrap/download V=99"
<Hauke>
but havbing a mirror hash is good as we do not haev to clone this repo all the time
black_ant has quit [Ping timeout: 246 seconds]
rmilecki has quit [Ping timeout: 264 seconds]
Namidairo has joined #openwrt-devel
linzst has quit [Quit: Leaving]
linzst has joined #openwrt-devel
Immanuel_ has quit [Quit: Connection reset by reptilians]
Immanuel has joined #openwrt-devel
user890104_ is now known as user890104
<mangix>
Hauke: i think it was some python problem