kk yap | 1 Mar 09:24 2011
Picon

Re: NOX Controller

Hi Prachi,


It is a software.  You can refer to the url in the paper (http://noxrepo.org).

Regards
KK

On 1 March 2011 00:22, prachi dhamorikar <prachi_dh123-/E1597aS9LQxFYw1CcD5bw@public.gmane.org> wrote:
Hi KK,

Is NOX controller used in Openroads is a software program or is it a separate box, like a hardware component which I have to configure separately ?


Regards,
Prachi


_______________________________________________
openflow-discuss mailing list
openflow-discuss@...
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
Dan Talayco | 2 Mar 09:00 2011
Picon

indigo-1.0 web rc3 available

Announcing the availability of the indigo-1.0-web-rc3 release.  This release
targets new users of the Pronto 3290.  In particular, new users should be able
to upgrade to this release without connecting to the serial port.  Instructions
are available here:

http://www.openflowhub.org/display/Indigo/Up+and+Running+on+the+3290

The new image is available at the usual web site:

http://openflow.org/brcm_limited_access/

The filename is indigo-1.0-web-rc3-3290.tgz.  Please let me know if you have 
any problems with the image.

My apologies for the delay in the availability of this release for the LB4G.
It appears to be necessary to upgrade the Linux kernel on this platform in
order to complete the port.  Determining the requirements for this task is
currently underway.

Regards,
Dan
Leonardo Linguaglossa | 2 Mar 16:01 2011
Picon

OpenFlow- NOX compiling problem

Hello everybody,
I am new to OpenFlow and NOX controller and I am trying to install NOX from source.

My configuration is a NetFPGA Cube, with all package installed and also the openflow is already installed, but I am having problems about the installation of Nox.

At first I followed what is said in the install guide using git, but I received:

git clone git://noxrepo.org/nox
Cloning into noxcore...
fatal: The remote end hung up unexpectedly

So I tried to download the source and do the installation in this way, but after doing the ./configure (gone well), when I do the make command, the output is:


openflow-event.cc: At global scope:
openflow-event.cc:68: error: expected ‘,’ or ‘...’ before ‘*’ token
openflow-event.cc:68: error: ISO C++ forbids declaration of ‘ofp_flow_expired’ with no type
openflow-event.cc: In function ‘vigil::Event*<unnamed>::handle_flow_expired(vigil::datapathid, int)’:
openflow-event.cc:72: error: ‘ofe’ was not declared in this scope
openflow-event.cc:72: error: ‘buf’ was not declared in this scope
openflow-event.cc: In function ‘vigil::Event* vigil::openflow_packet_to_event(vigil::datapathid, std::auto_ptr<vigil::Buffer>)’:
openflow-event.cc:277: error: ‘OFPT_FLOW_EXPIRED’ was not declared in this scope
openflow-event.cc:278: error: no matching function for call to ‘handle_packet(vigil::Event* (&)(vigil::datapathid, int), vigil::datapathid&, const ofp_header*&, std::auto_ptr<vigil::Buffer>&)’
make[5]: *** [openflow-event.lo] Error 1
make[5]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src/lib'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src/lib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta'
make: *** [all] Error 2

I hope you could help me, because I don't know how to overcome this problem.
Regards,

Leonardo
_______________________________________________
openflow-discuss mailing list
openflow-discuss@...
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
Srini Seetharaman | 2 Mar 16:07 2011
Picon

Re: OpenFlow- NOX compiling problem

Hi Leonardo
This question is more appropriate for the nox-dev mailing list.

Could you please retry "git clone git://noxrepo.org/nox" ? The old
version you downloaded is for versions of OpenFlow earlier than 1.0.
We don't really support it at this point (I hope your NetFPGA switch
is also ver1.0)

Thanks
Srini.

On Wed, Mar 2, 2011 at 7:01 AM, Leonardo Linguaglossa
<theleos88@...> wrote:
> Hello everybody,
> I am new to OpenFlow and NOX controller and I am trying to install NOX from
> source.
>
> My configuration is a NetFPGA Cube, with all package installed and also the
> openflow is already installed, but I am having problems about the
> installation of Nox.
>
> At first I followed what is said in the install guide using git, but I
> received:
>
>    git clone git://noxrepo.org/nox
> Cloning into noxcore...
> fatal: The remote end hung up unexpectedly
>
>
> So I tried to download the source and do the installation in this way, but
> after doing the ./configure (gone well), when I do the make command, the
> output is:
>
>
> openflow-event.cc: At global scope:
> openflow-event.cc:68: error: expected ‘,’ or ‘...’ before ‘*’ token
> openflow-event.cc:68: error: ISO C++ forbids declaration of
> ‘ofp_flow_expired’ with no type
> openflow-event.cc: In function
> ‘vigil::Event*<unnamed>::handle_flow_expired(vigil::datapathid, int)’:
> openflow-event.cc:72: error: ‘ofe’ was not declared in this scope
> openflow-event.cc:72: error: ‘buf’ was not declared in this scope
> openflow-event.cc: In function ‘vigil::Event*
> vigil::openflow_packet_to_event(vigil::datapathid,
> std::auto_ptr<vigil::Buffer>)’:
> openflow-event.cc:277: error: ‘OFPT_FLOW_EXPIRED’ was not declared in this
> scope
> openflow-event.cc:278: error: no matching function for call to
> ‘handle_packet(vigil::Event* (&)(vigil::datapathid, int),
> vigil::datapathid&, const ofp_header*&, std::auto_ptr<vigil::Buffer>&)’
> make[5]: *** [openflow-event.lo] Error 1
> make[5]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src/lib'
> make[4]: *** [all] Error 2
> make[4]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src/lib'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/netfpga2/nox/nox-0.4.0~beta'
> make: *** [all] Error 2
>
> I hope you could help me, because I don't know how to overcome this problem.
> Regards,
>
> Leonardo
>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@...
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
>
kk yap | 2 Mar 17:34 2011
Picon

