Dan Williams wrote:
On Tue, 2008-04-22 at 06:42 +0200, Patrick McHardy wrote:
The patch "prism54: set carrier flags correctly" makes my
prism54 device in AP mode come up without a carrier, which
in causes IPv6 to not add a link-local address, which in
turn causes radvd (configured to announce routes on that
device) to refuse to start, breaking IPv6 for the entire
network.
I didn't check whether a carrier is detected once a client
associates, but in any case it seems to me that a device
in AP mode should always indicate a carrier.
Should always indicate a carrier _when it's configured and up_. If you
just go 'iwconfig eth1 mode master' it shouldn't, but if you do:
ifconfig eth1 up
iwconfig eth1 mode master essid foobar
then it should.
Yes, it was up and running of course. No carrier though.
--
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
