Weirdest super hub problem ever!

timberheadverde · 16-02-2011, 19:41

hey,
im gunna cut to the chase here, I cant go to 192.168.0.1 no matter what! not on wired not on wireless not on google chrome not on firefox! any ideas??

arcimedes · 16-02-2011, 20:03

Any error message?

philce · 16-02-2011, 20:05

I had this too, responds to pings but nothing on the web interface.

A reboot will fix.

qasdfdsaq · 16-02-2011, 20:06

Can you ping 192.168.0.1?

Is the device in the Superhub's trusted devices list?

timberheadverde · 16-02-2011, 20:11

Quote:

Originally Posted by philce

I had this too, responds to pings but nothing on the web interface.

A reboot will fix.

Thanks

for some reason i didnt try rebooting LOL thanks

Chrysalis · 17-02-2011, 02:35

I think I am on my 4th day uptime now, superhub will give soon probably

. Then another 20 reboots to get myself back on channel 7 upstream :p.

Nopanic · 17-02-2011, 05:52

Quote:

Originally Posted by jordyGFC

Thanks

for some reason i didnt try rebooting LOL thanks

How come you're not using talk talk ?

zekeisaszekedoes · 17-02-2011, 16:53

Quote:

Originally Posted by philce

I had this too, responds to pings but nothing on the web interface.

A reboot will fix temporarily.

Fixed that for you! Actually constantly rebooting the Super Hub seems the only way to keep it working consistantly. I'd recommend a reboot every six hours or so.

**Hugh** · 17-02-2011, 16:59

Strange - I haven't had a problem since I got mine a couple of weeks ago.

Not rebooted it yet (and it has another router (Buffalo Airstation) attached to it (for upstairs wifi).

Peter_ · 17-02-2011, 17:02

Quote:

Originally Posted by Hugh

Strange - I haven't had a problem since I got mine a couple of weeks ago.

Not rebooted it yet (and it has another router (Buffalo Airstation) attached to it (for upstairs wifi).

I find it strange that people think the is an issue if you use another router on a long ethernet cable, it is just so convenient.

RainmakerRaw · 17-02-2011, 18:32

Quote:

Originally Posted by Hugh

Strange - I haven't had a problem since I got mine a couple of weeks ago.

Not rebooted it yet (and it has another router (Buffalo Airstation) attached to it (for upstairs wifi).

I hadn't had this problem in the two months I've had my hub either... until yesterday. Ever since, I get a few minutes' web browsing and then the hub 'dies'. I can ping, even getting a response from 192.168.100.1 but I can't get any sites to load in the browser. The hub's WebUI doesn't load or respond either, it just times out.

I've reinstalled Windows 7 x64, tried from Linux, tried on my phone... same thing. I even uninstalled my firewall and AV suite and rebooted, but to no avail. It's just randomly started denying web access (or access to itself) on a whim. Sometimes a reboot of the network adapter fixes things, but mostly I have to reboot the "super" hub itself.

Frankly I'm getting bored of this now. I want to use the internet, not spend 12 hours a day investigating and "fixing" the super hub just to load Google.

If I ring the 0800 50 meg support line, will they reactivate my modem MAC so I can ditch the hub? The engineer didn't take it (the modem) away when we moved house, so I still have it sat here waiting to restore decent service!...

qasdfdsaq · 17-02-2011, 19:04

Dunno if this is the Superhub or something funny going on with VM's network - I've seen this happen once or twice on my standalone 50mb modem. That used to need rebooting several times a day but it's gone down to once a week now...

RainmakerRaw · 17-02-2011, 19:05

Quote:

Originally Posted by qasdfdsaq

Dunno if this is the Superhub or something funny going on with VM's network - I've seen this happen once or twice on my standalone 50mb modem. That used to need rebooting several times a day but it's gone down to once a week now...

If it was VM's network surely the hub would still respond by displaying its webUI on the LAN IP? That's locally served, nothing to do with VM's network on the WAN side.

qasdfdsaq · 17-02-2011, 19:16

You'd think that, but nearly everything the hub and/or modem does is controlled by the CMTS equipment at the other end. What devices it allows to connect, how they're allowed to connect, and what services/interfaces are available, what ports are open, etc. are all instructed from their end. They could probably turn off the web UI remotely if they wanted to, so I guess if the modem suddenly loses contact with the network it might panic and just get confused what it should be doing. Or it could be a totally unrelated bug.

Chrysalis · 17-02-2011, 19:49

I suspect VM can do things remotely, my ssh stopped working now on 192.168.100.1.

I did a backup of the superhub config and its in binary format haha, usually router's dump in ascii.

Also I think I am locked out of channel 7 upstream now it seems they reverted me back to 1 channel only, if I rang up and asked about it, I would likely be fed some bs about it cant be fixed etc. yet its all a remote configuration and how they choose to manage users out of choice.