Building in OpenFlow/SDN support

[Ondrej Zajicek]

On Fri, Jun 14, 2013 at 09:22:25PM +1200, Sam Russell wrote:
> Thanks for the reply Ondrej,
> 
> The reason I want to separate both the kernel and devices is to build
> something like RouteFlow - create fake interfaces that relate to physical
> interfaces on a router, assign IPs to them (and drive ARP and ping from
> that), but also translate the routes from the fake kernel into flows on the
> router.

Hi

This is interesting and would be nice to have, but i don't understand
one detail. I understand why you need replacement for kernel proto to
translate routes to flows for SDN, but i don't understand why you need
replacement for device proto to create fake interfaces if you also plan
to use tun/tap - in that case you would already have 'real' tun/tap
ifaces which would be enumerated in BIRD in a standard way.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20130614/c267faa9/attachment-0001.asc>