Hide Forgot
On my IRC proxy server machine I run Bitlbee - http://www.bitlbee.org/main.php/news.r.html - which proxies IM traffic and serves it out as IRC traffic, and I *also* run Bip - http://bip.milkypond.org/ - which is a classic IRC bouncer. I have Bip connected to some 'normal' IRC servers - Freenode, GIMPNet et al - but also to the Bitlbee server running on the same machine. I just updated Bip and on restart it's suddenly failing, with an SELinux denial: Apr 13 14:50:46 ircproxy kernel: [1130671.241638] type=1400 audit(1334353846.325:24): avc: denied { name_bind } for pid=27865 comm="bip" src=17037 scontext=system_u:system_r:bitlbee_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket it never used to do so. Is this a policy bug? Or do we need to ship some kind of policy in the Bip and/or Bitlbee package(s) to allow this? Or is it just something I need to enable as a sysadmin? Thanks!
Did you setup 17037/tcp port?
i picked the port, yeah. it's arbitrary. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
bip's default is 6667, the standard IRC port.
Then you need to execute semanage port -a -t ircd_port_t -p tcp 17037