Dear Andrew I tried both techniques but no technique is working. Network is behaving the same. When I created two wlan interfaces i.e. wlan0 and wlan1 and I added both interfaces to /etc/config/openflow. I assigned IP's to wlan0 and wlan1 by using ifconfig command and then used these IP's as gateways for devices. IP's which I assigned are as below. IP of WAN port of AP: 192.168.1.1 mask 255.255.255.0 IP of Controller: 192.168.1.2 mask 255.255.255.0 GW: 192.168.1.1 IP of wlan0: 192.168.2.1 mask 255.255.255.0 IP of wlan0-1: 192.168.3.1 mask 255.255.255.0 IP of Client-1: 192.168.2.2 mask 255.255.255.0 GW: 192.168.2.1 (Connected to wlan0) IP of Client-2: 192.168.3.2 mask 255.255.255.0 GW: 192.168.3.1 (Connected to wlan0-1)
I started POX controller and ping client-2 from client-1 but didn't work. Got Destination host unreachable. When I connected both clients to same connection then ping was successful but the problem remains i.e. when controller was down, still devices communicate. similarly I used "option isolated 1" but didn't work for me. When I checked the link http://wiki.openwrt.org/doc/uci/wireless#common.options1 there I found that network option is required but the link below http://archive.openflow.org/wk/index.php/Pantou_:_OpenFlow_1.0_for_OpenWRT#Wireless_Configuration_2 shows network option commented. Can it be the reason? Or the problem is something else? Any suggestion is appreciable. On Mon, Jan 6, 2014 at 9:33 PM, Sayed Qaiser Ali Shah < 11msitqs...@seecs.edu.pk> wrote: > Oh wow great. Thanks a lot Andrew Ferguson. I will definitely try this. > So the problem was with my understanding. I apology. :) > > > On Mon, Jan 6, 2014 at 7:40 AM, Andrew Ferguson <a...@cs.brown.edu> wrote: > >> >> On Jan 6, 2014, at 2:04 AM, Sayed Qaiser Ali Shah < >> 11msitqs...@seecs.edu.pk> wrote: >> >> By response I mean successful response. You must have gone through this >> conversation I did the same what Murphy suggested and you helped me out. >> But still problem didn't solved. >> When I switch on device and controller is not connected, then by >> connecting clients to AP without connecting controller, clients still ping >> each other. >> >> >> did you understand Murphy's message? if not, let me give it a go: you >> should think of the wireless AP as providing, by default, a regular, >> non-OpenFlow switch on each wireless LAN. because of this, the devices >> will still be able to ping each other even if the controller is >> disconnected. it's the same situation as if you attached a physical switch >> or a hub to a single, OpenFlow-controlled port, and then attached the >> laptops to that non-OpenFlow switch, instead of to the OpenFlow port. >> does that make sense? >> >> if you want to implement the scenario you describe, you have two options: >> >> 1) try to disable the default behavior explained above -- this was >> Murphy's suggestion. however, he was able to do it using a different >> wireless AP than you have, so it may not be possible for you. by looking at >> the OpenWRT wiki page for wireless configuration -- >> http://wiki.openwrt.org/doc/uci/wireless -- why don't you try adding: >> >> option isolate 1 >> >> to your wifi-iface section? it should look like something like: >> >> config wifi-iface wlan0 >> option device radio0 >> option mode ap >> option isolate 1 >> option ssid (your network SSID) >> ... >> >> I have not tried this, so I don't know if it will work. the OpenWRT >> wireless page specifically says it does not work for some hardware and some >> releases of OpenWRT, so you might have to build your own OpenWRT + OpenFlow >> image, and even then it is not guaranteed to work. >> >> 2) simply create *two* wireless networks. each wireless network can >> appear as a separate OpenFlow-controlled "port" to your OpenFlow >> controller. if you attach one laptop to the first network, and the second >> laptop to the second network, then you will be able to fully control their >> traffic via the OpenFlow controller. this method is pretty much guaranteed >> to work. :-) >> >> so, your new configuration would look like: >> >> config wifi-iface wlan0 >> option device radio0 >> option mode ap >> option ssid MY-NETWORK-1 >> ... >> >> config wifi-iface wlan1 >> option device radio0 >> option mode ap >> option ssid MY-NETWORK-2 >> ... >> >> >> you will also need to add the second wifi network to your >> /etc/config/openflow. for example, it might look like this: >> >> config 'ofswitch' >> option 'dp' 'dp0' >> option 'dpid' '000000000001' >> option 'ofports' 'eth0.1 eth0.2 eth0.3 eth0.4 wlan0 wlan0-1' >> option 'ofctl' 'tcp:192.168.1.10:6633' >> option 'mode' 'outofband' >> >> >> note that all of this is explained on the Pantou wiki page: >> http://archive.openflow.org/wk/index.php/Pantou_:_OpenFlow_1.0_for_OpenWRT#Wireless_Configuration_2 >> >> >> good luck! >> >> Andrew >> > > > > -- > > > > > *Regards Sayed Qaiser Ali ShahMSIT-12 NUST (SEECS)* > -- *RegardsSayed Qaiser Ali ShahMSIT-12NUST (SEECS)*
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
