I saw this maybe a year ago with existing customers who had updated their router FW. I haven’t seen it recently. Maybe Netgear fixed it. You might try putting latest FW on the router, but of course that’s difficult if the customer can’t connect to the Internet.
I think about 2% of customers ever update their router FW. The few that do, apparently it’s a crapshoot whether the update fixes more bugs than it creates. When router vendors introduce a new router, it seems they put any piece of garbage FW on the first shipments from China assuming first thing the customers will do is update the FW. To their credit, they are starting to prompt you to update FW as part of router configuration, turn on auto update by default, and make it so you don’t have to download the FW image to a laptop first but can just click on a button in the router GUI. From: AF <af-boun...@af.afmug.com> On Behalf Of Jesse DuPont Sent: Wednesday, March 13, 2019 2:32 PM To: AnimalFarm Microwave Users Group <af@af.afmug.com>; Jason McKemie <j.mcke...@veloxinetbroadband.com> Subject: Re: [AFMUG] Newer Netgear PPPoE Issues Yes! The issue is that even though the PPPoE Server Name field in the router is blank (which would imply it would accept any PPPoE Server Name), it is really NOT blank. It ignores the PPPoE server name that your concentrator is sending and attempt to connect to a PPPoE server name of "ppp", which your concentrator denies because that's (presumably) not its name. So, you can either hard code your real PPPoE server name into the router or you can create a PPPoE server instance name called "ppp". I found this using packet capture when having the same issue. Jesse DuPont Network Architect email: jesse.dup...@celeritycorp.net <mailto:jesse.dup...@celeritycorp.net> Celerity Networks LLC Celerity Broadband LLC Like us! facebook.com/celeritynetworksllc Like us! facebook.com/celeritybroadband On 3/13/19 12:54 PM, Jason McKemie wrote: I haven't looked into it too much, but am seeing a strange issue with the newer Netgear routers (r6120 for example) wherein they outright refuse to connect via PPPoE. I do not have this problem with any other routers as far as I know, and higher-end Netgears and/or older models seem to work just fine as well. Is anyone else having similar issues? -Jason
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
