14

I have been playing with the aircrack-ng tools, and also Kismet to see how my networks appear.

Kismet creates a monitor interface wlan0mon which it uses for scanning.

With airmon-ng I can create and remove monitor interfaces, but I am unable to remove wlan0mon created by kismet. wlan0mon remains regardless of if I forcefully kill the Kismet process or exit cleanly.

airmon-ng stop wlan0mon

results in a message that monitor mode is disabled for wlan0mon, but I can find no way to remove it.

Can anyone tell me why this is? I am much more interested in learning why I can't remove this interface, although a solution would also be nifty.

I have looked at another similar question which suggested using grimwepa with the verbose switch, but from what I could tell grimwepa never calls to use kismet.

Jay White
  • 289

1 Answers1

15

If your wireless card runs a netlink compatible driver (eg. based on the standard mac80211 stack), you can use the following command to delete the interface:

iw dev wlan0mon del

See iw help output for more info on creating/deleting VIFs:

dev <devname> interface add <name> type <type> [mesh_id <meshid>] [4addr on|off] [flags <flag>*]
phy <phyname> interface add <name> type <type> [mesh_id <meshid>] [4addr on|off] [flags <flag>*]
        Add a new virtual interface with the given configuration.
        Valid interface types are: managed, ibss, monitor, mesh, wds.

        The flags are only used for monitor interfaces, valid flags are:
        none:     no special flags
        fcsfail:  show frames with FCS errors
        control:  show control frames
        otherbss: show frames from other BSSes
        cook:     use cooked mode

        The mesh_id is used only for mesh mode.

dev <devname> del
        Remove this virtual interface
Pablo A
  • 1,733
koniu
  • 616