In article <kwSKi.4391$NG7.2073@kovat.provo.novell.com>, Valentin wrote:
> I want to put a Terminal Server for each ISP using Generic TCP Proxy and a
> single Border Manager.
>
> ISP1<->NIC1<->BM<->NIC2<->TS1
> ISP2<->NIC3<->BM<->NIC4<->TS2
>
Let us say that ISP1 is the default route here.
The internal NIC's are not a problem.
Putting generic TCP proxy on each public NIC is not a problem either.
However, sending replies out the ISP2 public nic when the ISP1 NIC has the
default route IS a problem.
Your server will always send internet replies to the default route, unless it
knows 'where' to send the replies. So traffic could come in the ISP2 NIC,
but try to go back out the other.
If you go to the non-default-route internet router (ISP2), and enable NAT on
the LAN side of that router (which you could do with a Cisco), then all
traffic coming in from the Internet on that ISP link will look (to BMgr) like
it was coming from a local host. Then, BMgr will not have to send the
replies to the default route, because it will think it is directly connected
(on NIC2) to the requester.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to
http://www.craigjconsulting.com ***