Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[mininet-discuss] Failed to build netoworks using Mininet.

Brandon Heller brandonh at stanford.edu
Wed Mar 28 13:51:48 PDT 2012


On Wed, Mar 28, 2012 at 1:41 PM, Weiyang Mo <wmo at optics.arizona.edu> wrote:

> Thank you.
>
>
>
> Following is what I did:
>
>
>
> I install Openflowtutorial.vdk on VM and the virtual box is installed in
> my native host.
>
>
>
> Now I connect the switch port ETH!(the switch IP address is 192.168.1.1)
> to my native host and manually configure the native host IP address to
> 192.168.1.10.


If your VM is being bridged, the host IP shouldn't matter.   It's the guest
IP that matters.  If your network has MAC registration/filtering, then the
DHCP will fail until you register the guest MAC.



> However when I run "sudo dhclient ethx" in my VM, I cannot get any IP
> address,and I cannot ping the native host or even the switch.
>
>
Tcpdump at the host to see what's passing through.  Tcpdump outside the
host to see if the DHCP requests are coming from the guest.  Verify that
your pronto switch can ping your host.

None of these steps are tied to Mininet; I suggest you find someone local
to help with the networking, as I can't help you to remotely debug these
non-Mininet problems in an efficient way.

-b


>
>
> Many thanks.
>
>
>
> Weiyang
>
>
>
>
>
>
>
> ________________________________
> From: Brandon Heller [brandonh at stanford.edu]
> Sent: Wednesday, March 28, 2012 1:26 PM
> To: Weiyang Mo
> Cc: mininet-discuss at lists.stanford.edu
> Subject: Re: [mininet-discuss] Failed to build netoworks using Mininet.
>
> On Wed, Mar 28, 2012 at 1:19 PM, Weiyang Mo <wmo at optics.arizona.edu
> <mailto:wmo at optics.arizona.edu>> wrote:
> Hi,Thanks very much.
>
>
>
> Do you mean OpenFlow tutorial? I used the Mininet VM before. But the
> problem is that the Pronto openflow switch cannot ping the NOX controller
> in the VM. But I the switch can easily communicate with NOX controller in
> my native host. That's the reason I want to install all things on my native
> host.
>
> It's likely that your VM is NATed behind the host to give it internet
> access.
>
> I would suggest changing the network mode on your virtualization software
> from NAT to bridging.  If the VM can get an address to which the Pronto
> switch can route packets (e.g. on the same subnet), then the pronto should
> be able to connect to your controller.
>
> Once you can ping from the Pronto to your VM, things should work.
>
> -b
>
>
> Best
>
>
>
> Weiyang
>
> ________________________________
> From: Brandon Heller [brandonh at stanford.edu<mailto:brandonh at stanford.edu>]
> Sent: Wednesday, March 28, 2012 1:12 PM
> To: Weiyang Mo
> Cc: mininet-discuss at lists.stanford.edu<mailto:
> mininet-discuss at lists.stanford.edu>
> Subject: Re: [mininet-discuss] Failed to build netoworks using Mininet.
>
> Hi Weiyang,
>
> Are you able to use the provided Mininet VM?  Installation issues like
> these can be hard to debug without access to the remote system.
>
> -b
>
> On Wed, Mar 28, 2012 at 1:04 PM, Weiyang Mo <wmo at optics.arizona.edu
> <mailto:wmo at optics.arizona.edu><mailto:wmo at optics.arizona.edu<mailto:
> wmo at optics.arizona.edu>>> wrote:
> Hi, I reboot it and rum mn-c but same problems happen.
>
>
>
> But I find my version is 2.6.32.33, not the version 2.6.37. But I already
> install it using " sudo ./install.h -k".
>
>
>
> Thanks
>
>
>
> Weiyang
>
> ________________________________
>
> From: Brandon Heller [brandonh at stanford.edu<mailto:brandonh at stanford.edu
> ><mailto:brandonh at stanford.edu<mailto:brandonh at stanford.edu>>]
> Sent: Wednesday, March 28, 2012 12:48 PM
> To: Weiyang Mo
> Cc: mininet-discuss at lists.stanford.edu<mailto:
> mininet-discuss at lists.stanford.edu><mailto:
> mininet-discuss at lists.stanford.edu<mailto:
> mininet-discuss at lists.stanford.edu>>
> Subject: Re: [mininet-discuss] Failed to build netoworks using Mininet.
>
> Is the problem repeatable?  Does it still happen after a reboot (which is
> required after installation) and after you run mn -c (to clear away any
> state that may have been corrupted in this run)?
>
> -b
>
> On Wed, Mar 28, 2012 at 12:37 PM, Weiyang Mo <wmo at optics.arizona.edu
> <mailto:wmo at optics.arizona.edu><mailto:wmo at optics.arizona.edu<mailto:
> wmo at optics.arizona.edu>><mailto:wmo at optics.arizona.edu<mailto:
> wmo at optics.arizona.edu><mailto:wmo at optics.arizona.edu<mailto:
> wmo at optics.arizona.edu>>>> wrote:
> HI,all,
>
> I used "native installation" to install the Mininet on Ubuntu 10.04. There
> are no problems in the process of installation.
>
> However when I try to build a network using mininet using " sudo mn". The
> hosts and switches are successfully added but some problems may happen in
> "adding links". Here is the following information:
>
> Traceback (most recent call last):
>  File "/usr/local/bin/mn", line 5, in <module>
>  pkg_resources.run_script('mininet==0.0.0', 'mn')
>  File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 461, in
> run_script
>  self.require(requires)[0].run_script(script_name, ns)
>  File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1194, in
> run_script
>  execfile(script_filename, namespace, namespace)
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/EGG-INFO/scripts/mn",
> line 276, in <module>
>  MininetRunner()
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/EGG-INFO/scripts/mn",
> line 110, in __init__
>  self.begin()
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/EGG-INFO/scripts/mn",
> line 245, in begin
>  autoStaticArp=arp, listenPort=listenPort )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/net.py",
> line 151, in __init__
>  self.build()
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/net.py",
> line 306, in build
>  self.buildFromTopo( self.topo )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/net.py",
> line 299, in buildFromTopo
>  createLink( src, dst, srcPort, dstPort )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/util.py",
> line 134, in createLink
>  return node1.linkTo( node2, port1, port2 )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/node.py",
> line 315, in linkTo
>  node2.addIntf( intf2, port2 )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/node.py",
> line 279, in addIntf
>  moveIntf( intf, self )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/util.py",
> line 125, in moveIntf
>  retry( retries, delaySecs, moveIntfNoRetry, intf, node, printError )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/util.py",
> line 98, in retry
>  while not fn( *args, **keywords ) and tries < retries:
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/util.py",
> line 112, in moveIntfNoRetry
>  links = node.cmd( 'ip link show' )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/node.py",
> line 241, in cmd
>  self.sendCmd( *args, **kwargs )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/node.py",
> line 186, in sendCmd
>  self.write( cmd + separator + ' printf "\\177" \n' )
>  File
> "/usr/local/lib/python2.6/dist-packages/mininet-0.0.0-py2.6.egg/mininet/node.py",
> line 148, in write
>  os.write( self.stdin.fileno(), data )
> OSError: [Errno 32] Broken pipe
>
>
> Any ideas to solve the problems?
>
> Thanks very much
>
> Best
>
> Weiyang
> _______________________________________________
> mininet-discuss mailing list
> mininet-discuss at lists.stanford.edu<mailto:
> mininet-discuss at lists.stanford.edu><mailto:
> mininet-discuss at lists.stanford.edu<mailto:
> mininet-discuss at lists.stanford.edu>><mailto:
> mininet-discuss at lists.stanford.edu<mailto:
> mininet-discuss at lists.stanford.edu><mailto:
> mininet-discuss at lists.stanford.edu<mailto:
> mininet-discuss at lists.stanford.edu>>>
> https://mailman.stanford.edu/mailman/listinfo/mininet-discuss
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.stanford.edu/mailman/private/mininet-discuss/attachments/20120328/70e550fe/attachment.html>


More information about the mininet-discuss mailing list