Jump to content

Issues trying to put Virgin Superhub 2 into modem mode


Recommended Posts

Hi guys

 

So I was reading this thead:

 

http://forum.netduma.com/topic/2715-how-to-set-up-r1-as-primary-router-with-virgin-super-hub-2/

 

And realized that although I had my R1 set up and working fine, I wasn’t using the recommended setup, so I followed the instructions in the thread but I’m having some problems.  I got as far as step 7in the guide when I hit trouble.

 

Basically, once I’ve put my Superhub 2 into modem mode and connected up the R1 I get no connectivity whatsoever.  My devices see the R1’s wifi signal and can connect to it, but when they do there’s no connectivity.

 

How long should it take after powering up the Superhub 2 and the R1 before I get connectivity ? In the tutorial it just says “after some time”, but I left it for a good ten minutes and it didn’t seem to make any difference ?  Will the fact that I’ve had the R1 up and running previously be causing issues ?

 

I also tried rebooting (not resetting) the superhub but it doesn’t seem to make any difference.  Anyone else using a Superhub 2 had any similar problems ? 

For the time being I’ve gone back to using the wifi signal from the superhub 2 so I can chat on here and understand what I’m doing wrong.

 

Many thanks in advance !

 

*prepares to be taken to network school*

 

Link to comment
Share on other sites

When I had virgin, I had the same setup, SH Netduma devices, if I remember rightly I turned everything off, connected the Duma to the SH (wired) and the turned everything on again left it for 5 mins and the booted it up and it worked (surprisingly)

Link to comment
Share on other sites

When I had virgin, I had the same setup, SH Netduma devices, if I remember rightly I turned everything off, connected the Duma to the SH (wired) and the turned everything on again left it for 5 mins and the booted it up and it worked (surprisingly)

 

LOL @ "surprisingly".  There seems to be a pretty dim opinion of Virgin's kit on here, is there a reason why ?  I've never really had any issues with them up until now ?

 

Regarding the modem mode though maybe I've just been too impatient in trying to get it working again.  I'd plugged the hub in first and given it a minute or two before connecting the R1, maybe I need to power them both up at the same time  :unsure: ?

Link to comment
Share on other sites

LOL @ "surprisingly".  There seems to be a pretty dim opinion of Virgin's kit on here, is there a reason why ?  I've never really had any issues with them up until now ?

 

Regarding the modem mode though maybe I've just been too impatient in trying to get it working again.  I'd plugged the hub in first and given it a minute or two before connecting the R1, maybe I need to power them both up at the same time  :unsure: ?

I really had no issues with Virgin other than their traffic management, and extremely bad jitter, which was BAD at times, PA assist looked like a politician on a lie detector. It was a while ago when I had the SH connected up as I had an ASUS with the SH in modem mode and had no problems when I set up the Duma, I think I booted the SH and then switched on the Duma a few minutes later, sorry I can't be more specific, but the mists of time and all that ......... :)

Link to comment
Share on other sites

My only issue with Virgin is the jitter and spikes on my line, the wifi is a bit pants on the Superhub but I expect that from a isp provided router.

 

I found that I had to set it link everything up and then turn it on in stages...

Superhub first (give it 5 mins to settle), then the Netduma (again give it a few), then my Asus Router (few mins), then the devices.

 

You may need to connect to the Duma via ethernet (with your laptop) if you're having trouble though - then you can go in and tinker with the settings (to make sure it can recognise the superhub behind it etc).

 

Or set it up with the Superhub in router mode and everything trailing behind it and then switch it modem mode after you're all good (and then switch it all of and restart it all again in stages).

 

Also, if memory serves me correctly, the ethernet port on the Superhub are counter-intuitive...

As in, once you put it in mode mode only one ethernet port works and it was the opposite end to the one I expected so you may have the cable (linking from the hub to the Duma) in the wrong hole.

 

*That's what she said.

 

 

And when the superhub goes into modem mode the ip changes I believe, definitely internal (192.168.100.1 I believe) and possibly external IP too - not sure if that would cause a problem but worth a punt.

 

 

I'm just off out but I'll check in on this thread later and see how you're doing...

Link to comment
Share on other sites

