On Wed, 15 Mar 2006 15:58:45 -0800, Jouni Malinen wrote:
> Neither did I at first, but after some debugging, I would assume that
> you actually meant to return from ieee80211_ioctl_siwap() if the
> previous address is identical to the new one, not if it has changed.. In
> other words:
>
> [...]
>
On Wed, Mar 15, 2006 at 07:24:05PM +0100, Jiri Benc wrote:
> On Wed, 15 Mar 2006 09:52:26 -0800, Jouni Malinen wrote:
> > This sounds good, but I was unable to get this working. I created a WDS
> > link with initial peer address 00:01:02:03:04:05. This added the netdev
> > and STA entry correctly.
On Wed, 15 Mar 2006 09:52:26 -0800, Jouni Malinen wrote:
> This sounds good, but I was unable to get this working. I created a WDS
> link with initial peer address 00:01:02:03:04:05. This added the netdev
> and STA entry correctly. However, when I run "iwconfig wds0 ap
> 00:11:22:33:44:55", I do no
On Mon, Mar 06, 2006 at 04:44:21PM +0100, Jiri Benc wrote:
> Setting of address of WDS remote peer wasn't possible by a WE call. Remote
> WDS peer can be understood as a remote AP and SIOCSIWAP/SIOCGIWAP are unused
> in WDS mode, so let's use them.
This sounds good, but I was unable to get this wo
Setting of address of WDS remote peer wasn't possible by a WE call. Remote
WDS peer can be understood as a remote AP and SIOCSIWAP/SIOCGIWAP are unused
in WDS mode, so let's use them.
Signed-off-by: Jiri Benc <[EMAIL PROTECTED]>
Index: dscape/net/d80211/ieee80211.c
===
