Hi guys, unfortunately I am experiencing connetion problems with my brand new OF line. My ISP told me to set VLAN ID to 835 to properly connect but, after reading many threads on the forum, I still cannot connect. I have this settings right now, as suggested here
Should I manually check/correct the value in /etc/config/network ? Are there any guide to do so? Don't know how to connect and edit thi setting. Thank you so much!
Please run the following commands (copy-paste the whole block) and paste the output here, using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have
ubus call system board; \
uci export network; uci export dhcp; uci export firewall; \
head -n -0 /etc/firewall.user
Do you have version 19.07 or 21.02?
What router do you have?
The connection VLAN is only half the story! To be exact the L2 part. The ISP also need to specify his L3 settings which probably most often mean that you should have DHCP client as protocol on wan interface with fiber connection. But that question is for your ISP to answer.
I think the switch in that model is an Atheros gigabit chip which supports a full table of all 4096 possible VLANs. So you don't need a separate option vid, you can just use option vlan 835. (though if you are mixing LuCI and CLI, LuCI may prefer it the separate way). Check that with swconfig dev switch0 help the first line of the report is the number of VLANs capable.
Since VLAN 835 (instead of 2) is now being tagged on both the CPU and the external port, there is no longer an eth0.2 and the option device which sets the MAC address should be changed to eth0.835.
Read the log to see why WAN is not connecting. If you have no connectivity with the ONT you will see "Timeout waiting for PADO packets." In that case you could connect a PC with Wireshark directly to the ONT to see if it is emitting PADO packets tagged 835 as expected.
The configuration in the first post was just the right one, it works actually. There were some misconfigurations on SVLAN with the OF infrastructure owner. Thank you all.