How do I ALTQ hostap interface?
How do I ALTQ my wireless (hostap mode) interface in 10.0-R? If I try to add a queue to wlan0, pf complains that wlan0 has no ALTQ support (even though it is an ath(4) interface and ath(4) is supposed to be supported by ALTQ). ALTQ is already setup and working with my wired ethernet over em(4). Am I supposed to specify ath0 as the interface for the pf queue? What if I want to bridge my wireless and wired networks? I thought the bridge would consist of em0 and wlan0 members, and pf will not like that (claiming that bridge0 has no ALTQ driver...but I don't know if that is pf reacting to if_bridge(4) itself not having altq support or the wlan0 member of it... ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Is there anyone who can look at, and possibly fix this?
Hi! Neither of those drivers have active maintainers in FreeBSD. I'm sorry. :( -a On 21 August 2014 11:59, Chuck Burns brea...@gmail.com wrote: There was a bug filed about 7 months ago, with iwi crashing under heavy usage. I am also hitting this bug under 10-stable. Things that trigger the bug are heavy two-way usage, such as bittorrent/aria2c and X11-forwarding over my LAN. bug#185478 The original reporter had this bug under 10.0-RELEASE, and I was under 10-stable. Took several reboots (and quite a bit of $HOME corruption as well) to track down a semi-reliable way to reproduce the bug. It does not always trigger a kernel panic, but iwi will always die with iwi0: Firmware Error and usually, attempting to restart netif will cause the panic. Even restarting netif will not bring the system back. I've got a urtw0 usb dongle that I can sometimes get to work after the iwi0 goes belly up, but not always (and for the record, I had tons of trouble with urtw0 back in 9-current, and it was -never- made stable for me...) With that said, however, iwi0 seems to be perfectly stable under OpenBSD and various Linux distros, which makes me wonder if A) do we need a different firmware version? or B) is there a problem with our implementation of the driver? I'm happy to provide as much more information as I can (I'm currently not running FreeBSD on this machine, but that is easily, and quickly remedied if anyone wants to attempt a fix with me) Thanks, Chuck Burns ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: How do I ALTQ hostap interface?
Looking on the freebsd-net list it seems like a we don't know how to hack altq to work with multiqueues problem, but supposedly it's been solved with em(4) (since it works fine with altq) , (but not necessarily with igb)? OpenBSD is of course no longer useful here since they have removed ALTQ. Perhaps it's time to revisit Dummynet/IPFW for shaping (it was just nice having an easily unified NAT and shaping ruleset). On Thu, Aug 21, 2014 at 1:43 PM, Adrian Chadd adr...@freebsd.org wrote: I've no idea. Sorry, I've kept asking those who are interested in altq to figure out how to do it for drivers with if_transmit() and so far it's been crickets/silence. -a On 21 August 2014 08:53, Peter Lai cowb...@gmail.com wrote: Does 9-STABLE support ath(4) and ALTQ? thanks On Thu, Aug 21, 2014 at 10:38 AM, Adrian Chadd adr...@freebsd.org wrote: Hi, ath(4) now uses if_transmit() and thus there's no ALTQ support at the moment. Sorry. -a On 21 August 2014 02:43, Peter Lai cowb...@gmail.com wrote: How do I ALTQ my wireless (hostap mode) interface in 10.0-R? If I try to add a queue to wlan0, pf complains that wlan0 has no ALTQ support (even though it is an ath(4) interface and ath(4) is supposed to be supported by ALTQ). ALTQ is already setup and working with my wired ethernet over em(4). Am I supposed to specify ath0 as the interface for the pf queue? What if I want to bridge my wireless and wired networks? I thought the bridge would consist of em0 and wlan0 members, and pf will not like that (claiming that bridge0 has no ALTQ driver...but I don't know if that is pf reacting to if_bridge(4) itself not having altq support or the wlan0 member of it... ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: How do I ALTQ hostap interface?
On 21 August 2014 14:13, Peter Lai cowb...@gmail.com wrote: Looking on the freebsd-net list it seems like a we don't know how to hack altq to work with multiqueues problem, but supposedly it's been solved with em(4) (since it works fine with altq) , (but not necessarily with igb)? It's a solvable problem. It's just not solvable with the kinds of hacks that stuck ALTQ in there the way it is in the first place. For em, igb, etc they solved it by having a legacy hey implement the old network transmit interface thing stick around. -a ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
