Packetfront/Waystream gear
Does anyone have experience running Packetfront hardware in a production network? We've looked at a few and they seem to be pretty good but I want to know if they have downsides. We're looking at them for edge switches now and thinking about if they can be site routers or switches (either a q-in-q vlan handoff to a ring or a separate L3 with routing protocols depending on how the site is accessed) You can contact me offlist if you don't want to talk about it publicly. Thanks, Robert
Re: Fwd: [ PRIVACY Forum ] Windows 10 will share your Wi-Fi key with your friends' friends
On 07/06/2015 02:16 PM, Richard Golodner wrote: Mommy has an Android... Android shares your wifi password with Google. Including the password of everyone's wifi you've ever logged into. http://www.computerworld.com/article/2474851/android-google-knows-nearly-every-wi-fi-password-in-the-world.html
Re: symmetric vs. asymmetric [was: Verizon Policy Statement on Net Neutrality]
On 03/03/2015 08:07 AM, Scott Helms wrote: I'm not done collecting all of our data yet, but just looking at what we have right now (~17,000 APs) over half of the clients connected have an upload rate of 5mbps or less. A just over 20% have an average upload rate of 1mbps. BTW, the reason we're working on the WiFi data is that we think this is a huge problem, because consumers don't separate the performance of the in home WiFi from their overall broadband experience and we need to dramatically improve the in home WiFi experience to increase customer satisfaction. The Cloud solved most peoples issues with NAT. Rather than having IPv6 to a fileserver at my house, I've got the option of IPv4 to dropbox anywhere. Most people store all their data on remote servers now. That means unless they're uploading a new picture to facebook or a new video to youtube, 90% of their at home usage of their wireless will be downloads (looking at existing content). Given that some people are getting Active Ethernet to the home, with IPv6, we might see an eventual new killer app that changes the way bandwidth is used, but I think right now the reason we're not seeing a killer app is because of two things: 1. Users don't have the bandwidth. Most people really are on constrained pipes that can't tolerate heavy uploads 2. NAT still breaks things for everyone so people can't do it.
Re: Comcast Business Internet Options
On 06/30/2014 03:49 PM, Phil Gardner wrote: Damn, interesting. Though for my needs, I'm more interested in the response time for service than all out speed. I'd also be surprised if they offer that in my state. Where are you located? Usually you can get an okay DSL connection as a backup and that would be better than most of the SLAs from big companies*. Alternatively you could get a wifi or USB LTE dongle for a secondary connection. Of course that may not be available in your area, but I've gotten LTE in surprising places. * The problem with the SLAs being that they won't restore your service in 3 days, they'll just credit you the full price of your dinky circuit. The good news is if your inside wiring is clean then you probably won't have too many outages on cable. Ask your neighbors if their Internet is reliable. signature.asc Description: OpenPGP digital signature
Re: COX contact
On 08/12/2013 02:35 PM, Meshier, Brent wrote: I've tried tech support but they only seem to be concerned about signal strength rather than peering issues. --- Please refer to http://www.amherst.com/amherst-email-disclaimer/ for important disclosures regarding this electronic communication. I checked your email headers and it doesn't include the signal strength. Can you include that in the subject line in future emails? Also since they didn't indicate what to measure or what units, I would say that my signal strength currently is 5. Oh, and if you have a signal strength meter that only goes to 10 you need to buy the better one that goes to 11. signature.asc Description: OpenPGP digital signature
Re: IP4 address conservation method
On 2013-06-05 18:25, Ricky Beam wrote: That said, I do use a stripped debian box as an inter-vlan router. You don't want to see the pages of tweaks it's taken to stop it being a broadcast storm generator. (and no, arpd is stupid hack.) It's a beautiful thing to run tcpdump ... broadcast and see no packets! (And I'm not too happy with the BS 32 interface limit for multicast routing.) Actually, I'd love to see the pages of tweaks. Seems like it would be useful if I need to do this in the future :) Maybe drop it on the Debian wiki somewhere if you get the chance. Or at the least it would be nice to know what issues you're hitting now. You can tune the neighbor cache size and timeout via sysctl, so I would think it would be more of a memory limit than anything (unless the kernel uses a really poor hash lookup for arp entries) --Ricky --Robert
