Bug 744057 - bitlbee doesnt listen on all interfaces
Summary: bitlbee doesnt listen on all interfaces
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bitlbee
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 20:42 UTC by Joakim Verona
Modified: 2018-04-11 11:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-21 11:49:31 UTC
Type: ---


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.