On Tue, Feb 9, 2010 at 11:28 AM, Peter Balland wrote:
> On Tue, Feb 9, 2010 at 8:12 AM, Todd Deshane wrote:
>>
>> ovs-dpctl dump-flows internalbr (seems to reveal the problem --
>> actions drop is specified)
>> in_port0003:vlan65535 mac52:54:00:12:34:56->52:54:00:12:34:56 type0800
>> proto1 ip10.
On Tue, Feb 9, 2010 at 11:12 AM, Todd Deshane wrote:
>
> ovs-dpctl dump-flows internalbr (seems to reveal the problem --
> actions drop is specified)
> in_port0003:vlan65535 mac52:54:00:12:34:56->52:54:00:12:34:56 type0800
> proto1 ip10.0.0.2->10.0.0.3 port8->0, packets:45, bytes:4410,
> used:0.8
On Tue, Feb 9, 2010 at 8:12 AM, Todd Deshane wrote:
>
> ovs-dpctl dump-flows internalbr (seems to reveal the problem --
> actions drop is specified)
> in_port0003:vlan65535 mac52:54:00:12:34:56->52:54:00:12:34:56 type0800
> proto1 ip10.0.0.2->10.0.0.3 port8->0, packets:45, bytes:4410,
> used:0.896
Hi Jesse,
On Tue, Feb 9, 2010 at 10:44 AM, Jesse Gross wrote:
> Normally when you create a bridge, you should include the bridge local port.
> For example:
> bridge.internalbr.port=internalbr
> Not only can it cause problems if it is not included but you shouldn't need
> to use dummy0 since that
On Tue, Feb 9, 2010 at 9:25 AM, Todd Deshane wrote:
> The output of ovs-vswitchd ovs-vswitchd.conf is now quieter:
> Feb 09 09:07:47|1|cfg|INFO|using "ovs-vswitchd.conf" as
> configuration file, ".ovs-vswitchd.conf.~lock~" as lock file
> Feb 09 09:07:47|2|ofproto|INFO|using datapath ID 00
Hi Justin,
I tried what you suggested below, but still no connectivity.
The output of ovs-vswitchd ovs-vswitchd.conf is now quieter:
Feb 09 09:07:47|1|cfg|INFO|using "ovs-vswitchd.conf" as
configuration file, ".ovs-vswitchd.conf.~lock~" as lock file
Feb 09 09:07:47|2|ofproto|INFO|using da
