Quote:
Originally Posted by jggimi
You are blocking ICMP traffic, as part of your default block rule. You may want it, as it would allow ping, traceroute, and similar information to flow unimpeded.
It is not clear, from your last post, what platform you were running your failed curl command from, and the path it would take to connect to 192.168.0.200. Were you running this from the firewall, or from another platform on the network that connects to 0.200 *through* the firewall?
If it is going through your router, did you enable the IP forwarding sysctl?
Does the curl connection function correctly when pf is disabled? |
Everything is behind the firewall/router and I'm doing nightly dumps on my openbsd server and then I use curl to ftp the dumps to another server. Thanks I'll allow ICMP traffic to come on in. Setting up pf for a client server is different from a firewall which is the reason of the clumsy mistakes.