ath and 802.11a
Hi Is anybody using 802.11a with ath? The manpage lists a/b/g as working, although g definitly doesn't work for me, only b does. Now I'm curious if anything besides b actually works before I buy an antenna for a. Or is it just my cards? If not, why isn't there a note about this in the manpage? Thanks. -- Fridtjof Busse If you want to stay dad you've got to polish your image. I think the image we need to create for you is repentant but learning. -- Calvin
Re: ath and 802.11a
* Theo de Raadt [EMAIL PROTECTED]: Is anybody using 802.11a with ath? The manpage lists a/b/g as working, although g definitly doesn't work for me, only b does. Now I'm curious if anything besides b actually works before I buy an antenna for a. Or is it just my cards? If not, why isn't there a note about this in the manpage? There are many different models of the ath hardware. Not everything works perfectly -- but much of it does work. I think it is a bad thing to make simplified statements like you did above. Well, there was a thread some weeks ago that stated that 802.11g generally doesn't work with ath (in Hostap and 802.11g): no, only 11b with atheros. there is no implementation for 11g in openbsd. Or does g only not work in hostap? Without specific model information *taken right out of dmesg*, noone will be able to help you. ath0 at pci0 dev 13 function 0 Atheros AR5212 rev 0x01: irq 12 ath0: AR5212 5.9 phy 4.3 rf5112 3.6, FCC1A, address 00:0b:6b:36:00:dc That's a Wistron CM 9. Any chance of getting a working on this typ of card? -- Fridtjof Busse YAAH! DEATH TO OATMEAL! -- Calvin
Re: ath and 802.11a
* Andrew Smith [EMAIL PROTECTED]: Seconded (as if I needed to with Theo responding :P) I have an old Atheros based cardbus adaptor that will supposedly do b +g but I know for a fact not a, check the specs of the device please and do as Theo asks... dmesg is useful. Well, I'll not try a with an unsupported piece of hardware. According to the manpage my Wistron CM 9 does a/b/g. But it doesn't do g and that's why I'm not sure if it will do a as well. Interesting thing is that according to CVS only b was reported working, but a/b/g was added to the manpage. It doesn't really help me if the manpages lists the modes the card supports instead of the mode that OpenBSD supports... -- Fridtjof Busse This game lends itself to certain abuses. --- Calvin
Re: Cards/chips supporting hostap mode
* Steve B [EMAIL PROTECTED]: I'm trying to find what wireless PCI cards or chipsets support hostap mode. The Prism 2/2.5/3 is referenced everywhere. Is that that the only one or do any of the others such as Atheros support hostap mode? I'm using a ral-based card (Sitecom) running without any problems as hostap on 3.8-current. As a matter of fact, it works better (i.e. range) than my old Prism2. -- Fridtjof Busse
hostap and bridging
Hi Did anybody get one of the more recent wifi-drivers (e.g. ral or ath) working in hostap-mode and DHCP *without* using bridging? For me, DHCP won't work if I configure ral0 as a normal device on 3.8-beta. Damien told me DHCP probably only works with ral if DHCP listens on the bridge and that this is likely due to the new net80211 subsystem (thus it won't work for any of the new drivers without bridging). Is that correct? If so, why? I don't want to have to use bridging for my wireless-networl as I prefer routing. My Prism2 works just fine without bridging, but this driver is a lot older. -- Fridtjof Busse From now on, I'll connect the dots my own way. -- Calvin
Re: Queueing on two interfaces
* kami petersen [EMAIL PROTECTED]: since nobody else seems to have an answer i'll suggest one thing to try: maybe you could think of it as three separate steps, where arriving traffic from the outside: a) is deprioritized if not voip, then b) gets routed/NATed, then c) can be queued again individually for the internal nets according to other demands. how? [snip] Hi Thanks for your reply. Last night I played around for a few hours and tried something similiar (and it works so far): Since I'm using tun0 on the wireless interface, I bridged tun0 to the internal interface, using OpenVPNs bridging capabilities. And voila, the traffic that goes to the wireless interface ends up in the queue for the internal interface. SSH and mail work very fast even if I stress the SDSL-link with other stuff, so it looks like it queueing works on both networks. I can live with this solution since the wireless interface itself is not bridged, only the encrypted tunnel. Seems to work just fine :) OK, I now have a problem with internal traffic (i.e. traffic that goes to the router itself) since the WLAN only has 11MBit while the ethernet has 1GBit, but that's not really critical for me since I don't often copy files locally. -- Fridtjof Busse
Queueing on two interfaces
Hi Since I didn't get any reply to my initial question, I'll try to be a bit more specific: I've got a machine with three interfaces: One is my SDSL-link and the other two are internal. One of the internal interfaces is wired, the other one wireless, using OpenVPN (i.e. tun0). Queueing of traffic leaving the machine is easy, but is there any way to queue incoming traffic without cutting the available bandwidth in half (50% for each interface)? I found a suggestion about using lo1 and binat, but I don't really know how to do that. E.g., I need to make sure that VOIP-traffic arriving via the wired interface is priorised over all other traffic, even the one that is going to the wireless network. Otherwise, I get heavy distortions if the wireless-net uses much bandwidth. Any way to do this? Maybe bridging? I prefer routing, but I'm grateful for anythin... :) Thanks. -- Fridtjof Busse
altq on multiple interfaces
Hi I'm currently trying to enhance my altq-rules and I apologize in advance if this is a FAQ, but I definitly googled: So far, I used priq on my internal and external interface to prioritize VoIP over SSH over mail over everything else. But now I have a third interface that sometimes consumes a lot of traffic and is thus killing VoIP. Is there a simple way to basically say everything that enters my router, no matter which internal interface it uses, has to follow these rules? The two internal interfaces are different Class-C nets and they have to stay this way. And traffic that comes from the router but not from the internet should be able to use the full FastEthernet bandwidth and not just the SDSL-speed configured in altq. Is there any way to do this without having to use two sets of rules for incoming traffic? The FAQ only lists a CBQ example for a system with more than 2 interfaces and I'd really like to stay with priq. Or do I have to switch to CBQ? Thanks :) -- Fridtjof Busse
Problem with ste-interface
Hi I recently switched from several rl-NICs to one quad ste-NIC (D-Link DFE-580tx) since I was running out of PCI-slots. The new NIC works very well except for one problem with kernel-pppoe. The SDSL-modem is connected to ste0 and hostname.pppoe0 is configured as described in the docs (and this configuration worked flawless with a rl-NIC). But now I only get 1/100 of the bandwidth over the pppoe-link it should have and the only way to fix this I found so far is to repower the modem. After that, pppoe reastablishes the link and I get full bandwidth. No idea what might cause this, so how can can I debug this? ste0 at pci2 dev 4 function 0 D-Link Systems 550TX rev 0x12: irq 11 address 00:05:5d:5e:93:14 ukphy0 at ste0 phy 0: Generic IEEE 802.3u media interface ukphy0: OUI 0x000885, model 0x0023, rev. 0 ukphy1 at ste0 phy 1: Generic IEEE 802.3u media interface ukphy1: OUI 0x000885, model 0x0023, rev. 0 ste1 at pci2 dev 5 function 0 D-Link Systems 550TX rev 0x12: irq 5 address 00:05:5d:5e:93:15 ukphy2 at ste1 phy 0: Generic IEEE 802.3u media interface ukphy2: OUI 0x000885, model 0x0023, rev. 0 ukphy3 at ste1 phy 1: Generic IEEE 802.3u media interface ukphy3: OUI 0x000885, model 0x0023, rev. 0 ste2 at pci2 dev 6 function 0 D-Link Systems 550TX rev 0x12: irq 12 address 00:05:5d:5e:93:16 ukphy4 at ste2 phy 0: Generic IEEE 802.3u media interface ukphy4: OUI 0x000885, model 0x0023, rev. 0 ukphy5 at ste2 phy 1: Generic IEEE 802.3u media interface ukphy5: OUI 0x000885, model 0x0023, rev. 0 ste3 at pci2 dev 7 function 0 D-Link Systems 550TX rev 0x12: irq 10 address 00:05:5d:5e:93:17 ukphy6 at ste3 phy 0: Generic IEEE 802.3u media interface ukphy6: OUI 0x000885, model 0x0023, rev. 0 ukphy7 at ste3 phy 1: Generic IEEE 802.3u media interface ukphy7: OUI 0x000885, model 0x0023, rev. 0 -- Fridtjof Busse
Re: openbsd and dietlibc
* poncenby [EMAIL PROTECTED]: Why? OpenBSD's libc is pretty slim already. If you have need of a further cut-down libc, you could trim it more. Because I want dietlibc for a fnord installation and haven't got the time or experience to fiddle around and get fnord to work with anything but dietlibc. any chance of pointing me in the right direction? dietlibc is for Linux. So it won't work on *BSD without any porting- effort. Compile fnord without dietlibc (remove it from the Makefile) or use gatling (libowfat-cvs compiles on 3.7). I actually prefer gatling. -- Fridtjof Busse
Problems with wi0 as hostap
Hi I'm running a Netgear MA311 in hostap-mode on OpenBSD 3.7. wi0 at pci0 dev 10 function 0 Intersil PRISM2.5 rev 0x01: irq 12 wi0: PRISM2.5 ISL3874A(Mini-PCI), Firmware 1.1.1 (primary), 1.8.2 (station) Sometimes I have problems with DHCP, i.e. the clients don't get an IP. So I checked dmesg and found this: wi0: init failed wi0: failed to allocate 1594 bytes on NIC wi0: tx buffer allocation failed wi0: failed to allocate 1594 bytes on NIC wi0: mgmt. buffer allocation failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_start: xmit failed wi0: device timeout wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed wi0: wi_mgmt_xmit: xmit failed This doesn't look to healthy. Might this be the cause for my DHCP-trouble? Otherwise the card works fine and has a good range, so I'd like to keep it (my former 3CRWE777A had a really lousy range). But it's really annoying not getting an IP every now and then. -- Fridtjof Busse I've coined new words, like misunderstanding and Hispanically. George W. Bush March 29, 2001
Re: Ralink hostap
* Mark Uemura [EMAIL PROTECTED]: like to know if anybody got a ralink-card working in hostap-mode. I had a ralink mini-pci working in hostap mode and running dhcpd using this snapshot. OpenBSD 3.7-current (GENERIC) #134: Sun May 22 01:41:01 MDT 2005 $ sudo ifconfig ral0 media autoselect mediaopt hostap nwid mywap Same thing I used (I added the media autoselect later, but it didn't change anything. No DHCP, nothing got through. The interesting thing was that both 802.11g and 802.11b clients had no problems connecting to the ral Access Point at the same time believe it or not. The g client was rock solid but the b client was up and down like a rollercoaster. I was informed that I could easily kill a g network by introducing a b client but that didn't happen for me :( Instead the b client was hanging on for dear life. I didn't test 11g, but 11b worked fine, but only with static IP- addresses. As of the snapshot above, ralink was not yet ready for prime time. I was able to panic my wap quite easily just by starting an IPsec session from the g client :( I've already sent the trace to [EMAIL PROTECTED] I know that the developers will get this sorted out in due time. I'm just happy to have so many wireless device choices :) Well, I'm not using WEP and OpenVPN instead of IPsec. I didn't get my card to crash so far. But without working DHCP, hostap is not really useful. Is this a driver issue? Most likely but you should be able to get a g network working pretty easily with a current snapshot. I didn't have a g-client at the time of my first writing. But I find it hard to imagine that DHCP didn't work because of 11b. Someone suggested to me off-list that there might be support for DHCP missing in the driver itself. -- Fridtjof Busse You saw the president yesterday. I thought he was very forward- leaning, as they say in diplomatic nuanced circles. George W. Bush July 23, 2001 Referring to his meeting with President Vladimir Putin of Russia.
Ralink hostap
Hi Since I didn't get any replies to my initial question (http://archives.neohapsis.com/archives/openbsd/2005-05/1711.html), I'd like to know if anybody got a ralink-card working in hostap-mode. Currently, I have to set the client's IP statically, since for some reason DHCP doesn't get through. Is this a driver issue? -- Fridtjof Busse If the terriers and bariffs are torn down, this economy will grow. George W. Bush January 7, 2000 Spoken in Rochester, New York during presidential campaign.
