I am new to OpenWRT and have done some reading regarding to VLAN trunking on WAN setup. However, the provided solution doesn't work. Therefore, asking support from this great community
I would like to avoid double NAT, by changing my ISP's ONT router into bridge mode. The setup is PPPOE, using VLAN trunking. I have the required VLAN_ID, PPPOE username and password.
How to replicate this in OpenWRT (after changing ISP's router to bridge mode)?
I am on OpenWRT 23.05 on LinkSys EA7500 v2 (default firmware and setting, except wireless and have add HTTPS DNS Proxy using LuCI at default setting as well).
Have done the following:
Adding new VLAN Device: Network - Interfaces - Device
Device type: VLAN 802.1q
Base device: WAN (wan and wan6)
VLAN_ID: 219 (as per my ISP)
Other setting is default.
Adding new WAN Interface: Network - Interfaces - Interfaces
Protocol: PPPOE
Device: the above VLAN on Point (1)
Username and Password: according to my IP.
Thank you...
[edited: adding reference pic to ISP's router, which needs to be replicated in OpenWRT, after the router changed to bridged mode]
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
I assume, I can change all those changes using LuCI, right? Will check it first, how to do it...
If I remove VLAN setting (where I set VLAN_ID 219), then how should I set-up VLAN? This is coming from original ISP's router setting. I have tried to disable VLAN on it, but then no internet connection... Therefore, I assume, VLAN has to be set (maybe I'm wrong).
Nitpick: a "(vlan) trunk" caries multiple vlan on a link. If you just have a vlan tagged ethernet then it is just a vlan nothing more.
And yes, just configure your vlan stanza and set vlan id and mtu on your wan interface...
I'm suggesting removing the 802.1q stanza I highlighted. The underlying .1q device will be automatically created when you use standard dotted notation on the wan. That is, when you specifcy wan.219 as the device, the 802.1q tagging will automatically work.
Sorry for late response.. I lost my internet when making the changes. Was worse than the last time (prior to posting this thread), as I need to call my ISP to reset my router.
Anyway..
Here is the error from "wan" interface (previously "BIZWAN"), with wan.219 (VLAN active):
Protocol: PPPoE
MAC: redacted
RX: 313.73 GB (230631143 Pkts.)
TX: 31.45 GB (131018537 Pkts.)
Error: Unknown error (USER_REQUEST)
Error from "wan" interface, if VLAN is not used:
Protocol: PPPoE
MAC: redacted
RX: 0 B (0 Pkts.)
TX: 778 B (8 Pkts.)
Error: Connection attempt failed
That's a lot of data for a failure... are you sure it's not connecting properly?
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
Still no IP on "wan", instead the same error message.. Initially, "connection attempt failed". And then change to "unknown error (USER_REQUEST)" Protocol: PPPoE MAC:redacted RX: 0 B (0 Pkts.) TX: 5.90 KB (168 Pkts.) Error: Connection attempt failed
(after a while change to: unknown error (USER_REQUEST)
It's possible that the isp is locked to the mac address of the original router. If so usually you wait for a timeout period to expire with the isp before it accepts the new mac address or you find out what the mac address of the old one was and copy it across to wan.219 to use
oh, another thing you might want to try as a last resort is using one of the LAN ports as your wan port try taking lan4 out of br-lan and making a lan4.219 for instance, use lan4 as your wan port and see if that works
Though I made this post under the assumtpion you were using a ipq40xx based device but I looked it up and yours is a mt7621 so it probably won't make a difference
I'm using this same router and my ISP also requires the use of a VLAN ID. But sharing my config won't help you with that as I have a managed switch taking care of the VLAN part of things.
However, I have always consistently had a problem with PPPoE starting on the wan port because the port somehow doesn't initialize properly. For this reason, I start an unmanaged interface on the same port. This seems to have the effect of making sure the port is initialized properly and PPPoE works: