Firewall not blocking ports

7echno7im · 12-11-2011, 02:32 PM

I have external administration on, but I want to block 22 still. Is this possible? I don't recall my ssh port being wide open before the upgrade even though I had external admin on (for https).

I tried to follow the wiki example the best I could but it is outdated.

It seems no matter how I slice it, 22 is open to the pub.

7echno7im · 12-11-2011, 02:36 PM

The attachment is wrong and I cant edit it.

7echno7im · 12-11-2011, 02:37 PM

Capture.PNG

7echno7im · 12-11-2011, 02:41 PM

Is it just me or did the "Source Port" option go away in 9.1?

dmorris · 12-11-2011, 03:33 PM

Firewall doesn't process traffic to/from the untangle server, just traffic going *through* the untangle server. If you don't want port 22 open, I'd just disable SSH.
If you don't want it to show as closed, you can go into config->networking->advanced->packet filter and at the bottom uncheck "Allow SSH from all interfaces."

btw, No point in adding matchers to rules that just match on "any." You might as well remove them since they always match.

Yes, source port went away.
I bet you noticed that when you tried to add a matcher to set source port = 22, right?

7echno7im · 12-11-2011, 08:24 PM

Awesome thank you. Sorry I should have remembered about the packet filter. Honestly, Untangle has run so well for so long I haven't had to adjust any of this. It truly has been set it and forget it. I still want ssh internally, just not exposed to the public so I created a user packet filter rule. Works like a charm.

I did notice the source port went away when trying to make the FW rule

thanks for the help.

12-11-2011, 02:36 PM	#2 (permalink)
7echno7im Master Untangler Join Date: Feb 2009 URLs submitted: 1 Posts: 169	The attachment is wrong and I cant edit it. __________________ www.techtronic.us

12-11-2011, 02:37 PM	#3 (permalink)
7echno7im Master Untangler Join Date: Feb 2009 URLs submitted: 1 Posts: 169	Capture.PNG __________________ www.techtronic.us

12-11-2011, 02:41 PM	#4 (permalink)
7echno7im Master Untangler Join Date: Feb 2009 URLs submitted: 1 Posts: 169	Is it just me or did the "Source Port" option go away in 9.1? __________________ www.techtronic.us

12-11-2011, 03:33 PM	#5 (permalink)
dmorris Untangle Junkie Join Date: Nov 2006 Location: San Mateo, CA URLs submitted: 10 Posts: 10,611	Firewall doesn't process traffic to/from the untangle server, just traffic going through the untangle server. If you don't want port 22 open, I'd just disable SSH. If you don't want it to show as closed, you can go into config->networking->advanced->packet filter and at the bottom uncheck "Allow SSH from all interfaces." btw, No point in adding matchers to rules that just match on "any." You might as well remove them since they always match. Yes, source port went away. I bet you noticed that when you tried to add a matcher to set source port = 22, right? __________________ Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself. If you need Untangle support please call or email support@untangle.com Last edited by dmorris; 12-11-2011 at 03:40 PM..

12-11-2011, 08:24 PM	#6 (permalink)
7echno7im Master Untangler Join Date: Feb 2009 URLs submitted: 1 Posts: 169	Awesome thank you. Sorry I should have remembered about the packet filter. Honestly, Untangle has run so well for so long I haven't had to adjust any of this. It truly has been set it and forget it. I still want ssh internally, just not exposed to the public so I created a user packet filter rule. Works like a charm. I did notice the source port went away when trying to make the FW rule thanks for the help. __________________ www.techtronic.us

Protect

Filter

Perform

Connect

Manage

Add-Ons