Hi ppl!
For the record, bridge and physical interface requires promisc on...
Dam it!
I did found since same issue occurred with single bridge config (without
openvswitch), and tcpdumping interfaces shown a sympthom of some one
unable to see what was happening on the bus... promisc...
My best regards!
On 04-08-2016 14:22, José Tomás ( for openvswitch) wrote:
Hi!
Now I did used tunctl -t <tap name>
Also:
# ovs-ofctl show br1
OFPT_FEATURES_REPLY (xid=0x2): dpid:0000000c29a6034b
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan
mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src
mod_tp_dst
1(ens34): addr:00:0c:29:a6:03:4b
config: 0
state: 0
current: 1GB-FD COPPER AUTO_NEG
advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
supported: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
speed: 1000 Mbps now, 1000 Mbps max
5(tap10): addr:4a:6c:27:62:bf:29
config: PORT_DOWN
state: LINK_DOWN
current: 10MB-FD COPPER
speed: 10 Mbps now, 0 Mbps max
6(tap11): addr:62:73:b6:8a:d8:5a
config: PORT_DOWN
state: LINK_DOWN
current: 10MB-FD COPPER
speed: 10 Mbps now, 0 Mbps max
LOCAL(br1): addr:00:0c:29:a6:03:4b
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
So we see
config: PORT_DOWN
state: LINK_DOWN
which is relevant and makes me answer to you that this should not have
nothing to do with OVS.
But at may old configuration I do get:
34(tapDMZ09): addr:92:5f:ff:27:f5:ba
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
35(tapDMZ10): addr:76:4c:a5:d8:95:64
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
36(tapDMZ11): addr:8e:a8:6b:10:e7:bd
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
37(em1): addr:64:51:06:d8:fd:bc
config: 0
state: 0
current: 1GB-FD COPPER AUTO_NEG
advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-HD 1GB-FD
COPPER AUTO_NEG AUTO_PAUSE
supported: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-HD 1GB-FD
COPPER AUTO_NEG
speed: 1000 Mbps now, 1000 Mbps max
LOCAL(br-main1): addr:64:51:06:d8:fd:bc
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
And for this old config I only have my logs where I just see ovs-vsctl
commands, and I do not have any tunctl installed.
Also this tapDMZ11 and tapDMZ10 are not bounded to any VM.
Also, my old server has Ubuntu 14.10 and OVS 2.1.3
I'm following your recommendation, let me see what I get.
On 2016-08-03 22:38, Justin Pettit wrote:
On Aug 2, 2016, at 10:21 AM, José Tomás@... <...> wrote:
So far I search I always do find
"master ovs-system state UP"
at ip addr show where I get
"master ovs-system state DOWN"
help needed to understand why this...
By the way I'm working with fresh installs for Ubuntu 14.04 and
16.04, same issue... :(
I don't think this is an OVS issue. Have you bound something to the
tap interface to make it come up? There are some discussions on the
web if you search for "tap device down linux" if you haven't read
those yet.
-
--
Tomás
My best regards!
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
