Virgin Media Discussion Thread

Slam62 said:
Don’t get too excited, that page very rarely works for me and when it does its full price.
Click to expand...

Yeah but I just chatted to vm and got a better deal, but need to look it over before I potentially accept but I can't find it on the account.

Not the greatest

but got offered

350 boosted to 500mb (volt)
mix tv
anytime calls

£59, I'm paying considerably more.

But can't find the offer, lol.
 
Last edited:
Ok so signed up again with Virgin, Ive been happy with the broadband to be honest and nothing around my way comes close to the speed they offer yet, so in 18 months time that may have changed though and I can look elsewhere. In the meantime I think the deal I got isn't to bad, certainly nothing fantastic but its better than paying £83 a month not including mobile phone plan price.

Now have

500mb broadband
mixit tv
talk weekends chatter
o2 10gb sim plan unlimited minutes/text

£62
 
On the web chat waiting again to pretend to cancel and notice there is an offers page on my account which is £25 for 350mbit (250 + Volt although I ditched the O2 sim a few months ago :shrug: ) which doesn't seem bad considering I was paying £30 before. When phoning before they didn't seem to do anything less than 18 months contract now which is annoying as should be a couple of other options for FTTP for the first time coming up.
 
Last edited:
Duke said:
On the web chat waiting again to try and to pretend to cancel and notice there is an offers page on my account which is £25 for 350mbit (250 + Volt although I ditched the O2 sim a few months ago :shrug:) which doesn't seem bad considering I was paying £30 before. When phoning before they didn't seem to do anything less than 18 months contract now which is annoying as should be a couple of other options for FTTP for the first time coming up.
Click to expand...

I just signed up post above yours to an 18m contract, but my area is still unknown on fttp rollout, hopefully by end off my contract BT or community fibre will be around here.

By the way VM offer 30 day rolling contracts. If you are out of contract you should be able to go onto a rolling contract.

I did above via what’s app, but when we were out of contract at start of year we phoned up retention line and went onto the 30day rolling, but now back into 18m after negotiating the above.
 
Last edited:
beachBOYken said:
I just signed up post above yours to an 18m contract, but my area is still unknown on fttp rollout, hopefully by end off my contract BT or community fibre will be around here.

By the way VM offer 30 day rolling contracts. If you are out of contract you should be able to go onto a rolling contract.

I did above via what’s app, but when we were out of contract at start of year we phoned up retention line and went onto the 30day rolling, but now back into 18m after negotiating the above.
Click to expand...
I'd guess the rolling contract is more? I'm not sure of the ETA of other builds around here, there is Youfibre who have done what it sounds like they've done in other areas and just wire up one or two streets, Open Reach have a few road works planned but nothing on their site with a date but Truespeed have started recently which are most likely the best bet out of them. The same as you though luckily my area for VM is actually okay so its not terrible but lower pings and quicker upload for work would be handy.
 
Last edited:
Duke said:
I'd guess the rolling contract is more? I'm not sure of the ETA of other builds around here, there is Youfibre who have done what it sounds like they've done in other areas and just wire up one or two streets, Open Reach have a few road works planned but nothing on their site with a date but Truespeed have started recently which are most likely the best bet out of them. The same as you though luckily my area for VM is actually okay so its not terrible but lower pings and quicker upload for work would be handy.
Click to expand...

Nope rolling contract was not more, I can’t remember what we said now to get put on it, at time we negotiated the price down a little and basically said price was too much and can’t afford it , advisor came back with a suggestion of a rolling contract.

Edit/ actually I remember now we said we were looking at joining Community Fibre in very near future, although it’s not here yet, so they offered the rolling contract.
 
Last edited:
Signed up and they sent a hub 3. I guess the lower 132mb tier don't get the newer hubs. My sister is signed up to O2 so I wonder if the Volt stuff still applies.
 
jklc said:
Signed up and they sent a hub 3. I guess the lower 132mb tier don't get the newer hubs. My sister is signed up to O2 so I wonder if the Volt stuff still applies.
Click to expand...
Yes I think the higher tiers get the hub 4 and 5 until they have more of them in stock maybe? The volt thing should self activate after a few days or so, else give them a nudge, I can't remember if it just needs to be the same address or if the account name has to match as well, have a feeling matching address is enough.
 
Anyone got o2 SIM card plan ?

I switched to a volt package and got sent a new o2 SIM card in the post, in the meantime I got a text on my old vm SIM card saying text SWAP to 20220.

Im lost, lol. Do I do this now on my old virgin mobile sim or when I have the o2 sim in my phone?
 
Last edited:
beachBOYken said:
Anyone got o2 SIM card plan ?

I switched to a volt package and got sent a new o2 SIM card in the post, in the meantime I got a text on my old vm SIM card saying text SWAP to 20220.

