New fiber modem with router

ICOTERA-IGW3000

Last week my old fiber modem died, and I had to get a new set up. And with a newer device, things should be better made with mistakes from the past, right? … if just it was so.

So here are my problems, some that should have been found and fixed long ago in my opinion.

  • Problem 1: Create port forwarding rule, set it to enable, enable loop-back, apply. And it will not enable loop-back, to enable loop-back, click the box again, press save, then apply. Changing destination ip and pressing apply, will disable loop-back again, even if it was on before pressing apply. Ip is changed properly.
  • Problem 2: When port forwarding port 80 with loop-back enabled, and you enable WiFi. All port 80 traffic is routed to the ip port 80 is forwarded to. So suddenly http://facebook.com/ is my own server, http://google.com/ is also send to my server… everything port 80 is send there, but only after enabling WiFi. http://192.168.1.1/ which should be the router iself, also directs to the port 80 routed ip.
  • Problem 3: Pressing and holding reset will reset the router, but it will fail to start up properly afterwards. When looking at the status led’s, they report all is okay, but it will not respond to any internal traffic. http://192.168.1.1/ isn’t even on the network. Solution to that is to keep power cycling it until it decides to show up on the network again.
  • Problem 4: DNS on default ip (192.168.1.1) stops working after a few days of use. A fix is to power cycle it, or to change the default dns ip to 8.8.8.8 for primary and 8.8.4.4 for secondary.
  • Problem 5: Ping times has gotten higher. With my old modem, and my own Cisco router, I had ping times reliably at 2ms to http://google.dk/ now with this ICOTERA IGW3000, it is between 8ms and 20ms, and spikes even higher.
  • Problem 6: After transferring a certain (exact size not found yet) amount of data, it just stops responding. Only way I have found to get it to respond again, is a manual power cycle.

Leave a Reply