Kali Linux problema rete kali vs metasploitable

Stato
Discussione chiusa ad ulteriori risposte.
Se non va metti la scheda con connessione bridge, così da sia alla Metasploitable2 che a Kali il solito IP locale 192.168.1.3 per esempio. Dialoga con quei due IP. Se devi fare un port scanning e la Meta ha IP 192.168.1.4 usi Nmap contro quell'IP

Sent from my GT-S7580 using Tapatalk
 
Scrivi su terminale

lspcii -v

Cerca la scheda di rete. Troverai il nome usato dal driver a livello kernel che noi chiameremo KERDRIV. Torna su terminale e scrivi:

>modprobe -r KERDRIV
>modprobe KERDRIV

In questo modo reinizializzi manualmente il driver a livello kernel. Solitamente funziona


lspcii -v
Comando "lspcii" non trovato. Forse si intendeva:
Comando "lspci" dal pacchetto "pciutils" (main)
lspcii: comando non trovato
 
fatto come vedi non funziona ... ora farei come dice cryptoteam ma non ho capito bene cosa devo fare mi potete spiegare passo passo? come si fa a mettere la schededa con connessione bridge ? vi ringrazio in anticipo
 
lspci -v
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
Subsystem: ASUSTeK Computer Inc. P8P67/P8H67 Series Motherboard
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: snb_uncore

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fa000000-fb0fffff
Prefetchable memory behind bridge: 00000000c0000000-00000000d1ffffff
Capabilities: <access denied>
Kernel driver in use: pcieport

00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: ASUSTeK Computer Inc. P8 series motherboard
Flags: bus master, fast devsel, latency 0, IRQ 36
Memory at fb407000 (64-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: mei_me

00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. P8 series motherboard
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at fb406000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci

00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. Device 8444
Flags: bus master, fast devsel, latency 0, IRQ 37
Memory at fb400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Capabilities: <access denied>
Kernel driver in use: pcieport

00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Capabilities: <access denied>
Kernel driver in use: pcieport

00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Capabilities: <access denied>
Kernel driver in use: pcieport

00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
Memory behind bridge: fb300000-fb3fffff
Capabilities: <access denied>
Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=07, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fb200000-fb2fffff
Capabilities: <access denied>

00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fb100000-fb1fffff
Capabilities: <access denied>
Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. P8 series motherboard
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at fb405000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci

00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. Device 844d
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich

00:1f.2 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 4 port SATA IDE Controller (rev 05) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: ASUSTeK Computer Inc. Device 844d
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 20
I/O ports at f0d0
I/O ports at f0c0
I/O ports at f0b0
I/O ports at f0a0
I/O ports at f090
I/O ports at f080
Capabilities: <access denied>
Kernel driver in use: ata_piix

00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. P8 series motherboard
Flags: medium devsel, IRQ 11
Memory at fb404000 (64-bit, non-prefetchable)
I/O ports at f000

00:1f.5 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 2 port SATA IDE Controller (rev 05) (prog-if 85 [Master SecO PriO])
Subsystem: ASUSTeK Computer Inc. Device 844d
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 20
I/O ports at f070
I/O ports at f060
I/O ports at f050
I/O ports at f040
I/O ports at f030
I/O ports at f020
Capabilities: <access denied>
Kernel driver in use: ata_piix

01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])
Flags: bus master, fast devsel, latency 0, IRQ 38
Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at d0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000
Expansion ROM at fb000000 [disabled] [size=512K]
Capabilities: <access denied>
Kernel driver in use: nouveau

01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at fb080000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel

05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. P8B WS Motherboard
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fb300000 (64-bit, non-prefetchable) [size=32K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd

06:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=06, secondary=07, subordinate=07, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fb200000-fb2fffff
Capabilities: <access denied>

07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
I/O ports at d000
Memory at fb220000 (32-bit, non-prefetchable)
Expansion ROM at fb200000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: r8169

08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Device 84b7
Flags: bus master, fast devsel, latency 0, IRQ 35
I/O ports at c050
I/O ports at c040
I/O ports at c030
I/O ports at c020
I/O ports at c000
Memory at fb100000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: ahci
 
Scrivi su terminale

lspcii -v

Cerca la scheda di rete. Troverai il nome usato dal driver a livello kernel che noi chiameremo KERDRIV. Torna su terminale e scrivi:

>modprobe -r KERDRIV
>modprobe KERDRIV

In questo modo reinizializzi manualmente il driver a livello kernel. Solitamente funziona

modprobe -r r8169
modprobe: ERROR: ../libkmod/libkmod-module.c:769 kmod_module_remove_module() could not remove 'r8169': Operation not permitted

utente@linux:~$ modprobe r8169
utente@linux:~$

il secondo comando non da alcun risultato
 
mi scuso in anticipo ma credeo di avere fatto confusione con i terminali ... ho eseguito quei comandi dal terminale del pc e non da quello della vm in cui ho meta e kali ... risultato ora non riesco piu' ad accedere a kali ... mi sono incasinato ...
aprendo kali da vm mi trovo il seguente popup :

p, li { white-space: pre-wrap; }

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/sbin/rcvboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

come posso risolvere ?
 
sudo /sbin/rcvboxdrv setup
[sudo] password for utente:
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...done.
Starting VirtualBox kernel modules ...done.


ho appena provato il suggerimento di kali di cui sopra ed è andato bene solo che kali non lo apre los tesso ...
così ho provato a reinstallare kali ma non ci riesco piu' ... perchè?

dice: passo d'installazione non riuscito
cosa devo fare? ...
 
Stato
Discussione chiusa ad ulteriori risposte.