Re: CARP again, again
On Dec 23, 2004, at 5:28 PM, ed wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, sorry to bother you all again. I have a question, we have two DSL connections, and I plan on using two boxes, which are carped. But, I'd like to do this in a fashion such that I can failover to a different connection when the primary one becomes unusable. Would anyone have experience of doing this, and how exactly does one determine that the connection has failed? Does it base the failure on link status or on IP untouchables? CARP really has nothing to do with this. CARP is a link-layer protocol which allows one box to assume the virtual interface when another becomes unavailable on the same local segment. Since each box will still see each other as alive when your route goes down, they'll operate as usual. Your problem is a network-layer issue. Attack it just like you might with one box connected to dual gateways, since that's exactly what you're emulating. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net
Re: CARP again, again
On Thu, 2004-12-23 at 17:28, ed wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, sorry to bother you all again. I have a question, we have two DSL connections, and I plan on using two boxes, which are carped. But, I'd like to do this in a fashion such that I can failover to a different connection when the primary one becomes unusable. Would anyone have experience of doing this, and how exactly does one determine that the connection has failed? Does it base the failure on link status or on IP untouchables? well--setting 'net.inet.carp.preempt=1' will allow you to fail-over all interfaces on the primary if a single interface loses link. if you want to get fancier than that; i.e., pinging upstream hosts over each link--take a look at ifstated: DESCRIPTION The ifstated daemon runs commands in response to network state changes, which it determines by monitoring interface link state or running external tests. For example, it can be used with carp(4) to change running services or to ensure that carp(4) interfaces stay in sync, or with pf(4) to test server or link availability and modify translation or routing rules. the source is present in 3.6, but not compiled in the default system--have a look in: /usr/src/usr.sbin/ifstated for the bits. -j -- Television! Teacher, mother, secret lover. --The Simpsons
Re: Traffic Monitoring, IP
Bob DeBolt wrote: http://www.ntop.org might be what your looking for Bob But the latest ntop's doesn't compile on latest OpenBSD's Marcel
Re: Traffic Monitoring, IP
On Thu, 2004-12-23 at 21:44 +0100, Miroslav Kubik wrote: Hi Im trying to make some kind of network traffic graphs on my OpenBSD box but Take a look at pfflowd/softflowd from Damien Miller -- Massimo
Re: Traffic Monitoring, IP
Thanks but your solution seems to be too difficult to set up. I looked at ntop as well but unfortunetaly current version has some problem in OpenBSD 3.6 according to the ntop forum. So what next? MK - Original Message - From: Massimo [EMAIL PROTECTED] To: Miroslav Kubik [EMAIL PROTECTED] Cc: pf@benzedrine.cx Sent: Friday, December 24, 2004 10:17 AM Subject: Re: Traffic Monitoring, IP On Thu, 2004-12-23 at 21:44 +0100, Miroslav Kubik wrote: Hi Im trying to make some kind of network traffic graphs on my OpenBSD box but Take a look at pfflowd/softflowd from Damien Miller -- Massimo
