Hey Markus, After clearing some things out i was able to get the traffic into ovs with the approach that you mentioned. Thanks
@Kyle, When I add an internal interface using ovs-vsctl add-port br0 port0 -- set Interface port0 type=internal and then try to bring up this interface, ifconfig port0 up My machine freezes permanently. Its a complete hang and i have to power-rest the machine to bring it back up. I am on a VM. On Mon, Dec 24, 2012 at 10:48 AM, Ahmed Talha Khan <[email protected]> wrote: >> Hi, > >> You could also try using virtual eth pairs, like this: >> >> ip link add type veth >> >> That will give you veth0 and veth1 which are tied together. Connect > one of >> them to your OVS bridge. Then give the other veth an IP >> address, and pump traffic into that, OVS should receive it >> via its pair. > > Hey Markus, I tried this but did not receive any traffic on OVS. > > ip link add type veth > ifconfig veth1 20.20.20.20/32 up(veth0 added to OVS) > > and then i played traffic on veth1 > tcpreplay -i veth1 arp.pcap > > Traffic doesnot reach the other end. The traffic cannot even be seen > on veth1 this way(tcpdump/wireshark) > > > >> Best regards, >> Markus > > > On Tue Dec 18 11:28:20 PST 2012, Ahmed Talha Khan auny87 at gmail.com wrote: >> >> Good. I will give it a try next morning and give the results here. Thanks >> for the guidelines though. I am also curious how does the entire dev team >> does its testing, because you said you adopted this approach. Is this >> approach common to all or there are other methods. What about the method >> that I proposed in my initial email? > > -- > Regards, > -Ahmed Talha Khan -- Regards, -Ahmed Talha Khan _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
