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
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
P.S: Which version of nox are you running? I believe this works fine in
destiny.
Aaron
2012/1/12 Aaron Rosen aro...@clemson.edu
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
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
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 jjji...@gmail.com
Hi Aaron,
I'm using the latest
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
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
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
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 the