Im lost, lol. Do I do this now on my old virgin mobile sim or when I have the o2 sim in my phone?
Click to expand...

Are you sure there isn't a letter in there somewhere telling you what to do? There nearly always is. I would read that as sending the text on your old SIM card, then swap to the new SIM.
 
Has anyone noticed their connection varies quite wildly depending on which IP address/range they get? For example, on 86.8.0.0/17 (iirc) I was pinging Cloudflare/1.1.1.1 around 12ms and had great latency (for VM) to almost everyone. Outliers were Quad9 (28ms) and Oracle's network (28-30ms).

Since I swapped back to VyOS, I picked up a new IP in the 80.194.132.0/22 range. Latency is absolutely awful (double or worse, across the board), and my TBB graph is a car crash compared to before, even with fq-codel. I'm now going to have to play around with spoofing the WAN interface's MAC to get a new IP in a 'better' range. Has anyone else noticed this?
 
  • Like
Reactions: R3X
Rainmaker said:
Has anyone noticed their connection varies quite wildly depending on which IP address/range they get? For example, on 86.8.0.0/17 (iirc) I was pinging Cloudflare/1.1.1.1 around 12ms and had great latency (for VM) to almost everyone. Outliers were Quad9 (28ms) and Oracle's network (28-30ms).

Since I swapped back to VyOS, I picked up a new IP in the 80.194.132.0/22 range. Latency is absolutely awful (double or worse, across the board), and my TBB graph is a car crash compared to before, even with fq-codel. I'm now going to have to play around with spoofing the WAN interface's MAC to get a new IP in a 'better' range. Has anyone else noticed this?
Click to expand...
I'm on 80.192.24.0/22 and get ~16ms to London, ~6ms on OR FTTP depending on which peer I end up on.
 
ChrisD. said:
I'm on 80.192.24.0/22 and get ~16ms to London, ~6ms on OR FTTP depending on which peer I end up on.
Click to expand...
I think it's actually a local issue. I've just spoofed an old MAC and rebooted the Hub, and still:

Code: 
user@vyos:~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=53 time=36.9 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=53 time=33.7 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=53 time=34.7 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=53 time=34.8 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=53 time=26.7 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=53 time=25.8 ms
^C
--- 1.1.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 15ms
rtt min/avg/max/mdev = 25.791/32.103/36.876/4.242 ms

