as Openwrt doesn’t work at all with SFP ONT, which is not the case with the debian from the wiki
i have two solutions, put the bpi-r3 in a drawer and wait for the problem to be solved one day. Or install Debian and set it up to work as a wifi router.
i know how to configure openwrt, but I don’t know how to do anything with debian.
Can someone please share his configuration ? what files to configure to have a basic router + wifi + HW offloading ?
newer debian versions use systemd and so you should use the systemd way to configure things.
a router basicly needs at least the following things:
network-config of course
additional hardening (sysctl, auditd, ssh, filesystem,webserver, other services)
as a base you can create an up-to-date debian for r3 using my Images repo
( need some users for testing )
these use latest uboot/ATF/mainline-linux from my repos for creating the image. so it depends on what is the problem in openwrt…so for unexperienced user the better way should be helping to get the sfp working in openwrt where you can configure all on the luci web interface…in debian all is on cli and manually configuration as it is designed as server-OS not router-OS
SFP-Support is a kernel-thing, not openwrt or debian-specific. and kernel things should be fixed in mainline and if not possible then in specific repos (like openwrt or my linux-repo).
i already put some systemd-files in the generated debian images so there is already a basic network-setup, but firewall (you find basic examples in my wiki too) etc is not yet applied as this is user-specific and i wanted to leave the system as virgin as possible.
so the problem is that the gpios of the sfp are reused with the uart to getting in the embedded system of the stick. vendors debian only ignores the pins so the tx-fault pin cannot trigger the sfp-framework
neither for mainline nor for openwrt disabling tx-fault pin is a correct solution…so we need a better way before apply to any repo.
i tried some years ago adding an own patch to openwrt and failed
i know that, but do anybody else know it too? imho it is necessary to separate these things
afaik there is no quirk yet…but imho this could be a good solution
@frank-w can’t you just compile (or use the latest firmware i compiled) and burn it on a sdcard and test it on your BPI-R3 ? You’ll find immediatly what’s wrong and what’s need to be fixed…
this will go way faster as you know what to do, and you understand what you do…That’s actualy 2 weeks since i first posted here about this ONT problem and we are still at the same point, maybe with more problems added…
Actually all topics i’m in are about “Do this”, “do that”, “post this”, “post that”.
Now the situation is that we can’t create a working image from @dangowrt git, and we are still asked to do things. 2 weeks that we are turning around. all logs are already posted.
if you want more logs, please fix the git firmware which is actualy totaly broken even for RJ45 ports.
I’m not experienced in openwrt and do not have such sfp. So testing will be hard…and i have many sdcards currently in use (2+ for each board i have here for testing).
You ran into revovery maybe write to sdcard was not finished (or pervious boot filling pstore with crash dump). Make sure all data is written to card not rely on gui saying copy is finished. I don’t think kernel is broken in this way after last commits.
yes this is development…and r3 is a development board there are only a few people here for getting things to work and doing support as far as possible. but we need some information on what is the exact problem…
you boot above shows only the tftp and nand detection…i guess abit more above there is a hint on which device is booted and maybe why tftp is done.
make sure the switches are really in the right position to boot from card. if uboot loads from card then kernel should too. but we experienced some read errors in uboot waiting for some guidance from vendor.