Re: tcpsvd vs. tcpserver
Charlie Brady <[email protected]>
| Newsgroups | gmane.comp.misc.pape.general |
|---|---|
| Message-ID | <Pine.LNX.4.44.0410051024090.29217-100000@e-smith.charlieb.ott.istop.com> |
On Mon, 4 Oct 2004, Vincent Danen wrote, re conversion from tcpserver cdb to tpcsvd: > On 23-Sep-04, at 9:55 AM, Gerrit Pape wrote: [...] > > Yes, except for the -X option, and that the cdbs are not compatible, > > you > > can't use a cdb created with tcprules with ipsvd(7), you would need to > > create a new one using ipsvd-cdb(8), or use the directory directly. > > I think using the directory makes more sense since the directory needs > to exist anyways (I can see it being different for a large directory > with a lot of rules, but I think by and large the directory method > would be the simplest). I've recently done some conversion, and found the directory method simple and clear. Unless you have a heavily pounded server, I doubt you'd notice any performace difference. What I've found useful is to generate one config file for each policy I wish to implement (in my case, only "local" and "default"), and generate a set of symlinks for each network specification, viz: 0 -> default, 192.168.1 -> local, 127.0.0.1 -> local, 10.39.155 -> local. [This approach is perfect for me, since I generate all my config from a db of service policies and network lists; it may be less useful if you expect a human to construct the files and symlinks.] --- Charlie