50M : Poor VM Connection, strange TBB quality monitor etc..

[Rashboots]

OK.... a lot to take in here so sorry if I missed out anything from anyone's posts!

This is my graphs at the minute (ignore the packetloss, something tripped the electric!):

Test Hub


Own Hub


There doesn't appear to be any craziness on the test hub at the minute, but it would always take a while to build up anyway, it would never just start going crazy after it's been plugged in.

At the moment, bar my less than perfect graph, everything seems OK. So I'll leave it until it goes crazy again.

We only have 3 things connected to our hub at the minute, boyfriends laptop (wired), my laptop (wireless) and boyfriends ipad (wireless)

The test hub only had the NAS drive connected (wired).

The thought of someone trying to or having access to the NAS drive scares me... :-/

[Sephiroth]

So.overnight, nothing was connected to your SH? If not, we've not really moved forward. if so, there's the difference for the PT to bite on.

[Rashboots]

No Everything was disconnected, there was nothing connected via wifi either.

The only thing that was connected to ANY superhub was the seagate NAS drive which i'd unplugged from my SH to the test SH, as you can see from the graphs.

I'm trying to google my issue to see if anyone else has had any problems with that particular NAS drive and virgin, or any other router/modem... I can't find anything though. Frustrating!

[Sephiroth]

The test hub shows no signs of anything unusual with the NAS connected.

So, you've got a nothing'd SH (yours) with green sections perurbations (which shouldn't happen). The test SH is behaving normally.

I ake it that the channels remain the same as before on both SHs?

From your SH stats, it seems that the SH is in router mode. Are the settings identical as between yours and the test SH? Firewall levels? All the optional settings?

As I said, on the face of it, something for the PT to bite on and he'll be scratching his head too.

[Rashboots]

Sorry I never replied to this last night, had loads of uni work to get done and needed no distractions

The test SH is now behaving in the same manner as my SH did when the NAs drive was connected to it... WINNER (graphs below)! So it's definitely the NAS drive... now to pinpoint what exactly is causing the high external latency... And again, it's around the 6am mark that it starts to happen.

I can't log on remotely to the SH to see what mac addresses are linked to that SH, I will have to do this tonight after I've got home.

What would you, Seph, or anyone else recommend is my next step into looking at what's causing the NAS drive to behave so bizarrely? As I mentioned before, googling my issue brings little back in the way of my problem, but I don't know how to phrase my issue properly so it could be out there, I'm just searching for the wrong thing!

Test SH graph


Own SH graph
[img]Download Failed (1)[/img]

[Sephiroth]

First step is to look in the DHCP and account for all the MAC addresses shown as connected. If only the NAS drive is connected to that SH, look at the wirelss section and see if anything is connected there.

In any case, turn wireless off on the test SH and see what that does. Bit by bit, we'll get there.

[Rashboots]

I'll do this tonight, as soon as I get home

What if nothing appears to be connected that shouldn't be? We do have the FTP access option selected, is it worth de-selecting this?

[Chrysalis]

if you dont need it yes, always turn everything off unless needed.

[qasdfdsaq]

Originally Posted by qasdfdsaq

Connect it to a proper router and monitor the traffic coming in and out of it. It could either be lots of traffic coming from the device, or certain types of traffic confusing the Shrub.

I only need to send one packet with the right data in it to make my Shrub baulk and cut off internet access for everybody...

[Rashboots]

Qas.. do you mean put the NAS drive on it's own router or use a router instead of the hub entirely?

Sorry I missed your post! :-)

[qasdfdsaq]

Either. Or connect it to a PC with two network cards. In any case what's important is the traffic between the NAS and the Superhub. You'll need to monitor it one way or another to determine what is causing the Superhub to bork, whether it be the quantity or the content of the traffic.

[Qtx]

If that packet is internet-routable, should report it as a bug to VM in case someone else figures it out as a denial of service attack. Found certain custom UDP packets can cause my VM router to fall over but its not a SH.

At leasts its not something as simple as ping -l 65510 superhub

[Sephiroth]

I think this is getting too deep for the OP. The bit by bit approach should get to the bottom of this.

[qasdfdsaq]

Someone fancy explaining Wireshark bit by bit to the OP?

[Sephiroth]

What will wireshark do if it's only the NAS drive that's connected and accounting for the traffic? Or was that a humourous suggestion, Qas?