Hello,My Beacon Controller Hub is unable to connect with the default IP address 
as given in the tutorial:
Tutorial Scenario:Make sure the reference controller used before is not 
running:$ sudo killall controller
You will need to tell the Mininet virtual switches to connect to your host 
machine's IP address. To get that, from your Mininet ssh window run the command 
sudo route:openflow@openflowtutorial:~$ sudo route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.206.0   *               255.255.255.0   U     0      0        0 eth0
default         192.168.206.2   0.0.0.0         UG    0      0        0 eth0
Look for the line that starts with default, and typically your host's IP 
address will be the IP in the Gateway column. If that IP address ends with .1, 
and later you are unable to connect Mininet to Beacon, try the same IP but 
swapping the ending .1 with .2.You should also restart Mininet to make sure 
that everything is "clean". From your Mininet console:mininet> exit
$ sudo mn --topo single,3 --mac --switch ovsk --controller remote --ip 
<your_host_ip>
The --ip parameter defines in which IP your controller is located. Note that 
this is the IP your host uses to communicate with the VM, as discussed above. 
In my case, the VM's IP is 192.168.206.4 and the host's IP is 192.168.206.2 . 
Thus, I started mininet using$ sudo mn --topo single,3 --mac --switch ovsk 
--controller remote --ip 192.168.206.2

Now it's time to start Beacon.Wait until the application indicates that the 
OpenFlow switch has connected. When the switch connects, your Eclipse console 
should print something like this:01:07:31.095 [pool-2-thread-2] INFO 
n.b.core.internal.Controller - Switch connected from 
java.nio.channels.SocketChannel[connected local=/192.168.206.2:6633 
remote=/192.168.206.4:54994]
Here in the above line the connected local is connected to the same IP address 
that was mentioned in the command to create the topology.
Real Scenario:
When I run the Command "sudo route" i get the following 
entries:openflow@openflowtutorial:~$ sudo routeKernel IP routing 
tableDestination     Gateway         Genmask         Flags Metric Ref    Use 
Iface10.0.2.0        *               255.255.255.0   U     0      0        0 
eth7192.168.56.0    *               255.255.255.0   U     0      0        0 
eth8default         10.0.2.2        0.0.0.0         UG    0      0        0 eth7
As per the tutorial my default destination has the IP Address " 10.0.2.2". And 
after running the second command that is :
mininet> exit
$ sudo mn --topo single,3 --mac --switch ovsk --controller remote --ip 
10.0.2.2A topology is created and in my case the Console output by eclipse is 
given below:

osgi> 09:54:58.942 [pool-2-thread-1] INFO  n.b.core.internal.Controller - 
Started thread Thread[pool-2-thread-1,5,spring-osgi-extender[6789b939]-threads] 
for IOLoop IOLoop [id=0 stream_count=0]09:54:58.942 
[SpringOsgiExtenderThread-3] INFO  n.b.core.internal.Controller - Beacon Core 
Started09:54:59.740 [SpringOsgiExtenderThread-4] TRACE 
n.b.tutorial.LearningSwitchTutorial - Starting09:54:59.814 
[SpringOsgiExtenderThread-4] INFO  n.b.core.internal.Controller - Controller 
listening on *:663309:55:05.271 [pool-2-thread-2] INFO  
n.b.core.internal.Controller - Switch connected from 
java.nio.channels.SocketChannel[connected local=/127.0.0.1:6633 
remote=/127.0.0.1:49289]09:55:05.372 [pool-2-thread-2] INFO  
n.b.core.internal.Controller - Added switch OFSwitchImpl 
[Socket[addr=/127.0.0.1,port=49289,localport=6633] DPID[?]] to IOLoop IOLoop 
[id=0 stream_count=1]

So my question is ..why my switch didn't got connected to the default IP 
address that is 10.0.2.2 instead of 127.0.0.1. As according to the tutorial 
scenario the switch must connect to the default IP address( the same that was 
mentioned while creating topology). 
Thank you,









                                          
_______________________________________________
openflow-discuss mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

Reply via email to