On Mon, Feb 15, 2010 at 4:55 PM, Todd Deshane wrote:
> On Mon, Feb 15, 2010 at 3:28 PM, Jesse Gross wrote:
> > Again, ovs-dpctl dump-flows is your friend. It will show you the
> currently
> > active flows as well as the actions. You must run it while there is
> traffic
> > on the network due t
On Mon, Feb 15, 2010 at 3:28 PM, Jesse Gross wrote:
> Again, ovs-dpctl dump-flows is your friend. It will show you the currently
> active flows as well as the actions. You must run it while there is traffic
> on the network due to the 5 second timeout.
Your previous response of internalbr and e
On Sat, Feb 13, 2010 at 11:03 PM, Todd Deshane wrote:
>
> So, with this in place, is there any reason why this flow is being deleted:
>
> Feb 13 22:24:23|746001|dpif|DBG|dp0: delete flow in_port:vlan65535
> mac00:11:22:bb:aa:dd->00:1c:0f:95:1d:42 type0800 proto17
> ip128.153.144.73->128.153.N.
On Fri, Feb 12, 2010 at 2:51 PM, Todd Deshane wrote:
> So I think the next problem that I would like to solve is getting the
> host network to work correctly. When I do the obvious of simply
> copying the flows for the VM and changing the mac address to that of
> eth0, the host is not able to work
On Fri, Feb 12, 2010 at 2:51 PM, Todd Deshane wrote:
>
>
> I could probably live without some networking on the host (until I can
> figure it out), but I still do need the host to be able to manage and
> connect to the VMs. Is there a way for me to create some sort of
> bridge or other networking
On Fri, Feb 12, 2010 at 12:27 AM, Justin Pettit wrote:
> Those flow entries all look reasonable to me. I don't see anything that
> would allow SSH or ICMP. Are you sure that you have the correct datapath
> configured? I notice all those packet and byte counters are zero. Can you
> try runni
On Thu, Feb 11, 2010 at 09:27:10PM -0800, Justin Pettit wrote:
> The reason the port numbers weren't showing up before was that the
> flows you were adding weren't fully specified. To the program, it
> looked like you were saying add a flow about port 22, but it doesn't
> know if you're talking ab
On Feb 11, 2010, at 8:12 PM, Todd Deshane wrote:
> Adding tcp and udp made the port numbers show up, which is helpful and
> allowed me to debug some more. I had to allow dns over 5353, as those
> flows were being deleted.
The reason the port numbers weren't showing up before was that the flows yo
Adding tcp and udp made the port numbers show up, which is helpful and
allowed me to debug some more. I had to allow dns over 5353, as those
flows were being deleted.
I found the cause of the second NIC getting an IP on the external
network, that happens when the arp rules are enabled. I will have
The first thing to check is that you're specifying the protocols all
the way up in your flow-add command. For TCP/IP/Ethernet you can use
the shortcut "tcp". Similarly, there's "udp" for UDP, etc. It should
be in the ovs-ofctl man page, but it's easy to miss.
Try that and let us know how th
Hi All,
I almost have open vSwitch working the way I want it to, but I am
running across some unexpected problems. I've setup 2 switches, an
internal and an external, with the initial configuration of:
bridge.internalbr.port=internalbr
bridge.externalbr.port=externalbr
bridge.internalbr.mac=00:11
11 matches
Mail list logo
