Hi Murphy,
It worked. Now I can see the topology module working like a charm. I
still have to fix some issues (surely related to the fact that I have to
set up the flow-mods with the proper VLAN tag to forward the packets).
I would like to thank all of you guys for your help.
El 12/01/2012 1
There have been some changes to logging. Use -v -v.
-- Murphy
On Jan 12, 2012, at 10:10 AM, Sergio Jiménez Feijóo wrote:
> Hi Aaron,
>
> I have moved to the destiny branch and compiled everything again. The
> topology component seems to work fine (I can see "new link detected" messages
> in
Hi Aaron,
I have moved to the destiny branch and compiled everything again. The
topology component seems to work fine (I can see "new link detected"
messages in the log) but now I can't see the log messages of my
application (VLOG_DBG function) despite I'm running NOX with the -v
flag. My app
Hi Sergio,
Could you try to run your application without flowvisor. I find it strange that
flowvisor would be causing a problem here, even though it treats lldp packets
rather awkwardly.
That said, if your setup works without flowvisor then we can definitely say
that flowvisor is at fault and
If you do a packet dump at the flowvisor do you see vlan tags on these LLDP
packets returned to you?
I'm guessing the LLDP packets that are returned to you from the switch (Via
PACKET_IN) ) do not have VLAN tags correct? (The switch takes them off
since this switch isn't acting as a pure of switch
Hi Aaron,
My application that runs on NOX examines the packets and forwards them
keeping the same VLAN ID tag. But how does the topology module tell the
switches that they must send the LLDPs with a certain VLAN ID tag? The
topology module is independent from my application and I can't control
Did you do git checkout -b destiny
When the controller sends the LLDP packet it won't have a vlan tag. Once it
leaves the switch, the switch will add your tag for you. I don't think
that's the problem.
Aaron
2012/1/12 Sergio Jiménez Feijóo
> Hi Aaron,
>
> I'm using the latest version (I thin
Hi Aaron,
I'm using the latest version (I think). I downloaded it from the git
repository by the command "git clone git://noxrepo.org/nox" a few days ago.
My flowspace consists on tagging all my trafic with a certain VLAN ID
(VLAN 13). All the traffic tagged with that VLAN ID belongs to my
f
P.S: Which version of nox are you running? I believe this works fine in
destiny.
Aaron
2012/1/12 Aaron Rosen
> Hi,
>
> I've encountered an issue like this before with flowvisor and the
> discovery module. The easiest thing to do is to change the lldp value in
>
> ./src/nox/lib/packet/ethernet.
Hi,
I've encountered an issue like this before with flowvisor and the discovery
module. The easiest thing to do is to change the lldp value in
./src/nox/lib/packet/ethernet.py
#LLDP_TYPE = 0x88cc
LLDP_TYPE = new_value
then add this new_value, ether_type to your slice.
Hopefully that wi
Hi guys,
I've developed a NOX aplication which needs to use the topology
component to discover the network topology. I've tested my application
in a testbed of 6 Linksys WRT54GL running the OpenWRT Pantou firmware
(without flowvisor) and it worked like a charm. Now I'm testing my
aplication i
I suggest you switch to mininet or OpenFlowVMS which means this
easier. The former being more newer. (Disclaimer: I maintain the
latter).
Regards
KK
On 16 November 2010 11:11, Macapuna, Carlos A. B.
wrote:
> Do you don't need of s4:
>
> SWITCHES="s1 s2 s3 s4 s5"
> s2_SLIRP=yes
> - s4_SLIRP=yes
Do you don't need of s4:
SWITCHES="s1 s2 s3 s4 s5"
s2_SLIRP=yes
*- s4_SLIRP=yes (remove)*
VMS="end1 openflow1 openflow2 end2"
end1_NETS=s1
end2_NETS=s5
openflow1_NETS="s1 *s2* s3"
openflow2_NETS="s3 *s2* s5"
end1_KERNEL=kernel.bin
end2_KERNEL=kernel.bin
openflow1_KERNEL=kernel.bin
openflow2_KERN
I am trying to build the following network topology in NOX
|--| |--|
|-| |--|
| End1 |---| Openflow1 || Openflow2
|-| End 2 |
|--| |--|
|-|
Hi,
It seems like there is something about flowdb and LAVI at the moment.
I will try to take a look at it within this week. My apologies for
the slow reaction.
Regards
KK
2009/11/23 Arturo Veras :
> hi,
> did you try LAVI ? i can see the topology but i cannot see the flows.
>
>
> --
hi,
did you try LAVI ? i can see the topology but i cannot see the flows.
>There are no applications contained in the standard Nox distribrution
>which provide visualization of the topology. However some third party
>apps h
There are no applications contained in the standard Nox distribrution
which provide visualization of the topology. However some third party
apps have been built. For example:
http://www.openflowswitch.org/wk/index.php/LAVI
.m
hi
Is there any application to see the topology of a network?
---
hi
Is there any application to see the topology of a network?
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
18 matches
Mail list logo