Should I open port 50 on my firewall

From: Tigger (tiggerdakat_at_yahoo.com)
Date: 09/30/04


Date: 30 Sep 2004 10:58:03 -0700

We have two groups of people setting up an SA to our sonicwall. One
has been successful without changing any access rules in the
sonciwall.
The other could not create a vpn tunnel without creating an access
rule that looks like this:

IPSEC (ESP) [0,50]
Source (the remote ip address of the VPN) WAN
Destination *

Would a rule like this compromise our LAN and/or firewall in any way.
It has always been my experience that we didn't have to open up any
ports or create any services on our Sonicwall.
Any thoughts would be appreciated.



Relevant Pages

  • Re: Should I open port 50 on my firewall
    ... > We have two groups of people setting up an SA to our sonicwall. ... > has been successful without changing any access rules in the ... > Source (the remote ip address of the VPN) WAN ... > Would a rule like this compromise our LAN and/or firewall in any way. ...
    (comp.security.firewalls)
  • Re: Connectivity between Two Subnets
    ... VPN tunnel. ... On the remote LAN, I have a Sonicwall with IP 192.168.15.1 and one ... >> Network Neighborhood but can not access any files or shared resources on ...
    (microsoft.public.windows.server.sbs)
  • Recommend me a firewall - Firebox 1000 vs. Sonicwall
    ... One of the strengths I like about Sonicwall is the fact that it ... doesn't require static IP's on both side of the vpn tunnel whereas ... on the Watchguard products, their lower line does and you have to step ... I do like the funtionality of the Firebox line but on the SOHO units, ...
    (comp.security.firewalls)
  • Watchguard Firebox 1000?
    ... I am replacing a Sonicwall Pro-300. ... bought the pro-vx and had to have it replaced because it was so buggy. ... set up a VPN tunnel between a sonicwall and this unit? ...
    (comp.security.firewalls)
  • VPN between SonicWall Pro230 and IPCop 1.3?
    ... Is it possible to create a VPN tunnel between a SonicWall Pro230 and ... IPCop 1.3? ... are there any "gotchas" to look out for? ...
    (comp.security.firewalls)