Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Ycarus has joined #openwrt-devel
Acinonyx has quit [Read error: Connection reset by peer]
Acinonyx has joined #openwrt-devel
indy has quit [Ping timeout: 260 seconds]
indy has joined #openwrt-devel
<nitroshift>
anyone who can help me? building an image based on kernel 5.9 and under /build_dir/hostpkg i have libubox that pops out an error, missing a helper file that is included in /build_dir/hostpkg/json
<nitroshift>
the file requesting the helper is located under /build_dir/hostpkg/libubox and states #include <json.h>
<nitroshift>
what the correct syntax to point to the correct location?
<nitroshift>
nevermind, figured it out :)
Nick_Lowe has joined #openwrt-devel
Red_M has joined #openwrt-devel
Red_M has quit [Changing host]
Red_M has joined #openwrt-devel
blb4393 has joined #openwrt-devel
adrianschmutzler has joined #openwrt-devel
decke has joined #openwrt-devel
<russell-->
alix have bios at 38400 baud, but grub is defaulting to 115200
Tusker has quit [Quit: Time wasted on IRC: 1 day 7 hours 14 minutes 59 seconds]
<damex>
rsalvaterra: why?
<damex>
that is so horrible
<rsalvaterra>
damex: It's not horrible. It's UNIX. And it works, of course.
<damex>
rsalvaterra: if something works - does not mean it should be used
<damex>
like cat+grep+sed in place of awk.
<rsalvaterra>
That's an apples to oranges comparison. ;)
<russell-->
please seek medical attention immediately
<rsalvaterra>
LOL
<rsalvaterra>
Ok, I guess that's a "no". :P
woshty has joined #openwrt-devel
<karlp>
very much so...
<karlp>
build your own custom if you want to go crazy
<rsalvaterra>
In any case, I believe it's a good idea to at least have this file transfer possibility documented in the wiki. Do you agree?
<PaulFertser>
damex: if there's sed there shouldn't be any need for grep.
adrianschmutzler has quit [Quit: ~ Trillian - www.trillian.im ~]
gch9812136 has joined #openwrt-devel
gch981213 has quit [Ping timeout: 268 seconds]
gch9812136 is now known as gch981213
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rr123_ has quit [Remote host closed the connection]
gch9812133 has joined #openwrt-devel
gch981213 has quit [Ping timeout: 256 seconds]
gch9812133 is now known as gch981213
Rene__ has quit [Remote host closed the connection]
Nick_Lowe has joined #openwrt-devel
dangole has joined #openwrt-devel
<dangole>
rsalvaterra: maybe add a comment about comparing sizes and checksums when using such methods...
swex has quit [Quit: swex]
swex has joined #openwrt-devel
am0rphis has joined #openwrt-devel
dedeckeh has quit [Remote host closed the connection]
<rsalvaterra>
dangole: Oh, yeah, I noticed absolutely no reference to checksum comparison in the wiki too.
<rsalvaterra>
Wait, it's mentioned, after all.
black_ant has quit [Ping timeout: 256 seconds]
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
black_ant has joined #openwrt-devel
<rsalvaterra>
But if someone's yoloflashing without comparing hashes, I guess the file transfer is the least of his problems.
swex has quit [Quit: swex]
gch9812130 has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812130 is now known as gch981213
<ynezz>
anyone familiar with the rtl83xx u-boot? I've DGS-1210-28-F1 (RTL8382M_8218B_INTPHY_8218B_8214FC_DEMO) with U-Boot 2011.12.(2.1.5.67086)-Candidate1 (Oct 20 2017 - 15:38:59) and having issue with UART TX, tried 3 different UART converters but still not able to type in the u-boot prompt
<ynezz>
I'm able to stop the execution with the Esc key during 'Hit Esc key to stop autoboot: 0', but then nothing more
<ynezz>
is it somehow locked? couldn't find any mention about it anywhere
<ynezz>
it doesn't stop on any other key, so I assume, that the wiring is correct
<blogic>
ynezz: yes
<blogic>
esc to interrupt boot
<blogic>
then ctrl-c
<ynezz>
ooh, victory!
<ynezz>
thanks!
<blogic>
1 sec
<blogic>
owrt=tftpboot 0x8f000000 dlink10; bootm
<blogic>
use that ram addr for an initramfs boot
<stintel>
is it time to by realtek stock as the entire openwrt community will now buy rtl-based switches? :P
<rsalvaterra>
Heh… I'd really like to my TL-SG2008 v1 how to OpenWrt, as it's running VxWorks…
<rsalvaterra>
*to teach
<rsalvaterra>
… but I haven't got the equipment for it it yet (programmer and SOP8 clamp).
<PaulFertser>
rsalvaterra: raspberrypi can be used as an SPI flash programmer without additional tools.
<rsalvaterra>
Oh, really? I have a RPi B+ somewhere.
<blogic>
stintel: hehe
woshty has quit [Ping timeout: 240 seconds]
<PaulFertser>
rsalvaterra: sure, there's a page on flashrom wiki. You can connect it directly to the target chip provided Vcc is 3.3 V.
<rsalvaterra>
It's been a while, I need to measure again, but I'm almost sure it's 3.3 V.
<PaulFertser>
But you'll have to solder some wires if you have no clamp. And probably somehow take care for the SoC to not influence the communication, is there a reset pin you can pull low?
<stintel>
haha I made that mistake of hooking up a 3.3V programmer to a SPI NOR flash chip without verifying its voltage first
<stintel>
*poof*
<stintel>
now I have an Odroid XU4 with 1.8V SPI for those
<rsalvaterra>
stintel: Me too, a looong time ago… trying to turn a Sound Blaster Live! Value into a Live! Gold. :P
<stintel>
ehehehe
<stintel>
sounds long time ago indeed
woshty has joined #openwrt-devel
<rsalvaterra>
Yeah, almost 20 years ago.
nitroshift has quit [Quit: Gone that way --->]
woshty has quit [Ping timeout: 240 seconds]
woshty has joined #openwrt-devel
matteoelimo has quit [Ping timeout: 240 seconds]
mbm has quit [Ping timeout: 240 seconds]
matteoelimo has joined #openwrt-devel
[mbm] has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
SimJoSt- has quit [*.net *.split]
_jf has quit [*.net *.split]
pgwipeout[m] has quit [*.net *.split]
MatMaul has quit [*.net *.split]
flokli has quit [*.net *.split]
SimJoSt- has joined #openwrt-devel
_jf has joined #openwrt-devel
MatMaul has joined #openwrt-devel
flokli has joined #openwrt-devel
pgwipeout[m] has joined #openwrt-devel
flokli has quit [Max SendQ exceeded]
pgwipeout[m] has quit [Ping timeout: 246 seconds]
JuniorJPDJ has quit [Ping timeout: 240 seconds]
decke[m] has quit [Ping timeout: 244 seconds]
olmari has quit [Ping timeout: 260 seconds]
Floppe has quit [Remote host closed the connection]
Floppe has joined #openwrt-devel
pavlix has quit [Ping timeout: 244 seconds]
voltagex has quit [Ping timeout: 244 seconds]
aparcar[m] has quit [Ping timeout: 244 seconds]
svanheule[m] has quit [Ping timeout: 244 seconds]
MatMaul has quit [Ping timeout: 246 seconds]
fblaese has quit [Ping timeout: 246 seconds]
nick[m] has quit [Ping timeout: 260 seconds]
agb[m] has quit [Ping timeout: 260 seconds]
flokli has joined #openwrt-devel
<damex>
how come there is just adrianschmutzler reviewing PR/MR on github? should i just dump it as patches and send to maillist to get merged or what?
<damex>
feels bad that there is no adjustments left, changes work great and yet, no one can merge it
swex has joined #openwrt-devel
pgwipeout[m] has joined #openwrt-devel
fblaese has joined #openwrt-devel
nick[m] has joined #openwrt-devel
pavlix has joined #openwrt-devel
svanheule[m] has joined #openwrt-devel
decke[m] has joined #openwrt-devel
olmari has joined #openwrt-devel
JuniorJPDJ has joined #openwrt-devel
voltagex has joined #openwrt-devel
pgwipeout[m] has quit [Quit: Bridge terminating on SIGTERM]
fblaese has quit [Quit: Bridge terminating on SIGTERM]
pavlix has quit [Quit: Bridge terminating on SIGTERM]
olmari has quit [Quit: Bridge terminating on SIGTERM]
svanheule[m] has quit [Quit: Bridge terminating on SIGTERM]
JuniorJPDJ has quit [Quit: Bridge terminating on SIGTERM]
decke[m] has quit [Quit: Bridge terminating on SIGTERM]
nick[m] has quit [Quit: Bridge terminating on SIGTERM]
<PaulFertser>
Yes, they shouldn't be both started if some of them is not needed.
<rsalvaterra>
Yeah, this is a bit weird. Yes, it's a multicall binary, but they're still independent daemons…
<rsalvaterra>
So, wpa_supplicant should only be started if there's at least one STA iface. Likewise, hostapd should only be started if there's at least an AP iface.
<PaulFertser>
Yes
<rr123>
I also noticed eap_server is only enabled for WPS mode in hostapd, which is odd, eap_server should be a toggle flag in /etc/config/wireless in my opinion
<rsalvaterra>
rr123: I gather you need wpa_supplicant on your router, just not all the time, right?
adrianschmutzler has joined #openwrt-devel
<rr123>
rsalvaterra: for me it will be an AP so no need wpa_supplicant ever, but someone might need set openwrt as a client, or repeater, that will need wpa_supplicant, the point is, start wpa_supplicant when it's needed, not turn on it by default, that saves 2.3MB RAM at least
<stintel>
if you don't need wpa-supplicant ever then just use hostapd and problem solved?
<stintel>
or is wpad the default in our images
<rr123>
stintel: yes that's what I'm building, but all docs recommend wpad-*
<rsalvaterra>
rr123: Yeah, the docs… :/
<rsalvaterra>
The docs are so wonderful I just ignore them and read the source code, most of the time.
<rr123>
quote: "for bare metal system you read the doc then write the code, for linux(openwrt) you read the code then write the doc" :(
* rr123
is clueless about 'diff hostapd hostapd-openssl' in menuconfig
<rsalvaterra>
stintel: Still, just using hostapd isn't solving the underlying problem… :/
<rr123>
in Makefile they're all the same, $(Package/hostapd/install), reading Makefile now
<rsalvaterra>
rr123: I'd just use one of the hostapd-basic-{openssl,wolfssl}, depending on your requirements.
<rr123>
rsalvaterra: I'm now using hostapd and wpa_supplicant, not sure what those openssl/wolfssl are for(security? or just CA-based 8021x, or what?), also I plan to hack the init script to try out eap_server which is unsupported by current openwrt code
<rr123>
the menuconfig under wirelsssAPD is very confusing
<rsalvaterra>
For WPA3 Personal and OWE, you need openssl/wolfssl.
<rr123>
so, hostapd-wolfssl is a superset of hostapd then?
<rsalvaterra>
The WirelessAPD menu is "interesting", indeed. :P
<rr123>
looks like openwrt is shifting towards wolfssl from openssl
<stintel>
openssl was never default
<rsalvaterra>
rr123: Yes. The hostapd is a variant with embedded crypto, and only supports WPA2-PSK.
<adrianschmutzler>
the indent is completely broken as well. I once tried to fix it, but something in the internals seems to be wrong
<rsalvaterra>
adrianschmutzler: The indentation depends on the order the CONFLICTS directives are expressed, I believe.
<rsalvaterra>
I had to juggle with them a bit for the tor-basic variant.
<rr123>
ok I now enabled 'hostapd-wolfssl' and 'wpa-supplicant-wolfssl', hope that's a good alternative to 'wpad' or 'wpad-wolfssl'
<rsalvaterra>
Why not just hostapd-basic-wolfssl…?
<rr123>
there is only hostapd-basic-openssl, plus, the basic only has wpa-psk/11r/11w but I need wpa2-enterprise
<rsalvaterra>
rr123: You're not running master?
<rsalvaterra>
Ah, if you need WPA2 Enterprise you must run a -full variant.
<rsalvaterra>
If you're on master, there's definitely hostapd-basic-wolfssl. You don't need it, though. :)
<rsalvaterra>
Ah! It's just hostapd-basic.
* rr123
is trying to add eap_server compiler flag to Makefile
<rsalvaterra>
rr123: That's not enough. Not even the full variant is configured with internal RADIUS. You need an external one.
<rr123>
it appears hostapd can do basic 8021x/eap-authentication without a full freeradius somewhere else
<rr123>
but I'm unsure, thus the test
<rsalvaterra>
Wait a minute. hostapd-basic is *not* linked against wolfssl. There actually isn't a hostapd-basic-wolfssl variant!
<rsalvaterra>
Guys? Do we want to add it? If so, I'll take care of it.
<rsalvaterra>
I'm going to add it anyway, since I need it for my AirGrid M2. :P
<adrianschmutzler>
The question is whether the (relatively) few bytes that hostapd saves compared to wpad matter when we add wolfssl/openssl anyway ...
<rsalvaterra>
adrianschmutzler: The point is RAM, not storage.
<adrianschmutzler>
interesting; can you elaborate?
<rsalvaterra>
With wpad, you have two daemons. Sure, that's a different issue and should be solved too.
<rsalvaterra>
And yes, I'm aware that a good part of the processes memory is shared, but still…
<adrianschmutzler>
and this has an impact even if the relevant feature isn't used? i.e. wpad... will consume more memory if I just ran an AP compared to hostapd?
<rsalvaterra>
adrianschmutzler: wpad_supplicant is started unconditionally, even if there are no STA interfaces defined.
<rsalvaterra>
Check out the /etc/init.d/wpad script.
<adrianschmutzler>
Okay, interesting. Never thought about this in detail, I should have a closer look at some point.
damex has joined #openwrt-devel
<rsalvaterra>
And the same is valid for hostapd, it's always started even if there are no AP ifaces. :)
<adrianschmutzler>
btw I have sta interfaces running with hostapd only
<rsalvaterra>
Uhh… with no crypto, right?
<adrianschmutzler>
yes, IIRC
<adrianschmutzler>
used for configuring automatic meshing in Freifunk context
<rsalvaterra>
Yeah, I thought it would something like that.
<rsalvaterra>
*be
<adrianschmutzler>
so, network is open anyway, and whoever really wants to break the network locally will be able to anyway
<adrianschmutzler>
the switch from wpad to hostapd actually made it possible to still support the 4m flash devices with 19.07 ...
<rsalvaterra>
Sure, but this use case is related to WPA2/3 Personal, otherwise we wouldn't need no supplicant. :)
<adrianschmutzler>
Of course, I slipped into OT a little here ...
Grommish_ has joined #openwrt-devel
<rsalvaterra>
I still believe in 4 MiB. :P
<rsalvaterra>
Stripped to the bare essentials, of course, but not impossible…
<adrianschmutzler>
Well, for me it's a practical point, in Freifunk communities you frequently have 80-90 % of _devices_ with 4M
Grommish has quit [Ping timeout: 264 seconds]
<adrianschmutzler>
I try to keep them working as long as possible, so we don't create a huge pile of waste
<rsalvaterra>
Reduce, Reuse <- you are here, Recycle. :)
<rsalvaterra>
Ok, BRB…
* rsalvaterra
dives in the hostapd makefile, again…
<adrianschmutzler>
check your oxygen, don't drown there
<stintel>
hehe
<rsalvaterra>
It's not that bad, once you understand the structure… it's arguably better than the menu itself. :P
Grommish_ has quit [Ping timeout: 272 seconds]
Grommish has joined #openwrt-devel
<adrianschmutzler>
Yes, but I'm always confused by the high degree of redundancy there that cannot be optimized away
<rsalvaterra>
Complicated package is complicated. :)
<Grommish>
damex: Shield builds out/flashes fine with your octeon changes.
<Grommish>
damex: I'm still hoping you can wangle an octeon3 target so we can ditch octeonplus
<damex>
Grommish: nice, thanks. could you please report to MR?
<damex>
Grommish: i believe we could propose octeon3 subtarget later. it is harder to propose all changes at the same time
<Grommish>
damex: true, it wouldn't matter about changing it later.. just as much work
<Grommish>
But it gives us another device to justify it
<Grommish>
Or at least try to justify it heh
opal has quit [Ping timeout: 240 seconds]
<damex>
Grommish: it is not just about device. it is about what it could give beside FPU. we need to test and show that there is an actual performance improvement in openwrt related tasks
<Grommish>
damex: right.. which isn't something I could quantify prior
<Grommish>
Certainly not as the only octeon3 device
<Grommish>
err could NOT quantify
<lemmi>
for all network related tasks, i couldn't see any difference that mattered
<philipp64|work>
stintel: working on x509 support for strongswan… but noticed a few things weren’t supported… like keyingtries and left/rightprotoport...
<Grommish>
I don't know if the encryption ASICs will make a difference or not
<Grommish>
and not every octeon3 has them
opal has joined #openwrt-devel
<stintel>
philipp64|work: we're still in crisis situation at work and I'm still don't have time to properly focus on stuff outside of that
<philipp64|work>
other thoughts… what about having a common UCI for libreswan and strongswan? looking at the UCI, some of the documentation doesn’t seem to agree with /etc/init.d/ipsec …
<philipp64|work>
okay, I’ll plug at it and let you know when I have something to look at. hope the alligators aren’t snapping at your butt.
<philipp64|work>
was also thinking about migrating from ipsec.conf to swanctl.conf
<philipp64|work>
if anyone else wants to join in on the Strongswan party, more eyes on the problem are welcome…
<rsalvaterra>
adrianschmutzler: Since OpenWrt is an operating system (mostly) for wireless routers, I believe it would even make more sense for the default wireless daemon to be hostapd and not wpad…
<stintel>
philipp64|work: feel free to come up with something better :)
voxadam has joined #openwrt-devel
<adrianschmutzler>
rsalvaterra: well, that's a general "function vs. size" question, which different people will answer differently
<adrianschmutzler>
or "function vs. resource consumption" with reference to your RAM argument
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<rsalvaterra>
I'm not 100 % sure yet about the RAM argument either… It's the same executable, so the code is only mapped once. The difference will be in the data.
<philipp64|work>
stintel: I like the idea of /etc/init.d/ipsec abstracting away the “backend” and just continuing to transparently when the cut-over is made from ipsec.conf to swanctl.conf … but that means that the settings should probably have more “generic” names… which means throwing a switch.
<rsalvaterra>
Memory accounting is hard.
<adrianschmutzler>
And that's exactly why I asked about whether having relevant interfaces or not will matter
<adrianschmutzler>
So, we would come to the main measure for all these discussions: Is there a sufficient reason to _change_ the current state?
<rsalvaterra>
I'll answer that question after building/running. ;)
<adrianschmutzler>
Will be interesting in any case. However, I personally doubt you will find many allies among the committers for wpad->hostapd
<rsalvaterra>
Oh, I don't mind about whatever the defaults are. I just believe in this case it makes sense to have the choice.
<adrianschmutzler>
So, coming back to whether one should just have an hostapd-basic-xxxssl available?
<rsalvaterra>
Yep!
<rsalvaterra>
Hey, this morning I suggested disabling scp by default since we can transfer files via ssh, and I was told to seek medical assistance, so… :P
<rr123>
aren't they just the same multi-call dropbear
<adrianschmutzler>
rsalvaterra: And to which conclusion did the doctors come?
<rsalvaterra>
rr123: scp is over 14 % of the dropbear size.
<rsalvaterra>
adrianschmutzler: Right. :P
<adrianschmutzler>
But knowing that is actually an interesting lever for 4M again ...
<rsalvaterra>
Let's put it this way: my dropbear executable is 96165 bytes.
<rsalvaterra>
(74Kc, -O2)
<rr123>
dropbear here is 253K
<rr123>
but I turned on all the 'features', I probably don't need them all
<rsalvaterra>
rr123: To reduce the size as much as I did, you need to apply my pending patch series… and even then it won't be enough, as I have still a patch to compile dropbear with MIPS16 instructions.
<rsalvaterra>
The only crypto I have enabled is Ed25519, Curve25519 and ChaCha20-Poly1305.
phaidros has joined #openwrt-devel
adrianschmutzler has quit [Quit: ~ Trillian - www.trillian.im ~]
heffer has quit [Read error: Connection reset by peer]
heffer has joined #openwrt-devel
<rr123>
rsalvaterra: i think hostapd-common is the one started wpa_supplicant unconditionally, specifically, the /etc/init.d/wpad script inside it
<rr123>
it basically says if you have a wpa_supplicant installed i will run it immediately, i don't care if it's from wpad or you need it or not
<rsalvaterra>
rr123: Yes, it's what I told PaulFertser, above.
<rsalvaterra>
I wasn't expecting such a large difference in the final image size (openwrt-ath79-generic-ubnt_nanostation-loco-m-squashfs-sysupgrade.bin)…
<rr123>
you don't ever need wpa-supplicant then, mesh/client/repeater might need that?
<rsalvaterra>
rr123: Wonderful question. I have no idea. I only use infrastructure mode.
Borromini has joined #openwrt-devel
<philipp64|work>
rr123: I think the latest versions of wpa_supplicant can either be a client or AP, so for a while now that’s been all you’ve needed. It has subsumed the hostapd functionality.
Ycarus has quit [Quit: Ycarus]
dangole has joined #openwrt-devel
<dangole>
rr123, rsalvaterra philipp64|work: wpa_supplicant supports AP mode to some degree, however, we do not support making use of that in OpenWrt. It lacks WPA-Enterprise features and a few other things, but Android uses that for thethering, so it does work to some degree
<rsalvaterra>
dangole: Interesting, and quite unexpected. :)
ivanich has quit [Quit: Konversation terminated!]
<dangole>
obviously we'd also have to reimplement AP+STA (which is a local patch we've been carrying more than a decade)...
<rsalvaterra>
dangole: And here I was, thinking carrying patches for over 3 months is a lot of time…
<rr123>
dangole: thanks for the info
<rr123>
just came back from election, time to try eap_server
<rr123>
to see if it can replace freeradius for simple 8021x use case
<karlp>
has anyone tried ap+sta recently? does it stillkill the AP side if you get the wrong password on the sta side? (kill == hangs trying to reconnect sta forever, never servicing the ap side)
<karlp>
I'd be ok with terrrible perf for channel switching, but the lockout on wrong password made it pretty much useless
CrazyLemon has quit [Ping timeout: 268 seconds]
dangole has quit [Ping timeout: 240 seconds]
ChanServ has quit [shutting down]
ChanServ has joined #openwrt-devel
CrazyLemon has joined #openwrt-devel
ivanich has joined #openwrt-devel
kubrickdave has quit [Read error: Connection reset by peer]
kubrickdave has joined #openwrt-devel
feriman has quit [Ping timeout: 256 seconds]
Borromini has quit [Quit: Lost terminal]
Borromini has joined #openwrt-devel
rmilecki has quit [Quit: Konversation terminated!]