Bug 744057

Summary:	bitlbee doesnt listen on all interfaces
Product:	[Fedora] Fedora	Reporter:	Joakim Verona <joakim>
Component:	bitlbee	Assignee:	Robert Scheck <redhat-bugzilla>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	mcepl, mcepl, redhat-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-21 11:49:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joakim Verona 2011-10-06 20:42:45 UTC

Description of problem:

bitlbee doesnt listen on all interfaces only the loopback one.


Version-Release number of selected component (if applicable):


How reproducible:

always

Steps to Reproduce:
1. start bitlbee
2. connect to bitlbee from another machine
3. connection fails
  
Actual results:

connection fails

Expected results:

that connection works

Additional info:

if I change the service file it works:
ExecStart=/usr/sbin/bitlbee -D -n -i 0.0.0.0

according to bitlbee docs listening on all interfaces is default.

as it is now bitlbee is only usable on localhost. Thats an important usecase,
but connecting from other machines is also important.

Comment 1 Matěj Cepl 2012-06-21 11:49:31 UTC

This is actually intentional. For normal users we don't want to create a security risk of opening yet another port on their system, and if you are brave enough to run bitlbee as a publicly accessible (or LAN-accessible for that matter) so you are ready to deal with firewalls etc., then you should be smart enough to make a simple change to the service file.