Thanks for the replies guys, if I get the time this evening I'm going to have another bash at getting this working, I'll report back with an update.....

 

.....unless of course I screw it up and can't get online, mwa ha ha

Link to comment
Share on other sites

Hi guys, I had another stab at this this evening and seem to have been able to get it working now, not sure what exactly I did differently (if anything) but I've been able to get the SuperHub into modem mode and I'm now connecting through the R1 so all is good in that respect.

 

I'm having a problem now though connecting to my VPN so might need to give Crossy a nudge again  :(

Link to comment
Share on other sites

Hi guys, I had another stab at this this evening and seem to have been able to get it working now, not sure what exactly I did differently (if anything) but I've been able to get the SuperHub into modem mode and I'm now connecting through the R1 so all is good in that respect.

 

I'm having a problem now though connecting to my VPN so might need to give Crossy a nudge again  :(

 

You didn't do anything differently, they just needed a few mins to 'forget' about one another I expect - your routers were in love.

 

VPN is beyond me I'm afraid...

Link to comment
Share on other sites

You didn't do anything differently, they just needed a few mins to 'forget' about one another I expect - your routers were in love.

 

VPN is beyond me I'm afraid...

 

:lol:

Link to comment
Share on other sites

Great to hear you're online! Post up with what VPN you're using, you'll need the config files from them.

 

I'm using iPredator, Crossy had helped me to sort out getting things working here:

 

http://forum.netduma.com/topic/15514-setting-up-the-r1-to-use-my-ipredator-vpn-account/

 

But unfortunately I'm having issues applying the VPN now, I keep getting this message:

 

I've also had a problem with devices like my phone being connected to the R1 successfully in the evening, then the following morning finding that connectivity to the router has been lost.  When I try to reconnect my phone to the R1 wifi I'll get a message saying the password is incorrect even though it's not ?  Strange.

post-8378-0-30906500-1463651955_thumb.png

Link to comment
Share on other sites

  • Administrators

For VPN

 

Firstly please try disable your anti-virus, adware or firewall and see if the error goes away.

If the error does not go away and you see failed try again in 5 s connection timed out in the log then you are trying to connect to a server that is down. Please untick enable click apply. Reboot the router and try connect to a different server please.

 

Is this with or without the VPN applied? Disable wifi workaround in settings > miscellaneous. Also set a static IP to your phone in DHCP lease.

Link to comment
Share on other sites

For VPN

 

Firstly please try disable your anti-virus, adware or firewall and see if the error goes away.

If the error does not go away and you see failed try again in 5 s connection timed out in the log then you are trying to connect to a server that is down. Please untick enable click apply. Reboot the router and try connect to a different server please.

 

Is this with or without the VPN applied? Disable wifi workaround in settings > miscellaneous. Also set a static IP to your phone in DHCP lease.

 

I'll work through these suggestions this evening and report back.

Link to comment
Share on other sites

Ok so I'm having a bit of an experiment now.  I haven't fiddled with the VPN just yet, but to answer your question the issues I was having were without the VPN being applied. 

 

Checked in settings > misc and wifi workaround was already disabled.  I’ve used settings > DHCP lease to assign a static IP address to all my devices on the network. 

 

I also used the Mac’s wifi scanner to work out which was the best wifi channel and updated that too.  Saved a copy of my profile in case I need to reboot the router.

Link to comment
Share on other sites

Sooo..... I seem to be getting great connectivity having tweaked the wifi channel and applying static IPs, but.....

 

Still getting failed to communicate with the router.  Can’t see anything in the log about trying again after 5 seconds.  Is it safe to post the log text here ?

 

I did try disabling firewall and antivirus on my Mac but it didn't seem to make any difference.

 

Sorry but I don’t know how to try to connect to a different server, presumably it means changing something in the config which I understand but I’m not quite techie enough to know which bit needs changing L

Link to comment
Share on other sites

  • Administrators

Good to hear that issue seems to be resolved. Give the router a reboot and try reconnecting. You'd switch out the top 3 servers at the top with others they provide but just try a standard reboot from misc first.

Link to comment
Share on other sites

