Am Freitag, den 07.03.2008, 18:45 +0100 schrieb Wouter de Jong:
> Hi,
>
> We have 2 FreeBSD machines running as a firewall in a CARP+pf+pfsync setup.
> Worked great, however . today I noticed something weird.
>
> I had to reboot the master machine, and when it came back ...
> one of the CARP
Hi,
We have 2 FreeBSD machines running as a firewall in a CARP+pf+pfsync setup.
Worked great, however . today I noticed something weird.
I had to reboot the master machine, and when it came back ...
one of the CARP addresses no longer worked.
Looking in the logs, I got carp4: incorrect hash
Olivier Nicole wrote:
As a general rule, you should have one IP per NIC. Putting
thousands of IP addresses on a single box is a misuse of limited IP
space, unless you are using RFC-1918 addresses. What is the actual
problem you are trying to solve?
That is not true.
As a web hosting company,
> As a general rule, you should have one IP per NIC. Putting
> thousands of IP addresses on a single box is a misuse of limited IP
> space, unless you are using RFC-1918 addresses. What is the actual
> problem you are trying to solve?
That is not true.
As a web hosting company, you may want to
John Oxley wrote:
I know that I can put at least 65,000 aliases on an interface using
ifconfig alias. What kind of affect does this have on the system load
wise?
Benchmark it yourself, it will depend on your hardware and your workload.
As a general rule, you should have one IP per NIC. Putti
I know that I can put at least 65,000 aliases on an interface using
ifconfig alias. What kind of affect does this have on the system load
wise?
smime.p7s
Description: S/MIME cryptographic signature
While setting up a server with several IP addresses on the same
interface, we noticed something a bit odd.
When we add the new IP address with the command
ifconfig fxp0 alias 192.168.12.100 netmask 255.255.255.255
We can ping the address and all seems well at first. Then apparently
the other m
