Thanks for your suggestion Justin.
We have tested the veth. the openflow switch side works great, but Click
seems not working correctly.
Here is what I've configured on eth1, the same configuration applies to
eth2 and eth3:
We created two pairs of veth for each real interface, one end is bridged to
the real one, the other end is used by the ovs and click.
####script starts
#create two veth pairs
ip link add veth1.0.0 type veth peer name veth1.0.1
ip link add veth1.1.0 type veth peer name veth1.1.1
#bridging the real interface with one end of each pair
ovs-vsctl add-br br-eth1
ovs-vsctl add-port br-eth1 eth1
ovs-vsctl add-port br-eth1 veth1.0.0
ovs-vsctl add-port br-eth1 veth1.1.0
#bring up interfaces
ifconfig eth1 promisc up
ifconfig veth1.0.0 promisc up
ifconfig veth1.0.1 promisc up #used by OpenFlow switch
ifconfig veth1.1.0 promisc up
ifconfig veth1.1.1 promisc up #used by Click
####script ends
This is a figure that illustrate our configuration for eth1.
+---------------------------+
| br-eth1 |
+------+----------+---------+
| eth1 |veth1.0.0 |veth1.1.0|
+--+---+-----+----+----+----+
| | |
----------+ | +----+-----+------+--------+
veth1.0.1 |veth1.1.1 | ... | ... |
+-----+ +----------+------+--------+
|click| | of-switch |
+-----+ +--------------------------+
The problem is: click can see the incoming packets (e.g. a ping packet),
but after it finishes processing and send it back to the linux stack (using
Click's ToHost element), the packet gets dropped and the OS doesn't send a
response to the ping.
Is there a function in ovs that act like Click's ToHost, to send all the
ipv6 packets to Click without being forwarded by ovs?
Thanks,
Xinming
2014-09-28 20:11 GMT-04:00 Justin Pettit <[email protected]>:
> Those are aliases. Here's some documentation on veths:
>
> http://backreference.org/2013/06/20/some-notes-on-veth-interfaces/
>
> --Justin
>
>
> On September 28, 2014 at 4:19:03 PM, Xinming Chen ([email protected])
> wrote:
> > Do you mean IP alias like eth1:0, eth1:1? I've tried that but OVS can't
> see
> > any packet on alias interfaces.
> > If this is not what you mean, can you give me a link of veths? I'd be
> glad
> > to try them out.
> >
> > Thanks,
> > Xinming
> >
> > 2014-09-28 18:25 GMT-04:00 Justin Pettit :
> >
> > > Can you connect OVS and Click with something like veths?
> > >
> > > --Justin
> > >
> > >
> > > On Sep 28, 2014, at 2:34 PM, Xinming Chen wrote:
> > >
> > > Hi All,
> > > For some reason we want to put OVS and Click modular router on the same
> > > machine, setting up the OVS as an OpenFlow switch to route IPv4
> traffic,
> > > and Click to route IPv6 traffic.
> > > But we haven't find a way to have both of them working. Both Click and
> OVS
> > > uses kernel modules to intercept packets. And to my understanding, if a
> > > packet goes into OVS, it will be controlled by OVS until it is sent
> out of
> > > a port. The same applies to Click.
> > > Is there a way that can classify the packets and make OVS only
> intercept
> > > the IPv4 packets? or is there a way that OVS can hand the packet to
> Click
> > > once it recognice an IPv6 packet?
> > >
> > > Thanks!
> > >
> > > --
> > > Xinming Chen
> > >
> > > _______________________________________________
> > > discuss mailing list
> > > [email protected]
> > > http://openvswitch.org/mailman/listinfo/discuss
> > >
> > >
> > _______________________________________________
> > discuss mailing list
> > [email protected]
> > http://openvswitch.org/mailman/listinfo/discuss
> >
>
>
--
Xinming Chen
PhD Candidate
Network Systems Lab, Department of Electrical and Computer Engineering
University of Massachusetts Amherst, MA 01003 USA
<http://security.riit.tsinghua.edu.cn/wiki/Xinming_Chen>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
