Hi Niky,
something tells me this was introduced with a patch that I was asked to push
a while back (df58e02b9dec24564878e0d77274f551d349e070). I reverted it for
now, which I think temporarily corrects this (can you verify?) and i'll try
to push a real fix soon.
On Thu, Oct 14, 2010 at 9:47 PM,
didn't look at the original problem, but the rolled back patch does look
wrong to me. I think it's almost right now, but the last part should be
arr[i + 2]
On Oct 15, 2010 12:58 AM, Kyriakos Zarifis kyr.zari...@gmail.com wrote:
___
nox-dev mailing list
This is sort of my solution as well, with the only exception. Because
the switch might connect, disconnects and connect again before
the timer fires, in which case the if connected[dpid] will return true
although there was a disconnection in the middle, I also keep
track of which dpids currently
I am running nox zaku as released on the September 15th, should I update?
--niky
James McCauley wrote:
didn't look at the original problem, but the rolled back patch does
look wrong to me. I think it's almost right now, but the last part
should be arr[i + 2]
On Oct 15, 2010 12:58 AM,
Are you sure this is NOX 0.6.0? Where/how did you get the code? What does
grep ^VERSION Makefile (in your build directory) say?
.. I just want to be sure we know what we're dealing with here.
-- Murphy
On Oct 15, 2010, at 3:01 PM, Chui-Hui Chiu wrote:
Hi, all,
I have encountered a weird
JM Are you sure this is NOX 0.6.0? Where/how did you get the code? What
JM does grep ^VERSION Makefile (in your build directory) say?
Sorry to keep banging this drum, but: This sort of thing would be a lot
easier to keep track of if people who wanted a particular version could
download a tarball
rant
Actually in this case, Chui-Hui will not be able to anything if we
have went the tarball way. We are essentially not very customized to
CentOS. Tarballs are also particularly hard to update.
/rant
Regards
KK
On 15 October 2010 18:04, Josh Smift j...@bbn.com wrote:
JM Are you sure this is
Hi,
Given that this bug is blocking one of the Gec9 plenary demos, I would
like to start debugging it.
Do you have an idea where should I start looking? In which file do you
believe the problem is?
Thanks,
niky
Niky Riga wrote:
I am running nox zaku as released on the September 15th,
Hey Niky,
for a fast fix, and in order to avoid pulling/rebuilding, you can manually
apply this change in lib/packet/tcp.py
(somewhere around line 158 if I recall)
self.options.append(tcp_opt(tcp_opt.MSS,val))
elif arr[i] == tcp_opt.WSOPT:
if
What about having a tcpdump of the control traffic between NOX to/from
FV, and FV to/from switch? Each disconnection will have a new
connection following it, then you will see the hellos, feature
requests and replies, etc.
I would like to see the NOX's log too. NOX typically does not kill a
KK: I've looked through the tcpdumps and the sequence is:
HELLO
HELLO
FEATURE_REQUEST
FEATURE_REPLY
VENDOR MSG
ERROR (vendor unsupported)
PACKET_IN (lldp)
and then disconnect
- Rob
.
On Fri, Oct 15, 2010 at 9:07 PM, kk yap yap...@stanford.edu wrote:
What about having a tcpdump of
Two of the switches are local to stanford and NECs:
necsw2 (00:00:00:12:e2:78:31:f5)
necsw(00:00:00:12:e2:78:67:65)
necsw is the main connection point to the other flowvisors, so it would
receive packet_in's from the other flowvisor.
- Rob
.
On Fri, Oct 15, 2010 at 9:15 PM, kk yap
Sorry... the ... meant more packet_in's.
- Rob
.
On Fri, Oct 15, 2010 at 9:15 PM, kk yap yap...@stanford.edu wrote:
ERROR (vendor unsupported)
PACKET_IN (lldp)
and then disconnect
Can I know the model of the switch, and what ... means? The front
part looks correct at a glance.
Can someone send the pcap file on the list, so that people can
actually start doing real investigation here? If it is too big, send
to Nick Bastin? (Sorry, Nick...)
I would still like to see the NOX's output.
Regards
KK
On 15 October 2010 21:36, Rob Sherwood rob.sherw...@stanford.edu wrote:
I've put the pcapfile on yuba:~capveg/nineveh-fv.tcpdump (for those who have
access... it's a 2MB file).
It's a trace of both to the FV on nineveh:6633 (from the FV on openflow5)
and to the controller on nineveh:1734. If you just filter on port 1734 you
get just the controller traffic.
- Rob
.
15 matches
Mail list logo
