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
>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
