Hey there,

@Martin: I'm running Ubuntu 8.10, kernel 2.6.27-7-generic and the virtual
topology is the one described in
http://noxrepo.org/manual/vm_environment.html

yes, it is a virtual setup

regarding vdeslirp, you probably have a point there because I did mess with
it a bit in order to get openflow running. I got a buffer overflow message
from vdeslirp (i think it was when I run start-vm-test, but I can't recall
100%), and I found this post concerning a vde bug:
https://bugs.launchpad.net/ubuntu/+source/vde2/+bug/287109
I followed mariof's advice - downloaded the vde source and changed
slirpvde.c line:
static char pidfile_path[_POSIX_PATH_MAX];
to
static char pidfile_path[PATH_MAX];
and also added #define PATH_MAX 4096 in 3 other files that I got a compile
error, and recompiled vde. I did this kind of blindly, but it did get
openflow running.

Just now i tried to apt-get install vde2, but I still get the same problem


On Wed, Feb 4, 2009 at 8:39 PM, kk yap <[email protected]> wrote:

> Hi Kyrialos,
>
> If you are using a virtual setup, check your vdeslirp.
>
> Regards
> KK
>
> 2009/2/4 kyriakos zarifis <[email protected]>:
> > Hi and thanks for the quick reply
> > yes, I noticed that you answered the same thing only some hours ago.
> >
> > However even if I ignore the test result, I still get the problems when
> > connecting nox to the switch, as described below:
> >
> > Any clues there?
> > Thanks
> >
> > (ps. sorry for the duplicate Martin)
> >
> >>
> >>
> >> When I tried the next the next step of noxrepo.org/manual
> >> <http://noxrepo.org/manual> ( ./nox_core -v -i pgen:10 packetdump ) I
> got:
> >>
> >>
> >>
> ------------------------------------------------------------------------------------------
> >> 00001|packetgen|DBG:waiting for features request
> >> 00002|packetgen|DBG:waiting for features request
> >> ...
> >> ...   /(this went on for 5 secs)/
> >> ...
> >> 01599|packetgen|DBG:waiting for features request
> >> 01600|packetgen|DBG:waiting for features request
> >> 01601|packetgen|DBG:waiting for features request
> >> 01602|packetgen|DBG:waiting for features request
> >> 01603|packetgen|DBG:waiting for features request
> >> 01604|packetgen|DBG:waiting for features request
> >> 01605|nox|WARN:pgen:: closing connection due to timeout after 5 seconds
> in
> >> sending features request state
> >>
> >>
> ------------------------------------------------------------------------------------------
> >>
> >>
> >> I moved on with the guide and tried to set up nox with openflow, setting
> >> up the switch looked ok:
> >>
> >>
> >>
> -----------------------------------------------------------------------------------------
> >> hda:/cdrom# ./dpctl addif nl:0 eth0
> >> eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
> >> device eth0 entered promiscuous mode
> >> send_openflow_skb: send failed: -3                          <-------(I'm
> >> not sure if this is supposed to be here, i guess not)
> >>
> >> hda:/cdrom# ./dpctl addif nl:0 eth1
> >> eth1: link up, 100Mbps, full-duplex, lpa 0x05E1
> >> device eth1 entered promiscuous mode
> >> send_openflow_skb: send failed: -3
> <-------(same)
> >>
> >> hda:/cdrom# ./dpctl show nl:0
> >> features_reply (xid=36c3c26e):dp id:505400000003
> >> tables: exact:131072, compressed:0, general:100
> >> buffers: size:-1, number:256
> >> features: capabilities:0x17, actions:0xff
> >> 0(eth0): addr:50:54:00:00:00:03, speed:100, flags:0, feat:0xf
> >> 1(eth1): addr:50:54:00:00:00:04, speed:100, flags:0, feat:0xf
> >> LOCAL(of0): addr:3a:7e:bd:e6:fc:7a, speed:0, flags:0, feat:0
> >> get_config_reply (xid=f93e7de): miss_send_len=128
> >> hda:/cdrom#
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >>
> >>
> >> and the same problem reflected when I tried to connect the controller
> with
> >> the switch :
> >>
> >>
> >> [NOX screen]:
> >>
> >>
> --------------------------------------------------------------------------------------
> >> (initialization ommited but looked fine)
> >> ...
> >> 00028|openflow|DBG:Passive tcp interface bound to port 2525
> >> 00029|openflow|DBG:Passive tcp interface received connection
> >> 00030|nox|WARN:stream: closing connection due to timeout after 5 seconds
> >> in sending features request state
> >> 00031|openflow|DBG:Passive tcp interface received connection
> >> 00032|nox|WARN:stream: closing connection due to timeout after 5 seconds
> >> in sending features request state
> >> 00033|openflow|DBG:Passive tcp interface received connection
> >> 00034|nox|WARN:stream: closing connection due to timeout after 5 seconds
> >> in sending features request state
> >> 00035|openflow|DBG:Passive tcp interface received connection
> >> 00036|openflow|WARN:stream: connection closed by peer
> >>   <---(this was when i sent Ctrl^C to the openflow switch (screen below)
> >> 00037|nox|WARN:Error sending features request: Unknown error 4294967295
> >>
> >>
> --------------------------------------------------------------------------------------
> >>
> >> [openflow switch screen]:
> >>
> >>
> --------------------------------------------------------------------------------------
> >> hda:/cdrom# ./secchan nl:0 tcp:10.0.2.2:2525 <http://10.0.2.2:2525>
> >> 00001|rconn|WARN:nl:0: connected
> >> 00002|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
> >> 00003|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connection
> >> closed
> >> 00004|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
> >> 00005|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connection
> >> closed
> >> 00006|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
> >> 00007|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connection
> >> closed
> >> 00008|rconn|WARN:tcp:10.0.2.2:2525 <http://10.0.2.2:2525>: connected
> >> Ctrl^C
> >>
> >>
> --------------------------------------------------------------------------------------
> >>
> >>
> >> Has anyone come across any similar problem?
> >> Any input appreciated
> >>
> >> Regards,
> >> Kyriakos
> >>
> >>
> >> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> nox-dev mailing list
> >> [email protected]
> >> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >>
> >
> > _______________________________________________
> > nox-dev mailing list
> > [email protected]
> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> >
> >
>
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to