<Grommish>
and that'll be in the ./target/linux/xxxx/base-files
<OutBackDingo>
Grommish: yikes... im trying to figure out, how firmware updates can be done from a management system if it has X different devices, and X different versions of firmware per device
nitroshift has joined #openwrt-devel
<OutBackDingo>
so logic is hey device what are yopu, and what firmware version are you running
<Grommish>
OutBackDingo: Well.. Each target will have it' own file and compat for sysupgrade to key against
<Grommish>
check the /lib/upgrade/platform.sh
<OutBackDingo>
so basically device answers with im a "DEVICE" with "Version"
<Grommish>
Yes, which will key against the compatiblity of the target baked into the image
<OutBackDingo>
no easy solution LOL
<Grommish>
Well, it is
<Grommish>
your target name is in the image file
<Grommish>
openwrt-octeon-itus_shield-router-squashfs-sysupgrade.tar for example
<OutBackDingo>
right but how does the system know which image to give the device... this is the problem
<Grommish>
Gotcha
<Grommish>
Well.. You should use ssh and script automation to read that board_name
<OutBackDingo>
its alsmost like we have to maintain a "device" database itself for devices/fimrwares
<Grommish>
hehe All.. Welcome to the wonder world of OpSec?
<OutBackDingo>
or write code to get boardname/model/version and release
<OutBackDingo>
and store that when the device rgisters to the system
<OutBackDingo>
be easier for it to say, im runing on firmware image "name" LOL
<Grommish>
If you use SSH certs, you can just do: ssh <address> cat /var/sysinfo/model
<Grommish>
from the management system
<Grommish>
and use that to decide which sysupgrade to scp
<Grommish>
then execute it via ssh remote from /tmp
<Grommish>
Throw an exception if it can't match the model/board_info
<Grommish>
If you are building from source, you can always just edit your targets to read whatever you want
<Grommish>
or plant an additional identifer in that 01_sysinfo
<Grommish>
or platform.sh
<Grommish>
platform.sh is where those board_info and model are populated
<OutBackDingo>
yeah i guess we have to build a promper hi, im board arch, target, name, version
<Grommish>
Then you can just rebase your local source repo to bounce those change to the top rather than pulling
<Grommish>
so you're kept up to date with the upstream. I do this to re-add the 2 additional boot slots on my device locally, for example
AlexisEvelyn has joined #openwrt-devel
<OutBackDingo>
yes that all make sense if your only using a single device type
<Grommish>
./scripts/env is your friend :)
<Grommish>
You can setup multiple target environment with their own .config
<Grommish>
and just switch between then
<OutBackDingo>
or we can say any device in target A and target B, then derive the the device soecific
<OutBackDingo>
basically Target System and Target Profile
<AlexisEvelyn>
Hi, is the the correct place to ask about how one can get started on compiling OpenWRT for an unsupported modem? Basically, I want to add support to a modem I have. I've already successfully built coreutils statically using the OpenWRT mips32 compiler (which I used sha256sum from coreutils to make sure I correctly dumped the stock firmware via
<AlexisEvelyn>
netcat). So, if having the stock firmware helps with figuring out how to add support, I already have it dumped.
<Grommish>
I've got ./script/env defines for my Shield, th ER10x, the rpi4 and an x86_64 target
<Grommish>
AlexisEvelyn: Ideally, You'd find a supported device that uses the SoC for you're device, see what needs to be changed and define the new target
<Grommish>
AlexisEvelyn: What device?
<AlexisEvelyn>
It's a Sagem 4320. It has a 2 core Broadcom4350 V8.0 cpu and a BCM6306KMLG adls line driver chip.
<Grommish>
I know Broadcom people consistently complain about lack of drivers because.. broadcom
<Grommish>
but I dunno if that'd judt Wifi or everything
<AlexisEvelyn>
I was unable to figure out any alternate names for the modem, so I was stuck on finding any related firmware that would work (e.g. if the same modem was supported under a different name),
<Grommish>
That uses that SoC and there is al ink from tmomas in that thread on how to start poking at it
<Grommish>
Might be a good starting point
rmilecki has joined #openwrt-devel
ivanich has joined #openwrt-devel
<Grommish>
mangix: ping
<Grommish>
mangix: I got asked this and I don't know how to answer, gimme a hint? "I made a patch, sent it to the mailing list. It got reviewed and I was asked to make some changes. After sending V2 I realised I didn't cc the original reviewer, so I am not sure they see it. The email was only addressed to the mailing list. Resend (and dupe) or send as a v3?"
ivanich has quit [Remote host closed the connection]
ivanich has joined #openwrt-devel
<AlexisEvelyn>
So, it looks like I need to learn by looking at previous commits. https://openwrt.org/docs/guide-developer/adding_new_device. It appears that I might have bootloader tftp as when I telnet into the device (without issuing the sh command to gain full shell), I can see a tftp command. This is when the modem is fully booted up, so I don't know for sure
<AlexisEvelyn>
if this is the bootloader tftp command or just a regular one (I've never used ftp on a bootloader before).
<AlexisEvelyn>
Oh, nevermind, it is bootloader. This is an example argument. `-g -t i -f filename server_ip Get (flash) broadcom or whole image to modem`
<Grommish>
tftp is it's own protocol similar to ftp, but different (trivial file transport proto).
<Grommish>
AlexisEvelyn: You can use tftpd64 if you're Windows based. Easy to setup
<Grommish>
Most NAS boxes have it built in as well, if you've got one on the network
<AlexisEvelyn>
I'm on a Mac. I did not realize it was a different protocol, but I can probably find a version of a tftp server for Mac (or if that fails, then I'll use Virtualbox for Windows or Debian).
<Grommish>
*nod* I'm sure Mac has a tftp, but I have no knowledge of the Mac ecosphere
<rmilecki>
if (!ofpart_node && !mtd_is_partition(master))
<rmilecki>
i thought that mtd_is_partition is false also only for master MTD device
<rmilecki>
so if there is a problem it should be in both: upstream and our 5.4 backport
ivanich has quit [Read error: Connection reset by peer]
ivanich_ has joined #openwrt-devel
<philipp64>
AlexisEvelyn: well, not quite. The MacOS firewall doesn't like TFTP.
<AlexisEvelyn>
Huh. I'm not sure why it wouldn't. I have the "automatically allow built in software to receive incoming connections" box ticked on and the router is able to tell me if a file exists on the tftp server (I created a blank file called test.txt and it can tell when the file exists when I retrieve it).
<AlexisEvelyn>
I'm currently just trying to work out how to have the router boot from a firmware image and not flash it. The tftp client hints that the only options involve flashing the firmware image.
<AlexisEvelyn>
I know the router is not able to write the test.txt file, it throws `tftp: write error`, but that's probably due to it being a blank file and not a config file like it was expecting.
Acinonyx has quit [Ping timeout: 240 seconds]
Acinonyx has joined #openwrt-devel
Tost has joined #openwrt-devel
<philipp64>
turn off the firewall and try again.
<philipp64>
but reading is a better test.
valku has quit [Quit: valku]
<AlexisEvelyn>
Once I can figure out what tftp considers a config file, I'll be able to confirm if it completely works or not. Currently the command `tftp -p -t f -f /etc/gateway.conf 192.168.254.1` results in `tftp: server error: (2) Access violation` and the next line being `tftp: Could not back up config file.`.
<AlexisEvelyn>
This is being ran as the root user.
<AlexisEvelyn>
I'm actually thinking of trying to see if I can boot directly from usb without overwriting the existing firmware, so that way once I can build an image, I can test it without bricking the device.
<AlexisEvelyn>
This is because the tftp command seems to hint at only being able to flash config/images and not just booting from a temp directory.
danitool has joined #openwrt-devel
danitool has quit [Client Quit]
<rmilecki>
blocktrr1: there's a bug indeed I think
<AlexisEvelyn>
Good news is, I can access files from my USB drive on the router. Bad news is, I have no idea how to get the router to reboot using an image. Sure, I can probably modify cmdline, but then I run the risk of bricking the router (and while I've used serial before using my RPI's GPIO pins, but I'm not entirely sure that I can unbrick from that).
rsalvaterra has joined #openwrt-devel
<AlexisEvelyn>
Like, I know it's possible to temporarily reboot from a file as I've done it before on an old Android phone while experimenting with Linux. I just don't know what commands the app used to accomplish the temporary boot switch.
figgyc has quit [Quit: No Ping reply in 180 seconds.]
<rmilecki>
blocktrr1: i've a fix ready
figgyc has joined #openwrt-devel
<rmilecki>
blocktrr1: i've to describe my changes & send the fix, i'll do that today
<AlexisEvelyn>
I can confirm that my flash drive lights up before networking is done and then it stops, then lights up after networking is done. So I believe the router is checking the usb for something (potentially a boot image).
Borromini has joined #openwrt-devel
hbug___ has quit [Remote host closed the connection]
<ynezz>
pkgadd: can you incorporate the review comments in #4060?
hbug___ has joined #openwrt-devel
clayface has joined #openwrt-devel
glyph has quit [Read error: Connection reset by peer]
<PaulFertser>
philipp64: hey. Were you able to login to wiki?
Immanuel has quit [Quit: Connection reset by reptilians]
<jow>
rmilecki: not sure how to answer that
<rmilecki>
oops ;)_
<jow>
I am open to alternative suggestions
Immanuel has joined #openwrt-devel
<jow>
the underlying uci config is such an extreme clusterfuck that I pretty much gave up trying to visualize it
<aparcar[m]>
any advise on how to disable services during first start? should I just add a uci-defaults file containing a list of `service foobar {stop,disable}`?
<rmilecki>
jow: oh :/
<rmilecki>
i thought that you got sth nice with nbd after all
<jow>
there's two way to define bridges
<jow>
then the weird bqackwards indirect way to attach wireless interfaces to bridges
<rmilecki>
jow: is that a problem with netifd and UCI? or just DSA complexity?
<jow>
semantically overlapping with list/option ifname
<jow>
I'd say a problem with netifd/uci
<jow>
that config is organically growns over the course of 15 years or so with no clear concept on the desired semantics, no clear teminology, no proper definition of involved entities, their relation ships, constraints etc.
<rmilecki>
jow: i was thinking about improving LuCI, now I'm wondering if we should refactory netifd/uci instead
<jow>
lot's of implicit state, alternating defaults, ...
<jow>
double of even triple overloaded options with different semantics and acceptable values depending on context and chosen protocol
<jow>
proto handlers spawning virtual sub interfaces or not depending on options
<rmilecki>
jow: ok, so I guess reworking netfid is they way to go
<rmilecki>
jow: any tips where to start? what should we do first to clean up that mess?
<jow>
no, redesigning the network config first, then change whatever needs changing
<jow>
compe up with a clear and consistent way to express desired configuration
<jow>
draw a clear destinction between layer 2 (bridges, vlans, tunnels) and layer 3 config
<rmilecki>
hard to redesign config options that are not even properly documented anywhere :|
<jow>
a proper way to deal with dual stacked configuration
<jow>
no @wan vs. wan6 vs. wan_6
<jow>
a sane way to related wireless netdevs to layer2 objects such as bridges
<jow>
*relate
<jow>
and not some "just use wireless.wifi-iface.network" crap which does different things depending on how the destination network is defined
<jow>
(is it a bridge? then bridge it. is it a vlan? maybe a vlan on top of a bridge, then bridge it too? is it a netdev? then just inherit ip settings. is it a netdev already in use by something else? then overwrite random ip settings or simply do nothing, depending on the phase of the moon)
<rmilecki>
jow: ok, you concinced me about the mess we have there
<rmilecki>
*convinced
<jow>
I recently learned that we now also support vlan aliases
<jow>
and that settings in "config interface lan; option type bridge" will conflict with ones in "config device; option type bridge; option name br-lan"
<jow>
one would assume they get merged internally, but nope, undefined behaviour
<jow>
so you now need to add ui logic to forbit the creation of a device called "br-foo" if a "config interface foo; option type bridge" exists
<barhom>
Rule is being added but it seems like it gets added to the INPUT chain which means I cannot alter the routing, I'd like that rule to hit the PREROUTING chain instead. Can I do that from uci configs?
<jow>
barhom: add `option dest '*'`
<jow>
specific src & dest or src & dest '*' -> FORWARD, src '*' & specific dest -> POSTROUTING, dest '*' & specific src -> PREROUTING, any src and unset dest option -> INPUT, all other cases OUTPUT
<barhom>
That worked! Thanks
<barhom>
Makes sense, thanks
Immanuel has quit [Quit: Connection reset by reptilians]
Immanuel has joined #openwrt-devel
Radu-Mamy has joined #openwrt-devel
<blocktrr1>
rmilecki: will do when im finished with work
<rmilecki>
blocktrr1: thx
swex has quit [Ping timeout: 268 seconds]
decke has quit [Quit: Leaving.]
<rmilecki>
jow: thanks for explanations
<rmilecki>
jow: i'm wondering thoug if we shouldn't require all "dynamic" devices like tap, tunnels, etc. to be explicitly defined
swex has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
kristrev has quit [Read error: Connection reset by peer]
Immanuel has quit [Quit: Connection reset by reptilians]
kristrev has joined #openwrt-devel
Immanuel has joined #openwrt-devel
kristrev_ has joined #openwrt-devel
kristrev has quit [Ping timeout: 265 seconds]
Neighbor11111119 has quit [Ping timeout: 252 seconds]
kristrev_ has quit [Ping timeout: 240 seconds]
Neighbor11111119 has joined #openwrt-devel
kristrev has joined #openwrt-devel
kristrev has quit [Ping timeout: 268 seconds]
Borromini has quit [Ping timeout: 240 seconds]
kristrev has joined #openwrt-devel
guidosarducci has quit [Remote host closed the connection]
<JonOsterman>
why there are more and more warnings like: WARNING: Makefile 'package/feeds/packages/collectd/Makefile' has a dependency on 'libcurl', which does not exist
<AlexisEvelyn>
Here's something interesting. For compiling libelf-0.8.13, the Makefile has `--target=x86_64-apple-darwin20.4.0 --host=x86_64-apple-darwin20.4.0 --build=x86_64-apple-darwin20.4.0` with `--enable-elf64` and the error is `configure: error: neither int nor long is 32-bit`.
Tost has joined #openwrt-devel
<AlexisEvelyn>
I believe that is related with Apple removing support for 32 bit. Not entirely sure why it's trying to build for OSX, when I'm trying to build firmware for testing ram only booting. I'm trying to see what happens when I build a generic (smp bcm63xx) firmware (generic as in not for a specific device, not the 1 core option). Looks like I'll be using
<AlexisEvelyn>
Debian in Virtualbox.
JonOsterman has quit [Remote host closed the connection]
greearb has quit [Read error: Connection reset by peer]
<AlexisEvelyn>
I discovered by looking through example logs that on the Wiki that one can load tftp in ram only (using the version of tftp on the router), but it has to be a custom ramdisk build. As I have to restart to enable Virtualbox, I'll see you on the other side.
AlexisEvelyn has quit [Quit: Connection closed]
JonOsterman has joined #openwrt-devel
greearb has joined #openwrt-devel
AlexisEvelyn has joined #openwrt-devel
Borromini has joined #openwrt-devel
silverwhitefish has joined #openwrt-devel
feriman has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
JonOsterman has quit [Remote host closed the connection]
JonOsterman has joined #openwrt-devel
Slimey has quit [Read error: Connection reset by peer]
Slimey has joined #openwrt-devel
goliath has joined #openwrt-devel
AlexisEvelyn has quit [Quit: Connection closed]
dwmw2_gone has quit [Quit: Coyote finally caught me]
dwmw2_gone has joined #openwrt-devel
zkrx has quit [Ping timeout: 265 seconds]
slh64 has quit [Ping timeout: 260 seconds]
slh64 has joined #openwrt-devel
slh64 has quit [Client Quit]
JonOsterman has quit [Remote host closed the connection]
JonOsterman has joined #openwrt-devel
slh64 has joined #openwrt-devel
zkrx has joined #openwrt-devel
Acinonyx_ has quit [Ping timeout: 260 seconds]
Acinonyx has joined #openwrt-devel
dedeckeh has quit [Quit: Connection closed]
anothernicforirc is now known as eJunky
dedeckeh has joined #openwrt-devel
AlexisEvelyn has joined #openwrt-devel
JonOsterman has quit [Remote host closed the connection]
JonOsterman has joined #openwrt-devel
eduardas has quit [Quit: Konversation terminated!]
dedeckeh has quit [Quit: Connection closed]
JonOsterman has quit [Remote host closed the connection]
JonOsterman has joined #openwrt-devel
shibboleth has joined #openwrt-devel
JonOsterman has quit [Remote host closed the connection]
JonOsterman has joined #openwrt-devel
AlexisEvelyn has quit [Quit: Connection closed]
rmilecki has quit [Ping timeout: 240 seconds]
eJunky has quit [Ping timeout: 250 seconds]
JonOsterman has quit [Remote host closed the connection]
JonOsterman has joined #openwrt-devel
feriman has quit [Ping timeout: 240 seconds]
black_ant has quit [Ping timeout: 246 seconds]
ivanich_ has quit [Quit: Konversation terminated!]
Tost has quit [Ping timeout: 240 seconds]
JonOsterman has quit [Remote host closed the connection]
JonOsterman has joined #openwrt-devel
nslu2-log has quit [Quit: Disconnecting from stoned server.]
Dagger has quit [Ping timeout: 260 seconds]
nslu2-log has joined #openwrt-devel
Borromini has left #openwrt-devel [#openwrt-devel]
Dagger has joined #openwrt-devel
lnslbrty has quit [Ping timeout: 252 seconds]
goliath has quit [Quit: SIGSEGV]
nslu2-log has quit [Quit: Disconnecting from stoned server.]
nslu2-log has joined #openwrt-devel
gladiac133779 has quit [Read error: Connection reset by peer]
JonOsterman has quit [Remote host closed the connection]
gladiac133779 has joined #openwrt-devel
JonOsterman has joined #openwrt-devel
shibboleth has quit [Quit: shibboleth]
lukedashjr has joined #openwrt-devel
luke-jr has quit [Ping timeout: 240 seconds]
luke-jr has joined #openwrt-devel
lukedashjr has quit [Ping timeout: 252 seconds]
<pkgadd>
ynezz: done (re PR#4060)
JonOsterman has quit [Remote host closed the connection]