Add another magic number (we'd have used the Navtel one, except that

nobody from Navtel has ever said whether their format differs from the
standard one anywhere other than the time stamp).

diff --git a/savefile.c b/savefile.c
index 6c47e5f60fb3b62ee45346ab2e558053401c1b60..6fcb2f653e04c52ef7ec29a03809fc61cbda17b8 100644 (file)
--- a/savefile.c
+++ b/savefile.c
@@ -30,7 +30,7 @@
 
 #ifndef lint
 static const char rcsid[] _U_ =
 
 #ifndef lint
 static const char rcsid[] _U_ =

-    "@(#) $Header: /tcpdump/master/libpcap/savefile.c,v 1.126.2.12 2005-08-13 22:29:44 hannes Exp $ (LBL)";
+    "@(#) $Header: /tcpdump/master/libpcap/savefile.c,v 1.126.2.13 2005-08-29 21:05:45 guy Exp $ (LBL)";

 #endif
 
 #ifdef HAVE_CONFIG_H
 #endif
 
 #ifdef HAVE_CONFIG_H


@@ -71,6 +71,12 @@ static const char rcsid[] _U_ =
  */
 #define NAVTEL_TCPDUMP_MAGIC   0xa12b3c4d
 
  */
 #define NAVTEL_TCPDUMP_MAGIC   0xa12b3c4d
 

+/*
+ * Normal libpcap format, except for seconds/nanoseconds timestamps,
+ * as per a request by Ulf Lamping <[email protected]>
+ */
+#define NSEC_TCPDUMP_MAGIC     0xa1b23c4d
+

 /*
  * We use the "receiver-makes-right" approach to byte order,
  * because time is at a premium when we are writing the file.
 /*
  * We use the "receiver-makes-right" approach to byte order,
  * because time is at a premium when we are writing the file.