Re: [nox-dev] A discovery question

2011-07-14 Thread Kyriakos Zarifis
Exactly, this version is what would make sense to me too :> (And I also doubt NOX currently does what the page claims) On Thu, Jul 14, 2011 at 5:50 PM, Murphy McCauley wrote: > Okay, I just read that page, and... you're right, that's definitely what it > says. It seems to indicate that what it'

Re: [nox-dev] A discovery question

2011-07-14 Thread Murphy McCauley
Okay, I just read that page, and... you're right, that's definitely what it says. It seems to indicate that what it's talking about there is what is "currently implemented in Nox's discovery.py". I think this is false. I won't completely swear to this, but I did just rewrite discovery like tw

Re: [nox-dev] A discovery question

2011-07-14 Thread Kyriakos Zarifis
Hm. That was my impression too, but now looking at the doc again, the phrase "Switch B (OpenFlow -enabled) will update it's internal OFDP table. Switch B will forward the received OFDP advertisement out all other ports." confused me. 2011/7/14 Murphy McCa

Re: [nox-dev] A discovery question

2011-07-14 Thread Murphy McCauley
So the normal LLDP multicast address should never be forwarded. No problem there except that NOX couldn't "see through" intermediate switches there. On the other hand, with the OFDP address... OpenFlow switches still won't forward such messages (NOX looks at them in discovery, but never instruc

Re: [nox-dev] A discovery question

2011-07-14 Thread kk yap
Oops.. I read the GENI document again, and Murphy is right in that the multicast address is different here. My apologies. This address will be forwarded by mac bridges though. Won't this be risking a broadcast storm? Am I missing something again? Regards KK On 14 July 2011 13:23, kk yap wro

Re: [nox-dev] A discovery question

2011-07-14 Thread kk yap
I believe OFDP uses LLDP as Kyriakos mentioned. So, there is no real difference here. As for the question of discovering a "link" between two OpenFlow switches connected by a non-OpenFlow switch, the link will be discovered if the switch does not process LLDP and thus pass it on. Else, the interm

Re: [nox-dev] A discovery question

2011-07-14 Thread Murphy McCauley
Right. Someone correct me if I am wrong here, but really the only difference between OFDP and normal LLDP is that OFDP uses a normal multicast address so that it can see connectivity across non-OpenFlow switches. The purpose being... if you have two OpenFlow switches connected via an intermedi

Re: [nox-dev] A discovery question

2011-07-14 Thread Kyriakos Zarifis
OFDP is a made-up term used to describe how OF uses LLDP packets to perform discovery. There is no such thing as an OFDP packet. The packets used for discovery are LLDP packets. On Thu, Jul 14, 2011 at 4:32 AM, wunyuan wrote: > ** > Hi, > > Thanks for your answer. > > We observe the information

Re: [nox-dev] A discovery question

2011-07-14 Thread wunyuan
Hi, Thanks for your answer. We observe the information from this URL (http://groups.geni.net/geni/wiki/OpenFlowDiscoveryProtocol) this information is that OFDP advertisements are sent to a "normal" multicast MAC (01:23:00:00:00:01), and we find our openflow switch send the lldps to this mac

Re: [nox-dev] A discovery question

2011-07-14 Thread Kyriakos Zarifis
Hi, I'm not sure if I understand the question, but Discovery uses LLDP packets. Short description here: http://noxrepo.org/noxwiki/index.php/Discovery On Thu, Jul 14, 2011 at 3:43 AM, wunyuan wrote: > Hi, > > We have a question about the nox discovery. > > Our NOX version is NOX 0.9.0(zaku) in

[nox-dev] A discovery question

2011-07-14 Thread wunyuan
Hi, We have a question about the nox discovery. Our NOX version is NOX 0.9.0(zaku) in our openflow enviroment. We monitor a port of a openflow by wireshark, and we observe that the lldp packets are sent to a multicast MAC (01:23:00:00:00:01). However we see the discovery.py code and find th