OS/2, eCS & ArcaOS - Technical > Networking
Wireshark port
Paul Smedley:
Hey Martin,
--- Quote from: Martin Iturbide on June 05, 2017, 02:29:28 am ---That's a very interesting port. I wonder which other library dependencies does the pcap library has.
Is this one? http://www.tcpdump.org/#latest-releases
--- End quote ---
For pcap, it's not so much dependencies, it will need some code written to allow the pcap libraries to access a network card on OS/2. I have some sample code from Digi that I'll investigate.
Meanwhile, iptrace logs captured manually should be able to be analysed using wireshark, so getting pcap is a nice to have, not a must have. Short term, it may be possible to get wireshark able to launch iptrace from the gui (wireshark seems to support external capture utilities).
Cheers,
Paul
Paul Smedley:
Updated build, http://smedley.id.au/tmp/wireshark-2.2.7-os2-20170611.zip
Major change is that opening binary captures files is fixed.
Capture menu is now not greyed out, but it doesn't work yet :)
Dariusz Piatkowski:
Hi Paul!
I got this latest release and upon starting the app from CLI I get the following:
=== START ===
[G:\APPS\TCPIP\WIRESHARK\BIN]wireshark
(process:401): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0)
Abnormal program termination - pid=0x0191 - tid=0x01 - G:\APPS\TCPIP\WIRESHARK\B
IN\WIRESHARK.EXE
Abnormal program termination - pid=0x0191 - tid=0x01 - G:\APPS\TCPIP\WIRESHARK\B
IN\WIRESHARK.EXE
=== STOP ===
QT 4.7.3 is installed and working with other apps. Maybe heimdal? I have the previous release (heimdal-1.5.3-os2-20160723.zip) which was required as part of the SAMBA client update you did a while ago (Kerberso authentication I think???)...I did not install the recommended heimdal-1.5.3-os2-20160730.zip hesitating to impact my working SAMBA configuration. libc066 & libcx in-place as per the latest REL availability in RPM/YUM.
If I can go ahead and update heimdal to your 0730 release, or better yet, if I can install the RPM/YUM heimdal-libs release 1.5.3-1.oc00 I'd be happy to, although I'm not sure if that matches your heimdal-1.5.3-os2-20160730.zip release? The only potential problem is that the RPM/YUM release is i386 platform, whereas all my current stuff (or the stuff I can control) is i686.
David McKenna:
Thanks Paul! I tried this build and the GUI starts fine, but the console fills up with 'Libc Panic: Child aborting fork' messages and the POPUPLOG is filled with this:
------------------------------------------------------------
06-12-2017 17:50:43 SYS3175 PID 0071 TID 0001 Slot 00b7
C:\PROGRAMS\WIRESHARK\BIN\WIRESHARK.EXE
c0000005
1e781e28
P1=00000002 P2=13850000 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000000 EBX=03bcfd18 ECX=05df0160 EDX=20807e32
ESI=00000039 EDI=05df0160
DS=0053 DSACC=d0f3 DSLIM=9fffffff
ES=0053 ESACC=d0f3 ESLIM=9fffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:1f802de4 CSACC=d0df CSLIM=9fffffff
SS:ESP=0053:03bcfc8c SSACC=d0f3 SSLIM=9fffffff
EBP=03bcfc8c FLG=00010246
LIBC066.DLL 0001:00001e28
--------------------------------------------------------------------------------------
Doesn't actually crash though.... maybe I should ignore these errors and just press on?....
Regards
Paul Smedley:
Hi guys,
I suspect David and Dariusz's problems are the same, although interesting that I don't see the same here.
wireshark.exe is trying to fork() & exec and executable, and fork() is failing for some reason. Here, fork() simply returns an error, it doesn't cause any traps as such.
I'm using heimdal from ArcaOS with no issues.
I'm running in a VM with the W4 kernel which may be a point of difference.
David - if you could try ignoring the errors it would be appreciated - I may need to disable all capture support until this is fixed - as mentioned, capture support is enabled but won't work until we get a functional libpcap port.
Cheers,
Paul
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version