Sven Peters <[EMAIL PROTECTED]> writes: G'day Sven.
As an administrative note, I find it much easier to respond to your messages if you edit your comments inline rather than top-posting like this; it can be otherwise impossible to know what, exactly, you mean... > Yes, you're right. ...by this, since you just cut all the context away from the statement. > I'm intending to use simple linux hardware without snmp. SNMP is a network protocol, and Linux has both SNMP clients and servers. I am not sure you quite follow what it would be for. > Was wondering if heartbeat could be used to see if the hardware breaks No, because heartbeat doesn't offer hardware monitoring at that level. You /could/ use an OCF agent to monitor the hardware, I guess, but I don't think that does quite what you think it does. > and do the activation of the inactive interfaces on a second similar > machine. Unless you have *extremely* uncommon hardware there will be no inactive interface on the machine; both will be connected, full time, to the modem and -- unless the modem hardware fails -- will always be "active." (You /could/ be intending to run PPPoE on the server and have been referring to the PPP interface above, but I don't think so?) > VPNwise I was thinking about OpenVPN but still open to any other > products which are open source. I would not advise any other open source product except, perhaps, an IPSec based solution; the others are a security minefield to try and walk. Personally, I don't like IPSec much, as it is very complex, especially with vendor extensions, but it has the virtue of being at least standard where OpenVPN is a one implementation wonder. > I had already a look at http://lartc.org/howto/ and got some ideas but > it'll still be a lot of work to put together all the scripts. I think you probably need to do a lot more work on your design before you get to writing scripts: work out how everything should hang together logically, then implement it. Once you know what you are implementing most of the scripting is relatively easy, in my experience. The hard part is the network design. > As it isn't such an uncommon problem I was wondering if somebody else > has a similar setup and likes to exchange experiences, ideas and > pitfalls. You can reach me off list. Sadly, it is actually a pretty uncommon problem; most people don't have the resources to install multiple redundant links, or the need for availability to maintain them. Worse, because everyone has /different/ requirements you end up with multiple solutions, each to a slightly different problem. Regards, Daniel -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
