于 2015年01月15日 13:33, Jesse Gross 写道:
On Wed, Jan 14, 2015 at 9:26 PM, Badiger, Vishwanath (Vishwa)
wrote:
Hi,
I am in the process of migrating MSS clamping patch into recent OVS code base
2.3.0. But not finding functions like,
1. subfacet_make_actions()
2. iface_parse_tunnel()
Looks like OVS
Oh, maybe I see the problem: this folder is on a non-Unix fiale system
so it's probably not possible to have Unix sockets there. I'd think
that this would properly produce a different error (not ENOENT) but who
knows what happens in weird corner cases.
On Mon, Jan 19, 2015 at 03:34:59PM -0800, Bo
In any case, just to make absolutely sure, I'd recommend trying to build it in
another directory - I seem to remember having trouble building lots of things
in SharedFolder on VirtualBox.
> On Jan 19, 2015, at 3:26 PM, Bob Lantz wrote:
>
> 1. To answer your question, if two files have the same
1. To answer your question, if two files have the same name, deleting one will
delete the other.
2. I meant to amend this "just guessing, possibly" but I hit send too early ;-)
3. Is NTFS also case-insensitive by default? Could be a possible issue there
too.
4. The Linux kernel cannot be built on
I don't have a Mac but that's counterintuitive: how would a
case-insensitive file system cause "file not found" errors? Maybe you
could explain in more detail.
On Mon, Jan 19, 2015 at 03:14:53PM -0800, Bob Lantz wrote:
> This could happen if your SharedFolder is on a Mac with case-insensitive HFS
This could happen if your SharedFolder is on a Mac with case-insensitive HFS+.
On Jan 19, 2015, at 10:16 AM, Ben Pfaff wrote:
>
>
> On Fri, Jan 16, 2015 at 08:58:14AM +0100, Giuseppe Cofano wrote:
>> 2015-01-15 19:08 GMT+01:00 Ben Pfaff :
>>> On Thu, Jan 15, 2015 at 03:44:28PM +0100, Giuseppe C
I'll try this. Thank you Ben
On Mon, Jan 19, 2015 at 7:03 PM, Ben Pfaff wrote:
> On Mon, Jan 19, 2015 at 06:26:25PM +0100, Azouni Abdelhadi wrote:
> > Thank you for your reply.
> >
> > Actually, I'm supposing I'm in the dataplane so I don't have a direct
> > connection to the controller running
These can be caused by a few different things e.g. if you are firing in packets
at line rate then you will always see some errors here as the FIFO’s will fill
up. However, with the amount of errors you are seeing and the fact that you’ve
reported a 66 byte packet, I would start by checking that
On Mon, Jan 19, 2015 at 03:49:21PM +0800, yewgang wrote:
> Now for some reason I have to write codes like this (My program perform
> ovsdb-client):
>
> LOOP {
>
> important task every 2 second;
> ovsdb_idl_txn_commit_block(txn);
>
> }
>
> If ovsdb-server is OK, o
On Fri, Jan 16, 2015 at 08:58:14AM +0100, Giuseppe Cofano wrote:
> 2015-01-15 19:08 GMT+01:00 Ben Pfaff :
> > On Thu, Jan 15, 2015 at 03:44:28PM +0100, Giuseppe Cofano wrote:
> > > I need to use ovs >=2.3.0 to employ the full set of features of OF1.3.
> > >
> > > When I compile both ovs 2.3.0 and o
Dear ovs-developer,
Now for some reason I have to write codes like this (My program perform
ovsdb-client):
LOOP {
important task every 2 second;
ovsdb_idl_txn_commit_block(txn);
}
If ovsdb-server is OK, ovsdb_idl_txn_commit_block will not block; but if
ovsdb-ser
Ben, Looks like new floodlight install is using port 6653 instead of 6633.
I just changed the port and it is fine.
user1@user1-GT5464:~$ sudo ovs-vsctl list controller
_uuid : 0e9e5fc8-7ae5-4273-a44c-6917955916b9
connection_mode : []
controller_burst_limit: []
controller_rate_li
On Mon, Jan 19, 2015 at 06:26:25PM +0100, Azouni Abdelhadi wrote:
> Thank you for your reply.
>
> Actually, I'm supposing I'm in the dataplane so I don't have a direct
> connection to the controller running on port 6633.
>
> Any idea ?
tcpdump for packets on those ports.
Flow may not mean TCP connection with the current implementation. OVS
uses wildcards to cover the largest amount of traffic with the
smallest number of flows to improve performance. In theory, if MSS
clamping were enabled, it could force the installed flows to match TCP
connections; in practice thi
Thank you for your reply.
Actually, I'm supposing I'm in the dataplane so I don't have a direct
connection to the controller running on port 6633.
Any idea ?
Abdelhadi
On Mon, Jan 19, 2015 at 6:10 PM, Ben Pfaff wrote:
> Have you tried doing a port scan for ports 6633 and 6653?
>
> On Mon, Jan
Any hint?
Giuseppe
2015-01-16 8:58 GMT+01:00 Giuseppe Cofano :
> Here it is
>
>
> 2015-01-15 19:08 GMT+01:00 Ben Pfaff :
>
>> On Thu, Jan 15, 2015 at 03:44:28PM +0100, Giuseppe Cofano wrote:
>> > I need to use ovs >=2.3.0 to employ the full set of features of OF1.3.
>> >
>> > When I compile bot
Have you tried doing a port scan for ports 6633 and 6653?
On Mon, Jan 19, 2015 at 04:20:05PM +0100, Azouni Abdelhadi wrote:
> Hello,
>
> Please, anyone have an idea how to fingerprint an openflow controller from
> the dataplane ?
>
> Thanks
>
> Abdelhadi
>
> On Sat, Jan 17, 2015 at 1:23 AM, Az
On Mon, Jan 19, 2015 at 10:49:54AM -0500, Prasanna Yabaluri wrote:
> Ping does respond from switch to controller ...
>
> root@user1-GT5464:/home/user1# ping 192.168.0.106
> PING 192.168.0.106 (192.168.0.106) 56(84) bytes of data.
> 64 bytes from 192.168.0.106: icmp_seq=1 ttl=64 time=0.399 ms
> 64
Ping does respond from switch to controller ...
root@user1-GT5464:/home/user1# ping 192.168.0.106
PING 192.168.0.106 (192.168.0.106) 56(84) bytes of data.
64 bytes from 192.168.0.106: icmp_seq=1 ttl=64 time=0.399 ms
64 bytes from 192.168.0.106: icmp_seq=2 ttl=64 time=0.390 ms
root@user1-GT5464:/
Hello,
Please, anyone have an idea how to fingerprint an openflow controller from
the dataplane ?
Thanks
Abdelhadi
On Sat, Jan 17, 2015 at 1:23 AM, Azouni Abdelhadi wrote:
> Thank you for you reply Ben. But I think my question was not very clear.
> Actually, I wanna find the controller or jus
Hi all,
I had the following configuration:
ovs-vsctl show
Bridge br-ex
Port "eth0"
Interface "eth0"
Port br-ex
Interface br-ex
type: internal
eth0 being the eth device who's IP was migrated over to br-ex. The OVS
version used here was
I was going through openvswitch docs (OpenStack-131107.pdf and page number 13;
Attached snapshot of page with this mail).
I happen to see that first packet (of flow) goes to ovs-vswitchd (user space)
and this makes decision of how to process THIS FLOW. Later, subsequent packets
hit cached entry
I was going through openvswitch docs (OpenStack-131107.pdf and page number 13).
I happen to see that first goes to ovs-vswitchd (user space) and this makes
decision of how to process THIS FLOW. Later, subsequent packets hit cached
entry in ovs kernel module. Is this design still valid with lates
Dear ovs-developer,
Now for some reason I have to write codes like this (My program perform
ovsdb-client):
LOOP {
important task every 2 second;
ovsdb_idl_txn_commit_block(txn);
}
If ovsdb-server is OK, ovsdb_idl_txn_commit_block will not block; but if
ovsdb-ser
24 matches
Mail list logo
