Comments on: First impressions of Verizon FIOS http://cdonner.com/first-impressions-of-verizon-fios.htm We know accurately only when we know little, with knowledge doubt increases. (Goethe) Tue, 27 Jul 2010 17:33:30 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Exothermicus http://cdonner.com/first-impressions-of-verizon-fios.htm/comment-page-1#comment-3840 Exothermicus Sat, 05 May 2007 21:38:54 +0000 http://cdonner.com/christiandonner/first-impressions-of-verizon-fios.htm#comment-3840 The reason I noticed the NAT errors was that when it is hapening, I get browser timeouts trying to load web pages. Even when trying to access the routers web page at 192.168.1.1. When it starts happening, it is a pain to try browsing into the router to see what is happening. The reason the pages time out, is that the router starts logging dozens of these nat errors per second. Exo The reason I noticed the NAT errors was that when it is hapening, I get browser timeouts trying to load web pages. Even when trying to access the routers web page at 192.168.1.1. When it starts happening, it is a pain to try browsing into the router to see what is happening. The reason the pages time out, is that the router starts logging dozens of these nat errors per second.

Exo

]]> By: Christian Donner http://cdonner.com/first-impressions-of-verizon-fios.htm/comment-page-1#comment-3839 Christian Donner Sat, 05 May 2007 18:57:12 +0000 http://cdonner.com/christiandonner/first-impressions-of-verizon-fios.htm#comment-3839 I noticed the NAT errors at some point, but not anymore. I saw lots of other errors in the system log, though, and I used the information found at http://www.dslreports.com/forum/remark,17004527 to modify the configuration file. I still get a load of messages after a reboot, but after I while it becomes quiet. I noticed the NAT errors at some point, but not anymore. I saw lots of other errors in the system log, though, and I used the information found at
http://www.dslreports.com/forum/remark,17004527 to modify the configuration file. I still get a load of messages after a reboot, but after I while it becomes quiet.

]]> By: Exothermicus http://cdonner.com/first-impressions-of-verizon-fios.htm/comment-page-1#comment-3838 Exothermicus Sat, 05 May 2007 03:41:38 +0000 http://cdonner.com/christiandonner/first-impressions-of-verizon-fios.htm#comment-3838 I got my Fios a few days after you. The installer updated the ActionTec with the 160 firmware from the start. I have had nothing but trouble with the NAT connection table full errors, i'm ready to revert to my old router/firewall as well. But my Fios was installed using the Coax WAN interface. A buddy of mine is a heavy gamer on Fios with the same ActionTec router, he recomended going back to the 120 firmware as well. Earlier this week I did that, it initially appeared to help with the nat errors, but after about 10 hours of heavy downloading of Linux ISO's, I had the problem back. It almost appears if there is a resource leak in the firmware. I had the machine doing the downloading behind another router that I just set as the DMZ in the ActionTec rules. As an experiment, I went ahead and setup individual port forwarding rules for the computer. However GRC.com's sheilds-up now shows all my ports as closed with several open's sprinkled in where they definitely should not be. I double checked I have all remote administration options unchecked, yet the open ports persist. I have tried several different drop rules in an attempt to get back the same level of stealth I had with my old router; but I keep overiding the forwarding rules. The .120 firmware also broke my VOIP connection again. I found your comment about verizon blocking port 5060 of interest, that must be what my voip provider remotely changed, to get it working under the .160 firmware, I'll have to look at it's port settings again. The hardware in the router appears to be sized for the future Fios needs, but the firmware is not what I would call enterprise class as is promoted in the literature. Exo I got my Fios a few days after you. The installer updated the ActionTec with the 160 firmware from the start. I have had nothing but trouble with the NAT connection table full errors, i’m ready to revert to my old router/firewall as well. But my Fios was installed using the Coax WAN interface.

A buddy of mine is a heavy gamer on Fios with the same ActionTec router, he recomended going back to the 120 firmware as well. Earlier this week I did that, it initially appeared to help with the nat errors, but after about 10 hours of heavy downloading of Linux ISO’s, I had the problem back. It almost appears if there is a resource leak in the firmware. I had the machine doing the downloading behind another router that I just set as the DMZ in the ActionTec rules. As an experiment, I went ahead and setup individual port forwarding rules for the computer. However GRC.com’s sheilds-up now shows all my ports as closed with several open’s sprinkled in where they definitely should not be. I double checked I have all remote administration options unchecked, yet the open ports persist. I have tried several different drop rules in an attempt to get back the same level of stealth I had with my old router; but I keep overiding the forwarding rules. The .120 firmware also broke my VOIP connection again. I found your comment about verizon blocking port 5060 of interest, that must be what my voip provider remotely changed, to get it working under the .160 firmware, I’ll have to look at it’s port settings again.

The hardware in the router appears to be sized for the future Fios needs, but the firmware is not what I would call enterprise class as is promoted in the literature.

Exo

]]>