When you say, "wifi interface", do you mean wlan interface (which is VAP) at AP? or low-level wifi interface? I don't know rate-limit since I've never tried but it works well for regular OVS rules.
- Drop everything - Allow ARP - Allow DHCP - Allow DNS I applied the rule in one of ovs bridge and added multiple wifi interface over GRE tunnel. At least, I've tried this on top of Linux kernel 4.4 / OVS 2.6 - OPENWRT package. Best regards, On Thu, Jul 27, 2017 at 10:28 AM, Michael Williams <[email protected]> wrote: > Hi Ben, > > > I don't think I explained it properly. Between the wired ports we > can apply Openflow rules to limit traffic between computers connected via > those wired ports, and that works with standard OvS. On the wireless WiFi > side I would like to be able do the same thing and to limit the traffic > between WiFi connected devices. > > > Since WiFi only has one interface and not multiple individual ports like > the wired stuff, my rules for dropping traffic between ports won't work. So > I was wondering if there was someway with OvS to limit or stop > traffic between WiFi connected computers? > > > > ------------------------------ > *From:* Ben Pfaff <[email protected]> > *Sent:* Thursday, July 27, 2017 12:57 PM > *To:* Michael Williams > *Cc:* [email protected] > *Subject:* Re: [ovs-discuss] Multiple Virtual Wireless Ports > > On Thu, Jul 27, 2017 at 01:33:23PM +0000, Michael Williams wrote: > > We have OvS running on a wireless router with 4 wired Ethernet > > ports. We can apply rules on the wired ports but when we try to apply > > rules on the wireless port the rules don't work between multiple > > wireless devices. Is there a way within OvS to treat the wireless > > interface like multiple virtual ports so that when a wireless device > > connects we can apply rules to govern behavior between the wireless > > devices like we can with the wired devices? > > OVS doesn't distinguish between different kinds of ports, so the > restrictions you're describing don't make sense; OVS doesn't work that > way. You might be using a vendor's modified version of OVS. If so, > then you should ask the vendor for assistance. > > _______________________________________________ > discuss mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
