> > The gateway's IP address actually refers to two different machines.
> > Naturally the gateway is used quite a bit, and the syslog fills up with "arp
> > X moved from Y to Z on fxp0" messages.
>
> That's really not the right way to do it, and probably doesn't balance
> the load as well as you m
< said:
> The gateway's IP address actually refers to two different machines.
> Naturally the gateway is used quite a bit, and the syslog fills up with "arp
> X moved from Y to Z on fxp0" messages.
That's really not the right way to do it, and probably doesn't balance
the load as well as you mig
Oh, i am sorry, i was wrong, net.link.ether.inet.log_arp_wrong_iface
is for another problem.
On Tue, 18 Sep 2001, Maxim Konovalov wrote:
>
> Hello,
>
> On Tue, 18 Sep 2001, Matthew Luckie wrote:
>
> > Hi there
> >
> > At work there are several freebsd machines that route packets through a
> > "
Hello,
On Tue, 18 Sep 2001, Matthew Luckie wrote:
> Hi there
>
> At work there are several freebsd machines that route packets through a
> "load balanced" or "redundant" router configuration.
> The gateway's IP address actually refers to two different machines.
> Naturally the gateway is used q
Hi there
At work there are several freebsd machines that route packets through a
"load balanced" or "redundant" router configuration.
The gateway's IP address actually refers to two different machines.
Naturally the gateway is used quite a bit, and the syslog fills up with "arp
X moved from Y to
