Found an error I didn''t expect on bind starting. "command channel listening on 127.0.0.1#953" So.... I should be setting up an interface for ''lo'' as well? Haven''t found anyone mentioning the lo interface. I just assumed that lo would have been given a default ACCEPT policy. Just checking before I start trying to configure all this into the files. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer''s challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
Tom Allison wrote:> Found an error I didn''t expect on bind starting. > > "command channel listening on 127.0.0.1#953"That is not an error message.> > So.... I should be setting up an interface for ''lo'' as well? > Haven''t found anyone mentioning the lo interface. I just assumed that > lo would have been given a default ACCEPT policy. > > Just checking before I start trying to configure all this into the files.You should include no configuration for the loopback interface. The default intra-zone ACCEPT policy is automatically applied to fw->fw traffic. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer''s challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/