>> So i'm asking help for this if you mentioned it! I'm not developer, are you? >> I will pass here any useful info you will ask...script, log or whatever... > > I am a developer. > > Running the command that generates the message under "sh -vx", and > passing along the output, might be insightful.
# sh -vx sh-4.1# service network restart service network restart + service network restart Shutting down interface br0: [ OK ] Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface br0: [ OK ] Bringing up interface eth0: RTNETLINK answers: File exists [ OK ] Oct 26 10:13:05 alpha ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-br br0 Oct 26 10:13:05 alpha kernel: device eth0 left promiscuous mode Oct 26 10:13:05 alpha ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-port br0 eth0 Oct 26 10:13:05 alpha ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-br br0 Oct 26 10:13:05 alpha kernel: device br0 entered promiscuous mode Oct 26 10:13:09 alpha ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-br br0 Oct 26 10:13:09 alpha kernel: r8169 0000:03:00.0: eth0: link down Oct 26 10:13:09 alpha kernel: r8169 0000:03:00.0: eth0: link down Oct 26 10:13:09 alpha ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-port br0 eth0 Oct 26 10:13:09 alpha kernel: device eth0 entered promiscuous mode Oct 26 10:13:09 alpha ovs-vsctl: 00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --may-exist add-br br0 Oct 26 10:13:11 alpha kernel: r8169 0000:03:00.0: eth0: link up >> I have created bridge and added port to it as it is described in >> documentation rhel/README.RHEL <- is it outdated ? > > I don't know. This integration was contributed. I've never > personally tested it. The second question was how to create bridge and put IP on it, if i shouldn't use rhel scripts... As we already understood OVS documentation is not consistent and obvious. >> >> 3. yes i'm talking about compatibility >> >> So how can i remove it after "successful" integration ? (i did by doc >> >> insmod and ovs-brcompatd ) >> > >> > I would suggest not using ovs-brcompatd. >> >> Kidding? I have asked how to Remove this linked module on running >> system after i have inserted it and stop ovs-brcompatd. > > I don't really understand that statement. LOL. It's becoming sad. I have asked, how to uninstall compatibility "module" or what shit it is, from system. Clear? I think you are very junior dev, or your English is very bad, or you are secretary of real developers. Coz reading through this mail-list I've never seen you gave ANY useful information. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
