Interesting. Thank you for the reply.
I take it that the reason that OpenVPN logically can't support more than one connection using the same key to the VPN server is because a server for any secure tunnel expects the same IP address from the client, yes? So, if I run OpenVPN with the same key on two different computers behind my home router, I've essentially created two different tunnels, maintaining the same IP address for each tunnel, so it can be logically supported (assuming the server allows the key to be logged on concurrently for more than one tunnel). Whereas in the hypothetical I had asked about, the client's end of the tunnel would not maintain the same IP address, and that simply isn't allowed in the OpenVPN protocol, eh?
As it would be unfair to expect that I could have multiple concurrent tunnels using the same key from different IP addresses (how would you know the second IP address was really me and not a buddy of mine, eh?), this means I need to buy another account and load balance across two individual tunnels, one tunnel for each hard-line connection, yes? I'm pretty sure a single instance of pfSense can handle this, from what I've read. If it can't, I can just run 1 VMed pfSense for each OpenVPN tunnel, and then bond them with another VMed Pfsense for loadbalancing.
Do I have this right? Sounds like a good plan?
peace,
4eak