Re: [nox-dev] 6633 routing error

2010-12-09 Thread Abhishek Majumdar
With NOX running, when I start the network I don't see any output.After I've closed NOX and the network I get this: No screen session found. No screen session found. No screen session found. No screen session found. Thanks Abhishek Majumdar On 12/09/2010 02:26 AM, Murphy McCauley wrote: This i

Re: [nox-dev] 6633 routing error

2010-12-09 Thread Abhishek Majumdar
How do I do that? Will running the network do? Thanks Abhishek Majumdar On 12/09/2010 02:26 AM, Murphy McCauley wrote: This indicates that NOX is probably running just fine. You need to get your switches to connect to it. -- Murphy On Dec 9, 2010, at 12:23 AM, Abhishek Majumdar wrote: I t

Re: [nox-dev] 6633 routing error

2010-12-09 Thread Murphy McCauley
This indicates that NOX is probably running just fine. You need to get your switches to connect to it. -- Murphy On Dec 9, 2010, at 12:23 AM, Abhishek Majumdar wrote: > I tried to connect to 6633 with NOX running on the telnet terminal it said > "Connection closed by foreign host." > On the N

Re: [nox-dev] 6633 routing error

2010-12-09 Thread Abhishek Majumdar
I tried to connect to 6633 with NOX running on the telnet terminal it said "Connection closed by foreign host." On the NOX terminal it said "1|nox|WARN:stream: closing connection due to timeout after 5 seconds in sending features request state" Thanks Abhishek Majumdar On 12/08/2010 11:55

Re: [nox-dev] 6633 routing error

2010-12-09 Thread Abhishek Majumdar
Ok. That works. It doesn't give me any error message. But no visible output as well. What is the output supposed to be? Thanks Abhishek Majumdar On 12/09/2010 02:06 AM, kk yap wrote: Try deleting the vde directory. They should be temp files. Regards KK On 8 December 2010 23:38, Abhishek Ma

Re: [nox-dev] 6633 routing error

2010-12-09 Thread kk yap
Try deleting the vde directory. They should be temp files. Regards KK On 8 December 2010 23:38, Abhishek Majumdar wrote: > I don't have the prob with vde_switch anymore. I installed vde2. Now I have > a different problem. When i execute > > vms-start.py  it gives me > > "vde_switch: Could not b

Re: [nox-dev] 6633 routing error

2010-12-08 Thread Abhishek Majumdar
I don't have the prob with vde_switch anymore. I installed vde2. Now I have a different problem. When i execute vms-start.py it gives me "vde_switch: Could not bind to socket '/home/abhishek/opticsproj/vde/ctlof1host1/ctl': Address already in use vde_switch: Cleanup not removing files vde_swi

Re: [nox-dev] 6633 routing error

2010-12-08 Thread kk yap
Hi, I assume you have vde2 installed? What is the output of `which vde_switch`? Regards KK On 8 December 2010 23:21, Abhishek Majumdar wrote: > when i executed vms-start.py it gave me error: > "vde_switch: command not found". How do I fix this. > Also while running NOX, how do i connect/start

Re: [nox-dev] 6633 routing error

2010-12-08 Thread Abhishek Majumdar
when i executed vms-start.py it gave me error: "vde_switch: command not found". How do I fix this. Also while running NOX, how do i connect/start the switches? Thanks Abhishek Majumdar On 12/08/2010 11:55 PM, Murphy McCauley wrote: (CCing the list again) I don't know much about OpenFlowVMS,

Re: [nox-dev] 6633 routing error

2010-12-08 Thread Murphy McCauley
(CCing the list again) I don't know much about OpenFlowVMS, so I can't help you too much with that. But... there seems to be a typo on http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup Try grepping for port 6633 instead or 6663. Also, when yo

Re: [nox-dev] 6633 routing error

2010-12-08 Thread Murphy McCauley
(I've copied the list; it seems to have been dropped accidentally) It's normal behavior for NOX to start up and wait silently for switches to connect to it. Are you running any switches? -- Murphy On Dec 8, 2010, at 9:06 PM, Hasnat Ahmed wrote: > Hi all, > > i am also facing this issue. >

Re: [nox-dev] 6633 routing error

2010-12-08 Thread Murphy McCauley
Were you running any switches that were attempting to connect to it? -- Murphy On Dec 8, 2010, at 7:39 PM, Abhishek Majumdar wrote: > Ok. But it was doing that for a long time. more than 30 mins.?? > Thanks > Abhishek Majumdar > > On 12/8/2010 9:00 PM, Kyriakos Zarifis wrote: >> >> Hi Abhishek

Re: [nox-dev] 6633 routing error

2010-12-08 Thread Abhishek Majumdar
Ok. But it was doing that for a long time. more than 30 mins.?? Thanks Abhishek Majumdar On 12/8/2010 9:00 PM, Kyriakos Zarifis wrote: Hi Abhishek, nothing is necessarily wrong in what you're describing. NOX seems to have started and is waiting for switches to connect. Running nox_core with

Re: [nox-dev] 6633 routing error

2010-12-08 Thread kk yap
Hi Abhishek, > "NOX0.8.0`full`beta (nox_core), compiled Dec 8 2010 19:22:19 This looks suspicious, the current HEAD is zaku as Kyriakos mention. TThe current NOX head is 0.9.0 (zaku), and you should see this which you are not. It might not be critical for you though. FYI. Regards KK On 8 Dece

Re: [nox-dev] 6633 routing error

2010-12-08 Thread Kyriakos Zarifis
Hi Abhishek, nothing is necessarily wrong in what you're describing. NOX seems to have started and is waiting for switches to connect. Running nox_core with the "-v" flag will give you more information about what's happening. Zaku is fine. It's the current HEAD (master branch, and stable version)

[nox-dev] 6633 routing error

2010-12-08 Thread majumdar
After installing everything properly, when i tried the following "$./nox_core -i ptcp:6633 routing" it got stuck in an infinite loop. it gave "NOX0.8.0`full`beta (nox_core), compiled Dec 8 2010 19:22:19 Compiled with OpenFlow 0x01" and the prompt got stuck. I'm using a Ubuntu10Vm, OpenFlow v1.0. A