Re: Manipulating Wirefilter!!!

Hi Fahad,

This is a good place to start reading.
http://wiki.virtualsquare.org/wiki/index.php/VDE.  Hope this get you
started.

Regards
KK

On 1 March 2011 16:43, Fahad Rashid <fahad.rashid444@...> wrote:
> Hi KK,
>
>       I am new to openflow. i am doing work on wirefilter.I wanted to ask
> how can we log into the wirefilter through the
>
> management UNIX socket? I was reading the article of Tweaking
> the configuration but its not clearly explained in there.
>
> It say "You can use unixterm to configure the VDE switch during runtime, via
> the management UNIX socket invde/ctl<VDE switch name>." but i dont know how
> to do it.What basically is unixterm? and how to configure VDE switches
> through it.I have implemented openflow in a single pc.(nox zaku 0.9)
>
> Waiting for your reply
>
> Regard
>
> Fahad
Yi-Shou | 7 Mar 16:53 2011
Picon

Setting VLAN_ID by nox controller, but it's error

Hi,

My nox controller version is 0.8.0 full beta, and my OpenFlow version is 1.0.0,
I want setting VLAN_ID to OpenFlow by nox controller, so I edit pyswitch.py, see below:

------------------------------

-----------------------------------------
def forward_l2_packet(dpid, inport, packet, buf, bufid):
    dstaddr = packet.dst.tostring()
    print "test"
    if not ord(dstaddr[0]) & 1 and inst.st[dpid].has_key(dstaddr):
        prt = inst.st[dpid][dstaddr]
        if  prt[0] == inport:
            log.err('**warning** learned port = inport', system="pyswitch")
            inst.send_openflow(dpid, bufid, buf, openflow.OFPP_FLOOD, inport)
        else:
            # We know the outport, set up a flow
            log.msg('installing flow for ' + str(packet), system="pyswitch")
            flow = extract_flow(packet)
            flow[core.IN_PORT] = inport
            #actions = [[openflow.OFPAT_OUTPUT, [0, prt[0]]]]
####################modification#####################
       actions = [[openflow.OFPAT_SET_VLAN_VID, 2]]
###################################################
            inst.install_datapath_flow(dpid, flow, CACHE_TIMEOUT,
                                       openflow.OFP_FLOW_PERMANENT, actions,
                                       bufid, openflow.OFP_DEFAULT_PRIORITY,
                                       inport, buf)
---------------------------------------------------------------------------

Then I execute nox controller and OpenFlow
Execution in NOX controller:
./nox_core -i ptcp:6633 pyswitch -v
Execution in OpenFlow switch:
ofdatapath punix:/var/run/testa -d 004E46000000 -i nf2c0,nf2c1,nf2c2,nf2c3 &
ofprotocol unix:/var/run/testa --out-of-band --stp tcp:xxx.xxx.xxx.xxx:6633 -l ptcp:5566

