Upload GUI confusing

Comments

3 comments

  • Avatar
    Support Team

    @Bertrand

    Yes. You are right about the definition of upload/download. There are 2 pairs of concepts here.

    Upload means data sent from the device, download means data received by the device. 

    Inbound means connection established from the external, outbound means connection established from the internal. 

    So, for outbound traffic, the correct message should be "<distant IP> accessed device x", and the data direction can be either upload or download. We should be able to correct this. 

     

    When you are looking into the traffic detail, which is more important to you? The direction of data (upload/download), or the direction of the connection (inbound/outbound)? 

    0
    Comment actions Permalink
  • Avatar
    Bertrand Florat

    "So, for outbound traffic, the correct message should be "<distant IP> accessed device x", and the data direction can be either upload or download. We should be able to correct this. "

    Really ? you just said "outbound means connection established from the internal. " so the correct message from outbound is 'device x accessed <distant ip>'  like done currently, isn't it ? It is for the inbound case that you should change the label or I have still not understood what your mean ?

    "When you are looking into the traffic detail, which is more important to you? The direction of data (upload/download), or the direction of the connection (inbound/outbound)?"

    For me, the inbound/outbound concept is much more important than the 'upload/download" one but I have no limit and I own an excellent connection (>1Gbps download / 400 Mbps+ upload) so I don't care about this metric. People with asymmetric throughput should be much more interested. So I would suggest  to keep both (adding two new tabs 'inbound' and 'outbound').

    Another way would be to keep GUI as it is and to add a filter in 'history' tab (and maybe the others tabs as well?) to select 'inbound only' / 'outbound only' . What do you think ?

    0
    Comment actions Permalink
  • Avatar
    Support Team

    Sorry for the confusion. I meant to say the message for "inbound" should be " <distant IP> accessed device x".

    It is a good idea to add an inbound/outbound filter in the history tab. I believe people care more about specific connections rather than an aggregated result (total data count) regarding the inbound/outbound traffic. 

    I'll forward your suggestion to the team and add it to our todo list.

    Thanks a lot.

    0
    Comment actions Permalink

Please sign in to leave a comment.