Bug 553275 - The listen=tcp://127.0.0.1:2501 is ignored
Summary: The listen=tcp://127.0.0.1:2501 is ignored
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kismet
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-07 15:06 UTC by anonymous
Modified: 2010-12-04 00:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:45:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description anonymous 2010-01-07 15:06:16 UTC
Description of problem:

Kismet listens on any interface even though listen=tcp://127.0.0.1:2501 is specified. allowedhosts=127.0.0.1 is also ignored.

=========================================================================
netstat -natp

tcp        0      0 0.0.0.0:2501                0.0.0.0:*                   LISTEN      5469/kismet_server  
tcp        0      0 127.0.0.1:2501              127.0.0.1:59919             ESTABLISHED 5469/kismet_server


kismet.conf
=========================================================================
# Client/server listen config
listen=tcp://127.0.0.1:2501
# People allowed to connect, comma seperated IP addresses or network/mask
# blocks.  Netmasks can be expressed as dotted quad (/255.255.255.0) or as
# numbers (/24)
allowedhosts=127.0.0.1
# Maximum number of concurrent GUI's
maxclients=5
# Maximum backlog before we start throwing out or killing clients.  The
# bigger this number, the more memory and the more power it will use.
maxbacklog=5000

# Server + Drone config options
# dronelisten=tcp://127.0.0.1:3501
# droneallowedhosts=127.0.0.1
# dronemaxclients=5
# droneringlen=65535
============================================================================


Version: kismet-0.0.2009.06.R1-1.fc12.x86_64

Comment 1 Enrico Scholz 2010-01-17 10:04:50 UTC
can you please check the version in testing to see whether problem perists?

Comment 2 anonymous 2010-01-17 19:05:52 UTC
Enrico, I just tested the kismet-0.0.2010.01.R1-1200.fc12.x86_64 version and it's still the same.

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name  
tcp        0      0 127.0.0.1:8834              0.0.0.0:*                   LISTEN      1350/nessusd        
tcp        0      0 0.0.0.0:2501                0.0.0.0:*                   LISTEN      2610/kismet_server  
tcp        0      0 127.0.0.1:2501              127.0.0.1:59768             ESTABLISHED 2610/kismet_server  
tcp        0      0 127.0.0.1:59768             127.0.0.1:2501              ESTABLISHED 2570/kismet_client

Comment 3 Fedora Update System 2010-02-21 13:17:07 UTC
kismet-0.0.2010.01.R1-1201.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/kismet-0.0.2010.01.R1-1201.fc12

Comment 4 Enrico Scholz 2010-02-21 13:28:47 UTC
this update fixes 'listen' only; 'allowedhosts' requires more work and must be solved upstream.

Comment 5 Fedora Update System 2010-02-23 05:29:37 UTC
kismet-0.0.2010.01.R1-1201.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kismet'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-2569

Comment 6 Bug Zapper 2010-11-04 01:38:38 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2010-12-04 00:45:07 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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