Hi Luigi,
glad to see you :)
I just implement the datapath of the switch (base on openflow 1.0)
For the basis, a FreeBSD act as the switch
typical topo: (there should be a controller link with the switch, we
currently ignore it)
host1[eth0] [em0]switch[em1] --- [eth0]host2
(forgot cc before)
Hi, Jim
thanks for reply
this is my graduate design project
my aim is to implement a simple software switch based on openflow using
FreeBSD netmap as network I/O framework
besides, I'm succeed doing on bridge.c at 2 interfaces
add like
/* Func: int main()
Jaye,
I’d really like to see this work happen.
Let me know if I can help.
Jim
> On Sep 17, 2014, at 9:39 PM, upyzl wrote:
>
> Hi,
>
> I think it's right place to talk about FreeBSD 10 - netmap question
> (location at FreeBSD 10: /usr/src/tools/tools/netmap ; with kernel device
> netmap on)
>
Hi,
I think it's right place to talk about FreeBSD 10 - netmap question
(location at FreeBSD 10: /usr/src/tools/tools/netmap ; with kernel device
netmap on)
I'm (entry) study on openflow software switch based on netmap/vale
It seems very simple in vale-ctl.c and hard to add features for packet
p
