It took over 1 and a half hours of it doing this reboot dance until it finally stopped rebooting and stayed on.
I expect it was going through a series of firmware upgrades and configuration changes. That's not unknown for a device being plugged in for the first time and remotely managed.
Connexin REFUSED and HUNG UP on me when I insisted on getting the PPPOE info to use my own router.
Now this router is working and connected they better cough up that info. I cant even use my full connection speed with this garbage.
You haven't proved that their device is at fault, and even if it is, you should still complain about the service, because the service *includes* the router.
But firstly, you are testing via a wired connection aren't you? Wireless performance is almost always worse than wired, and affected by a whole bunch of things which are outside the service provider's control.
Also, have you tested with different client devices from different vendors? Windows laptops often perform like "garbage", due to poor quality NIC drivers and/or overhead from anti-virus scanning software.
Not happy with Connexin so far. I hope it just this router was having some issues and thats all it was. But refusing the PPPOE info and hanging up is a red flag.
If the WAN cable is an ethernet, then you can place a managed switch between the WAN port and the ONT, configure a third port as "mirror" or "span", and capture the PPPoE exchange using wireshark / tcpdump on that port. If the authentication is PAP, then you'll see the username and plaintext password.
If it's CHAP though, you'll only get the username and a hash of the password, which isn't very useful (if the password is long and randomly chosen).
Print Thread
Seansmit17
