El 14/01/2011 10:12, Jouni Malinen escribió: > On Thu, Jan 13, 2011 at 11:13:40PM -0800, Ben Greear wrote: >> If you have an ath9k AP interface running with hostapd, and you >> run: ip link set vap0 down; ip link set vap0 up; >> then it will disable beaconing. > > Yes. So what? > >> I'm not sure where the problem actually lies: Should ath9k >> start beaconing automatically on VAP interface add? Is >> it up to hostapd to detect the ifdown/ifup and re-set everything >> up properly? Or maybe it's just a very bad idea to bounce >> a VAP interface with 'ip link set'? > > I would say it is up to whoever decided to set the interface down to > restart hostapd.. There is a proposed patch for hostapd to do this > automatically, but I'm yet to fully understand why one would set the > interface down in the first place. I usually do it to influence routing from within quagga. Quagga have no provisions to restart another daemons on interface state change. This is just an example, I'm sure there are others valid use cases, so I really think that hostapd should restart beaconing/whatever in this case. Regards, Jorge -- ============================================================== Jorge Boncompte - Ingenieria y Gestion de RED DTI2 - Desarrollo de la Tecnologia de las Comunicaciones -------------------------------------------------------------- C/ Abogado Enriquez Barrios, 5 14004 CORDOBA (SPAIN) Tlf: +34 957 761395 / FAX: +34 957 450380 ============================================================== - There is only so much duct tape you can put on something before it just becomes a giant ball of duct tape. ============================================================== -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
