That Roku is cramming more extra wifi down my throat.Ĭrappy DirectTv installer misconfigured the MoCa bridge, again. Hp printer with WiFiDirect enabled, and connect to the wireless router.Ĭhromecast putting out WiFi, while connected to wireless router.Īll the Apples searching for Airplay, Airprint, etc ectĪppleTv doing the bonjour sleep_proxy arp dance, amongst others.Įverybody is running Dropbox Lan client, two or three print status monitors, searching for that Damn Chromecast to cast to, MdnsResponder because "If you wanna manage those iPhones with windows you gets Apple Networking with it.the list is endless here, much of it multicast and poorly coded it seems.īilly's Xbox is looking for Friends and Media neighbors.and demands UPnP be found. Most home networks I deal with on a daily basis look more like this: Here's the thing though, most folks do not. You sound savvy, so I would assume you have taken some time to ensure your network works well too. On a well planned and executed Network I would totally agree, I can run VM's stored on NFS over the wire at lag free gigabit speeds on my Lan. Thanks a bundle Google, at least I didn't splash out a sizable sum for a replacement router (although that's only because I couldn't get my wife's permission to buy something that had the performance plus bells and whistles). So it would be Google and not BT I have to blame for this personalised DDOS system that out four Chromecasts are providing (three permanently on and one plugged into the TV USB port). As an interim, I plugged in a Home Hub 4 that I had serving up wifi in our garage and that appears to be working fine so far. Next step was finding a router that did not resemble a randy porcupine that Mrs Sinclair would be happy to see on the telephone table in our hall (in fairness, the Home Hub is relatively anonymous looking except when being hit by angy teenagers who can't find the reset button). First step on that BTexit journey was the £18 Openreach VDSL modem off ebay. I too had concluded that our BT Home Hub 5 was living up to its (perhaps unfair?) reputation of being terrible due to frequent Wifi problems at home preventing our teenagers from using their gadgets and me watching Star Trek on Netflix via Chromecast and I was on the cusp of binning it and buying someone else's router. In short, it's OK to expect better, but you're not going to get perfect. However, unless you have a device that can process all potential traffic at the speed of the physical medium you're going to have problems of some sort - and that device wouldn't be competitive in a domestic market.Įven if it were, shared-media systems (like wired and wireless ethernet) depend to some extent on the connected devices behaving: if you have a device that jabbers constantly, there's not much you can do. A better thing to do might be to stop receiving altogether, but the AP would then effectively go deaf until it had caught up with the multicast traffic. While the router shouldn't totally lock up under these conditions and ought eventually to recover, receiving a large number of short packets back to back will inevitably seriously impact the throughput for other devices on the network and could result in network devices being dropped temporarily, simply because the radio space is being hogged by the amount of traffic from one source.ĭomestic access points are typically not equipped with particularly fast processors and so there is a depdency on the underlying network hardware to be able to discard or ignore data that's arriving too quickly - it's possible in this case that because the packets are multicast they're being passed up the stack to the CPU but there's no limit on the number of buffers that can be allocated for that purpose, the CPU is getting behind and hence memory is being exhausted.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |