The discussion below (Dec. 5, 2002) relates to BorderManager versions prior to BorderManager 3.7. But as long as you performed a Filtsrv Migrate process, it would also work fine on
BorderManager 3.7 servers, giving you the same default filters and exceptions as 3.6, 3.5 and 3.0. However, with BM37SP2.EXE, BRDCFG has finally changed.
With BRDCFG.NLM from BM37SP2 and later patches, BRDCFG now will give you the 'default BorderManager 3.7 filter exceptions'. (This subject is discussed at length in my book
on BorderManager packet filtering). Essentially, you get a series of stateful filter exceptions for the proxies to work. This is quite
different from the discussions of BRDCFG in my filtering book, so be aware that the new BRDCFG action will not match the description in the book. One nice thing about the new BRDCFG - it
should automatically put the filters and exceptions into NDS without requiring a Filtsrv Migrate process.
When posting about filtering issues in the forums, it will be very useful if you mention which version of BRDCFG you may have used, since the filtering problems between '3.7 defaults' and other
versions are very different. (My preference is to start with the 'old' defaults, and tighten them up, rather than use the 'new' defaults).
Ever needed to just wipe out the old filters and start from scratch? Here's the procedure. Note that saving your SYS:ETC\FILTERS.CFG file for backup purposes is a good idea, as that is
where your filters are defined. [Note: Filters are read from NDS in BorderManager 3.7 and 3.8. FILTERS.CFG will hold a backup copy of filters and exceptions if you use FILTCFG instead of iManager to
edit filters.]
From Caterina Luppi, Novell Support Connection Sysop:
1. At the server console, load INETCFG. In INETCFG, Protocols, disable IPX and IP filtering support. (Do not reinitialize system when exiting inetcfg!)
2. At the server console, type
3. Rename the file sys:\etc\filters.cfg on your BorderManager server.
4. Type Reinitialize System at the server console.
5. Make sure that the file sys:\etc\filters.cfg has not been recreated. (Look in the directory. The filters can be held in memory, and the filters.cfg file can be automatically recreated if you have
not followed all the steps).
6. LOAD BRDCFG at the server console and follow the prompts to set up the default filters and exceptions again.
For BorderManager 3.7 users (up to BM37SP2.EXE)
If you are using BorderManager 3.7, remember that you must next perform a FILTSRV MIGRATE procedure to migrate the filters ∓ exceptions from the FILTERS.CFG file into NDS. After BM37SP2 (and with
any version of BorderManager 3.8, BRDCFG will write filters directly into NDS.