It works for me now after I tried ap mode rather than ad hoc. Is there any special consideration to have OpenFlow working on a wireless interface that's client mode? My plan was to interconnect five TL-WR1043ND through wireless connections.
Cheers, Alison On Wed, Nov 13, 2013 at 12:14 PM, Yiannis Yiakoumis <yiann...@stanford.edu> wrote: > You can try a few things. > - Check if the AP connects to the controller. > - Start with two wired nodes to eliminate wireless issues. > - Check that hostapd is running at the AP. > - Does the client get WLAN-associated, but packets can't go through, or it > cannot even associate to your WiFi network... > > > On Wed, Nov 13, 2013 at 5:22 AM, Suneth Namal Karunarathna > <gkaru...@ee.oulu.fi> wrote: >> >> Hi, >> I tried with wlan0. Yes, it works. But, still user can't associate with >> the AP. Any suggestion?? >> I used static IPs. >> >> Namal >> >> >> On 12.11.2013 20:21, Yiannis Yiakoumis wrote: >> >> Try with wlan0 instead of radio0. >> >> Y. >> >> >> On Tue, Nov 12, 2013 at 10:08 AM, Alison Chan <chan7...@kettering.edu> >> wrote: >>> >>> Hello, >>> >>> I just enabled the wireless interface in TL-WR1043ND to be controlled >>> by openflow. But when I log in, ofdatapath isn't running, and >>> /etc/init.d/openflow restart gives the following: >>> >>> root@OpenWrt:/# /etc/init.d/openflow restart >>> eth0.1,eth0.2,eth0.3,eth0.4,radio0 >>> Configuring OpenFlow switch for out-of-band control >>> Jan 01 00:01:44|00001|netdev|ERR|ioctl(SIOCGIFINDEX) on radio0 device >>> failed: No such device >>> ofdatapath: failed to add port radio0 (No such device) >>> No need for further configuration for out-of-band control >>> >>> I've added radio0 with correct settings to /etc/config/wireless. >>> wireless, network, and openflow configs are as in this gist: >>> https://gist.github.com/alis0nc/7435766 >>> >>> Any assistance would be most appreciated. thanks! >>> >>> -- >>> Alison Chan >>> chan7...@kettering.edu >>> +1 909 278 7753 >>> >>> Sedulously eschew obfuscatory hyperverbosity or prolixity. >>> _______________________________________________ >>> openflow-discuss mailing list >>> openflow-discuss@lists.stanford.edu >>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> >> >> >> >> _______________________________________________ >> openflow-discuss mailing list >> openflow-discuss@lists.stanford.edu >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> >> >> >> _______________________________________________ >> openflow-discuss mailing list >> openflow-discuss@lists.stanford.edu >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> > > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > -- Alison Chan chan7...@kettering.edu +1 909 278 7753 Sedulously eschew obfuscatory hyperverbosity or prolixity. _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
