<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 17, 2015 at 4:40 PM, Nick Podolak <span dir="ltr"><<a href="mailto:nicholas.e.podolak@gmail.com" target="_blank">nicholas.e.podolak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 15, 2015 at 3:25 AM, Hans Dedecker <span dir="ltr"><<a href="mailto:dedeckeh@gmail.com" target="_blank">dedeckeh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It would be better to make this a device setting like promiscuous mode,macaddr, etc ... so it can be configured via UCI for every device and thus not only restricted for GRE<br></blockquote></div><span><font color="#888888"><br></font></span></div><span><font color="#888888"><div class="gmail_extra">Hans<br></div></font></span></div>
</blockquote></div><div class="gmail_extra"><br></div>You make an excellent point and I agree, but I'm unsure of some of the details.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Is promisc mode controllable from UCI? I didn't think it was but I can't tell from looking at these parts of netifd.</div></div></blockquote><div>Promiscuous mode is configurable from UCI; see device.c as all dev_attrs entries can be set via UCI <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">Help me understand the extent of this implementation. Looks like each of these would need modification. Did i miss anything?<br></div><div class="gmail_extra">device.c</div><div class="gmail_extra"> static const struct blobmsg_policy dev_attrs[__DEV_ATTR_MAX] = {</div><div> device_merge_settings(struct device *dev, struct device_settings *n)</div><div> device_init_settings(struct device *dev, struct blob_attr **tb)</div><div> device_dump_status(struct blob_buf *b, struct device *dev)</div><div>system-linux.c</div><div> system_if_get_settings(struct device *dev, struct device_settings *s)</div><div> system_if_apply_settings(struct device *dev, struct device_settings *s, unsigned int apply_mask)</div><div><br></div><div>UCI is all passthrough, right? nothing there would have to change?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div></div></font></span></div></blockquote><div>Your analysis regarding UCI and the impacted functions is correct; the promiscuous mode implementation can be used as guidance for the multicast device support.<br><br></div><div>Hans<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="HOEnZb"><font color="#888888"><div>-Nick</div></font></span></div>
</blockquote></div><br></div></div>