1. 21 Jun, 2017 1 commit
  2. 20 May, 2016 1 commit
    • YAMAMOTO Takashi's avatar
      utilities: Tweak python shebangs to use env · af51e6f0
      YAMAMOTO Takashi authored
      "python" command provided by pkg_alternatives is a shell script.
      At least on NetBSD-7, execve can't execute scripts whose interpreter
      is another shell script.  (While some "rich" shells like zsh seem
      to have handle the case by itself, NetBSD's /bin/sh doesn't.)
      Workaround the issue by using env command for shebangs for
      these scripts.
      
      Noticed with the recent tunnel-push-pop.at tests using ovs-pcap command.
      Signed-off-by: default avatarYAMAMOTO Takashi <yamamoto@ovn.org>
      Acked-by: default avatarBen Pfaff <blp@ovn.org>
      af51e6f0
  3. 02 Jul, 2012 1 commit
    • Ansis Atteka's avatar
      ovs-l3ping: A new test utility that allows to detect L3 tunneling issues · 2d8bdd8f
      Ansis Atteka authored
      ovs-l3ping is similar to ovs-test, but the main difference
      is that it does not require administrator to open firewall
      holes for the XML/RPC control connection. This is achieved
      by encapsulating the Control Connection over the L3 tunnel
      itself.
      
      This tool is not intended as a replacement for ovs-test,
      because ovs-test covers much broader set of test cases.
      
      Sample usage:
      Node1: ovs-l3ping -s 192.168.122.236,10.1.1.1 -t gre
      Node2: ovs-l3ping -c 192.168.122.220,10.1.1.2,10.1.1.1 -t gre
      
      Issue#11791
      Signed-off-by: default avatarAnsis Atteka <aatteka@nicira.com>
      2d8bdd8f
  4. 18 Apr, 2012 1 commit
    • Ansis Atteka's avatar
      ovs-test: Enhancements to the ovs-test tool · 8d25d9a2
      Ansis Atteka authored
      -Implemented support for ovs-test client, so that it could automatically
      spawn an ovs-test server process from itself. This reduces the number of
      commands the user have to type to get tests running.
      -Automated creation of OVS bridges and ports (for VLAN and GRE tests), so that
      user would not need to invoke ovs-vsctl manually to switch from direct, 802.1Q
      and GRE tests.
      -Fixed some pylint reported warnings.
      -Fixed ethtool invocation so that we always try to query the physical interface
      to get the driver name and version.
      -and some others enhancements.
      
      The new usage:
      Node1:ovs-test -s 15531
      Node2:ovs-test -c 127.0.0.1,1.1.1.1 192.168.122.151,1.1.1.2 -d -l 125 -t gre
      Signed-off-by: default avatarAnsis Atteka <aatteka@nicira.com>
      8d25d9a2
  5. 18 Nov, 2011 1 commit