>Есть два интерфайса: xl0-во внутр. сеть 192.168.0.0/24, xl1-во внеш. сеть с ADSL
>модемом 192.168.1.0/24, во внутренней сети есть сервер с 2003 виндой, нужно
>из инета подключатся терминалом к нему, пусть у него будет IP
>192.168.0.2:3389. Роутер на FreeBSD 5.2.1, ipfw работает в режиме все разрешенно,
>как правильно нужно прописать правило что бы происходило перенаправление пакетов с
>порта 3389 на внешнейм IP во внут. к серверу 192.168.0.2:3389
>
>спасибо всем....
из мана
fwd | forward ipaddr[,port]
Change the next-hop on matching packets to ipaddr, which can be
an IP address in dotted quad or a host name. The search termi-
nates if this rule matches.
If ipaddr is a local address, then matching packets will be for-
warded to port (or the port number in the packet if one is not
specified in the rule) on the local machine.
If ipaddr is not a local address, then the port number (if speci-
fied) is ignored, and the packet will be forwarded to the remote
address, using the route as found in the local routing table for
that IP.
A fwd rule will not match layer-2 packets (those received on
ether_input, ether_output, or bridged).
The fwd action does not change the contents of the packet at all.
In particular, the destination address remains unmodified, so
packets forwarded to another system will usually be rejected by
that system unless there is a matching rule on that system to
capture them. For packets forwarded locally, the local address
of the socket will be set to the original destination address of
the packet. This makes the netstat(1) entry look rather weird
but is intended for use with transparent proxy servers.
|
Вариант для распечатки
Маршрутизаторы CISCO и др. оборудование. (Public)
(??) on
12-Окт-04, 20:53 (MSK)
