I don't know much of anything about this configuration, but I think you are
missing "config interface" lines for the other ports in your
/etc/config/network file. You have one for eth0.0 and eth0.4, but I think you
need it for your additional ports as well.
Alternately, if you removed ports et
Also, When I do
ps aux | grep ofprotocol
1712 root 1040 Sofprotocol unix:/var/run/dp0.sock tcp:
130.127.39.200:
1758 root 1352 Sgrep ofprotocol
But I don't get anything for ofprotocol when i run ps aux. (I'm not sure if
that matters? Just because
http://www.openflowswitch.or
Yes Nox Zaku.
The only messages I get on the controller side are:
2|nox|WARN:stream: closing connection due to timeout after 5 seconds in
receiving features reply state
On Wed, Sep 22, 2010 at 5:03 PM, Kyriakos Zarifis wrote:
> this is running NOX Zaku? Did you get any helpful messages on
this is running NOX Zaku? Did you get any helpful messages on the controller
side? (looks like it connected for an instant)
On Wed, Sep 22, 2010 at 1:45 PM, Aaron Rosen wrote:
> Hello,
>
> I'm trying to setup a Wrt54GL to run openflow 1.0. I've installed the image
> and have configured my /etc/c
Yes,
I followed Kyriakos instructions and it seemed to build fine. (Though
currently, I think i'm having configuration problems with my Wrt).
Thanks!
Aaron
On Wed, Sep 22, 2010 at 4:31 PM, Bob Lantz wrote:
> I expect we will update the tutorial VM (and tutorial module) to nox-zaku,
> but we h
Hello,
I'm trying to setup a Wrt54GL to run openflow 1.0. I've installed the image
and have configured my /etc/config/network to be the following:
VLAN configuration
config switch eth0
option enable 1
config switch_vlan eth0_0
option device "eth0"
option vlan 0
optio
I expect we will update the tutorial VM (and tutorial module) to nox-zaku, but
we haven't done so yet.
In the mean time, there is nothing preventing you from checking out a new
nox-zaku and
building it! I built and ran nox-destiny in the tutorial VM without any
problems.
I don't have the code
Basically, you need to do what is described here for the example of
pyloop.py:
http://noxrepo.org/noxwiki/index.php/Developing_in_NOX#Building_a_Python_only_component
let us know if this works.
Regards
On Wed, Sep 22, 2010 at 12:40 PM, Kyriakos Zarifis wrote:
> Hi Aaron,
>
> it looks like the t
Hi Aaron,
it looks like the tutorial's VM is using an old NOX version.
In order to use the tutorial component with Zaku, I guess the easiest thing
to do is throw it in the nox/src/coreapps/examples directory.
You'd also need to add it in the Makefile.am of the same directory, and also
add an entry
Hello,
I'm trying to play around with nox and write my own controller. I have
successfully completed the HOTITutorial2010 . I'm now trying to now port
this controller for use with real hardware. I've installed the Openflow Wrt
1.0 image to an WRT54GL and I run ./nox_core -i ptcp:6633 pytutorial
Hi Stanislav
It seems to me the problem is that the spec is limiting. This might be
a message more appropriate for the openflow-discuss list.
Thanks
Srini.
On Fri, Sep 17, 2010 at 10:01 AM, Stanislav Lange
wrote:
> Hello,
>
> I would like my module to receive a list of installed flows from an Op
Hi Duong,
There is a set_route function in the flowroute_cache component. You
can find more details in the doxygen documentation.
Regards
KK
On 22 September 2010 07:44, duong nguyen wrote:
> Hi KK,
> Can you explain more concretely.
> where should I populate flowroute_cache. If I have to modif
Hi Duong,
The way to show flows has changed. You need to populate
flowroute_cache to see them. This is to give experiment on control on
what flows to show.
Regards
KK
On 22 September 2010 00:23, duong nguyen wrote:
> I think ENVI (git) lack of something to display flow.
> I can see flows with
Ah, I just saw that you resolved the error code/types.
Did you try to wireshark the problematic flow_mod packets to verify that
they look like what you want them to?
On Wed, Sep 22, 2010 at 12:01 AM, Kyriakos Zarifis wrote:
> Hi Guanyao,
>
> I haven't seen this error myself, but looking at the co
Hi Guanyao,
I haven't seen this error myself, but looking at the code it looks like it
is raised when a OFPT_ERROR is received from a switch, and looking at the
spec it looks like switches send this when the negotiated OF version is not
supported:
"If the negotiated version is supported by the re
15 matches
Mail list logo
