Subject | Re: [firebird-support] Re: Installing Firebird 2.0 on Xen AMD64 |
---|---|
Author | Helen Borrie |
Post date | 2007-01-23T21:45:53Z |
At 06:17 AM 24/01/2007, you wrote:
- did you have anything blocking access to network connections. You did.
been repeatedly explained, direct connection
doesn't happen across a network interface. The
client is not a network client, but a local
user. xinetd is the means by which the Classic
server is made available to network clients,
including a client that is sitting in front of
the machine and attempting to connect across the local loopback server.
Looking at AppArmor details, it's kinda like a
"Firewall for Dummies". Any network client
application has to be configured in AppArmor as a
"friend"; otherwise all client apps are enemies
-- Connection rejected by host!
If you have installed SuSE WITH AppArmor
activated, then it has probably allowed its own
client applications access by default. (You
could test this with the SendMail client, since
we know that the Sendmail server port (25) is open).
Anything *else* would have to be configured
explicitly. That is how firewalls work, even the
firmware firewall in your ADSL router, if you have one.
./heLen
>Michael Möhle wrote:And we return to the first replies to this thread
> > My Question again. Do you have AppArmor enabled?? It can prevent fb from
> > working.
> > Its a security tool from Novell/SuSE. Look here :
> > http://en.opensuse.org/Apparmor
> > If you have installed AppArmor you must create a so called 'Profile' for
> > your App.(FB)
> > If you dont do it AppArmor will proactively protect the operating system!
> > Or just uninstall AppArmor.
>
>I have it installed, but assumed it wasn't active. After this email, I
>see it is active by default (unlike the openSuse firewall).
>
>This is probably it.
- did you have anything blocking access to network connections. You did.
>But on the other hand, why would it run in direct connect mode?"It" being Firebird Classic? Because, as has
been repeatedly explained, direct connection
doesn't happen across a network interface. The
client is not a network client, but a local
user. xinetd is the means by which the Classic
server is made available to network clients,
including a client that is sitting in front of
the machine and attempting to connect across the local loopback server.
Looking at AppArmor details, it's kinda like a
"Firewall for Dummies". Any network client
application has to be configured in AppArmor as a
"friend"; otherwise all client apps are enemies
-- Connection rejected by host!
If you have installed SuSE WITH AppArmor
activated, then it has probably allowed its own
client applications access by default. (You
could test this with the SendMail client, since
we know that the Sendmail server port (25) is open).
Anything *else* would have to be configured
explicitly. That is how firewalls work, even the
firmware firewall in your ADSL router, if you have one.
>Still you are probably right.I'd bet my last dollar that he's right. None of the symptoms are missing.
./heLen