LinkBack URL
About LinkBacksGot ya... so could the problem be our Bandwidth control rules? The default enabled rules block certain SSL connections in the name of stopping ultrasurf, but I would think traffic from the untangle box itself would be exempt.
Got ya... so could the problem be our Bandwidth control rules? The default enabled rules block certain SSL connections in the name of stopping ultrasurf, but I would think traffic from the untangle box itself would be exempt.
Five time Microsoft ASP.Net MVP managing a Lenovo RD330 / E5-2420 / 16GB with Untangle 16.5 to protect a 1Gbps fiber link for ~450 residential college students and associated staff and faculty
traffic to/from your Untangle is not subject to the rack, so that's not it. could be Packet Filter rules, though.
I have two custom packet filter rules to restrict smtp traffic to a set of allowed servers (#1: permit the servers. #2: deny all smtp). I think I probably set those up a way long time ago when I was new to untangle and did not appreciate the difference between the packet filter and some other feature like the firewall app or the bypass rules. Both will only match TCP port 25 traffic. I'm tempted to just delete them, because my current understanding is that they're not actually doing anything, except perhaps blocking smtp traffic to the untangle box itself... and since reports e-mails are working, empirically they're not even doing that.
Otherwise it's default rules only.
Last edited by jcoehoorn; 03-19-2013 at 10:25 AM.
Five time Microsoft ASP.Net MVP managing a Lenovo RD330 / E5-2420 / 16GB with Untangle 16.5 to protect a 1Gbps fiber link for ~450 residential college students and associated staff and faculty
Posting Permissions
