may be another bug

[Jiri Fojtasek]

Tomas Charvat wrote:

>ok somebody already posted something about this problem but i didnt keep
>that message
>
>somebody reported problem that he lost some clients when his IP comes up on
>interface
>
>so i have this problem
>i set up wlan3 before wlan3 IP comes up
>
>iwpriv wlan3 reset 1
>    iwpriv wlan3 reset 2
>    iwconfig wlan3 mode master essid cobraac channel 5 retry 30 txpower 2
>    iwpriv wlan3 maccmd 1
>        iwpriv wlan3 addmac 00:06:25:1B:C2:6A # cobra
>    iwpriv wlan3 addmac 00:02:72:02:47:68 # murin
>    iwpriv wlan3 addmac 00:02:72:02:F5:DF # murin2
>       iwpriv wlan3 wds_add 00:02:72:02:47:68 # murinAP
>    iwpriv wlan3 wds_add 00:02:72:02:F5:DF # murinAP2
>
>
>ok after wlan3 is up, wlan3wds0 is going up ... OK
>wlan3wds0 is up and i can ping it
>in a moment when wlan3wds1 comes up, i lost wlan3wds0 and i have to run set
>up script again to get it back
>
>but if i will up wlan3 and wlan3wds0 during boot time and wlan3wds1 i will
>up manualy after boot
>client on wlan3wds0 will not get lost
>
>there is no any single command starting on IW in wlan3wds0(1) init script
>i do not see any problems with bad broadcast or subnet mask
>
>once i restart wlan3 , i can stop/start wds0(1) and client on wlan3wds0 will
>everytime comeback
>
>any tip ?
>
>i have one more machine with 4 wds clients... but they do run w/o problem
>its not may be bug in hostap ... may be some combination of sumfing ?
>there is no any single msg in syslog
>
>regards tomas
>
>
>routing table
>
>172.20.2.40     *               255.255.255.248 U     0      0        0
>wlan3wds1
>172.20.2.32     *               255.255.255.248 U     0      0        0
>wlan3wds0
>172.20.5.0      *               255.255.255.248 U     0      0        0
>wlan2
>172.20.4.8      *               255.255.255.248 U     0      0        0
>wlan0
>localnet        *               255.255.255.248 U     0      0        0 eth0
>172.20.2.8      xcobra.rip      255.255.255.248 UG    0      0        0
>wlan3
>172.20.2.0      *               255.255.255.248 U     0      0        0
>wlan3
>172.20.5.16     *               255.255.255.240 U     0      0        0
>wlan2
>172.20.4.48     kryspingw.rip   255.255.255.240 UG    0      0        0
>wlan0
>172.20.4.32     *               255.255.255.240 U     0      0        0
>wlan2
>172.20.3.0      kryspingw.rip   255.255.255.0   UG    0      0        0
>wlan0
>172.20.13.0     kryspingw.rip   255.255.255.0   UG    0      0        0
>wlan0
>172.20.0.0      radiatorgw.rip  255.255.254.0   UG    0      0        0 eth0
>loopback        localhost       255.0.0.0       UG    0      0        0 lo
>default         brouter.el-cha. 0.0.0.0         UG    1      0        0
>wlan1
>
>
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap
>
>  
>
Hi

I always use this:
I setup all interfaces and hostap paranmeters
Then i up all the interfaces
And finally i use a kick to all associated interfaces:
iwpriv wlan0 maccmd 4

That kick send a "kick" data frame that force all stations to reasociate 
... (some WDS cleints need it to restore normal operation after hostap 
box restart)

Jiri