Re: blocking by domain name

The easiest way to do that is to simply add the domain
name to your hosts.deny in the /etc directory

Todd

--- Ryan <ryanag <at> zoominternet.net> wrote:

> Is it possible to use Guarddog to block traffic by
> domain name instead
> of IP address?
> 
> For example, create a new address of baddomain.com,
> then reject http
> traffic to it.
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by xPML, a
> groundbreaking scripting language
> that extends applications into web and mobile media.
> Attend the live webcast
> and join the prime developer group breaking into
> this new coding territory!
>
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Guarddog-user mailing list
> Guarddog-user <at> lists.sourceforge.net
>

Re: blocking by domain name

Yeah, but that only works for applications that are aware of
TCP_wrappers. It won't work for my web browser.

Todd Relyea wrote:
> The easiest way to do that is to simply add the domain
> name to your hosts.deny in the /etc directory
>
> Todd
>
> --- Ryan <ryanag <at> zoominternet.net> wrote:
>
>   

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

(no subject)

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Guarddog-user digest, Vol 1 #472 - 1 msg

They use ports 4000-32000

You would need to set up and activate a user defined protocol rule for this 
ports.

On Wednesday 22 March 2006 09:15 pm, 
guarddog-user-request <at> lists.sourceforge.net wrote:
> Send Guarddog-user mailing list submissions to
> 	guarddog-user <at> lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/guarddog-user
> or, via email, send a message with subject or body 'help' to
> 	guarddog-user-request <at> lists.sourceforge.net
>
> You can reach the person managing the list at
> 	guarddog-user-admin <at> lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Guarddog-user digest..."
>
>
> Today's Topics:
>
>    1. live365 music (michel-verplancke <at> clix.pt)
>
> --__--__--
>
> Message: 1
> From: michel-verplancke <at> clix.pt

Re: cornfedsip: voip and sip protocol problems

Giorgio Pioda wrote:

> the bidirectional checkbox doesn't work properly. After setting up guarddog 
> correctly for the UDP 5004 port I looked back in the exported script and the 
> connection is NOT bidirectional.
> 
> Modifiing the script manually in the way shown below solved the problem:

Since I am in a similar situation ... the fix below applies to a 
firewall also doing NAT using Guidedog, correct ?

To be precise: the context is a box behind NAT calling outside, right ?

Thank you for your consideration,
Davide Bolcioni

-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: cornfedsip: voip and sip protocol problems

Actually I don't use Guidedog because I have a DSL router which connect all my 
home network. I suppose you have also to open your firewall ports (in the 
same way I've done it)  for your local zone in the firewall.

About NAT: my DSL router is NAT transparent... so I suppose it should work. I 
don't now if there is a special feature in guidedog to activate NAT, but I 
can imagine there is one.

gfwp

P.S. Buona Pasqua in ritardo

Alle 12.11, lunedì, 24 aprile 2006, Davide Bolcioni ha scritto:
> Giorgio Pioda wrote:
> > the bidirectional checkbox doesn't work properly. After setting up
> > guarddog correctly for the UDP 5004 port I looked back in the exported
> > script and the connection is NOT bidirectional.
> >
> > Modifiing the script manually in the way shown below solved the problem:
>
> Since I am in a similar situation ... the fix below applies to a
> firewall also doing NAT using Guidedog, correct ?
>
> To be precise: the context is a box behind NAT calling outside, right ?
>
> Thank you for your consideration,
> Davide Bolcioni
>
>
> -------------------------------------------------------

streaming music