I would say he's making a practical mistake (maybe two) and you're making two theoretical mistakes.
You're confusing authorization with authentication. (It's a common confusion.)
- Your dad is proposing an authorization policy: a computer that attempts to connect and that has provided a password in the past does not need to provide a password again.
- For our purposes here, a computer can be identified by the MAC address of the Ethernet interface (wired or wireless) that will connect with the router.
- However, a MAC address is not good for authentication, because it can easily be spoofed (many Ethernet cards allow you to change their MAC address at will). This is (if you're reporting his point of view correctly) your dad's practical mistake: without cryptography, you won't be getting much protection. (You will get some protection against a casual attacker.)
Notice I wrote cryptography, not encryption. Encryption provides confidentiality, that is, eavesdroppers wouldn't be able to snoop on your network. This may well be desirable, but what you're after here is authentication, and that does not derive directly from encryption (if you just encrypt a password in transit, an attacker can snoop on and replay the encrypted password and be authenticated as well). Cryptographic protocols such as SSL/TLS (the S in HTTPS), and more relevantly here WEP and WPA, provide some form of authorization as well as encryption.
It may be possible to implement your dad's authorization policy (that depends on your router model), but as I said before it wouldn't be very secure. WPA2 is the recommended security option for wifi networks (for wired networks, controlling physical access to the plugs is the usual solution; if you use PLC this may not be possible).
If am unconvinced that using cryptography would slow down your connection. It might add a little bit of latency, typically not enough to matter. As far as bandwidth is concerned, the physical medium is usually the limiting factor (if it's not, consider upgrading your router — you might get better radio equipment and so better speed even without encryption).
If you go for WPA, you would set a password in the router, and authorize any computer in possession of that WPA password to connect. You would then enter the password once on every computer that should connect (your software will remember the password for the next time, so you won't have to enter it again). That would provide a user experience similar to what your dad envisages, and a security that should be acceptable to you.
Seeing that I live in a rural area, it seems like neither of them are worth implementing unless I apply to become a broker. – digitxp – 2010-11-14T04:48:44.550
Also, quick question I don't wanna Google: I tried out a Netgear router that said that it could provide encryption only after disabling. Am I correct to assume that that router was feeding me BS? – digitxp – 2010-11-14T04:50:10.243
@digitxp: I don't understand your question: after disabling what? – Gilles 'SO- stop being evil' – 2010-11-14T10:23:41.030
Must've been typing faster than I could think. Disabling 802.11n, leaving only a/b/g/ to connect through. – digitxp – 2010-11-14T14:35:19.373
@digitxp: I can't think of a reason why encryption would be incompatible with 802.11n. It could be an issue with this particular model. – Gilles 'SO- stop being evil' – 2010-11-14T15:57:43.940
@Gilles That could be it. For now, I'm riding high on n and all the world is under my command ^-^ – digitxp – 2010-11-16T22:28:41.773