Having no other way to reach the machine will not make things easier. You can do silly tricks like
ssh user@remote "<setup>; sleep 10; <debugging commands>; sleep 10; <teardown>" where teardown would remove eth0 from br0 and put the IP back on it, and debugging commands could be things like starting a ping, dumping the datapath flows, ifconfig results, tcpdumps to files, etc. You also might want to check that the bridge's MAC is correct or irrelevant, that any routing is preserved, no firewalls, etc. -Reid On Tue, Feb 19, 2013 at 5:23 PM, Jing Ai <[email protected]> wrote: > Yeah. Before issuing ssh command, I double check br0 is created by ovs-vsctl > and internal interface br0 is up by ifconfig. > > Best, > Jing > > ________________________________ > Date: Tue, 19 Feb 2013 19:19:40 -0600 > From: [email protected] > To: [email protected] > CC: [email protected]; [email protected] > > Subject: Re: [ovs-discuss] How to smoothly add eth0 to the OVS bridge? > > Do you know whether br0 is actually up once the script terminates? > > I've found that I sometimes need to explicitly 'ifconfig br0 up', although > I'm not really sure why. > > On 02/19/2013 07:01 PM, Jing Ai wrote: > > The script is located on the remote host. I ran it after ssh to the remote > host. > > Now I changed to your way, say from my own host, I issued the following > command: > > ssh root@<remote host> "ovs-vsctl add-port br0 eth0; ifconfig eth0 0; > ifconfig br0 <eth0's ip address>" > > However, I still lost connection to the remote host. Did I still do sth > wrong? > > Best, > Jing > >> From: [email protected] >> Date: Tue, 19 Feb 2013 14:57:43 -0800 >> Subject: Re: [ovs-discuss] How to smoothly add eth0 to the OVS bridge? >> To: [email protected] >> CC: [email protected] >> >> Is the script local or remote? You need to run the command atomically from >> the >> remote perspective. This means you need the ssh command to be a single >> one, >> likely along the lines of: >> >> ssh user@remote remote_script >> >> or >> >> ssh user@remote "command && command ; command" >> >> . A local script would not work unless it invoked all the commands on a >> single >> command line. Hope this helps. >> >> -Reid >> >> PS here's the FAQ note you're referencing: >> (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.) >> >> >> On Tue, Feb 19, 2013 at 2:15 PM, Jing Ai <[email protected]> wrote: >> > Hey, >> > >> > I've noticed that there is already a FAQ illustrating the steps to add >> > eth0 >> > to the bridge, e.g., br0 as follows. >> > >> > ovs-vsctl add-br br0 >> > ovs-vsctl add-port br0 eth0 >> > ifconfig eth0 0.0.0.0 >> > ifconfig br0 <eth0's IP address> >> > >> > Since I issued the above commands on a remote host via ssh, I also put >> > them >> > in a script as instructed. However, when I run such a script, I >> > immediately >> > lost the connection to the remote host. Any idea? >> > >> > Best, >> > Jing >> > >> > >> > _______________________________________________ >> > 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
