From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Fri, 27 Jan 2012 03:13:19 +0800 References: <9AAB212A-A9C6-41CD-BACA-0BA1542FA8F5@net-forces.com> In-Reply-To: <9AAB212A-A9C6-41CD-BACA-0BA1542FA8F5@net-forces.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201270313.19652.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] ap_isolation issue Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking Hi, > We are trying to get OpenWRT with batman-adv 2011.4.0 to play nice using > ap_isolation. However as soon as ap_isolation is turned on the meshed ap > are not acessible anymore by our Linux firewall on which at least 1 ap > node is physically connected. The following pastebin post shows the exact > configuration and details: > > http://pastebin.com/2bghWLkp how is the Linux firewall connected to batman-adv-AP#1 ? Via eth0 ? Can you please also add the output of "batctl if" and "batctl sn" on all devices ? What happens if you disable the bridge loop avoidance ? Does it have any effect ? You are implying that disabling and then re-enabling the ap isolation also fixes the "ping problem" ? Regards, Marek