Chuck Swiger wrote:
On Feb 23, 2007, at 2:41 AM, Frank Bonnet wrote:
You can do other things, such as using ng_fec to perform port
trunking, or using IPFW or some other thing to manually force
traffic out of the other interface, but it's unlikely to result in
much benefit.
Thanks for the
Chuck Swiger wrote:
Configuring the two interfaces with two different IP addresses is no
problem at all, presuming that these IP addresses reside in different
subnets. If both IPs reside in the same subnet, you are better off
configuring the second IP as an alias on the first interface, and
Daan Vreeken [PA4DAN] wrote:
natd can be used to do this.
The following example assumes your external interface is called sk0 and the
seconde interface, connecting to the second server, is called sk1 :
# Start natd and tell it to forward pop3 traffic to the second server
natd -n sk0
On Feb 23, 2007, at 2:41 AM, Frank Bonnet wrote:
You can do other things, such as using ng_fec to perform port
trunking, or using IPFW or some other thing to manually force
traffic out of the other interface, but it's unlikely to result in
much benefit.
Thanks for the infos , I'll try
Hi Frank,
On Thursday 22 February 2007 12:55, Frank Bonnet wrote:
Hello
I have a new mailhub with two ethernet gigabit interfaces, and I would like
to transparently redirect IMAP or POP3 requests to the second interface
which have a different IP address, to let the first interface drive the
On Feb 22, 2007, at 3:55 AM, Frank Bonnet wrote:
I have a new mailhub with two ethernet gigabit interfaces, and I
would like to
transparently redirect IMAP or POP3 requests to the second
interface which
have a different IP address, to let the first interface drive the
SMTP traffic only.
