On 04/07/2011 09:24 AM, fernando at lozano.eti.br wrote: > and tried disabling SELinux and flusing iptables rules to no effect. What made you think SELinux was at fault? Did it report problems? Try turning it back on and making sure it's set to notify you of any issues, then try again. If you don't get any SELinux alerts, it's not involved.