Louis, Typical L2 IDS devices mostly work in transparent/TAP mode which means traffic is diverted to these devices without manipulating any packet header. Interfaces/Ports of these devices are in promiscuous mode. Based on the filtering rules , these devices take action on packets, most commonly drop if found malicious otherwise sent out through outgoing interface.
On Sat, Jan 21, 2017 at 12:04 AM, Henry Fourie <louis.fou...@huawei.com> wrote: > Vikash, > > Unclear what you mean by SFC spinning an L2 IDS? > > What is the behavior of L2 IDS devices? > > - Louis > > > > *From:* Vikash Kumar [mailto:vikash.ku...@oneconvergence.com] > *Sent:* Wednesday, January 18, 2017 10:49 PM > *To:* openstack-dev > *Subject:* [openstack-dev] [networking-sfc] Does SFC support chaining of > Layer 2 devices? > > > > All, > > I am exploring SFC for chaining an IDS device (strictly in L2 mode). As > of now, it looks SFC default supports only L3 devices. SFC APIs doesn't > have any way to specify the nature of device and without that, it seems > there is no way an operator can spin any device/VNF except L3 mode VNFs. Is > anything I am missing here ? Can one still spin a L2 IDS with SFC ? > > > > -- > > Regards, > > Vikash > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Regards, Vikash
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev