On Mon, 31 Jan 2011, Daniel Hartmeier wrote:
On Fri, Jan 28, 2011 at 08:49:27AM +0000, andy thomas wrote:
and this works fine as I can access webmail on port 444. But why can't I
access the Sonicwall on port 444? Does anyone know if the Sonicwall uses
additional ports or has anyone got this device to with with a PF-based
firewall?
First, I'd try to connect to the Sonicwall from the pf box itself,
so it's using its local address. If that doesn't work, how's the
pf box different from any other local client, for which this works?
Then try and add NAT on the pf box' internal interface, so redirected
connections should work like the previous test. If they don't, the
problem clearly is with the pf box.
I've logged into the pf box via ssh and used the lynx text browser to
access the Sonicwall's web interface on the internal interface and this
works fine.
But if they do work, but don't without NAT:
Check if maybe the Sonicwall has a list of networks it accepts
connections from. It might default to refuse connections from
non-local networks.
I'll get the guy who installed the Sonicwall to check this.
Also check if the Sonicwall has a correct default route. Without
a correct default route, non-local connections would fail precisely
in the way you describe...
I'd thought of that and the installer has confirmed it is set up
correctly.
Thanks for getting back to me,
Andy
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-pf
To unsubscribe, send any mail to "[email protected]"
