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

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

<channel>
<title>[Fixed] Identifying source of broadcast packets in Wireless Users Chat</title>
<link>http://www.dslreports.com/forum/r21099146</link>
<description></description>
<language>en</language>
<pubDate>Wed, 11 Nov 2009 13:28:45 EDT</pubDate>
<lastBuildDate>Wed, 11 Nov 2009 13:28:45 EDT</lastBuildDate>

<item>
<title>Re: [Fixed] Identifying source of broadcast packets</title>
<link>http://www.dslreports.com/forum/remark,21122915</link>
<description><![CDATA[<A HREF="/useremail/u/1386114"><b>glane</b></A> : Thanks tx_tower. I've had a lot of intermittent performance problems in the past year as the ISP has grown. I suspect this SM isolation issue has been at least part of the problem. I've already been looking for a new provider. So far the only options I've found are the 3G/EVDO providers or going back to a partial T1. I'm not excited about either one, but at least I have choices.  :huh:]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21122915</guid>
<pubDate>Wed, 17 Sep 2008 00:10:46 EDT</pubDate>
</item>

<item>
<title>Re: [Fixed] Identifying source of broadcast packets</title>
<link>http://www.dslreports.com/forum/remark,21112424</link>
<description><![CDATA[<A HREF="/useremail/u/1502824"><b>tx_tower</b></A> : canopy has a feature that prevents traffic from 1 SM reaching any of the other SM's on the network, quite useful to prevent rogue dhcp servers. I would suggest this to your ISP and start looking for a new provider if they didnt know about this feature cause things will only get worse I promise.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21112424</guid>
<pubDate>Mon, 15 Sep 2008 11:00:08 EDT</pubDate>
</item>

<item>
<title>Re: [Fixed] Identifying source of broadcast packets</title>
<link>http://www.dslreports.com/forum/remark,21111297</link>
<description><![CDATA[<A HREF="/useremail/u/1292795"><b>shorthairedp</b></A> : As far as what to tell your ISP goes, if you have to tell them, then they shouldnt be messing around either. Let them do their job as best THEY can. If you dont think their service is up to your technical standards, then terminate and go with another provider. Thats the way I look at the "tech" customers we have, but I humor them and look into it, which is rarely anything that is any of their business. If there is an issue, they get the standard "looking into it" response. What were are doing to look into it is none of their concern.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21111297</guid>
<pubDate>Mon, 15 Sep 2008 01:35:52 EDT</pubDate>
</item>

<item>
<title>Re: [Fixed] Identifying source of broadcast packets</title>
<link>http://www.dslreports.com/forum/remark,21109828</link>
<description><![CDATA[<A HREF="/useremail/u/1386114"><b>glane</b></A> : Thanks for your comments. I'm certainly not trying to "tweak" anything in my SM or beyond. I just collected enough info from the traffic I saw hitting my router to see why I was having performance problems. I use a PPPoE connection so all of the TCP/IP settings are automatic and my SM doesn't allow any sort of admin access from my side (AFAIK). I know enough not to stick my nose where it doesn't belong.  :D<br><br>It is definitely Canopy. When you said they can lock down my radio so it won't see this traffic, do you mean that the traffic won't be transmitted to my radio or that I just won't see it? If it will fix my performance problems, I'd be grateful if you can tell me specifically what to ask my ISP to do to make this happen. They've told me they've tried to configure my account to filter out the broadcast traffic but nothing they've tried has worked. I appreciate the time they've spent trying to fix things, but I seem to be a low priority because my connection is working...it's just performing poorly. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21109828</guid>
<pubDate>Sun, 14 Sep 2008 19:29:25 EDT</pubDate>
</item>

<item>
<title>Re: [Fixed] Identifying source of broadcast packets</title>
<link>http://www.dslreports.com/forum/remark,21107019</link>
<description><![CDATA[<A HREF="/useremail/u/1292795"><b>shorthairedp</b></A> : YOU should not be sniffing around on your ISPs network. YOU can do more harm than good. We have a customer like that, his radio is so locked down now that for us to manage it, we will have to go on site and default the unit. All because hes poking around.<br><br>though to confirm its a router (hooked in backwards probably) find the MAC, its probably a linksys MAC address. the big hammer way of locating it is to put an IP in the same subnet on an interface, start pinging the ip. start rebooting radios til it stops responding. <br><br>But if its canopy gear that should have SM isolation enabled. if nothing else, have them lock down your radio, and you wont see it either.<br><br>You sure you havent "tweaked" something on your end?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21107019</guid>
<pubDate>Sun, 14 Sep 2008 04:00:29 EDT</pubDate>
</item>

<item>
<title>[Fixed] Identifying source of broadcast packets</title>
<link>http://www.dslreports.com/forum/remark,21099146</link>
<description><![CDATA[<A HREF="/useremail/u/1386114"><b>glane</b></A> : I'm a customer of a WISP using Motorola Canopy gear. A few weeks ago I started seeing some unexpected traffic on my router's bandwidth graph and at the same time I started experiencing some additional intermittent problems...packet loss, dropped connections, erratic download speeds, etc. I connected a computer with Wireshark directly to the ISP's cable and found that at exactly two minute intervals, I receive about 10,000 ICMP broadcast packets that are 74 bytes each. During these spikes, which last about 10 seconds, my latency jumps from normal (40-50 ms) to 400-1000 ms and I sometimes see packet loss. Then it returns to normal.<br><br>Apparently somebody has a router that is screwed up but my ISP can't figure out who. The traffic is coming from an IP address of 192.168.1.1, which isn't in the ranges used by the ISP. I'm wondering if anyone who is experienced with Canopy could suggest a way for my ISP to track down which radio the traffic is coming from? My ISP has said they will install a bridge at the tower I connect to, which will filter out this traffic...if it is coming from a customer on a different tower. I'm thinking there must be a way to track down the culprit. Any ideas?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21099146</guid>
<pubDate>Fri, 12 Sep 2008 12:31:35 EDT</pubDate>
</item>

</channel>
</rss>
