D-Link 604+ Advanced Filtering & Firewall

Has anyone actually got the filtering on the DLink 604+ to work.

I was told by DLink support that all rules are applied equally and not
in any specific order. The documentation supplied with the product is
very poor.

If anyone has any ideas on how to apply some simple rules to open up
specific ports, it would be greatly appreciated.

Thanks,

Mike

"Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) m...
> Has anyone actually got the filtering on the DLink 604+ to work.
>
> I was told by DLink support that all rules are applied equally and not
> in any specific order. The documentation supplied with the product is
> very poor.
>
> If anyone has any ideas on how to apply some simple rules to open up
> specific ports, it would be greatly appreciated.

I`ve managed to suss how to route specific ports to specific Ip ranges on my
LAN, I used the "Virtual Server" Rules..

> > Has anyone actually got the filtering on the DLink 604+ to work.
> >
> > I was told by DLink support that all rules are applied equally and not
> > in any specific order. The documentation supplied with the product is
> > very poor.
> >
> > If anyone has any ideas on how to apply some simple rules to open up
> > specific ports, it would be greatly appreciated.
>
> I`ve managed to suss how to route specific ports to specific Ip ranges on
my
> LAN, I used the "Virtual Server" Rules..
>

i found this out from ringning their customer services. but load balancing,
i do not think the actual thing supports it, cos its never done it for my
LAN and i seem to keep most of it for DC++ with my house m8s complaining
around me

(E-Mail Removed) (Mike) wrote in message news:<(E-Mail Removed) om>...
> Has anyone actually got the filtering on the DLink 604+ to work.
>
> I was told by DLink support that all rules are applied equally and not
> in any specific order. The documentation supplied with the product is
> very poor.
>
> If anyone has any ideas on how to apply some simple rules to open up
> specific ports, it would be greatly appreciated.
>
> Thanks,
>
> Mike

Finally managed to sort this one, no help from DLink support who
advised using port forwarding.

I set "IP Filter State" to enabled and "If Not Matched" to Block,
which basically blocked all traffic to my router.

I then applied the rules I required.

The example rules below allow WWW access. (port 80 = WWW and port 53 =
DNS.)
Source Destination
1 enabled WWW_IN Pass ISP1 TCP 0.0.0.0/0 80 80
192.168.0.0/24 0 0

2 enabled WWW_OUT Pass ethernet TCP 192.168.0.0/24 0 0 0.0.0.0/0
80 80

3 enabled DNS_IN Pass ISP1 TCP 0.0.0.0/0 53 53
192.168.0.0/24 0 0

4 enabled DNS_OUT Pass ethernet TCP 192.168.0.0/24 0 0 0.0.0.0/0
53 53

5 enabled DNS_IN Pass ISP1 UDP 0.0.0.0/0 53 53
192.168.0.0/24 0 0

6 enabled DNS_OUT Pass ethernet UDP 192.168.0.0/24 0 0 0.0.0.0/0
53 53

0.0.0.0/0 = All IP addresses
192.168.0.0/24 = Internal IP addresses
ISP1 = Inward(source is the internet and destination is your network)
ethernet= Outward(source is your network and destination is the
internet)

You must create an inward and outward rule for each port & protocol
you wish to allow.

Rule 1. Inward: Allow from any IP address on specific port to Internal
IP addresses.
Rule 2. Outward: Allow from any internal ip address to any IP address
on specific port.

This seemed to work for me. As I opened other ports and IP addresses
the machines behind the firewall could use the services the newly
added rules applied to.

This probably all sounds obvious to people used to working with
firewalls but when you get one of these things out of the box there is
next to no documentation or resources on line to help you.

If you spot any errors in the above please let me know.

Mike

(E-Mail Removed) (Mike) wrote in message news:<(E-Mail Removed). com>...
> (E-Mail Removed) (Mike) wrote in message news:<(E-Mail Removed) om>...
> > Has anyone actually got the filtering on the DLink 604+ to work.
> >
> > I was told by DLink support that all rules are applied equally and not
> > in any specific order. The documentation supplied with the product is
> > very poor.
> >
> > If anyone has any ideas on how to apply some simple rules to open up
> > specific ports, it would be greatly appreciated.
> >
> > Thanks,
> >
> > Mike
>
> Finally managed to sort this one, no help from DLink support who
> advised using port forwarding.
>
> I set "IP Filter State" to enabled and "If Not Matched" to Block,
> which basically blocked all traffic to my router.
>
> I then applied the rules I required.
>
> The example rules below allow WWW access. (port 80 = WWW and port 53 =
> DNS.)
> Source Destination
> 1 enabled WWW_IN Pass ISP1 TCP 0.0.0.0/0 80 80
> 192.168.0.0/24 0 0
>
> 2 enabled WWW_OUT Pass ethernet TCP 192.168.0.0/24 0 0 0.0.0.0/0
> 80 80
>
> 3 enabled DNS_IN Pass ISP1 TCP 0.0.0.0/0 53 53
> 192.168.0.0/24 0 0
>
> 4 enabled DNS_OUT Pass ethernet TCP 192.168.0.0/24 0 0 0.0.0.0/0
> 53 53
>
> 5 enabled DNS_IN Pass ISP1 UDP 0.0.0.0/0 53 53
> 192.168.0.0/24 0 0
>
> 6 enabled DNS_OUT Pass ethernet UDP 192.168.0.0/24 0 0 0.0.0.0/0
> 53 53
>
> 0.0.0.0/0 = All IP addresses
> 192.168.0.0/24 = Internal IP addresses
> ISP1 = Inward(source is the internet and destination is your network)
> ethernet= Outward(source is your network and destination is the
> internet)
>
> You must create an inward and outward rule for each port & protocol
> you wish to allow.
>
> Rule 1. Inward: Allow from any IP address on specific port to Internal
> IP addresses.
> Rule 2. Outward: Allow from any internal ip address to any IP address
> on specific port.
>
> This seemed to work for me. As I opened other ports and IP addresses
> the machines behind the firewall could use the services the newly
> added rules applied to.
>
> This probably all sounds obvious to people used to working with
> firewalls but when you get one of these things out of the box there is
> next to no documentation or resources on line to help you.
>
> If you spot any errors in the above please let me know.
>
> Mike

I had the same problem when I got mine - but I called D-Link's toll
free number and they were really helpful and knowledgable.