Re: Poor VM Connection, strange TBB quality monitor etc..
 

Ok I've just switched the network drive over onto the test hub and off my hub.

Time for sleep. .. will see how it looks in the morning.

---------- Post added at 00:22 ---------- Previous post was at 00:09 ----------

[img]Download Failed (1)[/img]

Definitely the NAS drive then...

---------- Post added at 00:25 ---------- Previous post was at 00:22 ----------

Seagate something or other... my boyfriends so I'm not sure of the make or model.

I'll do some investigating tomorrow. I'm too tired to mess with it now, just happy we've solved the mystery!!

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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...

Re: Poor VM Connection, strange TBB quality monitor etc..
 

I wonder if you got someone snooping on your NAS?

Re: Poor VM Connection, strange TBB quality monitor etc..
 

Good move switching the NAS to the other SH. Lucky you've still got it.

Chrys has an interesting point that I thought of before but dismissed. The NAS shouldn't have any effect on the outgoings from your SH unless it's being accessed externally, like your wi-fi has been hacked. That can be checked on the SH or router when the TBB goes strange by examining the DHCP log - which MAC addresses are accessing the system; they should count up to the number of accountable devices.

Another thing you can try is turn wireless off in the middle of an episode to narrow the field down further.

But your experiment to switch the NAS onto the other SH is capital.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

exactly, if its affecting external latency it suggests its been accessed.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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
http://www.thinkbroadband.com/ping/s...09-12-2012.png

Own Hub
http://www.thinkbroadband.com/ping/s...09-12-2012.png

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... :-/

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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!

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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
http://www.thinkbroadband.com/ping/s...10-12-2012.png

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

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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?

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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

Re: Poor VM Connection, strange TBB quality monitor etc..
 

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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! :-)

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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 ;)

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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

Re: Poor VM Connection, strange TBB quality monitor etc..
 

Someone fancy explaining Wireshark bit by bit to the OP?

Re: Poor VM Connection, strange TBB quality monitor etc..
 

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?

Re: Poor VM Connection, strange TBB quality monitor etc..
 

Definitely getting a bit too deep for me! Although I do love learning and having a challenge to face ;-)

The PT took the test hub away last night, so i only have mine to go on now.

He said to ignore the think broadband graphs because the latency caused by the NAS drive shouldnt affect our connection... I don't feel overly comfortable doing that if I'm honest as its my way of knowing what's going on. But the NAS drive needs to be investigated.

I won't let this one beat me!

Re: Poor VM Connection, strange TBB quality monitor etc..
 

I'm also disappointed by that answer as it stands. I mean, he's right that the NAS shouldn't have any network impact. But if we've proved that it has network impact, and on the face of it it seems so, then we need to get to the bottom of that.

Also, rewinding a bit, it's the TBB graph that brought the PT in, wasn't it? And it needs explaining. As I said, next step is tpo turn off all SH wireless functions with thr NAS attached and see what that produces.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

Wireshark will tell you what the NAS is sending, and therefore what is causing the latency problem.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

You'd have to have the NAS mapped onto the PC (which we're keeping off the network to eliminate it from what's going on). But, forgive my ignorance, if the NAS on its own is generating WAN traffic or being called from outside, then where does Wireshark come into it? Clearly I don't know enough about Wireshark.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

You can run Wireshark in promiscuous mode so it captures all network traffic on your LAN that is presented to the PC's network card. However,in this instance, I'm not convinced it would work as the traffic will be unicast and effectively 'filtered' by switch* function of the SH.

*Assuming the 4 LAN ports are part of a switch and not a hub.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

Thanks. All these years of Wireshark and never reached that!

Re: Poor VM Connection, strange TBB quality monitor etc..
 

Promiscuous mode works really well if you've got a network switch that supports port mirroring... :)

---------- Post added at 20:30 ---------- Previous post was at 20:27 ----------

Remove the default gateway from the NAS - You'll still be able to access it locally but it won't know about the WAN...

Not sure you've mentioned yet (and apologies if you have) the make and model?

Re: Poor VM Connection, strange TBB quality monitor etc..
 

That's why I said get a proper router or connect it via a PC with two network cards.

Re: Poor VM Connection, strange TBB quality monitor etc..
 

.... and as said, it's getting too complex for the OP. We should stick to belt and braces.