but bridging needs ipfw (or pf) and with heavy traffic
it needs lots of cpu.
----- Original Message -----
From: "Marcin Jessa" <[EMAIL PROTECTED]>
To: "OxY" <[EMAIL PROTECTED]>
Cc: <freebsd-net@freebsd.org>
Sent: Tuesday, May 16, 2006 4:31 PM
Subject: Re: changing default route
On Tue, 16 May 2006 15:53:38 +0200
"OxY" <[EMAIL PROTECTED]> wrote:
any other solution?
can i solve it with static routing?
Create a bridge interface, assign both the nics as it's members and
assign the IP to it.
Marcin.
----- Original Message -----
From: "Charles Swiger" <[EMAIL PROTECTED]>
To: "OxY" <[EMAIL PROTECTED]>
Cc: <freebsd-net@freebsd.org>
Sent: Tuesday, May 16, 2006 1:10 AM
Subject: Re: changing default route
> On May 15, 2006, at 7:04 PM, OxY wrote:
>> have two interfaces with the same ip, em0 connected to another
>> server with crosslink, em1 is the public, can be reached from the
>> internet connected to a switch.
>
> Don't do that. Use bridging instead, if appropriate.
>
> --
> -Chuck
>
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
