Search Mailing List Archives
[mininet-discuss] Connect real host to mininet network(using hwintf.py )
skjaiswal79 at hotmail.com
Wed Dec 25 06:08:47 PST 2013
Thanks for reply 1. Regarding connecting physical host to virtual switch in mininetI have configure eth1 without IP in my mininet VM(10.222.41.53 i.e running on my Window desktop ip is 10.222.41.37 and subnet 255.255.252.0 CIDR format ) mininet at mininet-vm:~/mininet/examples$ ifconfig -aeth0 Link encap:Ethernet HWaddr 08:00:27:23:98:a0
inet addr:10.222.41.53 Bcast:10.222.43.255 Mask:255.255.252.0
eth1 Link encap:Ethernet HWaddr 08:00:27:2b:b7:a7
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
and I have change hwintf.py for adding my external floodlight controller IP( ruining on my windows machine 10.222.41.37)and add physical host IP(i.e my windows host ip 10.222.41.37) like this... # try to get hw intf from the command line; by default, use eth1
intfName = sys.argv[ 1 ] if len( sys.argv ) > 1 else 'eth1'
info( '*** Connecting to hw intf: %s' % intfName ) info( '*** Checking', intfName, '\n' )
checkIntf( intfName ) info( '*** Creating network\n' )
net = Mininet()
c1 = net.addController( 'c1', ip='10.222.41.37')
s1 = net.addSwitch('s1')
h1= net.addHost('h1', ip='10.222.41.37')
net.addLink( h1, s1 ) info( '*** Adding hardware interface', intfName, 'to switch',
s1, '\n' )
_intf = Intf( intfName, node=s1 ) when I ran this script using mininet at mininet-vm:~/mininet/examples$ sudo python hwintf.py
*** Connecting to hw intf: eth1*** Checking eth1
*** Creating network
*** Adding hardware interface eth1 to switch s1
*** Note: you may need to reconfigure the interfaces for the Mininet hosts:
[<Host h1: h1-eth0:None pid=5204> ]
*** Configuring hosts
*** Starting controller
*** Starting 1 switches
*** Starting CLI:
mininet> After that my controller attaching all physical device in this subnet to mininet virtual switch.but if want try to ping from h1 to then show following error. mininet> h1 ping 10.222.41.85
PING 10.222.41.85 (10.222.41.85) 56(84) bytes of data.
>From 10.222.41.37 icmp_seq=1 Destination Host Unreachable
>From 10.222.41.37 icmp_seq=2 Destination Host Unreachable My (flood controller is already running with forwarding enable mode then we need not add to any flow for ARP and ICMP)can u help me regarding this what i'm doing wrong here.
I have also followed your following step and Skype is launch but after login in in skpye
getting error Skpye can't connect.
can u help regarding this i'm able to ping internet like google after running nat.py (from h1 host but unable to connect Skype after launching its).
2. Try running skype from within an xterm, or using the 'x' command from the CLI:
mininet> x h1
mininet> h1 skype >& /dev/null &
or (shortcut, but only do this once per host):
mininet> x h1 skype
> Today's Topics:
> 1. Re: Connect real host to mininet network(using hwintf.py )
> (Bob Lantz)
> Message: 1
> Date: Tue, 24 Dec 2013 08:10:45 -0800
> From: Bob Lantz <rlantz at cs.stanford.edu>
> To: Suresh <skjaiswal79 at hotmail.com>
> Cc: "mininet-discuss at lists.stanford.edu"
> <mininet-discuss at lists.stanford.edu>
> Subject: Re: [mininet-discuss] Connect real host to mininet
> network(using hwintf.py )
> Message-ID: <1BAC29A0-C18B-4B00-9520-1C4A13D3920D at cs.stanford.edu>
> Content-Type: text/plain; charset="iso-8859-1"
> p.s. I hope it is extremely clear that by "the 'physical' interface of your vm, the host-only or bridged interface that you created using your virtual machine monitor and are attaching using hwintf.py" I mean a (new) interface (e.g. eth1) that you created for this express purpose. If you have a clear understanding of what kind of network configuration you are trying to create, it will all make sense.
> On Dec 24, 2013, at 8:03 AM, Bob Lantz <rlantz at cs.stanford.edu> wrote:
> > 1. It's probably clear already, but using hwintf.py with a VM, you should add the "physical" interface of your VM, the host-only or bridged interface that you created using your virtual machine monitor and are attaching using hwintf.py, and then you should configure your VMs with appropriate IP addresses and routes so they can talk to either the host-only network or to your LAN.
> > 2. Try running skype from within an xterm, or using the 'x' command from the CLI:
> > recommended way:
> > mininet> x h1
> > mininet> h1 skype >& /dev/null &
> > or (shortcut, but only do this once per host):
> > mininet> x h1 skype
> > On Dec 23, 2013, at 11:55 PM, Suresh <skjaiswal79 at hotmail.com> wrote:
> >> Hello all
> >> I have install mininet vm on my desktop windows machine (ip 10.222.41.37)
> >> And my mininet vm conneted to LAN on eth0 interface and ip is 10.222.41.53
> >> eth0 Link encap:Ethernet HWaddr 08:00:27:23:98:a0
> >> inet addr:10.222.41.53 Bcast:10.222.43.255 Mask:255.255.252.0
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> I am trying to connect my desktop machine which is in same subnet and ip is 10.222.41.37
> >> I mean I want to connect my physical host (not virtual host like in mininet h1, h2) to mininet virtual host.
> >> I m using hwintf.py file for creating virtual switch but I do not know how to add my physical host
> >> Another scenario I want to do on mininet I have install skype 4.2 version
> >> And run nat.py and able to connect (ping gooogle.com) but
> >> If want connect skype with my login id unable to loging.
> >> /mininet/examples#skype &
> >>  1649
> >> (from h1 console)
> >> sudo python nat.py
> >> *** Creating network
> >> *** Adding controller
> >> *** Adding hosts:
> >> h1 h2 h3 h4
> >> *** Adding switches:
> >> s1
> >> *** Adding links:
> >> (h1, s1) (h2, s1) (h3, s1) (h4, s1)
> >> *** Configuring hosts
> >> h1 h2 h3 h4
> >> *** Starting controller
> >> *** Starting 1 switches
> >> s1
> >> *** Hosts are running and should have internet connectivity
> >> *** Type 'exit' or control-D to shut down network
> >> *** Starting CLI:
> >> mininet> h1 ping google
> >> ^Cmininet> h1 ping google.com
> >> PING google.com (220.127.116.11) 56(84) bytes of data.
> >> 64 bytes from maa03s16-in-f3.1e100.net (18.104.22.168): icmp_req=1 ttl=53 time=54.4 ms
> >> 64 bytes from maa03s16-in-f3.1e100.net (22.214.171.124): icmp_req=2 ttl=53 time=53.2 ms
> >> Thanks in advance.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.stanford.edu/pipermail/mininet-discuss/attachments/20131224/255ab135/attachment-0001.html>
> mininet-discuss mailing list
> mininet-discuss at lists.stanford.edu
> End of mininet-discuss Digest, Vol 46, Issue 56
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mininet-discuss