News for hackers. Stuff that matters.
Re:Google Fiber agrees to acquire Webpass by cardigan on Wednesday June 22, 2016 @08:21PM (#11958066)
So will Webpass be faster now?
Re:Google Fiber agrees to acquire Webpass by boulos on Wednesday June 22, 2016 @08:28PM (#11958095)
My webpass is already 1 Gbps symmetric. If yours is less, it's a per-building upgrade (so maybe with additional capital they'd do that in more places) and may not be feasible.

Disclosure: I work at Google (but not on Fiber).

Re:Google Fiber agrees to acquire Webpass by pbarnes_1 on Wednesday June 22, 2016 @08:53PM (#11958185)
It's more the interconnection with the rest of the Internet than the building uplink... :)

My building is on 500mbit Webpass and things get pretty dire at peak times.

Re:Google Fiber agrees to acquire Webpass by asah on Wednesday June 22, 2016 @08:54PM (#11958188)
me too: Argenta.
Re:Google Fiber agrees to acquire Webpass by bobbles on Wednesday June 22, 2016 @08:30PM (#11958100)
Coming from australia and not familiar at all with Webpass... is the latency low? ie. could people use this for gaming internet connections?
Re:Google Fiber agrees to acquire Webpass by pbarnes_1 on Wednesday June 22, 2016 @08:55PM (#11958192)
As someone who used to live in Sydney and now in SF with Webpass... I can tell you that Webpass would be what a proper NBN rollout would look like. It's kind of amazing. It only costs $60/month and you just get an ethernet drop.

No login, no metering, no shaping.

Example latency:

  admin@RT-AC5300-E6A0:/tmp/home/root# ping -c 5 8.8.8.8
  PING 8.8.8.8 (8.8.8.8): 56 data bytes
  64 bytes from 8.8.8.8: seq=0 ttl=55 time=3.526 ms
  64 bytes from 8.8.8.8: seq=1 ttl=55 time=3.559 ms
  64 bytes from 8.8.8.8: seq=2 ttl=55 time=3.547 ms
  64 bytes from 8.8.8.8: seq=3 ttl=55 time=3.518 ms
  64 bytes from 8.8.8.8: seq=4 ttl=55 time=3.584 ms

  --- 8.8.8.8 ping statistics ---
  5 packets transmitted, 5 packets received, 0% packet loss
  round-trip min/avg/max = 3.518/3.546/3.584 ms
Re:Google Fiber agrees to acquire Webpass by baddox on Wednesday June 22, 2016 @11:43PM (#11958710)
And no public IP, which was really disappointing when I switched from AT&T Uverse.
Re:Google Fiber agrees to acquire Webpass by pyvpx on Thursday June 23, 2016 @06:49AM (#11960028)
I'm always intensely curious what residential (and these days, even business) customers want with a dedicated, publicly routable IPv4 address.

why were you disappointed?

Re:Google Fiber agrees to acquire Webpass by baddox on Thursday June 23, 2016 @01:51PM (#11963014)
I wouldn't use it for anything too resource-intensive or important. It's just nice to have my home development environment available over SSH for the rare coding emergency. I shouldn't exaggerate how disappointed I am. It's obviously not very crucial to me, since it would be easy enough to set up a cheap VPN for tunneling but I haven't bothered to do that yet.
Re:Google Fiber agrees to acquire Webpass by kornholi on Thursday June 23, 2016 @08:40PM (#11965402)
why not just use IPv6?
Re:Google Fiber agrees to acquire Webpass by rosege on Wednesday June 22, 2016 @09:08PM (#11958237)
Someone will probably roll something like this out in the metro areas and it will eat the NBN
Re:Google Fiber agrees to acquire Webpass by pbarnes_1 on Wednesday June 22, 2016 @09:10PM (#11958246)
Webpass only serves multiple dwelling units AFAIK.

You can already order microwave and fixed fiber links in Sydney CBD, Pyrmont, etc but they cost a lot more than $60/m.

The NBN was a solid idea. Execution is always kind of the issue though.

Re:Google Fiber agrees to acquire Webpass by tacticus on Thursday June 23, 2016 @02:20AM (#11959186)
> was

:( such a sad truth.

Re:Google Fiber agrees to acquire Webpass by ClassyJacket on Wednesday June 22, 2016 @10:33PM (#11958507)
I doubt it. I'm no expert, but isn't it illegal to provide non-NBN internet to any house that has NBN?

I recall someone complaining that they had no internet at all for months, because the NBN wire got hooked up to their house, but not plugged into anything at the other end - then their internet company was legally obliged to disconnect their DSL because technically they had an NBN cable - it just wasn't plugged in to anything.

Of course this would be a good law IF we were getting proper fibre NBN (and the above technicality got seen to). Just like we don't want multiple companies running power lines to one house.

Re:Google Fiber agrees to acquire Webpass by bjeanes on Wednesday June 22, 2016 @10:50PM (#11958557)
It's not illegal for a company to offer an alternative to the NBN. I think it is however mandatory for a provider who can service a dwelling with NBN to upgrade from a legacy technology (i.e. DSL) to the NBN.

This does not preclude other high-speed internet options servicing those dwellings.

For example, https://www.lightningbroadband.com.au offers or plans to offer 100/100 (actually, some pages have mentioned 200/200 but maybe that's coming later or business only). A salesperson explicitly told me they plan to service NBN-connected areas too but that they'll probably prioritise other non-NBN metro areas first, because the demand will be stronger.

Re:Google Fiber agrees to acquire Webpass by walrus01 on Wednesday June 22, 2016 @08:54PM (#11958191)
Based on what I know of Webpass' network architecture, I'd be very surprised if latency was >5ms average from any of their individual on-net buildings back to any of the major IX points where they have routers in the SF Bay area.
Re:Google Fiber agrees to acquire Webpass by curun1r on Wednesday June 22, 2016 @08:39PM (#11958137)
Former Webpass customer here. I never used it for gaming, but the highest latency I ever got from SpeedTest with an SF server was 8ms and it was usually 3-4. My building was on the 100mbps plan and the actuals were ~90mbps down, ~65mbps up.

I'd hope that connection would be good enough for gaming.

Re:Google Fiber agrees to acquire Webpass by kbar13 on Wednesday June 22, 2016 @09:17PM (#11958268)
after like 100kbps speed does not matter for gaming. you need a good quality connection (stable latency + no packet loss)
Re:Google Fiber agrees to acquire Webpass by djcapelis on Wednesday June 22, 2016 @08:33PM (#11958111)
Yes.

It's point to point wireless to a building and Ethernet from there. No real latency issue there.

Re:Google Fiber agrees to acquire Webpass by r1ch on Wednesday June 22, 2016 @08:40PM (#11958142)
Curious what they're using for backhaul wireless links if they're offering 1 gbps service. Not many solutions can handle that kind of speed.
Re:Google Fiber agrees to acquire Webpass by jauer on Wednesday June 22, 2016 @09:55PM (#11958393)
Right now you can get away with a lot of "oversubscription" in MDU situations when you have 1-2Gbps to the building (typical millimeter-wave radio speeds).

I wouldn't be surprised if they have buildings fed with 1x1Gbps going to 40x1Gbps clients.

(hand waving about Erlangs and queuing theory here) E.g. if you assume everyone is downloading a DVD image from a fast mirror (CentOS install DVD or something), they probably won't all start the download at the same time so there's a really good chance one user will finish their download before someone else starts theirs.

My MDU users rarely crack 1Mbps on a 30-day 95th percentile basis.

Re:Google Fiber agrees to acquire Webpass by gkop on Wednesday June 22, 2016 @10:26PM (#11958484)
Are you preparing for popular streaming video products pushing 4K content?
Re:Google Fiber agrees to acquire Webpass by jauer on Thursday June 23, 2016 @02:24AM (#11959201)
A popular model is to use wireless until enough you have enough customers in a building to justify building out fiber so you can supply more bandwidth. Even without fiber you could have a 50 unit building with half the units streaming 4K@30Mbps simultaneously and have enough bandwidth left over for typical web use.
Re:Google Fiber agrees to acquire Webpass by rayiner on Wednesday June 22, 2016 @08:46PM (#11958167)
Looks like millimeter wave: https://webpass.net/about_network.
Re:Google Fiber agrees to acquire Webpass by teen on Wednesday June 22, 2016 @08:57PM (#11958200)
Weird, I had Webpass for a year and was using it for a ton of gaming, and had no idea it was using wireless. It was really consistent and fast.
Re:Google Fiber agrees to acquire Webpass by boulos on Wednesday June 22, 2016 @08:44PM (#11958158)
I've got about 15ms to google.com (and the silly speedtest.net page reports 4ms for whatever they chose nearby).
Re:Google Fiber agrees to acquire Webpass by jeff18 on Wednesday June 22, 2016 @08:46PM (#11958163)
The latency to the West Coast Battle.net server is a very steady 12ms according to the Starcraft in-game UI.
Re:Google Fiber agrees to acquire Webpass by firloop on Wednesday June 22, 2016 @09:06PM (#11958234)
I live in SF and have the 100mbps Webpass. Over my wifi, I get pings of <5ms to AWS us-west-1.