On Sat, Dec 6, 2014 at 2:00 AM, Abhijit Bhopatkar <[email protected]> wrote:
> If your wireless device is always coming up with same name e.g. "usb0" then > just add an entry in /etc/network/interfaces. This will prevent > network-manger from claiming this device and you can configure it as you > need using cli. > > If the name is not same all the time you will have to play with udev to get > that done first. Google for how to make sure ethernet devices are given > same name. mostly editing /etc/udev/rules.d/70-persistent-net.rules > > Also you may want to still use network-manager, you can control it using > "nmcli" through scripts, you don't need the UI or applet running. It might > be better since network manager takes care of lot of things for you esp in > wireless networks. > Thanks Abhijit for this suggestion. Of course I haven't put a 'No' stamp on network-manager in this project. It is just the case that the project involves some proprietary algorithms in networking, where the network-manager might not fit. Besides, I am also doubtful about tech support from nm-community. I posted this 'SAME' message on network-manager mailing list too, but got a too abstract and useless (yet theoretically correct!!!) reply on it, which didn't solve my query. But still in my final image, I will certainly include nmcli though and will try to make use of its capacities wherever the situation permits. By the way, how to mark a thread as 'SOLVED' in this mailing list? > On 28 November 2014 at 05:58, Vasudeo Bidve <[email protected]> wrote: > > > Hi, > > > > I am working on a networking project where only Wi-Fi interfaces are > > used on all hosts for communication. It has to be a private network, > > operating on IPv6 without using DHCP(v6). So obviously, the trick is > > to assign Link-Local IPv6 addresses to all hosts using their > > respective MAC ids and proceed. > > > > I did a proof-of-concept of such networking using Ethernet and PCs > > with ubuntu (14.04 LTS). But this is not working with wireless > > interfaces. > > > > I tried to do this with command line utilities like 'iw' and > > 'iwconfig' on my PCs, but as soon as I plug in the USB-wifi adapter, > > the network-manager in ubuntu sets it in 'managed' mode, which I don't > > want. Further, if I try to assign another mode, I get an error message > > as 'device is busy'. Then by taking the link down, it doesn't add any > > modes. Using the network setting panel in ubuntu, I can configure it > > in 'ad-hoc' mode, but I want to do it programmatically (through a C > > code, shell script, anything) without using that network-manager > > utility finally in my project. > > > > In my project, finally all PCs will be replaced by embedded linux > > SBCs. USB wi-fi adapters will possibly be replaced by wi-fi modules. > > But programmatically, they should be able to communicate with each > > other at Link-Local IPv6 addresses in Ad-Hoc mode. > > > > At this moment, what I need is a set of wireless interface APIs, (of > > course with some helpful documentation) to configure the wifi > > interface in Ad-Hoc mode (possibly in AP/Station mode as and when > > needed), get a Link-Local IPv6 address assigned to itself and start > > networking. Any URL to such information will also do. > > > > If there is any step-by-step guide (or example codes) then it will be > > even more helpful. > > > > Thanks and Regards > > > > Vasudeo K. Bidve > > > > _______________________________________ > > Pune GNU/Linux Users Group Mailing List > > > _______________________________________ > Pune GNU/Linux Users Group Mailing List > _______________________________________ Pune GNU/Linux Users Group Mailing List
