On 9/28/07, Dennis Borgmann <dennis.borgmann@xxxxxxxxxxxxxx> wrote:
This seems not to be a bridging problem then, since your pal didn't move to a new access point, his information should be correct in all bridges (either correct interface or no entry). Therefore packets sent to him should be correctly delivered. OTOH his outgoing packets could be blocked by his access point as long as it thinks you are locally attached (the first packet coming in via the other access point should disillusion it without need for a timer).
The behavior you are seeing is opposite, therefore I think you have misidentified the cause. Can you use VOIP software on a real computer, and run packet capture software? It might be very informative to have a connection phone <-> computer and also computer <-> computer in order to see if any packets are actually being missed, and in which direction.
Most likely your phone clears the routing table when you dissociate from the other access point, and the routing table isn't rebuilt until dhcp runs at the new location. This affects outgoing packets more than incoming, since your adapter still may honor packets destined to your MAC address and broadcast within its range. Of course it may not be the routing table either.
Dear list-members!
I am using OpenWRT (www.openwrt.org) on two accesspoints. Within
OpenWRT, the wireless interface and the ethernet interface are bridged
to one interface (br0).
Those two accesspoints are standing quite far from one another. Their
WLAN-cells do not cross each other, meaning I have an area in between
the two accesspoints, where there is no accesspoint of the two
accessible: a dead spot.
Now I use two WLAN-telephones (Cisco 7920). I start calling one of the
phones inside the same radio cell and I answer this call. Now I start
moving away to the other accesspoint. As soon as I see myself assiciated
to the "new" accesspoint, I am able to hear my mate on the other phone
in the "old" cell, but he cannot hear me. This stays this way, until a
This seems not to be a bridging problem then, since your pal didn't move to a new access point, his information should be correct in all bridges (either correct interface or no entry). Therefore packets sent to him should be correctly delivered. OTOH his outgoing packets could be blocked by his access point as long as it thinks you are locally attached (the first packet coming in via the other access point should disillusion it without need for a timer).
The behavior you are seeing is opposite, therefore I think you have misidentified the cause. Can you use VOIP software on a real computer, and run packet capture software? It might be very informative to have a connection phone <-> computer and also computer <-> computer in order to see if any packets are actually being missed, and in which direction.
Most likely your phone clears the routing table when you dissociate from the other access point, and the routing table isn't rebuilt until dhcp runs at the new location. This affects outgoing packets more than incoming, since your adapter still may honor packets destined to your MAC address and broadcast within its range. Of course it may not be the routing table either.
certain point of time is reached. In our tests, he has been able to hear
my voice recurring at :30 each minute. Take these examples:
05:40:20 I roamed to the "new" AP
05:40:30 my mate could hear me
05:43:35 I roamed to the "new" AP
05:44:30 my mate could hear me
05:47:03 I roamed to the "new" AP
05:47:30 my mate could hear me
...and so on.
So at a certain point of time, there seems to be a flushing of some
bridge-tables, but I don't know, how I could influence this behaviour.
Is this "flushing" somehow to be done manually? Or is there a timer,
which sets this behaviour?
I sniffed the WLAN a little while my tests have been done and the result
is, that the "old" accesspoint seems to still believe me in his radio
cell. So he sends out data for me all of the time, but since my
telephone has moved away, there is no more client to ACK these packages.
After the time mentioned before has passed, these packet are away and
the communication goes on the way it should. So I assume, there is a
timeout, that tells the AP to flush its old bridge-MAC tables of
clients, that he did not hear of since XX seconds...
Any help would be appreciated. Thanks a lot in advance,
Dennis
_______________________________________________
Bridge mailing list
Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/bridge
_______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
