wds with both ap's associating to stations

Doug Yeager doug at aircomwireless.net
Sun Dec 29 08:01:23 EST 2002


thanks jouni,
i wanted to make sure i was attempting something that was possible before i 
went looking for my problem.
things seem to happen as soon as i bringe up the bridge.  at this point i 
have one other AP about 5 feet away with basically the identical config.  i 
also have one station running at the same time.

this is my messages log when i bring up the bridge.  thesse "hook" messages 
go on and on in my log.


Dec 28 11:31:18 home kernel: NET4: Ethernet Bridge 008 for NET4.0
Dec 28 11:31:18 home kernel: Bridge firewalling registered
Dec 28 11:31:18 home /etc/hotplug/net.agent: invoke ifup br0
Dec 28 11:31:39 home kernel: device wlan0 entered promiscuous mode
Dec 28 11:33:33 home login(pam_unix)[1053]: session opened for user root by 
LOGIN(uid=0)
Dec 28 11:33:33 home  -- root[1053]: ROOT LOGIN ON tty1
Dec 28 11:34:18 home kernel: device wlan0wds0 entered promiscuous mode
Dec 28 11:34:55 home kernel: br0: port 1(wlan0) entering listening state
Dec 28 11:35:10 home kernel: br0: port 1(wlan0) entering learning state
Dec 28 11:35:25 home kernel: br0: port 1(wlan0) entering forwarding state
Dec 28 11:35:25 home kernel: br0: topology change detected, propagating
Dec 28 11:35:41 home kernel: br0: port 1(wlan0) entering disabled state
Dec 28 11:46:56 home kernel: br0: port 1(wlan0) entering listening state
Dec 28 11:47:01 home kernel: br0: port 2(wlan0wds0) entering listening state
Dec 28 11:47:11 home kernel: br0: port 1(wlan0) entering learning state
Dec 28 11:47:16 home kernel: br0: port 2(wlan0wds0) entering learning state
Dec 28 11:47:26 home kernel: br0: port 1(wlan0) entering forwarding state
Dec 28 11:47:26 home kernel: br0: topology change detected, sending tcn bpdu
Dec 28 11:47:31 home kernel: br0: port 2(wlan0wds0) entering forwarding state
Dec 28 11:47:31 home kernel: br0: topology change detected, sending tcn bpdu
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:32 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:32 home kernel: nf_hook: hook 0 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (unowned) dev=br0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.10:0 192.168.1.1:0 L=84 
S=0x00 I=12225 F=0x0000 T=255
Dec 28 11:47:32 home kernel: nf_hook: hook 0 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (unowned) dev=br0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.10:0 192.168.1.1:0 L=84 
S=0x00 I=12225 F=0x0000 T=255
Dec 28 11:47:32 home kernel: nf_hook: hook 1 already set.
Dec 28 11:47:32 home kernel: skb: pf=2 (unowned) dev=br0 len=84
Dec 28 11:47:32 home kernel: PROTO=1 192.168.1.10:0 192.168.1.1:0 L=84 
S=0x00 I=12225 F=0x0000 T=255
Dec 28 11:47:33 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:33 home kernel: skb: pf=7 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:33 home kernel: nf_hook: hook 3 already set.
Dec 28 11:47:33 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:33 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
Dec 28 11:47:33 home kernel: nf_hook: hook 4 already set.
Dec 28 11:47:33 home kernel: skb: pf=2 (owned) dev=wlan0wds0 len=84
Dec 28 11:47:33 home kernel: PROTO=1 192.168.1.1:0 192.168.1.10:0 L=84 
S=0x00 I=0 F=0x4000 T=64
D






At 01:41 AM 12/29/2002 -0800, Jouni Malinen wrote:
>On Sat, Dec 28, 2002 at 06:06:09PM -0500, Doug Yeager wrote:
>
> > following this example is great, but i want both AP's to associate to
> > stations.  this example only has A associating.
> > is it o.k. to do a "brctl addif br0 wlan0" and "ifconfig wlan0 0.0.0.0" 
> for
> > B configuration also?  i try to do this and i start getting some errors
> > when i try to ping from one station to another.  i don't know if the 
> errors
> > are supposed to be there or a bug.  any help would be great
>
>Yes, it should be OK to add wlan0 to the bridge device on both APs. What
>kind of errors do you get? Is the connection between stations working at
>all in that configuration? If not, can you find the place where packet
>is lost (e.g., is it sent over WDS link)?
>
>--
>Jouni Malinen                                            PGP id EFC895FA
>_______________________________________________
>HostAP mailing list
>HostAP at shmoo.com
>http://lists.shmoo.com/mailman/listinfo/hostap




More information about the HostAP mailing list