Airtel V-Fiber (VDSL) - Problems after upgrade [40 Mbps/Bangalore]

liverpool79

Newbie
Messages
213
Location
Bangalore
ISP
Airtel
So just to give you all an update/experience with the VDSL connection so far.....not as good as ADSL.Im fact i would go so far as to say it's been pretty unstable as one can see from the screenshots of pings/packet loss that i've recorded between Jan 17-Jan 30:

Source

Source


As can be seen from above screens lot's of 'General Failure' during the first few days later followed by a mix of 'General Failure' and Request Timed Out' msgs...

Finally,i got fed up and called CC today and told them about it.The engineer from my area got back to me and said he needed to upgrade the router firmware....which if i recall correctly he had already done a few weeks back! Then the usual router restart....took me 20 minutes to connect to my wireless network...i have no idea why...it kept saying 'could not connect'!!

Anyway,past hour or so the ping replies are much better with an occasional "General Failure' popping up every 20-30 replies.No 'Request Timed Out's' yet thank god.

Overall,my older ADSL connection was so stable,i'm really not sure the increased speeds of VDSL is worth the grief if this continues on.Reminds me of Sify ( 'shudders')
 
Messages
146
Location
NA
since they were providing free router I too have upgraded to VFiber a couple days back and I must say my connection is just as stable as it was on ADSL and I hope it stays that way. Though I am only getting 16mbps. SNR is only 10-15 db but connection is stable till now.
 
Last edited:

liverpool79

Newbie
Messages
213
Location
Bangalore
ISP
Airtel
Well since my connectivity issue is still alive,i did a little experiment and pinged my public IP both on my old laptop as well as my brother's brand new laptop.My old laptop showed the same errors mentioned above while my brother's laptop gave continous replies with no packet loss.

So my question is could my old wireless network adapter (Atheros AR5007EG) have trouble connecting properly to the VDSL modem? Is that why only my laptop is exhibiting these connectivity issues?

Also, when diagnosing my network (which is working by the way),i get:

Cannot communicate with DNS server (xxx.xx.xx.xxx)

Network diagnostics pinged the remote host but did not receive a response.
 
D

Deleted member 63558

Hi I would suggest you to take a Ethernet from your Airtel's Modem and put the Ethernet directly to your PC or Laptop. After that, ping Google.com

ping google.com -t

Don't use any other router in-between and don't test it on WiFi. It is possible that your WiFi is causing you such problems.

If ethernet shows the same problem? Then for sure Airtel is what causing the problem (given that the ethernet you are using is perfect).

Do it and report back.

Do for at-least 1 day.

Tell your family members that internet is not working (so that they don't ask you if it's working or not).

This test will tell you the real picture and help us too for helping you better.
 

liverpool79

Newbie
Messages
213
Location
Bangalore
ISP
Airtel
@Adidam

So i did as you asked and monitored the connection and here are the reults:

Direct Ethernet cable:

Ping statistics for 216.58.197.46:
Packets: Sent = 400, Received = 400, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 13ms, Average = 12ms

Ping statistics for 122.xxx.xxx.xxx:
Packets: Sent = 400, Received = 400, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms

Ping statistics for 172.217.31.206:
Packets: Sent = 2000, Received = 2000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 15ms, Average = 12ms

Ping statistics for 122.xxx.xxx.xxx:
Packets: Sent = 2000, Received = 2000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 12ms, Average = 0ms

-------------------------------------------------------------------------------------------------------------------------


WiFi (on) next to router/modem:

Ping statistics for 122.xxx.xxx.xxx:
Packets: Sent = 200, Received = 200, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 65ms, Average = 1ms

Ping statistics for 216.58.197.46:
Packets: Sent = 400, Received = 400, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 94ms, Average = 18ms


--------------------------------------------------------

Wifi on in room (16-18 feet from router/modem)


Ping statistics for 172.217.26.174:
Packets: Sent = 400, Received = 390, Lost = 10 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 3112ms, Average = 79ms

Ping statistics for 172.217.26.206:
Packets: Sent = 2000, Received = 1956, Lost = 44 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 3054ms, Average = 94ms

Ping statistics for 216.58.197.46:
Packets: Sent = 2000, Received = 1891, Lost = 109 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 151ms, Average = 16ms

