<djfe>
There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form.
<djfe>
the idea is to have this reviewed and merged before he adds a patch for the d-link covr-x1860. It makes the installation of these easier/possible and improves support for existing devices like the d-link dap-x1860 (firmware that can be installed from the web gui instead of the bootloader http Page)
<djfe>
Feedback and reviews are welcome, so he can move along :)
<PaulFertser>
Christophe[m]1: my question would be "how do you know mikrotik allocate that many MAC addresses?"
<PaulFertser>
allocated
<PaulFertser>
Does it match what vendor firmware uses?
goliath has quit [Quit: SIGSEGV]
<Christophe[m]1>
all(!) bpi-r3 seem to have 00:0c:43:26:60:00 set in eeprom
<PaulFertser>
Christophe[m]1: identical MACs on all boards, and they ship like that and their firmware uses that, for real, are you sure? Sinovoip can't be that insane can they?
<Christophe[m]1>
i guess it's random mac addresses
<PaulFertser>
Christophe[m]1: but then OpenWrt should ignore EEPROM and generate a random address for each phy on first boot.
<PaulFertser>
(random with locally-administered bit set)
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<Znevna>
wait, what does this have to do with MikroTik?
<Christophe[m]1>
Znevna: I'm assuming paul meant sinovoip
<PaulFertser>
Christophe[m]1: so what address are you reading from /sys/class/net/eth0/address ?
<Christophe[m]1>
From what I understand, eth0's mac address is random as well, but generated by uboot, thus persistent.
<Christophe[m]1>
PaulFertser: 9a:80:d8:xx:xx:8c and I've seen this one in an uboot env var.
<PaulFertser>
Christophe[m]1: so what you read from /sys/class/net/eth0/address is already a random locally-administered address, persistent because u-boot stores it in some env, right?
<PaulFertser>
Good, all makes sense then.
<Christophe[m]1>
PaulFertser: Yes. o0
<Christophe[m]1>
eth1 gets a completely different mac 8e:ab:80:xx:xx:d8, and we're skipping eth0 + 1.
<Christophe[m]1>
I checked for wireless mac addresses in the uboot env and could find any. maybe we should make phy1's mac eth1+1 xD
<KanjiMonster>
now it shows 12 commits, you need to go the other way ;p
<Slimey>
..
<SlimeyX>
i dont know what you mean
<Slimey>
i dont know how to use git, just adding device support lol
Borromini has joined #openwrt-devel
<KanjiMonster>
Slimey: in your git repo in your branch, do a "git rebase -i origin/main", then you will show you a list of commits you have that aren't in OpenWrt yet that you have
<Slimey>
ok
<KanjiMonster>
it should show you several commits, probably all from you with the same title
<Slimey>
yes
<KanjiMonster>
you want to set the first to "r" or "reword", as you want to edit the commit message to add line breaks, and the other ones to "f" or "fixup", so they all get merged into one commit
<KanjiMonster>
when you save and quit this text editor, it should bring you directly to editing the first commit's message
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Slimey>
i dont understand, i must have 100 lines that says pick
<KanjiMonster>
ah, I see what happened
<KanjiMonster>
clear the editor and remove all lines that are not comments, then quit
<KanjiMonster>
that should abort the rebase
<KanjiMonster>
so the first thing you want to do is to make sure your main branch is up to date
<KanjiMonster>
so switch to it and pull from openwrt (it should to a fast-forward)
<KanjiMonster>
that's where your commits come from, you merged openwrt changes into your feature branch, but the main branch of your fork did not have them
Borromini has quit [Quit: Lost terminal]
schwicht has joined #openwrt-devel
<Slimey>
done
robimarko has quit [Quit: Leaving]
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
schwicht has joined #openwrt-devel
<KanjiMonster>
Slimey: then switch back to your feature branch, and do a "git rebase -i main" (I omitted the origin/, since I don't know if you pushed your main update)
<Slimey>
ok now i get the commits i created
Tapper has quit [Ping timeout: 480 seconds]
<Slimey>
is it in order from oldest to newest?
<KanjiMonster>
yes
<Slimey>
so "r" pick 23bf42786b ath79: add support for Adtran Bluesocket BSAP-192x board is that correct?
<KanjiMonster>
not quite, you want to replace "pick" with "r" (or "reword")
<karlp>
r is just reword, you might want to "s"quish them all together...
<KanjiMonster>
you need to keep at least one commit
<KanjiMonster>
first one to reword, all the other ones to squash into the reworded one
<KanjiMonster>
or fix to not trigger a "please update the commit message" everytime