public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH 1/1] batman-adv: Always flood IGMP/MLD reports
Date: Sun, 28 Jun 2015 09:37:20 +0800	[thread overview]
Message-ID: <2472003.5ybaWVxMcq@voltaire> (raw)
In-Reply-To: <1434893777-17618-2-git-send-email-linus.luessing@c0d3.blue>

[-- Attachment #1: Type: text/plain, Size: 2701 bytes --]

On Sunday, June 21, 2015 15:36:17 Linus Lüssing wrote:
> With this patch IGMP or MLD reports are always flooded. This is
> necessary for the upcoming bridge integration:
> 
> An IGMPv2/MLDv1 querier does not actively join the multicast group the
> reports are sent to. Because of this, this would lead to snooping
> bridges/switches not being able to learn of multicast listeners in the
> mesh and wrongly shutting down ports for multicast traffic to the mesh,
> leading to packet loss.

I am not quite clear on what the patch does. It helps to support a feature 
that is yet to come (upcoming bridge integration) or improves the situation 
today ?


>  /**
>   * batadv_mcast_forw_mode_check - check for optimized forwarding potential
> @@ -376,9 +434,11 @@ static int batadv_mcast_forw_mode_check(struct
> batadv_priv *bat_priv, case ETH_P_IP:
>  		return batadv_mcast_forw_mode_check_ipv4(bat_priv, skb,
>  							 is_unsnoopable);
> +#if IS_ENABLED(CONFIG_IPV6)
>  	case ETH_P_IPV6:
>  		return batadv_mcast_forw_mode_check_ipv6(bat_priv, skb,
>  							 is_unsnoopable);
> +#endif
>  	default:
>  		return -EINVAL;
>  	}

This hunk seems not really related to the patch itself ?


>  /**
> - * batadv_mcast_tvlv_ogm_handler_v1 - process incoming multicast tvlv
> container + * batadv_mcast_tvlv_ogm_handler_v2 - process incoming multicast
> tvlv container * @bat_priv: the bat priv with all the soft interface
> information * @orig: the orig_node of the ogm
>   * @flags: flags indicating the tvlv state (see batadv_tvlv_handler_flags)
>   * @tvlv_value: tvlv buffer containing the multicast data
>   * @tvlv_value_len: tvlv buffer length
>   */
> -static void batadv_mcast_tvlv_ogm_handler_v1(struct batadv_priv *bat_priv,
> +static void batadv_mcast_tvlv_ogm_handler_v2(struct batadv_priv *bat_priv,
>  					     struct batadv_orig_node *orig,
>  					     u8 flags,
>  					     void *tvlv_value,

By removing mcast v1 you effectively are breaking compatibility with all nodes 
running v1 and require everyone to upgrade to v2. Is there a good reason for 
that ? The multicast optimizations can't easily work with v1 and v2 ?

By reading your patch it does not become clear why v2 is needed in the first 
place. The tvlv's content seems to be identical ?


> @@ -206,6 +206,8 @@ static int batadv_interface_tx(struct sk_buff *skb,
>  	if (atomic_read(&bat_priv->mesh_state) != BATADV_MESH_ACTIVE)
>  		goto dropped;
> 
> +	skb_set_network_header(skb, ETH_HLEN);
> +
>  	soft_iface->trans_start = jiffies;
>  	vid = batadv_get_vid(skb, 0);
>  	ethhdr = eth_hdr(skb);

Why is this change part of the patch ?

Cheers,
Marek


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-06-28  1:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21 13:36 [B.A.T.M.A.N.] [PATCH 0/1] batman-adv: Always flood IGMP/MLD reports Linus Lüssing
2015-06-21 13:36 ` [B.A.T.M.A.N.] [PATCH 1/1] " Linus Lüssing
2015-06-26 12:43   ` Simon Wunderlich
2015-06-28  1:37   ` Marek Lindner [this message]
2015-06-28  3:59     ` Linus Lüssing
2015-06-28 13:21       ` Marek Lindner
2015-06-29  2:52         ` Linus Lüssing
2015-06-29  4:42           ` Linus Lüssing
2015-06-22 17:55 ` [B.A.T.M.A.N.] [PATCH 0/1] " Linus Lüssing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2472003.5ybaWVxMcq@voltaire \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox