Can fog affect Metro?

Jumpy

30% Packet loss last night in Limerick. Its never been this bad. Can fog affect it?
Signal was fine. But IP was brutal.

watty

I had over 60% packet loss. At one stage IRC wouldn't work. Then suddenly it was perfect with steady 23ms ping to www.heanet.ie

So, yes EXTREME fog will reduce the signal. But NO, that was not the problem. My signal was fine. (well no worse than usual).

8:50 am 19th Mar 2009

Jumpy

Thanks Watty, so it wasnt just me. Im on Sector 1 apparently. I wonder if there was an issue there. Not sure if you would be on the same.
I was on the phone last night to Australia and it was like a mobile phone fading in and out.

What time did it become stable again? Phone calls were still bad at 10:30pm

OwenM

seems to be pretty rubbish again tonight, hope it's not the start of a trend.

OwenM

how do you know what sector you are on?

Jumpy

I asked them. But this problem is covering all sectors in Limerick apparently.

9400

Hi All,
Digiweb still very poor in Limerick, I'm getting 10-15 % packet loss for the last couple of weeks. Very unreliable. How do ye find it?

watty

Contact support

On the "right" setting I have no packet loss and on the "wrong" setting I get 60% loss.

Right now in Limerick,

C:\>ping www.heanet.ie -t

Pinging samhain.heanet.ie [193.1.219.57] with 32 bytes of data:

Reply from 193.1.219.57: bytes=32 time=18ms TTL=58
Reply from 193.1.219.57: bytes=32 time=20ms TTL=58
Reply from 193.1.219.57: bytes=32 time=18ms TTL=58
Reply from 193.1.219.57: bytes=32 time=20ms TTL=58
Reply from 193.1.219.57: bytes=32 time=21ms TTL=58
Reply from 193.1.219.57: bytes=32 time=20ms TTL=58
Reply from 193.1.219.57: bytes=32 time=25ms TTL=58
Reply from 193.1.219.57: bytes=32 time=23ms TTL=58
Reply from 193.1.219.57: bytes=32 time=19ms TTL=58
Reply from 193.1.219.57: bytes=32 time=21ms TTL=58
Reply from 193.1.219.57: bytes=32 time=23ms TTL=58
Reply from 193.1.219.57: bytes=32 time=22ms TTL=58
Reply from 193.1.219.57: bytes=32 time=25ms TTL=58
Reply from 193.1.219.57: bytes=32 time=20ms TTL=58
Reply from 193.1.219.57: bytes=32 time=21ms TTL=58
Reply from 193.1.219.57: bytes=32 time=22ms TTL=58
Reply from 193.1.219.57: bytes=32 time=16ms TTL=58
Reply from 193.1.219.57: bytes=32 time=18ms TTL=58
Reply from 193.1.219.57: bytes=32 time=22ms TTL=58
Reply from 193.1.219.57: bytes=32 time=20ms TTL=58
Reply from 193.1.219.57: bytes=32 time=25ms TTL=58

Ping statistics for 193.1.219.57:
    Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 25ms, Average = 20ms

email them and phone them. I unfortunately can't help. I only know what MY settings should be.

9400

Thanks for the reply Watty,
Here's my results (fairly poor)

packets sent 27 lost 1 = 3%

round trip times
min= 10ms max= 595ms avg = 119ms

I've emailed their support and they are 'looking into the problem'. That was 2 weeks ago!!

I've been with digiweb for the last 2 years and never had a problem. Just wondering - what 'settings' exactly are you referring to?

Thanks

Liam

Jumpy

If you are connected directly to the modem go to http://192.168.100.1/
Copy and paste the RF Parameters section.

It should come out like this

RF Parameters
Downstream
Frequency Power -1 dBmV
Signal to Noise Ratio 29 dB Modulation QAM64
Upstream
Frequency Power 59 dBmV
Upstream Data Rate 5120 Ksym/sec Modulation QPSK

Before they switched me to the other sector I had
Signal to Noise of 25-27 and a Power of -5

watty

59 is very bad. Either you are very far away, a tree in the way or misaligned outdoor radio or faulty outdoor radio or marginal quality outdoor radio.

I'd expect your Upstream power to be less than 45dB with that downstream signal.

Get on to support in the morning.

Jumpy

Thanks Watty, I called them they did something on their end and its now at 42dB.

watty

So zero packet loss now?

Jumpy

Not sure yet, still at work.

Jumpy

0% after 100 pings.
1% after continous for 2 hours.

Not bad Ted, not bad.

OwenM

I emailed digiweb support and explained how the service has been very poor lately and I also attached a txt file with the 2000 pings i did to heanet.ie in the space of an hour - showing 17% packet loss.

I got an email back the following day saying they had adjusted some settings and it seems to be fine now - my ping times have even improved.

Can't really complain about them can you?