Ip Spoofing And Ssh

I set up ssh and my router to allow remote login into my machine. Upon viewing the logs I have found numerous different people attempting to gain access to my computer through ssh. While I realize it is unlikely that they will get in (since my user name is nothing common like test, mike, or admin) I'm generally a very cautious person and I am not happy allowing these attacks to go on.

In order to prevent these attacks, this is the plan I have developed:

I can modify the hosts.allow and hosts.deny files to let in only one ip address such as 83.32.99.101. The computer will deny all other IPs. The IP address is totally irrelevant as long as I know what it is. Then, from anywhere I am, I can spoof my ip address so that to my computer, my IP appears as 83.32.99.101. Its almost like having a second password that no one knows to look for.

The problem is that I don't know much about IP spoofing, I don't know if this would work, and I can't find any information about how to spoof your IP address. Can someone please point me towards a guide on how to spoof your ip? Additionally, what tools are available for Linux that allow or provide ip spoofing capabilities?


Thanks
Mike

Personally I think that is too overcomplicated. I'd rather just disable root login, change the port to something non-standard, set up key authentication and disable password. Lastly add something like denyhosts to block multiple failed attempts. All but the last option can be set up through the /etc/ssh/sshd_config file.

With regards to disabling root login, I have PermitRootLogin set to no, but I am still able to log in as root from a remote location. I don't know if theres something else I have to set as well.

If root login is correctly disable and i attempt to log in as root remotely, will it still prompt for a password and just not let me in or will it deny me outright?


Regardless, some information on how to spoof an IP address would be useful. I'm learning about penetration testing and I need to be able to spoof IP address in order to test if a machine is vulnerable to that sort of attack.

Thanks,
Mike

Why not forget about this kind of mucking around with IP spoofing and just use public key pairs for authentication? That's far more secure than just a password. If you can carry around the software to spoof IPs (assuming it can be done, you might as well carry around a ssh client and your key).

Sorry, don't ask me about IP spoofing, you'd have to hang out with crackers.

I guess its a little complex. Thanks anyway guys.