Agglomerator Help File
All
the rules that have been inserted are displayed in the sequence
that you have entered them, unless you have used the INSERT
command which in this case the rule will be inserted at the
specified row. Otherwise the rule is added to the end of their
own target.
Main Window
This command appends the rule to the end of the chain.
The rule will in other words always be put last in the rule
set in comparison to previously added rules, and hence be
checked last, unless you append or insert more rules later
on.
This command replaces the old entry at the specified line.
It works in the same way as the delete command, but instead
of totally deleting the entry, it will replace it with a new
entry. This might be good while experimenting with your firewall
mainly.
Insert a rule somewhere in a chain. The rule is inserted at
the actual number that is specified in the Rule No: box.
It will mangle the packet so that it will reach the
specified IP within your lan. ie: web server at 192.168.1.101
Note that the IP addresses within your lan does not need to
be routable.
Used to give access to the outer world for your LAN, servers
like workstations too.
When you nat a connection, it means that we set the IP address
used on a specific network interface instead of the --to-source
option, and the IP address is automatically grabbed from the
information about the specific interface. Nat also has the
effect that connections are forgotten when an interface goes
down, which is extremely good if we, for example, kill a specific
interface.
Add a rule
Not sure what your doing, read our Tcp/IP tutorial.
Tcp/IP tutorial
The IP Range is used to do Destination Network Address Translation,
which means that it is used to rewrite the Destination IP
address of a packet. If a packet is matched, and this is the
target of the rule, the packet, and all subsequent packets
in the same stream will be translated, and then routed on
to the correct device, host or network. This target can be
extremely useful, for example, when you have an host running
your web server inside a LAN, but no real IP to give it that
will work on the internet. You could then tell it to forward
all packets going to its own HTTP port, on to the real web
server within the LAN. We may also specify a whole range of
destination IP addresses, and the IP Range mechanism will
choose the destination IP address at random for each stream.
Hence, we will be able to deal with a kind of load balancing
by doing this.
Note that the IP Range is only available within the R-Robin
chain Note, as described previously, that a single stream
will always use the same host, and that each stream will randomly
be given an IP address that it will always be Destined for,
within that stream. We could also have specified only one
IP address, in which case we would always be connected to
the same host. Also note that we may add an port or port range
to which the traffic would be redirected to. Do note that
port specifications are only valid for rules that specify
the TCP or UDP protocols.
A port or a range of ports (22-80) can be specified in conjunction
with NAT to IP.
Deleting a rule is made by selecting the target (R-Robin
or Nat) and using the number of the rule on the left side of
the main screen.
|
ontact Details:
To give you the help
that you need to build your own network devices by giving an other life
to your PCs.
A group of highly motivated and diligent individuals, all masters in their
areas of expertise. For any assistance, please mail us at : 
All
our products are designed to help you build your network device in an unattended
setup. 
Our
rates are the most competitive you will find on the market. We believe
in delivering excellent worth for your money. 
The information you provide us will be highly confidential, and will not
be passed on to a third party. The extent of information you want to provide
us depends wholly on your discretion.