Centurylink Fiber config Nighthawk RAX120

[nlq44261]

I'm having trouble with the configs for my RAX120 so that it will establish a link with Centurylink Fiber. I can't get it to work unless I connect it to the Centurylink provided router and turn off PPPoE login. I would prefer to have it set up so the RAX120 is connected directly to the ONT.

The RAX120 is currently set to Router mode.
What I've tried so far includes the following settings under Advanced>Setup>Internet Setup:

Internet connection requires log on: yes

Wan Preference: Internet port (1Gbps)

Internet Service Provider: PPPoE

PPPoE settings -

login: 'xxxxx@centurylink.net'

password: 'xxxxxxxxx'

Service name if required: this setting is left blank

Connection Mode: Always on

Idle Timeout: 5 min

Internet IP Address: Get dynamically from ISP

DNS Address: Get Automatically from ISP

Router MAC Address: Use Default Address

VLAN ID Configuration (see below)

In ADVANCED>Advanced Setup>VLAN / Bridge Settings I have the following:

Enable VLAN / Bridge Group: enabled

By VLAN tag group:

Name: Internet

VLAN ID: 201

Priority: 1

Wired Ports: All

Wireless: All

Additionally I've attempted IPv6 settings configured as disabled and 6to4 Tunnel mode but the router just wont pull any Public IP address or DNS information with the above settings when plugged into either the Centurylink router or directly into the ONT

Am I missing some sort of configuration somewhere? Please help

[antinode]

> In ADVANCED>Advanced Setup>VLAN / Bridge Settings [...]

   Someplace in some CenturyLink instructions, a VLANID of 201 was
mentioned?

   I know nothing, but I suspect that you're fiddling with the wrong
VLAN stuff.  I'd clear that stuff out, and investigate:

ADVANCED > Internet Setup : Use VLANID (and the box for the ID number).

[nlq44261]

There is no VLANID entry in ‘ADVANCED > Internet Setup’ on the nighthawk rax120 web configuration page. There is only a link at the end of the ‘Internet Setup’ page to send you to the ‘ADVANCED > Advanced Setup > VLAN / Bridge Settings’ page to configure the VLANID.

All the VLAN config mentions I’ve seen tell you to make the change on that page using the ‘By VLAN tag Group’ toggle

[nlq44261]

Here’s a photo of my VLAN settings as well

[nlq44261]

I forgot to post the last bit of settings that could affect connectivity. Here they are:

ADVANCED > Setup > WAN Setup

Disable Port Scan and DoS Protection: feature disabled
Default DMZ Server: disabled
Respond to Ping on Internet Port : feature disabled
Disable IGMP Proxying: feature enabled
MTU Size(in bytes): 1492
NAT Filtering: Secured
Disable SIP ALG: feature disabled

I’ve tried NAT filtering in both ‘Secured’ and ‘Open’ settings but I haven’t gotten to the point where this router is pulling a public IP address from centurylink

[antinode]

> There is no VLANID entry in `ADVANCED > Internet Setup' on the
> nighthawk rax120 web configuration page. [...]

   Ok.  Your junk is more modern than my junk.  Sorry about the
distraction.  (At least _I_'m learning something.)

   In my recent wanderings, I stumbled across instructions for the
RAX120 on iiNet (only a world away):

      https://help.iinet.net.au/setting-common-non-iinet-supplied-modems-nbn-fttp
      https://help.iinet.net.au/how-set-netgear-nighthawk-rax120-nbn-fttp-wireless

   Except for the suggested Priority value, it seems to agree with what
you're doing.

   Otherwise, aside from faulty PPP credentials, I'm about out of ideas.

   But note that Netgear routers have a history of mishandling special
characters in PPPoE credentials, so, if yours contain non-alphanumeric
characters, then you might need to take some special steps.  See, for
example:

      https://community.netgear.com/t5/x/x/m-p/1354547

   CenturyLink can't see what's going wrong?

[nlq44261]

Thanks for the new info I appreciate you digging that up. I’ll check those out later today and see if those help. There are a lot of special characters in my ppp password so that might be the issue.

Unfortunately the internet is not In my name so I have to coordinate with the roommate on the tech support.

[antinode]

> [...] mishandling special characters in PPPoE credentials, [...]

   That should have read "PPP credentials".  In my case, it was a PPPoA
password.

> [...] There are a lot of special characters in my ppp password [...]

   I never did any serious research, so I know approximately nothing,
but I got the impression that "special" in this case meant "special to a
UNIX shell", like the "<" in the cited example.  "@" was reported to be
harmless (which would be consistent with that criterion).

   If in doubt, I'd expect an unneeded "\" to be harmless, unless the
string gets too long.

   Anything you discover along those lines would be interesting.
There's no evidence of Netgear being interested in fixing the problem,
so better defining its boundaries could be helpful to someone.  Worst
case should be only more wasted time.

[FarmerBob1]

Priority should be "0". That means over rides everything. Also I have noticed that this area for some time has not been too stable. Make sure that it looks like this everytime you go to it:

The "Enable" checkmark keeps unchecking itself.

Hope this helps?!

 . . . fb

[FarmerBob1]

And even with CL Routers, although their software is genius, IPv6 when "Dual Stacked" or "Tunneled" is flaky at best. AND NG has changed the UI on this lately to negate when you get an IPV6A on the WAN. But it's still there for the LAN and this too is flakey. Alot of my gear runs so much better just with IPv6 on for interal networking as it has decades. This is the set up (use the numbers listed and the Connection Type is "6rdTunnel"). NG hasn't learned how to use HTML yet and especially for inverted UIs:

The "Not Available" that is under the LAN set up use to also be up in the WAN section. That was such a help to find out if you were getting an address from the WAN and what state the LAN was in helped in trouble shooting. But back then, it was set it and leave it, because there were no issues. it started when the "Not Available" was removed from the WAN area is when IPv6 started to be flakey. I wish they'd fix this OR put it back to the way it was. I see no reason for it to have been altered.