Re: crash when running kismet with urtw(4) device [FIXED]
I was not sure if I mistyped usbtask and made this note to check the sources as soon as the machine comes back up. This was not meant to be sent this via this report, I simply forgot to edit it out again. Sorry for that. You did not mistype usbtask. usbatsk stands for usb abort task. Probably usbabrt would have been a better choice. I too am not a big fan of this kind of puns in ps output. Damien
Re: TP-LINK TL-WN722N
otus(4) only supports the AR9170 chip which is a completely different beast than the AR9271. The AR9271 chipset is not supported by OpenBSD, it would require a new driver. It is supported under Linux by the ath9k_htc driver so it would be possible to add support in OpenBSD by reusing code in athn(4). The AR9271 is not very interesting though, it didn't make it into a lot of products, is expensive, and these big USB dongles are boring and ugly. All the 802.11 USB devices made by Atheros have been quite disappointing. Damien
Re: high Ierrs in netstat -ni
| NameMtu Network Address Ipkts IerrsOpkts Oerrs Colls | iwn01500 Link 00:21:5c:04:9e:19 365841 6544 237425 4 0 A 2% frame error rate is not that unusual on a wireless link, considering that iwn increments Ierrs for every frames with a bad FCS, for frames that cannot be decrypted correctly, or for frames that are too short. FWIW, I have similar results with a ral adapter: NameMtu Network Address Ipkts IerrsOpkts Oerrs Colls ral01500 Link 00:22:43:76:6a:8e43081 44231460 0 0 Damien
Re: zyd fails to associate with a network
| Maybe anyone knows how can I get any debugging information about my device? | I could try to solve it on my own if I understood where the error is... ifconfig zyd0 debug is usually a good start. Damien
Re: zyd fails to associate with a network
| So now I know that that: | | 1. the association fails with status 25; | 2. the drivers actively sends free-roaming requests during | asssociation | process while is requested to connect an exact network. | | Where can I read what is association failed (status 25) and | deauthenticate (reason 3)? Does anyone know what the problem is? Status 25 is IEEE80211_STATUS_SHORTSLOT_REQUIRED. It means that the access point refuses association from clients that do not support short slot time. zyd(4) does not have the IEEE80211_C_SHSLOT capability. I'll try to see what is required to support that functionnality. I suggest you submit a PR with sendbug so it does not get lost. Damien
Re: zyd fails to associate with a network
| Thanks! | | While it's not a valid workaround, I've set my router up to long slot, | so my issue is resolved. | | Still, could You please tell me where can I find that info without | disturbing developpers and mailing list memebers? In the IEEE 802.11 standard or in /usr/src/sys/net80211/ieee80211.h or /usr/include/net80211/ieee80211.h Damien
Re: Multiple ESSIDs on a single wireless adapter?
| I want to configure multiple wireless interfaces, each | advertised by its own ESSID (nwid according to OpenBSD | ifconfig), using one and the same wireless adapter. (This | is definitely possible on Linux -- I have a working setup | and I am trying to reproduce it on OpenBSD 4.7). It is not possible on OpenBSD. We do not support the creation of virtual access points yet. Regards, Damien
Re: athn0 fails to connect to Motorola Droid wireless tethering
| lladdr 08:00:25:fe:ee:ca 60dB 54M ibss,short_preamble,short_slottime cache Your Droid is operating in independent BSS (IBSS) mode. athn(4) does not support this operating mode yet. rum(4) does (to some extent, i.e no WPA), but you have to specify mediaopt ibss when configuring the interface. Damien
Re: 4.7 and AR5007
| Here is mine. Source was updated from cvs prior to compiling. Thanks. Thanks. But what I really need are the messages (if any) printed when a scan is performed (ifconfig athn0 scan), not just the messages printed during device attachment. Damien
Re: 4.7 and AR5007
| I have the same laptop with the same issue and have been meaning to | ask about it, but Noah beat me to it. | I'd apprecate being kept in the loop about this. If there is anything | I can do to help out, just let me know. | | Corey Yes, please recompile a kernel after changing the value of athn_debug in /usr/src/sys/dev/ic/athn.c to 10: int athn_debug = 0; - int athn_debug = 10; Then reboot and send me the dmesg. The AR9285 works for several people so it is very likely a difference in chip or EEPROM revision that triggers different code paths. Damien
Re: 4.7 and AR5007
| I've been having trouble with a 9285 in a low end Gateway | laptop/netbook. I've been tracking snapshots and it always locks up the | machine when I run 'ifconfig athn0 scan' after 5 seconds or so. Can not | switch to another terminal and can not log in over the network (fast | ethernet, re0, which does work fine) after it locks up. | | I have tried both amd64 and i386 and the issue is the same. Anything | else I can do to help whoever might be interested in fixing it? Are | snapshots new enough? I could send the laptop to a developer for a week | or two if that would help, I'm in the US though. I could also just send | the card to someone, it's useless in it's current state anyhoo. | | Anyway, if anybody has any suggestions I would greatly appreciate them. | | Cheers, | noah Yes, please run ifconfig athn0 debug before you scan (from the console), and send me the output. Damien
Re: Dell Studio 1558
Hi, ... | - Network wired and wireless both work. ... | iwn0 at pci3 dev 0 function 0 Intel WiFi Link 6000 rev 0x35: apic 2 | int 17 (irq 7), MIMO 2T2R, MoW, address 00:23:14:13:b8:00 It is the first time I see a dmesg with a Centrino Advanced-N 6200 :-) Have you tried to associate with an access point and transfer data over it, or are you saying that it works just because it is detected? If it really works, then that's great news! Damien
Re: iwn stopped working after OpenBSD upgrade in January, 2010
There is no iwn-firmware-5.3. The latest package is rev 5.2. It contains the exact same images than you can download from: http://intellinuxwireless.org/?n=Downloads Please run ifconfig iwn0 debug before dhclient iwn0 and send me the output. | media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g) Have you forced media to OFDM54? If so, try with ifconfig iwn0 media autoselect. Damien
Re: Realtek urtw(4) driver and hostap mode
| [...] | AFAIK, hostap mode is crappy with most drivers, since they doesn't vary | the sending strength (AKA 'power saving') and the clients expect this. | [...] Actually, power saving at the AP has nothing to do with sending strength. It is about buffering frames in the AP for clients that are sleeping. And yes, OpenBSD does not currently do that, so clients that are sleeping will never wake up (actually they will wake up at regular interval but will immediately return to sleep) because the AP does not inform them that they have buffered frames. This is something that is being worked on but that is not easy to implement properly. USB devices are usually a bad choice for building an AP anyway, since they have some restrictions (usually, they do not give per-frame feedback about TX retries, making it difficult to do per-client rate control, or they don't provide a way to update beacons content atomically, making it difficult to support anything but 802.11b or plain 802.11a for instance). Some drivers (ural(4), rum(4), maybe others as well) provide some very limited AP support that can be handy sometimes but you can't rely on this for everyday use. The situation is a little bit better for PCI/CardBus devices, but we don't support AP mode power-saving for them either. Damien
Re: Planex GW-USMicroN not recognized by run
| OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009 there you go. this is 4.5-release. Damien
Re: Planex GW-USMicroN not recognized by run
| [...] | So is this card actually supposed to be supported by either | current or 4.5? | | Later | Peter Hi, The USB ID for the Planex GW-USMicroN adapter was added to the run(4) driver just after the 4.5 release, so the June 16th i386 snapshot should work. From sys/dev/usb/if_run.c: USB_ID(PLANEX2, GWUSMICRON), From sys/dev/usb/usbdevs: vendor PLANEX2 0x2019 Planex Communications ... product PLANEX2 GWUSMICRON 0xed14 GW-USMicroN Damien
Re: Intel 5100AGN in 4.5?
OpenBSD 4.5 Release has support for Intel WiFi Link 5000 Series adapters. See http://www.openbsd.org/45.html Damien
Re: wpa2 and osx
| hi list, | i have a problem with wpa2 and osx. i could connect to the ap | if i force it to use wpa1 only. all other wpaprotos gives a : | WPA2(PSK,unknown/TKIP,AES/TKIP) | while scanning with airport and the association failed. the test | cases and dmesg could be found here: | http://sumi.thepixelz.com/obsd/wpa-openbsd.txt The unknown comes from the PSK-SHA-256 authentication protocol supported by OpenBSD (this is a protocol defined in Draft 802.11w that has a stronger key derivation function than the legacy PSK-SHA1). Unfortunately, some broken (non standard compliant) supplicants are confused by unknown authentication protocols and try to associate using 802.1X in this case. I've seen this with Intel PRO/Set on XP too. I'm not quite sure what to do since it's not OpenBSD fault at all. The current approach is that if a user specifies psk with the wpaakms ifconfig command, both PSK-SHA1 and PSK-SHA-256 are advertised by the AP. Maybe I should add psk-sha256 to the list of supported values for wpaakms so that people who have interoperability problems can disable PSK-SHA-256 with wpaakms psk. The default setting would be psk,psk-sha256. Because we are approaching release, I will probably stop advertising PSK-SHA-256 by default for 4.5 (AFAIK, only OpenBSD clients are currently capable of selecting this authentication protocol, although some very recent versions of wpa_supplicant may support it too.) Damien
Re: Linksys WUSB600N and Access Point
| I spent some time today on trying to get it to act as an Access Point. run(4) does not support HostAP mode and probably never will as I'm not inclined to add support for it. Advertising HostAP support in ural(4) and rum(4) was a mistake I'm not going to reproduce. Those devices simply don't have what it takes to properly support HostAP mode. I'm not removing HostAP from ural(4) and rum(4) because some people already depend on it, but quite frankly, it is nothing else than a toy. You will start running into troubles as soon as you start mixing 11b and 11g stations in your BSS. Beacons are simply never updated. There is also no rate control in HostAP mode with these devices. | Tried initially a WPA setup which gave me a kernel panic, so rebooted | and tried to set an access point with no encryption just to confirm | that it worked. Could you please send me the output of the panic? It should never panic, no matter what you do. Damien
Re: can't build ifconfig on landisk
Run make includes in /usr/src/include/ first. Damien | hello, | i can't build the ifconfig on landisk. | snapshot is from 2008/04/18 /usr/src is up to date. | | see attached logfile. | | best regards | thomas | cc -O2 -pipe-DINET6 -c ifconfig.c | ifconfig.c: In function `setifwmm': | ifconfig.c:1422: error: storage size of `wmm' isn't known | ifconfig.c:1426: error: `SIOCS80211WMMPARMS' undeclared (first use in this function) | ifconfig.c:1426: error: (Each undeclared identifier is reported only once | ifconfig.c:1426: error: for each function it appears in.) | ifconfig.c: In function `setifwpa': | ifconfig.c:1434: error: storage size of `wpa' isn't known | ifconfig.c:1437: error: `SIOCG80211WPAPARMS' undeclared (first use in this function) | ifconfig.c:1440: error: `SIOCS80211WPAPARMS' undeclared (first use in this function) | ifconfig.c: In function `setifwpaprotos': | ifconfig.c:1448: error: storage size of `wpa' isn't known | ifconfig.c:1457: error: `IEEE80211_WPA_PROTO_WPA1' undeclared (first use in this function) | ifconfig.c:1459: error: `IEEE80211_WPA_PROTO_WPA2' undeclared (first use in this function) | ifconfig.c:1467: error: `SIOCG80211WPAPARMS' undeclared (first use in this function) | ifconfig.c:1470: error: `SIOCS80211WPAPARMS' undeclared (first use in this function) | ifconfig.c: In function `setifwpaakms': | ifconfig.c:1478: error: storage size of `wpa' isn't known | ifconfig.c:1487: error: `IEEE80211_WPA_AKM_PSK' undeclared (first use in this function) | ifconfig.c:1489: error: `IEEE80211_WPA_AKM_IEEE8021X' undeclared (first use in this function) | ifconfig.c:1497: error: `SIOCG80211WPAPARMS' undeclared (first use in this function) | ifconfig.c:1500: error: `SIOCS80211WPAPARMS' undeclared (first use in this function) | ifconfig.c: At top level: | ifconfig.c:1508: error: `IEEE80211_WPA_CIPHER_USEGROUP' undeclared here (not in a function) | ifconfig.c:1508: error: initializer element is not constant | ifconfig.c:1508: error: (near initialization for `ciphers[0].cipher') | ifconfig.c:1508: error: initializer element is not constant | ifconfig.c:1508: error: (near initialization for `ciphers[0]') | ifconfig.c:1509: error: `IEEE80211_WPA_CIPHER_WEP40' undeclared here (not in a function) | ifconfig.c:1509: error: initializer element is not constant | ifconfig.c:1509: error: (near initialization for `ciphers[1].cipher') | ifconfig.c:1509: error: initializer element is not constant | ifconfig.c:1509: error: (near initialization for `ciphers[1]') | ifconfig.c:1510: error: `IEEE80211_WPA_CIPHER_TKIP' undeclared here (not in a function) | ifconfig.c:1510: error: initializer element is not constant | ifconfig.c:1510: error: (near initialization for `ciphers[2].cipher') | ifconfig.c:1510: error: initializer element is not constant | ifconfig.c:1510: error: (near initialization for `ciphers[2]') | ifconfig.c:1511: error: `IEEE80211_WPA_CIPHER_CCMP' undeclared here (not in a function) | ifconfig.c:1511: error: initializer element is not constant | ifconfig.c:1511: error: (near initialization for `ciphers[3].cipher') | ifconfig.c:1511: error: initializer element is not constant | ifconfig.c:1511: error: (near initialization for `ciphers[3]') | ifconfig.c:1512: error: `IEEE80211_WPA_CIPHER_WEP104' undeclared here (not in a function) | ifconfig.c:1512: error: initializer element is not constant | ifconfig.c:1512: error: (near initialization for `ciphers[4].cipher') | ifconfig.c:1512: error: initializer element is not constant | ifconfig.c:1512: error: (near initialization for `ciphers[4]') | ifconfig.c: In function `getwpacipher': | ifconfig.c:1523: error: `IEEE80211_WPA_CIPHER_NONE' undeclared (first use in this function) | ifconfig.c: In function `setifwpaciphers': | ifconfig.c:1530: error: storage size of `wpa' isn't known | ifconfig.c:1539: error: `IEEE80211_WPA_CIPHER_NONE' undeclared (first use in this function) | ifconfig.c:1548: error: `SIOCG80211WPAPARMS' undeclared (first use in this function) | ifconfig.c:1551: error: `SIOCS80211WPAPARMS' undeclared (first use in this function) | ifconfig.c: In function `setifwpagroupcipher': | ifconfig.c:1559: error: storage size of `wpa' isn't known | ifconfig.c:1563: error: `IEEE80211_WPA_CIPHER_NONE' undeclared (first use in this function) | ifconfig.c:1567: error: `SIOCG80211WPAPARMS' undeclared (first use in this function) | ifconfig.c:1570: error: `SIOCS80211WPAPARMS' undeclared (first use in this function) | ifconfig.c: In function `setifwpapsk': | ifconfig.c:1577: error: storage size of `psk' isn't known | ifconfig.c:1592: error: `SIOCS80211WPAPSK' undeclared (first use in this function) | ifconfig.c: In function `print_cipherset': | ifconfig.c:1720: error: `IEEE80211_WPA_CIPHER_NONE' undeclared (first use in this function) | ifconfig.c: In function `ieee80211_status': | ifconfig.c:1739: error: storage size of `psk' isn't known | ifconfig.c:1744: error: storage size of `wmm' isn't known | ifconfig.c:1745: error: storage
Re: wpa now in current?!
WPA-PSK only and for a limited number of drivers. This is definetely work-in-progress, but the basic functionality is there. Damien | damn it ... I'm really excited and I can't really believe it: | http://marc.info/?l=openbsd-cvsm=120837078900999w=2 | | Does that mean wpa is now included and working in current? | | thx a lot | didier
Re: Intel Core2 Dual/Quad - i386 or amd64?
It appears that the wireless driver your Thinkpad requires wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG is not supported in OpenBSD/amd64. See http://www.openbsd.org/amd64.html That is not true. Both wpi(4) and iwn(4) are in amd64 GENERIC. The web page needs an update though. Damien
Re: What is WPA status in OpenBSD
I still have plans to continue the WPA work in the near future. No estimated time of arrival though, especially as I tend to become lazy as I get older. Damien | Dear All, | | I would love to use OpenBSD on my laptop but the problems is that most of | my work places use WPA encrypted wireless networks | | So what is a status of WPA support in OpenBSD? I know that a lot of people | ask about this. | | Last cvs commit I found with some work done with WPA is from 2007/08/22 | | http://marc.info/?l=openbsd-cvsm=118781535213730w=2 | | No active work with WPA in OpenBSD 4.3 or -current? | | P.S. I'm not waiting for a kind of reply like: WPA is bad - use VPN | tunnels ;) | | Thank you, | | - | Dominik Zalewski | System Administrator | OpenCraft | t- +2 02 3336 0003 | w- http://www.open-craft.com
Re: WiFi parameters
| I'm currently looking for a way to configure fragmentation | thresholds and beacon intervals on a Ralink-based WiFi card on | OpenBSD 4.2, configured as an AP. Frames fragmentation is not supported by OpenBSD, both in the TX and RX paths. This is a limitation of the ieee80211(9) layer (for the RX path) as well as a limitation of the drivers (for the TX path.) An OpenBSD AP can't talk to stations using fragmented frames. You can't configure the beacon interval too, basically because there's no such option in ifconfig and an ioctl in ieee80211(9) is missing. It wouldn't be too hard to implement though. Damien
Re: IPoEoA on ueagle?
| I am running 4.2-RELEASE and have recompiled the kernel to include the | lines: | | Option NATM | ueagle* at usb? | | My Sagem [EMAIL PROTECTED] 800 E2 is recognised by the kernel: | | # dmesg | grep ueagle | ueagle0 at uhub3 port 2 | ueagle0 detached | ueagle0 at uhub3 port 2 | ueagle0: Analog Devices Eagle II, rev 1.00/50.0b, addr 2 | ueagle0: address: 00:60:4c:16:d1:60 | # | | My ISP uses IPoEoA. | I have done a bit of reading on ATM (although I am by no means an expert) | and I would like to know if IPoEoA is supported in ueagle. No. ueagle supports plain IPoA (with or without LLC encap) and PPPoA only. It's more a limitation of the OS (netatm stack) than a limitation of the driver though. Are you sure your ISP really uses IPoEoA? It is the first time I see this. Does your modem synchronize at least? (just run ifconfig ueagle0 up) Damien
Re: Bug in the wireless wpi driver ?
You're using the wrong firmware. On OpenBSD 4.1, you should be using revision 1.13 of the firmware package as stated in the 4.1 wpi(4) man page. But you should consider upgrading to OpenBSD-current because a lot of improvements have been made in the wpi driver since 4.1. Damien Hay Damien, i have install OBSD 4.1 last day on Sony VAYO VGN-C1S and have any problems with the wpi-driver, too. After i'm installed the wpi-firmware-2.14.1.5 and i make on with #ifconfig wpi0 up then, #wpi0: could not read the firmware also, i moved wpi-3945abg to wpi-ucode. Now, it's read firmware, but he could not lock memory best reagards Boris
Re: Bug in the wireless wpi driver ?
| # ifconfig wpi0 down | # ifconfig wpi0 nwid NAME up | wpi0: timeout waiting for thermal sensors calibration | wpi0: fatal firmware error This means that your radio switch is off. Damien
Re: lenovo thinkpad x61s support for wireless + sound
Thanks a lot for helping me debugging the issues with interrupts and testing all the iwn(4) patches I sent to you! Damien | Hi, | | I just wanted to report that today and after gallons of sweat and | blood and some 14 compiled kernels to test the drivers and patches of | Damien Bergamini (iwn0) and Deanna Phillips (azalia) (and correct a | lot of mistakes I made), I finally got my brand new lenovo thinkpad | wireless device (Intel 4965AGN) and sound card (Intel 82801H HD) to | work with OpenBSD -current. | | Volume up/ down work perfectly (on terminal, for X it'll be more | tricky, depends on your WM, but mute does work both in X and no-X). | | I have seen some people complaining on the difficulty of wireless | management in obsd; I am writing a script now to simplify it and I'll | post it as soon as I have it running. | | By the way, the keys for light up/down works just out of the box. | | So... don't hesitate and get a new lnovo thinkpad x61s! | | Cheers, | | Pau Amaro-Seoane
Re: wpi3945 driver bug?
| I am using the wpi3945 driver with the latest wpi-firmware | (2.4.14). When I am not using my wireless connection for some | time, because the laptop is staying switched on and unused for | some time, I do get a wireless time-out. What is a wireless time-out? It is normal that the access point deassociates idle stations. But the wpi(4) driver should reassociate immediately. Damien | The OpenBSD is Obsd-current snap 20-07-07, but the issue was | already there as long as I am using Obsd (about three months now). | | Is this a driver bug or can it be solved another way? | | Jan
Re: wpi3945 driver bug?
That is a different problem. It happens when the wireless button that enables/disables the radio has not been pushed, or if it is an ACPI-only button or if it's a software switch that needs some vendor-specific driver to actually enable the radio. Damien i get another type of timeout in my ThinkPad T61, the wireless doesn't work: wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: irq 11, MoW2, address 00:19:d2:97:24:61 ifconfig wpi0 up wpi0: timeout waiting for thermal sensors calibration (i'm using the f/w package 2.14.4 as proposed by the manpage in -current) reyk
wpi(4) changes require firmware upgrade
Recent changes in wpi(4) require an upgrade of the wpi-firmware package to revision 2.14.4. As usual, you can find a prepackaged version of the firmware at: http://damien.bergamini.free.fr/packages/openbsd/wpi-firmware-2.14.4.tgz or you can download it directly from: http://www.intellinuxwireless.org/ and copy it to /etc/firmware/wpi-3945abg The driver will stop working if you don't upgrade the package. Damien
Re: wpi(4) changes require firmware upgrade
Of course, this is only for people following -current. *DO NOT* update your wpi-firmware package if you're running 4.1! Users running 4.1 must use rev. 1.13 of the package as indicated in the wpi(4) man page. Older revisions of the firmware are available under: http://damien.bergamini.free.fr/packages/openbsd/ Damien | Recent changes in wpi(4) require an upgrade of the wpi-firmware | package to revision 2.14.4. | As usual, you can find a prepackaged version of the firmware at: | http://damien.bergamini.free.fr/packages/openbsd/wpi-firmware-2.14.4.tgz | | or you can download it directly from: | http://www.intellinuxwireless.org/ | and copy it to /etc/firmware/wpi-3945abg | | The driver will stop working if you don't upgrade the package. | | Damien
Important wpi(4) changes in -current
I've just committed some important changes to the wpi(4) driver for Intel PRO/Wireless 3945ABG adapters: http://marc.info/?l=openbsd-cvsm=118107389909915 Those changes require that you upgrade your wpi-firmware package to version 2.14.3 or your adapter will stop working. The firmware package is made available here: http://damien.bergamini.free.fr/packages/openbsd/wpi-firmware-2.14.3.tgz Also, the default behavior of the driver is now to scan only channels that are listed as authorized in the adapter's EEPROM. You may no longer be able to associate if you were using a channel not in your regulatory domain. Please report any regression you might see directly to me. Damien
Re: ppp.conf for ueagle and pppoa
Hi, The route command is only necessary for plain IPoA. For PPPoA, ppp will create the route for you. Just put: set device PPPoA:ueagle0:8.35 in your ppp.conf file. And make sure to copy the firmware files (which are not freely redistributable) in your /etc/firmware/ directory. You can find them here: http://damien.bergamini.free.fr/ueaglefw/ Damien | Hello, | | I've got my Sagem 800 to be recognized properly by | uncommenting the ueagle* and NATM lines and rebuild | the kernel, but the man-pages for ueagle and ppp.conf are | kind of confusing. -In the ueagle(4) it says to use route | to create a PVC, but I don't understand how to use this | information in the ppp.conf. The bergamini-pages only | confuses the matter even more: | http://damien.bergamini.free.fr/ueagle/ppp.html | | -Could some just tell me what to put in set device for a ppoa connection | (vc, vpi=8, vci=35) in a ppp.conf, and what else I need to do to get it to | work? | | Thx
Re: wirless LAN - DWL-G120 on OPENBSD 4.0
It is based on the Conexant Prism54 USB2.0 chipset which is not currently supported in OpenBSD. If you send it to me I may consider writing a driver for it on a rainy day ;-) Damien | Is any one working on this driver? | I have D-LINK DWL-G120 USB wireless. | dmesg shows some thing like this | - | ugen0 at uhub2 port 1 | ugen0: D-Link product 0x3701, rev 2.00/2.03, addr 2 | | - | I run ifconfig -a but cannot show it at all? | | DO you have any ideas to make this card work? | do I have to compile the kernel? | if yes , what to change? | | Thanks | Minh
Re: Ralink broken after last update
Name Mtu Network AddressIpkts IerrsOpkts Oerrs Colls With rssadapt: ral0 1500 Link 00:0e:2e:86:87:76 21153 836324635 1796 0 With AMRR. Rebuilt from CVS couple of hours ago. ral0 1500 Link 00:0e:2e:86:87:76 501773 422 1002191 159 0 I left the lappy downloading stuff and it's been going at rock solid 750KB/s for the last hour or so. I think it has never worked so well. Indeed. You go from 7.3% output packets lost down to 0.016% :) Damien
Re: Ralink broken after last update
Could you please run the following commands on your ral-based access point, preferably before and after the rssadapt-AMRR change: # netstat -i # ifconfig -M ral0 Thanks, Damien | I'm running Canyon CN-WF511 wireless PCI card (Ralink RT2561S) | in hostap mode in my 30m2 flat, serving one laptop next room. | The wireless quality has always been less than stellar, even | when few meters from the OpenBSD box antenna. But it works for | reading mail and news and thats all that matters in this case. | | Unfortunately, after updating last week (I'm following -current) | things got a bit worse. When in the same room with the AP, it works | as craptastically as before, but further away (say 5 meters and a | concrete wall between) things slowly cripple to the point when laptop | can't even find the AP. | | Long story short, looks like this update is to blame here: | | replace rssadapt(9) with amrr for automatic rate control. | as a side-effect, this should fix all the bogus xmit rate panics | users have been complaining about for some time when operating in | HostAP mode. | | I grabbed previous versions of relevant files from cvsweb and | rebuilt the kernel. | | Things work well now. | | Btw, I, too, suffered kernel panics before but forcing mode 11b in | hostname.ral0 took care of that. | | Here's my dmesg: http://doktor.kompro.ee/dmesg | | PS. I stared at the output of tcpdump -i ral0 -y IEEE802_11_RADIO | when it was broken but could'nt make any sense of it. | If someone would tell me what to look for there, I'm willing | to break things again and investigate.
Re: Ralink broken after last update
| I'm in this case too using OpenBSD 4.0-current (GENERIC) #1163: Thu | Oct 19 14:40:44 MDT 2006 : | | ural0 at uhub0 port 1 | ural0: Nintendo Nintendo Wi-Fi USB Connector, rev 2.00/0.01, addr 2 | ural0: MAC/BBP RT2571 (rev 0x05), RF RT2526, address 00:0d:0b:c3:cb:bb | | ural0 is in hostap mode, /etc/hostname.ural0 : | | 192.168.13.254 255.255.255.0 media DS11 mediaopt hostap mode 11b nwid w3lC0m3_H0 | m3 chan 11 | | I use it from my powerbook, and sometimes, I lost Wi-Fi connectivity | for about 1 minutes... Screen helps :) This is a different problem. ural(4) has always used AMRR for rate control and it isn't even enabled in hostap mode. Is your problem new to OpenBSD 4.0 or was it already existing in previous releases? Is your powerbook wifi adapter working in powersave mode? Thanks, Damien
Re: ral0 errors
Could you provide a dmesg of your OpenBSD wireless router so that I can know what Ralink chip and radio you have? Do you know the model of the wireless adapter in your PowerBook? These messages are not normal so sending them to /dev/null is not an option ;) I'm quite busy right now but I'll look at this problem after work. Thanks, Damien |I have OBSD setup as my wireless router and it works perfectly! However | when I connect with my PowerBook, I start getting tons of output on the | console. The PowerBook does connect and it can use the network. | | 1.) Is there anything I can do about this? | 2.) If not can I send these messages to /dev/null somehow? I still want | to get most messages on the console, but this one happens so often that | I can't do anything else if I'm on the console. | | cat /etc/hostname.ral0 | inet 192.168.2.254 255.255.255.0 NONE media autoselect mediaopt hostap | mode 11g nwid Devious_WL_BackOff chan 11 | | I'm also using OpenVPN for this and have several other machines | connected wirelessly no problem, but whenever the PowerBook connects I | get | | Sep 28 12:47:49 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:49 mbsd /bsd: ral0: sending data frame failed 0x0099aafa | Sep 28 12:47:49 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:49 mbsd /bsd: ral0: sending data frame failed 0x0099aafa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x00c9aafa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:50 mbsd /bsd: ral0: sending data frame failed 0x0319aafa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x001003fa | Sep 28 12:47:51 mbsd /bsd: ral0: sending data frame failed 0x05d1aafa | | Thanks | | B
Intel policy wrt OSS [was: Re: cvs.openbsd.org: src]
Intel's policy with respect to open-source software[1] which has been presented at OSDL (I wasn't there unfortunately) is clear and can be summarized as follow: - make us look like we're open-source friendly by opening a project on sourceforge. - give the open-source community the bare minimum so that they can serve as our beta-testers. Even, they're far less opened that what they pretend to be in their slides: If you need to keep IP closed source (for example some whiz-bang algorithm), document the hardware sufficiently that the community can provide their own. So Intel please tell me where I can find the documentation of your Intel PRO/Wireless products so that I can improve the drivers myself? Damien [1] Balancing Open Source and Corporate Objectives James Ketrenos, Intel SGG Core Software Division, ipw2100/2200/3945 project manager, July 25, 2006 http://developer.osdl.org/dev/opendrivers/summit2006/james_ketrenos.pdf http://developer.osdl.org/dev/opendrivers/summit2006/james_ketrenos.mp3 And yes, it was in the Open Drivers summit! | CVSROOT: /cvs | Module name: src | Changes by: [EMAIL PROTECTED] 2006/09/29 21:02:45 | | Modified files: | share/man/man4 : wpi.4 iwi.4 ipw.4 | | Log message: | We have again tried to talk to Intel about being able | to redistribute firmware and they are being totally | unhelpful. | | If you'd like to tell Intel how screwed up this | situation is, you should mail [EMAIL PROTECTED]
Re: ral0 hostap Power Save Polling Problem
I'll look at these PSP problems after 4.0. Thanks for your report. Damien | hello, | i have a problem with me wrap board and a gigabyte ral card in hostap | mode. when my ibook or my thinkpad(with windows) is on battery then i | have packet lost. when the notebooks are connected to power the | connection is fine. | it seem i have this problem: | http://www.intel.com/support/wireless/wlan/sb/cs-006205.htm | but i have not found a workaround for my apple notebook. is this problem | known? | | any hints are welcome :) | thx | thomas
Re: ueagle(4) advice
| I guess I need to recompile my kernel with line 232 enabled? Yes. You may also need to uncomment the line: #option NATM if your ISP requires the use of PPPoA. In this case, you'll need to use user-ppp since kernel pppd does not support PPPoA. | And download the firmware from http://damien.bergamini.free.fr/ | ueaglefw/ ? Yes. Unfortunately, Analog Devices have always refused to clarify the license of this firmware. | Is there anything else about which any reader of this feels I | should be warned? Yes. If your ISP requires the use of PPPoE, ueagle(4) won't work since there's no support for Ethernet encapsulation over AAL5 in the kernel. Also ADSL2+ is not supported because of bandwidth limitations in USB1.0. But I've been using ueagle(4) over a IPoA/VCMUX ADSL line (8Mbits/s downstream) with great success for quite some time. Damien
Re: iwi broken in 3.8-current?
Please try to force 11g mode by hand: % ifconfig iwi0 mode 11g I'm pretty sure the firmware crashes when scanning channels in the 5GHz band. This bug should affect 2915ABG adapters only. Scanning of those channels was disabled in 3.8. Damien
Re: USB ralink vs. PCMCIA ralink
You should prefer the PCMCIA one. The RT2500USB chipset has poor support for per-node tx rate adaptation and is thus a bad choice for hostap mode. Damien | I have a hard time making up my mind which is better: | a USB ralink wireless (Surecom EP-9001G) or a PCMCIA ralink | wireless (Surecom EP-9428G). | According to man ral they're both supported so this question isnt about | diffrent chipset but about what bus type is preferable: USB or PCMCIA. | Or if the Surecom USB (or PCMCIA) sucks and is crap please let me know. | | --- | Lars Hansson
