Hi Thanks for the reply. This is not the problem, because I'm positive that the payload contains purely textual information.
However, I did manage to fix the problem. Thought it would be nice to share what I discovered.... My C program called the pcap_open_live function like this: handle = pcap_open_live(dev, BUFSIZ, 1, 100, errbuf); However this doesn't work and for some reason the output goes all wrong. The following does work though! handle = pcap_open_live(dev, 2048, 1, 100, errbuf); I think 2048 is enough for the packets on the connections I will monitor, so that should be ok. Regards, Justin ----- Original Message ----- From: "Michael Richardson" <[EMAIL PROTECTED]> To: "Justin Robinson" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, September 11, 2003 12:52 AM Subject: Re: [tcpdump-workers] Output goes weird! > -----BEGIN PGP SIGNED MESSAGE----- > > > You have "printed" an unprintable character. Likely a ^O to put the > terminal into the alternate character set. Maybe UTF-8. > > You need to call "isprint()" before you print things. > > ] Out and about in Ottawa. hmmm... beer. | firewalls [ > ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ > ] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/ |device driver[ > ] panic("Just another Debian/notebook using, kernel hacking, security guy"); [ > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.2 (GNU/Linux) > Comment: Finger me for keys - custom hacks make this fully PGP2 compat > > iQCVAwUBP1+5UIqHRg3pndX9AQEYwQP/QWD5u1om2N988ikXMgu8ro7wKzAaUXO7 > 0qTWN1FqlSFvrRvw/WGVJCrFe76hXQvoV4AWC/PX0XdxsJCxTRv4wkPCsP3PjyBW > uZ4N5Oqqnmpexi2XjRh2ALzbgG7ft110CGKMc2lqFi7KPZ58We+RBHd70+x2A/4u > VCZzXJ2cmJY= > =VqR5 > -----END PGP SIGNATURE----- > - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]
