Настройка utorren для TMG + FWC

Настройка utorren для TMG + FWC

Agnicul

Пользователь

Сообщения: 101
Благодарности: 2

Всем привет!
Руководствуясь всеизвестными правилами настроил TMG на работу с торрентами:
1) Set up the following new Protocols:

Name: BitTorrent (Inbound)
Ports: TCP - 64000 to 64100 Inbound
Secondary connection: TCP 64000 - 64100 Outbound

Name: BitTorrent (Outbound)
Ports: TCP - 64000 to 64100 Outbound
Secondary connection: TCP 64000 - 64100 Inbound

Name BitTorrent (UDP)
Ports: 64000 to 64100 Send Receive
Secondary connection: 64100 to 64100 Send Receive

You can add each of these to the same Access Rule. Создал правило доступа, из внутренне к внешней по вышеуказанным портам)

Create another new Protocol on a per-client basis:

Name: BitTorrent (Server - <Client Name>)
Ports: Create a TCP Inbound port range somewhere between 64000 and 64100 (e.g. 64000 to 64010)

Create a Non-Web Server Protocol Publishing Rule per BitTorrent client (client machines must have static IP or have DHCP reservations). These rules are the same thing as SOHO router's "port forwarding":

Name: What ever you want, be descriptive as to what the client using this rule is
Server IP: The client running BitTorrent
Listen from: External (aka The Internet)

Edit the above Server Publishing rule and go to the To tab. Make sure the radio box "Requests appear to come from the original client" is ticked. Создал правило не вебсервера, от клиента к внешней по вышеуказанным портам)

Go to Configuration -> General -> Define Firewall Client Settings -> Application Settings tab

Create two New Applications:

Application: [Executable name without file extension, e.g. utorrent]
Key: RemoteBindUdpPorts
Value: 64000-64100

Application: [Executable name without file extension, e.g. utorrent]
Key: ServerBindTcpPorts
Value: 64000-64100

Save all of the above changes and commit them to the ISA Server. Создал правило доступа для FWC)

Open utorrent, go to Options -> Preferences -> Connection, set the/a port that your Server Publishing Rule is using.

Under Advanced, go to net.outgoing_port and set it between 64000 and 64100. Указал порт в utorrent клиенте)

I've also set the IP/host name to report to tracker to a Dyndns hostname, though you can also use the ISA Server's external IP (if you're running ISA in Edge firewall mode).

Note: I have not gotten DHT to function in my limited tests (sits at Waiting to log in or login with 0 nodes), but uTorrent reports that NAT is functioning correctly. Download speeds are excellent and upload also works.

Also note that these same steps should be applicable to ISA 2004, but NOT ISA 2000.

И не работает...

Отправлено: 11:45, 10-11-2011

cameron

Ветеран

Сообщения: 4677
Благодарности: 1092

Профиль | Отправить PM | Цитировать

Цитата Agnicul:

И не работает... »

мде.

new protocol:
%name_inbound% - TCP inbound - %порт_указанный_в_клиенте%.
%name_outbound% - TCP outbound - %порт_указанный_в_клиенте%.
БЕЗ дополнительного чего-то либо.
Publish non-web server protocols:
%name% - IP хоста с клиентом - свежесозданный протокол - next
FW Policy:
Allow - %name_outbound% - internal - External - all users
Apply

Цитата Agnicul:

Under Advanced, go to net.outgoing_port »

верно.

-------
в личке я не консультирую и не отвечаю на профессиональные вопросы. для этого есть форум.

Это сообщение посчитали полезным следующие участники:

Delirium

Отправлено: 11:59, 10-11-2011 | #2