BM 3.9 Allow Rules issue

[@engineer.com gellenb]

On my old BM 3.8 server I had rules to allow access to sites blocked
by the filtering software. In some cases, those sites have multiple
servers within their domain and I created rules with * that worked.
For example:

URL alllow all access to http://*.website.*/*

That allowed access to www.website.com, www.website.org,
www-1.website.com, img.website.org and so on.

Now with BM 3.9SP2 I can't get those rules to work. If I add each
possible site into the rules like, www.website.com, www.website.org,
www-1.website.com, www-1.website.org, img.website.org and so on, it
works as long as I find all the various servers inside that domain and
place each one in the rule. Do the * no longer work, or do I have
to create rules differently?

Thanks

[Craig Johnson]

In article <v5ka95haf1dv96fqt...@4ax.com>, Gellenb wrote:
> Do the * no longer work, or do I have
> to create rules differently?
>

They should still be working. Did you see a change with aclcheck from
sp2? (I'm thinking you should try backrevving that to sp1 as a test).

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

[@engineer.com gellenb]

That fixed it. We went from 3.8 right up to 3.9 SP2 about two weeks
ago and just found out about the problem.

I put back ACLCHECK.NLM 4.90.02 dated March 6, 2008 replacing the one
4.91.03 January 27, 2009 and it is now working.

Thanks!

[Craig Johnson]

In article <7ura95585mekdbnbj...@4ax.com>, Gellenb wrote:
> I put back ACLCHECK.NLM 4.90.02 dated March 6, 2008 replacing the one
> 4.91.03 January 27, 2009 and it is now working.
>

OK, thanks for the feedback on that one.

Be aware that there is a new aclcheck in development now, and some
people have gotten it from Novell to fix an abend issue. I don't know
when it will come out as a public patch, but keep checking the Novell
patch list, (or tip #1 at the URL below).