Problem with VLAN tagging on DIR-860L (MT7530)

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi there,

first of all i want to say thanks to the LEDE and open source project developers in general. Here's my question.

I bought the router named in the title because it seems to be the best shot at price vs. performance while having AC Wifi.

In germany the biggest VDSL provider uses PPPoE with Username/Pass, but the packets sent to the modem must be Tagged with VLAN Tag 7. I have been successfully doing this with LEDE and OpenWrt on other devices: configuring switch to make eth0.7 and tagging CPU and WAN, then mapping the PPPoE Interface to eth0.7 and providing credentials.

Here's the problem: Unfortunately this does not work for me on this router. Reading the Syslog, i find the message "daemon.warn pppd[5120]: Timeout waiting for PADO packets". In the past, this was the error message i got before configuring WAN/WAN6 with VLAN Tag 7, tagging fixed it and i got internet connection.

It seems that the VLAN tags or whole packets are being dropped, because i don't get connection when configuring as described. I have read a thread i don't really understand besides it adressing a driver problem with MT7530 switch. I assume it might adresses my problem. I would be grateful if somebody could help me understanding it:
https://dev.openwrt.org/browser/trunk/target/linux/ramips/files/drivers/net/ethernet/ralink/mt7530.c?rev=47114

I have been successfully compiling my openwrt images on Ubuntu in the past, but don't know if/how i need to change some parts of the source to make it work.

I would be grateful for any help. Thanks in advance!

1 Like
2

Can you provide your /etc/board.json file here?

3

Here you go. Reading that file i already see that there might be the problem, as wan is not associated to eth0.7 with PPPoE Protocol. But i don't know exactly which parameters must be changed to get it working. Thanks for your input so far!

{
"model": {
"id": "dir-860l-b1",
"name": "D-Link DIR-860L B1"
},
"led": {
"wan": {
"name": "wan",
"type": "netdev",
"sysfs": "dir-860l-b1:green:net",
"device": "eth0.2",
"mode": "link tx rx"
}
},
"switch": {
"switch0": {
"enable": true,
"reset": true,
"ports": [
{
"num": 1,
"role": "lan"
},
{
"num": 2,
"role": "lan"
},
{
"num": 3,
"role": "lan"
},
{
"num": 4,
"role": "lan"
},
{
"num": 0,
"role": "wan"
},
{
"num": 6,
"device": "eth0",
"need_tag": false,
"want_untag": false
}
],
"roles": [
{
"role": "lan",
"ports": "1 2 3 4 6t",
"device": "eth0.1"
},
{
"role": "wan",
"ports": "0 6t",
"device": "eth0.2"
}
]
}
},
"network": {
"lan": {
"ifname": "eth0.1",
"protocol": "static",
"macaddr": "90:8d:78:XX:XX:XX"
},
"wan": {
"ifname": "eth0.2",
"protocol": "dhcp",
"macaddr": "90:8d:78:XX:XX:XX"
}
}
}

1 Like
4

I have the same problem with my DIR-860L. I used to use a earlier build of lede that was still under development and that seemed to have support for VLAN's. I tried the updated rc version of the build and it seems to loose support again.

5

Has VLAN support been fixed in the final 17.01 release? I am looking to buy a DIR-860l myself.

6

Which older build has VLAN support?

7

Bump. (10 char)

8

Bump. (10 char)

9

Just to test, try to set the Switch configuration to this:

Important: The untagged parts should stay, where they are at the moment in your configuration. The only changes are VLAN 7 tagged at CPU and WAN.

I had problems with gaps at the VLANs e.g. at a 1, 2, 4 configuration only 1 and 2 worked. At 1, 2, 3, 4 configuration every VLAN worked fine.

I used LEDE 17.01 Build

Just an uneducated guess: They used the index of the for loop instead of the array element they wanted to address to configure the VLAN Switch.

1 Like
10

Thank you so much, Aufhaxer! This did it for me! All VLAN IDs had to be tagged on CPU port and i have working PPPoE Connection in VLAN7 on WAN Port!

11

Glad to hear. :slight_smile:

With the current snapshot and the master i built myself it seems to be working as expected and without the need of the useless VLANs.

I would like you to test the current snapshot and delete the unused VLANs, to confirm my results:
https://downloads.lede-project.org/snapshots/targets/ramips/mt7621/

You have to install luci manually through ssh with "opkg update && opkg install luci".

12

Hi aufhaxer,

I'm sorry to tell you that with the current snapshot, deleting all VLANs from 3 to 6 still brings me back to the old problem:

Sat Mar 18 20:51:30 2017 daemon.warn pppd[1510]: Timeout waiting for PADO packets
Sat Mar 18 20:51:30 2017 daemon.err pppd[1510]: Unable to complete PPPoE Discovery
Sat Mar 18 20:51:30 2017 daemon.info pppd[1510]: Exit.

I'll stick with your workaround for now. Let me know if you need more logs or if you want me to test some more for you, i'll be happy to do so. Thanks so far anyway!

13

Hi molocho,

thank you for your results. This input is very helpful.

I have to withdraw my results from last post. The issue like in your case still seems to be broken in the latest snapshot of LEDE. But still glad to hear, that the workaround does his job. :slight_smile:

We are currently discussing this issue in two separate threads. Since the problem of yours has been fixed for the moment, I would like you to participate, if possible, in the other thread to limit it to only one. Mt7621 DIR-860L does not support VLAN's

14

Having to deal with a couple of different ISPs, working with different protocols and different VLAN IDs, i just found out, that the current stable LEDE Release 17.01.4 has some fixes for a part of the issue. Using VLAN 7 (Germany's Telekom ISP via VDSL), there is no problem having VLAN IDs 1, 2, 7 present, using PPPoE.
Dealing with a PPPoE FTTB Connection from a different ISP (Germany M-Net) which requires to use VLAN 40, it is only possible to get a connection when again inserting VLANs 3-39 in between.
The issue seems to be persistent for higher numbered tags.

Having different LEDE routers at hand, a direct comparison with the same build for different platforms does not show this issue on other devices which use different Hardware.

15

Could we try and upvote the issue on the bug tracker? Hopefully a fix will be found sooner then :slight_smile:

https://bugs.lede-project.org/index.php?do=details&task_id=1147

16

Managed to pinpoint the issue. Not sure yet where a fix should be applied. Please view the bug tracker for more details.

17

I noticed that we have a similar discussion going on in Mt7621 DIR-860L does not support VLAN's

Can we safely close the linked topic, in order to follow up with this issue in only one thread?

18

I am fine with that. Would it maybe be possible to merge the topics instead though?

19

I could move the other thread over to this one, but this would result in all messages being appended to this thread, breaking the chronological order. I don't think that this would be a good idea.

I can close the other thread and attach a note that discussion of this topic will go on in this thread here.

20

Sounds good to me, thank you. :slight_smile: