on 29-01-2020 16:25
Prior to taking part in 1gb trial I had an Asus rt ac68u which I used instead of hub 3. During the trial I tested my hub 4 with Asus and all good but for the sake of the trial I kept the hub 4 going.
Today I decided to switch back to Asus with usual set up with Hub 4 in modem mode. All was good but I was only getting 250mb download so I swapped my cat 5e for the virgin cat 6 supplied and this is when it all went wrong.
I could not get my Asus to connect.
1. I factory reset both hubs and started all over again still no connection.
2. Called second line faults 3 times and walked through re setting hub 4 but no luck and was told my third party router was the issue.
Here is what I have discovered.
when in modem mode and all set up correctly my Asus can not detect connection from hub 4 (port 4) . If I plug in to the hub 4 directly from desktop I can access the hub 4 but no internet. if I reboot I get internet.
Occasionally the hub 4 says no RF connection (no idea what this means) on status page and when in modem mode I can also access it via 192.168.0.1 which should take me to the Asus. When it does this I can access internet whilst plugged in to Asus as if its just passing through.
I have now factory reset the hub 4 and changed password and when I try and access the hub it tells me password is wrong. I try the password on the base and that is wrong also???
I feel the thing is so glitchy
It all worked previously and my set up has not changed.
Answered! Go to Answer
on 29-01-2020 16:58
It might be worth using the instructions for connecting a router to the Hub 3 --------------->
Power off the Hub3.
Then, set up your own router with the WAN port set to be in DHCP mode. Make sure it’s fully initialised (leave 5 min) and then put in the Cat 5E/6 cable to the Hub 3.
Now power up the VM hub and you should get a connection. This order only needs to be done the first time you connect your own router to the VM hub.
on 29-01-2020 17:32
I have seen other reports of the Hub4 being able to be accessed when in modem mode on 192.168.0.1. What I should do is change your own router to be on 192.168.0.254. This would stop two devices having the same IP address on the sub net which may be causing your problem.
on 29-01-2020 19:27
on 29-01-2020 16:58
It might be worth using the instructions for connecting a router to the Hub 3 --------------->
Power off the Hub3.
Then, set up your own router with the WAN port set to be in DHCP mode. Make sure it’s fully initialised (leave 5 min) and then put in the Cat 5E/6 cable to the Hub 3.
Now power up the VM hub and you should get a connection. This order only needs to be done the first time you connect your own router to the VM hub.
on 29-01-2020 17:32
I have seen other reports of the Hub4 being able to be accessed when in modem mode on 192.168.0.1. What I should do is change your own router to be on 192.168.0.254. This would stop two devices having the same IP address on the sub net which may be causing your problem.
on 29-01-2020 17:34
Hi,
I assume I put the Hub 4 into modem mode before powering down. I have done this already but to be fair I did not wait for the Asus router to settle before powering up Hub 4.
on 29-01-2020 18:22
@GoodSamaritan wrote:I have now factory reset the hub 4 and changed password and when I try and access the hub it tells me password is wrong. I try the password on the base and that is wrong also???
So if you have done that and the hub is not letting you login how can you change to modem mode now?
on 29-01-2020 18:52
I have reset it again. I was highlighting how unpredictable the hub is.
on 29-01-2020 19:27
on 30-01-2020 10:01
So I have tried all of above and still no connection. Different cables no luck.
on 30-01-2020 10:10
Feel free to contribute to my post here:
https://community.virginmedia.com/t5/Networking-and-WiFi/Hub-4-Bugs-Glitches/m-p/4135960
on 24-07-2020 12:36
I have similar problem.
As soon as I switch superhub 4 into router mode, router can't see any connected ethernet cables. When I switch it back as default then router can see all attached devices.
I think it's software issue and again Virgin fu..ed it up.