12-08-2019 02:03 AM
HI, I have just purchased the above router and have spent the weekend configuring it both manually and with the help of the on-board wizard.
I have updated the Bios to the latest version 1.0.1.19
My ISP is Spark New Zealand, and their instructions are as follows;
Set up VDSL on a non-Spark modem
Any VDSL modems need to align with Telepermit PTC274 certification. You'll need your modem Is user
guide, and then adjust the modem Is settings to match the following:
Operating mode: VDSL2
• PPP protocol: PPPoE
PPP username: user@spark.co.nz
• PPP password: password
• PPP auth type: PAP
• Encapsulation: 802.10
• PCP marking: O
• VID: 10
• MTU: 1500 or Auto
Note: You may not need to fill out all these fields. You don't need a specific PPP username and password,
but you won't be able to connect if either field is blank.
In all cases, the modem finds the DSL line but the internet light goes red.
I have attached the latest log file from the moment I connected the DSL line.
In addition I have also used the information from my spark modem
v INTERNET TROGS VDSL VID 10
Access type VDSL
IPv4 status: Connected
IPv4 address: 125_236.218.251
IPv4 primary DNS server: 122_56.237.1
IPv4 secondary DNS server: 210_55.111.1
PPP0E AC-Name: PAK-BNG01
LANI: Connected Full 100Möps
LAN2: Disconnected
LAN3: Disconnected
LAN4: Disconnected
MAC address: 64:6D:6C:C0:D8:E2
IP address: 192168.7.254
If have also tried MAC address cloning, factory resetting and extra cups of tea.
Any suggestions as to what to try next?
Solved! Go to Solution.
12-10-2019 11:20 PM
I have solved the problem.
I found a similar issue on https://community.cisco.com/t5/routing/cisco-rv134w-connection-problem-to-vdsl2-centurylink/td-p/3953559
Using this as a guide it became apparent that the default PTM Entry does not work here, nor will it allow the editing of the VLAN field.
The solution provided by Georg Pauwen to qpgmr400@cox.net was to create a new xDSL entry in the routing table, which then allows the editing of the VLAN field.
Make this new profile the default routing profile and off we go.
Problem solved.
12-10-2019 11:20 PM
I have solved the problem.
I found a similar issue on https://community.cisco.com/t5/routing/cisco-rv134w-connection-problem-to-vdsl2-centurylink/td-p/3953559
Using this as a guide it became apparent that the default PTM Entry does not work here, nor will it allow the editing of the VLAN field.
The solution provided by Georg Pauwen to qpgmr400@cox.net was to create a new xDSL entry in the routing table, which then allows the editing of the VLAN field.
Make this new profile the default routing profile and off we go.
Problem solved.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide