installare e configurare kismet

Networking, configurazione della connessione, periferiche e condivisioni di rete.
Avatar utente
magozurlinux
Accecante Asceta
Accecante Asceta
Messaggi: 25004
Iscrizione: mercoledì 17 marzo 2010, 17:44
Desktop: xubuntu
Distribuzione: Xubuntu 22.04.3 LTS x86_64
Sesso: Maschile
Località: Pisa

Re: installare e configurare kismet

Messaggio da magozurlinux »

Bisogna fare questa prova; da terminale dai questi comandi:

Codice: Seleziona tutto

sudo apt-get purge bcmwl-kernel-source broadcom-sta-common broadcom-sta-source

Codice: Seleziona tutto

sudo apt-get install b43-fwcutter firmware-b43-installer
riavvia il portatile.
Xubuntu 22.04 LTS - saluti da magozurlinux a tutti gli utenti del forum :ciao:
Avatar utente
Musashi73
Prode Principiante
Messaggi: 62
Iscrizione: lunedì 12 ottobre 2015, 7:38
Desktop: Ubuntu
Distribuzione: Ubuntu 20.04LTS
Sesso: Maschile

Re: installare e configurare kismet

Messaggio da Musashi73 »

Ciao,

priam di tutto scusa per il ritardo. Ho eseguito i comandi che mi hai rilasciato, tutto sembrava funzionare ma dopo un secondo o un terzo riavvio sembra esserci qualche problema.
  • Quando avvio il pc dopo il caricamento del GRUB appare un messaggio riferito al driver installati della scheda wifi:

    Codice: Seleziona tutto

    Support for cores revision 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=1
Immagine


La schermata appare con le reti wifi ma non si vedono la trasmissione dei pacchetti. Dopo l'installazione del driver funzionava, ma successivamente non ha più funzionato
Immagine

Quando Kismet si collega alla mia rete wifi, subito dopo si disconette e si collega con un'altra rete wifi del piano inferiore (quella di mio fratello). Mi appare il seguente messaggio
Immagine

Grazie per il tuo importante aiuto e scusa per il disturbo
Avatar utente
magozurlinux
Accecante Asceta
Accecante Asceta
Messaggi: 25004
Iscrizione: mercoledì 17 marzo 2010, 17:44
Desktop: xubuntu
Distribuzione: Xubuntu 22.04.3 LTS x86_64
Sesso: Maschile
Località: Pisa

Re: installare e configurare kismet

Messaggio da magozurlinux »

Prova a dare questi comandi:

Codice: Seleziona tutto

sudo ifconfig wlan0 down

Codice: Seleziona tutto

sudo modprobe -r b43

Codice: Seleziona tutto

sudo modprobe b43

Codice: Seleziona tutto

sudo ifconfig wlan0 up
riavvia kismet
Xubuntu 22.04 LTS - saluti da magozurlinux a tutti gli utenti del forum :ciao:
Avatar utente
Musashi73
Prode Principiante
Messaggi: 62
Iscrizione: lunedì 12 ottobre 2015, 7:38
Desktop: Ubuntu
Distribuzione: Ubuntu 20.04LTS
Sesso: Maschile

Re: installare e configurare kismet

Messaggio da Musashi73 »

Come vedi a volte sembra funzionare
Immagine
ma poi si disconnette
Immagine
e si connette ad un'altra connessione/router wifi e mi appare il solito messaggio
Immagine
Penso che siamo quasi alla configurazione finale, sicuramente manca qualcosina da modificare.
Avatar utente
Musashi73
Prode Principiante
Messaggi: 62
Iscrizione: lunedì 12 ottobre 2015, 7:38
Desktop: Ubuntu
Distribuzione: Ubuntu 20.04LTS
Sesso: Maschile

Re: installare e configurare kismet

Messaggio da Musashi73 »

Ciao,

ho fatto la prova collegando il cavo di rete e adesso sembra funzionare
Immagine

Cosa sono "autogroupe probe" e "autogroup data"?

Grazie per il tuo utile aiuto. :ciao:
Avatar utente
magozurlinux
Accecante Asceta
Accecante Asceta
Messaggi: 25004
Iscrizione: mercoledì 17 marzo 2010, 17:44
Desktop: xubuntu
Distribuzione: Xubuntu 22.04.3 LTS x86_64
Sesso: Maschile
Località: Pisa

Re: installare e configurare kismet

Messaggio da magozurlinux »

Prego, di nulla!

autogroupe probe si riferisce agli ESSID o SSID delle reti wireless rilevate;

autogroup data si riferisce ai pacchetti data ricevuti tramite lo sniffing della rete senza fili bersaglio.

Hai installato aircrack-ng per crackare le reti wireless?
Xubuntu 22.04 LTS - saluti da magozurlinux a tutti gli utenti del forum :ciao:
Avatar utente
Musashi73
Prode Principiante
Messaggi: 62
Iscrizione: lunedì 12 ottobre 2015, 7:38
Desktop: Ubuntu
Distribuzione: Ubuntu 20.04LTS
Sesso: Maschile

Re: installare e configurare kismet

Messaggio da Musashi73 »

Ancora no, ma se lo installo cosa posso fare con questo programma?
Avatar utente
magozurlinux
Accecante Asceta
Accecante Asceta
Messaggi: 25004
Iscrizione: mercoledì 17 marzo 2010, 17:44
Desktop: xubuntu
Distribuzione: Xubuntu 22.04.3 LTS x86_64
Sesso: Maschile
Località: Pisa

Re: installare e configurare kismet

Messaggio da magozurlinux »

crackare le reti wireless con chiave di protezione WEP e WPA.
Xubuntu 22.04 LTS - saluti da magozurlinux a tutti gli utenti del forum :ciao:
cavitillo
Scoppiettante Seguace
Scoppiettante Seguace
Messaggi: 258
Iscrizione: lunedì 6 febbraio 2006, 9:18
Desktop: Mate
Distribuzione: Ubuntu 18.04.3 LTS x86_64
Sesso: Maschile

Re: installare e configurare kismet

Messaggio da cavitillo »

Ciao, anche a me si è verificato lo stesso errore di Musashi73 nel senso che kismet non riesce a connettersi al server e poi si aprono finestre da configurare.

Codice: Seleziona tutto

lspci -nn | grep -i net
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)
04:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)

Codice: Seleziona tutto

sudo lshw -C network: 
  *-network               
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 07
       serial: 60:a4:4c:7d:14:4d
       size: 10Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8168e-3_0.0.4 03/27/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
       resources: irq:31 ioport:d000(size=256) memory:d00fb000-d00fbfff memory:d0000000-d0003fff
  *-network
       description: Wireless interface
       product: AR9485 Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: wlp4s0
       version: 01
       serial: 2c:d0:5a:5a:11:09
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=4.2.0-25-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
       resources: irq:17 memory:ff900000-ff97ffff memory:ff980000-ff98ffff
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: wwx582c80139263
       serial: 58:2c:80:13:92:63
       capabilities: ethernet physical
       configuration: broadcast=yes driver=huawei_cdc_ncm driverversion=22-Aug-2005 firmware=Huawei CDC NCM device link=no multicast=yes
Ho modificato anche il file

Codice: Seleziona tutto

sudo gedit /etc/kismet/kismet.conf
aggiungendo questa riga:

Codice: Seleziona tutto

ncsource=wlan0:name=qualcomm
e non c'è stato nulla da fare, il problema persiste :ciao:
Allegati
kismet.png
Ogni cosa a suo tempo!
Avatar utente
magozurlinux
Accecante Asceta
Accecante Asceta
Messaggi: 25004
Iscrizione: mercoledì 17 marzo 2010, 17:44
Desktop: xubuntu
Distribuzione: Xubuntu 22.04.3 LTS x86_64
Sesso: Maschile
Località: Pisa

Re: installare e configurare kismet

Messaggio da magozurlinux »

Ciao.

Da terminale dai questi comandi:

Codice: Seleziona tutto

sudo gedit /etc/kismet/kismet.conf
vai nella riga che hai aggiunto:

Codice: Seleziona tutto

ncsource=wlan0:name=qualcomm
il dispositivo della tua rete wireless non è wlan0 ma wlp4s0; modificala così:

Codice: Seleziona tutto

ncsource=wlp4s0:name=atheros
salva ed esci dall'editor di testo.

Codice: Seleziona tutto

sudo kismet
Xubuntu 22.04 LTS - saluti da magozurlinux a tutti gli utenti del forum :ciao:
cavitillo
Scoppiettante Seguace
Scoppiettante Seguace
Messaggi: 258
Iscrizione: lunedì 6 febbraio 2006, 9:18
Desktop: Mate
Distribuzione: Ubuntu 18.04.3 LTS x86_64
Sesso: Maschile

Re: installare e configurare kismet

Messaggio da cavitillo »

Stesso problema connection refused. :muro: Per utilizzare kismet so che devo impostare la mia scheda wireless in monitor mode e questo l'ho fatto, quando l'ho lanciato però era attiva anche una connessione con chiavetta usb. Va bene così oppure deve lavorare solo la wireless in monitor mode?
Ogni cosa a suo tempo!
Avatar utente
magozurlinux
Accecante Asceta
Accecante Asceta
Messaggi: 25004
Iscrizione: mercoledì 17 marzo 2010, 17:44
Desktop: xubuntu
Distribuzione: Xubuntu 22.04.3 LTS x86_64
Sesso: Maschile
Località: Pisa

Re: installare e configurare kismet

Messaggio da magozurlinux »

Deve lavorare solo la scheda wireless atheros in monitor mode.

Da terminale postami questo comando:

Codice: Seleziona tutto

cat /etc/kismet/kismet.conf
Xubuntu 22.04 LTS - saluti da magozurlinux a tutti gli utenti del forum :ciao:
cavitillo
Scoppiettante Seguace
Scoppiettante Seguace
Messaggi: 258
Iscrizione: lunedì 6 febbraio 2006, 9:18
Desktop: Mate
Distribuzione: Ubuntu 18.04.3 LTS x86_64
Sesso: Maschile

Re: installare e configurare kismet

Messaggio da cavitillo »

Codice: Seleziona tutto

 cat /etc/kismet/kismet.conf
# Kismet config file
# Most of the "static" configs have been moved to here -- the command line
# config was getting way too crowded and cryptic.  We want functionality,
# not continually reading --help!

# Version of Kismet config
version=2009-newcore

# Name of server (Purely for organizational purposes)
# If commented out, defaults to host name of system
# servername=Kismet Server


# Prefix of where we log (as used in the logtemplate later)
# logprefix=/some/path/to/logs

# Do we process the contents of data frames?  If this is enabled, data
# frames will be truncated to the headers only immediately after frame type
# detection.  This will disable IP detection, etc, however it is likely
# safer (and definitely more polite) if monitoring networks you do not own.
# hidedata=true

# Do we allow plugins to be used?  This will load plugins from the system
# and user plugin directiories when set to true (See the README for the default
# plugin locations).
allowplugins=true

# See the README for full information on the new source format
# ncsource=interface:options
# for example:
# ncsource=wlan0
# ncsource=wifi0:type=madwifi
# ncsource=wlan0:name=intel,hop=false,channel=11
ncsource=wlp4s0:name=atheros


# Comma-separated list of sources to enable.  This is only needed if you defined
# multiple sources and only want to enable some of them.  By default, all defined
# sources are enabled.
# For example, if sources with name=prismsource and name=ciscosource are defined,
# and you only want to enable those two:
# enablesources=prismsource,ciscosource

# Control which channels we like to spend more time on.  By default, the list
# of channels is pulled from the driver automatically.  By setting preferred channels,
# if they are present in the channel list, they'll be set with a timing delay so that
# more time is spent on them.  Since 1, 6, 11 are the common default channels, it makes
# sense to spend more time monitoring them.
# For finer control, see further down in the config for the channellist= directives.
preferredchannels=1,6,11

# How many channels per second do we hop?  (1-10)
channelvelocity=3

# By setting the dwell time for channel hopping we override the channelvelocity
# setting above and dwell on each channel for the given number of seconds.
#channeldwell=10

# Channels are defined as:
# channellist=name:ch1,ch2,ch3
# or
# channellist=name:range-start-end-width-offset,ch,range,ch,...
#
# Channels may be a numeric channel or a frequency
#
# Channels may specify an additional wait period.  For common default channels,
# an additional wait period can be useful.  Wait periods delay for that number 
# of times per second - so a configuration hopping 10 times per second with a
# channel of 6:3 would delay 3/10ths of a second on channel 6.
#
# Channel lists may have up to 256 channels and ranges (combined).  For power 
# users scanning more than 256 channels with a single card, ranges must be used.
#
# Ranges are meant for "power users" who wish to define a very large number of
# channels.  A range may specify channels or frequencies, and will automatically
# sort themselves to cover channels in a non-overlapping fashion.  An example
# range for the normal 802.11b/g spectrum would be:
#
# range-1-11-3-1
#
# which indicates starting at 1, ending at 11, a channel width of 3 channels,
# incrementing by one.  A frequency based definition would be:
#
# range-2412-2462-22-5
#
# since 11g channels are 22 mhz wide and 5 mhz apart.
#
# Ranges have the flaw that they cannot be shared between sources in a non-overlapping
# way, so multiple sources using the same range may hop in lockstep with each other
# and duplicate the coverage.
#
# channellist=demo:1:3,6:3,11:3,range-5000-6000-20-10

# Default channel lists
# These channel lists MUST BE PRESENT for Kismet to work properly.  While it is
# possible to change these, it is not recommended.  These are used when the supported
# channel list can not be found for the source; to force using these instead of
# the detected supported channels, override with channellist= in the source defintion
#
# IN GENERAL, if you think you want to modify these, what you REALLY want to do is
# copy them and use channellist= in the packet source.
channellist=IEEE80211b:1:3,6:3,11:3,2,7,3,8,4,9,5,10
channellist=IEEE80211a:36,40,44,48,52,56,60,64,149,153,157,161,165
channellist=IEEE80211ab:1:3,6:3,11:3,2,7,3,8,4,9,5,10,36,40,44,48,52,56,60,64,149,153,157,161,165

# 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.  To have a Kismet server export live packets
# as if it were a drone, uncomment these.
# dronelisten=tcp://127.0.0.1:3501
# droneallowedhosts=127.0.0.1
# dronemaxclients=5
# droneringlen=65535

# OUI file, expected format 00:11:22<tab>manufname
# IEEE OUI file used to look up manufacturer info.  We default to the
# wireshark one since most people have that.
ouifile=/etc/manuf
ouifile=/usr/share/wireshark/wireshark/manuf
ouifile=/usr/share/wireshark/manuf
ouifile=/Applications/Wireshark.app/Contents/Resources/share/wireshark/manuf

# Do we have a GPS?
gps=true
# Do we use a locally serial attached GPS, or use a gpsd server, or
# use a fixed virtual gps?
# (Pick only one)
gpstype=gpsd
# Host:port that GPSD is running on.  This can be localhost OR remote!
gpshost=localhost:2947


# gpstype=serial
# What serial device do we look for the GPS on?
# gpsdevice=/dev/rfcomm0

# gpstype=virtual
# gpsposition=100,-50
# gpsaltitude=1234

# Do we lock the mode?  This overrides coordinates of lock "0", which will
# generate some bad information until you get a GPS lock, but it will 
# fix problems with GPS units with broken NMEA that report lock 0
gpsmodelock=false
# Do we try to reconnect if we lose our link to the GPS, or do we just
# let it die and be disabled?
gpsreconnect=true

# Do we export packets over tun/tap virtual interfaces?
tuntap_export=false
# What virtual interface do we use
tuntap_device=kistap0

# Packet filtering options:
# filter_tracker - Packets filtered from the tracker are not processed or
#                  recorded in any way.
# filter_export  - Controls what packets influence the exported CSV, network,
#                  xml, gps, etc files.
# All filtering options take arguments containing the type of address and
# addresses to be filtered.  Valid address types are 'ANY', 'BSSID',
# 'SOURCE', and 'DEST'.  Filtering can be inverted by the use of '!' before
# the address.  For example,
# filter_tracker=ANY(!"00:00:DE:AD:BE:EF")
# has the same effect as the previous mac_filter config file option.
# filter_tracker=...
# filter_dump=...
# filter_export=...
# filter_netclient=...

# Alerts to be reported and the throttling rates.
# alert=name,throttle/unit,burst
# The throttle/unit describes the number of alerts of this type that are
# sent per time unit.  Valid time units are second, minute, hour, and day.
# Burst describes the number of alerts sent before throttling takes place.
# For example:
# alert=FOO,10/min,5
# Would allow 5 alerts through before throttling is enabled, and will then
# limit the number of alerts to 10 per minute.
# A throttle rate of 0 disables throttling of the alert.
# See the README for a list of alert types.
alert=ADHOCCONFLICT,5/min,1/sec
alert=AIRJACKSSID,5/min,1/sec
alert=APSPOOF,10/min,1/sec
alert=BCASTDISCON,5/min,2/sec
alert=BSSTIMESTAMP,5/min,1/sec
alert=CHANCHANGE,5/min,1/sec
alert=CRYPTODROP,5/min,1/sec
alert=DISASSOCTRAFFIC,10/min,1/sec
alert=DEAUTHFLOOD,5/min,2/sec
alert=DEAUTHCODEINVALID,5/min,1/sec
alert=DISCONCODEINVALID,5/min,1/sec
alert=DHCPNAMECHANGE,5/min,1/sec
alert=DHCPOSCHANGE,5/min,1/sec
alert=DHCPCLIENTID,5/min,1/sec
alert=DHCPCONFLICT,10/min,1/sec
alert=NETSTUMBLER,5/min,1/sec
alert=LUCENTTEST,5/min,1/sec
alert=LONGSSID,5/min,1/sec
alert=MSFBCOMSSID,5/min,1/sec
alert=MSFDLINKRATE,5/min,1/sec
alert=MSFNETGEARBEACON,5/min,1/sec
alert=NULLPROBERESP,5/min,1/sec
#alert=PROBENOJOIN,5/min,1/sec

# Controls behavior of the APSPOOF alert.  SSID may be a literal match (ssid=) or
# a regex (ssidregex=) if PCRE was available when kismet was built.  The allowed 
# MAC list must be comma-separated and enclosed in quotes if there are multiple 
# MAC addresses allowed.  MAC address masks are allowed.
apspoof=Foo1:ssidregex="(?i:foobar)",validmacs=00:11:22:33:44:55
apspoof=Foo2:ssid="Foobar",validmacs="00:11:22:33:44:55,aa:bb:cc:dd:ee:ff"

# Known WEP keys to decrypt, bssid,hexkey.  This is only for networks where
# the keys are already known, and it may impact throughput on slower hardware.
# Multiple wepkey lines may be used for multiple BSSIDs.
# wepkey=00:DE:AD:C0:DE:00,FEEDFACEDEADBEEF01020304050607080900

# Is transmission of the keys to the client allowed?  This may be a security
# risk for some.  If you disable this, you will not be able to query keys from
# a client.
allowkeytransmit=true

# How often (in seconds) do we write all our data files (0 to disable)
writeinterval=300

# Do we use sound?
# Not to be confused with GUI sound parameter, this controls wether or not the
# server itself will play sound.  Primarily for headless or automated systems.
enablesound=false
# Path to sound player
soundbin=play

sound=newnet,true
sound=newcryptnet,true
sound=packet,true
sound=gpslock,true
sound=gpslost,true
sound=alert,true

# Does the server have speech? (Again, not to be confused with the GUI's speech)
enablespeech=false
# Binary used for speech (if not in path, full path must be specified)
speechbin=flite
# Specify raw or festival; Flite (and anything else that doesn't need formatting
# around the string to speak) is 'raw', festival requires the string be wrapped in
# SayText("...")
speechtype=raw

# How do we speak?  Valid options:
# speech    Normal speech
# nato      NATO spellings (alpha, bravo, charlie)
# spell     Spell the letters out (aye, bee, sea)
speechencoding=nato

speech=new,"New network detected s.s.i.d. %1 channel %2"
speech=alert,"Alert %1"
speech=gpslost,"G.P.S. signal lost"
speech=gpslock,"G.P.S. signal O.K."

# How many alerts do we backlog for new clients?  Only change this if you have
# a -very- low memory system and need those extra bytes, or if you have a high
# memory system and a huge number of alert conditions.
alertbacklog=50

# File types to log, comma seperated.  Built-in log file types:
# alert				Text file of alerts
# gpsxml			XML per-packet GPS log
# nettxt			Networks in text format
# netxml			Networks in XML format
# pcapdump			tcpdump/wireshark compatible pcap log file
# string			All strings seen (increases CPU load)
logtypes=pcapdump,gpsxml,netxml,nettxt,alert

# Format of the pcap dump (PPI or 80211)
pcapdumpformat=ppi
# pcapdumpformat=80211

# Default log title
logdefault=Kismet

# logtemplate - Filename logging template.
# This is, at first glance, really nasty and ugly, but you'll hardly ever
# have to touch it so don't complain too much.
#
# %p is replaced by the logging prefix + '/'
# %n is replaced by the logging instance name
# %d is replaced by the starting date as Mon-DD-YYYY
# %D is replaced by the current date as YYYYMMDD
# %t is replaced by the starting time as HH-MM-SS
# %i is replaced by the increment log in the case of multiple logs
# %l is replaced by the log type (pcapdump, strings, etc)
# %h is replaced by the home directory

logtemplate=%p%n-%D-%t-%i.%l

# Where state info, etc, is stored.  You shouldnt ever need to change this.
# This is a directory.
configdir=%h/.kismet/
:ciao:
Ogni cosa a suo tempo!
Scrivi risposta

Ritorna a “Connessione e configurazione delle reti”

Chi c’è in linea

Visualizzano questa sezione: 0 utenti iscritti e 5 ospiti