[Prism54-devel] [Bug 62] New: iwconfig settings must be applied after ifconfig up

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=62

           Summary: iwconfig settings must be applied after ifconfig up
           Product: prim54
           Version: 1.0.2.2
          Platform: ia32
        OS/Version: Linux 2.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Device Driver
        AssignedTo: prism54-devel@prism54.org
        ReportedBy: dan@ddktech.com


I'm using the debian wireless-tools (26+27pre10-1) and a tarball snapshot I 
grabbed on 2/24. 
 
At first, on an ifup eth1, the cards comes up and continually scans (I guess 
looking for APs).  It does find my AP (with WEP turned on and all keys 
programmed) and my neighbor's APs.  It does not lock onto my AP, but continues 
to scan.  No traffic can pass. 
 
An iwconfig eth1 at this point shows all information (key, mode, ESSID, etc...) 
to be correct. 
 
Then, if I go through and issue all the iwconfig commands that are contained in 
/etc/network/interfaces (specifically essid, enc, channel, mode), my NetGear 
WG511 locks onto my AP and traffic passes. 
 
I came across a note by Luis R. Rodriguez in bug#41 that suggested this 
approach, but immediately after Luis' note came a note from ajfa saying this 
should not be necessary. 
 
 
lspci -vvv: 
0d:00.0 Network controller: Harris Semiconductor D-Links DWL-g650 A1 (rev 01) 
        Subsystem: Netgear: Unknown device 4800 
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- 
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- 
        Latency: 80 (2500ns min, 7000ns max) 
        Interrupt: pin A routed to IRQ 11 
        Region 0: Memory at 15000000 (32-bit, non-prefetchable) [size=8K] 
        Capabilities: [dc] Power Management version 1 
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0+,D1+,D2+,D3hot+,D3cold+) 
                Status: D0 PME-Enable- DSel=0 DScale=0 PME- 
 
 
Cardbus Bridge: 
00:03.0 CardBus bridge: Texas Instruments PCI1420 
        Subsystem: Dell Computer Corporation: Unknown device 00b0 
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- 
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- 
        Latency: 168, Cache Line Size: 0x08 (32 bytes) 
        Interrupt: pin A routed to IRQ 11 
        Region 0: Memory at 14000000 (32-bit, non-prefetchable) [size=4K] 
        Bus: primary=00, secondary=09, subordinate=0c, sec-latency=176 
        Memory window 0: 14400000-147ff000 (prefetchable) 
        Memory window 1: 14800000-14bff000 
        I/O window 0: 00004000-000040ff 
        I/O window 1: 00004400-000044ff 
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+ 
        16-bit legacy interface ports at 0001 
 
00:03.1 CardBus bridge: Texas Instruments PCI1420 
        Subsystem: Dell Computer Corporation: Unknown device 00b0 
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- 
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- 
        Latency: 168, Cache Line Size: 0x08 (32 bytes) 
        Interrupt: pin A routed to IRQ 11 
        Region 0: Memory at 14001000 (32-bit, non-prefetchable) [size=4K] 
        Bus: primary=00, secondary=0d, subordinate=10, sec-latency=176 
        Memory window 0: 14c00000-14fff000 (prefetchable) 
        Memory window 1: 15000000-153ff000 
        I/O window 0: 00004800-000048ff 
        I/O window 1: 00004c00-00004cff 
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite+ 
        16-bit legacy interface ports at 0001



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.