mirror/freebsd-ports
1
0
Fork 0
mirror of https://git.FreeBSD.org/ports.git synced 2024-12-21 04:06:46 +00:00
Code Issues Releases Activity
da392aa3b4
freebsd-ports/net/l4ip/pkg-plist

15 lines
439 B
Plaintext
Raw Normal View History

- add l4ip-v1.0.b294, the L4 health check daemon for IPFILTER. The idea is that IPFilter in its current state can already do a simple L4 round-robin in its NAT rules. However, it does not detect or sense when a service and/or host is down. It will continue to send requests to a downed service/host. However, IPFilter lets us add and remove rules on-the-fly so it should be possible to build a daemon that lets you specify "clusters". In each cluster you would specify its members/hosts and services. As well as a health-check for the service to determine its current state. Once a service was deemed "up" we would add a Round-Robin rule to the NAT table, and naturally, the reverse once we detect a service as being "down". In addition to this, this program can optionally add ipf rules to log for RST (reset) packets coming from the members of your clusters. In the situations where the software/port goes down, but the host itself is still working, we would detect failure instantly. (Since the forwarded connections to the service would trigger a RST packet back). If this option is enabled, l4ip spawns the "ipmon" command to monitor for the "log" entries given when such a packet is detected. l4ip will then mark the service down. This is an add-on feature and is strictly not necessary for functional usage. It is currently only supported for TCP. WWW: http://www.lundman.net/unix/l4ip.php
2006-02-17 18:44:32 +00:00
sbin/l4ip
- update COMMENT - better config file handling
2006-02-17 18:55:04 +00:00
@unexec if cmp -s %D/etc/l4ip.conf %D/etc/l4ip.conf.sample; then rm -f %D/etc/l4ip.conf; fi
etc/l4ip.conf.sample
@exec [ -f %B/l4ip.conf ] || cp %B/%f %B/l4ip.conf
- add l4ip-v1.0.b294, the L4 health check daemon for IPFILTER. The idea is that IPFilter in its current state can already do a simple L4 round-robin in its NAT rules. However, it does not detect or sense when a service and/or host is down. It will continue to send requests to a downed service/host. However, IPFilter lets us add and remove rules on-the-fly so it should be possible to build a daemon that lets you specify "clusters". In each cluster you would specify its members/hosts and services. As well as a health-check for the service to determine its current state. Once a service was deemed "up" we would add a Round-Robin rule to the NAT table, and naturally, the reverse once we detect a service as being "down". In addition to this, this program can optionally add ipf rules to log for RST (reset) packets coming from the members of your clusters. In the situations where the software/port goes down, but the host itself is still working, we would detect failure instantly. (Since the forwarded connections to the service would trigger a RST packet back). If this option is enabled, l4ip spawns the "ipmon" command to monitor for the "log" entries given when such a packet is detected. l4ip will then mark the service down. This is an add-on feature and is strictly not necessary for functional usage. It is currently only supported for TCP. WWW: http://www.lundman.net/unix/l4ip.php
2006-02-17 18:44:32 +00:00
%%EXAMPLESDIR%%/apache1.conf
%%EXAMPLESDIR%%/apache2.conf
%%EXAMPLESDIR%%/dns1.conf
%%EXAMPLESDIR%%/dns2.conf
%%EXAMPLESDIR%%/ftp1.conf
%%EXAMPLESDIR%%/ftp2.conf
%%EXAMPLESDIR%%/ldap.conf
%%EXAMPLESDIR%%/ldap1.conf
%%EXAMPLESDIR%%/ldap2.conf
@dirrm %%EXAMPLESDIR%%
Reference in New Issue Copy Permalink