Hi all,
KK has pushed a version of NOX 0.6 to yuba that has the 1.0 wire
compatible openflow.h file. The new branch name is nox-for-1.0
Can everyone who is tasked with adding features to NOX please update the
NOX ETA column given that there is now a version of NOX that you can
use. Guido
Hi all,
A while ago I sent a patch to add the ability to send switch config
messages to switches from within Python apps. This diff appears not to
have made it into the 0.50 release.
Here's my patch once again. This patch was made against an old version
of the 0.40 branch -- as a result the
Hi all,
Discovery seems to be sending out LLDP packets on the local OpenFlow
port. This seems a little odd to me as I would expect we're unlikely to
encounter any other switches on the local port.
I'm running the 0.40 pre/beta nox (I haven't yet merged in the latest
changes with 0.40
Hi Nicira,
I need to send switch_config messages to each switch to enable flow
expiry messages (OpenFlow 0.8.9 / 0x97). Since this functionality
doesn't appear to be in Nox by default I added it myself. If you're
interested you can pull the change from our repo -- commit
Just a quick heads-up that no one has tagged the 0.4 release in either
tree (noxrepo/nicira internal).
Not critical, but thought you might want to do it before it gets
forgotten completely.
Glen
___
nox-dev mailing list
nox-dev@noxrepo.org
datapath_join events in Python pass in a dpid and stats dictionary. The
hardware address in stats['ports']['hw_addr'] are ugly -- the data
type is a string.
To use the hardware address in Python I have to do the following
(assuming I want an int):
hw_addr = \0\0 +
Hi all,
Just a quick heads-up that calling install_datapath_flow from python
seems to result in a bogus value in out_port. Not critical since this is
an ADD FLOW command but perhaps it should be cleaned up?
Attached is a capture of a flow mod from pyswitch. Note that the
OpenFlow control
) {
::memcpy(ofm-actions, actions.data(), actions.size());
}
It's definitely setting the outport to OFPP_NONE.
Glen Gibb wrote:
Hi all,
Just a quick heads-up that calling install_datapath_flow from python
seems to result in a bogus value in out_port. Not critical since this
is an ADD FLOW
One more follow-up to my own e-mail.
The code below is in your internal version but not in the version I just
pulled from noxrepo. Nothing you guys need to do -- I'll just expect to
see that change in noxrepo when you next push.
Have a good weekend,
Glen
Glen Gibb wrote:
Just to follow up
Hi Nicira,
When you get a chance can you push a version of NOX that is compatible
with 0x97 to noxrepo.org please?
In the mean time I'll pull from your internal repo.
Thanks,
Glen
___
nox-dev mailing list
nox-dev@noxrepo.org
Ben Pfaff wrote:
Glen Gibb [EMAIL PROTECTED] writes:
When you get a chance can you push a version of NOX that is compatible
with 0x97 to noxrepo.org please?
In the mean time I'll pull from your internal repo.
I'm not sure that we've yet added support for 0x97 to NOX, but we
Actually, this specific problem doesn't have a cure in our local
branch, but one can work around it using the reactor.callFromThread
call which executes a function within the reactor's thread. The
example below worked just fine on our local branch and it *should*
work with the noxrepo.org
I'm afraid that trying to use signal gives the following error:
ValueError: signal only works in main thread
Martin Casado wrote:
I think
import signal
signal(signal.SIGHUP, foo)
should work.
Is there an easy way to get a Nox python application to respond to
SIGHUP?
Thanks,
Glen
Hi all,
Just wanted to alert you to the fact that occasionally I see flow expiry
messages from one of our wireless APs running nox-box in which there is
no flow information: Here a sample event object as seen by Python:
{'datapath_id': 58939760960L, 'this': Swig Object of type 'pyevent *'
Yeah, just picked that up myself.
Thanks,
Glen
Natasha Gude wrote:
That gets fixed in commit a64fdb162f43b1bcacdeacd61a4541a539cb163b.
Should be datapath_id (missing an 'a')
On Sep 5, 2008, at 4:17 PM, Glen Gibb wrote:
Actually if I explicitly list pyrouting and pyauthenticator
I discovered a topology that broke my previous implementation. An
updated implementation is attached.
Glen
Glen Gibb wrote:
Hi all,
I've implemented basic spanning tree support for NOX as a Python app.
I've attached my implementation as a diff. This requires the
send_port_mod patch that I
My mistake here. UINT32_MAX is the same as -1 for signed numbers. :-)
Thanks for pointing that out Brandon.
Glen Gibb wrote:
Hi all,
In install_datapath_flow in core.py we have:
def install_datapath_flow(self, dp_id, attrs, max_idle, actions,
buffer_id
. We're looking
to include actions such as disabling ports, but that's not in there yet.
--Justin
On Aug 9, 2008, at 12:36 PM, Martin Casado wrote:
I'm not sure port mod is supported in the OF reference
implementation. Justin/Ben?
On Aug 8, 2008, at 4:42 PM, Glen Gibb wrote:
Hi all
attached.
Glen
Glen Gibb wrote:
Hi all,
Attached are the diffs to enable me to send port mods from python.
Feel free to integrate the diff and let me know if you have any
comments/questions.
Oh, and to actually send a port mod I just do this from my app:
self.ctxt.send_port_mod(dp, set_port(port
out the OF interfaces;
maybe this will help in the meantime.
-Brandon
On Wed, Jul 30, 2008 at 11:42 AM, Glen Gibb [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
We plugged an HP ProCurve switch into an OpenFlow switch today and
it caused crashes in discovery
Here's the full LLDP packet.
Glen
Martin Casado wrote:
That would be very helpful. Thanks.
On Jul 30, 2008, at 3:32 PM, Glen Gibb wrote:
I think the LLDP inside the Packet In is truncated. Let me know if
you need the whole packet.
Glen
Martin Casado wrote:
Thats what I get for reading
Hi all,
I notice that the format of fields in the flow dictionary/object appears
different in Flow_in versus Flow_expiry in Python.
In Flow_in, if I do a print event.flow I get:
{'dl_type': 2054, 'nw_dst': 2873313822L, 'dl_src': 345045179815L,
'nw_proto': 0, 'tp_dst': 0, 'tp_src': 0,
Hi Nicira,
I've got a documentation feature request for you. Can you add a section
to the manual outlining events and event ordering. As an application it
would be useful to have a list the order of events that NOX generates if
a new host is connected to the network and sends in a packet.
Ben Pfaff wrote:
Glen Gibb [EMAIL PROTECTED] writes:
Ben Pfaff wrote:
Glen Gibb [EMAIL PROTECTED] writes:
I've got another issue here, this time to do with flow
establishment. I'm trying to ping from one host to another through
a bunch of OF switches -- this succeeds
connected to the same port as a switch, which is
incorrect. In the test code, the inport/outport fields of the
FullRoute object describe where the endhosts are connected, not where
the links are connected (which is on port 0).
Natasha
On Jul 18, 2008, at 8:16 PM, Glen Gibb wrote:
Hi all
Hi all,
Perhaps I'm misunderstanding the get_route event but I'm getting error
messages like the following at times:
8|routing|ERR:Invalid route between aps 1731efa639:3 and
1731ed8d28:0 (inport == outport)
Can someone clarify what this error means? As far as I can tell this
error doesn't
Hi all,
What would trigger a Buffer_id xxx at internal ap message?
Thanks,
Glen
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Hi all,
I've got another issue here, this time to do with flow establishment.
I'm trying to ping from one host to another through a bunch of OF
switches -- this succeeds if the OF switches are brought up before NOX
but fails if the OF switches are brought up after NOX.
The details are as
Ben Pfaff wrote:
Glen Gibb [EMAIL PROTECTED] writes:
I've got another issue here, this time to do with flow establishment.
I'm trying to ping from one host to another through a bunch of OF
switches -- this succeeds if the OF switches are brought up before NOX
but fails
29 matches
Mail list logo