OK, so I've tried rebooting the router through Settings > Miscellaneous and I'm getting a "Failed to communicate with the router" error message still ?

 

Also it seems to lock up the browser page that I'm using to view the Netduma admin  :huh:

 

Any suggestions ?

Link to comment
Share on other sites

  • Administrators

Okay so could be the server itself that is down. Have a look through the config files available for an alternative and replace it at the top of your current config. 

 

How do you mean lock up? If you close the tab and open a new interface page does it behave as expected?

Link to comment
Share on other sites

I've just had a word with some of the guys on iPredator's IRC support and they suggested using port 443 which I've done, but unfortunately I'm still having issues, basically I'm just getting the Failed to communicate with router error message again.

 

About the page locking up, it just seems to become unresponsive and run very slowly, it works eventually though.

Link to comment
Share on other sites

  • Administrators

So you've changed to that port in the config itself? Can you post the error log please & config you're using.

 

For page locking up make sure you're on the default theme and using Chrome.

Link to comment
Share on other sites

So you've changed to that port in the config itself? Can you post the error log please & config you're using.

 

For page locking up make sure you're on the default theme and using Chrome.

 

OK, i made a short video so you can see what sort of difficulties I'm having:

 

https://www.youtube.com/watch?v=wPkmjI2dY8k&feature=youtu.be

 

You'll see what I mean now about the page becoming unresponsive.  Because it's crapping out it's not letting me copy and paste the text from the error log, nor does it seem to be refreshing the error log with the details of my most recent attempt to apply the VPN with port 443 configured.  That being said, this is the config I'm using (again for some reason it keeps defaulting back to port 1194):

 

# VER: 0.25
client
dev tun0
proto udp
remote nat.openvpn.ipredator.se 1194
remote nat.openvpn.ipredator.me 1194
remote nat.openvpn.ipredator.es 1194
resolv-retry infinite
nobind
 
auth-user-pass /etc/openvpn/IPredator.auth
auth-retry nointeract
 
ca [inline]
 
tls-client
tls-auth [inline]
ns-cert-type server
remote-cert-tls server
remote-cert-ku 0x00e0 
 
keepalive 10 30
cipher AES-256-CBC
persist-key
comp-lzo
tun-mtu 1500
mssfix 1200
passtos
verb 3
replay-window 512 60
mute-replay-warnings
ifconfig-nowarn
 
# Disable this if your system does not support it!
tls-version-min 1.2
 
