[ovs-discuss] Compile ovs for Andriod

Yongqiang Liu liuyq7809 at gmail.com
Thu Feb 3 05:53:49 UTC 2011


Hi Everyone,
For running ovs on Android, so far i can add wlan interface to the dp0 as a
port, there is no problem, you can see:
# ./ovs-dpctl show dp0
system at dp0:
    flows: cur:0, soft-max:1024, hard-max:1048576
    ports: cur:2, max:1024
    groups: max:16
    lookups: frags:0, hit:0, missed:4153, lost:4053
    queues: max-miss:100, max-action:100
    port 0: dp0 (internal)
    port 1: tiwlan0

but when i added 3G interface, which appears as a ppp0 interface, there is
an error:
# ./ovs-dpctl add-if dp0 ppp0
Feb 02 21:41:03|00001|dpif|WARN|system at dp0: failed to add ppp0 as port:
Invalid argument
ovs-dpctl: adding ppp0 to dp0 failed (Invalid argument)

the following is the interface information of ppp0:
# ifconfig ppp0
ppp0: ip 10.231.190.28 mask 255.255.255.255 flags [up point-to-point running
multicast

Does anyone ever adds point-to-point interface to ovs on PC?
What shall i do to solve this problem?

Thanks



2011/1/28 Ben Pfaff <blp at nicira.com>

> This doesn't make any sense to me.  If there is some equivalent to
> valgrind on android you might want to try that.
>
> This code uses the major(), minor(), and makedev() macros.  I wonder if
> Android has funny definitions of those?
>
> On Fri, Jan 28, 2011 at 11:14:34AM -0800, Yongqiang Liu wrote:
> > Following is the output of running "ovs-dpctl -v show":
> >
> > # ./ovs-dpctl -v show
> > Jan 28 11:07:51|00001|dpif_linux|WARN|/dev/net/dp46388 is device 248:255
> but
> > should be 248:0, fixing
> > system at dp0:
> > Jan 28 11:07:51|00002|dpif|DBG|system at dp0: get_stats success
> >     flows: cur:0, soft-max:1024, hard-max:1048576
> >     ports: cur:2, max:1024
> >     groups: max:16
> >     lookups: frags:0, hit:0, missed:954, lost:854
> >     queues: max-miss:100, max-action:100
> > Jan 28 11:07:51|00003|dpif|DBG|system at dp0: get_stats success
> > Jan 28 11:07:51|00004|dpif|DBG|system at dp0: port_list success
> >     port 0: dp0 (internal)
> >     port 1: tiwlan0
> > Jan 28 11:07:51|00005|dpif_linux|WARN|/dev/net/dp46388 is device 248:0
> but
> > should be 248:1, fixing
> > Jan 28 11:07:51|00006|dpif_linux|WARN|/dev/net/dp46388 is device 248:1
> but
> > should be 248:2, fixing
> > Jan 28 11:07:51|00007|dpif_linux|WARN|/dev/net/dp46388 is device 248:2
> but
> > should be 248:3, fixing
> > Jan 28 11:07:51|00008|dpif_linux|WARN|/dev/net/dp46388 is device 248:3
> but
> > should be 248:4, fixing
> >
> > And the following is the status of the char device:
> >
> > # cd /dev/net/
> > # ls -l
> > crwx------ root     root     248, 255 2011-01-28 11:07 dp46388
> > #
> >
> >
> > 2011/1/28 Ben Pfaff <blp at nicira.com>
> >
> > > On Fri, Jan 28, 2011 at 02:02:15AM -0800, Yongqiang Liu wrote:
> > > > Hi Everyone:
> > > >
> > > > For running ovs on Android phone, so far i have installed
> > > openvswitch_mod.ko
> > > > on Android kernel and cross compiled ovs-dpctl.
> > > > It seems they work on Android:
> > > > 1. I can create a datapath dp0
> > > > 2. i can add phone's wifi interface (tiwlan0) to the dp0
> > > >
> > > > the following is the dp0 status:
> > > > # ./ovs-dpctl show
> > > > system at dp0:
> > > >     flows: cur:0, soft-max:1024, hard-max:1048576
> > > >     ports: cur:2, max:1024
> > > >     groups: max:16
> > > >     lookups: frags:0, hit:0, missed:4, lost:0
> > > >     queues: max-miss:100, max-action:100
> > > >     port 0: dp0 (internal)
> > > >     port 1: tiwlan0
> > > > Jan 28 01:48:39|00001|dpif_linux|WARN|/dev/net/dp46388 is device
> 248:0
> > > but
> > > > should be 248:1, fixing
> > > > Jan 28 01:48:39|00002|dpif_linux|WARN|/dev/net/dp46388 is device
> 248:1
> > > but
> > > > should be 248:2, fixing
> > > > Jan 28 01:48:39|00003|dpif_linux|WARN|/dev/net/dp46388 is device
> 248:2
> > > but
> > > > should be 248:3, fixing
> > > > Jan 28 01:48:39|00004|dpif_linux|WARN|/dev/net/dp46388 is device
> 248:3
> > > but
> > > > should be 248:4, fixing
> > > > Jan 28 01:48:39|00005|dpif_linux|WARN|/dev/net/dp46388 is device
> 248:4
> > > but
> > > > should be 248:5, fixing
> > > >
> > > > But i don't know reason of the dpif_linux WARN message, and is it a
> > > > potential problem, how to fix it?
> > >
> > > That is a really strange error message.  The openvswitch_mod kernel
> > > module creates a character device driver, and the userspace components
> > > create corresponding device nodes /dev/net/dp<N> as needed.  But the
> > > device nodes are only numbered 0 through 255, so /dev/net/dp46388
> > > doesn't make any sense and I don't understand why ovs-dpctl would be
> > > trying to create it.
> > >
> > > Could you run "ovs-dpctl -v show" and post the output?  There will be a
> > > lot of output.  The output might give some hints.
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20110202/ffdf74cb/attachment-0001.html>


More information about the discuss mailing list