Printable View
I have code that sends and receives using RAW sockets. When I have wireshark capturing on the interface, my code receives the packet. Else, my code waits in the recvfrom(). What would cause something like this? Why would running wireshark affecting the program?
What packet? I don't think you've done a very good job explaining your problem.Quote:
When I have wireshark capturing on the interface, my code receives the packet
I guess it has something to do this this...
http://cboard.cprogramming.com/netwo...aw-socket.html
Yes, it is in reference to the 'Linux raw socket' post. Sorry I didnt explain it well. I have code that sends packets (pre-canned headers etc) from eth0. Based on information in the packet, the packet will either come back on eth0 or eth1. When I also have wireshark running listening on the interface, I am getting the packets that are supposed to come back on eth0. (Note: it also captures the packet I send. So I do some filtering). But when I stop wireshark, my code just waits on that recvfrom().
I put both interfaces in promiscuous mode and now everything works fine.