Seems like the authenticator is dying here. It seems to be locked in a loop for your requesting host 10.10.11.34. I could not replicate the error on my side. Srini, can you?
I am using the latest zaku. Jean, could you update to that? I did a git pull --rebase this morning. Regards KK On 6 December 2010 18:41, kk yap <yap...@stanford.edu> wrote: > Thanks Jean. I will stare on it when I get to a wireshark capable > terminal tomorrow. > > Regards > KK > > On 6 December 2010 18:31, Jean Tourrilhes <j...@hpl.hp.com> wrote: >> On Mon, Dec 06, 2010 at 05:47:46PM -0800, kk yap wrote: >>> Hi Jean, >>> >>> I am confused you seem to be giving us partial logs >> >> Hi, >> >> Attached you will find a complete log and a complete PCAP >> output, as complete as I could make, and they correspond to the same >> run on the switch without the LAG. >> >> I would like first to know what happenind to packet 135 and >> why the controller did not forward it. Same for packet 151, 165... >> Then, I would like to know why the controller sent packet 133 >> which is clearly a NoX error. >> >> Have fun... >> >> Jean >> > _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
