| | |
|
|
BadBlue Private Network Deployment Scenarios
|
|
BadBlue Help Center
>>
Gnutella Sharing FAQ
BadBlue Discussion
Email support
|
|
|
|
Deployment Scenarios for Organizational Sharing
BadBlue can utilize the Gnutella protocol in several
different ways to effect private networking for a variety
of traditional corporate sharing applications. The
following sections outline typical deployment scenarios
in Intranet, Extranet and hybrid configurations.
|
|
Intranet (LAN) Sharing Only
Add the following lines to the EXT.INI file for machines which
are to connect.
If a FLDS section already exists in the EXT.INI
file, don't create a new FLDS section, simply add the
statements at the end of the existing section.
[FLDS]
ALLOWNATCONNECTS=1
GNUTELLAPINGRATE=1800
GNUTELLACONNREQUEST=INET CONNECT/0.4
GNUTELLACONNRESPONSE=INET OK
GNUTELLALISTURL=
The ALLOWNATCONNECTS=1 setting permits BadBlue to attempt connections to
NAT'ed machines (e.g., per RFC 1918, the norm in many intranet
scenarios).
The GNUTELLAPINGRATE can be adjusted upwards for two
reasons:
(a) to reduce internal network traffic; and (b) because machines
typically stay attached to the network for longer periods of
time than in general Internet sharing situations.
The
GNUTELLACONNREQUEST and GNUTELLACONNRESPONSE settings can
be adjusted to ensure that only correctly configured machines
will be able to connect.
By clearing the GNUTELLALISTURL value, BadBlue won't fetch
the default Gnutella page for finding other peers. You can
use the Connect to friendly machines menu to configure
your PC to find other peers. Or if your organization has
a web page that lists addresses
or DNS names of approved peers, you can specify the page
here (see Advanced
Configuration Settings for instructions on specifying
this page).
To ensure additional levels of security, review the
Security Help Center to take advantage
of access control, IP restrictions and other security capabilities
which can help restrict access to authorized users.
|
|
Intranet-Extranet Sharing
Add the following lines to the EXT.INI file for machines which
are to connect.
If a FLDS section already exists in the EXT.INI
file, don't create a new FLDS section, simply add the
statements at the end of the existing section.
[FLDS]
ALLOWNATCONNECTS=1
GNUTELLAPINGRATE=360
GNUTELLACONNREQUEST=MYCO CONNECT/0.4
GNUTELLACONNRESPONSE=MYCO OK
GNUTELLALISTURL=
For machines inside a firewall, the ALLOWNATCONNECTS=1
permits BadBlue to attempt connections to
NAT'ed machines (e.g., per RFC 1918, the norm in many intranet
scenarios). For machines outside a firewall (e.g., a
dialup user connecting to the Internet without a VPN),
ALLOWNATCONNECTS=0 can be used.
The GNUTELLAPINGRATE can be adjusted upwards for two
reasons:
(a) to reduce network traffic on the LAN; and (b) because machines
typically stay attached to the network for longer periods of
time than in general Internet sharing situations.
The
GNUTELLACONNREQUEST and GNUTELLACONNRESPONSE settings can
be adjusted to ensure that only correctly configured machines
can connect.
By clearing the GNUTELLALISTURL value, BadBlue won't fetch
the default Gnutella page for finding other peers. You can
use the Connect to friendly machines menu to configure
your PC to find other peers. Or if your organization has
a web page that lists addresses
or DNS names of approved peers, you can specify the page
here (see Advanced
Configuration Settings for instructions on specifying
this page).
To ensure additional levels of security, review the
Security Help Center to take advantage
of access control, IP restrictions and other security capabilities
which can help restrict access to authorized users.
|
|
|
Secure Intranet-Extranet Sharing *
Add the following lines to the EXT.INI file for machines which
are to connect.
If a FLDS section already exists in the EXT.INI
file, don't create a new FLDS section, simply add the
statements at the end of the existing section.
[FLDS]
PROTOCOLKEY=secretpassword
ALLOWNATCONNECTS=1
GNUTELLAPINGRATE=360
GNUTELLACONNREQUEST=MYCO CONNECT/0.4
GNUTELLACONNRESPONSE=MYCO OK
GNUTELLALISTURL=
The PROTOCOLKEY is used to encrypt and decrypt all P2P
traffic using symmetric, private-key encryption.
For machines inside a firewall, the ALLOWNATCONNECTS=1
permits BadBlue to attempt connections to
NAT'ed machines (e.g., per RFC 1918, the norm in many intranet
scenarios). For machines outside a firewall (e.g., a
dialup user connecting to the Internet without a VPN),
ALLOWNATCONNECTS=0 can be used.
The GNUTELLAPINGRATE can be adjusted upwards for two
reasons:
(a) to reduce network traffic on the LAN; and (b) because machines
typically stay attached to the network for longer periods of
time than in general Internet sharing situations.
The GNUTELLACONNREQUEST and GNUTELLACONNRESPONSE settings can
be adjusted to ensure that only correctly configured machines
can connect.
All machines that are to connect to the network
should have identical settings for the PROTOCOLKEY,
GNUTELLACONNREQUEST and GNUTELLACONNRESPONSE.
By clearing the GNUTELLALISTURL value, BadBlue won't fetch
the default Gnutella page for finding other peers. You can
use the Connect to friendly machines menu to configure
your PC to find other peers. Or if your organization has
a web page that lists addresses
or DNS names of approved peers, you can specify the page
here (see Advanced
Configuration Settings for instructions on specifying
this page).
To ensure additional levels of security, review the
Security Help Center to take advantage
of access control, IP restrictions and other security capabilities
which can help restrict access to authorized users.
* Available soon, requires BadBlue
Enterprise Edition.
|
|
|
|
BadBlue Help Center
>>
Gnutella Sharing FAQ
BadBlue Discussion
Email support
|
|
|
