Its possible that you know more about this than I do. However, I don't think IP spoofing is a practical exercise. You can make an application which sends packets from your computer with an IP address which does not match your own. However, unless the protocol you're using explicitly sends the address of your computer externally to the low level which you have spoofed (which most don't) then the server is going to reply to the spoofed address. You will never receive the replies unless your computer is connected to the network on the spoofed address as well as under your normal address. If this is the case, what would be the point? If you wanted to make it look like traffic was coming from the spoofed address you could actually just use the desired interface instead of concocting some strange system with twice the amount of sockets as necessary.
I suppose it might be useful for protocols which might not expect the server to reply to the data, for instance protocols using UDP. The packets would arrive at the server with the spoofed ip address and as no data needs to be sent back it would appear in all the logs that the connection had nothing to do with you. However, for protocols built on top of TCP such as http, this seems quite useless.
I suppose it might be useful for protocols which might not expect the server to reply to the data, for instance protocols using UDP. The packets would arrive at the server with the spoofed ip address and as no data needs to be sent back it would appear in all the logs that the connection had nothing to do with you. However, for protocols built on top of TCP such as http, this seems quite useless.
Hoi Zaeme.
