<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: Pre-N and VOIP woes in Belkin</title>
<link>http://www.dslreports.com/forum/r14377635</link>
<description></description>
<language>en</language>
<pubDate>Wed, 25 Nov 2009 08:04:12 EDT</pubDate>
<lastBuildDate>Wed, 25 Nov 2009 08:04:12 EDT</lastBuildDate>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15764825</link>
<description><![CDATA[<A HREF="/useremail/u/908589"><b>vinnie97</b></A> : lol, interesting...maybe I'll do the same.  It would surely minimize the hassle, even though it's a little dishonest. I just don't know if I can find one locally for $90. ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15764825</guid>
<pubDate>Sun, 26 Mar 2006 16:18:47 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15763173</link>
<description><![CDATA[<A HREF="/useremail/u/1328974"><b>dsllvr</b></A> : I bought a ver 1002 and returned the ver 2000.....figured if they made a defective product, so be it...I exchanged it for one that worked. No more intermittant client assignments, either.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15763173</guid>
<pubDate>Sun, 26 Mar 2006 10:35:46 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15760144</link>
<description><![CDATA[<A HREF="/useremail/u/908589"><b>vinnie97</b></A> : How did you simply return it?  I'm assuming you did it within the required 15-day warranty period for most retail outlets.<br><br>I'll be sending in my v2000 to Belkin via RMA at the end of the month (I'm giving them until March 31st to provide an update) with the hope that they send me v1!  I will include a note for them NOT to send me another v2000 version whatever they decide.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15760144</guid>
<pubDate>Sat, 25 Mar 2006 18:49:18 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15759840</link>
<description><![CDATA[<A HREF="/useremail/u/1343647"><b>headcase99</b></A> : After not seeing any firmware updates from Belkin to address the problem with their Ver2000 units, I too finally did the same -- purchased a Ver1000, and returned the flawed Ver2000 unit.<br><br>I just could bear to go on without my SPI firewall turned on, and between streaming video and eventually my need to have VoIP, I knew the Ver2000 unit wasn't going to last without an update from Belkin.<br><br>Those Belkin boys must be oblivious to the problem.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15759840</guid>
<pubDate>Sat, 25 Mar 2006 17:33:18 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15511346</link>
<description><![CDATA[<A HREF="/useremail/u/1328974"><b>dsllvr</b></A> : I had a Belkin Pre-N Ver2000 and it chopped up my vonage.<br><br>Also dropped wireless clients and had to be rebooted every couple days.<br><br>Just installed another Belkin Pre-N but ver 1002 this time and so far, so good-firewall is up and no problems.<br><br>I am returning the Ver2000.<br><br>Hope this helps.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15511346</guid>
<pubDate>Sun, 19 Feb 2006 11:29:18 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15349674</link>
<description><![CDATA[<A HREF="/useremail/u/908589"><b>vinnie97</b></A> : My apologies, I had it in reverse!  TKIP is what I was using previously...AES seems rock solid thus far.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15349674</guid>
<pubDate>Sat, 28 Jan 2006 14:56:47 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15348025</link>
<description><![CDATA[<A HREF="/useremail/u/995338"><b>mozerd</b></A> : <div class="bquote"><SMALL>said by  vinnie97 <A HREF="/useremail/u/908589"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</SMALL><br><br>well, I got myself one of the F5D8000s for $79 at Provantage.com.  Once it arrives, I'll connect it and switch to TKIP encryption in hopes that it's the AES implementation causing the occasional wireless disconnects.</DIV>IMO the best performance, reliability and security is derived when you use WPA-PSK/AES<br><br>IMO there is no reason to use WPA-PSK/TKIP unless the wireless client does not have the AES support option and if using WZC under Windows XP/SP WPA-PSK/AES is natively supported.<br><br>Why? Because AES functions/processes at the chip level so it is significantly more efficient with the added bonus of being much more secure than TKIP encryption.<br><br>In the unlikely event you are finding that AES is slower than TKIP it is probably due to some OS issue related to an LSP process. LSP stands for Layered Service Provider and LSP processes are frequently attacked by malware of one kind or another.<br><SMALL>--<br>David Mozer<BR><A HREF="http://expertoncall.us"> IT-Expert on Call </A><BR> Information Technology for Home and Business</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15348025</guid>
<pubDate>Sat, 28 Jan 2006 10:15:32 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15337883</link>
<description><![CDATA[<A HREF="/useremail/u/908589"><b>vinnie97</b></A> : well, I got myself one of the F5D8000s for $79 at Provantage.com.  Once it arrives, I'll connect it and switch to TKIP encryption in hopes that it's the AES implementation causing the occasional wireless disconnects.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15337883</guid>
<pubDate>Thu, 26 Jan 2006 20:54:45 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15286631</link>
<description><![CDATA[<A HREF="/useremail/u/908589"><b>vinnie97</b></A> : Those NIC choices may be having an impact indeed.  The HP laptop is connecting with a Broadcom G and the PC an old (circa 2002/3) D-Link B.<br><br>I will look into snatching one of those models you mentioned to try on the PC and/or lappy.<br><br>PS. Prices are currently too prohibitive so that endeavor will have to wait.  So much for the usefulness of standards ratification. :p]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15286631</guid>
<pubDate>Fri, 20 Jan 2006 04:23:41 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15279408</link>
<description><![CDATA[<A HREF="/useremail/u/995338"><b>mozerd</b></A> : <div class="bquote"><SMALL>said by  vinnie97 <A HREF="/useremail/u/908589"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</SMALL><br><br>Even with v2000 as an AP, I get intermittent disconnects from both clients (one a B, the other a G)...so that won't even guarantee you trouble-free operation.</DIV>  vinnie97 <A HREF="/useremail/u/908589"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>, I have a large number of v200x working in commercial settings as dedicated AP's [6 months +] and I have had no complaints from any one of my clients insofar as dropping connections are concerned -- however all my clients are using F5D8010 and/or F5D8000 and or WMP54GX NIC's.<br><SMALL>--<br>David Mozer<BR><A HREF="http://expertoncall.us"> IT-Expert on Call </A><BR> Information Technology for Home and Business</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15279408</guid>
<pubDate>Thu, 19 Jan 2006 09:30:37 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15278507</link>
<description><![CDATA[<A HREF="/useremail/u/908589"><b>vinnie97</b></A> : Even with v2000 as an AP, I get intermittent disconnects from both clients (one a B, the other a G)...so that won't even guarantee you trouble-free operation.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15278507</guid>
<pubDate>Thu, 19 Jan 2006 03:22:36 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15273629</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : The QoS on the Pre-N routers to this day does not work, its just for looks and an extra button, turn it off and as far as port forwarding ive got it to work for my socom 3 on ps2 with the headset and all. easiest thing to do is use it as an AP. i run a D-Link DI-624 and Pre-N as AP]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15273629</guid>
<pubDate>Wed, 18 Jan 2006 15:25:22 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15197366</link>
<description><![CDATA[<A HREF="/useremail/u/995338"><b>mozerd</b></A> : <div class="bquote"><SMALL>said by headcase99 :</SMALL><br><br>Got to admit this thread has been extremely helpful for me, for reasons other than VoIP.<br><br>But after the firmware upgrade, suddenly my Real Player streaming videos had extremely poor audio on wireless or wired.  And the suggestion on this thread to disable the firewall (and reboot!) solved it -- now all is well until Belkin provides an update.<br><br>Lets just hope they don't break something else while fixing the firewall.</DIV>IF you have not already done so it IS very important that you email Belkin [<B>usnetsupp@belkin.com</B>] to complain that the SPI firewall BREAKS your system and request a firmware fix -- make sure to state that you do not feel that you are getting value for your money or the security protection expected if you have to disable the SPI firewall to get the functionality desired.<br><br>When emailing Belkin it is important to provide;<br>Model number and Version<br>Serial number<br>Date Purchased<br>Firmware version<br><br>The more people that email Belkin complaining about this issue the better.<br><SMALL>--<br>David Mozer<BR><A HREF="http://expertoncall.us"> IT-Expert on Call </A><BR> Information Technology for Home and Business</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15197366</guid>
<pubDate>Sun, 08 Jan 2006 07:38:01 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15197167</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Got to admit this thread has been extremely helpful for me, for reasons other than VoIP.<br><br>I recently purchased the Pre-N from Costco, after reading some fabulous performance reviews on the web.  I've got some Macs with built-in 802.11b cards (Airport), including my Titanium Powerbook with it's famously weak built-in antennae.<br><br>After trying the Pre-N with my Macs, I was pumped -- what an incredible jump in performance and range, even with the 802.11b cards!  So I knew this was the wireless router for me.  But alas, I had a new problem:  my Cisco VPN client would connect to the office, but not work properly (pass traffic) on wireless or wired.  I googled all over the Net, and found out that if I upgraded to the 2.01.02 firmware, it should resove that.  Upgraded, and now it works.<br><br>But after the firmware upgrade, suddenly my Real Player streaming videos had extremely poor audio on wireless or wired.  And the suggestion on this thread to disable the firewall (and reboot!) solved it -- now all is well until Belkin provides an update.<br><br>Lets just hope they don't break something else while fixing the firewall.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15197167</guid>
<pubDate>Sun, 08 Jan 2006 05:09:12 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15146501</link>
<description><![CDATA[<A HREF="/useremail/u/1308233"><b>antun</b></A> : Update:<br><br>You need to restart the router after turning the firewall off, in order to enforce the changes.<br><br>-Antun]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15146501</guid>
<pubDate>Sun, 01 Jan 2006 15:21:53 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,15146406</link>
<description><![CDATA[<A HREF="/useremail/u/1308233"><b>antun</b></A> : I am having problems making VOIP calls (using Skype) and I've just installed the Belkin Pre-N router. <br><br>- I've downloaded and installed the latest firmware update from Belkin (dated 9/12/2005).<br>- I've disabled the firewall.<br>- I've checked my connection speed and QOS, and they're both fine.<br><br>Before finding this thread, I could not HEAR or BE HEARD clearly. Making the above changes meant that I could HEAR inbound voice clearly, but outgoing voice is still very, very unclear.<br><br>Any ideas on this?<br><br>-Antun]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,15146406</guid>
<pubDate>Sun, 01 Jan 2006 14:59:26 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14965585</link>
<description><![CDATA[<A HREF="/useremail/u/873297"><b>dpa482</b></A> : Operate the pre-n in access point mode. The problem with the pre-n is the firewall. By using access point mode you disable the firewall and this will clear up problems with VOIP. Hopefully Belkin will come out with a new firmare update that will solve this problem. You will need to use either a software (zone alarm) based firewall or put your pre-n behind another router. Mine is behind a D-link 604.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14965585</guid>
<pubDate>Wed, 07 Dec 2005 07:10:03 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14965396</link>
<description><![CDATA[<A HREF="/useremail/u/163300"><b>Neosum</b></A> : I know this is an old thread but it seems the question was never answered. I have the same problem with this same belkin router, firmware version 2.00.06<br><br>Model: F5D8230-4 v2<br><br>I don't see an option to turn on or off QoS. I don't see any option to turn off SPI either. Was this issue ever resolved?<br><br>Below is a new thread I started before I found this thread.<br>&raquo;<A HREF="/forum/remark,14813375">[Vonage] Phone adapter behind firewall problem</A><br><br>I would love to get a solution to this problem without having to buy new hardware.<br><br>EDIT: Problem solved. Disabled firewall, QoS was enabled by default.QoS located under "wireless" and disabling firewall was under the main firewall tab rather than the subtabs.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14965396</guid>
<pubDate>Wed, 07 Dec 2005 04:55:56 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14419171</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have Vonage and Belkin pre-N router v1002.<br>is v.1002 what you mean by v2 (as opposed to v.2000)?<br><br>I have not read through this entire thread thoroughly, but I just want to say that my Vonage service works fine.<br><br>I did have some trouble with my alarm system's "kiss off" when trying to communicate with the monitoring center, which resulted in mutliple redial attempts and finally display of 'FC' on the keypad (or 'comm.failure' om 2nmd keypad).<br>This is apparently because the data is being transmitted<br>too fast to be fully understood.<br>I did some research and suggested to my friendly alarm installer that a "4+2 format" might help.<br>We ran a test (by temporarily programming my keypad with another account number that belongs to someone who has an older alarm that uses 4+2 and it worked on the first attempt. He is coming by tomorrow to reprogrammy unit; seems every zone has to reprogrammed (and re-tested).<br><br>The strange thing is that I hardly ever had problems with the current transmission format 'Contact ID' up until <br>a month or two ago, even though I had Vonage for years and have had this alarm for a year now.<br>Interestingly someone else experienced the exact same problem, where it stopped working about a month or two ago.<br>I will ask Vonage again if something was changed.<br><br>The Vonage technician (before I found out about '4+2' by googline even more and by testing it with my installer later that day) gave two possible reasons / solutions:<br>One was correct in that "lowering baud rate", which essentially comes down to switching to '4+2' format) <br>The other was grasping at straws at electromagnetic interference of large devices (microwave garage door opener) interefering with transmission over the WIRED telephone line .<br><br>I have a feeling Vonage changed something recently, but I don't know what.<br><br>The '4+2' format adds 7 seconds to the signal transmission time to the monitoring station, but that isn't a big deal; I doubt the burglar is going to stick around with a very loud siren ringing and a police station 1 minute drive away...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14419171</guid>
<pubDate>Thu, 22 Sep 2005 09:58:20 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14410423</link>
<description><![CDATA[<A HREF="/useremail/u/995338"><b>mozerd</b></A> : <div class="bquote"><SMALL>said by  stevedaulton <A HREF="/useremail/u/1006116"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</SMALL><br><br>3) As far as I can tell, v2 of the router adds the firewall and v1 did not have it at all. So it is no more insecure as running the original v1 (which I have as well).</DIV>The F5D8230-4 version 1000 series, has from its release, support for Stateful Packet Inspection [SPI Firewall] and Network Address Translation [NAT - also a form of Firewall]. The version 1000 series did not provide security logging of value where anyone who understands how to read the output could make an intelligent assessment of the traffic being logged. The QoS implementation on the 1000 series works well for me [VoIP specifically]<br>The version 2000 series of the F5D8230 improves on the logging -- however I have not had the time needed to fully asses its merits. My tests so far also show that the 2000 series of this device is [30% +/- 5%] slower than the 1000 series.<br><SMALL>--<br>David Mozer<BR><A HREF="http://expertoncall.us"> IT-Expert on Call </A><BR> Information Technology for Home and Business</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14410423</guid>
<pubDate>Wed, 21 Sep 2005 07:11:16 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14409773</link>
<description><![CDATA[<A HREF="/useremail/u/1006116"><b>stevedaulton</b></A> : Here is what I can tell about the firewall part of the router:<br><br>1) It prevents DOS, SYN, UDP, etc.. floods and attacks. That is pretty cool, except it is screwing up VOIP. Ironic that this router has a QOS setting that smooths out VOIP yet the SPI firewall kills it almost completely.<br><br>2) The NAT functions on the router are protecting it as well as just about any other run of the mill router out there, even with the firewall off.<br><br>3) As far as I can tell, v2 of the router adds the firewall and v1 did not have it at all. So it is no more insecure as running the original v1 (which I have as well).<br><br>Bottom line, I am just as protected as I was before I bought the v2 to replace my broken v1, so I am happy. Although I will really love it if and when they fix the firewall for VOIP.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14409773</guid>
<pubDate>Wed, 21 Sep 2005 01:24:43 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14409633</link>
<description><![CDATA[<A HREF="/useremail/u/103776"><b>camattin</b></A> : I sent, and got a reply, from tech support on this issue.  No resolution yet, though.  I haven't called them yet... since having the firewall off hasn't caused an increase in problems [i wound up not having to put my laptop that needs VPN access into the DMZ -- turning off the firewall /and/ rebooting solved that issue].<br><br><BLOCKQUOTE><br>Thank you for contacting Belkin Technical Support:<br><br>We will check if we can replicate the problem and we will get back to you as soon as we can. I apologize for the inconvenience.<br><br>If you still have problems, please contact us at 800-2235546 ext. 1093 to better assist you. Our Networking Support hours are 24/7. Anybody from our team should be more than happy to assist you with your technical issues.<br><br>Thank you,<br><br>Sam Villa<br>Technical Support<br>Belkin Corporation<br>Corporate Office<br></BLOCKQUOTE><br><br>I figure give them a week or so to chew on it, then I'll pester them for updates. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14409633</guid>
<pubDate>Wed, 21 Sep 2005 00:52:13 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14409303</link>
<description><![CDATA[<A HREF="/useremail/u/1006116"><b>stevedaulton</b></A> : I can verify that v2 of the pre-n router does indeed break VOIP. The SPI firewall is dropping out UDP packets as a DOS flood. You can look in the log file and see it. It is highly annoying as v1 of the pre-n router did not do this, at least not for me. I can also confirm that you must reboot the router after disabling the firewall or it won't work. Additionally, putting the voip adapter in the DMZ doesn't make a difference, reboot or not. I also updated to the 2.01.02 US version and it makes no difference either. Here is the log for any one interested:<br><br>DoS log: <br>2005-09-20 22:40:30 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:30 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:30 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:31 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:31 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:31 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:32 [UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:32 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:32 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:33 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:33 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:33 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:34 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:34 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:34 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:35 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:35 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:35 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:36 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:36 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:36 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:37 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:37 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:37 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] <br><br>2005-09-20 22:40:38 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:38 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:38 [HOST2005-09-20 22:40:39 [UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:39 [HOST Attack: UDP Flood] (UDP) LAN to WAN 192.168.2.2:16440->64.61.93.51:11898 [Drop] <br><br>2005-09-20 22:40:39 [HOST Attack: UDP Flood] (UDP) WAN to LAN 64.61.93.51:11898->65.13.190.234:16440 [Drop] ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14409303</guid>
<pubDate>Wed, 21 Sep 2005 00:00:41 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14383744</link>
<description><![CDATA[<A HREF="/useremail/u/1121068"><b>aktur</b></A> : All I know that I'm using skype with Pre-N without any problem. Wired and wireless.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14383744</guid>
<pubDate>Sat, 17 Sep 2005 10:20:49 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14383193</link>
<description><![CDATA[<A HREF="/useremail/u/103776"><b>camattin</b></A> : Hmm... can anyone with a V2000 router chime in?  I bet they changed quite a few things, and the UDP flood detection might very well have been one of them.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14383193</guid>
<pubDate>Sat, 17 Sep 2005 07:25:30 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14379148</link>
<description><![CDATA[<A HREF="/useremail/u/1253029"><b>texxsharkk</b></A> : I have version 1 (1002)...bought it the first week of August at Costco...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14379148</guid>
<pubDate>Fri, 16 Sep 2005 16:20:25 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14378279</link>
<description><![CDATA[<A HREF="/useremail/u/103776"><b>camattin</b></A> : Do you have version 1 or 2?  Wonder if they made some default changes between the two revs?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14378279</guid>
<pubDate>Fri, 16 Sep 2005 14:20:07 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14377990</link>
<description><![CDATA[<A HREF="/useremail/u/1253029"><b>texxsharkk</b></A> : I don't know...I have my firewall turned on and don't seem to have the same problems...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14377990</guid>
<pubDate>Fri, 16 Sep 2005 13:41:43 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14377809</link>
<description><![CDATA[<A HREF="/useremail/u/103776"><b>camattin</b></A> : No QoS issues here... it is simply the firewall blocking the UDP packets.<br><br>For the record, my QoS as reported by that website is 98%, rtt of only 2ms and max latency of 15ms... my connection rocks :).<br><br>On a side note...I did some speed tests through speakeasy's site before and after I switched out the routers (this belkin replaced a dlink) and saw marginally higher throughput... by about 10kbytes/s on download).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14377809</guid>
<pubDate>Fri, 16 Sep 2005 13:13:56 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14377729</link>
<description><![CDATA[<A HREF="/useremail/u/1253029"><b>texxsharkk</b></A> : Honestly, I can't really explain it, but I was having problems similar to you for a while and I really thought it was the router.  I really never did much other than a series of reloading firmware, rebooting quite a few times, running some tweak tests (you can find them here in the test section of this site)...and it seemed to 'magically' repair itself!  Still not sure what the problem really was.  My VoIP provider was having issues around the same time, so it could have been that.<br><br>I notice now that my upload speeds are pretty consistently running around 100kbs less when I'm using the VoIP, so that tells me the router QoS function is working.<br><br>When all else fails, disconnect everything, plug back in this order:  modem (let boot up), router (let boot up), VoIP box (let boot up), then plug in your ethernet connections and boot up your computers...its worth a try...<br><br>Have you tried running any QoS tests?  Try &raquo;<A HREF="http://myspeed.visualware.com" >myspeed.visualware.com</A><br>...it will give you speeds and QoS percentage.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14377729</guid>
<pubDate>Fri, 16 Sep 2005 13:01:51 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14377635</link>
<description><![CDATA[<A HREF="/useremail/u/103776"><b>camattin</b></A> : Yup... QoS on and off didn't make a difference.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14377635</guid>
<pubDate>Fri, 16 Sep 2005 12:50:48 EDT</pubDate>
</item>

<item>
<title>Re: Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14377464</link>
<description><![CDATA[<A HREF="/useremail/u/1253029"><b>texxsharkk</b></A> : did you turn "ON" QoS?   ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14377464</guid>
<pubDate>Fri, 16 Sep 2005 12:26:50 EDT</pubDate>
</item>

<item>
<title>Pre-N and VOIP woes</title>
<link>http://www.dslreports.com/forum/remark,14377409</link>
<description><![CDATA[<A HREF="/useremail/u/103776"><b>camattin</b></A> : Well, I bit the bullet and finally bought one.<br><br>As of right now, my only issue with it is that the firewall breaks my VOIP service (Vonage).  Here's a snippet from the firewall logs:<br><div class="code"><PRE><span class="codetext">2005-09-16 11:26:43 &#91;HOST Attack: UDP Flood&#93; (UDP) WAN to LAN 69.59.248.155:12960-&gt;a.b.c.d  :10050 &#91;Drop&#93;<br>2005-09-16 11:26:43 &#91;HOST Attack: UDP Flood&#93; (UDP) LAN to WAN 192.168.2.3:10050-&gt;69.59.248  .155:12960 &#91;Drop&#93;<br>2005-09-16 11:26:44 &#91;UDP Flood&#93; (UDP) WAN to LAN 69.59.248.155:12960-&gt;a.b.c.d:10050 &#91;Drop&#93;<br>2005-09-16 11:26:44 &#91;HOST Attack: UDP Flood&#93; (UDP) WAN to LAN 69.59.248.155:12960-&gt;a.b.c.d  :10050 &#91;Drop&#93;<br>2005-09-16 11:26:44 &#91;HOST Attack: UDP Flood&#93; (UDP) LAN to WAN 192.168.2.3:10050-&gt;69.59.248  .155:12960 &#91;Drop&#93;</SPAN></PRE></DIV>The 69.59.248.155 address is Vonage, the a.b.c.d is my public IP and 192.168.2.3 is the Cisco ATA-186's IP.  Since the router is dropping so many packets, no wonder I can't have a conversation with anyone.<br><br>I've sent an email to Belkin tech support... we'll see if they respond (after the h*** I just went through with buy.com's customer support, my expectations are low!!!).<br><br>Anyone here have any thoughts?<br><br>The really annoying thing is that turning off the firewall doesn't turn off the "DoS" .. umm .. 'features'. :(<br><br>UPDATE: Turning off the firewall AND REBOOTING allows VOIP to work.  When you turn off the firewall, it doesn't say you have to reboot and it doesn't reboot for you.  But I rebooted the router manually through the web interface, and Vonage started working.  The worse part of having the firewall off is having to put my work laptop in the DMZ to get the VPN working, since Belkin won't allow you to forward anything but TCP or UDP... I need to forward IP 50 for the VPN client.<br>-mod note, replaced pre tags with code tags to stop the margin blowout.<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14377409</guid>
<pubDate>Fri, 16 Sep 2005 12:18:19 EDT</pubDate>
</item>

</channel>
</rss>
