Re: Comcom/Samknows broadband testing from a different perspective

Dylan Hall <[email protected]> Fri, 28 Sep 2018 11:11:37 +1200
Newsgroups gmane.org.operators.nznog
Message-ID <CAFJtFYka_G0L1S1Y6Wtm46JiNSY0zTdAcha6b9FiFGXRFYGYyQ@mail.gmail.com>
Do you know which node (AKL vs WLG) you're talking to or it's IP address?

If not, can you flick me your address off list and I'll dig through the
flow records and try and figure it out.

The reason I ask is I'd like to see a traceroute to/from your address to
see the path the traffic is taking.

We have 10 Gbps ports on APE/AKL-IX, but only 1 Gbps on WIX/CHIX. Since the
testing started we've started seeing discards on our WIX port during the
evening which I'm pretty sure is being driven by the testing traffic. We've
ordered an upgrade to 10 Gbps which I expect to get live in the next couple
of weeks. This could explain the download test struggling to get close to 1
Gbps, but I think it less likely to impact the upload test.

Thanks,

Dylan


On Fri, 28 Sep 2018 at 08:49, Jason Orchard <[email protected]>
wrote:

> Hi
>
> Since putting the device on the Enable Network, I’m actually not overall
> happy with the results I'm seeing.
>
> There is an inconsistency with the Download/Upload Speed, Latency and
> Jitter.
>
> When testing using another Testing service such as Speedtest.net and
> Fast.com, Iperf  are consistently report my connection speed as 950Mb/s
> Downstream and 500Mb/s upstream.
>
> Samknows is reporting this My peak connection Speed for download of
> 742Mbp/s and upload 429Mbps, but these results are not consistent when I
> compare other speedtest services.
>
>
>
> According to the data provided from Samknows user analytics, they are
> testing the download speed on the hour between 6 pm and 11 am daily and one
> sample at 5 am.
> These times represent Enable network peak and off periods for traffic.
>
>
>
>    - The graph below are taken over a 7days period, sampling every 30
>       seconds at a bit per second.
>       - Have another member of NZNOC got similar testing results to mine
>       - What I can’t answer is how the data in the graphs below is
>       represented by Samknows.
>
>
>
> Note:
>
> The Samknows device is the only (Connection) plugged into this GPON
> interface.
>
> There is other user traffic been generated on this port other than
> samknows device.
>
>
>
> [image: cid:[email protected]]
>
>
>
>
>
> *Jason Orchard*
>
> Senior Network Engineer | Enable Networks Limited
>
> DDI +64 3 741 5283
>
> M    +64 27 666 8468
>
> www.enable.net.nz
>
>
>
> [image: cid:[email protected]]
>
>
>
> *From:* [email protected] <[email protected]>
> *On Behalf Of *[email protected]
> *Sent:* Thursday, 27 September 2018 5:12 PM
> *To:* Peter Lambrechtsen <[email protected]>
> *Cc:* NZNOG <[email protected]>; brian.cole-r/[email protected]
> *Subject:* Re: [nznog] Comcom/Samknows broadband testing from a different
> perspective
>
>
>
> OpenWRT/LEDE binary, Just shell on.. opkg update, -i what you need...,
> netstat -antop | grep EST this will surprise you, dest will surprise you
> more then I  put in the green wheely.  On the WAN link you may see lots of
> src privates indicating typical dinky rtr/fw nat not coping similarly
> actual/true $paid for bandwidth at src (home) = rubbish + legit flows.
> rubbish flows (in/out) of breaks packet concurrency increasing delays and
> maxin out (netflix/gaming stream) PDVs on clients - recommend filter|block
> upstream of router will lead to a huge improvement in media quality and
> performance of your home router.
>
> good luck - regards brian
> ---------------------------- Original Message ----------------------------
> Subject: Re: [nznog] Comcom/Samknows broadband testing from a different
> perspective
> From: "Peter Lambrechtsen" <[email protected]>
> Date: Thu, September 27, 2018 4:37 pm
> To: brian.cole-r/[email protected]
> Cc: "NZNOG" <[email protected]>
> --------------------------------------------------------------------------
>
> > There is a Geekzone thread that I kicked off when I attended the Commerce
> > Commission presentation about Samknows and got to meet Sam.
> >
> > https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=237852
> >
> > I've done a bit of analysis on the traffic but haven't dug too deep yet
> as
> > I didn't want to bust open the box and try and reverse engineer their
> > OpenWRT build.
> >
> > Happy to put anyone in touch with the guys I have dealt with directly
> from
> > the Comcom and Samknows too.
> >
> > On Thu, Sep 27, 2018 at 12:59 PM Brian Cole <brian.cole-r/[email protected]>
> > wrote:
> >
> >> Acknowledged with thanks,
> >>
> >> Brian
> >>
> >> On Thu, 27 Sep 2018 at 12:58 PM, Nathan Ward <[email protected]> wrote:
> >>
> >>> Hi Brian,
> >>>
> >>> You should call their support if you think there’s something going on
> >>> that’s impacting your connection.
> >>>
> >>> They will detect if your connection is in use and doing more than (I
> >>> think) 64kbit/s in the last 30s or something, and won’t run the tests.
> >>>
> >>> They have some clever stuff to detect if your wifi is in use, without
> >>> being connected to your network and without being your AP. Perhaps
> that’s
> >>> playing up?
> >>>
> >>> Pretty sure it’s publicly documented, check out the links in that
> >>> original post and if not we can dig up some other stuff I’m sure.
> >>>
> >>> On 27/09/2018, at 11:38 AM, Brian Cole <brian.cole-r/[email protected]>
> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Longtime listener; first time caller.
> >>>
> >>> I signed up to SamKnows (partly out of curiosity and partly so I can
> have
> >>> hard data about my connection that I pay for) at home.
> >>>
> >>> Over the last week my connection has gone from slightly adequate with
> the
> >>> occasional drop out to a slow connection with regular drop outs.
> >>>
> >>> Netflix and YouTube are stuttering, video games drop connection, and
> >>> websites hang at random times.
> >>>
> >>> I can't help but think that the email shared by Dylan sheds some light
> on
> >>> why that maybe.
> >>>
> >>> This programme won't be terribly successful if everyone gets sick of
> >>> having a terrible connection during peak hours and shuts the white box
> >>> down.
> >>>
> >>> Pretty frustrating.
> >>>
> >>> Brian
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> *Brian Cole* */** Research Projects Developer*
> >>> *Research & Enterprise **/** Research Office **/** University of
> >>> Waikato*
> >>> *Private Bag 3105* */* *Hamilton 3240* */*
> >>> *New Zealand**www.waikato.ac.nz* <http://www.waikato.ac.nz/> */*
> >>> *mob + 64 21 049 9183**email brian.cole-r/[email protected]
> >>> <brian.cole-r/[email protected]> *
> >>>
> >>> _______________________________________________
> >>>
> >>>
> >>> NZNOG mailing list
> >>> [email protected]
> >>> https://list.waikato.ac.nz/mailman/listinfo/nznog
> >>>
> >>>
> >>> --
> >> Please excuse any brevity, spelling mistakes, or errors in this email
> due
> >> to being sent from a mobile device.
> >> _______________________________________________
> >> NZNOG mailing list
> >> [email protected]
> >> https://list.waikato.ac.nz/mailman/listinfo/nznog
> >>
> > _______________________________________________
> > NZNOG mailing list
> > [email protected]
> > https://list.waikato.ac.nz/mailman/listinfo/nznog
> >
>
> The information contained in this message and/or attachments is intended
> only for the person or entity to which it is addressed and may contain
> confidential and/or privileged material. Any review, re-transmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the sender and
> delete the material from any system and destroy any copies
>
> Save a tree. Please think before printing this email.
> _______________________________________________
> NZNOG mailing list
> [email protected]
> https://list.waikato.ac.nz/mailman/listinfo/nznog
>

_______________________________________________
NZNOG mailing list
[email protected]
https://list.waikato.ac.nz/mailman/listinfo/nznog
image001.jpg (image/jpeg, 20.3 KB) - not displayed
image002.png (image/png, 124.7 KB) - not displayed
image001.jpg (image/jpeg, 20.3 KB) - not displayed