<f00b4r0>
silly question maybe but is it ok to sysupgrade a squashfs+f2fs sd card where the rootfs_data (f2fs) has been manually expanded?
<stintel>
fyi, it didn't help me find the reason
<stintel>
f00b4r0: if it works, you'll end up with the f2fs package being back to CONFIG_TARGET_ROOTFS_PARTSIZE
<stintel>
s/package/partition/
<f00b4r0>
stintel: that's what I was worried about. Thanks!
<stintel>
make a backup, and build an image with the desired size in that symbol
<f00b4r0>
except AIUI the image builder cannot adjust that value, can it?
<stintel>
can't answer that, never used IB before
<f00b4r0>
(tbh I'm not sure why we use such utterly small rootfs_data partition sizes for sd card targets)
<stintel>
the larger the slower
<f00b4r0>
what do you mean?
<stintel>
flashing / sysupgrade
<stintel>
e.g. 1GB will have multiple minutes of downtime on sysupgrade
<stintel>
that's annoying if this is your main router or only AP
<f00b4r0>
ah. I don't know how sysupgrade operates on these targets so it's not clear to me what's at play
<stintel>
afaik it's a sync dd
<f00b4r0>
i see
<stintel>
on my apu2 I had an extra partition after the OpenWrt partitions
<stintel>
and I used those for uxc containers
<f00b4r0>
interesting. I thought anything that came after openwrt partitions would be wiped on upgrade
<stintel>
just need to make sure not to change the OpenWrt boot or rootfs partition sizes then ;)
<f00b4r0>
ah that's it :)
<stintel>
I think the partition table is only recreated if it differs from the previous one
<stintel>
not sure though, but I've used this for years and am still using it on my apu2 in Belgium
<f00b4r0>
i'll check that out
<stintel>
and you can always experiment a bit in an x86 vm
<f00b4r0>
oh, that's a good point indeed
<f00b4r0>
didn't think of that
<stintel>
although different targets have different sysupgrade logic so you could still hit something you didn't encounter before
<stintel>
there's definitely room for improvement there
<f00b4r0>
sounds like it. I might take a deeper look since I do have some incentive now :)
<stintel>
there are a few (sub)targets using scripts/gen_image_generic.sh
<f00b4r0>
and I'm expecting my KS Mochabin-5G soon too, so another interesting playground
<stintel>
and some using legacy_sdcard_*
<stintel>
and maybe talk to Daniel Golle about the subject :)
<f00b4r0>
ok, will do :)
<stintel>
something something EFI something
<stintel>
ah and/or GPT vs BIOS
<stintel>
iirc that's why we renamed it to *legacy*_sdcard_*
Borromini has joined #openwrt-devel
<f00b4r0>
makes sense. Right now I'm dealing with a rockchip device (nanopi R2S - surprisingly capable thing), not touching x86 yet. But I will eventually for $$ reasons :)
<stintel>
I think you can throw a kernel in a GPT partition without filesystem, so no more dealing with vfat
<stintel>
stuff like that
<stintel>
ahh, I need to send v2 of EAP615
<mangix>
So windows has slow I/O
<f00b4r0>
hmm. Looking at .2 changelog it seems I can entirely skip this release. "if it ain't broke, don't fix it" :)
<user95>
stintel: regarding the downtime while flashing, I'm currently working on a new lab network built around an openwrt core/edge router. one idea that came to mind is to use a super-minimal base image that does just one thing: run the actual openwrt distro in docker or lxd
<user95>
bindmount config dirs into the container. when sysupgrade time comes, just push an updated image and tell docker to switch to the new one
<stintel>
user95: I have 2x Firebox M300, conntrackd and keepalived :)
<stintel>
paying extra for fast SD/uSD helps too
<f00b4r0>
stintel: did you manage to upstream support eventually? I haven't been paying attention :)
<stintel>
f00b4r0: yes, qoriq is in master
<f00b4r0>
awesome. I need to hunt ebay then :)
<stintel>
they can be found for < 100 :P
<stintel>
maybe that was for the m200
<stintel>
ah no, there are some < 100 EUR
<f00b4r0>
most in the US tho ;P
<stintel>
mattytap is looking into the proper musl ppc64 asm fix for checking AT_HWCAP for altivec support at runtime
<stintel>
once that lands in musl we can add support for the m200 also
<f00b4r0>
nice!
<stintel>
and at some point I'll pick up the Adtran BSAP3040 donated to me by Slimey and work on support for that too
<f00b4r0>
i've just setup an ebay alert :D
<user95>
stintel, holy shit what are you routing? those look like pcengine APU's much bigger, much badder, totally psycho stepbrother :o
<stintel>
user95: just my "home" network
<stintel>
but I have 1000/600 ftth
<stintel>
granted, I went a bit nuts the last few years
<user95>
stintel, if I may ask - have you ever run *sense?
<f00b4r0>
hehe
<Borromini>
stintel: is that a supported target already, the Adtran with its NXP SoC?
<stintel>
my main switch is a Huawei S6720-32C-PWH-SI with dual 1150w psu, it can deliver full PoE++ power on all 24 ports :P
<stintel>
user95: I probably briefly looked at it at some point, but I never really like bsd
<stintel>
liked*
<f00b4r0>
poe-powered toasters will be a thing soon enough :>
<stintel>
hahaha
<user95>
stintel, actually the bsd network stack can do some nice things wrt packet mangling
<stintel>
I have a unifi switch flex under my desk, it's powered by the huawei, and powers a Cisco 7941 IP phone, a Netgear GS108Tv3 and then a spare port for when I'm working on something
<stintel>
it's super convenient
<f00b4r0>
neat indeed
<stintel>
then the EAP615-Wall is equally neat
<stintel>
I bought 2 USW Flex to power an AP and extra switch behind my media cabinet, but that one was replaced by an EAP615-Wall and a switch on the poe passthrough port
<stintel>
hoping something similar comes out with 2.5/5/10GbE PoE-PD uplink and passthrough and 4x4 or more
<user95>
I'm a sucker for those tiny tp-link boxen. spent the better part of xmas holidays 2016 with some TL-MR3020s and a soldering iron
<stintel>
I have a few TP-Link OC200 but they're extremely frustrating to work with
<mangix>
user95: i remember i bricked mine.
* Borromini
is happy to have a SOIC clip
<user95>
mangix, I still have a bricked one on a shelf somewhere. yes, I also have a SOIC clip. but I also have GL.inet AR300ext now
Misanthropos has joined #openwrt-devel
<user95>
stintel, what do you think of openwisp?
<mangix>
this is why friends don't let friends use routers without breed
<stintel>
user95: haven't tried
<stintel>
without breed?
<mangix>
third party bootloader for mips routers
<stintel>
alright, eap615-wall v2 sent out
<stintel>
now some offscreen time
<stintel>
enjoy your weekends folks
<user95>
you too
Borromini has quit [Ping timeout: 480 seconds]
Borromini has joined #openwrt-devel
cbeznea has quit [Quit: Leaving.]
Borromini has quit [Quit: Lost terminal]
cbeznea has joined #openwrt-devel
rua has joined #openwrt-devel
<neggles>
pfsense is a disaster... it can't decide if it wants to use dnsmasq or unbound, so it leaves that up to you, and it also has zero support for being behind a DHCP relay...
<neggles>
very little you learn from setting up pfsense can be used on anything else T_T
<user95>
neggles: agreed, pfsense doesn't make it easy to learn transferrable knowledge. it does make it easy to get done what you intended in the first place though
hexagonwin[m] has quit [Server closed connection]
hexagonwin[m] has joined #openwrt-devel
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
JuniorJPDJ has quit [Server closed connection]
JuniorJPDJ has joined #openwrt-devel
cbeznea has quit [Quit: Leaving.]
clayface has quit [Ping timeout: 480 seconds]
srslypascal is now known as Guest618
srslypascal has joined #openwrt-devel
srslypascal has quit [Remote host closed the connection]
<neggles>
user95: debatable. i'd sooner put OpenWrt or VyOS on anything you might put pfSense on (or the free-home-use sophos XG appliance software, but OpenWrt is superior to that in quite a few ways)
<neggles>
there are several things it straight-up cannot do
<neggles>
things which are quite common, like "can't be the DHCP server behind a DHCP relay because it's impossible to configure a DHCP server without an interface, and impossible to add an IP pool in a subnet that's not available on a connected interface"
<neggles>
the documentation is frankly crap, it's not particularly intuitive, and while it's technically open-source you can't actually build a functioning ISO image from the public sources
<neggles>
if VyOS had a decent webui pfsense would be totally redundant...
<neggles>
i'm sure it works fine for a lot of people, reddit loves it (though that's a point against it in my book :P) but I find it intensely frustrating to use for even simple things... YMMV I guess
<user95>
TBH I was quite happy with pf, later opnsense on my home router (x86 passive cooled, MSI windbox)... it made a complex multi vlan, multi wan config with numerous services achievable without getting to know all the command line args and various config file stanzas by heart...
<user95>
then they dropped i386 support and I went all openwrt (was already running it on APs)
srslypascal has quit [Remote host closed the connection]
srslypascal has joined #openwrt-devel
srslypascal is now known as Guest628
srslypascal has joined #openwrt-devel
srslypascal is now known as Guest629
srslypascal has joined #openwrt-devel
Guest629 has quit []
Guest628 has quit [Ping timeout: 480 seconds]
mattytap_ has joined #openwrt-devel
mattytap has quit [Read error: Connection reset by peer]
srslypascal has quit [Ping timeout: 480 seconds]
srslypascal has joined #openwrt-devel
ecloud has quit [Ping timeout: 480 seconds]
ecloud has joined #openwrt-devel
cbeznea has joined #openwrt-devel
user98 has joined #openwrt-devel
bluew has joined #openwrt-devel
user95 has quit [Ping timeout: 480 seconds]
clayface has quit [Ping timeout: 480 seconds]
user98 has quit [Remote host closed the connection]
Guest600 is now known as Rayyan
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
zatwai_ has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
zatwai has joined #openwrt-devel
<Slimey>
successfully migrated our edge switches from 3850-12XS-E to 9500-12Q-A
swalker has joined #openwrt-devel
mattytap__ has joined #openwrt-devel
mattytap_ has quit [Ping timeout: 480 seconds]
Borromini has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
minimal has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
clayface has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
shibboleth has joined #openwrt-devel
Luke-Jr has joined #openwrt-devel
cbeznea has quit [Quit: Leaving.]
cmonroe has quit [Ping timeout: 480 seconds]
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
den has joined #openwrt-devel
den has quit []
<takimata>
so I don't know who to report this to, or if it even makes any sense, but just in case it does and it points to some glitch in the build system:
<takimata>
on 21.02.1 x86-64 squashfs-combined-efi images, df reports the overlayfs filled with ~58 MB (with /overlay just having some 50 KB of files)
<takimata>
doesn't happen with 21.02.2 ... so it's not a problem, but it's ... weird.
<takimata>
if that's something that has been fixed in the last few months, please ignore and sorry for the noise.
<takimata>
(I was just wondering why the heck my overlay is already 2/3rds full with me barely having installed any packages or edited any files.)