Banana Pi BPI-R3 OpenWRT image

Using any vlan used anywhere is wrong. You need to get your ISPs settings. Either extract them from working setup or ask your provider. Vlan-setup requires multiple pppoe-sessions with different credentials. I have this here in germany with local ISP (bambit one vlan for voip and one for internet)…and this ISP uses vlans 110 and 140

another point in my setup is that mac-adresses from both vlans need to be different on my side to get it working

Yes. Totally agree.

Apparently everything points to the conclusion that my ISP doesn’t use VLAN - (1) no mentions on ISP provided settings memo paper copy - only Username//Password, (2) VLAN off in my current router config that works fine.

Maybe also that Vlan is configured into ONT. In Europe almost every ISP that use PPPoE use a Vlan. Check also if you need to clone the MAC address of the original router or to comunicate the new MAC to the ISP.

1 Like

Thanks a lot! Worked like a charm.

How didn’t I try this earlier? This is so obvious. (Clone router’s MAC.)

While I know that my ISP doesn’t lock to a specific MAC address of my router - as I never communicated it to them and changed the router twice and I use internal MAC (didn’t ever override MAC address for this connection).

BUT it is quite reasonable to assume that ISP equipment may either validate the registered Vendor ID from MAC or at least check its Universally Administered Bit.

Apparently while understandable but it is still quite annoying shortcoming of OpenWRT’s default behavior - assigning Locally Administered random MAC address to WAN interface. (I wasted a week to figure this out - BIG disclamer in LuCi GUI would be VERY useful. Having LuCI GUI in a build by default would be helpful too BTW.)

OpenWrt does this because the R3 comes without any factory assigned MAC addresses. On off-the-shelf routers you usually have MAC addresses assigned by the vendor, and those are also used then by OpenWrt.

Yes. The reason is clear (that’s why I said understandable). It is clear that there is no other reasonable choice without factory MAC.

But the disclaimer would be definitely helpful - when wan device gets randomly generated MAC address with LAA bit set (as it should when the device doesn’t have its factory-assigned MAC address) - the GUI may highlight this with a hint that for some ISP this may not work - right there on Devices or Interfaces tab or in wan interface configuration dialog. In a very noticeable way - e.g. with red text.

Just a thought. The idea for GUI improvement that would greatly help some users to save time.

Somehow your reply notification got chewed by gmail :confused:

Is there a way to ensure that the network does not start until that hotplug event is processed?

Otherwise I’d try to hack it on the preinit phase.

It seems that the “samba4-server” package it is no more available on most recent Snaphots repository. Anyone with the same issue?

It is failing to build. The logs suggest it fails because GNUTLS is not found, which has also failed to build. See under fail logs, If you need it, raise a bug.

Finally installed the latest snapshot build of OpenWRT onto SD, left the factory OpenWRT on NAND for now. Things seem to work well with fewer option exposed in Network than the factory OpenWRT. I also noticed that luci-app-samba4 is unavailable for this architecture:

root@OpenWrt:~# opkg install luci-app-samba4
Unknown package 'luci-app-samba4'.
Collected errors:
* pkg_hash_check_unresolved: cannot find dependency samba4-server for luci-app-samba4
* pkg_hash_fetch_best_installation_candidate: Packages for luci-app-samba4 found, but incompatible with the architectures configured
* opkg_install_cmd: Cannot install package luci-app-samba4.

Any idea on how/when it will be available so I can use this router as a media server? Thanks!

Unfortunately the latest version Samba4 have a bug and fail for compile: https://downloads.openwrt.org/snapshots/faillogs/aarch64_cortex-a53/packages/samba4/.

Reading through the logs, and I’m not very experienced, it seems like the make rule is missing rather than a bug in the actual programming. I’m new to this whole community. Who looks after fixing these things? How is that done?

Discussion on openwrt :https://forum.openwrt.org/t/cant-install-samba4/160034/5. Maybe install and use : ksmbd or wait a few days for “repair” this issue.

OK, it looks like Samba4 is compiling now. So, I installed it through luci and I see some errors. Apparently the snapshot has moved on so I need to upgrade the system. So, I backup the settings and apply the update through luci. Now I get nothing from the router. So, I jump back into the serial connection and I see its’ looking for the backup file. How do I send the file over TFTP? Failing that, I also tried downloading the new SD Card image of the snapshot, and it runs, but I cannot copy it onto NAND now?

spi-nand: spi_nand spi_nand@1: Winbond SPI NAND was found.

spi-nand: spi_nand spi_nand@1: 128 MiB, block size: 128 KiB, page size: 2048, OOB size: 64

jedec_spi_nor spi_nor@0: unrecognized JEDEC id bytes: 00, ef, aa

‘spi-nand0’ is now active device

  • spi-nand0
    • device: spi_nand@1
    • parent: spi@1100a000
    • driver: spi_nand
    • type: NAND flash
    • block size: 0x20000 bytes
    • page size: 0x800 bytes
    • OOB size: 64 bytes
    • OOB available: 24 bytes
    • 0x000000000000-0x000008000000 : “spi-nand0”
    • 0x000000000000-0x000000080000 : “bl2”
    • 0x000000080000-0x000000380000 : “factory”
    • 0x000000380000-0x000000580000 : “fip”
    • 0x000000580000-0x000008000000 : “ubi”

Press ENTER to return to menu

this should work right?

https://www.asiarf.com/shop/wifi-wlan/wifi_mini_pcie/wifi6e-3000-802-11ax-3t3r-dbdc-mpcie/

Mates,

Do you install irqbalance?

So, the newest snapshot (25 May 23) ended up with the same problem on the SD card so I check the SD card but it tested fine. I reimaged the SD card and rather than running from the SD I directly copied to NAND and it runs fine there. Everything seems to work fine.

IRQbalance makes the device crash… sooo…

Update to 29 May 2023 sysupdate works well. Had to reinstall all of the opkg files, but the configuration files were still there.