I recently purchased a Netgear R7000 and flashed DD-WRT to it, but I am unable to get it to connect to my ISP.
My ISP is Telecom New Zealand and they allow connection of third party routers directly to their Fibre service. They supply the following required settings:
Operating Mode : MDI/MDIX
PPP Protocol : PPPoE
PPP Username: user@xtrabb.co.nz
PPP Password: ********
PPP Auth Type : blank (if you cannot leave blank, select PAP)
Encapsulation : 802.1Q
PCP Marking : 0
VID (or VLAN) : 10
MTU : 1,500 or AUTO
So I have configured PPPoE, created the VLAN 10, Set the 802.1Q tagging but it still will not connect.
Attached please find some screenshots of my setup.
I have noticed that when I change the VLAN of the WAN port from 2(Default) to 10 and assign the Bridge to LAN, it reverts back to showing the LAN bridge on VLAN 2 instead of VLAN 10.
Any help would be much appreciated. Thanks in advance.
Rudi Prinsloo
VLANS.jpg
Description:
VLAN settings. Assigned to bridge reverts back to VLAN 2 for some reason.
Can anybody tell me how to change it so that my WAN port is on VLAN10 with 802.1q tagging as required by my ISP? The GUI wont accept the changes for some reason so perhaps the command line will be more effective?
I have tried issuing the following commands to try and set the wan port to VLAN 10 with 802.1q tagging but when I commit and reboot the router resets to factory default:
nvram unset vlan2ports
nvram set vlan10ports="0 5u"
nvram set vlan10hwname="et0"
nvram set port0vlans="10 16"
nvram unset vlan2hwname
I am running out of ideas. Any help would be much appreciated. I could also offer a paypal donation to the kind soul who could help me get this working.
I've set the WAN port to PPPoE and entered my username and password.
The most important thing to do is to set up VLAN tagging to ID 100, but it seems to reset every time I reboot the router. _________________ Netgear R7000
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. _________________ Buffalo WZR-1750DHP: 34311
TRENDnet TEW-673GRU: 34311
TRENDnet TEW-811DRU: 33986
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.
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.