OS/2, eCS & ArcaOS - Technical > Networking
Wireshark port
Paul Smedley:
OK, for now, I've disabled pcap support until we have a functional implementation.
A Wireshark build without it included is at http://smedley.id.au/tmp/wireshark-2.2.7-os2-20170617.zip
David McKenna:
Thanks again, Paul! This one indeed does not have all the errors in the console. I spent some time with it and everything that should work seems to work just fine. I was a little disappointed to find I had no Bluetooth connection. I wonder what 'souronnet.os2world.net' does? :-)
In case someone reading wants to try it, here is what I did:
1) Open a command line window and type 'iptrace lan0' (or lan1 or lan2 depending on which interface you want to monitor)
2) Browse the network for a little while (don't leave iptrace running for too long or the log file could fill up your hard drive!)
3) close iptrace by hitting <enter>. There is now a file called 'iptrace.dmp' in the directory you ran iptrace from.
4) In the same directory type 'ipformat -x'. This formats the trace for wireshark and is a file named 'iptrace.enc'.
5) Open Wireshark and open the file 'iptrace.enc'
Dariusz Piatkowski:
It works awesome!!!
Wow, this is really great...I mean all the stuff I have ever wanted to know (or was curious) about in the normal TCP/IP traffic exposed and available for review.
Here are a couple of icons I quickly grabbed on-line...in case anyone else is looking for something prettier than the OS/2 CLI session icon.
Thanks again Paul!
Paul Smedley:
Hey Dave!
--- Quote from: David McKenna on June 18, 2017, 02:09:28 pm --- Thanks again, Paul! This one indeed does not have all the errors in the console. I spent some time with it and everything that should work seems to work just fine. I was a little disappointed to find I had no Bluetooth connection. I wonder what 'souronnet.os2world.net' does? :-)
In case someone reading wants to try it, here is what I did:
1) Open a command line window and type 'iptrace lan0' (or lan1 or lan2 depending on which interface you want to monitor)
2) Browse the network for a little while (don't leave iptrace running for too long or the log file could fill up your hard drive!)
3) close iptrace by hitting <enter>. There is now a file called 'iptrace.dmp' in the directory you ran iptrace from.
4) In the same directory type 'ipformat -x'. This formats the trace for wireshark and is a file named 'iptrace.enc'.
5) Open Wireshark and open the file 'iptrace.enc'
--- End quote ---
Thanks for the feedback! Are you OK if I copy/paste the above into readme.os2 to help other users?
This might be a nice workaround until/if we can get native packet capture into wireshark/2 :)
Cheers,
Paul
Paul Smedley:
Hey Dariusz,
--- Quote from: Dariusz Piatkowski on June 19, 2017, 02:16:44 am ---It works awesome!!!
Wow, this is really great...I mean all the stuff I have ever wanted to know (or was curious) about in the normal TCP/IP traffic exposed and available for review.
Here are a couple of icons I quickly grabbed on-line...in case anyone else is looking for something prettier than the OS/2 CLI session icon.
Thanks again Paul!
--- End quote ---
Thanks for the feedback - I'll add one of those icons into the distribution - I hadn't even thought about icons, I'll check the source code distro for an icon as well.
Cheers,
Paul
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version