Import Qlogs from a different computer

[Fritzbied58]

Is your feature request related to a problem? Please describe. I don't believe the issue I've encountered is a problem, but unsure. I had captured a 'chrome-net-export-log.json' from my work computer intended to upload it to 'https://qlog.edm.uhasselt.be/sigcomm/' for QUIC and Qlog analysis due diligence. However I could not read the qlog url from my work computer, so I uploaded it to my home computer. The attempted again to load it to the qlog tool site. The tool indicates it was uploaded but when I browse through the menu, the form is there but no data. When I upload a qlog capture on my home computer, it works fine. QUESTION: Is it possible to load qlogs captured on one computer and then analyze on a different computer?

Describe the solution you'd like Analyze Qlogs captured on one computer on a different computer.

Describe alternatives you've considered Submitting a boundary change request, but that is like to be problematic.

Additional context I'm not a web developer or programmer, so I may not be aware of the full scope of options. Thanks in advance

[rmarx]

Hello @Fritzbied58,

Sad to hear you had issues with qvis.

I'm however afraid I don't really follow your explanation. Especially the could not read the qlog url from my work computer makes little sense to me, since you're trying to upload a chrome netlog .json file if I understand correctly?

In general, it shouldn't matter on which computer you capture qlog/netlog files: qvis should just be able to visualize them (it only looks at the uploaded file, no other information on the computer).

What I suspect from your explanation is that you're uploading a netlog file from Chrome that's somehow buggy/too new/too short/... That might get -loaded- correctly, but then the visualization could indeed be buggy/missing. qvis supports Chrome netlog output, but it's experimental and not as stable as using qlog files directly.

Could you maybe upload the problematic file(s) here or send them to me at robin.marx@kuleuven.be so I can take a look and help figure out what's wrong?

Thanks, Robin

[Fritzbied58]

Robin,

Thanks for the response. I really like what you are doing and can see lots of potential use in the everyday IT service management world.

I've been using Qlog/Qvis to help me understand how QUIC functions using my home computer to capture MS O365 Teams meeting transactions, almost exclusively QUIC. I've been capturing the transactions with Wireshark as well. The real goal however is to capture the Qlog chrome browser information on my work computer, because that where the issues are seen, especially audio issues.

On my work computer, I opened 'chrome://net-export', then started some MS Azure O365 sessions to capture the files hoping I could then access netlog-viewer.appspot.com/#import on my work computer, but it was blocked.

I downloaded the Qlog file to my home computer, I opened it on netlog-viewer.appspot.com/#import, it opened fine. When I tried to upload the file to qvis.quictools.inf/#/files, It indicated that there were no connections, however there were many. I do most of the work on my computer because I can use Wireshark. Until recently I was allowed to use Wireshark on my work computer. Since Wireshark is my primary tool, I'm hoping that between the two I can gain a more functional understanding to allow me to explain it effectively.

I also want to upload some decrypted Wireshark pcaps as well, I really like your graphs...I'd like to run them through some jacked up government network transactions. The hardest part is that I'm not a programmer so I am hesitant to install much, being an X submarine guy, I never turn valves I don't understand.... I started out my IT career back in the late 70's as a morse code operator!

I hate even asking questions at this level, but I see QUIC deployment as important, and can seem to convince anyone in upper management that it's an important development, e.g., no resources.

Thanks in advance

WR/Fritz

On Thu, Dec 30, 2021 at 8:14 AM Robin Marx @.***> wrote:

Hello @Fritzbied58 https://github.com/Fritzbied58,

Sad to hear you had issues with qvis.

I'm however afraid I don't really follow your explanation. Especially the could not read the qlog url from my work computer makes little sense to me, since you're trying to upload a chrome netlog .json file if I understand correctly?

In general, it shouldn't matter on which computer you capture qlog/netlog files: qvis should just be able to visualize them (it only looks at the uploaded file, no other information on the computer).

What I suspect from your explanation is that you're uploading a netlog file from Chrome that's somehow buggy/too new/too short/... That might get -loaded- correctly, but then the visualization could indeed be buggy/missing. qvis supports Chrome netlog output, but it's experimental and not as stable as using qlog files directly.

Could you maybe upload the problematic file(s) here or send them to me at @.*** so I can take a look and help figure out what's wrong?

Thanks, Robin

— Reply to this email directly, view it on GitHub https://github.com/quiclog/qvis/issues/61#issuecomment-1003023940, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXCNPNPANIKEESJEEAD5LVLUTRLJRANCNFSM5K4NSD2Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>