After seeing that vYatta requires a driver plugged in to the interface,
i gave up debugging it.
Now i am trying vArmour driver. Looks simpler. Many things are clearer
except from that they have their own L3 agent. It sees it should be
enabling API calls when a new router is added, removed or
ok into,
>> https://github.com/jumpojoy/generic_switch kind of approach.
>>
>>
>>
>> -
>>
>> Trinath
>>
>>
>>
>>
>>
>>
>>
>> *From:* Oguz Yarimtepe [mailto:oguzyarimt...@gmail.com]
>> *Sent:* Friday, November
23, 2015 at 5:01 AM
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron][fwaas]some architectural advice on fwaas
driver writing
I am c
tepe [mailto:oguzyarimt...@gmail.com]
> *Sent:* Friday, November 20, 2015 5:52 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [neutron][fwaas]some architectural advice
> on fwaas driver writin
nt: Friday, November 20, 2015 5:52 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron][fwaas]some architectural advice on fwaas
driver writing
I created a sample driver by looking at vArmour driver that
I created a sample driver by looking at vArmour driver that is at the
Github FWaaS repo. I am planning to call the FW's REST API from the
suitable functions.
The problem is, i am still not sure how to locate the hardware
appliance. One of the FWaaS guy says that Service Chaining can help, any
On Mon, Nov 02, 2015 at 02:39:49AM EST, Oğuz Yarımtepe wrote:
> All i need is to create a firewall but instead of
> using Iptables, i want to use the hardware firewall and be able to define
> filtering rules.
In the current experimental API, Firewalls are
global in scope and cover an entire
– Hardware Firewall.
Hope this helps.
-
Trinath
From: Oğuz Yarımtepe [mailto:oguzyarimt...@gmail.com]
Sent: Monday, November 02, 2015 1:10 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [neutron][fwaa
Hi,
On Mon, Nov 2, 2015 at 11:25 AM, Somanchi Trinath <
trinath.soman...@freescale.com> wrote:
> Hi –
>
>
>
> Based on this “Assuming that, it will not be routing traffic, just
> filtering, and that we will be using virtual routers of Openstack”
>
>
>
> As I understand from the email, you might
: Oğuz Yarımtepe [mailto:oguzyarimt...@gmail.com]
Sent: Monday, November 02, 2015 4:36 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron][fwaas]some architectural advice on fwaas
driver writing
Hi,
On Mon, Nov 2, 2015 at 1:36 PM, Somanchi Trinath <
trinath.soman...@freescale.com> wrote:
> Hi-
>
>
>
Hi,
> I’m confused. Do you really have an PoC implementation of what is to be
> achieved?
>
>
No indeed. I am using iptables driver to understand the FWaaS structure and
trying to replace it
Hi,
After talking with FWaaS developers at the summit (German and Sridar), i
decided to write here also, maybe someone has an idea. I am trying to
integrate a hardware firewall to our Openstack environment. It is a custom
hardware running BSD on it and has a REST API for configuring. I talked
12 matches
Mail list logo
