R4 br-lan can't pppoe?

Banana Pi BPI-R4/BPI-R3 Mini/BPI-R3/BPI-R64/BPI-R2
1

When I dialed using br-wan, reported an error. (use Official firmware) 当使用官方固件并用br-wan进行拨号时.发生错误,无法正常拨号上网.请问如何修改? 单独使用设备LAN0拨号再次测试也不行。用Br-wan和单独LAN0拨号都不行.但是使用SFP0就是那个WAN口可以正常拨号上网

Sat Apr 27 02:54:30 2024 daemon.warn pppd[8084]: LCP: timeout sending Config-Requests
Sat Apr 27 02:54:30 2024 daemon.notice pppd[8084]: Connection terminated.
Sat Apr 27 02:54:30 2024 daemon.info : 07[KNL] interface pppoe-wan deleted
Sat Apr 27 02:54:30 2024 daemon.info pppd[8084]: Sent PADT
Sat Apr 27 02:54:30 2024 daemon.notice pppd[8084]: Modem hangup
Sat Apr 27 02:54:30 2024 daemon.info pppd[8084]: Exit.
Sat Apr 27 02:54:30 2024 daemon.notice netifd: Interface 'wan' is now down
Sat Apr 27 02:54:30 2024 daemon.notice netifd: Interface 'wan' is setting up now
Sat Apr 27 02:54:30 2024 daemon.info pppd[10203]: Plugin rp-pppoe.so loaded.
Sat Apr 27 02:54:30 2024 daemon.info pppd[10203]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Sat Apr 27 02:54:30 2024 daemon.notice pppd[10203]: pppd 2.4.8 started by root, uid 0
Sat Apr 27 02:54:30 2024 daemon.info pppd[10203]: PPP session is 1585
Sat Apr 27 02:54:30 2024 daemon.warn pppd[10203]: Connected to 4c:96:14:6c:eb:c5 via interface br-wan
Sat Apr 27 02:54:30 2024 kern.info kernel: [  118.270798] pppoe-wan: renamed from ppp0
Sat Apr 27 02:54:30 2024 daemon.info pppd[10203]: Renamed interface ppp0 to pppoe-wan
Sat Apr 27 02:54:30 2024 daemon.info pppd[10203]: Using interface pppoe-wan
Sat Apr 27 02:54:30 2024 daemon.notice pppd[10203]: Connect: pppoe-wan <--> br-wan

two:
Sat Apr 27 02:56:57 2024 daemon.info pppd[20313]: Plugin rp-pppoe.so loaded.
Sat Apr 27 02:56:57 2024 daemon.info pppd[20313]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Sat Apr 27 02:56:57 2024 daemon.notice pppd[20313]: pppd 2.4.8 started by root, uid 0
Sat Apr 27 02:57:12 2024 daemon.warn pppd[20313]: Timeout waiting for PADO packets
Sat Apr 27 02:57:12 2024 daemon.err pppd[20313]: Unable to complete PPPoE Discovery
Sat Apr 27 02:57:12 2024 daemon.info pppd[20313]: Exit.
Sat Apr 27 02:57:12 2024 daemon.notice netifd: Interface 'wan' is now down
Sat Apr 27 02:57:12 2024 daemon.notice netifd: Interface 'wan' is setting up now
Sat Apr 27 02:57:13 2024 daemon.info pppd[21001]: Plugin rp-pppoe.so loaded.
Sat Apr 27 02:57:13 2024 daemon.info pppd[21001]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Sat Apr 27 02:57:13 2024 daemon.notice pppd[21001]: pppd 2.4.8 started by root, uid 0

Error: Unknown error (NEGOTIATION_FAILED)

2

Maybe you need to add vlan and connect over this? Here in germany this is a common configuration.

An you should not connect via lan-bridge…

3

不是br-lan.是单独用lan0设备拨号. 不需要VLAN.

image
image1670×1328 153 KB
image
image1474×944 44 KB
image
image1816×1102 151 KB

这是原始路由上的配置不用配VLAN

image
image830×1042 69.1 KB

4

Please english text,also on screenshots…and they show your settings,but not what your ISP expects…some only allow specific mac-adresses

5

use SFP0 is pppoe OK use lan0 pppoe error.

you try it lan0 to pppoe test it

7

There are some problems with my description at the beginning. I can confirm that there is no problem with my pppoe settings because the sfp port of eth2 can dial normally. With the same setting, lan0 cannot dial normally.

8

I formatted the log as code for better readability,but the only problem i see is this:

 Timeout waiting for PADO packets

Which means you send PADI to your access node and got no response. On r4 the 2 sfp are mostly identical (both on mac directly),so i would guess there is a configuration issue on the bridge,but do not know any except vlan-awareness which would affect pppoe.

Which kernel/system do you use? Maybe disable offloading (flow offload,vlan offload).

Why dialin with lan0? Imho this is a very strange setup,as pppoe works on layer2…client sends PADI via broadcast (your full lan if bridged) and then get direct response (PADO with both macs set right) from access-control-node (router). Pppoe handshake then has 2 additional steps to handle ethernet parameters before next protocol (lcp) kicks in,but imho it is unrelated here.

9

because i have two broadband access to the internet one use sfp0 other use lan0

10

Have you tried removing lan0 from lanbr0 and use it with pppoe?

11

lan0 not in br-lan and not in br0 only lan0

see my pic

br-lan ： eth1、lan1、lan2、lan3

git from this

Linux OpenWrt 5.4.246 git

12

Hard to follow if someone (me) cannot read chinese chars and not know the frontend :stuck_out_tongue:

You can try use tcpdump on the interface and look if there is a PADI going out…maybe contact your isp if he sees this packet from your mac…maybe there is a mac filter…lan0 receives mac adress from eth0…maybe a problem is here that the other ports have same mac

13

:grinning: Now you can learn Chinese. thank you i‘will try it

14

Try upstream openwrt snapshot

15

上游的lan0可以拨号

openwrt23.snapshot lan0 pppoe is ok

but mtksdk openwrt21.02 can’t

So I post this problem on here.

16

then it is up to sinovoip to fix this issue

17

I had the same problem as him. lan 0 is isolated from brlan and subsequently set to wan intertace for pppoe dialing. Dial-up works normally on sfp0, but cannot be achieved on lan0 in this situation.

I captured packets on lan0 through tcpdump and found that there were PADI, PADO, and PADR packets, but I could not obtain the next stage of PADS packets. Maybe this is a driver problem with the switch that comes with MT7988 in the MTK SDK.

18

if mainline openwrt works without issues, i would not put work into it

Seems it is reported here too: mediatek: switch to Linux 6.1 and add BananaPi BPi-R4 by dangowrt · Pull Request #14140 · openwrt/openwrt · GitHub

you can try to revert/delete the ppe patch and see if it fixes your issue and report back