I have different hardware but had a similar issue. Using brainslayer r24160 on a Asus RT-AC68U the /tmp/ppp/options.pppoe file was not being written correctly. I could not find an option to configure the pppoe_wan_ifname nvram value from the web which results in the line nic-vlan2 being written into options.pppoe.
An incorrect nic-vlan value results in the PADIs going out on vlan2 rather than vlan10 so a pppoe connection will never get established.
Try:
Code:
nvram set pppoe_wan_ifname=vlan10
nvram commit
Awesome, that got it working thanks!
I had tried the VLAN settings as per the previous post, but I guess the build I was running had the same issue. I'm on BS 24461. Fingers crossed it's a stable release for everything else.
Thanks so much
when you reboot, does the vlan for the wan change back to vlan2 ?
when you reboot, does the vlan for the wan change back to vlan2 ?
I've noticed the same thing, settings saved revert after a reboot. It seems to only affect the tagging setting. I can't figure out how to make it save between router reboots, not sure why it is not saving?
when you reboot, does the vlan for the wan change back to vlan2 ?
I've noticed the same thing, settings saved revert after a reboot. It seems to only affect the tagging setting. I can't figure out how to make it save between router reboots, not sure why it is not saving?
It is a very old issue, multiple people have mentioned it multiple times on the forum here (including me). My e3000 is connected to a fiber-to-the-home provider as wel. It works great via pppoe, and some extra commands to work around this issue.
Simplest work-around is to save te commands as a startup script (administration -> commands -> paste there -> save startup), this will re-apply the changes on everey reboot. _________________ linksys E3000 (modded WRT610N-V2)@27453K3-Mega
Linksys WRT1900AC-v2 with latest LEDE code
For Broadcom, you do not use the "VLAN Tagging" section of the "Networking" tab. Because of the way Broadcom routers work, your WAN is already a VLAN, so you shouldn't use that interface.
Instead, you set the VLAN number of the WAN port under the "VLANs" tab and check the "Tagged" checkbox under the WAN port (don't check it anywhere else). Then, under the "Networking" tab, make sure that the "WAN Port Assignment" is correct.
If I understand correctly, this means that the maximum VLAN Id from your ISP is limited to 15 right? Or is there another way to handle for example VLAN ID 40 on your wan port?
code65536, you sir are a legend! A huge thank you!
I got fibre where I live today and done a google to use my existing Netgear WNDR4500, seeing a few trends about setting up the VLAN tagging, I was foreseeing a whole night full of stress, command line/ boot scripts.
But no, just followed your instructions for Broadcom routers and bingo, worked first go (reboot was needed after setting the settings).
I would also like to add something for other users, as this wasn't clear to me at first:
The "WAN Port Assignment" should be set to the new VLAN that was set on the VLANs tab. Also the VLANs page needs to be applied before it will show up in the "WAN Port Assignment" dropdown.
@geennaam, I'd assume in your case you'll have to use the command line to set a VLAN outside the default range.
code65536 wrote:
My ISP requires VLAN tagging on the WAN. I've gotten it to work with DD-WRT on both Broadcom- and Atheros-based routers.
Atheros:
Atheros-based routers do not have the "VLANs" tab. Instead, you go to the "Networking" tab and click Add under VLAN Tagging. Select your WAN interface, e.g., eth1, and select a VLAN ID, e.g., 2. This creates a new interface, named eth1.2 (if using the example above). You must then change the WAN Port Assignment from eth1 to eth1.2 (IIRC, you need to reboot first before that option appears).
Broadcom:
For Broadcom, you do not use the "VLAN Tagging" section of the "Networking" tab. Because of the way Broadcom routers work, your WAN is already a VLAN, so you shouldn't use that interface.
Instead, you set the VLAN number of the WAN port under the "VLANs" tab and check the "Tagged" checkbox under the WAN port (don't check it anywhere else). Then, under the "Networking" tab, make sure that the "WAN Port Assignment" is correct.
Hi I have finally got this working in NZ on spark fibre and it turns out to be pretty simple... the following is from another thread and was suggested by slice1900
Quote:
To those who are in New Zealand and want to use DD-WRT to connect to your Chorus ONT. My ISP Provider is Slingshot.
This is what I've done as per slice1900 suggestion. Follow on your own risk.
- Re-loaded firmware
- erase nvram
- factory reset (as can't ping anymore after erase)
- setup pppoe login and password
- activate vlan10 and tagged for W
- skip wan port assignment as it goes back to vlan2
- run the follwing commands "nvram set pppoe_wan_ifname=vlan10" "nvram commit"
Im posting this here in case anyone goes looking (like me) and is struggling!
Yes Broadcom is limited to 0-15. You can use the Robo switch Module to move the window.
A better solution is to get a R7800, that does not have this limitation.
BS patched switch-robo.c (for Broadcom chipset) to allow full 4096 VLAN IDs more than 6 months ago. No GUI support tho, as it’s still limited to 16. The only way to get more than 16 VIDs are via scripts.
Yes Broadcom is limited to 0-15. You can use the Robo switch Module to move the window.
A better solution is to get a R7800, that does not have this limitation.
BS patched switch-robo.c (for Broadcom chipset) to allow full 4096 VLAN IDs more than 6 months ago. No GUI support tho, as it’s still limited to 16. The only way to get more than 16 VIDs are via scripts.
Yes, any DD-WRT after 35165 will have this integrated.
Given that more and more ISPs will be using 802.1q tags in the future (for legitimate reasons, not to try to discourage third party routers) it would make a lot of sense for the DD-WRT GUI's WAN section to include a way to set vlan number for the WAN port to be tagged. That keeps all the WAN stuff in one place, making it simpler for people who only care about vlans to get the right tag set for their ISP.
I suppose if you wanted to fix the other GUI too, instead of fixed fields from 1-15 it could show 1-2 and then have an 'add' button where you can add another line with any vlan number you choose, i.e. like with the VAPs, bridges etc. Then you could have various non contiguous vlan numbers set in the GUI across the whole range, without making that page unwieldy by having 4000+ lines.
code65536, you sir are a legend! A huge thank you!