Ping statistics for 216.58.197.46:
Packets: Sent = 2000, Received = 1956, Lost = 44 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 193ms, Average = 21ms

Ping statistics for 216.58.197.78:
Packets: Sent = 400, Received = 392, Lost = 8 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 111ms, Average = 39ms

Ping statistics for 216.58.197.46:
Packets: Sent = 400, Received = 382, Lost = 18 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 163ms, Average = 22ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 371, Lost = 29 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 169ms, Average = 18ms

Ping statistics for 172.217.160.142:
Packets: Sent = 400, Received = 341, Lost = 59 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 91ms, Average = 17ms

Ping statistics for 172.217.160.142:
Packets: Sent = 400, Received = 392, Lost = 8 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 122ms, Average = 27ms

Ping statistics for 216.58.197.78:
Packets: Sent = 400, Received = 272, Lost = 128 (32% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 1754ms, Average = 28ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 326, Lost = 74 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 124ms, Average = 26ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 371, Lost = 29 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 1752ms, Average = 32ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 361, Lost = 39 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 153ms, Average = 18ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 396, Lost = 4 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 102ms, Average = 20ms

Ping statistics for 172.217.26.174:
Packets: Sent = 400, Received = 393, Lost = 7 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 107ms, Average = 40ms

Ping statistics for 172.217.31.206:
Packets: Sent = 800, Received = 785, Lost = 15 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 536ms, Average = 25ms

Ping statistics for 216.58.197.46:
Packets: Sent = 800, Received = 793, Lost = 7 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 110ms, Average = 20ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 393, Lost = 7 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 100ms, Average = 21ms

Ping statistics for 172.217.26.174:
Packets: Sent = 400, Received = 386, Lost = 14 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 118ms, Average = 41ms

Ping statistics for 216.58.197.78:
Packets: Sent = 400, Received = 390, Lost = 10 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 100ms, Average = 22ms

Ping statistics for 172.217.160.142:
Packets: Sent = 400, Received = 395, Lost = 5 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 136ms, Average = 19ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 395, Lost = 5 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 102ms, Average = 20ms

Ping statistics for 172.217.26.174:
Packets: Sent = 400, Received = 390, Lost = 10 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 337ms, Average = 52ms

Ping statistics for 172.217.31.206:
Packets: Sent = 400, Received = 391, Lost = 9 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 98ms, Average = 22ms

Ping statistics for 216.58.197.46:
Packets: Sent = 800, Received = 727, Lost = 73 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 3905ms, Average = 174ms
 
D

Deleted member 63558

Hi. Seeing the stats, I believe. You got your answer? It's your WiFi which is faulty.
 


liverpool79

Newbie
Messages
213
Location
Bangalore
ISP
Airtel
Yes,it does look like my specific problem is to do with WiFi.I think the easy solution would be to get a longer Ethernet cable since the laptop device i use is mostly confined to use in my room.

I have been looking up a few Ethernet cables online and decided on these 2 purely on ratings/reviews:

Amazon.in: Buy AmazonBasics RJ45 Cat-5e Network Ethernet Cable - 25 Feet (7.6 Meters) Online at Low Prices in India | AmazonBasics Reviews & Ratings

Quantum Ethernet Patch Cord CAT5 RJ45 Lan Straight Cable Category 5E - 10M meter/metre: Amazon.in: Computers & Accessories

Would either one of these be all right with my VDSL? Also,i would like to know if me using the net via cable would have any major adverse effect on rest of users in my home who connect through WiFi?
 
Last edited by a moderator:
D

Deleted member 63558

Hi. Amazon Basic is the best cable.
You connect ethernet to the router's RJ45 and Laptops RJ45.

Generally if you are just surfing, it won't.

But if you are downloading anything. Router might prioritize you over WiFi.

Apart from this, nothing else.

I would says. Get a cheap router Asus router from Amazon and use that for the WiFi.

It would solve your problems.

You can always return it in 10 days if didn't solve.
 

liverpool79

Newbie
Messages
213
Location
Bangalore
ISP
Airtel
@Adidam

Thanks for your patient replies and clarifications.Can you please confirm that these are RJ45's on my router and laptop?

pverb0r.jpg


cC4Ju0k.jpg