Hi Justin, Thank you for the reply. It is working now.
What I did? 1. I added eth0 (NAT) of ovs to the bridge. 2. I removed IP for the eth0. 3. I assigned IP for bridge (br0) using DHCP. 4. Made the Host-Only with out any IP. (I mean, I changed vmnet 0 settings as DHCP) 5. Added eth1 to br0 6. Got the IP address on eth0 of Host 1 via DHCP. *In OVS:* *----------* *ovs-vsctl add br br0* *ovs-vsctl add-port br0 eth0* *ifconfig eth0 0 * *dhclient br0 (eth0 should not have any IP while br0 should get an IP now)* *now if we ping www.google.com <http://www.google.com> it works* *next* *ovs-vsctl add-port br0 eth1* *in Host:* *dhclient eth0 (It should fetch an IP from DHCP).* *Then I am able to ping google from here.* *I got this idea from this video * https://www.youtube.com/watch?v=rYW7kQRyUvA *Thanks & Regards,* *RaviCharan* On Wed, Apr 9, 2014 at 4:35 PM, Justin Pettit <jpet...@nicira.com> wrote: > > On April 9, 2014 at 12:21:55 PM, RaviCharan Reddy ( > ravicharanred...@gmail.com) wrote: > > Now I created a bridge on my OVS, added ports eth1 and eth0 to the > bridge. > > When I added eth0 (Which is NAT) I am unable to access Internet via OVS. > > It sounds like this FAQ entry: > > Q: I created a bridge and added my Ethernet port to it, using commands > like these: > > ovs-vsctl add-br br0 > ovs-vsctl add-port br0 eth0 > > and as soon as I ran the "add-port" command I lost all connectivity > through eth0. Help! > > A: A physical Ethernet device that is part of an Open vSwitch bridge > should not have an IP address. If one does, then that IP address > will not be fully functional. > > You can restore functionality by moving the IP address to an Open > vSwitch "internal" device, such as the network device named after > the bridge itself. For example, assuming that eth0's IP address is > 192.168.128.5, you could run the commands below to fix up the > situation: > > ifconfig eth0 0.0.0.0 > ifconfig br0 192.168.128.5 > > (If your only connection to the machine running OVS is through the > IP address in question, then you would want to run all of these > commands on a single command line, or put them into a script.) If > there were any additional routes assigned to eth0, then you would > also want to use commands to adjust these routes to go through br0. > > If you use DHCP to obtain an IP address, then you should kill the > DHCP client that was listening on the physical Ethernet interface > (e.g. eth0) and start one listening on the internal interface > (e.g. br0). You might still need to manually clear the IP address > from the physical interface (e.g. with "ifconfig eth0 0.0.0.0"). > > There is no compelling reason why Open vSwitch must work this way. > However, this is the way that the Linux kernel bridge module has > always worked, so it's a model that those accustomed to Linux > bridging are already used to. Also, the model that most people > expect is not implementable without kernel changes on all the > versions of Linux that Open vSwitch supports. > > By the way, this issue is not specific to physical Ethernet > devices. It applies to all network devices except Open vswitch > "internal" devices. > > --Justin > > > > > -- Thanks & Regards, RaviCharan Masters - Network Communications E-mail: *rrkal...@uh.edu <rrkal...@uh.edu>* Contact: 832-914-3923
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
