>>Возможно повторюсь, но поиск не дал вразумительных результатов.
>>У меня два канала от разных провайдеров по ethernet
>>подключены к разным интерфейсам.
>>как настроить машину, чтобы была связь и по одному, и по другому
>>каналу.
>>конкретно меня интересуют настройки в rc.conf относительно defaultrouter и hostname
>>с остальным проблем нет...
>
>добавлю, что у меня firewall - IPFilter
Using NAT As a Load Balancer
Since ipnat is already rewriting packets for us, we can
use it to support one of the simpler features of those
expensive load-balancing systems and assign sessions to mul-
tiple destination addresses. This is accomplished using the
round-robin keyword:
rdr tun0 20.20.20.5/32 port 80 -> 192.168.0.5, 192.168.0.6 port 8000
But
If you use a rule like:
rdr x.x.x.x port 80 -> y.y.y.1,y.y.y.2,y.y.y.3 port 80 tcp round-robin
You will get an error like missing fields - 2nd port (,). This is because you can't put more than two hosts on a single round-robin line. You need to reformat it like this:
rdr x.x.x.x port 80 -> y.y.y.1,y.y.y.2 port 80 tcp round-robin
rdr x.x.x.x port 80 -> y.y.y.3 port 80 tcp round-robin
or better yet like:
rdr x.x.x.x port 80 -> y.y.y.1 port 80 tcp round-robin
rdr x.x.x.x port 80 -> y.y.y.2 port 80 tcp round-robin
rdr x.x.x.x port 80 -> y.y.y.3 port 80 tcp round-robin
The two examples above act exactly the same, but notice that the second example is much easier to manage. If one of your servers goes down, it's very easy to take it out of the loop quickly with the second example. In the first example, if y.y.y.1 or y.y.y.2 goes down, and you take that line out, you loose two hosts.
Помогло?
Вариант для распечатки
OpenNET: Виртуальная конференция (Public)
on
15-Мрт-04, 18:24 (MSK)
