OpenWrt Forum Archive

Topic: wl scan, error "eth1: Invalid argument"

The content of this topic has been archived on 8 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi!

I've just buy a WRT54GS v1.1 and installed the latest experimental build avaible:
Linux OpenWrt 2.4.30 #1 Sat Apr 23 18:13:56 EDT 2005 mips unknown
I've installed the wl tool from here:
http://wrt54g.free.fr/openwrt/b4/ipkg/

When I try to issue a scan command (wl scan), I have this message:
root@OpenWrt:/etc# wl scan
eth1: Invalid argument
scan    Initiate an active scan across all channels.
        Optional SSID argument specifies a particular SSID to scan.
        With no SSID argument, a broadcast SSID scan is performed.

I've try the reseting to default command (mtd erase nvram) and after a boot in falsafe mode to erase the j2ffs partition (firstboot) but the problem is still here.

Any idea ?
Thanks you for your help.

Olivier

I have recieved this error when the wrt is not in client mode. When placed in the client mode as oposed to ap mode, it works as expected.

commands:
wl ap 0

or

nvram set wl0_mode=sta
nvram commit
reboot

After the wrt is in client mode, then you can run wl scan and it should work.

Randy

I've try to put the wrt in client mode with the command nvram set wl0_mode=sta but it's the same.

Here is my nvram:

root@OpenWrt:~# nvram show
size: 2015 bytes (30753 left)
wl0_net_mode=mixed
os_ram_addr=80001000
wl0_frameburst=off
boardrev=0x10
il0macaddr=00:13:10:30:24:e4
bootnv_ver=2
et0macaddr=00:13:10:30:24:E2
boot_wait=on
watchdog=5000
wl0_infra=1
wl0_country_code=AU
et0mdcport=0
pmon_ver=CFE 3.61.13.0
wl0_ifname=eth1
gpio5=robo_reset
vlan0ports=1 2 3 4 5*
wl0_mode=sta
wl0_ap_isolate=0
os_flash_addr=bfc40000
wl0_gmode=1
sromrev=2
boardtype=0x0708
lan_netmask=255.255.255.0
wl0_dtim=1
wl0_ssid=OpenWrt
wl0_key1=
wl0id=0x4320
wl0_key2=
wl0_key3=
wl0_key4=
ag0=255
wl0_plcphdr=long
wl0_rate=0
wl0_closed=0
wl0_macmode=disabled
wl0_radioids=BCM2050
wl0_phytype=g
wl0gpio2=0
wl0_lazywds=0
wl0gpio3=0
boardflags2=0
wl0_afterburner=auto
wl0_antdiv=-1
wl0_wpa_psk=
wl0_unit=0
wl_country_code=AU
pa0itssit=62
wl0_wds=
cctl=0
wl0_radius_port=1812
wl0_auth=0
wl0_radius_ipaddr=
pa0maxpwr=0x4e
clkfreq=200
lan_ipaddr=10.0.0.1
vlan1hwname=et0
aa0=3
wl0_phytypes=g
wl0_frag=2346
wl0_wep=disabled
sdram_config=0x0062
wl0_country=
vlan1ports=0 5
scratch=a0180000
ccode=0
wl0_rateset=default
eou_device_id=DFEYNYIN
boardflags=0x0318
sdram_refresh=0x0000
sdram_ncdl=0xfdff08
wl0_rts=2347
wl0_wpa_gtk_rekey=3600
wl0_key=1
et0phyaddr=30
wl0_radio=1
wl0_bcn=100
wl0_hwaddr=00:13:10:30:24:E4
wl0_gmode_protection=auto
pa0b0=0x15eb
wl0_maclist=
pa0b1=0xfa82
pa0b2=0xfe66
sdram_init=0x000b
vlan0hwname=et0
dl_ram_addr=a0001000
wl0_radius_key=
wl0_corerev=7
wl0_channel=11
wl0_auth_mode=open
boot_ver=v3.4
wl0_crypto=tkip
boardnum=42

Thanks for your help.

Olivier

What happens when you type "wl ap"? It should return somthing similar to "ap mode is 0 (off)"

Randy

rridley wrote:

What happens when you type "wl ap"? It should return somthing similar to "ap mode is 0 (off)"

Randy

It returns 0.

root@OpenWrt:~# wl ap
ap is 0 (off)

Olivier

Another strange think, the power led is flashing...

Don't understand anythink... If you have an idea...

Thanks for your help.

Olivier

The discussion might have continued from here.