danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<aiyion>
Heyho. Quick question regarding SPI Flash. I'm trying to dump an AC1200 4G from Wavlink.
<aiyion>
Opened up, found the flash: GigaDevice 25Q128ESIG3
<aiyion>
flashrom does find "GD25B128B/GD25Q128B" or "GD25Q127C/GD25Q128C". Is the E variant just not yet supported in flashrom? or am I missing something?
<\x>
you just try one
<\x>
if the first one fails you try the second one
<\x>
it wont matter on read most of the times, but try reading with both chip profile
<\x>
as for write, whichever succeeds and finishes verify stage should be okay. gooluck to your firmware modding adventure ;)
<aiyion>
I found a thread where others implemented a somewaht support for the AC1200, the quectel modem worked in a cudy device I did half a year ago, so maybe this will be done after the weekend :)
soxrok2212 has quit [Ping timeout: 480 seconds]
Gaspare has joined #openwrt-devel
valku has joined #openwrt-devel
<aiyion>
\x This chip is taking its time; but I read the flash sucessfully with each of the two cipsettings thrice and have now six times the (hashsum verfied) same image.
<\x>
good
<aiyion>
"U-Boot 2018.09-g7cde25f-dirty fo" now that's going to be fun.
tlj_ has joined #openwrt-devel
tlj has quit [Ping timeout: 480 seconds]
soxrok2212 has joined #openwrt-devel
G10h4ck has joined #openwrt-devel
<G10h4ck>
Hello!
<Slimey>
hi
Slimey has quit [Quit: Going offline, see ya! (www.adiirc.com)]
Slimey has joined #openwrt-devel
Borromin1 has joined #openwrt-devel
<f00b4r0>
sorry for OT but would anyone here have a recommendation for a reputable online seller of refurb IT equipment (I'm looking for server RAM) in the EU? All the ones I find are in the US
* f00b4r0
would like to boost his buildbots on the cheap :)
<[Pokey]>
f00b4r0: I have stacks of server RAM in the UK
<f00b4r0>
[Pokey]: would you have DDR3 32G LRDIMMS? :)
<[Pokey]>
I do not xD
<f00b4r0>
heh :)
<[Pokey]>
I believe I have all 8GB DDR3 DIMMs
soxrok2212 has quit [Read error: Connection reset by peer]
<Borromin1>
aiyion: check the spec sheet for your flash chip, i had to add mine to flashrom
Gaspare has quit [Quit: Gaspare]
Borromini has quit [Ping timeout: 480 seconds]
<Borromin1>
aiyion: if you're lucky it might already be supported by their master code, worth checking. it's a quick and trivial compile.
soxrok2212 has joined #openwrt-devel
<aiyion>
Borromin1: will update flashrom in a moment.
<aiyion>
nope, still the same on v1.2-1015-g22e9313d
<Borromin1>
that's not master
<Borromin1>
master was at 7e8d17a8bd6e8239375666920b1824c4d24d4a01 when i pulled it in
<aiyion>
I'd like to open a wiki page for the WAVLINK AC1200 4G to note some components I just identified. Who do I need to ask for wiki access?
<aiyion>
nvmd; have enough access o.O
Gaspare has joined #openwrt-devel
<Borromin1>
aiyion: nevermind me, i thought g22e9313 was a git hash >_>
<Borromin1>
which it clearly is not.
<aiyion>
np :)
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
<hauke>
nbd: nice
<nbd>
to make it work, i simply dropped a lot of backport patches for older kernels that openwrt doesn't use
<nbd>
i still need to test it on 5.10, there's probably some remaining breakage
danitool has joined #openwrt-devel
<nbd>
also need to add the cve fixes that i pushed to master
<nbd>
do you agree with my choice of dropped legacy drivers?
<hauke>
ok fine with me
<hauke>
I was not aware that we still have an acx-mac80211 driver
<hauke>
will the CVEs get backported to older stable kernel versions
<nbd>
not sure. i prepared a patch series for 5.15 and i will send that out soon
<nbd>
older kernels might not need as many fixes
<nbd>
because most of the bugs are in MBSSID related code
<hauke>
ok
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
soxrok2212 has quit [Read error: Connection reset by peer]
soxrok2212 has joined #openwrt-devel
Borromin1 is now known as Borromini
Borromini has quit [Quit: Lost terminal]
Borromini has joined #openwrt-devel
cmonroe has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
<G10h4ck>
Hi!
<G10h4ck>
I am attempting some experiments with openvswitch in mesh networks, but the openvswitch package includes a ton of stuff that seems are not needed for my experiment
<G10h4ck>
so it doesn't fit even recompiling the image in most of my routers
<G10h4ck>
I need just need the capability to create a few ovs bridges and conficure them via openflow
<G10h4ck>
I suspect all the stuff like libopenvswitch ovsdb ovs daemon etc. are not needed in my usecase
<G10h4ck>
some suggestions on how to install the bare minimum?
cmonroe_ has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
xback has quit [Remote host closed the connection]
xback has joined #openwrt-devel
srslypascal is now known as Guest2984
srslypascal has joined #openwrt-devel
<dwfreed>
G10h4ck: ovsdb is what actually contains the switch configuration; it's needed
Guest2984 has quit [Ping timeout: 480 seconds]
Borromini has quit [Quit: Lost terminal]
cbeznea has quit [Quit: Leaving.]
borek has quit [Ping timeout: 480 seconds]
<G10h4ck>
dwfreed in my case the heig level configuration is managed by another custom compontent which is able to output openflow
csrf1 has joined #openwrt-devel
<G10h4ck>
in that case I guess only only ovs-vswitchd should be needed
<G10h4ck>
anyway I see libopenvswitch is 2.3M it seems huge for an embedded device, and used by even the most basic tool ovs-ctl -_- is this the toll to use openvswitch ?
csrf1 has quit []
csrf has joined #openwrt-devel
<dwfreed>
I mean, yeah
<dwfreed>
ovs is not intended for microscopic devices
<dwfreed>
equally I would not expect non-trivial configs to work well with the barebones DSA implementations of embedded devices
<G10h4ck>
dwfreed the idea is to use openvswitch mainly as datapath, another component which understand mesh networks would configure it
csrf has quit [Remote host closed the connection]
<G10h4ck>
sadly batman-adv seems not much alive anymore so we are looking for alternatives way
csrf has joined #openwrt-devel
<G10h4ck>
the idea we had was "let's implement layed 2 mesh logic in userspace and then configure openvswitch as kernel space datapath"
<G10h4ck>
and we are investigating the fesibility
<G10h4ck>
so basically we would have an ovs bridge with ethernet ports and wifi mesh ports, and then the table of the switch would be manipulated by a mesh aware compontent, to deal with loops, lossy links etc..
<nbd>
if you're doing your own datapath thing anyway, why not just implement the datapath in ebpf?
<G10h4ck>
I have thinked of that too nbd to use openvswitch was to avoid implementing the datapath, and just implement the mesh logic
<G10h4ck>
nbd did you recognized me? it's Gio from libre-mesh
<nbd>
yes
<nbd>
it's been a while
<G10h4ck>
how ar ere you?
<nbd>
doing fine, thanks. how about you?
<G10h4ck>
I am good too, in Argentina right now with the Altermundi people
<nbd>
cool
<G10h4ck>
so I thinked that openvswitch datapath should be fine for libre-mesh setup, but was just exploring that
<G10h4ck>
do you think reimplementing the datapath in ebpf would endup working better then attempting to reuse openvswitch stuff?
<nbd>
depends on the needs of the routing algorithm, i guess
<nbd>
with ebpf you can have more control over the datapath
<G10h4ck>
my idea was to keep the datapath kernel-space and move the wole mesh login like link discovery. quality measure, calculatinc best path etc. in user space
<nbd>
but it takes a while to learn how to fight the verifier :)
<nbd>
that makes sense
<nbd>
either way, if you choose ovs, i would recommend simply not using any of the existing ovs user space code
<nbd>
and just write your own thing that talks to the kernel ovs api
<nbd>
i don't think there's any easy way to cut down on the amount of bloat in the ovs user space
<G10h4ck>
it is a pity the ovs userspace is so bloated...
<G10h4ck>
thanks nbd i was feeling a bit lost exploring all that stuff and your opinion helps a lot
<nbd>
i think a ebpf data path in the kernel might actually end up being rather simple
<nbd>
the routing table is basically a map that uses the destination mac as primary key
<nbd>
and points to an entry in another map that keeps track of links
<nbd>
containing metadata such as the output device, packet counters, etc.
<nbd>
the program should recognize protocol data packets and simply bounce them to user space on a separate device
<nbd>
if you're using a custom eth type for encapsulation and don't use IP, the header overhead should be small as well
<nbd>
initially i would recommend simply bouncing all multicast traffic into user space and forwarding it from there
<nbd>
multicast/broadcast
<nbd>
makes it easier to deal with special cases for dhcp, arp, etc.
<G10h4ck>
thanks!
<nbd>
you're welcome. let me know how it goes and which approach you decide on
<nbd>
i'm definitely interested in this
<nbd>
i also have some experience writing ebpf programs, so i can offer some advice if you get stuck somewhere
<G10h4ck>
great!
<nbd>
for openwrt, i wrote 'bridger', which is a fast path for the linux bridge code and 'qosify' which does rule based dscp marking
<G10h4ck>
in current openwrt compiling ebpf stuff is already integrated in the toolchain?
<nbd>
there's some makefile magic to make it easy to build and package ebpf code
<G10h4ck>
didn't know of those new components at all!
<nbd>
inside qosify or unetd you can also find a header file bpf_skb_utils.h which makes it much easier to parse ip protocol stuff in skbs
<G10h4ck>
qosify seems something we my end up using in libre-mesh
<nbd>
maybe you might be interested in unetd as well
<nbd>
my goal with it was to create the easiest way to deploy and manage fully meshed decentralized wireguard networks
<G10h4ck>
very interesting
<nbd>
it also makes it easy to layer vxlan on top to bridge l2 segments over the network
<G10h4ck>
it seemsto have many interesting overlapping area which what i was investigating :D
<nbd>
unetd can also do direct connections over double-NAT, assuming at least one node is publicly reachable (or you're using DHT + a STUN server)
<G10h4ck>
and what happens if some connections are over lossy wifi links ? (smirk smirk)
<nbd>
it doesn't do any form of mesh routing
<nbd>
though i guess that might be interesting too
<nbd>
it has some limited configuration where you configure a node as a gateway for another node
<nbd>
it works on the basis of having a cryptographically signed network topology with wireguard keys, hostnames and ip/subnet addresses reachable over nodes with those keys
<nbd>
you can update the network topology and it'll spread across participating nodes
minimal has joined #openwrt-devel
<nbd>
and it'll exchange peer endpoint information to try to get every node to be able to talk to all other nodes directly
<nbd>
anyways... it was good talking to you, i need to get some sleep now
<nbd>
the kids wake me up early in the morning
<G10h4ck>
have a good sleep
<nbd>
thanks
<G10h4ck>
hugs to the family
<G10h4ck>
and thanks for sharing all the interesting ideas
<f00b4r0>
hmm odd. Why would lldpd log things like "MSAP has changed for port ifb4pppoe-fibre, sending a shutdown LLDPDU" when this port isn't under its purview
<f00b4r0>
(especially considering it's an ifb device)
<f00b4r0>
oh well, it's late, tomorrow's another day
Gaspare has quit [Quit: Gaspare]
Gaspare has joined #openwrt-devel
Gaspare has quit [Quit: Gaspare]
xback has quit [Remote host closed the connection]
xback has joined #openwrt-devel
mcbridematt has joined #openwrt-devel
G10h4ck has quit [Quit: Konversation terminated!]
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
f00b4r0 has quit [Read error: Connection reset by peer]
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
T-Bone has joined #openwrt-devel
aiyion has quit [Remote host closed the connection]