-
Unfortunatly there is not much I can do to fix this problem. since Microsoft disabled Raw TCP sockets in XP sp2, I had to use winpcap to send raw packets, and as that does not support many wireless adapters, (and those that it does support only work in "read mode" not write mode)
see: http://www.winpcap.org/misc/faq.htm#Q-16
Beleive me if it was I could find a way to do it I would,
2006-09-26 09:18:29 UTC in tracetcp
-
codetrifle committed revision 76 to the tracetcp SVN repository, changing 1 files.
2006-02-26 11:05:07 UTC in tracetcp
-
codetrifle committed revision 75 to the tracetcp SVN repository, changing 1 files.
2006-02-26 11:04:45 UTC in tracetcp
-
codetrifle committed revision 74 to the tracetcp SVN repository, changing 1 files.
2006-02-26 11:04:31 UTC in tracetcp
-
codetrifle committed revision 73 to the tracetcp SVN repository, changing 1 files.
2006-02-25 23:11:25 UTC in tracetcp
-
Can you provide more details of your networking hardware/setup.
2006-02-24 15:34:29 UTC in tracetcp
-
Hi, I've added a couple of new options, which I hope will fix the problem you are having....
you can get this version from:
http://tracetcp.sourceforge.net/test/tracetcp.zip
If that fixes you problem then let me know and I'll release this as a new version.
the options are:
-i <interface index> will allow you to force tracetcp to use a particular interface.
eg: tracetcp...
2005-10-04 10:46:32 UTC in tracetcp
-
Hi,
Tracetcp tries to work out which interface to use, based on the destination IP address, and I have tested it with multiple Ethernet interfaces but never with a dial up adapter present. So in your case it MAY be selecting the wrong interface. There is no command to force it to use a particular interface but it probably wont be hard to add that feature. I'll try to take a look at it at the...
2005-09-29 14:51:10 UTC in tracetcp
-
codetrifle registered the emailbuddy project.
2005-09-20 10:08:04 UTC in emailbuddy
-
Hi, I've not encountered a problem like this before, but if all network traffic stops, the I would suspect that its a problem with the network card driver. Have you made sure you are using the latest driver for your network card? If this doesnt help would it be possible to try a different make of network adapter? From the winpcap mailing list I've occasionally read that winpcap can conflict...
2005-07-14 08:42:25 UTC in tracetcp
