As said above, I want to use my TP-Link with Openwrt as DSL Modem. I read through some articles, but I just don't get it to work.
My test setup is a TP-Link (currently with th 19.07rc) and a 18.6-flashed FritzBox 7360, both, lantiq devices.
I currently have a working VDSL Telekom PPPOE connection on the 7360, but because I recently got 100Mbit instead of 25 I want to replace the 7360 with something more powerfull, because it can only manage about 60Mbit/s
The following things I tried :
I created a new VLAN on the 7360 switch with vid 2 and connected it to port 4 on the switch as untagged. On the TP-Link I although created a 2nd vlan with same settings. I also created a new interface on the TP-Link and bridged together the vlan 2 switch with the dsl0.7 modem named MODEM. then I changed the physical interface from my wan connection from dsl0.7 (VDSL needs VLAN id for PPOE) to eth0.2 switch. My thought was that the 7360 will send PPPOE packets untagged on port 4, the tplink gets them on its port4, forwards them to the dsl0 port and adds vlan tag 7, but it doesnt work. I also tried to set port 4 (in the switch configuration) on both devices to vlan 7 and tagged, but i still cant get a pppoe connection. When trying to establish a pppoe connection from the 7360 i can see on the interface tab on the tp-link, that the MODEM device receives packtets, but does not send anything.
I found WAN DSL bridge mode, but did not quite understand which settings are neccessary. Can anyone please point me in the right direction? Thanks!
Configuring a WAN bridge on the TD-W8980 between dsl0.7 and eth0.X is the right idea.
Please post the contents of /etc/config/network from both devices, and the output of running /etc/init.d/dsl_control status on the TD-W8980.
Screenshots from their LuCI switch configs could also be useful as an addition.
Hi! Yes, it's the TD-W8980, mixed it up somehow.
The FritzBox serves a WLAN which IP range is different from the LAN, and I just saw that I have bridged the WLAN to a LAN port, I'll try without that bridge again.
To test I just changed the pppoe interface from dsl0.7 to eth0.2.
Hostname : DSLModem
Model : TP-LINK TD-W8980
Architecture : xRX200 rev 1.2
Firmware Version : OpenWrt 19.07.0-rc1 r10649-c4fdb377a2 / LuCI openwrt-19.07 branch git-19.309.76540-c0e73d3
Kernel Version : 4.14.151
Try option vlan '2' (make the vlan numbers consecutive).
I believe this part of your config should work. Here is mine, just for reference:
config interface 'modem'
option type 'bridge'
list ifname 'dsl0.7'
list ifname 'eth0.7'
option macaddr 'e8:xx:xx:xx:xx:xx'
option proto 'none'
option auto '1'
Using eth0.2 is also fine, it is not necessary to have VLAN ID 7 on both sides of the bridge.
However, if you do decide to use VLAN ID 7, you must change the VLAN ID of the LAN2 interface to something different.
Some further ideas:
Set up PPPoE on the TD-W8980 temporarily to start with a simple, working configuration:
to '2' and everything works as expected.
Whats the difference between VID and VLAN? Is VId only the index for the VLAN and not the VLAN ID itself? Before tinkering around I had antoher VLAN added on the switch of the 8980 as VLAN2, bridged with the WLAN to still use it as an Wlan AP, and VLAN 3 for my PPPOE DSL experimenst. I removed both via Luci and added back only VLAN 2, but it seems the former VLAN 3 was kept somewhere. Now I can continue my plan to run OpenWRT as LXC container on my proxmox host and use the router as DSL MoDem and wireless access point. Thanks a lot!!!
I think it’s the other way around. The tag defaults to the VLAN option and can be explicitly set with the VID option. The VID option and a low-numbered VLAN option seems required for tags over the “table size” of the switch driver; for example VLAN 500 on a device with a 16 or 128 limit in the driver.