On Mon, Jun 25, 2018 at 5:09 PM, Ido Schimmel wrote:
> Hi Xin,
>
> On Mon, Jun 25, 2018 at 10:45:08AM +0800, Xin Long wrote:
>> This patch implements the feature described in rfc1812#section-5.3.5.2
>> and rfc2644. It allows the router to forward directed broadcast when
>> sysctl mc_forwarding is
On Mon, Jun 25, 2018 at 10:45 AM, Xin Long wrote:
> This patch implements the feature described in rfc1812#section-5.3.5.2
> and rfc2644. It allows the router to forward directed broadcast when
> sysctl mc_forwarding is enabled.
>
> Note that this feature could be done by iptables -j TEE, but it w
Hi Xin,
On Mon, Jun 25, 2018 at 10:45:08AM +0800, Xin Long wrote:
> This patch implements the feature described in rfc1812#section-5.3.5.2
> and rfc2644. It allows the router to forward directed broadcast when
> sysctl mc_forwarding is enabled.
You mean bc_forwarding?
>
> Note that this feature
On Mon, Jun 25, 2018 at 10:45 AM, Xin Long wrote:
> This patch implements the feature described in rfc1812#section-5.3.5.2
> and rfc2644. It allows the router to forward directed broadcast when
> sysctl mc_forwarding is enabled.
>
> Note that this feature could be done by iptables -j TEE, but it w
This patch implements the feature described in rfc1812#section-5.3.5.2
and rfc2644. It allows the router to forward directed broadcast when
sysctl mc_forwarding is enabled.
Note that this feature could be done by iptables -j TEE, but it would
cause some problems:
- target TEE's gateway param has
