rum wireless adapter in hostap mode

[Hugo Osvaldo Barrera]

I'm trying to set up a small box as an 802.11g AP, but there seems to
be something wrong.
Regrettably, the only devices close by I have to test the connection are
-A Windows XP PC
-A Windows 7 PC
-A PSP
I'm pretty sure the problem isn't any of the clients anyway.
For testing purposes, I'm running a totally insecure network. I'll add
the WPA stuff later.

When I try to connect from the PSP I get an error message saying
"Check the security settings for the network and try again". It DOES
auto-detect is as "security:none" though.
When I try to connect from one of the windows PC, I get the typical
really helpful message saying "Could not connect to the network"

Network card is a D-Link DWA-110.
It's an Atom-based mini-ITX PC.

This is my configuration (Hope I didn't leave anything out):

# ifconfig rum0
rum0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:22:b0:54:21:0b
        priority: 4
        groups: wlan
        media: IEEE802.11 autoselect mode 11g hostap
        status: active
        ieee80211: nwid CasaDeHugo chan 11 bssid 00:22:b0:54:21:0b 100dBm
        inet6 fe80::222:b0ff:fe54:210b%rum0 prefixlen 64 scopeid 0x4
        inet 172.16.0.1 netmask 0xffff0000 broadcast 172.16.0.255
# cat /etc/hostname.rum0
# /etc/hostname.rum0
inet 172.16.0.1 255.255.0.0 172.16.0.255 media autoselect mediaopt
hostap mode 11g chan 11 nwid CasaDeHugo

Comment: I've tried with the "-wpa -wpapsk" as well, just in case,
though I believe it's not really necessary if I haven't used WPA just
before
Also, I HAVE run
  # sh /etc/netstart rum0
after editing the file (just in case :D)



# dmesg
OpenBSD 4.6 (GENERIC.MP) #81: Thu Jul  9 21:26:19 MDT 2009
    deraadt@...:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2135109632 (2036MB)
avail mem = 2060738560 (1965MB)
RTC BIOS diagnostic error 80<clock_battery>
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe3590 (23 entries)
bios0: vendor Intel Corp. version "LF94510J.86A.0140.2008.1231.0012"
date 12/31/2008
bios0: Intel Corporation D945GCLF2D
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC WDDT MCFG ASF!
acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S4) UAR2(S4) PEX0(S4)
PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) PEX5(S4) UHC1(S3) UHC2(S3)
UHC3(S3) UHC4(S3) EHCI(S3) AC9M(S4) AZAL(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1596.36 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,CX16,xTPR,NXE,LONG
cpu0: 512KB 64b/line 16-way L2 cache
cpu0: apic clock running at 134MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1612.08 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,CX16,xTPR,NXE,LONG
cpu1: 512KB 64b/line 16-way L2 cache
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1612.08 MHz
cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,CX16,xTPR,NXE,LONG
cpu2: 512KB 64b/line 16-way L2 cache
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1612.08 MHz
cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,CX16,xTPR,NXE,LONG
cpu3: 512KB 64b/line 16-way L2 cache
ioapic0 at mainbus0 apid 2 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P32_)
acpiprt2 at acpi0: bus 1 (PEX0)
acpiprt3 at acpi0: bus -1 (PEX1)
acpiprt4 at acpi0: bus 2 (PEX2)
acpiprt5 at acpi0: bus 3 (PEX3)
acpiprt6 at acpi0: bus -1 (PEX4)
acpiprt7 at acpi0: bus -1 (PEX5)
acpicpu0 at acpi0
acpicpu1 at acpi0
acpicpu2 at acpi0
acpicpu3 at acpi0
acpibtn0 at acpi0: SLPB
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82945G Host" rev 0x02
vga1 at pci0 dev 2 function 0 "Intel 82945G Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0x80000000, size 0x10000000
inteldrm0 at vga1: apic 2 int 16 (irq 11)
drm0 at inteldrm0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: apic 2
int 17 (irq 255)
pci1 at ppb0 bus 1
re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x02: RTL8168C/8111C
(0x3c00), apic 2 int 16 (irq 11), address 00:1c:c0:c8:ce:49
rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2
ppb1 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x01: apic 2
int 18 (irq 255)
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x01: apic 2
int 19 (irq 255)
pci3 at ppb2 bus 3
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2
int 23 (irq 9)
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 2
int 19 (irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2
int 18 (irq 11)
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2
int 16 (irq 11)
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 2
int 23 (irq 9)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xe1
pci4 at ppb3 bus 4
pcib0 at pci0 dev 31 function 0 "Intel 82801GB LPC" rev 0x01
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x01: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 ignored (disabled)
pciide1 at pci0 dev 31 function 2 "Intel 82801GB SATA" rev 0x01: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using apic 2 int 19 (irq 10) for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: <WDC WD1600AAJS-00L7A0>
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x01: apic
2 int 19 (irq 10)
iic0 at ichiic0
admtm0 at iic0 addr 0x2d: 47m192
spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL5
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
mtrr: Pentium Pro MTRR support
rum0 at uhub0 port 4 "Ralink 802.11 bg WLAN" rev 2.00/0.01 addr 2
rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:22:b0:54:21:0b
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
uhidev0 at uhub3 port 1 configuration 1 interface 0 " USB Keyboard"
rev 1.10/2.80 addr 2
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub3 port 1 configuration 1 interface 1 " USB Keyboard"
rev 1.10/2.80 addr 2
uhidev1: iclass 3/0, 2 report ids
uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 2: input=3, output=0, feature=0
wskbd1: disconnecting from wsdisplay0
wskbd1 detached
ukbd0 detached
uhidev0 detached
uhid0 detached
uhid1 detached
uhidev1 detached
ehci_idone: ex=0xffff8000001f7600 is done!
ehci_idone: ex=0xffff8000002aaa00 is done!

[Bryan Brake]

On Thu, Nov 5, 2009 at 20:00, Hugo Osvaldo Barrera
<hugo@...> wrote:

> I'm trying to set up a small box as an 802.11g AP, but there seems to
> be something wrong.
> Regrettably, the only devices close by I have to test the connection are
> -A Windows XP PC
> -A Windows 7 PC
> -A PSP
> I'm pretty sure the problem isn't any of the clients anyway.
> For testing purposes, I'm running a totally insecure network. I'll add
> the WPA stuff later.
>
> When I try to connect from the PSP I get an error message saying
> "Check the security settings for the network and try again". It DOES
> auto-detect is as "security:none" though.
> When I try to connect from one of the windows PC, I get the typical
> really helpful message saying "Could not connect to the network"

<snipped...>


> ehci_idone: ex=0xffff8000001f7600 is done!
> ehci_idone: ex=0xffff8000002aaa00 is done!
>
>

RTFM:
http://www.openbsd.org/cgi-bin/man.cgi?query=rum&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html

I like the part that says:

 The rum driver supports automatic control of the transmit speed in BSS
     mode only.  Therefore the use of a rum adapter in Host AP mode is dis-
     couraged.

     Host AP mode doesn't support power saving.  Clients attempting to use
     power saving mode may experience significant packet loss (disabling power
     saving on the client will fix this).

[Hugo Osvaldo Barrera]

On Fri, Nov 6, 2009 at 04:02, Bryan <brakeb@...> wrote:

> On Thu, Nov 5, 2009 at 20:00, Hugo Osvaldo Barrera
> <hugo@...> wrote:
>> I'm trying to set up a small box as an 802.11g AP, but there seems to
>> be something wrong.
>> Regrettably, the only devices close by I have to test the connection are
>> -A Windows XP PC
>> -A Windows 7 PC
>> -A PSP
>> I'm pretty sure the problem isn't any of the clients anyway.
>> For testing purposes, I'm running a totally insecure network. I'll add
>> the WPA stuff later.
>>
>> When I try to connect from the PSP I get an error message saying
>> "Check the security settings for the network and try again". It DOES
>> auto-detect is as "security:none" though.
>> When I try to connect from one of the windows PC, I get the typical
>> really helpful message saying "Could not connect to the network"
>
> <snipped...>
>
>
>> ehci_idone: ex=0xffff8000001f7600 is done!
>> ehci_idone: ex=0xffff8000002aaa00 is done!
>>
>>
>
> RTFM:
>

http://www.openbsd.org/cgi-bin/man.cgi?query=rum&apropos=0&sektion=0&manpath=
OpenBSD+Current&arch=i386&format=html
>
> I like the part that says:
>
>  The rum driver supports automatic control of the transmit speed in BSS
>     mode only.  Therefore the use of a rum adapter in Host AP mode is dis-
>     couraged.

I remember having read this when I picked a card. All available cards
used rum, so I had no other choice.

What does the first part mean? I guess I should have asked this to
begin this. Does this mean that I should set the "media" option
manually to something like "media OFDM48 mediaopt hostap"? Or am I
misunderstanding something? I'm not too experienced when it comes to
wireless config.

That aside, I accidentally removed the "mode 11g" part, and now it works.
However, I'm quite intrigued to WHY it works... I can find no
explanation to why it would in B mode and not G (as it seems to be
falling back to 802.11b mode for some reason).

>
>     Host AP mode doesn't support power saving.  Clients attempting to use
>     power saving mode may experience significant packet loss (disabling
power
>     saving on the client will fix this).
>
>

Yes, clients have been configured not to power-save.

[Hugo Osvaldo Barrera]

This works:

inet 172.16.0.1 255.255.0.0 172.16.0.255 media autoselect mode 11b
mediaopt hostap chan 6 nwid CasaDeHugo

Neither of these do:

inet 172.16.0.1 255.255.0.0 172.16.0.255 media autoselect mode 11g
mediaopt hostap chan 6 nwid CasaDeHugo
inet 172.16.0.1 255.255.0.0 172.16.0.255 media OFDM36 mode 11g
mediaopt hostap chan 6 nwid CasaDeHugo

Is this still related to the lack of automatic control of the transmit
speed? I find it rather odd that only b mode works.

On Fri, Nov 6, 2009 at 12:53, Hugo Osvaldo Barrera
<hugo@...> wrote:

>
> On Fri, Nov 6, 2009 at 04:02, Bryan <brakeb@...> wrote:
> > On Thu, Nov 5, 2009 at 20:00, Hugo Osvaldo Barrera
> > <hugo@...> wrote:
> >> I'm trying to set up a small box as an 802.11g AP, but there seems to
> >> be something wrong.
> >> Regrettably, the only devices close by I have to test the connection are
> >> -A Windows XP PC
> >> -A Windows 7 PC
> >> -A PSP
> >> I'm pretty sure the problem isn't any of the clients anyway.
> >> For testing purposes, I'm running a totally insecure network. I'll add
> >> the WPA stuff later.
> >>
> >> When I try to connect from the PSP I get an error message saying
> >> "Check the security settings for the network and try again". It DOES
> >> auto-detect is as "security:none" though.
> >> When I try to connect from one of the windows PC, I get the typical
> >> really helpful message saying "Could not connect to the network"
> >
> > <snipped...>
> >
> >
> >> ehci_idone: ex=0xffff8000001f7600 is done!
> >> ehci_idone: ex=0xffff8000002aaa00 is done!
> >>
> >>
> >
> > RTFM:
> >

http://www.openbsd.org/cgi-bin/man.cgi?query=rum&apropos=0&sektion=0&manpath=
OpenBSD+Current&arch=i386&format=html
> >
> > I like the part that says:
> >
> >  The rum driver supports automatic control of the transmit speed in BSS
> >     mode only.  Therefore the use of a rum adapter in Host AP mode is
dis-

> >     couraged.
>
> I remember having read this when I picked a card. All available cards
> used rum, so I had no other choice.
>
> What does the first part mean? I guess I should have asked this to
> begin this. Does this mean that I should set the "media" option
> manually to something like "media OFDM48 mediaopt hostap"? Or am I
> misunderstanding something? I'm not too experienced when it comes to
> wireless config.
>
> That aside, I accidentally removed the "mode 11g" part, and now it works.
> However, I'm quite intrigued to WHY it works... I can find no
> explanation to why it would in B mode and not G (as it seems to be
> falling back to 802.11b mode for some reason).
>
> >
> >     Host AP mode doesn't support power saving.  Clients attempting to use
> >     power saving mode may experience significant packet loss (disabling

power
> >     saving on the client will fix this).
> >
> >
>
> Yes, clients have been configured not to power-save.