<ca>
-----BEGIN CERTIFICATE-----
MIIFJzCCBA+gAwIBAgIJAKee4ZMMpvhzMA0GCSqGSIb3DQEBBQUAMIG9MQswCQYD
VQQGEwJTRTESMBAGA1UECBMJQnJ5Z2dsYW5kMQ8wDQYDVQQHEwZPZWxkYWwxJDAi
BgNVBAoTG1JveWFsIFN3ZWRpc2ggQmVlciBTcXVhZHJvbjESMBAGA1UECxMJSW50
ZXJuZXR6MScwJQYDVQQDEx5Sb3lhbCBTd2VkaXNoIEJlZXIgU3F1YWRyb24gQ0Ex
JjAkBgkqhkiG9w0BCQEWF2hvc3RtYXN0ZXJAaXByZWRhdG9yLnNlMB4XDTEyMDgw
NDIxMTAyNVoXDTIyMDgwMjIxMTAyNVowgb0xCzAJBgNVBAYTAlNFMRIwEAYDVQQI
EwlCcnlnZ2xhbmQxDzANBgNVBAcTBk9lbGRhbDEkMCIGA1UEChMbUm95YWwgU3dl
ZGlzaCBCZWVyIFNxdWFkcm9uMRIwEAYDVQQLEwlJbnRlcm5ldHoxJzAlBgNVBAMT
HlJveWFsIFN3ZWRpc2ggQmVlciBTcXVhZHJvbiBDQTEmMCQGCSqGSIb3DQEJARYX
aG9zdG1hc3RlckBpcHJlZGF0b3Iuc2UwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw
ggEKAoIBAQCp5M22fZtwtIh6Mu9IwC3N2tEFqyNTEP1YyXasjf+7VNISqSpFy+tf
DsHAkiE9Wbv8KFM9bOoVK1JjdDsetxArm/RNsUWm/SNyVbmY+5ezX/n95S7gQdMi
bA74/ID2+KsCXUY+HNNUQqFpyK67S09A6r0ZwPNUDbLgGnmCZRMDBPCHCbiK6e68
d75v6f/0nY4AyAAAyqwAELIAn6sy4rzoPbalxcO33eW0fUG/ir41qqo8BQrWKyEd
Q9gy8tGEqbLQ+B30bhIvBh10YtWq6fgFZJzWP6K8bBJGRvioFOyQHCaVH98UjwOm
/AqMTg7LwNrpRJGcKLHzUf3gNSHQGHfzAgMBAAGjggEmMIIBIjAdBgNVHQ4EFgQU
pRqJxaYdvv3XGEECUqj7DJJ8ptswgfIGA1UdIwSB6jCB54AUpRqJxaYdvv3XGEEC
Uqj7DJJ8ptuhgcOkgcAwgb0xCzAJBgNVBAYTAlNFMRIwEAYDVQQIEwlCcnlnZ2xh
bmQxDzANBgNVBAcTBk9lbGRhbDEkMCIGA1UEChMbUm95YWwgU3dlZGlzaCBCZWVy
IFNxdWFkcm9uMRIwEAYDVQQLEwlJbnRlcm5ldHoxJzAlBgNVBAMTHlJveWFsIFN3
ZWRpc2ggQmVlciBTcXVhZHJvbiBDQTEmMCQGCSqGSIb3DQEJARYXaG9zdG1hc3Rl
ckBpcHJlZGF0b3Iuc2WCCQCnnuGTDKb4czAMBgNVHRMEBTADAQH/MA0GCSqGSIb3
DQEBBQUAA4IBAQB8nxZJaTvMMoSG47jD2w31zt9o6nSx8XJKop/0rMMHKBe1QBUw
/n3clGwYxBW8mTnrXHhmJkwJzA0Vh525+dkF28E0I+DSigKUXEewIZtKjADYSxaG
M+4272enbJ86JeXUhN8oF9TT+LKgMBgtt9yX5o63Ek6QOKwovH5kemDOVJmwae9p
tXQEWfCPDFMc7VfSxS4BDBVinRWeMWZs+2AWeWu2CMsjcx7+B+kPbBCzfANanFDD
CZEQON4pEpfK2XErhOudKEJGCl7psH+9Ex//pqsUS43nVN/4sqydiwbi+wQuUI3P
BYtvqPnWdjIdf2ayAQQCWliAx9+P03vbef6y
-----END CERTIFICATE-----
</ca>
 
<tls-auth>
-----BEGIN OpenVPN Static key V1-----
03f7b2056b9dc67aa79c59852cb6b35a
a3a15c0ca685ca76890bbb169e298837
2bdc904116f5b66d8f7b3ea6a5ff05cb
fc4f4889d702d394710e48164b28094f
a0e1c7888d471da39918d747ca4bbc2f
285f676763b5b8bee9bc08e4b5a69315
d2ff6b9f4b38e6e2e8bcd05c8ac33c5c
56c4c44dbca35041b67e2374788f8977
7ad4ab8e06cd59e7164200dfbadb942a
351a4171ab212c23bee1920120f81205
efabaa5e34619f13adbe58b6c83536d3
0d34e6466feabdd0e63b39ad9bb1116b
37fafb95759ab9a15572842f70e7cba9
69700972a01b21229eba487745c091dd
5cd6d77bdc7a54a756ffe440789fd39e
97aa9abe2749732b7262f82e4097bee3
-----END OpenVPN Static key V1-----
</tls-auth>
 
Also I made sure I was using the default theme before recording the video.
Link to comment
Share on other sites

Hi Fraser, so after a bit of tinkering yesterday I've been able to get the VPN working again.  I'd saved a profile so tried reapplying that and it appeared to work but for some reason it hasn't saved the DHCP settings so I'll need to reapply these.  For now all seems to be good, I'll shout if I have any issues though  :)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Guest
This topic is now closed to further replies.
×
×
  • Create New...