linux - How to know my wireless card has injection enabled?

I am playing around with aircrack.

And was trying to see whether my wireless card on my laptop can pass the injection test

And I end up seeing the following... does it mean my wireless card is not able to run aircrack?

root@myubuntu:/home/myubuntu# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11bg  ESSID:""  Nickname:""
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated   
          Bit Rate:54 Mb/s   Tx-Power:24 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=5/5  Signal level=0 dBm  Noise level=-57 dBm
          Rx invalid nwid:0  Rx invalid crypt:781  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@myubuntu:/home/myubuntu#  aireplay-ng -9 eth1
ioctl(SIOCSIWMODE) failed: Invalid argument

ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead.  Make
sure RFMON is enabled: run 'airmon-ng start eth1 <#>'
Sysfs injection support was not found either.

root@myubuntu:/home/myubuntu# 

Answer

From the output you displayed above, your current driver is not capable of packet injection. This is because you probably used the default (closed-source) drivers, many of which do not support injection.

You need to use the compat-wireless package, to compile your own drivers and use those instead (after uninstalling your current drivers). See this page from the Aircrack-ng Wiki which details how to compile your own drivers, as well as patch them to allow packet injection. At minimum, you need the mac80211.compat08082009.wl_frag+ack_v1.patch patch, as detailed in the wiki article linked above. Note that you should call the driver select script before compiling/installing.

As a side note, these drivers will also change the interface name from eth1 to wlan0 (which is also a lot more intuitive name). Depending on your card, the monitor interface name might be mon0 (increasing in number with each additional monitoring interface you create with airmon-ng start).