Then, I got some errors in OpenFlow:
Mar 07 00:35:09|00001|secchan|INFO|OpenFlow reference implementation version 1.0.0
Mar 07 00:35:09|00002|secchan|INFO|OpenFlow protocol version 0x01
Mar 07 00:35:09|00003|secchan|WARN|new management connection will receive asynchronous messages
Mar 07 00:35:09|00004|rconn|INFO|unix:/var/run/testa: connecting...
Mar 07 00:35:09|00005|rconn|INFO|tcp:xxx.xxx.xxx.xxx:6633: connecting...
Mar 07 00:35:09|00006|rconn|INFO|unix:/var/run/testa: connected
Mar 07 00:35:09|00007|port_watcher|INFO|Datapath id is 004e46000000
Mar 07 00:35:09|00008|port_watcher|INFO|Identified data path local port as "tap0".
...
Mar 07 00:35:09|00013|rconn|INFO|tcp:xxx.xxx.xxx.xxx:6633: connected
Mar 07 00:35:09|00001|datapath|WARN|unknown vendor: 0x2320
...
ofdatapath: lib/ofpbuf.c:168: ofpbuf_prealloc_headroom: Assertion `size <= ofpbuf_headroom(b)' failed.
Mar 07 00:35:12|00002|fault|EMER|Caught signal 6.
  0xbf9425c8
Mar 07 00:35:12|00003|fault|EMER|Caught signal 11.
  0x00000000
Mar 07 00:35:12|00018|netdev|ERR|ioctl(SIOCGIFFLAGS) on tap0 device failed: No such device
Mar 07 00:35:12|00019|port_watcher|WARN|could not get flags for tap0
Mar 07 00:35:12|00020|netdev|ERR|ioctl(SIOCGIFFLAGS) on tap0 device failed: No such device
Mar 07 00:35:12|00021|port_watcher|WARN|could not get flags for tap0
Mar 07 00:35:12|00022|rconn|WARN|unix:/var/run/testa: connection dropped (Connection reset by peer)
Mar 07 00:35:13|00023|rconn|INFO|unix:/var/run/testa: connecting...
Mar 07 00:35:13|00024|vconn_unix|ERR|/tmp/vconn-unix.7349.1: connection to /var/run/testa failed: Connection refused
Mar 07 00:35:13|00025|rconn|WARN|unix:/var/run/testa: connection failed (Connection refused)
Mar 07 00:35:13|00026|rconn|INFO|unix:/var/run/testa: waiting 2 seconds before reconnect

Can anybody tell me how to solve this problem?
Any suggest will be helpful. Thank you.


Yi-Shou
_______________________________________________
openflow-discuss mailing list
openflow-discuss@...
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
John B Carter | 7 Mar 22:00 2011
Picon

AUTO: John B Carter is out of the office (returning 03/12/2011)

I am out of the office until 03/12/2011.

I am away from the office until Friday evening, March 12th. In the interim, I will be checking email sporadically. I will get back to you as soon as possible upon my return.

Cheers,
John


Note: This is an automated response to your message "openflow-discuss Digest, Vol 29, Issue 3" sent on 3/7/2011 15:10:31.

This is the only notification you will receive while this person is away.

_______________________________________________
openflow-discuss mailing list
openflow-discuss@...
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
Saeed Attar | 8 Mar 02:35 2011
Picon

OpenFlow - push/pull labels

Hi

I couldn't find any examples on how to use push/pull labels in openflow,
Could any one point me to documentation or example code. in a simple
word how can we add a VLAN tag for a packet entering one port and
leaving through another.

Thanks
Saeed

The information in this e-mail may be confidential and subject to legal professional privilege and/or
copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
Rob Sherwood | 8 Mar 08:24 2011
Picon

Re: OpenFlow - push/pull labels

In OpenFlow version 1.0, the SET_VLAN action implicitly adds a vlan
tag if none exists, but a limitation of 1.0 is that you cannot manage
multiple vlan tags (e.g., QinQ).  You can remove the vlan tag with the
STRIP_VLAN action.

Multiple vlan tags are better handled in the recently released
OpenFlow 1.1 specification, that has explicit push and pop vlan
actions.

Both specifications are available at http://www.openflow.org/wp/documents/

Hope that helps,

- Rob
.

On Mon, Mar 7, 2011 at 5:35 PM, Saeed Attar <saeed.attar@...> wrote:
> Hi
>
> I couldn't find any examples on how to use push/pull labels in openflow,
> Could any one point me to documentation or example code. in a simple
> word how can we add a VLAN tag for a packet entering one port and
> leaving through another.
>
> Thanks
> Saeed
>
> The information in this e-mail may be confidential and subject to legal
> professional privilege and/or copyright. National ICT Australia Limited
> accepts no liability for any damage caused by this email or its attachments.
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@...
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
Max Ott | 8 Mar 09:52 2011
Picon

Re: OpenFlow - push/pull labels

Rob,

Saeed has compiled the OF1.1 version and wants to experiment with QinQ. Is there a simple description on how
to do this for a simple case?

Cheers,
-max

On 08/03/2011, at 6:24 PM, Rob Sherwood wrote:

> In OpenFlow version 1.0, the SET_VLAN action implicitly adds a vlan
> tag if none exists, but a limitation of 1.0 is that you cannot manage
> multiple vlan tags (e.g., QinQ).  You can remove the vlan tag with the
> STRIP_VLAN action.
>
> Multiple vlan tags are better handled in the recently released
> OpenFlow 1.1 specification, that has explicit push and pop vlan
> actions.
>
> Both specifications are available at http://www.openflow.org/wp/documents/
>
> Hope that helps,
>
> - Rob
> .
>
>
>
> On Mon, Mar 7, 2011 at 5:35 PM, Saeed Attar <saeed.attar@...> wrote:
>> Hi
>>
>> I couldn't find any examples on how to use push/pull labels in openflow,
>> Could any one point me to documentation or example code. in a simple
>> word how can we add a VLAN tag for a packet entering one port and
>> leaving through another.
>>
>> Thanks
>> Saeed
>>
>> The information in this e-mail may be confidential and subject to legal
>> professional privilege and/or copyright. National ICT Australia Limited
>> accepts no liability for any damage caused by this email or its attachments.
>> _______________________________________________
>> openflow-discuss mailing list
>> openflow-discuss@...
>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@...
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

The information in this e-mail may be confidential and subject to legal professional privilege and/or
copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

Gmane