Rip Wave!!!!

Gorgon

Is Ripwave frequency hopping?

im not sure what you mean all I know is that it's 2.4Ghz thats it, or if that answers your question fine.

spongebob

Originally posted by Gorgon
Serbian is correct it is on the 2.4 Ghz band but theres also the option for IBB to go on the 2.6Ghz band later on, I know they have been in talks with comreg about it.

There is no such option, Chorus and Ntl have all the 2.6 band.

It will go to 3G in 5 years....maybe.

IBB have been in negotiation with Chorus about using some of their allocation and running a BNVO (Virtual Network)

M

Gorgon

Originally posted by Muck
There is no such option

thats correct but all i meant is that Navini offer equipment opperating in the 2.6 band, not saying that are going to or not.

machalla

What about the chorus license being redistributed? According to an article in the Independent yesterday (if my moemory isn't going) chorus lost their license and it is going to be redistributed in beaty contest style auction. I didn't pay that much attention to it at the time but it might be worth a look. And the Canopy system thats in todays Irish Times sounds like it might have some potential. Although still needing a line of sight. Nice download speeds though potentially. 10 mb as opposed to 512K. Someday...

Mutant_Fruit

What tower are you running off all the way over there in balinteer, and do ya think i'd reach that same tower from rathfarnham/ballyroan?

Kappar

Originally posted by Mutant_Fruit
What tower are you running off all the way over there in balinteer, and do ya think i'd reach that same tower from rathfarnham/ballyroan?

The 3 Rock mast i'm not sure f you'd reach it from there give 'em a call

griffdaddy

mutant fruit, i live in ballyroan. real near the school and they told me they reckon i can get it, i'll know by wednesday. whereabouts are you? whats your name?

Mutant_Fruit

Excellant news!! i live the far end of ballyroan road... i won't say exactly where though... :-p but near blue havan.

I bitched so much that now i'm being offered an option to test ripwave :-D. I've already been contacted (yes they rang me!) by a member of the Ripwave team and they were uncertain if i'd get a signal... but i told em that i was in range of three-rock, but a tree blocked my LOS, thank god i didn;t say i was out of range.

Hopefully i'll get connected by tuesday. I'd be pretty surprised if they kept me waiting... i've been in touch with em everyday since wednesday 24th. The tech support guys must shudder when they hear my voice.... here are my currect ping stats:
Ping statistics for 195.26.12.225:
Packets: Sent = 52, Received = 46, Lost = 6 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 1059ms, Average = 525ms

Hopefully Ripwave will fix this nicely

griffdaddy

well i have a note on my record saying i get installed first! i told them wednesday was the only day i could do it so they said they'll probably do it wednesday, they're actually really friendly

griffdaddy

i'd be shi8tting in my payed for with blood broadband money boots if i was eircon!

Mutant_Fruit

well i have a note on my record saying i get installed first!

we'll see about that. I intend to get myself hooked up asap, but the odds are very high that they'll move directly from your house to mine, considaring we're so close. So we'll both get ripwave in the same hour.

i'd be shi8tting in my payed for with blood broadband money boots if i was eircon!

Damn right. Eircom are going down and out, they have a lowest caps & worst reports. I can't imagine people going with them when they see the cheaper alternatives.

Gorgon

Hold the phone I wouldnt start to get carried away i took the modem down to my friends house in Dundrum and am getting pings of the following

ping boards.ie -n 20

Pinging boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=237ms TTL=52
Reply from 217.114.166.147: bytes=32 time=125ms TTL=52
Reply from 217.114.166.147: bytes=32 time=105ms TTL=52
Reply from 217.114.166.147: bytes=32 time=285ms TTL=52
Reply from 217.114.166.147: bytes=32 time=125ms TTL=52
Reply from 217.114.166.147: bytes=32 time=145ms TTL=52
Reply from 217.114.166.147: bytes=32 time=495ms TTL=52
Reply from 217.114.166.147: bytes=32 time=255ms TTL=52
Reply from 217.114.166.147: bytes=32 time=125ms TTL=52
Reply from 217.114.166.147: bytes=32 time=185ms TTL=52
Reply from 217.114.166.147: bytes=32 time=105ms TTL=52
Reply from 217.114.166.147: bytes=32 time=165ms TTL=52
Reply from 217.114.166.147: bytes=32 time=395ms TTL=52
Reply from 217.114.166.147: bytes=32 time=355ms TTL=52
Reply from 217.114.166.147: bytes=32 time=215ms TTL=52
Reply from 217.114.166.147: bytes=32 time=115ms TTL=52
Reply from 217.114.166.147: bytes=32 time=155ms TTL=52
Reply from 217.114.166.147: bytes=32 time=215ms TTL=52
Reply from 217.114.166.147: bytes=32 time=155ms TTL=52
Reply from 217.114.166.147: bytes=32 time=145ms TTL=52

Ping statistics for 217.114.166.147:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 495ms, Average = 205ms

and jolt

ping www.jolt.co.uk -n 20

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=168ms TTL=56
Reply from 195.149.21.11: bytes=32 time=130ms TTL=56
Reply from 195.149.21.11: bytes=32 time=130ms TTL=56
Reply from 195.149.21.11: bytes=32 time=120ms TTL=56
Reply from 195.149.21.11: bytes=32 time=190ms TTL=56
Reply from 195.149.21.11: bytes=32 time=250ms TTL=56
Reply from 195.149.21.11: bytes=32 time=250ms TTL=56
Reply from 195.149.21.11: bytes=32 time=130ms TTL=56
Reply from 195.149.21.11: bytes=32 time=160ms TTL=56
Reply from 195.149.21.11: bytes=32 time=210ms TTL=56
Reply from 195.149.21.11: bytes=32 time=170ms TTL=56
Reply from 195.149.21.11: bytes=32 time=380ms TTL=56
Reply from 195.149.21.11: bytes=32 time=180ms TTL=56
Reply from 195.149.21.11: bytes=32 time=170ms TTL=56
Reply from 195.149.21.11: bytes=32 time=210ms TTL=56
Reply from 195.149.21.11: bytes=32 time=120ms TTL=56
Reply from 195.149.21.11: bytes=32 time=130ms TTL=56
Reply from 195.149.21.11: bytes=32 time=130ms TTL=56
Reply from 195.149.21.11: bytes=32 time=150ms TTL=56
Reply from 195.149.21.11: bytes=32 time=100ms TTL=56

Ping statistics for 195.149.21.11:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 380ms, Average = 173ms

the modem isnt where i would like it, it's downstairs not near the window, downloads are still good 50kb/s but it seems that upstairs directly at the window on the south-face of the house is the best place

griffdaddy

how does it make a difference if it's near the window when the signal is coming through a load blockages already? do you have to sort out payment details while they install it for after the test, or do they get back to you?

Gorgon

i dont know about the payment side of it, later on last night the ping rate fell off a great deal and i was getting pings in the 1000 - 2000ms and timeouts, im back home now and its fine. It works of somesort of reflective technology so it wont get a good signal directly in front of a solid brick wall

Kappar

Originally posted by griffdaddy
do you have to sort out payment details while they install it for after the test, or do they get back to you?

I signed a DD to start on the 1st of sept if i am happy with keeping it.

Mutant_Fruit

so basically you're saying pings vary greatly depending on where the box is placed... well i should have no problems moving the box around and checking pings from different areas in my house

As it is, my LOS broadband pings are great again... i'm now getting average pings of 20 to my gateway.... but it still spikes occasionally. But it's quite playable. maybe they've fixed it again, maybe not. I've been told that the pings were fixed 3 times already, and each time it only lasted a few hours

griffdaddy

still no sign of my ripwave, mutant, are you still gonna get yours installed? you might aswell, if only to get the engineers to come down our way

Mutant_Fruit

i got a call yesterday (thursday) saying that they can't get a signal out as far as ballyroan :-(. I'm not sure if i believe them though, they could just be trying to stop me testing ipwave... who knows. So as it is, i've still got the line of sight broadband.

However they did tell me that they were experienceing difficulties in the Tallaght tower, which was the first time they admitted they had problems, previously they were giving me the impression it was just me, but its not. THey said they don't know when the problems will be resolved though. But i guess it will be when they get more money to upgrade their servers.

griffdaddy

hmmm thats odd! i just got off the phone with them and i'll be ripping waves between 9 and 12 tomorrow morning!

Mutant_Fruit

well, tell me what signal strength you're getting, what your pings are like, what download speeds you get and any other relevant info like packet loss.

If you get a nice strong signal, then i might go right ahead and tell em to bring over a kit for me. But it seems the pings are better again today. I had a nice 2hour Counter-Strike session with pings of averaging 70 :-D best pings ever.

griffdaddy

whats counter strike? a game obviously but what kind?

Mutant_Fruit

Terrorist V Counter-Terrorist realistic shoot-em-up, available as a free download for people who own Half-Life, or for 15 eur (and less) in shops.

griffdaddy

i just failed the signal test! f'uck! i'm so pissed off. they can get it down in otterbrook though.

gandalf

Just got on the trial in Ballinteer. Fairly good performance so far. Unfortunately the connection is a bit ropey for gaming. But for general browsing its very good

Gandal.f

Mutant_Fruit

ah well, looks like they were telling me the truth.

**pats antenne** my baby is working good again anyway. i've been getting good pings these last 2 days :-D

Pinging www.boards.ie [217.114.166.147] with 32 bytes of d

Reply from 217.114.166.147: bytes=32 time=148ms TTL=53
Reply from 217.114.166.147: bytes=32 time=26ms TTL=53
Reply from 217.114.166.147: bytes=32 time=58ms TTL=53
Reply from 217.114.166.147: bytes=32 time=29ms TTL=53
Reply from 217.114.166.147: bytes=32 time=28ms TTL=53
Reply from 217.114.166.147: bytes=32 time=27ms TTL=53
Reply from 217.114.166.147: bytes=32 time=35ms TTL=53
Reply from 217.114.166.147: bytes=32 time=29ms TTL=53
Reply from 217.114.166.147: bytes=32 time=30ms TTL=53
Reply from 217.114.166.147: bytes=32 time=31ms TTL=53
Reply from 217.114.166.147: bytes=32 time=29ms TTL=53
Reply from 217.114.166.147: bytes=32 time=33ms TTL=53
Reply from 217.114.166.147: bytes=32 time=71ms TTL=53
Reply from 217.114.166.147: bytes=32 time=25ms TTL=53
Reply from 217.114.166.147: bytes=32 time=36ms TTL=53
Reply from 217.114.166.147: bytes=32 time=33ms TTL=53
Reply from 217.114.166.147: bytes=32 time=27ms TTL=53

Ping statistics for 217.114.166.147:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 148ms, Average = 40ms
Control-Break
Reply from 217.114.166.147: bytes=32 time=28ms TTL=53