WDS configuration issues

[Ray]

On Wed, Feb 12, 2003 at 02:21:51PM +0100, Kurthy Lorant wrote:
> Hi,
> 
> Try to downgrade the 1.4.9 firmware to 1.3.6. Or upgrade it to 1.5.6. 
> Both versions works for me, but with 1.4.9 I had similar problems 
> during this weekend.

Thanks, sure enough I moved all the cards to 1.3.6 and all the machines are
seeing each other.  I'm still not sure why the 1.4.9 cards appeared to work
in wds mode in one machine but not the others but I'm not going to worry
about it.

BTW, when I used Intersils' Winupdate to suck the firmware off of one of my
1.3.6 cards and flash it on a 1.4.9 card it also cloned the MAC address and
serial number.  Winupdate had a feature to edit the MAC and serial # but it
said (and was correct) that it wouldn't take effect until I re-flashed the
secondary firmware seperately (rather than as the primary/secondary/settings
lump it had sucked off the other card).  Bottom line is even though I had a
card with the firmware I wanted I still ended up fetching the firmware from
netgate.  

-- 
Ray



> 
> Lorant
> 
> > On Mon, Jan 27, 2003 at 12:04:10AM -0800, Dave wrote:
> > > Hi all,
> > > 
> > > I have not successfully been able to get automatic WDS functioning 
> no matter
> > > what version/configuration of hostap I use. I can get WDS to 
> function by
> > > adding the MACs manually but I can only randomly see WDS links come 
> up
> > > automatically using the instructions in README.prism2. All boxes 
> are within
> > > the same room and within feet of each other.
> > 
> > Did you ever manage to get this working?  I managed to get one of my
> > machines working but not the other 2 and I'm running out of ideas. 
> Like you
> > I can set up manual wds links with no problem but just not automatic 
> links. 
> > I'm using cvs from Jan 22.  I've got 2 sets of cards, 1 set with 
> 1.0.7/1.3.6
> > firmware and 1 with 1.1.0/1.4.9 and both behave the same way.  One 
> clue is
> > that the nodes that don't work also don't list any MAC addresses at 
> all in
> > /proc/net/hostap/wlan0.  The only other clue is that disabling 
> wireless.opts
> > and setting the channel etc in /etc/network/interfaces (this is 
> Debian)
> > caused the working machine to fail as well so there may be some cruft 
> in
> > /etc/pcmcia.  My settings are similar to those you listed but here 
> they are
> > anyway:
> > 
> > /usr/local/bin/prism2_param wlan0 other_ap_policy 1 
> > /usr/local/bin/prism2_param wlan0 autom_ap_wds 1
> > /usr/local/sbin/iwpriv wlan0 wds_add 00:00:00:00:00:00 
> > /usr/local/sbin/iwpriv wlan0 wds_add 00:00:00:00:00:00 
> > /usr/local/sbin/iwpriv wlan0 wds_add 00:00:00:00:00:00 
> > /usr/local/sbin/iwpriv wlan0 wds_add 00:00:00:00:00:00 
> > /usr/sbin/brctl addbr br0 
> > /usr/sbin/brctl addif br0 wlan0 
> > /usr/sbin/brctl addif br0 wlan0wds0 
> > /usr/sbin/brctl addif br0 wlan0wds1 
> > /usr/sbin/brctl addif br0 wlan0wds2 
> > /usr/sbin/brctl addif br0 wlan0wds3 
> > /sbin/ifconfig wlan0 0.0.0.0 
> > /sbin/ifconfig wlan0wds0 0.0.0.0 
> > /sbin/ifconfig wlan0wds1 0.0.0.0 
> > /sbin/ifconfig wlan0wds2 0.0.0.0 
> > /sbin/ifconfig wlan0wds3 0.0.0.0 
> > /sbin/ifconfig br0 192.168.4.6 up 
> > 
> > Channel, mode, and essid are being set in /etc/pcmcia/wireless.opts.
> > 
> > 
> > Any ideas?
> > 
> > -- 
> > Ray
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> > 
> > 
> 
> 
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap