I agree with most of this...the wizard was a start and started life as a rip from the m0n0 "magic shaper" code. If you look at the xml and compare it to the original m0n0 code, you won't see a whole heck of a lot of difference. Certainly a concept for post-1.0. Thanks
--Bill On 11/23/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Rather than seeing more "presets", which is an infinitely long list of > possible games or services we might want to put into the traffic shaper, > might I suggest the following for a future (post 1.0) release (note, these > concepts roll up, each builds on the next) > > Aliasing: already in the product. > > Host Groups: Ability to create a group which is really an alias for one or > more alias/hosts. Such as "mailservers" which would be a rollup for all > aliases or hosts in the group. > > Services: Ability to create a new service definition that would appear in > the dropdowns similar to the way SMTP, DNS and HTTP are in the dropdowns > today. Service definitions should allow multiple port ranges and protocol > types. This helps with the games or any other multiple-port service. > > The ability to create groups is used in Netscreen's OS, and the ability to > create a single alias for a service that has many ports is something I've > used in Sonicwall's OS. In Sonicwall, they don't allow services to overlap. > I haven't wrapped my head around that enough to envision if one could allow > overlapping services though... > > Anyhow, a service for a game might look like this: > > My Example Game: > TCP 3700 IN > UDP 3700 IN > TCP 3900-4000 OUT > UDP 3900-4000 OUT > > Then, in a NAT setup, "My Example Game" would appear in the dropdown. Or, > "Custom Service" would appear in the dropdown and a second picker/dropdown > would be used to choose from the Custom Services. > > Note: One problem with host groups is that there are conditions, such as > when you are using many-to-one NAT, that someone might think that using a > group alias is a good thing for incoming packets, but it wouldn't. The UI > would need to be clever enough to know what screens can use groups and > which require single hosts/aliases. > > - > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