:(

Time to play the 'wait a week to speak to someone who tells you to restart the Hub and then disconnects you while transferring the call'. I think I'll just post on their forum and wait (and wait).
 
Rainmaker said:
Time to play the 'wait a week to speak to someone who tells you to restart the Hub and then disconnects you while transferring the call'. I think I'll just post on their forum and wait (and wait).
Click to expand...
Fingers crossed it's temporary.

Code: 
root@UDM-SE:~# ping -I 80.192.27.xx 9.9.9.9
PING 9.9.9.9 (9.9.9.9) from 80.192.27.22 : 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=57 time=18.0 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=57 time=18.5 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=57 time=17.6 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=57 time=18.4 ms
64 bytes from 9.9.9.9: icmp_seq=5 ttl=57 time=17.2 ms
64 bytes from 9.9.9.9: icmp_seq=6 ttl=57 time=18.0 ms
64 bytes from 9.9.9.9: icmp_seq=7 ttl=57 time=16.4 ms
64 bytes from 9.9.9.9: icmp_seq=8 ttl=57 time=16.7 ms
64 bytes from 9.9.9.9: icmp_seq=9 ttl=57 time=16.6 ms
64 bytes from 9.9.9.9: icmp_seq=10 ttl=57 time=16.4 ms

Not great tbh for an idle connection!

Via Aquiss:

Code: 
root@UDM-SE:~# ping 9.9.9.9
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=59 time=5.18 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=59 time=5.01 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=59 time=5.11 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=59 time=5.21 ms
64 bytes from 9.9.9.9: icmp_seq=5 ttl=59 time=5.09 ms
64 bytes from 9.9.9.9: icmp_seq=6 ttl=59 time=5.23 ms
 
ChrisD. said:
Fingers crossed it's temporary.

Code: 
root@UDM-SE:~# ping -I 80.192.27.xx 9.9.9.9
PING 9.9.9.9 (9.9.9.9) from 80.192.27.22 : 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=57 time=18.0 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=57 time=18.5 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=57 time=17.6 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=57 time=18.4 ms
64 bytes from 9.9.9.9: icmp_seq=5 ttl=57 time=17.2 ms
64 bytes from 9.9.9.9: icmp_seq=6 ttl=57 time=18.0 ms
64 bytes from 9.9.9.9: icmp_seq=7 ttl=57 time=16.4 ms
64 bytes from 9.9.9.9: icmp_seq=8 ttl=57 time=16.7 ms
64 bytes from 9.9.9.9: icmp_seq=9 ttl=57 time=16.6 ms
64 bytes from 9.9.9.9: icmp_seq=10 ttl=57 time=16.4 ms

Not great tbh for an idle connection!

Via Aquiss:

Code: 
root@UDM-SE:~# ping 9.9.9.9
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=59 time=5.18 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=59 time=5.01 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=59 time=5.11 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=59 time=5.21 ms
64 bytes from 9.9.9.9: icmp_seq=5 ttl=59 time=5.09 ms
64 bytes from 9.9.9.9: icmp_seq=6 ttl=59 time=5.23 ms
Click to expand...

Yeah I'm more used to seeing pings in the 12-18ms region, which is rubbish enough - but mid 30s? No thanks! I've honestly never seen an ISP with worse latency and routing, ever. I've just renewed WAN DHCP again, and got back to this:

Code: 
user@vyos:~$ ping 1.0.0.1
PING 1.0.0.1 (1.0.0.1) 56(84) bytes of data.
64 bytes from 1.0.0.1: icmp_seq=1 ttl=53 time=19.2 ms
64 bytes from 1.0.0.1: icmp_seq=2 ttl=53 time=16.7 ms
64 bytes from 1.0.0.1: icmp_seq=3 ttl=53 time=38.8 ms
64 bytes from 1.0.0.1: icmp_seq=4 ttl=53 time=19.3 ms
64 bytes from 1.0.0.1: icmp_seq=5 ttl=53 time=18.4 ms
64 bytes from 1.0.0.1: icmp_seq=6 ttl=53 time=18.7 ms
64 bytes from 1.0.0.1: icmp_seq=7 ttl=53 time=36.2 ms
64 bytes from 1.0.0.1: icmp_seq=8 ttl=53 time=18.9 ms
^C
--- 1.0.0.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 20ms
rtt min/avg/max/mdev = 16.736/23.283/38.750/8.250 ms

So, yeah. Better than before, but still swinging up to the 30s on an idle line. I'll give it a day and see how it goes, and disable and re-enable QoS just to be safe (in case the eth0 redirect to the dummy ifb0 interface is suddenly causing lag).

Your Aquiss latency is pure goals. Netomnia have updated me after 6 months of local roadworks to say they expect to be another year before going live, as they're experiencing 'delays in the design phase'. Openreach have been very busy around here lately, and the FTTP checker has said 'actively building in your exchange now' for weeks. They finally arrived in our street last week! We live on a 'square' around a school (four roads around the perimeter of the square school grounds).

We are the first/corner house in the bottom left of the square, and they literally, I **** you not, dug a whole half of the square last week and laid fibre - but didn't do our side. Still no signs of progress, and they have approval for more works next week... on the other side of the square again. Hurry. Up! :D I swear someone, somewhere, is messing with me. Shouldn't be long now, hopefully. I've already been chatting with the CEO of Aquiss, and discussed networking and an IP block allocation etc. I'll literally place an order the second it's live, and then add in Netomnia when they (finally) turn up. For now, I'm the definition of frustrated. My wife thinks I'm nuts. She's probably right!
 
Steampunk said:
Are you sure there isn't a letter in there somewhere telling you what to do? There nearly always is. I would read that as sending the text on your old SIM card, then swap to the new SIM.
Click to expand...

Nope, its just a text saying new sim should arrive in 1-3 days and to text SWAP to activate, reading it again it looks like I need to do that once the new sim is in the phone.
 
Further tweaking on QoS:

Code: 
traffic-policy {
    shaper qos-down {
        bandwidth 800mbit
        default {
            bandwidth 800mbit
            burst 15k
            queue-limit 1000
            queue-type fq-codel
        }
    }
    shaper qos-up {
        bandwidth 85mbit
        default {
            bandwidth 85mbit
            burst 15k
            queue-limit 1000
            queue-type fq-codel
        }
    }
}

Went to:

Code: 
@vyos:~$ ping 1.0.0.1
PING 1.0.0.1 (1.0.0.1) 56(84) bytes of data.
64 bytes from 1.0.0.1: icmp_seq=1 ttl=53 time=19.4 ms
64 bytes from 1.0.0.1: icmp_seq=2 ttl=53 time=19.6 ms
64 bytes from 1.0.0.1: icmp_seq=3 ttl=53 time=19.6 ms
64 bytes from 1.0.0.1: icmp_seq=4 ttl=53 time=21.7 ms
64 bytes from 1.0.0.1: icmp_seq=5 ttl=53 time=19.5 ms
^C
--- 1.0.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 12ms
rtt min/avg/max/mdev = 19.421/19.951/21.697/0.883 ms

vyos-qos-800-85.png


That'll have to do for now.
 
You must log in or register to reply here.
Back
Top Bottom