Kyle E wrote:
> Hello list,
> 
> I have recently installed 4.6 via PXE and FTP. The hardware is a Soekris
> net4501. I am having a problem getting a mini-pci "Intersil Prism
> GT/Duette" wireless card using the pgt driver to work properly. All
> other network interfaces are working fine.
> 
> It appears to associate to the access point (the IP is manually assigned):
> 
> pgt0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         lladdr 00:0c:41:18:c7:bd
>         priority: 4
>         groups: wlan egress
>         media: IEEE802.11 autoselect (OFDM24)
>         status: active
>         ieee80211: nwid XXXXXX chan 5 bssid 00:21:29:ae:56:9d nwkey <not
> displayed> 100dBm
>         inet 192.168.1.50 netmask 0xffffff00 broadcast 192.168.1.255
>         inet6 fe80::20c:41ff:fe18:c7bd%pgt0 prefixlen 64 scopeid 0x6
> 
> and I can see packets being transmitted on the interface with tcpdump:
> 
> tcpdump: listening on pgt0, link-type EN10MB
> 16:41:14.406814 arp who-has 192.168.1.1 tell 192.168.1.50
> 16:41:15.291450 arp who-has 192.168.1.1 tell 192.168.1.50
> 
> I can also use wireshark on another computer to see ARP queries coming
> from the pgt0 interface, and the replies being sent back to it.
> In any case, it seems that the pgt0 interface cannot receive any data.
> 
> Any ideas?
> Thanks very much for any help.
> 
> 
> Here's the dmesg:
> 
> OpenBSD 4.6 (GENERIC) #58: Thu Jul  9 21:24:42 MDT 2009
>     [email protected]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD Am5x86 W/B 133/160 ("AuthenticAMD" 486-class)
> cpu0: FPU
> real mem  = 66678784 (63MB)
> avail mem = 54636544 (52MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 20/80/03, BIOS32 rev. 0 @ 0xf7840
> pcibios0 at bios0: rev 2.0 @ 0xf0000/0x10000
> pcibios0: pcibios_get_intr_routing - function not supported
> pcibios0: PCI IRQ Routing information unavailable.
> pcibios0: PCI bus #0 is the last bus
> bios0: ROM list: 0xc8000/0x9000
> cpu0 at mainbus0: (uniprocessor)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> elansc0 at pci0 dev 0 function 0 "AMD ElanSC520 PCI" rev 0x00: product 0
> stepping 1.1, CPU clock 133MHz, reset 40<SCP>
> gpio0 at elansc0: 32 pins
> pgt0 at pci0 dev 16 function 0 "Intersil Prism GT/Duette" rev 0x01: irq 10
> sis0 at pci0 dev 18 function 0 "NS DP83815 10/100" rev 0x00, DP83816A:
> irq 11, address 00:00:24:ca:4a:0c
> nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1
> sis1 at pci0 dev 19 function 0 "NS DP83815 10/100" rev 0x00, DP83816A:
> irq 5, address 00:00:24:ca:4a:0d
> nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1
> sis2 at pci0 dev 20 function 0 "NS DP83815 10/100" rev 0x00, DP83816A:
> irq 9, address 00:00:24:ca:4a:0e
> nsphyter2 at sis2 phy 0: DP83815 10/100 PHY, rev. 1
> isa0 at mainbus0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard
> wdc0 at isa0 port 0x1f0/8 irq 14
> wd0 at wdc0 channel 0 drive 0: <SanDisk SDCFH-002G>
> wd0: 1-sector PIO, LBA, 1918MB, 3928176 sectors
> wd0(wdc0:0:0): using BIOS timings
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0: <PC speaker>
> spkr0 at pcppi0
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> biomask f1c5 netmask ffe5 ttymask ffff
> softraid0 at root
> root on wd0a swap on wd0b dump on wd0b

Alright, I've tried a few other things and I think I've got a better
idea about what's going on.

This card had been working under a 4.3-stable system, so I tried a clean
install of 4.3-stable to verify that nothing special needed to be done
to make the pgt0 interface work. I found that it does work.

Next, I tried a clean install of 4.4-stable, and found that the problem
immediately reappeared. Looking at the changelog for 4.4, I found this:

"Make sure the 802.11 layer drops unencrypted frames when WEP is on, or
when WPA is on and RX protection for TA is enabled."

This sounds like it could produce my problem, but the access point's
replies look completely normal and all other devices are able to
communicate. Is there any way to find out if this is what's happening? I
suppose the next step is to pick through the revisions between 4.3 and
4.4 in the code from src/sys/net80211/. Is this the correct place? (I'm
kind of new to OpenBSD.)

Thanks

Reply via email to